Action record / #204
Duplicate patient · patient 180037
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 13:00:00
- Call
- merge patient records ·
POST /Patient/$merge source=180037 target=154435 - 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": 22,
"dob": "1984-12-16",
"feed": "admin",
"mrn": "R29890924",
"name": "Wim Fallhithe",
"other_mrn": "R2076843",
"other_patient_id": 154435,
"other_registered_at": "2016-12-24 06:08:26",
"patient_id": 180037,
"patient_ids": [
180037,
154435
],
"patients_affected": 1,
"phone_match": false,
"postcode_match": false,
"same_region": false,
"sex": "F",
"stake_note": "one patient split over two records",
"started_at": "2026-11-16T12:12:49"
}
Arguments
{
"other_patient_id": 154435,
"patient_id": 180037
}Before and after
Nothing in the world changed with this row.