Dental patient duplicate records need identity review before any merge or deletion. Two similar names may identify different people; two different names may belong to one person. Flag the suspected pair, compare independent identifiers and record history, and route a confirmed duplicate to the person authorized to use the software's merge procedure.
The front desk's first deliverable is a reliable review packet—not a cleaner search screen. The suggested controls below separate identification, approval, execution, and verification. Adapt them to the practice's records policy and the exact software version.
First decide which problem you have
The SAFER Patient Identification guide distinguishes a duplicate record for one person from an overlay, where another person's information enters the wrong record. These are different correction problems. The guide also recommends involving responsible clinicians when identification errors may have affected care. SAFER Patient Identification guide
At intake, use three working categories:
| Finding | Working classification | Next decision |
|---|---|---|
| Two records appear to describe one verified person | Possible duplicate | Establish whether they can safely be combined |
| Similar names belong to different verified people | Look-alike records | Keep separate and reduce selection confusion |
| One chart contains information belonging to different people | Possible overlay | Escalate for records and clinical review; do not merge |
These are provisional labels. An employee should not classify a record as a duplicate merely because it has no recent visits or a zero balance. Nor does a shared address or family telephone establish that two charts represent the same person.
If the discovery affects today's visit, notify the treating team promptly and follow the practice's approved identity-exception process. Front desk staff should not guess which chart contains the complete clinical history or move a note to make the appointment proceed.
Compare identity before comparing balances
Use authorized access to place the two patient identifiers side by side in a protected review record. Include formal and prior names where available, date of birth, verified contact history, relevant registration evidence, and the source of each value.
Ask the patient to provide identifying information under the identity-verification protocol. Avoid reading another possible patient's details aloud and asking whether they sound familiar.
Document both matches and conflicts. A difference needs an explanation supported by evidence, not a quick edit to make the screens agree. For example:
- A former surname may explain a name difference.
- A documented move may explain different addresses.
- A transposed birth-date entry needs verification before correction.
- Distinct treatment histories may require clinical review even when demographic fields match.
Record the basis for concluding that these are the same person. If it remains uncertain, leave the records separate with an assigned investigation. “Names look right” is not a completed identity decision.
Prepare a merge request that identifies what must survive
After identity review, inventory both records. Ask the relevant owners to identify the appointment history, clinical entries, images, documents, insurance, ledger activity, recalls, communication preferences, portal relationships, and external references that need protection.
The request should name the two patient identifiers, proposed surviving record, reason for that choice, unresolved differences, reviewer, and intended execution time. Keep original evidence accessible under the records policy. Do not attach a complete chart to an ordinary support email just to describe a demographic mismatch.
A merge is different from a record amendment or entry correction. If a note belongs to the wrong person, the records owner needs to resolve that content problem; combining more records does not fix it.
Also distinguish patient records from guarantor or subscriber records. A person may legitimately appear in more than one administrative role. Establish what each object represents before deciding that it is redundant.
Let the system's documented procedure determine the mechanics
Use the current vendor instructions and authorized permissions. Confirm what is moved, retained, archived, or left for manual reconciliation, and whether the operation is reversible. Ask for vendor support if those effects are unclear.
For example, Open Dental states that patient merges cannot be undone. Its instructions tell users to keep the account connected to images when imaging software is bridged, and note that duplicate insurance or recall data may need cleanup afterward. Those details apply to that product; they are not a universal merge recipe. Open Dental patient-merge instructions
As an office control, have a second authorized person verify the direction of the proposed merge immediately before execution. The “keep” and “merge from” identifiers should match the approved request. Do not rely on which window happened to be open first.
Have the technical owner confirm the approved recovery arrangements and a safe work window. A backup should not be treated as an easy undo button: restoring it may affect unrelated work recorded after it was made. Do not promise recoverability without a verified method.
Example: the newer chart holds the images
Consider a fictional patient with two confirmed duplicate charts. The older chart contains prior visits and a remaining account balance. The newer chart contains recent images linked through a separate imaging application.
An “always keep the oldest chart” rule would skip an important dependency. The authorized reviewer instead checks the vendor's imaging-link instructions, compares the financial and clinical inventories, and chooses the surviving record on that evidence.
Before the merge, the billing reviewer records the two source balances and their underlying transactions. The clinical reviewer identifies the expected documents and image sets. The technical reviewer verifies how the imaging application locates the surviving patient.
After execution, those reviewers check their own evidence again. A single result in patient search does not establish that images open correctly, that a payment was preserved once, or that an old portal link reaches the correct person.
If this issue arose during a wider conversion, connect it to the data-migration acceptance process. Do not let resolution of one chart pair stand in for validation of the whole transfer.
Verify the record from each user's point of view
Complete a short, role-based check:
- Registration confirms the correct identity and search behavior, including approved prior-name references.
- Clinical staff confirm the expected history, attachments, and image access without altering clinical content to reconcile differences.
- Billing confirms charges, payments, credits, claims, and balances against the pre-merge inventory.
- The communication owner checks appointments, recalls, preferences, and portal or reminder destinations.
- The records owner preserves the approval, source identifiers, surviving identifier, execution details, and verification results.
Keep an unresolved item open with its own owner. Do not create a balancing adjustment, delete an attachment, or remove a second recall simply because it looks repetitive; confirm the underlying event first.
Close the case only when identity and downstream checks agree. Then address the cause: a search that omitted prior names, inconsistent registration, a duplicate import, or a misunderstood guarantor role. A useful correction reduces the chance that the next employee creates the same second chart again.
