Resolve duplicate records, and record the ones that are not

Featurekamo-internal
Shipped
August 26, 2026 at 4:47 PM UTC
Author
kamo
Commit
be11efe

Registration prevents duplicates; nothing could fix the ones already there — from an import, a phone booking taken before the record was found, a married name. The merge and not-a-match endpoints had no caller at all. THE DIRECTION IS NAMED IN FULL. Both merges are offered as separate buttons saying who survives and who becomes a pointer, and the confirm repeats it: "merge A into B" is ambiguous on a screen showing both, and merging the wrong way round buries the chart that had the history in it. "DIFFERENT PEOPLE" IS THE HALF THAT GETS SKIPPED. Twins, a parent and child sharing a name, a father and son — these are offered as duplicates on every registration and every review until somebody records otherwise, and a pair re-examined forever is a pair somebody eventually merges by mistake. The prompt says what recording it achieves so it does not read as bookkeeping. Gated on MERGE_PATIENT_RECORDS, which is deliberately not implied by being able to register: merging is the most damaging thing this module does, and the right exists so a practice can hold it to a much shorter list than "the front desk".

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing