Anesthesia Coding Alert

Not every condition mentioned in the documentation should be coded.

Guideline 19 of the ICD-10-CM Official Guidelines for Coding and Reporting sounds deceptively simple:

“The assignment of a diagnosis code is based on the provider’s diagnostic statement that the condition exists. The provider’s statement that the patient has a particular condition is sufficient. Code assignment is not based on clinical criteria used by the provider to establish the diagnosis. If there is conflicting medical record documentation, query the provider.” (Section I.A.19)

This is one of the most frequently misunderstood rules in medical coding.

At first glance, this guideline appears to give coders broad authority to capture any diagnosis documented by a healthcare provider. What it means is that coders must be able to differentiate a statement from a mention. Let’s look at the facts that support this interpretation.

Understand Statement vs. Mention

Context matters when deciding when to code for a condition. A statement in a provider’s documentation is not the same as a mention. A statement may be a history of present illness (HPI), a formal attestation, or a level of detail required for medical necessity or a diagnosis. A mention states a fact, event, or condition that is not central to the date of service’s (DOS’s) assessment or plan.

Presence in the note is not proof of clinical relevance. Listing a chronic condition in the HPI becomes codable only when the provider demonstrates current involvement in the monitoring, evaluating, assessing/addressing, or treating of the condition. For example, a provider might list diabetes in the HPI or include it in the problem list, but unless there is documented evidence that the condition influenced today’s care, assessment, or plan, it is not reportable for that visit.

Similarly, the use of active voice (e.g., “Patient has diabetes” or “Patient is being treated for hypertension”) does not automatically make a diagnosis reportable. The active voice is a grammatical choice, not a coding rule. The Centers for Medicare & Medicaid Services does not recognize active voice as a determinant of code assignment in its official guidelines.

Shine These Guiding Lights on the Record

Three AHA Coding Clinic examples show how context determines whether a diagnosis should be reported.

Q3 2020 – The sore throat encounter

A patient presented to the emergency department with a sore throat. The provider listed several mental health conditions but did not evaluate, assess, or treat them during that visit. AHA Coding Clinic advises not to code those conditions.

Application: The note reflected history, not management. Since the mental health conditions did not influence the day’s care or decision-making, they do not meet the threshold for provider engagement.

Q3 2019 – The hernia repair with Crohn’s disease

The patient underwent hernia repair and the provider documented Crohn’s disease, linking it to an immune-modulating medication being managed before and after surgery. AHA Coding Clinic advises to code the Crohn’s.

Application: The provider addressed Crohn’s in the context of surgical planning and therapy management, clearly connecting it to the current care.

Q3 2021 – Chronic conditions and ongoing care

Chronic conditions should be coded only when they are evaluated, addressed, or treated at the encounter. Simply naming a diagnosis is not enough; there must be evidence of interaction between the provider and the condition.

Application: Adjusting medication, reviewing labs, or documenting stability or progression are examples of interaction. Coders should look for these clinical touchpoints before assigning a code because those actions prove the condition was managed, not merely mentioned.

View Through Different Lenses, Share Responsibility

Coders and providers work within different interpretive frameworks. Coders rely on regulatory guidance while providers operate under clinical practice standards, evidence-based medicine, and quality measures. Expecting physicians to memorize every coding nuance is as impractical as expecting coders to apply clinical judgment. True progress in documentation integrity emerges when both disciplines work side by side, each honoring the other’s craft, boundaries, and perspective.

Bridging these perspectives requires organizational guardrails: clinical documentation improvement education, structured electronic health record (EHR) templates, and policies that prompt linkage between clinical reasoning and codable documentation. When coders and providers both operate within clear structures, accuracy follows naturally.

Respect Guardrails That Protect Compliance

Organizations can foster integrity and consistency by:

• Embedding prompts in the EHR that ask whether a condition was addressed, managed, or assessed at the encounter.
• Requiring explicit linkage between the diagnosis and the plan of care.
• Differentiating “active” from “historical” conditions in policy and audit review.

Training coding professionals to validate conditions that are actively managed, addressed or clinically relevant, not simply present or phrased in the note.

These steps create a compliance safety net that prevents overcoding and under-reporting.

Trust, Don’t Look for Loopholes

Guideline 19 was never a loophole to justify volume-based coding. It is a trust agreement between documentation and interpretation. Coding professionals respect the provider’s diagnostic authority and providers respect the regulatory framework that governs how those diagnoses are reported. The organization stands between them, responsible for building systems that ensure integrity and accountability.

When applied correctly, Guideline 19 reminds us that accurate coding is not about counting conditions — it’s about conveying truth in care.

Johanna DeCelleri, CPC, CPCO, CDEO, CRC, AAPC Approved Instructor
(A version of this article first appeared in the April 2026 issue of AAPC the Magazine)