Study guide

2.2 Master Patient Index (MPI) & Demographic Management

NHA Certified Electronic Health Records Specialist CEHRS

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the NHA CEHRS Exam The CEHRS Test Plan & How to Use This Guide

2 Chapter 1: Foundations — Medical Terminology, Health Care Settings & the EHR

1.1 Medical Terminology I: Roots, Prefixes, Suffixes & Combining Forms 1.2 Medical Terminology II: Body Systems, Directional Terms & Clinical Abbreviations 1.3 Health Care Systems, Settings, Personnel & Credentials 1.4 Parts of the EHR & Core Functions of the Electronic Record 1.5 Regulatory Agencies, Professional Standards & Population Health Concepts

3 Chapter 2: Non-Clinical Operations — Patient Registration & Scheduling

2.1 Patient Registration & Intake Workflows 2.2 Master Patient Index (MPI) & Demographic Management 2.3 Appointment Scheduling & Resource Management 2.4 Patient Communication, Portals & Front-Office Operations 2.5 Encounter Documentation: Face Sheets, Labels, Armbands & Check-Out

4 Chapter 3: Non-Clinical Operations — Health Record Administration & Archiving

3.1 Health Record Types, Hybrid Systems & Data Conversion 3.2 Record Retention, Storage & Archival Policies 3.3 Release of Information (ROI) & Authorization Procedures 3.4 Auditing, Chart Maintenance & Record Integrity

5 Chapter 4: Non-Clinical Operations — Data Sources, Devices & EHR User Support

4.1 Retrieving Patient Data from Internal Databases (Provider, Payer & Financial) 4.2 Acquiring Patient Data from External Sources 4.3 Importing from Integrated Devices & Managing EHR Hardware Inventory 4.4 Identifying, Reporting & Reconciling Data Discrepancies 4.5 End-User EHR Training, Competency & Training Documentation 4.6 Communicating Software Updates, IT Troubleshooting & Escalation

6 Chapter 5: Clinical Operations — Clinical Intake, Point-of-Care & Vitals

5.1 Clinical Intake, Rooming & Vital Signs Documentation 5.2 Chief Complaint, History of Present Illness (HPI) & ROS 5.3 Physical Exam Documentation & Clinical Notes Formatting (SOAP) 5.4 Allergy Documentation, Adverse Reaction Logging & Safety Alerts 5.5 Problem Lists, Medical History & Immunization Tracking 5.6 Patient Education Materials in the EHR & Scope of Practice

7 Chapter 6: Clinical Operations — Templates, Documentation Review & Data Retrieval

6.1 Developing Clinical Templates for Data Capture 6.2 Reviewing Clinical Documentation for Completeness & Accuracy 6.3 Point-of-Care EHR Support & Telehealth Workflows 6.4 Navigating the EHR to Retrieve Requested Patient Data 6.5 Securely Transmitting & Exchanging Patient Data

8 Chapter 7: Clinical Operations — CPOE, Orders & Decision Support

7.1 Computerized Provider Order Entry (CPOE) Fundamentals 7.2 Laboratory & Diagnostic Test Order Entry and Results Tracking 7.3 Medication Reconciliation, e-Prescribing & Formulary Checks 7.4 Clinical Decision Support Systems (CDSS) & Practice Guidelines 7.5 Clinical Care Coordination, Referrals & Discharge Planning

9 Chapter 8: Revenue Cycle & Financial Management

8.1 Insurance Verification, Eligibility (EDI 270/271) & Prior Authorization 8.2 Superbills, Charge Capture & Encounter Form Management 8.3 Coding Fundamentals for EHR: ICD-10-CM, CPT & HCPCS Level II 8.4 Claim Submission (EDI 837), Remittance (EDI 835) & Revenue Cycle 8.5 Providing Estimated Patient Costs & Good Faith Estimates 8.6 Patient Statements, Payment Collection & Balance Reconciliation

10 Chapter 9: Regulatory Compliance, HIPAA & Security

9.1 HIPAA Privacy Rule & Protected Health Information (PHI) 9.2 Minimum Necessary Rule, Permitted Uses & Patient Rights 9.3 HIPAA Security Rule: Administrative, Physical & Technical Safeguards 9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs) 9.5 Information Blocking Rules, 21st Century Cures Act & Compliance Audits 9.6 Allocating & Verifying EHR Access Controls and Role-Based Privileges 9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation 9.8 Abbreviation Policies, Professional Standards & EHR Downtime Procedures

11 Chapter 10: Data Management, Reporting & Health IT Standards

10.1 Health IT Interoperability: HL7, FHIR & Health Information Exchanges (HIE) 10.2 Standardized & Ad Hoc Financial Reports 10.3 Standardized & Ad Hoc Clinical Reports 10.4 Verifying Report Accuracy & Avoiding Common Reporting Errors 10.5 Quality Reporting, MIPS, Promoting Interoperability & Clinical Dashboards 10.6 Data Abstraction, Quality Improvement Studies & EHR System Security Management

2.2 Master Patient Index (MPI) & Demographic Management

Key Takeaways Explain This Topic AI

The Master Patient Index (MPI) is the authoritative enterprise database that assigns a unique Medical Record Number (MRN) to ensure one patient has only one record across a health system.

Deterministic matching requires exact matches across key identifiers, whereas probabilistic matching uses statistical weights to identify potential matches despite typographical errors.

Duplicate records split a patient's health history across multiple MRNs, leading to fragmented clinical data, redundant diagnostic testing, and compromised patient safety.

Overlay errors occur when one patient's demographic or clinical data is mistakenly merged into another patient's existing MRN, creating severe safety and HIPAA privacy violations.

Standard front-office protocols mandate searching by date of birth and legal last name, including checking maiden names or aliases, prior to creating any new patient record.

Last updated: August 2026

The Master Patient Index (MPI) is the cornerstone of health information management (HIM) and data integrity within any healthcare organization. The MPI is an enterprise-wide database that maintains a permanent, accurate historical record of every patient registered across a health system. By assigning a single, unique Medical Record Number (MRN) to each individual, the MPI links all clinical documentation, laboratory findings, radiological images, billing records, and administrative encounters to one distinct patient identity. When multiple facilities—such as hospitals, outpatient clinics, urgent care centers, and specialty groups—share a unified database, the system is known as an Enterprise Master Patient Index (EMPI) . For the CEHRS, maintaining MPI integrity is paramount; errors in patient identity matching can result in catastrophic clinical mistakes, compromised privacy, and severe financial losses.

Core Demographic Data Elements in the MPI

To establish a unique record and prevent identity confusion, the MPI relies on a standardized core data set. The American Health Information Management Association (AHIMA) and federal health IT standards recommend including the following primary data elements within every MPI entry:

Internal Unique Identifier : The primary Medical Record Number (MRN) automatically generated by the EHR.

Full Legal Name : Legal first name, middle name, legal last name, and any applicable suffixes (Jr., III).

Aliases and Maiden Names : Historical names, maiden names, or social aliases used for cross-referencing.

Date of Birth : Mandatory 8-digit numerical date (MM/DD/YYYY).

Social Security Number (SSN) : A key unique identifier, though fuzzy matching algorithms accommodate missing SSNs.

Gender and Biological Sex : Current biological sex at birth alongside administrative gender.

Mother's Maiden Name : Historically used as a secondary identity verification attribute.

Address and Contact Data : Primary residential address, phone numbers, and emergency contact details.

Account / Encounter Numbers : Unique episode-of-care numbers generated for specific visits, which map back to the single master MRN.

Identity Matching Algorithms: Deterministic vs. Probabilistic

EHR systems employ sophisticated algorithms during registration to compare newly entered patient data against existing MPI records to prevent duplicate creation.

Deterministic Matching : The simplest matching methodology, which requires an exact, character-for-character match across specific key fields (e.g., exact match on SSN, Date of Birth, and Last Name). While deterministic matching produces near-zero false positives, it frequently fails when minor typographical errors, hyphenated names, or missing SSNs occur, resulting in undetected duplicate records.

Probabilistic Matching : Advanced statistical algorithms that evaluate multiple demographic fields simultaneously, assigning weighted mathematical scores based on the likelihood that two records belong to the same person. Probabilistic matching handles phonetic variations (e.g., "Kathleen" vs. "Catherine"), transposed DOB digits (e.g., 04/12/1980 vs. 04/21/1980), name inversions, and missing data elements. When a match score falls within a designated threshold (e.g., 85–95% probability), the EHR alerts the CEHRS to manually review the prospective match.

Feature Deterministic Matching Probabilistic Matching

Matching Rule Requires exact match on pre-defined key data fields Calculates statistical probability score across all fields

Sensitivity to Errors High; minor typos fail to produce a match Low; accounts for misspellings, nicknames, and transposed digits

False Positive Rate Extremely low Slightly higher; requires human review for mid-score matches

Best Application High-confidence matching with verified SSN Enterprise health systems (EMPI) with diverse patient populations

Critical MPI Integrity Errors: Duplicates, Overlays, and Overlaps

Errors in demographic management create three distinct, high-risk data integrity anomalies:

Duplicate Records : Occurs when a single patient is assigned two or more distinct MRNs within the same facility (e.g., MRN 10045 and MRN 88301 both belong to John Doe). Duplicate records split the patient's medical history; a physician reviewing MRN 88301 may fail to see severe drug allergies, chronic conditions, or recent diagnostic results documented under MRN 10045.

Overlay Errors : The most dangerous MPI error, occurring when one patient's record is mistakenly overwritten or merged into another completely different patient's MRN. For example, if "Jane A. Smith" is registered under "Jane B. Smith's" MRN, Jane A.'s clinical notes, lab results, and prescriptions become mixed into Jane B.'s chart. This creates immediate clinical harm (e.g., administering wrong medication) and constitutes a major HIPAA privacy violation.

Overlap Errors : Occurs in enterprise systems when a patient has separate records created across different facilities within the same healthcare organization (e.g., Hospital A and Hospital B) that have not been linked by the EMPI.

MPI Error Type Technical Definition Clinical & Privacy Impact

Duplicate Record One patient has multiple MRNs in the same facility Fragmented history, repeated tests, uncoordinated care

Overlay Error Data for Patient A is combined into Patient B's MRN Severe patient safety hazard, wrong treatment, HIPAA breach

Overlap Error Patient records exist at different sites without EMPI link Incomplete enterprise health record during cross-site visits

Best Practices for Search, Resolution, and HIM Reconciliation

Preventing MPI errors requires strict adherence to front-office search protocols and specialized HIM reconciliation workflows:

Mandatory Pre-Registration Search : Before clicking "Create New Patient," the CEHRS must perform a comprehensive multi-parameter search. Standard protocol mandates searching by Date of Birth plus the first three letters of the legal last name .

Checking Alias and Maiden Name Fields : Searching former names, hyphenated names, or previous addresses if an initial search yields no results.

HIM Merge/Unmerge Workflows : Front-office staff should never independently merge records. When a potential duplicate or overlay is identified, it must be flagged for the Health Information Management (HIM) department. HIM specialists analyze audit trails, compare historic documents, execute formal record merges for duplicates, or conduct complex record "unmerges" to separate overlaid charts.