Patient Intake Research
Measuring Duplicate Patient Profile Merge Time at Intake
A study protocol for measuring how long a dispensary takes to resolve two patient profiles that share a phone number, with separate intervals for identity verification, system merge, history reconciliation, and patient confirmation.
Key takeaways
- Define merge time from duplicate detection to a patient-confirmed surviving record.
- Measure identity verification, system merge, history reconciliation, and patient confirmation as separate intervals.
- Report failed or deferred merges beside the median so a fast system merge is not mistaken for a clean record.
- Keep the before-image, identity evidence, and merge note together for the review.
Question and scope
This study asks how long a dispensary takes to resolve two patient profiles that appear to belong to the same person. The unit is one duplicate pair tied to one intake visit and one surviving record. The review separates the detection, the identity check, the system merge, the history reconciliation, and the patient confirmation. It does not judge whether the patient should have been in the store's records at all.
Set the scope to one store and a fixed observation window. Record the record system, the intake form, the identity documents the store accepts, and the merge permission model. If the store changes systems during the window, separate the periods. A system change can alter both the duplicate rate and the merge path.
Include pairs caught at the counter, pairs found during a records audit, and pairs reported by the patient. A study that looks only at counter catches will understate the backlog. Record the disposition for every pair, including the pairs that were left open. The disposition mix is part of the result.
What the sources establish
The HHS Office for Civil Rights publishes health-information privacy guidance that shapes how patient records and merge logs are handled. The Virginia Cannabis Control Authority sets the licensed retail context in which the patient record exists. The National Institute of Standards and Technology publishes identity and access guidance that frames how identity evidence should be checked. These sources frame the operating conditions, not a required merge time.
The sources do not establish a maximum merge time or a required duplicate-resolution procedure. They also do not say whether a phone number is sufficient evidence of identity. The study therefore measures the store's own policy and its record system against what actually happened. The report should keep that local scope visible.
The sources support separating an identity delay from a system delay. A store that waits a day for the patient to bring identification has created an identity delay, while a system that takes an hour to rebuild a history index has created a system delay. The study should report both. The fix for one is a counter script, and the fix for the other is a vendor ticket.
Definitions and measures
Define detection as the moment a staff member notices that two profiles may describe the same person. Define identity verification as the moment the required evidence is reviewed and accepted. Define system merge as the moment the record system confirms the merge. Define resolution as the moment the patient confirms the surviving record.
Measure detection, identity verification, system merge, history reconciliation, and patient confirmation separately. Report the total merge time as the interval from detection to patient confirmation, but keep the components visible. A fast system merge followed by a slow history review is a different problem from a slow identity check followed by a fast merge. The components point to different fixes.
Record the profile numbers, the matching fields, the differing fields, and the evidence used. Note whether the pair shared a phone number, an address, a certification number, or only a name. Report the number of staff members who touched the case and the approval role. The study should not infer a merge from a record that merely stopped appearing.
Sampling and collection
Sample duplicate pairs from the intake log, the records audit, and the patient complaint log. Match each pair to an intake visit and a surviving record, and note any that cannot be matched. Record the record system, the intake form, and the staff role. The match is the foundation of a defensible merge-time measure.
Collect the before-image, the identity evidence, the merge note, and the patient confirmation. If the store cannot produce the before-image, record that gap as a finding. A merge that cannot be reconstructed is a record problem in addition to a privacy problem. The study should not rely on the surviving record alone.
Observe at least one duplicate review at the counter during the window. Record the search steps, the fields compared, and the point at which the patient is told what will happen. The observation shows whether the written routine matches the actual practice. A routine that looks clear on paper may be shortened when the line is long.
Verification pathway
Confirm the merge with the record system's audit log, not with a staff note. A note that says "merged" is not proof that the history moved to the survivor. Record the evidence type and the time it was captured. The study should distinguish a requested merge from a completed one.
Check the purchase count and the loyalty balance before and after the merge. The total number of completed sales should not change, and any difference needs an explanation. Record any adjustment and the person who approved it. The duplicate-profile counter routine describes the sequence that should feed this record.
Review the patient confirmation for accuracy and timing. The confirmation should show the surviving record's name and contact details without exposing the retired record. Record whether the patient received the confirmation before leaving. A confirmation that arrives after a failed pickup is too late to be useful.
Operational side effects
Measure the minutes the intake staff member spent away from the counter during the review. Record who covered the line and whether a private area was used. A duplicate review is not free even when the pair is small. The study should show the labor cost beside the record count.
Check whether the merge delayed a checkout, a certification check, or a prescription update. A pending merge can make the active record look incomplete at the register. Record the delay and the person who resolved it. The study should connect the merge to the patient's visit, not only to the database.
Review the effect on the patient's wait time and on the privacy of the conversation. A merge discussed at an open counter may expose information to the line. Record whether a private space was available and used. The study should not compare a quiet-hour case with a peak-hour case without noting the difference.
Analysis and reporting
Report the number of duplicate pairs, the median merge time, and the slowest case. Break the results down by detection point, matching field, and staff role. Report the identity time and the system time beside the total. A single average hides the difference between a fast merge and a slow history review.
Inspect the failures for patterns. A cluster of pairs sharing a phone number may point to an intake form that does not require a second identifier, while a cluster from one system may point to a search defect. Choose one change, such as a search-before-create step or a second identifier field. Do not rank staff by merge time when their systems or document checks differ.
Report the pairs that were still open at the review date separately. An open merge is not a zero-minute resolution, and treating it as one understates the backlog. Show the age of each open case and the owner. The report should make the unresolved records visible.
Keep the results in one page that the intake lead reviews monthly. Show the pair count, the median, the slowest case, the deferred merges, and the open backlog. The page should be short enough to discuss in a ten-minute meeting. A long report with no decision is not a useful study.
Limits and next action
The study cannot prove that a faster merge would prevent every duplicate or that every pair was recorded. It also cannot capture a duplicate that was corrected before anyone logged it. A missing pair is a limitation, not a zero. The report should state how many pairs were excluded and why.
Set a repeat review date and keep the definitions stable. Assign the correction to the intake lead and give the counter a clear identity check. The next review should test whether the same form or the same system fails again. A useful result is a merge routine that the store can explain and complete without a second visit.
Record the date the store last walked through its duplicate review with the people who actually work the intake desk. A routine that works for the manager may fail for the weekend crew. Add the walkthrough to the quarterly privacy review. The next study should use the current record system and the current document list.
Sources
The sources below support the privacy, identity, and retail context for this review. They do not measure this store, and no source is presented as a local benchmark. Check each link for its date and scope before reuse. The operational finding comes only from the intake and record-system evidence described in the method.
This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation.
Reviewed by the DispensaryVA editorial team on 2026-11-18.