Patient
The person receiving care, across encounters, departments, sites and time.
01 Why it matters
What depends on getting this right
A duplicate patient record is a clinical safety issue before it is a data one, and every measure of outcome, cost per episode and readmission depends on the same person being recognised across a pathway that crosses several systems.
02 Where it lives
Every system holds a different version
None of these is wrong. Each was built for a purpose and records the part of the entity that purpose needed, which is exactly why resolution is required rather than optional.
| System | What it holds of this entity |
|---|---|
| HIS / EMR | encounters, diagnoses, procedures and clinical notes |
| Master patient index | the identity layer itself, and its duplicate queue |
| Revenue cycle / billing | claims and the payer view of the same person |
| LIS / RIS / pharmacy | diagnostics and medicines ordered against the encounter |
| Scheduling | appointments, attendance and did-not-attend history |
03 Match keys
What actually matches, and what only looks like it does
| Key | How well it works |
|---|---|
| National health identifier | The strongest key where a national scheme exists. |
| Local medical record number | Reliable within a site, duplicated across a group. |
| Name, date of birth and sex | The classic triple, insufficient on its own at scale. |
| Address and next of kin | Useful supporting evidence, volatile on its own. |
04 Survivorship
When two records disagree, which value wins
Survivorship is a business decision, not a technical default. These rules should be agreed with the people who own the data and then applied consistently, because changing them later restates history.
Never auto-merge on weak evidence
A wrong merge in healthcare joins two people's clinical histories, which is worse than a duplicate.
Demographics from the most recently verified registration
Confirmed at the point of care rather than inferred.
Clinical data is never survived, only linked
Records are associated under one identity; observations themselves are not overwritten.
Every merge and unmerge is auditable
Reversibility is a clinical safety requirement, not a nice-to-have.
05 The cost of not doing it
What stays broken while it is unresolved
Fragmented clinical history
A clinician sees part of the picture, which is a direct safety risk.
Cost per episode impossible
Consumption across departments cannot be assembled into one pathway.
Readmission rates understated
A readmission under a second record looks like a new patient.
Duplicate testing
Tests repeated because the prior result is attached to the other identity.
06 Metrics that divide by it
The numbers this entity carries
07 Questions
Frequently asked
Why is auto-merging so dangerous here?
Because the cost of a false positive is not a reporting error. Joining two people's records creates a clinical record that describes nobody, so healthcare resolution runs with high match thresholds and a human review queue by design.
What makes the biggest difference to patient matching?
Capturing and verifying a national identifier at registration, plus standardised address and name handling. Most duplicate creation happens at the front desk, not in the data layer.
See the duplicates in your own data
We will resolve one entity on your systems, live, and show what the duplicates are costing.