Measure 2a and 2b: The Extent to which Persons Who Exit Homelessness to Permanent Housing Destinations Return to Homelessness within 6, 12, and 24 months
Program-wideoutcomeFY2026
Tier 3: Needs a partner
The outcome sits in a record another agency holds.
No cleared, validated, free outcome instrument exists for housing stability. The funder's own item (SAMHSA SUPRT-C client form, item A2d), an HMIS exit destination, or a partner record is the substitute. Source
Partner routes for another agency’s HMIS
- IL: housing exits, destinations and returns recorded in HMIS Held by Chicago CoC HMIS; All Chicago is the HMIS lead.
- Rule
- Local HMIS request approval and a fully executed DSA required for research or evaluation, subject to HUD HMIS standards and authorized uses. The published terms also specify destruction and breach-notification obligations.
- Lag
- Event lag and fulfillment SLA NR; requests are prioritized.
- Cost
- Some custom requests incur $150 per hour, quoted before work.
- Who may request
- Requesting entities approved by the HMIS lead for an authorized purpose; project participation alone does not confer unrestricted research access.
- Request
- Data request.
- UT: housing move-in, exits, destinations and longitudinal service records Held by Utah HMIS and participating contributing organizations.
- Rule
- UHMIS privacy and security rules, contributing-organization agreement, applicable client consent; a published cross-agency MOU can authorize partner access beyond standard sharing.
- Lag
- Event lag NR; depends on provider entry and reporting.
- Cost
- NR.
- Who may request
- Approved participating organizations; additional partner access must be specifically authorized.
Caveats
- HMIS exit data has an observation boundary. HMIS measures have an observation boundary. Exit destination and later recorded returns can support housing measures; absence of a recorded return alone does not establish continuous housing stability. This is a measurement inference, not an additional access right. Source
Agreement templates
- Utah HMIS cross-agency MOU A model for primary and partner contributing organizations to authorize program access, data entry and reporting beyond ordinary sharing settings. Also listed on the official Utah HMIS forms page.
- Riverside County CoC HMIS inter-agency data sharing agreement A CoC inter-agency HMIS data sharing agreement (Appendix G of the county's HMIS policies).
This measure begins with clients who exited to a permanent housing destination in the date range two years prior to the report date range. Of those clients, the measure reports on how many of them returned to homelessness as indicated in HMIS for up to two years after their initial exit.
- Instrument
- System Performance Measures HMIS Programming Specifications V1.0 (HMIS Data Standards FY2026)
- Target
- No target rule stated