Study guide

4.6 Master Patient Index Integrity

RHIA Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: RHIA Eligibility, Application, Fees, Format, Scoring, and Retakes

1.1 RHIA Purpose and Administrator-Level Scope 1.2 HIM-Only Eligibility Routes 1.3 MyAHIMA Application, Transcripts, and the 120-Day Scheduling Window 1.4 Fees, Format, and Appointment Time 1.5 Passing Score and Score Interpretation 1.6 Retakes, Certification Maintenance, and Current Statistics

2 2023 RHIA Outline, Exam Functionality, Pretest Items, and Study Strategy

2.1 Current 2023 Outline and Why It Controls Study 2.2 Domain Weights and Study-Time Allocation 2.3 Scored Items, Pretest Items, and Answer Discipline 2.4 Navigation, Flagging, Review, and Submit Workflow 2.5 Test Center Day and No-Resource Requirement 2.6 Official Task-Based Study Strategy

3 Data and Information Governance I: Documentation Integrity and Quality Reporting

3.1 Documentation Integrity as Governance 3.2 Complete, Accurate, and Timely Records 3.3 Documentation Standards and Clarification Workflows 3.4 Clinical Data Elements for Quality Reporting 3.5 Data Quality Validation for Reporting 3.6 Governance Committees, Metrics, and Remediation

4 Data and Information Governance II: Data Dictionaries, Retention, MPI, and Policy

4.1 Data Dictionary Standardization 4.2 Documentation and Data Standards 4.3 Data Analysis to Inform Management 4.4 Policies and Procedures for Information Governance 4.5 Retention and Destruction Policies 4.6 Master Patient Index Integrity

5 Compliance I: Access, Use, Disclosure, Patient Rights, ROI, and HIE

5.1 Domain 2 Compliance Decision Frame 5.2 Patient Access and Portal Governance 5.3 Advocacy for Patients and Families 5.4 ROI Intake, Validation, and Scope Control 5.5 Disclosure Documentation and Audit Trails 5.6 HIE and External Access Governance

6 Compliance II: Security, Breach Workflows, Cybersecurity, and Disaster Recovery

6.1 Request Workflow Controls and Escalation 6.2 Breach Protocols from Report to Resolution 6.3 Privacy and Security Initiatives 6.4 Cybersecurity Risks for HIM Leaders 6.5 Disaster Recovery and Downtime Readiness 6.6 Monitoring, Metrics, Tabletops, and Continuous Improvement

7 Data Analytics and Informatics I: EHR Support, Reporting, Databases, and Dashboards

7.1 EHR Support and HIM Administration 7.2 Reporting Lifecycle and Data Requests 7.3 Visualizations, Dashboards, and Executive Views 7.4 Database Management and Data Dictionaries 7.5 Data Mining and Analytics Workflows 7.6 Statistics Validation for Stakeholders

8 Data Analytics and Informatics II: CDI, Workflows, HIE, Integrations, and SDLC

8.1 Focused Documentation Audits for CDI, Quality, and Safety 8.2 CDI Workflows and Query Governance 8.3 Workflow Optimization Through Health Information Technology 8.4 HIE Governance and Exchange Controls 8.5 Software Integrations and Health Information Impact 8.6 Systems Development Life Cycle and HIM Participation

9 Revenue Cycle Management I: Reimbursement, Coding Validation, CDI, and Claims

9.1 Domain 4 Revenue Cycle Management Frame 9.2 Reimbursement Models and Provider Education 9.3 Coding Accuracy Validation Controls 9.4 HHS Documentation Requirements and CDI 9.5 Claims Workflow and Clean-Claim Controls 9.6 CDM, DNFB, and A/R Management

10 Revenue Cycle Management II: Revenue Integrity, Denials, Fraud, and Official Guidelines

10.1 Official Guidelines and Code Assignment 10.2 Groupings and Payment Data Validation 10.3 Revenue Integrity Program Design 10.4 Coding Audits, Monitoring, and Corrective Action 10.5 Denials Management and Appeals 10.6 Fraud Prevention and Compliance Escalation

11 Management and Leadership: Strategy, HR, Work Design, Training, Budgeting, and Projects

Strategy, Goals, and Change Management Contracting and Outsourcing Governance Human Resources, Staffing, and Performance Work Design and Process Improvement Training and Development Budgets, Accreditation, Compliance, and Projects

12 Final RHIA Review: Domain Integration, Exam Week, and Career Next Steps

Integrated Scenario Patterns Across Domains Final Week Domain-Weighted Review Test-Center Day, Functionality, and Pacing Results, Retakes, and RHIA Maintenance RHIA, RHIT, CHDA, CHPS, and CCS Career Map Readiness Checklist and Next-Step Plan

4.6 Master Patient Index Integrity

Key Takeaways Explain This Topic AI

AHIMA's Domain 1 includes Master Patient Index integrity as a Data and Information Governance task.

MPI integrity supports correct patient identification, record linking, care continuity, reporting reliability, and patient safety.

Common integrity risks include duplicates, overlays, overlaps, demographic errors, weak registration practices, and interface mismatches.

The RHIA-level response combines prevention, detection, correction, monitoring, staff training, and clear governance ownership.

Last updated: June 2026

The MPI is a patient-identity control

The AHIMA RHIA Domain 1, Data and Information Governance, includes Master Patient Index integrity. A Master Patient Index (MPI) is the system or database that links patient-identity information to the correct records and encounters within a facility. An Enterprise Master Patient Index (EMPI) extends that linkage across multiple facilities or systems. Integrity means the index accurately represents the right patient, the right identifiers, and the right linked records, the foundation for every other use of health information.

MPI problems are high risk because identity errors propagate. A duplicate splits one patient's history across more than one record number in the same system. An overlay merges information from two different patients under one identifier, the most dangerous error. An overlap occurs when the same patient has different identifiers across facilities or systems that are not properly linked. Demographic errors weaken matching and cascade into registration, reporting, access, and safety problems.

  • MPI issue Meaning Governance response
  • Duplicate One patient has more than one record in the same system Merge only after verification per policy

Overlay More than one patient is combined under one identifier Urgently separate records and notify affected workflows

Overlap Same patient has different identifiers across systems Resolve through enterprise identity-matching rules

Demographic error Name, date of birth, address, or other data is wrong Correct source data and reinforce registration standards

Interface mismatch Systems send or receive inconsistent identifiers Review mapping, matching logic, and error queues

Unworked potential match A possible duplicate is not resolved Prioritize by risk and aging with trained-staff review

Industry benchmarks help frame targets: AHIMA has long cited a goal of keeping the duplicate record rate at or below about 2% , while many unmanaged systems run far higher. Even small percentages translate to thousands of affected records in a large system.

Prevention is better than cleanup

MPI integrity starts at registration and scheduling. Staff should search before creating a new record, collect standardized demographics, verify identity per policy, avoid unapproved nicknames or abbreviations, and know when to escalate an uncertain match. System tools help, matching algorithms (deterministic and probabilistic), duplicate alerts, required fields, and work queues, but they do not replace training and governance.

A classic exam pattern is a duplicate spike after a new clinic opens, a system conversion, or a workflow change. The best answer is not merely to merge faster. The RHIA examines root cause: Are staff skipping the search step? Are required demographic fields missing? Did an interface begin sending values in a new format? Are matching thresholds too strict or too loose? Did training miss name variation or special populations such as newborns and twins?

Correction must be controlled

Merging or separating records affects care, release of information, billing, patient portals, quality reporting, and analytics. MPI correction must follow approved procedures, use trained staff, require verification evidence, preserve audit trails, and notify downstream areas. An overlay is urgent because one patient's data sits inside another patient's record, a direct patient-safety and privacy hazard; the organization must correct the identity link and assess every downstream effect, including potential HIPAA breach reporting.

Key MPI governance metrics:

Duplicate creation rate by registration point or location.

Potential-duplicate queue volume and aging.

Overlay incidents and time to resolution.

Percentage of records missing key demographic fields.

Match accuracy after a system change or conversion.

Staff compliance with search and verification procedures.

Downstream report or portal issues caused by identity errors.

RHIA exam reasoning

When an MPI scenario appears, classify it as prevention, detection, or correction. For a potential-duplicate queue, prioritize review by patient-safety and data-use risk and by aging. For an overlay, treat it as urgent because records from different patients are mixed. If a trend points to registration workflow, fix training and process at the source. If a system change causes mismatches, involve informatics and the interface owners. Above all, never merge unverified matches, an incorrect merge can create the very overlay you are trying to prevent.

MPI integrity underpins documentation integrity, quality reporting, patient access, analytics, and management reporting.

Matching algorithms and why thresholds matter

MPI tools match records using two main approaches. Deterministic matching requires exact agreement on chosen fields (for example, name plus date of birth plus Social Security number). It is precise but brittle: a single typo or a missing field breaks the match and creates a duplicate. Probabilistic matching scores the likelihood that two records belong to the same person by weighting many fields, tolerating minor variation such as nicknames or transposed digits. Probabilistic matching catches more true matches but can produce false matches if thresholds are set too loose.

The RHIA governance role is to tune thresholds and route uncertain scores to a human-reviewed work queue, never to auto-merge a borderline pair.

A worked MPI scenario

A system has 500,000 active records and a measured duplicate rate of 4%, roughly 20,000 duplicate records, twice AHIMA's target of about 2% or below. After a registration-workflow change, the monthly duplicate creation rate doubles.

The wrong answer is "merge faster." The RHIA response is layered: analyze where new duplicates originate (a report shows 80% come from one registration desk that skips the search step), reinforce the search-before-create procedure and retrain that staff, tighten required demographic fields, route potential matches to a verified queue, correct existing duplicates only after evidence-based verification, preserve audit trails on every merge, and track the duplicate creation rate weekly to confirm the trend reverses.

Because an incorrect merge fuses two patients into one record, an overlay, every correction must be evidence-based and auditable. Patient safety, privacy, billing accuracy, portal access, and quality reporting all hinge on the identity link being right, which is why MPI integrity is a foundational Data and Information Governance responsibility rather than a clerical task.