SpecsModelExploreRequirements
SpecsModelExploreRequirements
Patient Merger
Overview
Guide
Twin streams
Links and Communications
IDproduct.clinical_data.patient_master.merger
DescriptionMerges duplicate patient records.
Keymerger
Typecomponent
Statusactive
TeamClinical Data
Tags
Table of contents
Guide
Patient Merger
Responsibilities
Links and Communications
Requirements

Attributes

auditfull lineage
idempotencyrequired

Guide

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.

Links and Communications

1 outgoing link

Outgoing Links(1)

Target objectLabelLink typeRelationRaw idRequiredDescription
Patient Matcher

example-healthcare.product.clinical_data.patient_master.matcher

component
——linksproduct.clinical_data.patient_master.matcher——

Requirements