PATH “Projects for Assistance in Transition from Homelessness” Workflow June, 2016 1.

Slides:



Advertisements
Similar presentations
ShelterPoint™ Data-Entry Cheat Sheet
Advertisements

2014 HUD Data Standards. New & Active Clients All ESG, CoC and SSVF funded agencies are required to begin collecting data on new and active clients based.
2012 PATH Data Reporting Tison Thomas Substance Abuse and Mental Health Services Administration (SAMHSA) Rachael Kenney & Amy SooHoo SAMHSA Homeless and.
Ohio Balance of State Continuum of Care Introduction to the 2014 HUD Data Standards July 17, 2014.
Wilder Research HMIS and PATH September  General overview and program set-up  Data entry/data collection  Reporting  We will have time for questions.
Fine Print These are the anticipated changes that will occur, some modifications may still occur. The anticipated changes are still being coded. Additional.
HMIS Homeless Management Information System. MISSION To provide standardized and timely information to improve access to housing and services, and strengthen.
Billing Agent. Pre-Application Checklist Introduction to IMPACT and Key Terms Application Process Starting an Application The Business Process Wizard.
1 IRIS Participation Referral Process June What is PPS? The Program Participation System (PPS) is a system used by the State of Wisconsin for many.
Improving Data Entry and Reporting for the HOPWA Program May 2012.
2014 Homeless Management Information Systems (HMIS) Data Standards for ESG Presented by Melissa Mikel September
ClientPoint ™ Data Entry Workflow. ClientPoint “The filing cabinet!” Search for existing clients, or add clients.
2014 HMIS Data Standards Implementation in ServicePoint.
ClientPoint Data Entry Workflow for Outreach ServicePoint 5 1.
How to run APR and APR detail For those who has ART license.
Annual Performance Report ( APR ) Data Entry Workflow.
Emergency Shelter and Housing Assistance Program Data Requirements 12/3/2015.
New User Training for Singles Providers TCP Policy and Programs Team.
New User Training for Family Providers TCP Policy and Programs Team.
HMIS Data Quality Training 211 Orange County. Learning Objective This training is scheduled for 2 hours. Objective 1.Teach users how to find deficiencies.
2014 HMIS Data Standards Overview HMIS Data Standards Background – Key resources – Implementation Timeline – Revision Process Overview of Key.
Jill Shoemaker Michigan Coalition Against Homelessness.
New User Training for DHS Staff TCP Policy and Programs Team.
New User Training for Singles Providers TCP Policy and Programs Team.
Managing the Non-WISP Prioritization List Carrie Poser, COC Coordinator April 27, 2016.
2014 HMIS Data Standards Collection Points With Richard Madigan Michigan Coalition Against Homelessness MSHMIS System Administrator II
Adding Household Members to an Entry/Exit This tutorial is meant to explain in detail the steps to include a household member (existing or creating) to.
PIT/HIC Data Entry and Reporting
OR: How I learned to stop worrying and love the database
KYHMIS BOS Quarterly Meeting
Welcome to the Webinar Once you join the webinar you will need select the phone symbol on the top left hand corner of the screen to connect the audio Select.
2017 Data Standards Updates & Caseworthy 7.2
Reviewing VaCMS For VIEW worker
HMIS Data Standards 2017 Changes
KYHMIS BOS 2017 Data Standards Updates
HMIS Version 6.2 Upgrade September 2016 Provided by: P W
New User Training for Family Providers
MDHI and BOS User Group August HMIS User Group MDHI and BOS User Group
HMIS Updates New Data Quality Framework in HMIS
Minnesota’s Homeless Management Information System (HMIS)
Minnesota’s Homeless Management Information System (HMIS)
Bereavement Best Practice.
Homeless Alliance of WNY September 2017
Minnesota’s Homeless Management Information System (HMIS)
Minnesota’s Homeless Management Information System (HMIS)
PAST DUE: PATH & HMIS Integration
New User Training for Family Providers
Featuring: Kristen Rodgers, CommUnityCare Street Medicine Team
Minnesota’s Homeless Management Information System (HMIS)
Correcting Snapshots and Recording Annual Assessments in HMIS
Featuring: Whitney Bright, Goodwill Central Texas
September 15, 2008 Resource Coordinator Training
Community Processing Free Categorical Applications
Community Focusing on Income Free and Reduced Applications
Magellan CANS Application for WY CME: Training and Certification Entering the CANS Updated July 2018.
Let’s get people some bus passes!
KC METRO HMIS Training SSVF, RRH, HP.
The SMI Evaluation and Determination Process
KC METRO HMIS Training PATH.
Pantry System Overview
ClientPoint Data Entry Workflow
Louisiana Ryan White Part B & HOPWA Data Management Update 2018
KC METRO HMIS Training PSH and TLP.
Featuring: Whitney Bright, Goodwill Central Texas
Welcome Effective May 13, 2019 the following services will require an authorization through the KEPRO Atrezzo Portal: Code Modifier Description T1017 HF.
KC METRO HMIS Training Emergency Shelter.
ClientPoint Data Entry Workflow
2019 Data Standards September 4, Data Standards September 4, 2019.
HMIS Support.
Presentation transcript:

PATH “Projects for Assistance in Transition from Homelessness” Workflow June,

Agenda Review of Definitions and Key Workflow Components Data Entry Workflow Preview of Services and Referrals 2

Two Program Types Street Outreach and Services Only! Which Program do I enter my Data Into? If place not meant for habitation - would go under Street Outreach. If ES, doubled up, or at risk of becoming homeless, etc. would be Services Only. 3

Two Program Types Extremely Important !!! You MUST Enter Data As “EDA” into the Proper program that the client is being entered into. 4

How to think about PATH Entry, Engagement, Enrollment and Exit in the HMIS Work begins with client on first Date of Contact. First Contact is recorded in the Entry Assessment Client is engaged in PATH when they agree to services. A Date of Engagement is recorded in an Interim Review. An Exit from PATH should be recorded when the client leaves or completes the program. Entry into PATH Additional Points of Contact Recorded Date of Engagement Recorded Exit from PATH Additional client contacts are made and recorded in Interim Reviews. Client is Enrolled when they have been determined to be PATH eligible. Date of Enrollment Recorded PATH Funded Services and Referrals Provided 5

Data Collection Stages Collection Phase: Outreach – Contacts Date Location – Minimum data that provider can identify client with 6

Data Collection Stages Collection Phase: Engagement/Enrollment – Housing Status – Name – SSN – Veteran Status – Date of Birth – Date of Engagement – Mental Health Problem – Substance Abuse – Maximum UDEs where possible – Referrals/Services 7

Data Collection Stages Collection Phase: Engagement/Enrollment – PATH Status/Enrollment – Full UDEs – PATH Specific Data Income and Sources Non-Cash Benefits Health Insurance Disabilities – Referrals/Services 8

Data Collection Stages Data Collection Phase: Exit – Reason for Leaving – Destination – Housing Status – Income and Sources – Non-Cash Benefits – Health Insurance – Disabilities – Connection with SOAR 9

Contact – Definition & Data Entry Process  Contacts: A contact is defined as an interaction between a worker and a client designed to engage the client. Contacts may include activities such as a conversation between the street outreach worker and the client about the client’s well-being or needs, an office visit to discuss their housing plan, or a referral to another community service.  A contact must be recorded using the outreach subassessment anytime a client is met, including when an engagement date or project entry date is recorded on the same day.  Record Date of Contact, Location.  The date of the first Contact is the same as the Entry date 10

Contact – Definition & Data Entry Process If the client was contacted on the date of engagement, a contact must also be entered for that date using the Outreach subassessment. – If the client was contacted on the date that PATH Status was determined (enrolled or not enrolled), a contact must also be entered for that date using the Outreach subassessment. 11

Engagement – Definition & Data Entry Process An Engagement Date is the date on which an interactive client relationship results in a deliberate client assessment or beginning of a case plan. The date of engagement should be entered into HMIS at the point that the client has been engaged by the outreach worker. This date may be on or after the project entry date and must be prior to project exit. If the client exits without becoming engaged, the engagement date should be left blank. If the client was contacted on the date of engagement, a contact must also be entered for that date. 12

Enrollment A PATH Enrollment occurs at the point when a client has been determined PATH eligible and has formally consented to participate in services provided by the PATH project. The date of enrollment may be on or after the project Entry date and on or after the Date of Engagement. A worker should enroll a client in PATH if the following has occurred: – The worker determined the client to be PATH eligible (homeless or at immanent risk of homelessness and seriously mentally ill (SMI)). – The worker recorded at least one contact with the client which could be the contact at project Entry – The worker has established a Date of Engagement with the client which is on or after the date of project Entry. – The worker has determined eligibility and the client has agreed to PATH enrollment. 13

Enrollment & Date of PATH Status Determination If the client has been determined eligible and consented to participate in services provided by the PATH project, then the ‘Client Became Enrolled in PATH’ data element is answered yes, and the appropriate Enrollment Date should be recorded. – If the client was contacted on the date that PATH Status was determined, a contact must also be entered for that date. If a client is not enrolled in PATH, then the ‘Client Became in Enrolled in PATH’ data element is answered no, and the date of the non-enrollment and reason should be recorded in the corresponding fields. An exit from the program should then be added for that same date. 14

HMIS Workflow Review Note: Anytime the Term “New Contact” is mentioned, It is referring to clicking the ADD button on the Outreach Sub Assessment either on Entry or Interim Assessment. 15

Add Entry Exit - Review 16 Entry / Exits are the core of ServicePoint. The Program, Entry Date and Exit Date define the clients relationship to programs, services, and all the other actions which ServicePoint lets us record. Until the client has the dates of Entry / Exits recorded you can consider the Client “On Hold”. Just waiting to be connected but not there yet. For PATH, the entry date will be the date you first have contact with a client. Exit dates are added when the client is no longer in the program.

Enter a client into a program Choose household members Choose the Type (PATH), confirm The Entry Date is correct, and then Press Save and Continue If entering as part of a household check household members 17

Recording Outreach Contacts 18 Start Date, End Date and Date of contact will be the Same date. The First contact will equal the client entry date! Must Click ADD to ADD your first Outreach Contact Add date and time of contact Add location (Place not meant for habitation, residential service setting, non-residential service setting

Recording Outreach Contacts 19 Date of Engagement, Enrolled in PATH and Date can be added at entry. IF NOT, They Must be updated through the Interim Assessment on the Entry Exit Tab.

Add Interim Review 20

Add Interim Review 21

Add Interim Review Type = Update Review Date = Date of Outreach 22

Add Interim Review Click ADD to create a new contact date, When appropriate, update the date of engagement, and Client became enrolled Y/N and the qualifying date. If No to became enrolled, you must add a reason. This is the new contact that was add through interim assessment 23

Using Interim Reviews to Add new Contact, Engagement Date and PATH Status Information Interim Reviews should also be used to add an Engagement Date and PATH Status Determination information (regardless of enrollment or non-enrollment). Interim Review type should = update and Review Date should correspond to Engagement Date or PATH Status Determination Date 24

Interim Reviews Interim Reviews should continue to be used to add a new contact or record any updates to a client record, such as changes to income, benefits, insurance, and disability information. 25

Recording Services - Review 26

Recording Services - Review 27

Recording Services Prior to Enrollment (non PATH Funded) Do Not add Path Funded Service type for Services prior to Path Enrollment 28

Adding Services After Enrollment (PATH Funded) After the client has been Enrolled, you NEED to Select Both Service Type and Path Funded Service Provided for Path Service to be reported. 29

Adding Services After Enrollment (PATH Funded) 30

Creating Referrals - Review PATH reporting requires that clients receiving assisted referrals be enrolled in PATH (4.16 A Referrals Provided – PATH). 31

Creating Referrals - Review 32

Creating Referrals - Review 33

Creating Referrals - Review Be sure to check the box indicating the Referral Type 34

Exiting Clients from PATH in HMIS Clients who are no longer receiving PATH services or outreach should be exited in the system (60 days without service or contact would apply here) If a client is not enrolled for any reason, once PATH Status Determination information is recorded, an exit from the program should be added to the client record 35

Resources HMIS Help Desk: HUD Exchange: HMIS Data Standards: PATH Program HMIS Manual: program-hmis-manual/ program-hmis-manual/ 36