Posted on

Nov 12, 2026

Most Commonly Miscoded ICD-10 Codes After FY 2026 Update

Physician reviewing diagnosis code specificity on a tablet in a clinic exam room after the FY 2026 ICD-10 update.
Physician reviewing diagnosis code specificity on a tablet in a clinic exam room after the FY 2026 ICD-10 update.

Most Commonly Miscoded ICD-10 Codes After the FY 2026 Code Set Update: A Clinic Operations Playbook

The most commonly miscoded ICD-10-CM codes after the FY 2026 update are unspecified defaults (I50.9, E11.9, N18.9), incomplete diabetes complication pairs, the new hypoglycemia level subcategory (E16.A-), CKD and obesity staging codes, and Excludes1 conflicts. Correcting them requires clinician-documented specificity at the point of care, not retrospective coder inference.

Unspecified diagnosis codes remain the top FY 2026 miscoding risk

CLINICAL UPDATE 2026: Revised for 2026 CMS CPT G2211 attestation rules, California SB 1120 compliance, and NCCI Modifier 25 bundling criteria.

The FY 2026 ICD-10-CM code set took effect October 1, 2025, and applies to all encounters with dates of service on or after that date. Each annual update adds codes, deletes codes, and revises tabular instructions. The miscoding pattern that follows every update is the same: EHR problem lists and favorite-code pick lists keep pointing to legacy or unspecified codes while the official code set has moved toward greater granularity.

Unspecified codes are not invalid, but they are frequently inaccurate. ICD-10-CM Official Guidelines permit unspecified codes only when the clinical documentation does not support a more specific option. When the clinician has documented ejection fraction, CKD stage, or a diabetic complication elsewhere in the note, selecting the unspecified code misrepresents the record. Payers and risk adjustment auditors treat that mismatch as either undercoding (lost revenue and lost risk capture) or internal inconsistency (audit trigger).

Medical directors should treat specificity as a clinical quality issue first and a revenue issue second. A note that says "CHF" with no type or acuity fails to communicate the patient's physiology to the next clinician, the care manager, or the quality program. The coding gap is a symptom of a documentation gap, and the documentation gap originates in the exam room.

This playbook ranks the codes that produce the highest volume of corrections, denials, and risk adjustment data validation (RADV) findings in outpatient settings after the FY 2026 transition. Each section defines the documentation element that resolves the error, the audit exposure if that element is missing, and the operational control a clinic can deploy.

Heart failure coded as I50.9 forfeits specificity and invites audits

The code I50.9 (ICD-10-CM), heart failure, unspecified, is among the most overused codes in primary care, cardiology follow-up, and hospitalist transitions. ICD-10-CM provides specific codes for systolic (I50.2-), diastolic (I50.3-), combined (I50.4-), right heart failure (I50.81-), and other specified types, each with acuity axes (acute, chronic, acute on chronic). The heart failure subcategories also include terms aligned with ejection fraction phenotypes, such as heart failure with reduced or preserved ejection fraction.

The documentation fix is narrow: the clinician must state the type and acuity in the assessment. Coders cannot assign I50.22 (chronic systolic heart failure) from an echocardiogram report alone if the treating clinician never linked the finding to a diagnosis in the encounter note. Writing "HFrEF, chronic, EF 30% on 2025 echo, stable on GDMT" resolves the code, supports medical necessity for medication management, and satisfies risk adjustment MEAT criteria (Monitor, Evaluate, Assess, Treat).

Combination coding compounds the error. When hypertension and heart failure coexist, ICD-10-CM presumes a causal relationship and directs coders to I11.0 (hypertensive heart disease with heart failure) plus the specific I50 code. When CKD is also present, I13.- applies. Clinics that code I10 plus I50.9 separately miss both the combination code and the specificity code, producing a claim that is wrong on two axes.

Audit vulnerability is highest in Medicare Advantage RADV reviews, where heart failure carries substantial risk adjustment weight under the CMS-HCC V28 model. A chart that supports only I50.9 still maps to a payment HCC, but a chart that lists heart failure on the problem list without MEAT evidence in the encounter fails validation entirely.

Diabetes coded as E11.9 ignores documented complications and remission

The code E11.9 (ICD-10-CM), type 2 diabetes mellitus without complications, is the single most common diabetes miscode in ambulatory audits. The error occurs when the note documents a complication (neuropathy, nephropathy, retinopathy, hyperglycemia, hypoglycemia) but the claim carries E11.9 because it was the default problem list entry.

ICD-10-CM's "with" convention presumes a causal link between diabetes and conditions listed under "with" in the Alphabetic Index, including CKD, peripheral neuropathy, and several other conditions, unless the clinician documents a different cause. A patient with type 2 diabetes and stage 3b CKD should be coded E11.22 plus N18.32, not E11.9 plus N18.9. Coding E11.9 alongside a diabetic complication code is internally contradictory and will fail editing logic at many payers.

Uncontrolled diabetes remains a trap. The word "uncontrolled" does not map to a single code. The clinician must specify hyperglycemia (E11.65) or hypoglycemia (E11.649 or E11.641 with coma). Notes that say "poorly controlled DM2, A1c 9.8" should explicitly state "with hyperglycemia" to support E11.65.

Remission coding is still misunderstood. The E11.A code for type 2 diabetes without complications in remission, introduced in a recent update cycle, requires explicit clinician documentation of remission. Coders should not infer remission from a normal A1c in a patient taking metformin. Conversely, clinicians who document sustained normoglycemia off pharmacotherapy but never write the word "remission" leave the chart coded as active diabetes.

Long-term medication Z codes are routinely omitted. Z79.4 (long-term current use of insulin), Z79.84 (oral hypoglycemic drugs), and Z79.85 (injectable non-insulin antidiabetic drugs) should accompany the diabetes code when applicable. Clinics that build diabetes macros in their 1,000+ Specialty Clinical Macros library should include a required medication-class field to trigger the correct Z code.

New hypoglycemia level codes require documented glucose thresholds

The FY 2026 update introduced a hypoglycemia level subcategory (E16.A-) that classifies hypoglycemia by clinical severity: level 1, level 2, and level 3. These levels align with the consensus framework used in diabetes care, where level 1 reflects glucose below 70 mg/dL and at or above 54 mg/dL, level 2 reflects glucose below 54 mg/dL, and level 3 reflects a severe event with altered mental or physical status requiring assistance from another person.

Diabetic hypoglycemia codes now pair with a level code when the level is documented. Tabular instructions direct coders to use an additional code for the hypoglycemia level with the diabetic hypoglycemia codes. A claim carrying E11.649 alone, when the note documents a glucose of 48 mg/dL, is incomplete under FY 2026 rules.

The most frequent FY 2026 error is assigning a level without a supporting value or functional description. "Hypoglycemic episode last week" supports E11.649 but no level. "Patient's spouse administered glucagon after patient became confused, glucometer 41" supports level 3. Medical directors should instruct clinicians to document the lowest recorded value, the source (CGM, fingerstick, lab), and whether third-party assistance was required.

Clinics should audit CGM-heavy endocrinology and primary care panels first. CGM downloads frequently show level 2 events that clinicians review but do not name in the assessment. The data exists in the chart, but the diagnosis does not, and coders cannot code from device reports the treating clinician has not interpreted.

CKD stage and obesity class codes fail without explicit staging

N18.9, chronic kidney disease unspecified, persists in claims years after stage 3 was split into N18.31 (stage 3a) and N18.32 (stage 3b). The distinction matters clinically (eGFR 45 to 59 versus 30 to 44), for risk adjustment, and for quality measures. Clinicians frequently document an eGFR value without naming the stage, and coders cannot calculate stage from a lab value.

The fix is a stage statement tied to the clinician's interpretation: "CKD stage 3b, eGFR 38 stable over 6 months, on SGLT2 inhibitor." Two eGFR values more than 90 days apart support chronicity, which protects the code from audit challenges that a single depressed eGFR reflects acute kidney injury.

Obesity class codes introduced in a recent cycle (E66.811, E66.812, E66.813 for class 1, 2, and 3) are now widely misapplied. The class code describes the clinician's diagnosis; the BMI Z code (Z68.-) describes the measurement. Official guidelines allow BMI to be taken from other clinicians' documentation (such as nursing), but the associated weight diagnosis must come from the treating provider. Coding Z68.41 without a documented obesity diagnosis is an unsupported claim line.

Anti-obesity medication prior authorizations amplify this risk. Payers reviewing GLP-1 receptor agonist requests cross-check the obesity class code, BMI Z code, and documented comorbidities. A mismatch between E66.9 on the claim and Z68.43 in the record frequently generates a denial that takes weeks to overturn.

Excludes1 conflicts and combination codes trigger automated claim edits

Excludes1 notes indicate that two conditions cannot be reported together because they are mutually exclusive. Annual updates add and revise these notes, and clinics relying on outdated code pairs produce claims that fail automated edits. Common outpatient conflicts include reporting both a sign or symptom code and the definitive diagnosis that explains it, and pairing conditions the tabular list classifies as alternatives.

Official guidance clarified that when two conditions are unrelated, an Excludes1 note may not prohibit dual reporting. This exception requires the clinician to document that the conditions are independent. Without that statement, the claim defaults to the edit, and coders have no basis to override.

Combination codes are the other high-volume error. Hypertensive heart and kidney disease (I13.-), diabetes with complications (E11.2- through E11.6-), and COPD with acute exacerbation (J44.1) each replace two separate codes. Reporting the components separately is a coding error, not a stylistic choice, and payers increasingly flag it through predictive editing software.

SDOH Z codes are underreported rather than miscoded. Z55 through Z65 codes may be assigned from documentation by any member of the care team, including social workers and nurses, and they support the CMS social drivers of health screening measures. Clinics that screen but fail to code lose both quality credit and the data trail that justifies care management time.

The FY 2026 miscoding risk matrix for clinic leadership

The following table maps each high-risk clinical parameter to its documentation requirement, audit exposure, and the structured control the Scribing.io Clinical Interface applies during note generation. DOM refers to the documentation object model that structures each assessment element before it reaches the coder.

Clinical Parameter

Documentation Requirement

Audit Vulnerability

Scribing.io DOM Mechanism

Heart failure type and acuity (I50.-)

Systolic, diastolic, combined, or other type; acute, chronic, or acute on chronic; EF reference

I50.9 default; RADV failure without MEAT; missed I11.0 or I13.- combination

Required type and acuity fields; hypertension cross-check prompts combination code

Diabetes complications (E11.-)

Named complication linked to diabetes; hyperglycemia or hypoglycemia stated explicitly

E11.9 coded alongside complication codes; "uncontrolled" without qualifier

Complication extraction from assessment; conflict alert when E11.9 coexists with complication

Hypoglycemia level (E16.A-)

Lowest glucose value, source, and need for third-party assistance

Level assigned without supporting value; missing level with diabetic hypoglycemia code

Glucose value and assistance capture; level suggestion requires clinician confirmation

Diabetes remission (E11.A)

Explicit clinician statement of remission and supporting clinical course

Remission inferred from labs; active diabetes coded after documented remission

Remission term detection; blocks code suggestion without explicit clinician language

CKD stage (N18.-)

Named stage (3a, 3b, etc.) with eGFR trend supporting chronicity

N18.9 default; stage inferred by coder from lab value

eGFR trend display with required stage selection in assessment

Obesity class (E66.81-) and BMI (Z68.-)

Provider-documented obesity class; BMI from any qualified clinician

BMI Z code without weight diagnosis; class and BMI mismatch on prior auth

BMI-to-class consistency check; flags missing provider diagnosis

Excludes1 pairs

Statement of independence when conditions are unrelated

Automated claim edit rejection; symptom coded with definitive diagnosis

FY 2026 tabular edit library applied before note sign-off

SDOH (Z55 to Z65)

Screening result documented by any care team member

Screening performed but not coded; quality measure gap

Screening response mapping to Z code candidates for review

Every mechanism in this table keeps the clinician as the decision-maker. The interface surfaces specificity gaps and conflicts; it does not assign codes the clinician did not support with documented clinical judgment. That design choice matters for both compliance and the payer review environment described below.

Modifier 25 and G2211 attestation depend on clean diagnosis linkage

Diagnosis specificity directly affects procedure and add-on code reimbursement. NCCI edits bundle many minor procedures with the E/M service performed on the same day. Modifier 25 unbundles them only when the E/M is significant and separately identifiable. Linking both the E/M and the procedure to the same unspecified diagnosis weakens the separately identifiable argument. Our guide on Managing Modifier 25 Clinical Revenue Integrity details the documentation split.

A practical example clarifies this. A patient presents for diabetes and heart failure follow-up and receives a knee injection during the same visit. If the claim links the E/M only to M17.11 (unilateral primary osteoarthritis, right knee), the E/M looks like pre-procedure evaluation. If the E/M links to E11.22, N18.32, and I50.32 with documented medication adjustments, the separately identifiable work is evident.

HCPCS G2211, the visit complexity add-on, compensates for longitudinal care relationships. CMS policy for 2025 and continuing into 2026 permits G2211 when the E/M is reported with modifier 25 in the narrow circumstance of same-day annual wellness visits, vaccine administration, or Medicare Part B preventive services. It remains unpayable when modifier 25 attaches to an E/M billed with other procedures. Clinics should confirm the current Physician Fee Schedule language before configuring billing rules.

G2211 audit defense rests on documenting the ongoing relationship: the clinician is the continuing focal point for the patient's care or provides ongoing care for a single serious or complex condition. Specific, chronic diagnosis codes (I50.32, E11.22, N18.32) make that relationship legible to reviewers. A claim carrying only I50.9 and E11.9 provides weak evidence of longitudinal complexity management.

California SB 1120 changes how AI-driven denials are reviewed

California SB 1120, effective January 1, 2025, requires that health plans and disability insurers using artificial intelligence or algorithms in utilization review ensure that medical necessity determinations are made by a licensed physician or qualified health care professional. The algorithm cannot supplant clinician decision-making, and it must base determinations on the individual patient's clinical history and circumstances rather than solely on group datasets.

The law has two implications for clinic coding operations. First, when a California plan denies a service, the clinic can request evidence that a qualified reviewer examined the individual record. Second, that individual review will scrutinize the chart itself, so clinical documentation specificity becomes the deciding factor once a human reviewer is involved.

Clinics outside California should watch this framework closely. Several states have introduced similar legislation, and CMS rules for Medicare Advantage already require that coverage determinations consider individual patient circumstances. The direction is consistent: payer algorithms face more oversight, and the clinical record carries more weight in each dispute.

Ambient documentation tools must mirror the same principle on the provider side. AI-assisted documentation should draft, structure, and flag, while the signing clinician remains accountable for every diagnosis. A defensible workflow records clinician confirmation of each specificity element, which is the audit trail regulators and payers increasingly expect.

A 30-day remediation protocol for clinic medical directors

Week one establishes the baseline. Pull a report of the top 25 diagnosis codes by claim volume for encounters since October 1, 2025. Calculate the percentage of unspecified codes (any code ending in .9 or containing "unspecified" in its descriptor) within heart failure, diabetes, CKD, COPD, and obesity. Flag any provider whose unspecified rate exceeds the clinic median by more than 50 percent.

Week two targets the pick lists. Audit EHR favorites, problem list defaults, and order set diagnosis associations. Remove deleted codes, replace unspecified defaults with prompts requiring specificity, and add the E16.A- hypoglycemia level codes to diabetes order sets. This single step often resolves a large share of the error volume because many miscodes originate from a convenience list built before the update.

Week three addresses clinician documentation habits. Conduct a focused 20-minute education session on the five highest-volume errors in your baseline report. Provide specialty-specific note structures from the Specialty Clinical Documentation Library so cardiology, endocrinology, nephrology, and primary care teams each see examples relevant to their panels.

Week four validates the intervention. Sample 10 charts per provider and score each for type, acuity, stage, complication linkage, and MEAT support. Compare against the week one baseline. Repeat the sample at 90 days to confirm durability, and schedule the next review for the April interim update window and the FY 2027 transition on October 1, 2026.

Build escalation rules for persistent outliers. Providers whose specificity rate does not improve after education should receive one-on-one review with a certified coder present. Frame the discussion clinically: specific documentation improves handoffs, care management targeting, and quality measure accuracy, not only reimbursement.

Track three operational metrics monthly: unspecified code rate by condition category, first-pass claim acceptance rate, and query volume from coding staff. A falling query volume with a stable or improving acceptance rate indicates the documentation is now resolving specificity at the source.

Frequently asked questions about FY 2026 ICD-10 miscoding

When did the FY 2026 ICD-10-CM code set take effect?

The FY 2026 ICD-10-CM code set took effect October 1, 2025, and applies to encounters with dates of service on or after that date. Claims for earlier dates must use the prior year's code set. Clinics should also monitor CMS for any April 1 interim updates during the fiscal year.

Is coding I50.9 for heart failure a compliance violation?

Coding I50.9 is not automatically a violation, but it is inaccurate when the record documents heart failure type or acuity. Official guidelines permit unspecified codes only when documentation lacks specificity. Repeated use despite documented ejection fraction and acuity creates RADV exposure and signals internal record inconsistency to auditors.

How should clinicians document the new hypoglycemia level codes?

Clinicians should document the lowest recorded glucose value, its source (CGM, fingerstick, or lab), and whether another person had to assist the patient. These elements distinguish levels 1, 2, and 3 within E16.A-, which accompany diabetic hypoglycemia codes such as E11.649 when the level is documented.

Can E11.9 be reported with a diabetic complication code?

No, E11.9 means type 2 diabetes without complications, so pairing it with codes like E11.22 or E11.40 is contradictory. When complications are documented, report the specific complication codes instead. Add Z79 medication codes for long-term insulin, oral hypoglycemic, or injectable non-insulin therapy when applicable to the patient.

Does diagnosis specificity affect G2211 and Modifier 25 reimbursement?

Yes, specific chronic diagnosis codes strengthen evidence of longitudinal care for G2211 and separately identifiable work for Modifier 25. Linking an E/M and a procedure to the same unspecified diagnosis weakens both arguments. G2211 with Modifier 25 is payable only alongside AWVs, vaccine administration, or Part B preventive services.

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Image

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.