Data Elements: P3 PATH Status

Data Element

The HMIS (Homeless Management Information System) data element P3 PATH Status is used to determine whether a client is eligible for the PATH program. Clients that reach enrollment should have one of the following PATH Status options recorded:

  • Client became enrolled in PATH –

An enrollment date is collected to identify the date when a PATH eligible individual and a PATH provider have mutually and formally agreed to engage in services and the provider has initiated an individual file or record for that individual. The date of PATH enrollment should be entered into the HMIS at the point that the client has become enrolled. It may be on or after the Project Start Date (data element 3.10) or Date of Engagement (data element 4.13) and prior to Project Exit Date (data element 3.11).

  • Client was found ineligible for PATH or client was not enrolled for other reason(s)

If the client exits the project without being enrolled, the PATH Status element still needs to be completed, indicating that the client was not enrolled and the reason the client was not enrolled. If the client was contacted on the date that PATH Status was determined, a contact, recorded as a Current Living Situation (data element 4.12) must also be entered for that date.

  

  • Unable to locate client

This is used to account for clients not enrolled in the PATH program because they cannot be found.

    

Data Element Type

P3 PATH Status is a Program Specific Data Element and is collected for Head of Household and adults enrolled in PATH Street Outreach and Services Only projects.

Collection Point

Occurrence Point  - At Determination; collect once, at or before exit, when the status is determined.

Why It Matters

P3 PATH Status is used to determine whether a client is eligible for the PATH program.

Data Quality

How to correct: Enter value, if known on Project Entry or Interim Assessment.

 

* 2024 HUD Data Standards

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.