When Systems Disagree
How do we know where an operating number came from?
Last reviewed
Direct answer
You know where a number came from only if lineage was recorded when the number was created: which systems supplied the values, what definition and calculation were applied, what was changed, and who approved any determination. If that record does not exist, tracing a number means rebuilding it by hand, and the result is usually uncertain.
Why this happens
Most reporting tools keep the calculation but not the decisions. You can see the formula, but not why one source was chosen over another or who adjusted a value.
Lineage matters most when a number is challenged by a board, a lender or a surveyor. That is also when there is the least time to rebuild it.
Example: one community, one day, three numbers
Clinical system
92 residents
Counts everyone admitted and not discharged, including a resident on hospital leave.
Accounting
90 residents
Counts billable resident days; the hospital leave and a same-day move-in are excluded until the period closes.
CRM
91 residents
Counts the signed move-in but has not yet received the move-out recorded on the floor.
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
None of these systems is malfunctioning. Each records a different event, on a different clock, under a different definition. The disagreement is information, not noise.
The governance question
The useful question is not "which number is right?" but "which number has authority to govern this decision?" Evidence from each system is preserved, the disagreement is surfaced rather than averaged away, the operator decides which source has authority for the decision at hand, and that determination is written to a governing record with its lineage.
Evidence → Disagreement → Authority → Governing Record
What good operating infrastructure should do
- Preserve every source value instead of overwriting it.
- Detect and surface disagreements before they reach a report.
- Apply operator-approved rules about which source governs which decision.
- Record who made each determination, when, and why.
- Make every governing number traceable back to its sources.
SeniorCRE perspective
SeniorCRE is designed around this exact moment. Its Governed Operating Record keeps the original values from each system, flags where they disagree, and records the operator’s determination of which value governs, so that every downstream report, recommendation and action reads from a number with known authority. When systems disagree, the operator governs. Status: the Governed Operating Record is designed and not yet implemented in any community. What has been built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.