Multi-State Senior Housing Data Governance: One Record, Many Rules
Do not fork the record. A multi-state portfolio has one operator-controlled operating record with one authoritative source per field; state variation is carried as parameters and attributes of that field, applied when a report is produced, not as duplicate fields created at ingest. In practice that means three commitments: one portfolio definition per contested metric, with each state’s counting rule mapped into it and the raw source value retained; field-level lineage on every admitted value, so a state figure and a board figure can both be traced to the same origin; and a property-to-…
On this page
Reads happen per system and per region. Governance happens once, above all of them, which is what keeps a portfolio figure and a state figure from becoming two unrelated truths.
Each of these is a definition problem wearing a technical disguise. The governing rule in the right-hand column is what keeps one field from becoming several.
The same five phases as the pillar , with Phase 1 carrying the state-divergence inventory and Phase 3 reconciling per property and per state before any portfolio roll-up is published.
A multi-state portfolio usually inherits duplicate systems by acquisition. Governing the record first means the consolidation decision can be made deliberately rather than under reporting pressure. See also integration without replacing your EHR .
DATA → TRUTH → DECISION → EXECUTION, applied per field. Read the Operator Authority Chain™ for the full argument.
Key points
- A method for maintaining one operator-controlled operating record across a multi-state portfolio, where states define census, acuity, staffing and reportable events differently.
- Keep one operator-controlled operating record with one authoritative source per field, and carry state variation as parameters of those fields rather than as duplicate fields. Write one portfolio definition per contested metric, map each state’s counting or scoring rule into it while retaining the raw source value, fix the property-to-entity mapping per effective date, reconcile at property and s…
- Each state needs its own view, not its own field. A state view is the governed field with that state’s inclusion rule applied at report time. The moment a state gets its own stored field, the portfolio has two numbers with equal standing and no rule for choosing between them — which is exactly the condition a governed record exists to prevent.
- Both are produced and both are traceable to the same underlying value. The governed record shows the portfolio figure, the state figure, the parameter that separates them, and who accepted each. When systems or definitions disagree, the operator governs — the disagreement is documented rather than averaged away.
- No. Regional systems are read one direction and remain the operator’s systems of record until the operator decides otherwise. Clinical scope is a configuration choice: SeniorCRE includes its own EHR and eMAR and can serve as the clinical system of record, or it can run alongside an incumbent clinical system with exactly one authoritative MAR at all times.
- The property-to-entity mapping is held per effective date with history retained, and decisions reference the record version they were made against. A reorganisation therefore produces a visible restatement with its own basis, rather than silently changing the figures a past decision was made on.
- No. The record makes state-specific reporting reproducible and traceable, and it records who made each determination. It does not render a regulatory opinion, and no compliance outcome is claimed. Operators remain responsible for their filings and should confirm requirements with their own counsel and regulators.
Frequently asked questions
- How do I govern senior housing and care data across multiple states?
- Keep one operator-controlled operating record with one authoritative source per field, and carry state variation as parameters of those fields rather than as duplicate fields. Write one portfolio definition per contested metric, map each state’s counting or scoring rule into it while retaining the raw source value, fix the property-to-entity mapping per effective date, reconcile at property and state level, and produce both state and portfolio views from the same governed field.
- Should each state have its own version of the number?
- Each state needs its own view, not its own field. A state view is the governed field with that state’s inclusion rule applied at report time. The moment a state gets its own stored field, the portfolio has two numbers with equal standing and no rule for choosing between them — which is exactly the condition a governed record exists to prevent.
- What happens when a state definition conflicts with the board definition?
- Both are produced and both are traceable to the same underlying value. The governed record shows the portfolio figure, the state figure, the parameter that separates them, and who accepted each. When systems or definitions disagree, the operator governs — the disagreement is documented rather than averaged away.
- Does multi-state governance require replacing regional systems?
- No. Regional systems are read one direction and remain the operator’s systems of record until the operator decides otherwise. Clinical scope is a configuration choice: SeniorCRE includes its own EHR and eMAR and can serve as the clinical system of record, or it can run alongside an incumbent clinical system with exactly one authoritative MAR at all times.
- How are entity and licence changes handled without restating history?
- The property-to-entity mapping is held per effective date with history retained, and decisions reference the record version they were made against. A reorganisation therefore produces a visible restatement with its own basis, rather than silently changing the figures a past decision was made on.
- Is this a compliance product?
- No. The record makes state-specific reporting reproducible and traceable, and it records who made each determination. It does not render a regulatory opinion, and no compliance outcome is claimed. Operators remain responsible for their filings and should confirm requirements with their own counsel and regulators.
https://seniorcre.com/senior-living-data-integration/multi-state-data-governance