Patient Intake

Merging Duplicate Patient Profiles That Share a Phone Number

DispensaryVA Editorial TeamPublished
Merging Duplicate Patient Profiles That Share a Phone Number

Two profiles appear at the counter under different spellings, but both carry the same mobile number and the same date of birth. One profile has the current certification and the other has an older purchase history. The patient insists they have only one account and wants the records combined before checkout. A merge looks like a housekeeping task, but it can move protected health information between identities if the match is wrong.

A duplicate profile is a data-quality problem with a privacy edge. The store needs to prove that both records belong to the same person before any history moves. It also needs to keep enough of the old record to explain what changed. The routine below keeps the merge deliberate, documented, and reversible where the system allows it.

Pause before the merge

Do not merge the profiles while the patient is standing at a busy counter. Move the conversation to a quieter workstation where the screen is not visible to the line. Tell the patient that the records will be reviewed before anything is combined. A merge done in a hurry is hard to audit and harder to undo.

Open both profiles side by side and note the record numbers. Do not edit either profile until the comparison is complete. Take a screenshot or print a summary of each record for the merge file. The before-image is the only proof of what the records looked like.

Tell the patient what information the store will use to confirm identity. Ask for a government-issued photo identification and the certification document the store already accepts. Do not ask for extra medical details to settle a database question. The HHS Office for Civil Rights publishes health-information privacy guidance that should shape how the counter handles this conversation.

Compare the records field by field

Compare the legal name, date of birth, phone number, address, and certification number on both profiles. Note which fields match exactly and which differ. A shared phone number alone is not proof of identity, because families and roommates share numbers. The date of birth and the certification number carry more weight than a mobile number.

Check the certification issuer and the expiration date on each profile. An expired certification on one record does not mean the profile is fake, because the patient may have renewed under the other spelling. Compare the certification number digit by digit before assuming it is the same document. A transposed digit can make two records look unrelated.

Review the purchase history and the creation date on each profile. A record created years ago with steady activity is different from a record created last week by a typo. Look for duplicate loyalty entries, duplicate notes, and conflicting contact preferences. Record the differences in the merge file rather than resolving them from memory.

Verify identity with the patient present

Ask the patient to confirm the legal name and date of birth without prompting them with the screen. Read the certification number from the document and compare it to both profiles. If the patient cannot explain a difference, stop and ask a second staff member to review. A patient who is guessing is not a reliable merge authority.

Check whether either profile is linked to a caregiver or an authorized representative. A merge can break a caregiver relationship if the link lives on the record that is retired. Confirm who should retain access after the merge and note the decision. The patient should understand that access will follow the surviving record.

Do not collect a new certification or a new medical document just to complete the merge. Use the documents the store already holds and the identification the patient already provided. If the documents conflict, ask the patient which one is current and record the answer. The Virginia Cannabis Control Authority sets the licensed context, while the store's privacy policy should define who can approve a merge.

Pick the surviving record

Choose the profile with the current certification and the most complete contact details as the survivor. The surviving record should be the one the patient will use for future visits and renewals. Do not choose based on which record is older or which one the budtender opened first. Write the reason for the choice in the merge note.

Keep the retired record number in the merge note even after the profile disappears from the active list. The number is the link between the old audit trail and the new record. If the system keeps a merged-record flag, confirm that it points to the survivor. A merge that erases the old number makes later reconciliation impossible.

Check the loyalty balance and any stored preferences before the merge. Decide whether points should combine, stay with the survivor, or be frozen for review. Record the decision and the person who approved it. A silent loyalty adjustment is a common source of patient complaints after a merge.

Move history without losing the audit trail

Move only the history that belongs to the verified patient and leave unrelated notes behind. If the system cannot move individual notes, export the retired record before the merge. Store the export in the restricted records location, not in a shared drive. The export is a fallback if the merge has to be explained or reversed.

Reconcile the purchase count before and after the merge. The total number of completed sales should not change, and any difference needs an explanation. Check the date of the most recent purchase on the survivor. A merge that resets the last-visit date can distort the store's recall and outreach records.

Record the merge time, the staff member, the approver, and the system confirmation. Attach the before-image and the identity check to the same note. If the system produces a merge receipt, save it with the record. The note should let a reviewer reconstruct the decision without interviewing the counter staff.

Close the merge and tell the patient

Show the patient the surviving profile's name and contact details before they leave. Ask them to confirm that the phone number and address are correct. Explain that future visits will use the combined record and that the old profile will no longer appear. Give the patient a simple way to report a problem with the merge.

Do not discuss the retired record's contents in the waiting area. Keep the explanation focused on which profile is active and how to update contact details. If the patient asks about old purchase history, confirm that it was reviewed without reading it aloud. Privacy at the counter is part of the service, not an afterthought.

Send the merge note to the privacy or records owner at the end of the day. Flag any merge where the identity evidence was incomplete or the history could not be moved. The owner should review those cases before the next reporting cycle. A merge that is never reviewed is a data quality risk that compounds.

Review duplicate creation at intake

Count new duplicate profiles over the month and group them by intake step. Look for misspelled names, shared phone numbers, and certification numbers entered with different spacing. A pattern at one workstation may point to a form field or a search habit. The fix may be a search-before-create step rather than more training.

Test the intake search with a known duplicate before the next shift. Ask the staff member to search by date of birth and by certification number, not only by name. Confirm that the search returns the existing profile before a new one is created. Record the test result and the person who ran it.

Set a review date and assign the follow-up to the intake lead. Keep the merge log separate from the patient's clinical record and restrict access to it. Review the log at the monthly privacy meeting and close any open cases. A duplicate that is caught at intake costs minutes, while one that reaches a merge costs hours.

patient recordsduplicate profilesintake