RoundsCorrowmere Clinics · Estmark synthetic data · seed 23

Duplicate patient · patient 180001

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
Tuesday 10 November 11:00:00
Call
merge patient records · POST /Patient/$merge source=180001 target=66345
Tier and status
tier 2 escalated
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
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": 29,
  "dob": "1990-02-05",
  "feed": "admin",
  "mrn": "R19428256",
  "name": "Rosa Quarrmere",
  "other_mrn": "R9696950",
  "other_patient_id": 66345,
  "other_registered_at": "2022-10-03 12:03:10",
  "patient_id": 180001,
  "patient_ids": [
    180001,
    66345
  ],
  "patients_affected": 1,
  "phone_match": true,
  "postcode_match": true,
  "same_region": true,
  "sex": "M",
  "stake_note": "one patient split over two records",
  "started_at": "2026-11-10T10:33:55"
}

Arguments

{
  "other_patient_id": 66345,
  "patient_id": 180001
}

Before and after

Nothing in the world changed with this row.

What happened next

#WhenProblem foundWhat the operator didTierStatusDecided byNote
10Tue 12:15 duplicate patient
patient 180001
merge patient records
POST /Patient/$merge source=180001 target=66345
2approved Ines Wendmore (records lead, scripted)same person, confirmed on the phone or address [scripted staff responses (synthetic)]