RoundsCorrowmere Clinics · Estmark synthetic data · seed 23

Duplicate patient · patient 180006

same person, confirmed on the phone or address [scripted staff responses (synthetic)]

When
Friday 13 November 14:25:00
Call
merge patient records · POST /Patient/$merge source=180006 target=36915
Tier and status
tier 2 approved
Definition
duplicate patient v1
Decided by
rules: Same name, birth date and sex, 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_records restores the before-snapshot below

Evidence the detector returned

{
  "bookings_affected": 0,
  "bookings_on_new_record": 0,
  "clinic_id": 26,
  "dob": "1969-01-18",
  "feed": "admin",
  "mrn": "R16958764",
  "name": "Amir Pellcombe",
  "other_mrn": "R5032849",
  "other_patient_id": 36915,
  "other_registered_at": "2023-12-27 07:59:42",
  "patient_id": 180006,
  "patient_ids": [
    180006,
    36915
  ],
  "patients_affected": 1,
  "phone_match": false,
  "postcode_match": true,
  "same_region": true,
  "sex": "F",
  "stake_note": "one patient split over two records",
  "started_at": "2026-11-13T13:18:20"
}

Arguments

{
  "other_patient_id": 36915,
  "patient_id": 180006
}

Before and after

{
  "after": {
    "appointments": [],
    "patients": [
      {
        "id": 180006,
        "merged_at": "2026-11-13T14:25:00",
        "merged_into": 36915
      }
    ]
  },
  "before": {
    "appointments": [],
    "patients": [
      {
        "id": 180006,
        "merged_at": null,
        "merged_into": null
      }
    ]
  }
}