Diagnosis Coding from Documentation

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

Diagnosis Coding from Documentation

Key Takeaways Explain This Topic AI

Every diagnosis code must be supported by the provider's documentation in the health record; the coder abstracts, never invents.

Coders abstract condition, acuity, site, laterality, etiology/manifestation links, complications, and documented organisms.

Lab values, medications, orders, and copied-forward problem-list entries do not by themselves establish a diagnosis when a provider statement is missing.

Conflicting, incomplete, or clinically ambiguous documentation is resolved by a compliant, non-leading query, not by assumption.

Last updated: June 2026

Coding Only What the Record Supports

Diagnosis coding begins with a careful read of the encounter to identify the reason for care, the conditions evaluated or treated, relevant signs and symptoms, complications, cause-and-effect statements, and the details needed for specificity. The governing principle from the ICD-10-CM Official Guidelines is that code assignment is based on the provider's documentation . The coder may use the entire record (nursing notes, lab values, imaging, the medication administration record) to clarify a documented condition, but those sources cannot create a diagnosis the provider never stated.

A non-physician clinician's note generally does not establish a diagnosis. A few narrow exceptions in the FY 2026 guidelines let coders use specific documentation from any clinician who is part of the care team: body mass index (BMI), pressure ulcer stage, coma scale, NIH Stroke Scale (NIHSS), Social Determinants of Health (SDOH) Z-codes, laterality, and blood alcohol level may be taken from nursing, dietitian, social-worker, or EMS notes. But the associated medical condition itself — the obesity, the pressure ulcer, the stroke — must still be documented by the patient's provider.

Coding a BMI of 42 from a nursing note without a provider-documented overweight/obesity diagnosis is noncompliant, because the BMI is a supporting detail, not the diagnosis.

Facts to Abstract from Every Encounter
Condition or reason for the encounter
Acute, chronic, acute-on-chronic, recurrent, in remission, or resolved status
Anatomic site, body system, and laterality (right, left, bilateral)
Etiology-and-manifestation relationship (e.g., diabetes with neuropathy)
Complication, adverse effect, poisoning, or underdosing detail
Causative organism when documented or linked by the codebook
Encounter type, healing status, or sequela when a 7th character applies

A disciplined abstraction also distinguishes the reason for the encounter from comorbidities that affect care . On the CCA you report the conditions that coexist at the time of the encounter and that require or affect treatment or management — and you do not report conditions that were previously treated and no longer exist, except where a history Z code is relevant. Resolved conditions, conditions documented only on an old problem list, and findings the provider never addressed are generally not reportable for the current encounter.

Linking Language and the "With" Convention

FY 2026 guidelines presume a causal relationship for the word "with" or "in" when two conditions are linked in the Alphabetic Index or in a Tabular instructional note, even if the provider did not explicitly state the link. For example, the Index entry "Diabetes, with, nephropathy" lets you assign the diabetes-with-CKD combination code without a separate physician statement of causality.

The presumed-link rule does not extend to conditions the guidelines specifically carve out; for instance, the relationship between hypertension and heart conditions is assumed ("Hypertension, with heart"), but the relationship between hypertension and kidney disease is also assumed, whereas a sign or symptom must still be clinically consistent. The opposite is true when conditions are not linked in the Index: the coder needs explicit provider documentation of the relationship before assuming it.

Situation Coder action
Two conditions linked by "with"/"in" in the Index Assume the causal link; code the combination
Conditions not Index-linked Require explicit provider documentation of the link
Lab/medication suggests a condition, no provider statement Do not code it; query if it affects the encounter
Discharge note conflicts with operative note Query to resolve before final coding
Symptom integral to a confirmed diagnosis Do not code the symptom separately

Watch the directionality trap on the exam: "with" implies a link only when the conditions are Index-linked . If a question gives "diabetes" and "osteomyelitis" with no Index subterm pairing them, the coder may not assume diabetic osteomyelitis without a provider statement.

When to Query, and How

Avoid coding from habit. Hypertension, diabetes, heart failure, chronic kidney disease, wounds, fractures, sepsis, and infections routinely need extra detail (type, acuity, stage, organism, laterality). The best exam answer is usually the most specific supported code, never the most severe possible code. When a required detail is missing and the record can reasonably be clarified, a compliant, non-leading physician query is the right action.

A query must follow AHIMA/ACDIS query-practice standards. It must:

present the clinical indicators from the record (labs, imaging, treatment) without suggesting the answer,
offer reasonable, clinically supported options (including "unable to determine" or "other"),
never indicate the financial impact of one answer versus another, and

preserve the provider's independent clinical judgment.

A query phrased "Given the elevated glucose and insulin, the patient has diabetes, correct?" is leading and noncompliant. A compliant version states the indicators ("glucose 310 mg/dL, sliding-scale insulin ordered") and asks the provider to clarify the clinical significance, offering options that include diabetes, stress hyperglycemia, other, and unable to determine. Documentation consistency also matters: if one note says right side and another says left, or the discharge diagnosis conflicts with the operative report, the coder seeks clarification rather than guessing or defaulting to bilateral.

On the CCA, the most defensible answer in any ambiguous, conflicting, or incomplete-documentation scenario is almost always "query the provider" rather than "assign the more specific code" or "assume the relationship."