Diagnosis Coding from Documentation
Key Takeaways
- 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.
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."
A patient's glucose is markedly elevated and insulin is administered, but no provider documents diabetes. For CCA purposes, what should the coder do?
The Alphabetic Index links "Diabetes" and "chronic kidney disease" under the subterm "with." The provider documents both conditions but never states they are related. What does the FY 2026 guideline allow?
An operative note documents excision of a lesion on the left arm, while the clinic note says right arm. What is the best coding action?