ICD-10 Code E11.65: Type 2 Diabetes with Hyperglycemia

Key Takeaways

ICD-10 Code E11.65 is the billable diagnosis code for Type 2 diabetes mellitus with hyperglycemia, valid from 2016 through 2026.

ICD-10-CM does not use the term ‘uncontrolled’ diabetes – hyperglycemia is the documented clinical condition, requiring elevated glucose evidence in the chart.

E11.65 is a distinct code from E11.9 (without complications) and E11.69 (other specified complication) – selecting the wrong code triggers claim denials.

Pabau’s claims management software helps diabetes clinics document hyperglycemia accurately and submit cleaner claims with fewer denials.

ICD-10 Code E11.65: Definition and Clinical Description

Diabetes claim denials consistently rank among the most common reasons payers reject endocrinology and primary care submissions. One frequent source of that friction is the wrong code selection within the E11 family – specifically, confusing E11.65 with E11.9 or E11.69. Metabolic health EHR workflows that embed code selection criteria at the point of documentation help prevent these costly errors before claims leave the practice.

ICD-10 Code E11.65 is a billable, specific ICD-10-CM diagnosis code representing Type 2 diabetes mellitus with hyperglycemia. It sits within Chapter 4 of the ICD-10-CM tabular list, covering endocrine, nutritional, and metabolic diseases (E00-E89). According to the Centers for Medicare and Medicaid Services (CMS), this code has been valid and billable for every coding year from 2016 through 2026. This article covers the clinical description, code hierarchy, documentation requirements, related code comparisons, and billing considerations providers need to use E11.65 correctly.

Clinical Meaning of E11.65

Hyperglycemia in the context of Type 2 diabetes refers to persistently elevated blood glucose levels that exceed normal physiological thresholds. Per AAFP guidance on ICD-10 documentation, the classification system considers hyperglycemia a complication of diabetes rather than a standalone symptom – which is why ICD-10 Code E11.65 resides in the E11.6 subcategory for “other specified complications,” not the E11.9 unspecified category.

Clinically, common indicators include fasting plasma glucose above 126 mg/dL, random glucose exceeding 200 mg/dL, or an HbA1c reflecting poor glycemic control. Lab values like HbA1c and blood glucose monitoring results can function as supporting documentation, though the physician’s explicit documentation of hyperglycemia remains the primary coding driver.

E11.6 Code Family and Code Hierarchy

Understanding where ICD-10 Code E11.65 sits within the broader classification structure matters for coders selecting between adjacent codes. The parent category E11 covers all Type 2 diabetes mellitus manifestations, while the E11.6 subcategory narrows to “Type 2 diabetes mellitus with other specified complications.”

The E08-E13 range covers all diabetes mellitus types classified by the World Health Organization’s ICD-10 classification. E11 specifically applies to Type 2 diabetes with insulin-resistant pathophysiology, distinguishing it from E10 (Type 1) and E13 (other specified types). Never assign the parent code E11 or subcategory E11.6 on a claim – only fully specified, billable codes like E11.65 are accepted by payers.

Documentation Requirements for E11.65

Claim denials for ICD-10 Code E11.65 almost always trace back to documentation gaps. Payers and auditors expect the medical record to clearly support the presence of hyperglycemia at the time of service. Generic references to “poorly controlled diabetes” without supporting clinical evidence rarely survive a retrospective audit.

According to the CDC’s official ICD-10-CM coding tool, documentation must support the code assigned. For E11.65, the record should include at least one of the following. Using structured patient records that capture lab values alongside visit notes makes this verification far simpler during payer audits.

• Elevated blood glucose results – fasting glucose above 126 mg/dL or random glucose above 200 mg/dL documented in the chart
• HbA1c values reflecting poor control – typically 8.0% or higher, though the physician’s interpretation matters more than the threshold alone
• Physician’s explicit notation – the clinical note must use the term “hyperglycemia” or document that blood sugar is elevated; coders cannot infer this from lab values alone
• Treatment response documentation – medication adjustments, insulin dosage changes, or dietary counseling triggered by the hyperglycemic episode strengthen the record
• Clinical context – symptoms such as polyuria, polydipsia, or fatigue that correlate with the lab findings add supporting weight

One important clarification from ICD-10-CM guidelines: the term “uncontrolled” does not appear in the ICD-10-CM classification system. As confirmed by AAFP coding guidance and widely discussed in AAPC coder forums, hyperglycemia is the appropriate clinical term when blood glucose is elevated. Coders receiving documentation that states “uncontrolled Type 2 diabetes” should query the physician to confirm whether hyperglycemia is the intended clinical finding before assigning E11.65. For comparison, see how ICD-10-CM documentation standards apply across other clinical conditions where specificity is required.

ICD-10 Code E11.65 vs. E11.9: Choosing the Right Code

The most common coding decision providers face is whether to assign E11.65 or E11.9 for a routine diabetes management visit. The distinction hinges entirely on whether hyperglycemia is actively documented at that encounter – not on whether the patient has a history of poor glucose control.

E11.9 (Type 2 diabetes mellitus without complications) applies when glucose is well-controlled, no acute complications are present, and the visit is routine monitoring. E11.65 applies when the current encounter involves documented elevated glucose requiring clinical attention. Assigning E11.9 when the chart contains elevated glucose readings and a physician note addressing them is under-coding. The opposite – assigning E11.65 when glucose is controlled and the note does not mention hyperglycemia – is over-coding and a potential compliance risk under HIPAA compliance requirements.

The comparison with E11.69 is equally important. E11.69 covers “other specified complications” of Type 2 diabetes beyond hyperglycemia – for example, diabetic peripheral neuropathy not captured by another more specific code. When hyperglycemia is the primary documented complication, E11.65 is more specific and preferred. Some encounters may warrant both codes when hyperglycemia coexists with another complication. Coders managing mental health comorbidities alongside diabetes can reference how anxiety ICD-10 codes handle similar specificity decisions for concurrent conditions.

E11.65 vs. E11.649: Hyperglycemia vs. Hypoglycemia

E11.649 covers Type 2 diabetes mellitus with hypoglycemia without coma – the clinical opposite of E11.65. Both codes sit within the E11.6 subcategory, making them easy to conflate. Hyperglycemia means glucose is too high; hypoglycemia means glucose is critically low. Assigning E11.65 when the clinical record describes a hypoglycemic episode creates a factual coding error, not merely a specificity issue, and can affect patient risk profiles in claims data.

ICD-9 Crosswalk and Historical Coding Context

Practices transitioning older patient records or working with legacy billing systems occasionally need to crosswalk ICD-10 Code E11.65 to its ICD-9-CM predecessor. Using the official General Equivalence Mappings (GEMs) maintained by CMS, E11.65 maps backward to ICD-9-CM code 250.80.

• ICD-9-CM 250.80 – “DMII oth nt st uncntrld” (Diabetes mellitus, Type II, other, not stated as uncontrolled) – the legacy equivalent for this condition
• Mapping direction – This is a backward crosswalk (ICD-10 to ICD-9); forward mapping from ICD-9 250.80 can produce multiple ICD-10 candidates, so GEMs should always be reviewed with clinical context
• Validity period – E11.65 was introduced with the ICD-10-CM transition effective October 1, 2015 (FY2016) and has remained valid through FY2026 with no modifications to the code descriptor

For research purposes or Medicare data analysis, the ResDAC resource on ICD codes in Medicare files explains how both ICD-9 and ICD-10 codes appear across different claims datasets and fiscal year boundaries. This is particularly relevant for providers analyzing patient populations across pre- and post-transition date ranges.

Streamline Diabetes Documentation and Claims

Pabau helps diabetes and metabolic health practices capture hyperglycemia documentation at the point of care, reducing E11.65 claim denials and coding errors before they reach the payer.

Book a demo

Billing and HCC Risk Adjustment Considerations

ICD-10 Code E11.65 carries significant implications beyond correct claim submission. Diabetes codes within the E11 family are mapped to Hierarchical Condition Categories (HCC) under the CMS-HCC Risk Adjustment Model used for Medicare Advantage and accountable care contracts. Accurate assignment of E11.65 – when clinically supported – contributes to a more accurate risk score for the patient population, which in turn affects plan capitation rates and quality benchmark calculations.

Providers using claims management software integrated with their EHR benefit from automated coding validation that cross-references documented diagnoses against submitted codes. This reduces the chance that a chart containing clear hyperglycemia evidence is submitted under E11.9 – a gap that both underpays the provider and misrepresents patient acuity.

Common Denial Patterns and How to Avoid Them

Several recurring denial patterns affect E11.65 claims. First, the code is submitted without a supporting lab value or physician notation in the record – payers conducting post-payment audits will recoup these. Second, E11.65 is used repeatedly across multiple visits for a patient whose glucose is now well-controlled, without updating the code to E11.9. Third, coders assign E11.65 based on a history notation rather than a current-visit finding.

• Verify current-visit documentation – E11.65 requires hyperglycemia to be present at the encounter being coded, not just historically
• Review each visit’s labs – a patient who was hyperglycemic last quarter may now be at goal; update the code accordingly
• Confirm physician language – coders should not independently infer hyperglycemia from labs; physician documentation must make the connection
• Apply appropriate sequencing – when E11.65 is the reason for the visit, it sequences as the principal diagnosis; when it is a comorbidity affecting management of a different primary condition, it sequences as an additional code per ICD-10-CM Official Guidelines

For broader coding context, the AAPC Codify ICD-10-CM lookup provides access to the full E11 code family with official code notes, excludes, and includes annotations that inform sequencing decisions. Reviewing those annotations alongside the ICD-10-CM Official Guidelines for Coding and Reporting reduces guesswork significantly for complex encounters.

Expert Picks

Need to understand how ICD-10-CM coding specificity applies to other neurological conditions? Intraparenchymal Hemorrhage ICD-10 Codes covers documentation precision requirements across a clinically complex code family.

Managing mental health comorbidities alongside diabetes in your patient panel? Situational Anxiety ICD-10 Code explains how to code anxiety conditions that often present alongside chronic metabolic disease.

Looking for an EHR built for metabolic and chronic disease management? Metabolic Health EMR explains how Pabau supports documentation workflows for endocrine and metabolic conditions.

Want to reduce diabetes claim denials with cleaner submissions? Claims Management Software outlines how Pabau validates coding against clinical documentation before claims reach the payer.

Conclusion

ICD-10 Code E11.65 is precise but only as useful as the documentation supporting it. The code captures a clinically meaningful distinction – that a patient’s Type 2 diabetes is currently manifesting with hyperglycemia – and that distinction matters for claims accuracy, HCC risk scoring, and audit compliance. Practices that build documentation prompts for elevated glucose directly into their clinical workflows minimize the gap between what the physician observes and what the coder submits.

Pabau’s claims management software supports diabetes and metabolic health clinics in aligning clinical notes with billing codes before claims are submitted. To see how Pabau handles diabetes documentation workflows from encounter to submission, book a demo with the team.

Frequently Asked Questions