Master Data Management: Resident, Unit, Employee and Community Identifiers

Cross-system data governance depends on knowing that two records describe the same thing. A resident in the EHR, the billing system and the CRM may carry three different keys, a slightly different name spelling and different move-in dates. Without master data, a portfolio roll-up counts that resident one, two or three times depending on the report.

Master data management gives the core entities of the business one identity each. The data dictionary gives the core terms of the business one meaning each. Together they let figures from different systems and communities be combined honestly.

This work is foundational and unglamorous, and it pays back in every later step. Reconciliation needs matching keys. Lineage needs stable identities. Access control needs to know which community a record belongs to.

1. Step 1

   Name the master entities

   Start with resident, unit, employee and community. Add payer, vendor and referral source as the program matures.

2. Step 2

   Assign portfolio identifiers

   Give each entity a stable identifier that does not depend on any single system. Record which source creates the entity — for example, the CRM for prospects, the EHR for residents.

3. Step 3

   Map local keys

   Maintain a crosswalk from each system's local key to the portfolio identifier. Review new and unmatched records on a set cadence.

4. Step 4

   Publish the data dictionary

   For each reported term, publish the formula, source system, timing, exceptions, owner and effective date. Leave definitions in brackets until owners approve them: [governing definition].

5. Step 5

   Govern merges and changes

   Write a rule for merging duplicates and for changing identifiers or definitions. Changes need owner approval and are recorded with their effective date.

• Using one system's key as the master. When that system is replaced, every identity in the portfolio changes with it.
• Silent local definitions. A community that computes occupancy differently without recording an exception makes every comparison unreliable.
• Merging without a rule. Ad hoc merges of duplicate residents or employees can destroy history. A documented rule and an audit trail protect it.

Next guide: Audit Trails and Lineage: Tracing Every Figure to Its Source Record

Or return to the full data governance playbook for senior housing & care.