Housing & Homelessness HMIS Wrapper

Principal workflows

• Consent: Each client's consent to share is recorded once, by the agency that serves them, with exactly which partners and which kinds of information it covers and when it ends.
• Share: Partners see a shared client view that contains only what the client's consent and the data sharing agreements allow, drawn from the HMIS and partner systems.
• Refer: Outreach teams, 311, health partners and police can refer a person to outreach or a service. Referrers see whether the referral was taken up, not the client's record.
• Coordinate: Case conferencing and coordinated entry teams work from a shared list of consenting clients, track housing matches and record the actions each agency has agreed to take.

Who uses it

• HMIS leads and Continuum of Care staff
• Shelter, outreach and housing program staff at partner agencies
• Coordinated entry teams who assess and prioritize clients for housing
• City and county human services, health and public safety departments
• Privacy officers who answer for how client data is shared

Reporting

• Referral status and response by source and area
• Case conference actions and follow-through
• Housing match pipeline and decline reasons
• Consent coverage and consents ending soon
• Access accounting for any client
• HMIS synchronization and data quality

Features

• Granular consent: Consent recorded by partner and by information category, with start and end dates, revocation and a history of every change.
• Sharing rules engine: Data sharing agreements turned into rules that decide what each partner can see, applied every time a record is opened.
• Shared client view: One view of the client across partners, showing only the information each viewer is entitled to see.
• Restricted categories: Health, behavioral health, substance use and justice information kept in separate categories that need their own specific consent.
• Outreach referrals: A referral form for partners, 311 and public safety, routed by area to the right outreach team, with status shown to the referrer.
• Public safety boundary: Police and crisis responders can refer and see referral status, but cannot search or view client records.
• By-name list: A shared list of consenting clients for case conferencing, with housing status, assessments and agreed actions.
• Case conferencing: Agendas, attendance, decisions and actions recorded for each case conference, with follow-up tracked to completion.
• Housing match tracking: Coordinated entry matches to housing openings tracked from referral to move-in or decline, with reasons.
• HMIS synchronization: Client, enrollment and service data read from the HMIS using HUD data standard elements, and outcomes written back where supported.
• Privacy request handling: Client requests to see, correct or restrict their information recorded and tracked to a response.
• Access accounting: A record of every view and share of each client's information, available to the privacy officer and, on request, the client.

Integrations

• HMIS: Client, enrollment, service and assessment data read from your HMIS through its API or HMIS CSV exports, using HUD data standard elements.
• Coordinated entry: Assessments and prioritization data from the coordinated entry process, whether it runs in the HMIS or a separate tool.
• 311 and 211: Requests about people who may need help can be passed to outreach as referrals, including from Moraph's 311 Omni-Channel Citizen Intake.
• Public safety referral intake: Police, fire and EMS submit referrals through a web form or a feed from their own systems, under the data sharing agreement with their department.
• Health partners: Clinics and health systems can share care coordination information where clients consent, under a business associate agreement where PHI is involved.
• Housing inventory: Openings in permanent supportive housing, rapid rehousing and other programs from your inventory or the HMIS.
• Single sign-on: Staff sign in through the HMIS lead's identity provider or their agency's own (SAML or OpenID Connect).
• Work API: Aggregate and de-identified referral and coordination data available to your data warehouse through the Moraph Work API.

Deployment

• Moraph cloud: Hosted and operated by Moraph in the United States region, the only region used for government data.
• Dedicated environment: A single-tenant environment for Continuums of Care or counties whose policies require isolation, scoped in the proposal.
• With a managed service: Optionally run alongside a Moraph managed service for partner onboarding, sharing rule changes and support.

Security and privacy

• Single sign-on: Staff sign in through your identity provider, so your password and multi-factor policies apply.
• Consent-based access: Each record view is checked against the client's consent and the sharing rules at the moment it is opened.
• Encryption and keys: Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.
• Complete audit trail: Every view, share, referral and consent change is logged with the person, agency and time, and cannot be edited.
• US hosting: Government and client data is hosted in the United States region only.
• Business associate agreement: Where health information covered by HIPAA is involved, Moraph signs a business associate agreement.

Limitations

• It is not an HMIS. Your HMIS remains the system of record, and HUD-required reports continue to be produced from it.
• Sharing follows the consent and agreements you configure; your Continuum of Care, its privacy officer and counsel decide what may be shared and with whom.
• Victim service providers do not enter client data into HMIS, and their clients' information is not shared through the Wrapper.
• Public safety partners can refer and see referral status but cannot see client records; it is not a tool for enforcement or locating individuals.
• Synchronization with the HMIS depends on what your HMIS vendor's API or exports support, and writing outcomes back is not available with every HMIS.
• It does not manage housing subsidies or payments to landlords. Moraph does not hold funds.
• Health information is shared only where a client consents and the participating organizations' agreements, including any business associate agreement, are in place.
• Coordinated entry prioritization policy is set by your Continuum of Care; the Wrapper applies and records it but does not decide it.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/housing-and-homelessness-hmis-wrapper. Purchasing routes and company information: www.moraph.com/how-to-buy.