Metric 7b.1 – Change in exits to permanent housing destinations
Program-wideoutcomeFY20267b.1
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 is divided in three tables: 1. Metric 7a.1 – Counts leavers who exited Street Outreach (SO) during the report date range and how many of those exited to an acceptable destination. 2. Metric 7b.1 – Counts leavers who exited ES-EE, ES-NbN, SH, TH, PH – RRH, and PH (for any non-RRH PH type, must be without moving into housing) during the report range and how many of those exited to permanent housing destinations. 3. Metric 7b.2 – Counts stayers and leavers with a housing move-in date (as defined by the Handling Housing Move-In Dates section of the HMIS Standard Reporting Terminology Glossary) in all PH projects except PH-RRH and how many of those were stayers or leavers who exited to permanent housing destinations.
- Instrument
- System Performance Measures HMIS Programming Specifications V1.0 (HMIS Data Standards FY2026)
- Target
- No target rule stated