SpecsModelExploreRequirements
SpecsModelExploreRequirements
Patient Repository
Overview
Guide
Schema
Twin streams
Links and Communications
IDproduct.clinical_data.patient_master.patient_repo
DescriptionStores patient demographics and identifiers.
Keypatient_repo
Typecomponent:database
Statusactive
TeamClinical Data
Tags
Table of contents
Guide
Patient Repository
Data model
Notes
Schema
Links and Communications
Requirements

Attributes

encryptioncolumn-level
retention7y
storePostgreSQL

Guide

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.

Schema

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
100%

Links and Communications

1 incoming link

Incoming Links(1)

Source objectLabelLink typeRelationRaw idRequiredDescription
Patient Matcher

example-healthcare.product.clinical_data.patient_master.matcher

component
——linksproduct.clinical_data.patient_master.patient_repo——

Requirements