Action record / #101
Duplicate patient · patient 180033
different phone and postcode: namesakes, not one person [scripted staff responses (synthetic)]
- When
- Friday 13 November 16:50:00
- Call
- merge patient records ·
POST /Patient/$merge source=180033 target=91517 - Tier and status
- tier 2 rejected
- 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
- Ines Wendmore (records lead, scripted)
- Undo
- nothing to undo
Evidence the detector returned
{
"bookings_affected": 0,
"bookings_on_new_record": 0,
"clinic_id": 1,
"dob": "1942-11-19",
"feed": "admin",
"mrn": "R22340090",
"name": "Olaf Wendings",
"other_mrn": "R9116423",
"other_patient_id": 91517,
"other_registered_at": "2019-08-05 05:38:29",
"patient_id": 180033,
"patient_ids": [
180033,
91517
],
"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-13T15:15:48"
}
Arguments
{
"other_patient_id": 91517,
"patient_id": 180033
}Before and after
Nothing in the world changed with this row.