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 Repository
Data model
Notes
SpecsModelExplore
Patient Repository
OverviewGuideSchemaLinks and Communications

Patient Repository

The Patient Repository persists demographics, identifiers and merge lineage for each EMPI record. It is the durable source for FHIR Patient reads.

Storage profile

PostgreSQL with row-level encryption for identifier columns; retention follows HIPAA policy.

Data model

The schema is small and audit-oriented. The ERD is embedded on the Overview tab.

Notes

  • PATIENT.id is the internal EMPI key; external MRNs live in IDENTIFIER rows with assigning authority.
  • Merge operations retain MERGE_HISTORY so compliance can reconstruct lineage.
  • Exactly one golden record survives a merge; source ids are tombstoned, not deleted.