EMPI
Enterprise Master Patient Index
An EMPI resolves whether records from different systems refer to the same person, using probabilistic matching to link identities without a shared identifier.
An Enterprise Master Patient Index (EMPI) is the system that answers a deceptively hard question: are these two records the same patient? Without a universal patient identifier in the US, the same person appears across EHRs, labs, and payers with different names, spellings, and demographics.
EMPIs use deterministic rules and probabilistic (and increasingly ML-based) matching across demographics — name, date of birth, address, and other attributes — to link records with high confidence while flagging uncertain matches for human review. Good patient matching is foundational to safety: a mismatch can attach the wrong data to the wrong person.
Identity resolution becomes especially important during data exchange and consolidation — HIE and QHIN query, payer-to-payer transfer, and EHR migrations — where records from many sources must be merged reliably.
How this relates to Health1st
Health1st's Patient Identity & Data Quality Agent performs probabilistic and ML-based patient matching, dedup/merge, and anomaly detection, so translated records attach to the right patient across systems and networks.
Related terms
FHIR is HL7's modern, web-native standard for exchanging healthcare data as modular JSON/XML resources over RESTful APIs.
A QHIN is a network designated under TEFCA to exchange health data nationwide with other QHINs on behalf of its participants.
TEFCA is the US framework that connects health data networks nationwide through a common legal and technical agreement, operationalized by QHINs.
Ready to turn months of interface work into days?
See a live HL7 v2 ↔ FHIR translation on your own message types. No obligation.
