Action record / #187
Duplicate patient · patient 180012
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 12:00:00
- Call
- merge patient records ·
POST /Patient/$merge source=180012 target=45414 - Tier and status
- tier 2 escalated
- Definition
- duplicate patient v1
- Decided by
- rules: Same name, birth date and sex, and phone match.
- 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": 39,
"dob": "2014-07-19",
"feed": "admin",
"mrn": "R17004883",
"name": "Emil Corrbury",
"other_mrn": "R9723106",
"other_patient_id": 45414,
"other_registered_at": "2023-01-28 06:15:24",
"patient_id": 180012,
"patient_ids": [
180012,
45414
],
"patients_affected": 1,
"phone_match": true,
"postcode_match": false,
"same_region": true,
"sex": "F",
"stake_note": "one patient split over two records",
"started_at": "2026-11-16T11:13:52"
}
Arguments
{
"other_patient_id": 45414,
"patient_id": 180012
}Before and after
Nothing in the world changed with this row.