Loading...
Whitepaper
Why interoperability in senior housing & care is earned workflow by workflow—and why governance begins where exchange ends.
Published by SeniorCRE, LLC. September 2026.
Asking whether an organization in senior housing & care “is interoperable” is too broad to be useful. Interoperability is better assessed workflow by workflow, with the counterparties, coverage and failure paths stated. Exchange alone does not determine which definition or source is authorized for a particular decision. That is a governance question, and the operator remains accountable for answering it.
A digital connection pays off only once the counterparties use it too. A technically superior link that reaches a third of an operator’s pharmacies is less useful, day to day, than a fax line that reaches all of them. As Brendan Keeler puts it, the reliability of ubiquity “beats the functional advantages of a technically superior one.” So each workflow climbs its own adoption curve, and success in one buys remarkably little in the next.
The useful question is not whether two organizations are interoperable. It is which workflows they can complete electronically, and with what share of their counterparties.
Exhibit 1
Cross-organizational workflows, graded from the operator’s perspective. Grades are directional, not audited.
| Counterparty | Workflow | Status | Note |
|---|---|---|---|
| Payers | Skilled nursing claims and eligibility | Electronic | via clearinghouses |
| Medicaid waiver billing for assisted living | Fragmented | varies by state | |
| Prior authorization for post-acute stays | Analog | portals, fax, phone | |
| Hospitals | Admission, discharge and transfer notifications | Fragmented | hospital mandate since 2021; strongest for skilled nursing |
| Referrals into post-acute and residential care | Fragmented | platforms plus fax | |
| Discharge information to assisted living and memory care | Analog | ||
| Pharmacies | New prescriptions for residents | Fragmented | network exists; long-term care mandate counted from 2028 |
| Pharmacy orders synchronized to the eMAR | Fragmented | depends on vendor pairing | |
| Refill requests and order clarifications | Analog | ||
| Physicians | Visit notes and care plans | Fragmented | |
| Change-of-condition notices, orders and signatures | Analog | ||
| Home health, hospice, therapy | Visit scheduling and shared care plans | Analog | |
| Labs and diagnostics | Lab orders and results | Fragmented | looks green with one dominant lab |
| Mobile imaging reports | Analog | ||
| Regulators | Skilled nursing assessment and quality reporting | Electronic | federally mandated |
| Infection and outbreak reporting | Fragmented | by setting and state | |
| Assisted living incident and licensing reports | Analog | state forms and portals | |
| Suppliers | Orders and invoices with major distributors | Electronic | for operators on purchasing platforms |
| Local and specialty vendors | Fragmented | ||
| Referral sources, families | Placement-agency lead handoff; family updates | Fragmented | |
| Owners, REITs, lenders | Monthly financial and census packages; covenant certificates | Analog | spreadsheets and PDFs |
| Occupancy and rate data to benchmarking services | Fragmented | ||
| Insurers | Incident, claim and loss-run exchange | Analog |
Source note: SeniorCRE analysis, September 2026, adapting the workflow framework in Brendan Keeler, “Interoperability, Unbuttoned” (Health API Guy, September 29, 2026).
The single largest push toward electronic exchange in American healthcare was the federal EHR incentive program created by the HITECH Act in 2009. It paid hospitals and physicians to adopt certified EHRs. Long-term and post-acute care providers were ineligible. Residential care fared worse still: only 41% of residential care communities used an EHR in 2020, up from 26% in 2016. Workflows go digital where money or a mandate arrives. In senior housing & care, the money largely did not arrive, and the mandates that did were written for skilled nursing and hospitals.
Exhibit 2
| Lever | What it does | Skilled nursing | Assisted living, memory care |
|---|---|---|---|
| HITECH EHR incentives (2009) | Paid hospitals and physicians to adopt and use certified EHRs | Ineligible | Ineligible |
| Resident assessment submission | Requires electronic submission of resident assessment data to CMS | Yes | No |
| Hospital event notifications (2021) | Hospitals must make a reasonable effort to send admission, discharge and transfer notices to applicable post-acute providers | Yes, as recipient | Not clearly |
| SNF Value-Based Purchasing | Withholds 2% of Medicare Part A payments and redistributes 60% based on quality, including readmissions | Yes | No |
| CMS-0057-F (2026 and 2027) | From Jan. 1, 2026, affected payers decide prior authorizations within 72 hours (expedited) or 7 days (standard) and state specific denial reasons; payer prior authorization APIs are due Jan. 1, 2027 | Yes, for Medicare Advantage and Medicaid stays | Limited |
| Controlled-substance e-prescribing (2028) | Part D prescriptions for long-term care residents count toward prescriber e-prescribing compliance from Jan. 1, 2028 | Yes | Depends on facility and state definitions |
Source note: See Sources below. “Limited” and “not clearly” reflect that these rules are written for payers, hospitals and certified post-acute providers rather than state-licensed residential settings; applicability to a specific community should be confirmed with counsel.
Suppose every line on the map turned green tomorrow. Data could move and still arrive with different definitions, effective dates and purposes. That does not make one system wrong. It means the receiving organization must state which representation is authorized for the decision at hand, how differences are reconciled and who approved the rule.
This is a separate claim from the workflow map above. The map describes exchange. The example below describes the governance required after exchange. It is illustrative design logic, not evidence from an operator deployment.
Exhibit 3
Illustrative example; values are hypothetical. For a daily staffing decision, the operator may authorize physically present residents under an approved census rule. For a sales review, deposits and expected move-ins remain a separate pipeline measure. For revenue analysis, billed resident days reconcile to the ledger. Governance does not collapse these measures into a universal occupancy number; it preserves each definition, purpose, authority and lineage.
SeniorCRE is operator-controlled operating infrastructure for senior housing & care. It sits above the clinical, financial, workforce and occupancy systems an operator already runs. The construct that differentiates it is the Operator-Controlled Operating Record: a governed record in which definitions, source authority, reconciliation and lineage are set by the operator, not by any single vendor. When systems disagree, the operator governs.
“Governed” does not mean SeniorCRE is right about everything. It means the record preserves the representation the operator has authorized for a stated purpose, together with the source records, governing rule, reconciliation history and accountable approval.
Exhibit 4
Describes the design construct and target state. Permission to act does not equal authority to determine truth; authorization is a separate, recorded control.
Exhibit 5
| Workflow | Canonical entities | What must be governed |
|---|---|---|
| Hospital notifications and discharge information | Resident, Care Plan | The event and condition record authorized for the receiving workflow |
| Pharmacy orders, refills and clarifications | Resident, Care Plan | The authorized source and reviewer for each order change |
| Physician orders; home health and hospice visits | Care Plan, Shift | The relationship among care ordered, scheduled and documented |
| Claims, prior authorization, Medicaid waiver billing | Resident, Ledger | The rule connecting billed revenue to eligible days of care |
| Referral and placement-agency leads | Resident, Property/Unit | What counts as a lead, deposit, move-in and available unit |
| Agency staffing and payroll | Shift, Ledger | The rule connecting scheduled, worked and paid hours |
| Owner packages, covenant certificates | Ledger, Property/Unit, Entity | The contract, accounting policy or approved plan that defines each measure |
| Regulatory and insurer reporting | Resident, Entity | The authorized record for each filing purpose |
Illustrative mapping to the record’s six canonical entities; describes design intent, not a current integration.
The operator keeps its incumbent EHR, CRM, scheduling and financial systems. SeniorCRE is designed to apply operator-approved definitions, authority, reconciliation and lineage across what those systems produce.
Where an operator deliberately chooses, SeniorCRE can be deployed as the system of record for selected functions, including its own EHR and eMAR, domain by domain. Replacement is never a condition of governance.
Neither deployment model is in operator production today. See seniorcre.com/deployment-models.
An operator and an owner may evaluate the same month through different contractual and economic lenses. Governance does not remove judgment or repair incomplete drafting. It can make the basis of a measure inspectable: the governing contract, approved budget, accounting policy or operator rule; the source records used; any reconciliation performed; and the person authorized to approve it.
The figures that decide payments between them are narrower than the operating record. In third-party management, NOI or EBITDAR decides most of them: fees, covenant tests, lease coverage and distributions. Occupancy decides a payment mainly where a loan carries a minimum-occupancy covenant. That short list is where an agreed, inspectable basis matters most.
Read Owner and operator: one operating recordInteroperability in senior housing & care is uneven and is more usefully assessed workflow by workflow than as a single organizational attribute. Exchanged data can retain different definitions and purposes. The governance discipline described here selects an authorized representation for a declared use and preserves its lineage.
That the workflow grades are audited or apply to a specific operator. That every system disagreement is a governance failure, or that one universal number should replace purpose-specific measures. That SeniorCRE’s Operator-Controlled Operating Record is in operator production today. That a named vendor integration or quantified outcome, savings or return exists.
SeniorCRE will publish deployment evidence when it has it, not before.
This paper should not treat every discrepancy as proof of a governance gap. The argument narrows when a difference is ordinary arithmetic, delayed synchronization, professional judgment, incomplete contract drafting or an unreported follow-through on an agreed action, and can be resolved without a durable authority rule. It would be falsified for a workflow if the operator can already show a consistently applied definition, named source authority, documented reconciliation, retained lineage, accountable authorization and verified execution across the systems involved.
The practical test is therefore workflow-specific: identify a consequential decision, inspect the rule and source records behind it, identify who may authorize action, and verify that the result returns to the record. SeniorCRE has not yet demonstrated that full chain in an operator production deployment.
All sources accessed September 2026.
The workflow framework on this page is adapted from Brendan Keeler’s essay “Interoperability, Unbuttoned.” Its use here does not imply his endorsement of SeniorCRE. Other names and marks are the property of their respective owners; mention does not imply affiliation, integration or production deployment. Nothing on this page is legal, regulatory, clinical or investment advice.