Source of Truth: Deciding Which System Wins When Data Disagrees

The census report says 82 residents. The billing system says 80. The staffing schedule was built for 84. Everyone in the meeting has a number, and each number came from a system that is correct by its own logic. Without a rule for which system wins, meetings turn into debates, reports get rebuilt by hand and leadership stops trusting the data.

The remedy is a simple governance habit: decide, for each type of data, which system is the source of truth, and make every other system follow it.

Why systems disagree

Disagreement is normal, not a sign of incompetence. Common causes include:

Different definitions. One report counts a resident on the day of admission, another counts after the first midnight.

Timing differences. One system updates in real time, another syncs overnight, another is updated by hand at month end.

Duplicate entry. The same fact is typed into two systems, and one gets missed or mistyped.

Different purposes. A scheduling tool tracks who is expected to work, a payroll system tracks who was paid for hours worked.

Integration gaps. Data moves between systems through exports, interfaces or spreadsheets, and each hop is a chance for error.

The authoritative system rule

For each important piece of data, name one system as the authority. That system is where the data is created and corrected. Other systems may display it, but they do not change it, and when there is a discrepancy, the authoritative system is right until proven otherwise.

Here is a typical starting point for a senior-living or skilled nursing operator. Adjust it to your own software:

Clinical data

Resident clinical information, orders and care documentation: the electronic health record.

Admission, discharge and transfer events: the EHR, since these drive census and billing downstream.

Scheduling and workforce data

Employee records, pay rates and hours worked: the payroll or HR system.

Planned shifts and coverage: the scheduling system, with actual hours reconciled to timekeeping.

Financial and billing data

Charges, payer information, claims and receivables: the billing or financial system, fed by clinical events from the EHR.

General ledger and budgets: the accounting system.

Resident and family contact data

Choose one: usually the EHR or a customer relationship tool, and keep others read-only.

Your list may differ, and some data will straddle two systems. The point is to write the choice down.

How to build the rule

List your key metrics and fields. Start with the ones leadership uses: census, staffing hours, receivables, admissions.

Trace each to where it is created. Who first enters it, and in what system?

Name the authority and the owner. The owner is a person who can fix errors and answer questions.

Document the definition. For example, what counts as an occupied bed on a given day.

Decide how data flows. Prefer interfaces over retyping. If a manual step is unavoidable, record who does it and how often.

Publish it. A one-page data map that lives where managers can find it is enough to start.

Reconcile on a schedule

Even with a clear rule, errors slip in. Set up regular reconciliations, such as a monthly census check between the EHR and billing, or a payroll to schedule comparison. When a mismatch appears, fix it in the authoritative system first, then let the correction flow downstream. Track recurring mismatches, since they point to a process or integration problem worth fixing.

Handle the human side

People protect their spreadsheets. Staff who built a report by hand may worry the new rule makes their work irrelevant. Explain that the goal is to reduce rework, not blame. Involve department leaders in choosing the authority, because they know how the work really happens.

Protect the data

A source of truth should also be well controlled. Limit who can edit authoritative records, keep audit logs of changes and back them up. For systems containing protected health information, apply HIPAA access controls and review them regularly.

Where to start

Pick one painful discrepancy, such as census, and solve it end to end. Define it, assign the authority, fix the flow and measure whether the arguments stop. Then move on to the next.

UnityCare IT helps healthcare operators map their systems, set data ownership and build the interfaces and reports that keep scheduling, clinical and billing numbers aligned.

Related service

An outsourced IT department with proactive maintenance and one number to call.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Address: UnityCare Technologies, 2524 N Broadway Ste 554, PMB 947974, Edmond, Oklahoma 73034-4172