State & local government · Moraph software

Housing & Homelessness HMIS Wrapper

Coordinate care across shelters, services and outreach without giving up client privacy

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

The Housing & Homelessness HMIS Wrapper sits alongside your Continuum of Care's Homeless Management Information System and lets partner agencies coordinate around each client under the consent the client has given. Shelters, outreach teams, health and social service partners share what each client has agreed to share, and public safety partners can refer people to outreach without seeing their records. Every share, view and referral is recorded, so the HMIS lead can show that data moved only as clients and agreements allowed.

The problem it solves

People experiencing homelessness are served by many organizations at once: shelters, street outreach, health clinics, social services and, often, police or crisis responders. Each holds part of the picture, and the HMIS is not set up for fine-grained, consent-based sharing with partners outside it. So information is passed by phone and email with no record of what was shared or why, police calls about people in crisis do not reach outreach teams, and agencies hesitate to share at all for fear of breaching privacy rules.

  • Client consent is recorded on paper or not at all, and is hard to check before sharing
  • Partners outside the HMIS coordinate by phone and email with no record
  • Public safety contacts with unhoused people rarely become referrals to outreach
  • Agencies cannot show who saw a client's information or why

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

Requirements it supports

HUD HMIS Data Standards (HMIS Data Dictionary and HMIS Data Manual)HMIS Data and Technical Standards Final Notice (2004), including privacy and security standardsContinuum of Care Program interim rule (24 CFR Part 578)Violence Against Women Act confidentiality provisions for victim service providersHIPAA Privacy and Security Rules (45 CFR Parts 160 and 164), where covered entities participateConfidentiality of Substance Use Disorder Patient Records (42 CFR Part 2)

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    Recording consent

    The case manager records exactly what the client agreed to share, with whom, and until when.

    Client 40271 · Consent to share

    Recorded by
    Example Shelter (fictional)
    Method
    Signed form, uploaded
    Partners
    Outreach, coordinated entry, Example Health Clinic (fictional)
    Basic and housing information
    Shared
    Health information
    Shared with Example Health Clinic only
    Substance use information
    Not shared
    Ends
    Sample end date

    Client choices

    • No information to public safety partners
    • Referral status may be shown to referrers
    • Client informed of right to revoke
    The case manager records exactly what the client agreed to share, with whom, and until when.

  2. Step 2

    The shared client view

    A partner sees only the categories the client agreed to share with that partner; the rest is marked as not shared.

    Client 40271 · Viewed by coordinated entry

    Current program
    Emergency shelter
    Assessment
    Completed, sample date
    Housing status
    On by-name list
    Health information
    Not shared with this partner
    Agencies involved
    3

    Shared notes

    • Prefers contact at shelter in the morning
    • Has identification documents on file
    • Interested in rapid rehousing
    A partner sees only the categories the client agreed to share with that partner; the rest is marked as not shared.

  3. Step 3

    Outreach referrals

    Referrals from 311, partners and public safety arrive in one queue, routed by area to the right outreach team.

    ReferralSourceAreaNeedAgeStatus
    RF-8812Police liaisonExample District 2Person in distress, cold weather3 hoursNew
    RF-8807311Example District 4Encampment welfare check1 dayContact attempted
    RF-8799Health partnerExample District 1Discharge without housing1 dayEngaged
    RF-8790ShelterExample District 2Needs documents for housing2 daysAccepted
    Referrals from 311, partners and public safety arrive in one queue, routed by area to the right outreach team.

  4. Step 4

    What the referrer sees

    A police liaison sees the progress of their own referral, not the person's record.

    Referral RF-8812 · Submitted by police liaison

    1. Referral submitted with location and observed needsPolice liaison
    2. Routed to Outreach Team EastSystem
    3. AcceptedOutreach worker
    4. Contact made; person engaged with outreachOutreach worker
    5. Referral closed; no further detail shared under client's consentSystem
    A police liaison sees the progress of their own referral, not the person's record.

  5. Step 5

    Case conferencing

    Coordinated entry staff work from the by-name list of consenting clients and record the actions each agency agrees to.

    ClientAssessmentProgram interestAgreed actionOwnerDue
    Client 40271CompletedRapid rehousingGather income documentsExample ShelterSample date
    Client 38810CompletedSupportive housingSchedule unit viewingExample Housing AgencyOverdue
    Client 41502DueNot yet knownComplete assessmentOutreach Team EastSample date
    Coordinated entry staff work from the by-name list of consenting clients and record the actions each agency agrees to.

  6. Step 6

    Access accounting

    The privacy officer can show exactly who saw a client's information and why.

    DateUserAgencyActionPurposeConsent basis
    Sample dateCase manager 12Example ShelterViewed recordCase managementOwn agency
    Sample dateCE specialist 3Coordinated entryViewed recordPrioritizationConsent CN-40271
    Sample dateNurse 7Example Health ClinicViewed health notesCare coordinationConsent CN-40271
    Sample dateOutreach worker 5Outreach Team EastAttempted view, deniedNot statedNo consent
    The privacy officer can show exactly who saw a client's information and why.

Workflows

The principal workflows

  1. 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.

    • Case manager explains the sharing options in plain language
    • Client chooses which partners and information categories to share with
    • Signed or verbal consent recorded with the date and an end date
    • Consent linked to the client's HMIS record
    • Client can revoke or change consent at any time, and the change applies to future sharing

  2. 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.

    • Client data read from the HMIS on a schedule or by API
    • Sharing rules from the agreements and the client's consent applied
    • Each partner sees the categories it is entitled to and no more
    • Restricted information such as health or substance use records shown only where specific consent exists
    • Every view is logged with the person, partner and purpose

  3. 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.

    • Referral submitted with location, needs and any safety notes
    • Referral routed to the outreach team or agency responsible for that area
    • Outreach worker accepts, attempts contact and records the outcome
    • Referrer sees the referral status at the level the client's consent allows
    • Unanswered referrals escalated to the coordinating agency

  4. 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.

    • By-name list built from consenting clients and the HMIS
    • Case conference agenda prepared from the list
    • Actions assigned to agencies with due dates
    • Housing matches and their outcomes recorded
    • Outcomes written back to the HMIS where your HMIS supports it

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Case manager

Case manager, outreach worker, shelter intake worker, housing navigator

Works directly with clients: records their consent, coordinates services with partners and follows up referrals.

Sees

  • Their own agency's clients, as recorded in the HMIS
  • Information shared by other partners under the client's consent
  • Referrals routed to their team
  • Case conference actions assigned to their agency

Does

  • Records, changes and revokes client consent
  • Accepts referrals, records contact attempts and outcomes
  • Shares information with partners within the client's consent
  • Adds notes for partners the client has agreed to share with
  • Completes case conference actions

Cannot

  • See clients who have not consented to share with their agency
  • See restricted categories without the client's specific consent
  • Change sharing rules or data sharing agreements
Approvals
Nothing they do needs approval, but every view and share is recorded and reviewable by the privacy officer.
Notified about
Referrals routed to their team, consents nearing their end date, and case conference actions due.

Coordinated entry staff

Coordinated entry specialist, assessor, housing matcher

Assesses and prioritizes clients for housing under the Continuum of Care's written standards, and tracks matches to openings.

Sees

  • The by-name list of consenting clients with assessment results
  • Housing openings and match history
  • Shared information needed for prioritization, within consent

Does

  • Records or imports coordinated entry assessments
  • Prepares case conference agendas from the by-name list
  • Proposes housing matches and records their outcomes
  • Assigns case conference actions to agencies

Cannot

  • Change the prioritization policy set by the Continuum of Care
  • See restricted categories without specific consent
  • Manage users or sharing rules
Approvals
Matches follow the Continuum's written standards; overrides of the prioritization order are recorded with a reason and reviewed by the HMIS lead.
Notified about
New openings, matches declined or stalled, and clients newly added to the list.

Partner agency lead

Program director, shelter manager, agency HMIS administrator

Answers for their agency's use of shared information and makes sure referrals and actions are worked.

Sees

  • Their agency's clients, referrals and actions
  • Their staff's access and activity
  • Consent coverage for their agency's clients

Does

  • Requests user accounts for their staff
  • Reassigns referrals and actions within the agency
  • Reviews their staff's access each period
  • Signs the agency's participation in data sharing agreements

Cannot

  • See other agencies' clients beyond what consent allows
  • Grant access directly; accounts are created by the HMIS lead
  • Change sharing rules
Approvals
Staff accounts they request are created by the HMIS lead administrator.
Notified about
Referrals unanswered by their team, access reviews due and staff accounts not used for a period your policy sets.

Public safety liaison

Police homeless liaison officer, crisis intervention team member, fire or EMS community paramedic

Connects people they meet to outreach, rather than to enforcement, without needing access to service records.

Sees

  • Referrals they have submitted
  • The status of each referral: received, contact attempted, engaged
  • Further detail only where the client has specifically consented

Does

  • Submits referrals with location, observed needs and safety notes
  • Adds information to an open referral
  • Withdraws a referral submitted in error

Cannot

  • Search for or open client records
  • See health, substance use, shelter location or service history
  • Export data
Approvals
Their access level is set by the data sharing agreement with their department and approved by the privacy officer.
Notified about
Status changes on referrals they submitted.

HMIS lead administrator

HMIS lead, HMIS system administrator, Continuum of Care data manager

Runs the shared environment: partners, users, sharing rules, the HMIS connection and data quality.

Sees

  • All partners, users and their roles
  • Sharing rules, agreements and their versions
  • HMIS synchronization status and data quality results
  • The audit trail

Does

  • Onboards partner agencies and creates user accounts
  • Configures sharing rules from approved agreements
  • Monitors the HMIS connection and resolves data issues
  • Reviews prioritization overrides
  • Runs access reviews

Cannot

  • Put a sharing rule into effect without the privacy officer's approval
  • Edit or delete audit trail entries
  • Grant public safety partners access to client records
Approvals
Sharing rule changes and new partner types are approved by the privacy officer.
Notified about
Synchronization failures, data quality issues, access requests and access reviews due.

Privacy officer

Privacy officer, compliance officer, Continuum of Care privacy lead

Makes sure information moves only as clients and agreements allow, and answers clients' privacy requests.

Sees

  • Sharing rules and data sharing agreements
  • Access accounting for any client
  • Privacy requests and their status
  • The audit trail

Does

  • Approves or returns sharing rule changes
  • Reviews unusual access, such as many records viewed by one user
  • Responds to client requests to see, correct or restrict their information
  • Investigates and records suspected privacy incidents

Cannot

  • Change client consent on a client's behalf without a recorded request
  • Edit or delete audit trail entries
  • Approve a sharing rule they drafted themselves
Approvals
Approves sharing rules, public safety access levels and responses to privacy requests.
Notified about
Sharing rules awaiting approval, privacy requests received, and access patterns flagged for review.

Data and reporting analyst

Continuum of Care data analyst, county human services analyst

Reports on coordination, referrals and housing outcomes using de-identified or aggregate data.

Sees

  • Aggregate and de-identified reporting data
  • Referral, match and case conference metrics
  • Data quality results

Does

  • Runs and schedules reports
  • Builds dashboards for funders and leadership
  • Reviews data quality with partner agencies

Cannot

  • See identified client records
  • Change sharing rules or user access
  • Export identified data
Approvals
Access to any identified data for a specific project is approved by the privacy officer, with a scope and end date.
Notified about
Scheduled reports ready and data quality issues on their reports.

Permissions at a glance

ActionCase managerCE staffAgency leadPS liaisonHMIS leadPrivacyAnalyst
Record or revoke client consentOwn work onlyNo accessOwn work onlyNo accessNo accessView onlyNo access
View shared client recordsOwn work onlyOwn work onlyOwn work onlyNo accessView onlyView onlyNo access
View restricted categoriesOwn work onlyNo accessNo accessNo accessNo accessView onlyNo access
Share information with a partnerOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo accessNo access
Submit a referralFullFullFullOwn work onlyNo accessNo accessNo access
Accept and work referralsOwn work onlyNo accessOwn work onlyNo accessNo accessNo accessNo access
Manage by-name list and housing matchesView onlyFullView onlyNo accessApprovesNo accessNo access
Change sharing rulesNo accessNo accessNo accessNo accessFullApprovesNo access
Respond to privacy requestsNo accessNo accessNo accessNo accessView onlyFullNo access
Run aggregate reportsNo accessOwn work onlyOwn work onlyNo accessFullFullFull
View audit trail and access accountingNo accessNo accessOwn work onlyNo accessView onlyView onlyNo access
Manage users and rolesNo accessNo accessNo accessNo accessFullApprovesNo access
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Consent decides access: no role, including the HMIS lead, sees a client's shared record at a partner unless the client's consent and the agreements allow it, and restricted categories need their own specific consent.
  • Public safety partners are limited by design. They can refer people to outreach and follow the status of their own referrals, but they cannot search, open or export client records.
  • Roles are configured with you during implementation and can be limited by agency, program and area. Every permission change is recorded, and access review reports list each person's roles for periodic review.
  • Staff sign in through the identity provider your HMIS lead designates, and partner agencies' users can be federated from their own identity providers where agreements allow.

Features

What it does

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

How it connects to your systems

Connects toHowWhat flows
HMISClient, enrollment, service and assessment data read from your HMIS through its API or HMIS CSV exports, using HUD data standard elements.In: clients, enrollments, services, assessments. Out: referral and match outcomes, where your HMIS accepts them.
Coordinated entryAssessments and prioritization data from the coordinated entry process, whether it runs in the HMIS or a separate tool.In: assessments and prioritization scores. Out: match outcomes.
311 and 211Requests about people who may need help can be passed to outreach as referrals, including from Moraph's 311 Omni-Channel Citizen Intake.In: referral location, description and request number. Out: referral status.
Public safety referral intakePolice, fire and EMS submit referrals through a web form or a feed from their own systems, under the data sharing agreement with their department.In: referrals. Out: referral status only.
Health partnersClinics and health systems can share care coordination information where clients consent, under a business associate agreement where PHI is involved.In and out: care coordination notes within the client's consent.
Housing inventoryOpenings in permanent supportive housing, rapid rehousing and other programs from your inventory or the HMIS.In: openings and eligibility rules.
Single sign-onStaff sign in through the HMIS lead's identity provider or their agency's own (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APIAggregate and de-identified referral and coordination data available to your data warehouse through the Moraph Work API.Out: referrals, matches, case conference actions and status.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

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.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Coordination

Referral status

For outreach leads and the HMIS lead

Referrals received, accepted, contacted and engaged, with the time each spent waiting.

Break down by
Referral source, Area, Outreach team, Status
Delivered as
Live dashboard; CSV export
Used for
Making sure referrals are answered and spotting areas without enough outreach coverage.

Case conference actions

For coordinated entry staff and agency leads

Actions agreed at case conferences, who owns them, and whether they are done or overdue.

Break down by
Agency, Action type, Due date, Status
Delivered as
Live dashboard; scheduled email
Used for
Following through on what agencies agreed to do for each client.

Housing match pipeline

For coordinated entry staff and the Continuum of Care

Matches made, accepted, declined and moved in, with decline reasons and time at each stage.

Break down by
Program type, Provider, Stage, Decline reason
Delivered as
Live dashboard; CSV export
Used for
Finding where matches stall between referral and move-in.

Public safety referrals

For hMIS lead, public safety leadership and city leadership

Referrals made by police, fire and EMS and how many led to engagement with outreach, in aggregate.

Break down by
Department, Area, Period, Outcome
Delivered as
Live dashboard; PDF export
Used for
Showing whether public safety contacts are reaching services.

Privacy

Consent coverage

For agency leads, HMIS lead and privacy officer

Active clients with consent on file, by scope, and consents ending soon or revoked.

Break down by
Agency, Consent scope, End date window, Status
Delivered as
Live dashboard; scheduled email
Used for
Renewing consent before it lapses and seeing where clients choose not to share.

Access accounting

For privacy officer, and clients on request

Every view and share of a selected client's information: who, which agency, when and for what purpose.

Break down by
Client, Agency, User, Date range
Delivered as
On request in the product; PDF export
Used for
Answering a client's request to know who has seen their information, and investigating concerns.

Unusual access

For privacy officer

Access patterns flagged for review, such as many records opened by one user or views outside a user's usual area.

Break down by
User, Agency, Pattern, Review outcome
Delivered as
Live dashboard; scheduled email
Used for
Catching inappropriate access early and recording the review.

Privacy requests

For privacy officer

Client requests to see, correct or restrict their information, and the response to each.

Break down by
Request type, Agency, Status, Received date
Delivered as
Live view; CSV export
Used for
Tracking every request to a documented response.

Operations

HMIS synchronization and data quality

For hMIS lead

Synchronization runs, records that failed to load, and missing or inconsistent data elements by agency.

Break down by
Run date, Agency, Data element, Error type
Delivered as
Live dashboard; scheduled email
Used for
Keeping the shared view accurate and working data issues with agencies.

User access review

For agency leads, HMIS lead and privacy officer

Each user's agency, role and last sign-in, for periodic certification.

Break down by
Agency, Role, Last sign-in
Delivered as
Scheduled; CSV and PDF export
Used for
Removing access that is no longer needed.

Audit trail extract

For privacy officer and auditors

Who did what and when for a selected client, user, agency or period.

Break down by
Record, User, Action, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Answering audit, monitoring and incident questions with evidence.

Exports, access and evidence

  • Coordination and outcome reports use aggregate or de-identified data by default; identified data appears only in reports for roles entitled to see it.
  • Federally required HUD reports, such as the Annual Performance Report, Longitudinal Systems Analysis and System Performance Measures, continue to be produced from your HMIS.
  • Every report can be exported to CSV, and summary and evidence reports to PDF. Reports can be scheduled to arrive by email for the people entitled to see them.
  • Aggregate referral and coordination data is available through the Moraph Work API for your data warehouse or business intelligence tool.
  • Running and exporting a report is itself recorded in the audit trail, and small counts can be suppressed in published reports to protect individuals.

Deployment

Where and how it runs

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 controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Agreements and consent

We work with your HMIS lead, privacy officer and counsel to translate data sharing agreements and consent forms into categories and sharing rules. Your Continuum of Care approves them.

HMIS connection

We connect to your HMIS through its API or HMIS CSV exports and agree the schedule. We need a contact from your HMIS vendor or administrator.

Partner onboarding

Partner agencies are set up with their programs, users and areas, and sign participation in the agreements before their staff get access.

Referral routing

Outreach areas, teams and escalation paths are configured, and referral routes from 311, public safety and health partners are set up and tested.

Coordinated entry

The by-name list, case conferencing and match tracking are configured to your Continuum's written standards.

Training and go-live

Case managers are trained on explaining consent to clients, and each partner type on its own workflows. Partners can be brought on in phases.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • 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.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Take your current consent form and check that each choice on it can be recorded and enforced
  2. Open the same sample client as three different partners and compare what each sees
  3. Submit a referral as a public safety liaison and confirm what they can and cannot see
  4. Run a mock case conference from the by-name list
  5. Request an access accounting for a sample client
  6. Confirm with your HMIS vendor what the connection can read and write

Questions

Frequently asked questions

Does this replace our HMIS?

No. Your HMIS stays the system of record for HUD data and reporting. The Wrapper reads from it and adds consent-based sharing, referrals and coordination with partners.

Can police see client information?

Not by default. Public safety partners can submit referrals and see their status. Anything more is shown only where a client has specifically consented and your agreements allow it.

Which HMIS products does it work with?

It connects through an HMIS's API or the HUD HMIS CSV export format. What can be read and written back depends on your HMIS vendor, which we confirm during scoping.

Who owns the data?

Your Continuum of Care and its participating agencies do, under your agreements. How it is returned and deleted at the end of the contract is set out in the contract.

How is it priced?

As a subscription, usually measured by the number of participating agencies or users, with implementation charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate Housing & Homelessness HMIS Wrapper

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Housing & Homelessness HMIS Wrapper guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Housing & Homelessness HMIS Wrapper support guide.

Related products