4.6 Master Patient Index Integrity
Key Takeaways
- AHIMA's current 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 governance ownership.
The MPI is a patient identity control
The current AHIMA RHIA Domain 1 includes Master Patient Index integrity. A Master Patient Index, often shortened to MPI, is the system or database that links patient identity information to the correct records and encounters. In an enterprise environment, a related enterprise MPI may help connect identity across multiple facilities or systems. Integrity means the index accurately represents the right patient, the right identifiers, and the right linked records.
MPI problems are high risk because identity errors spread. A duplicate record can split a patient's history across more than one identifier. An overlay can combine information from two different patients into one record. An overlap can occur when the same patient has different identifiers across facilities or systems that are not properly linked. Demographic errors can weaken matching and cause 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 according to 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 | Possible duplicate is not resolved | Prioritize by risk and aging with trained staff review |
Prevention is better than cleanup
MPI integrity starts at registration and scheduling. Staff should search before creating a new record, use standardized demographic collection practices, verify identity according to policy, avoid unapproved abbreviations or nicknames, and understand when to escalate uncertain matches. System tools can help with matching algorithms, duplicate alerts, required fields, and work queues, but tools do not replace training and governance.
A common exam pattern is a duplicate spike after a new clinic opens, a system conversion, or a workflow change. The best answer is not only to merge records faster. The RHIA manager should examine root cause: Are staff skipping search steps? 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 fail to cover special populations or name variation?
Correction must be controlled
Merging or separating records can affect care, release of information, billing, patient portals, quality reporting, and analytics. That is why MPI correction should follow approved procedures, use trained staff, require verification evidence, preserve audit trails, and notify downstream areas when needed. An overlay is especially urgent because one patient's information may appear in another patient's record. The organization must correct the identity link and assess downstream effects.
MPI governance metrics include:
- Duplicate creation rate by registration point or location.
- Potential duplicate queue volume and aging.
- Overlay incidents and time to resolution.
- Percentage of records with missing key demographic fields.
- Match accuracy after system changes or conversions.
- Staff compliance with search and verification procedures.
- Downstream report or portal issues caused by identity errors.
RHIA exam reasoning
When an MPI scenario appears, identify whether the issue is prevention, detection, or correction. If the risk is a potential duplicate queue, prioritize review based on patient safety and data use. If the risk is an overlay, treat it as urgent because records from different patients may be mixed. If a trend points to registration workflow, fix training and process at the source. If a system change causes mismatches, involve informatics and interface owners.
MPI integrity is a foundation for every other use of health information. Documentation integrity, quality reporting, patient access, analytics, and management reporting all depend on the correct patient identity link.
One patient has two separate medical record numbers in the same system. What MPI issue is most likely?
Why is an overlay usually more urgent than an ordinary potential duplicate?
A new registration workflow causes duplicate rates to rise. What is the best RHIA-level action?