SpecsModelExploreRequirements
SpecsModelExploreRequirements
Patient Merger
Responsibilities
Patient Merger
Overview
Guide
Twin streams
Links and Communications

Patient Merger

The Patient Merger consolidates duplicate EMPI records — re-pointing encounters and observations, retaining provenance and writing audit events.

Irreversible without audit

Every merge requires idempotency keys and writes a full lineage trail — compliance must reconstruct who merged whom and why.

Responsibilities

  • Invoked after matcher confirmation or steward approval.
  • Idempotent merges with rollback metadata for compliance review.
  • Emits events consumed by Audit Service.