Duplicate-patient workflows should flag possible matches for an approved identification process, not automatically merge people because their names look similar. Define who investigates, which evidence may be used and how a confirmed correction affects linked records. A merge can have consequences beyond the demographic screen.
Let’s plan your patient record review.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Establish responsible governance
ONC's SAFER guides include patient identification as a dedicated safety area. Use appropriate reference material alongside qualified local clinical, records and privacy review; a generic matching checklist does not establish institutional compliance.
Record the approved identity attributes and verification process. Avoid inventing a universal match score or identifier hierarchy without domain review.
Define the investigation stages
| Stage | Software requirement | Acceptance case |
|---|---|---|
| Candidate detected | Show why review is suggested | Similar names remain distinct |
| Investigation assigned | Named authorised owner | No unowned ambiguous queue |
| Evidence reviewed | Controlled access to relevant information | Unrelated records stay protected |
| Decision recorded | Match, distinct or unresolved | Rationale and authority retained |
| Merge or correction executed | Approved relationship handling | Linked records traced |
| Error discovered later | Governed correction path | Impact and history visible |
Separate detecting a candidate from making the identity decision. Similarity can help prioritise review but is not authority to combine records.
Map downstream effects before merging
For a hypothetical clinic, appointments, reports, documents, portal accounts and billing references may link to the affected records. Identify each dependency and how it follows the approved correction.
Do not assume changing one database identifier repairs external systems or downloaded documents. Maintain a reconciliation plan and show unresolved downstream work.
Test mistaken candidates and recovery
Use synthetic records with similar names, changed contact details and conflicting identifiers. Verify staff can decide that records are distinct without repeatedly reopening the same candidate unnecessarily.
Exercise an approved correction scenario after a prior merge decision. Preserve evidence and access controls; do not offer unrestricted destructive merge or unmerge shortcuts without a reviewed process.
Patient matching questions
Is an exact name and phone match sufficient?
Do not assume it. Shared or changed contact details and similar names require the approved identification process.
Should every duplicate candidate block care administration?
Have qualified institutional owners define the operational response. The software should make uncertainty and responsibility visible.
Use document provenance requirements, and review the correction workflow with Drema's healthcare software team.
This article explains what to build, not legal advice. Rules change; confirm against the current official text before relying on it.