Action record / #174
Duplicate patient · patient 180009
same person, confirmed on the phone or address [scripted staff responses (synthetic)]
- When
- Monday 16 November 10:47:00
- Call
- merge patient records ·
POST /Patient/$merge source=180009 target=135149 - Tier and status
- tier 2 approved
- Definition
- duplicate patient v1
- Decided by
- rules: Same name, birth date and sex, and phone and postcode 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": 31,
"dob": "2003-02-13",
"feed": "admin",
"mrn": "R16761094",
"name": "Greta Pellmore",
"other_mrn": "R7395824",
"other_patient_id": 135149,
"other_registered_at": "2024-03-27 01:21:37",
"patient_id": 180009,
"patient_ids": [
180009,
135149
],
"patients_affected": 1,
"phone_match": true,
"postcode_match": true,
"same_region": true,
"sex": "F",
"stake_note": "one patient split over two records",
"started_at": "2026-11-16T09:59:54"
}
Arguments
{
"other_patient_id": 135149,
"patient_id": 180009
}Before and after
{
"after": {
"appointments": [],
"patients": [
{
"id": 180009,
"merged_at": "2026-11-16T10:47:00",
"merged_into": 135149
}
]
},
"before": {
"appointments": [],
"patients": [
{
"id": 180009,
"merged_at": null,
"merged_into": null
}
]
}
}