Study guide

MPI and Patient Identity

CCA Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation, Eligibility, and Exam Strategy

Official Sources, Credential Purpose, and Candidate Profile Eligibility and Recommended Preparation Exam Format, Scoring, Pass Rates, Fees, Retake, Refund, and Delivery Code-Book Rules After 2026-05-01 Navigation and Timing Strategy Under Current AHIMA Instructions 8-14 Week Study Plan

2 Code Books, Guidelines, and Coding Workflow

2026 Code-Book Readiness and Allowed-Resource Mindset Coding Workflow: Read, Abstract, Locate, Assign, Sequence, Validate Medical Terminology, Anatomy, and Pathophysiology Foundation Coding Conventions and Official Guideline Use Query and Documentation Clarification Boundary Error-Log Method for Coding Misses

3 Clinical Classification Systems: ICD-10-CM

ICD-10-CM Structure and Conventions Diagnosis Coding from Documentation Principal/First-Listed Diagnosis and Sequencing by Setting Laterality, Episode/Seventh Character, and Combination Codes Signs/Symptoms vs Confirmed Diagnoses Common Exam Traps and Documentation Support

4 CPT, HCPCS, E/M, Modifiers, and Physician Coding

CPT Structure and Category Logic HCPCS Level II Basics E/M Level Components: History, Exam, MDM, and Time Modifiers, Bundling, Unbundling, and NCCI Edits Physician and Outpatient Coding Scenarios Medical Necessity and Payer Guideline Awareness

5 Inpatient Coding, ICD-10-PCS, and Setting-Based Sequencing

Inpatient Guidelines and UHDDS Concepts ICD-10-PCS Root Operation Thinking Procedure Coding from Operative Documentation Setting-Based Sequencing Differences Abstracting from the Inpatient Record DRG Impact without Upcoding

6 Reimbursement Methodologies and Revenue Cycle

Revenue Cycle Overview for Coders DRG, APC, Fee Schedule, RBRVS, and Risk Adjustment Claim Forms, Charge Capture, and Financial Communication NCCI Edits, LCD/NCD, and Medical Necessity Denials Evaluation and Processing Ethical Payer and Physician Clarification Workflow

7 Health Records, Data Content, and Information Governance

Medical Record Components Quantitative and Qualitative Record Analysis Abstraction and Retrieval Workflows MPI and Patient Identity Data Standards, Vocabularies, and Coding Reports Provider Education on Health Data Standards

8 Compliance, Ethics, Audits, and Clinical Documentation Improvement

Documentation Support and Code Validation Ethical Coding and AHIMA Code-of-Ethics Mindset Physician Queries and CDI Boundaries Fee/Charge Ticket and Chargemaster Updates External Audits and Compliance Preparation Fraud/Abuse Risk and Unsafe Shortcut Patterns

9 Information Technologies, Encoders, CAC, and EHR Workflows

EHR Navigation Encoders, Groupers, and HIM Systems Practice Management Systems CAC Strengths and Validation Limits Data Quality, Interoperability, and Workflow Errors Technology-Related Exam Traps

10 Confidentiality, Privacy, Security, and Minimum Necessary

HIPAA and State Privacy Basics for Exam Scenarios Minimum Necessary Access Passcodes, Passwords, and Secure Work Environment Recognizing and Reporting Privacy Violations Staff Education on Confidentiality ROI and Disclosure Decision Boundaries

11 Integrated CCA Domain Review and Practice Strategy

Blueprint-Weighted Mixed Review Linking Clinical Classification to Reimbursement and Compliance High-Probability Distractors Timed 105-Question Simulation Strategy Codebook Speed Drills and Scenario Triage Final Weak-Domain Remediation

12 Exam Day, Results, Retakes, Recertification, and Career Next Steps

Final 30/14/7 Day Plan Pearson VUE Test-Center Checklist, IDs, Code Books, and ATT Results, Pass/Fail Scoring, and Certificate Availability Retake Timing, Fees, Refunds, and Complaint Rules AHIMA Recertification Over a 2-Year Cycle CCA to CCS, RHIT, and RHIA Career Path

MPI and Patient Identity

Key Takeaways Explain This Topic AI

The master patient index (MPI) links a patient to record numbers, encounters, and demographic identifiers; an enterprise MPI spans multiple facilities or systems.

Accurate identity underpins retrieval, coding, billing, patient safety, quality reporting, and privacy.

Duplicate, overlay, and overlap errors corrupt data and create safety and disclosure risk in distinct ways.

Suspected identity errors route to the MPI/HIM identity-management process; coders do not merge, delete, or keep coding from a questionable record.

Last updated: June 2026

Master Patient Index and Identity

The master patient index (MPI) is the system that links each patient to their medical record number(s), encounters, demographics, and other identity data. When it spans multiple facilities or systems, it is an enterprise master patient index (EMPI) . CCA Domain 3 includes retrieving patient information from the MPI, but the skill is not merely finding a name — it is locating the correct patient and encounter so the right documentation supports the right codes, claim, quality data, and disclosure decisions.

Identity Elements Used for Matching

MPI data may include name and aliases, date of birth, sex, address, phone, Social Security number (where collected), MRN, enterprise identifier, encounter numbers, facility, and links to prior names or merged records. Matching should use multiple identifiers — never one detail alone. Best-practice patient identification typically relies on at least two identifiers (for example, name plus date of birth) before accessing or acting on a record.

Three Identity Error Types

  • Error Definition Primary risk
  • Duplicate One patient has two or more MRNs Split history, fragmented coding data, missed prior conditions

Overlay One patient's documentation filed under another patient's MRN Mixed diagnoses, allergies, and results across two people — a patient-safety hazard

Overlap One patient has separate records across systems that should be linked but are not Incomplete view of the patient across the enterprise

An overlay is the most dangerous because clinical data — allergies, medications, lab results — crosses between two real patients, and disclosing it can breach the wrong person's privacy. A duplicate is more of a completeness and reimbursement problem; an overlap is an integration gap. The distinctions are not academic: an overlay can cause a clinician to act on the wrong patient's allergy or result, which is why overlays are treated as patient-safety incidents and not merely data cleanup.

Duplicates quietly fragment a patient's longitudinal history, so a prior surgery or chronic condition sitting under the second medical record number never surfaces during the current encounter, weakening both care and coding. Overlaps appear most often after mergers or when a patient is seen across affiliated facilities that have not yet linked their identifiers, leaving a true but incomplete record on each side.

Matching logic is what holds the index together, and the exam may probe why single-identifier matching fails. Names are shared, misspelled, hyphenated, or changed after marriage; dates of birth collide constantly in large populations; and addresses and phone numbers change. Robust matching therefore weighs several attributes together — name, date of birth, sex, and often an enterprise identifier — and flags probable matches for human review rather than auto-merging.

This is why a coder who notices something off should never "fix" identity in the moment: an apparent duplicate may actually be two different people who share a birthday and a common name, and an unauthorized merge would create a far worse overlay. The safe move is always to surface the suspicion to the identity-management team that owns the matching rules and the audit trail.

Worked Scenario

A coder opens Patient B's chart and finds a lab result clearly belonging to Patient A. This is a probable overlay (misfiled documentation). The coder must not use that result to support a code, must not copy it into both charts to "preserve access," and must not keep coding from the suspect record. The correct action is to stop and report the issue through the HIM identity-management/MPI process .

CCA Response Pattern

When an item describes a suspected MPI problem, the safe answer is: stop relying on the questionable record and escalate through HIM identity management. The coder does not merge records, delete data, or continue coding unless policy authorizes the next step. Resolving duplicates and overlays is governed by data-integrity policy and audit trails so that nothing is lost.

Why Identity Errors Reach the Coder

The coder is often the first downstream user to notice an identity error because coding requires reading the whole encounter closely. A diagnosis that contradicts the patient's documented sex, a surgical history that cannot belong to the stated age, an allergy list that flips between two notes, or a result addressed to a different name are all red flags. Recognizing the pattern matters more than diagnosing the exact error type, because the response is the same: stop, do not code from the suspect data, and escalate.

Coding from a duplicate can split a patient's history so that prior conditions are missed and the case mix is understated; coding from an overlay can attach one patient's diagnoses, procedures, and present-on-admission status to a completely different person's claim, which is both a billing error and a reportable privacy breach.

Identity as a Data-Quality Function

Identity integrity is preventive, not just corrective. Standardized naming conventions, demographic validation at registration, mandatory two-identifier verification before access, and routine duplicate-rate monitoring all reduce errors before they reach the coder. A facility that tracks its duplicate rate treats identity as an ongoing information-governance metric rather than a one-time cleanup, and many organizations run periodic MPI clean-up projects with strict audit trails so that no clinical data is lost when records are merged or unmerged.

For the exam, remember the hierarchy of action: verify identity with at least two identifiers before doing anything, suspect an error when the clinical picture is internally inconsistent, refuse to reuse or duplicate questionable data, and route every suspected duplicate, overlay, or overlap to the HIM identity-management process rather than fixing it informally. That sequence protects patient safety, coding accuracy, claim integrity, and privacy at the same time, which is exactly why MPI questions are weighted as high-risk scenarios.