A buyer's procurement document — not a vendor's marketing checklist
The dominant RFP frameworks in senior housing & care were inherited from healthcare IT research firms, trade association procurement guides, and legacy software business models. They were never designed to evaluate an operator-controlled operating record. They were designed to evaluate which modules to purchase from which vendor — and they systematically disadvantage the platforms most likely to address the structural problems operators are actually experiencing.
This whitepaper replaces those frameworks with a procurement document built around how operating events propagate through a senior housing & care portfolio. It contains 13 evaluation sections, suggested vendor response prompts, a 1–5 scoring model, and the Operating Event Test — the single clearest way to separate a true Senior Housing & Care Operating Infrastructure from a collection of modules.
Three structural shifts
Evaluates how a single operating event — a level-of-care change, an admission, a shift swap — propagates through clinical, billing, workforce, and capital views.
Tests for one operator-controlled operating record across the six entities (Resident, Care Plan, Ledger, Shift, Property/Unit, Entity) — not a federation of integrated point tools.
Models the operational tax of remaining fragmented — revenue leakage, agency premium, integration overhead — alongside the line-item software cost.
What every vendor must answer
Each section includes a procurement question, a suggested vendor response prompt, and a place to record the 1–5 score and evidence. The full PDF includes the response prompts and a scoring worksheet — the summary below sets the scope.
Platform Architecture & Data Model
Does the platform run on one operator-controlled operating record — resident, care plan, ledger, shift, property, entity — or a federation of point modules stitched by middleware?
Clinical-to-Billing Propagation
When a clinical level-of-care change is documented, how quickly and reliably does it propagate to the billing ledger and the investor reporting layer?
Workforce & Acuity Integration
Does scheduling respond to real-time acuity, census, and skill mix — or is it driven by static templates and reconciled after the fact?
Real-Time Investor & Capital Reporting
Can owners, REITs, lenders, and capital partners pull one operator-controlled operating record without overnight ETL or repeated downstream reconciliation?
Migration Timeline & Risk
What is the realistic implementation curve, parallel-run window, and cut-over risk profile — including data fidelity for clinical, financial, and HR records?
Data Ownership & Portability
Who owns the operational data, in what format is it returned on exit, and how is portability guaranteed contractually — not just promised commercially?
API Access & Extensibility
Are first-class APIs documented, versioned, and rate-disclosed? Can your internal teams and downstream tools read and write without vendor brokerage?
HIPAA & SOC 2 Readiness
What is the current attestation status, the audit cadence, and the realistic Type II timeline? Read live wording at /trust before accepting marketing copy.
Multi-Community Hierarchy
Does the platform model holding company → operator → region → property → unit cleanly — with cascading permissions and roll-up reporting native to the schema?
Role-Based Access & Governance
How granular are roles, what is the audit trail of permission changes, and how are session, MFA, and concurrent-session governance enforced?
Audit Trails & Compliance Evidence
Is the platform append-only for clinical and financial events? Can a state surveyor or lender auditor be granted scoped, time-bound, read-only access?
AI Governance & Model Transparency
What models are deployed, in which workflows, with what human-in-the-loop controls, and what disclosures support a four-tier AI governance posture?
Implementation Support & Total Cost of Fragmentation
What is the all-in cost — implementation, integrations, internal labor, and the operational tax of remaining fragmented — modeled symmetrically across alternatives?
A 1–5 scale anchored to operating reality
| Score | Label | Definition |
|---|---|---|
| 1 | Absent | Capability does not exist or requires custom build. |
| 2 | Partial | Capability exists in fragments; requires middleware or manual reconciliation. |
| 3 | Functional | Capability ships, but is bolt-on rather than native to the data model. |
| 4 | Native | Capability is built into the operator-controlled operating record and propagates without integration work. |
| 5 | Operating-Event Native | Capability passes the Operating Event Test — a single event updates clinical, financial, workforce, and capital views simultaneously. |
One event. Four views. Zero integration calls.
Ask each vendor to demonstrate, in a live environment, what happens when a single operating event is recorded — a Level 3 → Level 4 care-tier change for a named resident at a named property. Time the propagation. Capture which views update natively, which require integration, and which require overnight ETL or manual reconciliation.
- Clinical view: assessment, care plan, and orders reflect the new acuity tier.
- Financial view: ledger picks up the rate change, AR is reforecast, payer split is correct.
- Workforce view: required skill mix and hours-per-resident-day update; schedule and acuity alert fire.
- Capital view: investor and owner dashboards reflect the same number — without an overnight job.
A platform built on one operator-controlled operating record passes this test in seconds. A federation of integrated modules answers in hours, days, or never. The Operating Event Test is not a feature comparison — it is a structural test of whether a platform is a true Senior Housing & Care Operating Infrastructure or a collection of modules with a shared logo.
Run it as a procurement document, not a marketing brief
Send the same 13 sections, the same response prompts, and the same scoring worksheet to every shortlisted vendor. Score evidence, not narrative.
Reserve 30 minutes in every finalist demo for the Operating Event Test. Capture the propagation timing on the record. This is the deciding artifact.
Take the next step
Download the full procurement document — vendor response prompts, scoring worksheet, and the Operating Event Test script — or schedule a portfolio assessment to apply the framework to your shortlist.