SpecsModelExplore
Overview
Actors
External Systems
Clinical Data Product
Clinical Ingestion
Clinical Data
Patient Master
Patient RepositoryPatient MatcherPatient Merger
Encounter Service
Observation Service
Analytics & Research
Clinical Apps
Governance & Audit
Patient Master
Internal structure
Components
How it is used
Create or link
Merge duplicates
API
Admission ingestion
SpecsModelExplore
Patient Master
OverviewGuidePatient Master APILinks and Communications

Patient Master

The Patient Master is the EMPI — enterprise master patient index. It answers the question every downstream service asks: who is this patient, are they already known, and are there duplicates?

Why a single index

Hospitals send overlapping MRNs and demographics. Without an EMPI, the same person becomes two patients and clinical safety breaks down.

Internal structure

Could not build diagram for model "example-healthcare".

Components

Patient Repository

Stores patient demographics and identifiers.

Patient Matcher

Matches incoming records to existing patients.

Patient Merger

Merges duplicate patient records.

How it is used

Match on ingest

The Patient Matcher scores incoming demographics against existing records.

Create or link

New patients persist in the Patient Repository; probable matches link instead of duplicating.

Merge duplicates

The Patient Merger consolidates confirmed duplicates with full audit trail.

API

The EMPI exposes REST endpoints for lookup, create and merge operations used by ingestion and FHIR. The contract is on the Overview tab.

Contract

Merge operations require an idempotency key so retried ADT messages do not double-merge.

Admission ingestion