Action record / #181
Duplicate patient · patient 180010
same person, confirmed on the phone or address [scripted staff responses (synthetic)]
- When
- Monday 16 November 11:25:00
- Call
- merge patient records ·
POST /Patient/$merge source=180010 target=84265 - Tier and status
- tier 2 approved
- 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
- Ines Wendmore (records lead, scripted)
- Undo
undo_merge_patient_recordsrestores the before-snapshot below
Evidence the detector returned
{
"bookings_affected": 0,
"bookings_on_new_record": 0,
"clinic_id": 3,
"dob": "1985-08-25",
"feed": "admin",
"mrn": "R10580454",
"name": "Gil Brackhithe",
"other_mrn": "R3172801",
"other_patient_id": 84265,
"other_registered_at": "2024-04-03 04:16:29",
"patient_id": 180010,
"patient_ids": [
180010,
84265
],
"patients_affected": 1,
"phone_match": true,
"postcode_match": false,
"same_region": true,
"sex": "M",
"stake_note": "one patient split over two records",
"started_at": "2026-11-16T10:31:28"
}
Arguments
{
"other_patient_id": 84265,
"patient_id": 180010
}Before and after
{
"after": {
"appointments": [],
"patients": [
{
"id": 180010,
"merged_at": "2026-11-16T11:25:00",
"merged_into": 84265
}
]
},
"before": {
"appointments": [],
"patients": [
{
"id": 180010,
"merged_at": null,
"merged_into": null
}
]
}
}