EHR / EMR
Does a senior living operator need one EHR across every community?
Last reviewed
Direct answer
No. A single EHR can simplify operations, but it is not required for governed portfolio reporting. What is required is one approved set of definitions and authority rules, applied to each community’s clinical source. Many operators keep several EHRs because of acquisitions, care settings or contracts. Moving to one platform is a strategic choice, not a requirement for governance.
Why this happens
Standardizing on one platform takes years across a growing portfolio. Comparable reporting is needed sooner.
Even organizations on one EHR configure it differently by community, so they still need governed definitions.
Hypothetical example: a level-of-care change on the 28th
EHR
Level of care: 3 (effective the 28th)
The reassessment was signed on the floor.
Billing
Level of care: 2 for the month
The rate change follows the billing cycle and a family notice period.
Scheduling
Care hours budgeted at level 2
Staffing plans were set before the reassessment.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Each value is correct for its system. The operating question is which one governs revenue, staffing and reporting for those three days.
The governance question
The EHR can be the authoritative source for clinical data while the operator still governs how that data becomes a financial, staffing or reporting decision. That cross-system step needs its own authority rules and record.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Read clinical events without altering the clinical record.
- Map clinical events to their financial and staffing consequences.
- Surface timing gaps between clinical, billing and scheduling systems.
- Govern across communities that use different clinical systems.
- Keep clinical authority with clinical leadership.
SeniorCRE perspective
Coherence before Intelligence. Replacement remains the operator’s choice. SeniorCRE is designed to govern what retained clinical systems produce. Its clinical record surfaces are built, but medication administration and eMAR remain roadmap — not built and excluded from Road 2 starting scope. A future clinical system-of-record configuration requires function-specific build, clinical-safety review and sign-off, end-to-end validation, data readiness and operator acceptance before production entry; it is not currently deployable. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
