Metrics 6a.1 and 6b.1 – Returns to ES, SH, TH, and PH projects after exits to permanent housing destinations within 6 and 12 months (and 24 months in a separate calculation)
Program-wideoutcomeFY20266a.1 and 6b.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).
Metrics 6a.1 and 6b.1 mirror Measure 2 but with a universe of Category 3 persons. Metric 6c.1 mirrors Measure 7b.1 but with a universe of Category 3 SH, TH, PH – RRH, and PH (without a housing move-in date as defined by the Handling Housing Move-In Dates section of the HMIS Standard Reporting Terminology Glossary) system leavers in the current reporting year. Metric 6c.2 mirrors Measure 7b.2 but with a universe of Category 3 PH-PSH system stayers and leavers in the current reporting year, with a housing move-in date as defined by the Handling Housing Move-In Dates section of the HMIS Standard Reporting Terminology Glossary.
- Instrument
- System Performance Measures HMIS Programming Specifications V1.0 (HMIS Data Standards FY2026)
- Target
- No target rule stated