A master patient index (MPI) and an electronic health record (EHR) solve different problems. An MPI helps an organization identify and match a person to the correct patient records. An EHR stores and presents clinical information and supports care workflows. Reliable identification is foundational to using the right record, but an MPI is not itself a complete clinical chart.
What is a master patient index?
An MPI is an index of patient identities and identifiers used by an organization or network to locate and link records. Implementations may use demographic attributes and local identifiers to help determine whether records refer to the same person. A master index may be organization-wide or enterprise-wide, depending on the system and context.
What does an EHR do?
An EHR supports electronic documentation and access to patient health information across care workflows. Depending on the system, it may include encounter notes, diagnoses, medications, orders, results, scheduling, and other functions. A single EHR may include patient-identification features, but the record system and the identity-matching function remain conceptually distinct.
MPI vs. EHR at a glance
| Question | MPI | EHR |
|---|---|---|
| Primary purpose | Identify and link records that belong to the same patient | Document and support clinical and related workflows |
| Typical information | Demographic identifiers and record numbers used for matching | Clinical and administrative information associated with care |
| Main risk if inaccurate | Duplicate records or information linked to the wrong identity | Incomplete, incorrect, or hard-to-use documentation and workflow data |
| Relationship | Can help locate the right record across systems or departments | May use identity data and may connect to an MPI or exchange service |
Why patient matching matters
If a person’s information is split across duplicate records, clinicians may not see a complete history. If records are incorrectly combined, information can be attributed to the wrong person. Matching is therefore a safety and data-quality concern, not merely a database housekeeping task.
Matching processes can use names, dates of birth, addresses, phone numbers, and other attributes. These details can change or be entered inconsistently. Organizations need policies for potential matches, manual review, duplicate resolution, and correction, especially when the system is uncertain. Avoid automatically merging records based only on a single similar field.
