When Systems Disagree
Why does integrating systems not eliminate conflicting data?
Last reviewed
Direct answer
Integration moves data between systems. It does not decide which value is authoritative when they disagree. A connected system can copy a stale or incorrectly defined value faster and more widely than a manual process. Integration removes rekeying. Governance removes ambiguity. Organizations need both, and integration without governance can make conflicting data harder to see.
Videos that answer this question
Watch: Can You Trust the Operating Picture of Your Enterprise? · 1:39
Watch: Senior Care Tech Paradigm · 8:30
Watch: RIDEA Governance Gap · 7:15
Watch: The Blind Spot: Connecting Capital to Care · 5:11
Watch: Truth before Intelligence · 10:50
Watch: Governing SI Truth · 7:34
Watch: The Architecture of Operational Truth · 7:45
Watch: The Monday Morning Number · 9:14
Watch: The Institutional Operator · 5:31
Watch: The Operator Authority Chain · 6:50
Why this happens
Most integrations follow "last write wins" or "source A overwrites B." Those are technical rules, and they quietly decide what the organization treats as true.
Once values are copied, two systems can agree only because one copied the other. That looks like confirmation, but nothing was actually checked. Unified data is not the same as governed truth.
Hypothetical 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.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
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 an operator-controlled operating record with its lineage.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
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 Operator-Controlled 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 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.
