Action record / #149
Duplicate patient · patient 180034
Needs a person: merge_patient_records is tier 2 (ask first) in the policy. Merge a newly registered duplicate record into the older one, moving its bookings across. · on-call notified (draft)
- When
- Monday 16 November 09:00:00
- Call
- merge patient records ·
POST /Patient/$merge source=180034 target=175105 - Tier and status
- tier 2 escalated
- Definition
- duplicate patient v1
- Decided by
- rules: Same name, birth date and sex; phone and postcode differ.
- Controller
- Needs a person: merge_patient_records is tier 2 (ask first) in the policy. Merge a newly registered duplicate record into the older one, moving its bookings across.
- Signed off by
- waiting for a person (see what happened next)
- Undo
- nothing to undo
Evidence the detector returned
{
"bookings_affected": 0,
"bookings_on_new_record": 0,
"clinic_id": 28,
"dob": "1993-08-24",
"feed": "admin",
"mrn": "R27419273",
"name": "Aron Craygate",
"other_mrn": "R2059209",
"other_patient_id": 175105,
"other_registered_at": "2025-09-07 18:39:01",
"patient_id": 180034,
"patient_ids": [
180034,
175105
],
"patients_affected": 1,
"phone_match": false,
"postcode_match": false,
"same_region": false,
"sex": "M",
"stake_note": "one patient split over two records",
"started_at": "2026-11-16T08:09:29"
}
Arguments
{
"other_patient_id": 175105,
"patient_id": 180034
}Before and after
Nothing in the world changed with this row.
What happened next
| # | When | Problem found | What the operator did | Tier | Status | Decided by | Note |
|---|---|---|---|---|---|---|---|
| 158 | Mon 09:22 | duplicate patient patient 180034 |
merge patient recordsPOST /Patient/$merge source=180034 target=175105 |
2 | rejected | Ines Wendmore (records lead, scripted) | different phone and postcode: namesakes, not one person [scripted staff responses (synthetic)] |