Handle repeated patient intake submissions without losing updates

A patient may submit an intake form twice because the confirmation did not appear, or send a second version to correct a detail. The clinic needs to distinguish those situations without discarding useful information. This guide covers administrative handling of repeated submissions, with staff responsible for resolving uncertain matches.

Distinguish an exact repeat from an amendment

Describe examples before choosing a matching rule. In a fictional clinic, Taylor submits a form again after a browser timeout, then sends another version with a corrected contact number. The first repeat may require no additional administrative action; the correction still needs attention. A matching name or email address alone does not establish that submissions are identical or belong to the same person. Define which source reference identifies a submission and how later changes remain visible to staff.

Preserve the original and subsequent versions

Keep enough source history for an authorised reviewer to understand what arrived and when. Show changed fields alongside the original rather than silently replacing the first submission. Follow the clinic’s approved storage and retention arrangements; retaining a processing history does not mean copying every sensitive field into general logs. Give each submission a reference that can be used in an exception task. Staff should be able to trace an amendment without searching unrelated patient records or relying on a filename.

Separate submission handling from record merging

Suppressing an exact repeated intake event is different from merging two patient records. The latter can affect existing information and should not be an automatic consequence of a similarity score. Ask clinic staff to define the approved identity-checking and correction process. If a potential match is uncertain, hold the administrative update for review and explain why. Keep both the source references and any destination reference available. The automation should not decide which clinical history is correct or remove a record to tidy a queue.

Check the outcome of interrupted writes

A connection can time out after the destination has accepted an intake item. Before replaying the request, check whether that original item already exists using the integration’s supported identifiers. Verify what the actual connector can do; do not assume a duplicate-prevention feature is available. Where the outcome cannot be established, route the item to staff as uncertain rather than failed. An additional confirmation message can also be a duplicate, so review notifications as well as record creation.

Give staff a clear review action

Show the reason for the possible match, the relevant differences and any action already completed. Let authorised staff mark an exact repeat, accept a correction through the approved process or keep separate requests distinct. Record the decision without implying that administrative review validates clinical content. If a submission contains information requiring another clinic process, route it according to the clinic’s instructions. Avoid a single button that both clears the alert and makes an unexplained record change.

Test repeats and legitimate new work

Use fictional test records to submit an exact repeat, simultaneous copies, an amended version and two distinct people with similar details. Interrupt a response after a test write and check recovery. Inspect the destination and messages produced, including whether a legitimate amendment remains available. Confirm that closing a duplicate alert does not delete the original evidence. Agree who reviews unresolved matches during ordinary operations and when the matching rules should be reconsidered after staff feedback.