Ask three departments how many residents are in the building and you may get three answers. The EHR shows one number, the billing system another and the staffing or scheduling tool a third. A resident discharged on Friday is still on the dietary list on Monday. A hospital transfer shows as in-house in one system and on leave in another. The differences are usually small, but they matter: they affect staffing, meal counts, billing accuracy, pharmacy orders, emergency preparedness lists and reports to leadership.
Census reconciliation is a routine, not a project. It makes sure every system agrees on who is in the building and who is not.
Timing: admissions, discharges and transfers are entered at different times by different people.
Manual re-entry: a resident is added to several systems by hand, and one is missed.
Different definitions: one system counts a resident on hospital leave as present, another does not.
Interface gaps: integrations between systems may fail quietly or only pass some events.
Bed and room changes: moves between rooms or units are not recorded everywhere.
Data entry errors: duplicate records, name variations or wrong dates.
Choose one system as the authority for admission, discharge and transfer events. For most long-term care organizations this is the electronic health record, since clinical staff enter the events there first. Other systems should receive their information from it, either through an interface or a defined manual step. Write this down, so that nobody wonders which number is correct.
Settle these questions in writing:
Who counts in the midnight census? Define in-house, leave of absence, hospital stay and bed-hold status.
What is a census day for billing? This often follows payer and state rules, so check with your business office and advisers.
Consistent definitions solve many apparent discrepancies without any data being wrong.
Print or export the census from the source-of-truth system at a set time.
Compare it with the other systems that depend on it, such as billing, dietary, pharmacy, scheduling and activities.
Mark any resident who appears in one list but not another.
Resolve the differences the same day, and note the cause.
A designated person, such as the business office manager or unit clerk, owns the check and has a backup.
Look at the list of differences found during the week and ask whether there is a pattern. Frequent errors in the same step suggest a process fix or a broken interface.
Before billing, reconcile census days between the clinical and billing systems. Investigate every variance, including leaves of absence and bed holds. This is where small errors turn into incorrect claims or missed revenue.
Imagine a 100-bed skilled nursing facility where the EHR shows 94 residents, billing shows 95 and dietary prepared 96 meals. Reconciliation finds that one resident was discharged on Saturday but the billing record was never closed, and another was transferred to the hospital and remains on the meal list. Each fix takes minutes, if found early.
Interfaces: ask whether your systems exchange admission, discharge and transfer information automatically, and how failures are reported. A silent interface failure is a major cause of mismatches.
Reports: build a standard comparison report so staff do not have to compare lists by eye.
Alerts: where possible, flag residents present in one system and not another.
Data hygiene: use consistent resident identifiers, and merge duplicates carefully with proper authorization.
Access: limit who can create or edit admission and discharge records, and log changes.
An accurate census supports your emergency plan. In an evacuation, a power outage or a weather event, you need to know exactly who is in the building. CMS emergency preparedness requirements for long-term care facilities expect plans to track residents, so a reliable count is part of readiness.
Census lists contain protected health information. Print only what you need, store them securely and shred paper copies. Keep exports in approved locations rather than on desktops or in email.
UnityCare IT helps long-term care organizations in Oklahoma, Texas and Arkansas review interfaces, build comparison reports and tighten the processes around resident data. If your counts rarely agree, we can help trace where they drift apart.
Keeping PointClickCare and other EHR systems fast, connected and available.
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