Many housing–health partnerships start with goodwill and a handful of referrals—and then stall when teams realize there is no stable operating budget for integration work. PSH providers may be expected to “coordinate care” without funded clinical capacity, while health partners are asked to show outcomes without reliable housing-side workflows. The gap is not motivation; it is misalignment between payment, contracting, and what actually happens on the ground.
To protect tenancy sustainment and housing stabilization while advancing housing–health partnerships, commissioning and contracting need to specify who does what, what is paid for, how it is evidenced, and how performance is governed when risk escalates.
Where the money (and the confusion) usually sits
Integration work often lands in the “in-between” space: not traditional tenancy support, not billable clinical care, and not clearly owned by any single system actor. Common unfunded tasks include discharge follow-up, medication reconciliation coordination, transport problem-solving, appointment re-engagement, and multi-agency risk planning. When these tasks are not explicitly contracted, they become discretionary—dependent on personalities, short-term pilots, or crisis moments.
Contracting must treat integration as a defined service component with deliverables, quality controls, and performance expectations. Otherwise, the partnership will drift into either: (1) over-medicalizing housing staff, or (2) under-serving tenants with complex health needs.
Oversight expectations you must design for
Expectation 1: Clear scope and role boundaries. Payers, commissioners, and auditors expect to see that housing staff are not providing clinical care beyond competence, and that clinical partners are accountable for clinical decisions. If role boundaries are unclear, the model becomes both unsafe and indefensible when something goes wrong.
Expectation 2: Measurable deliverables and an auditable trail. Whether funding flows via Medicaid managed care, health homes, or other vehicles, oversight bodies increasingly expect operational evidence: timeliness of follow-up, completion of care coordination activities, and documented escalation decisions. “We met and discussed” is not a deliverable; a documented action pathway is.
Designing a contractable “integration scope” for PSH
A practical approach is to define integration as a package of work that is distinct from core tenancy support and distinct from clinical treatment. The scope should specify:
- Eligibility and targeting (e.g., high-acuity tenants, frequent ED users, recent discharges)
- Service activities (care plan coordination, discharge follow-up, appointment re-engagement, barriers removal)
- Response times (e.g., post-discharge contact within 72 hours)
- Escalation responsibilities (who triggers mobile crisis, who contacts primary care)
- Documentation standards (what is recorded, where, and how it is shared)
- Quality checks (case review cadence, supervisory sign-off for high-risk decisions)
This turns integration into something funders can pay for and providers can staff reliably.
Operational example 1: A deliverables-based agreement for post-discharge stabilization
What happens in day-to-day delivery. The PSH provider and health partner contract for a defined “post-discharge stabilization” pathway. When a tenant is discharged, a trigger arrives via a hospital liaison or health plan notification. The housing team completes a home visit focused on immediate stability (food, utilities, safety hazards, ability to manage the unit). A clinical partner completes medication reconciliation and confirms follow-up appointments. The contract defines response times, minimum contact attempts, and required documentation fields (date/time, outcome, next steps). A weekly roster review checks that every discharge has a completed pathway or a documented reason it could not be completed.
Why the practice exists (failure mode it addresses). The discharge window is a predictable failure point: instructions are missed, meds are inconsistent, and tenants can decompensate quickly. Without a funded, contractable pathway, teams treat discharge work as “extra,” leading to gaps and preventable readmissions that destabilize housing.
What goes wrong if it is absent. Tenants return home without support, prescriptions are not filled, symptoms escalate, and housing staff experience a sudden “behavioral crisis” that is often medically driven. Providers then scramble reactively, often through emergency services, which damages trust and increases system costs.
What observable outcome it produces. Completed discharge pathways can be audited; follow-up timeliness improves; medication issues are identified earlier; and avoidable ED returns reduce—while tenancy disruptions linked to health events become less frequent.
Operational example 2: A care coordination rate tied to specific workflow outputs (not vague “engagement”)
What happens in day-to-day delivery. The health plan (or system commissioner) funds a per-member-per-month care coordination rate for eligible tenants. Payment is tied to defined outputs: a shared care plan updated at set intervals, documented appointment scheduling and attendance support, and a minimum number of proactive check-ins during high-risk periods. The PSH provider uses a standard template for care plan updates, records contact attempts, and logs barrier resolution activities (transport arranged, benefits reinstated, primary care re-established). Monthly, a sample of cases is reviewed jointly to confirm outputs and resolve any documentation drift.
Why the practice exists (failure mode it addresses). Many contracts pay for “coordination” without specifying the operational work, encouraging shallow documentation and inconsistent practice. A workflow-output model funds the real tasks that prevent deterioration and housing instability.
What goes wrong if it is absent. Coordination becomes a narrative note with little accountability. Staff spend time chasing information without clarity on what counts as completion. Health partners see inconsistent engagement, and the housing provider cannot justify staffing levels when budgets tighten.
What observable outcome it produces. More consistent coordination activity, clearer accountability for completion, stronger audit readiness, and improved continuity indicators (primary care connection, fewer missed follow-ups, fewer crisis-triggered contacts).
Operational example 3: Joint quality governance built into the contract (not bolted on later)
What happens in day-to-day delivery. The contract includes a joint governance structure: named leads, monthly quality meetings, and an escalation route for safety concerns. The group reviews a small set of defined metrics (timeliness of post-discharge follow-up, completion of care plan updates, crisis escalation pathways used, and repeat ED utilization). They also review “near misses” and high-risk incidents to improve processes rather than allocate blame. Action logs are kept, owners are assigned, and changes are tested and embedded into workflow training for staff across both organizations.
Why the practice exists (failure mode it addresses). Without contractual governance, partnerships rely on informal relationships. When staff turnover occurs or outcomes deteriorate, there is no shared mechanism to fix operational problems, and the model collapses into siloed work.
What goes wrong if it is absent. Repeated failures are treated as individual tenant issues rather than system design issues. Housing staff feel unsupported, health partners disengage due to “no-shows,” and eviction risk rises as incidents accumulate without a coherent plan.
What observable outcome it produces. More stable partnership performance over time, faster problem-solving when metrics worsen, and a defensible record showing the partnership actively manages quality and risk—supporting both tenant stability and payer confidence.
How to keep housing from becoming “unpaid clinical care”
Contracting should explicitly define what housing staff do not do: diagnose, prescribe, or provide treatment. Instead, housing staff should be funded to perform stabilizing coordination work and to trigger timely clinical response through agreed routes. Where clinical work is required in the field (e.g., wound checks, injectable medication support), it should be staffed and governed by clinical partners with appropriate supervision and liability coverage.
Practical evidence pack for commissioners and payers
To make integration sustainable, build a simple evidence pack aligned to the contracted scope: workflow completion logs, sample case files showing consent and documentation quality, governance minutes with action logs, and a small set of stability outcomes. This shifts the partnership from “nice idea” to an operating model that can survive leadership change, funding scrutiny, and audits.