ICD code R73.9 – Unspecified high blood glucose

Key takeaways

R73.9 is the billable ICD-10-CM code for elevated blood glucose without a confirmed diabetes diagnosis.

The Excludes1 note at R73 keeps R73.9 off any claim that carries an E08-E13 diabetes code.

Prediabetes takes R73.03, impaired fasting glucose R73.01 and impaired glucose tolerance R73.02, so R73.9 applies only when the note names no such disorder.

Moving from R73.9 to an E11 code requires a clinician’s documented diabetes diagnosis. A lab value above the ADA threshold isn’t enough on its own.

Pabau’s claims management software flags excluded code combinations before submission, which helps practices avoid the CO-11 and CO-50 denials tied to R73.9 claims.

ICD-10 Code R73.9: Clinical definition and scope

ICD-10 Code R73.9 is the billable code for hyperglycemia, unspecified. It covers elevated blood glucose that a clinician documents without diagnosing diabetes or naming a specific glucose disorder.

The CDC’s FY2027 ICD-10-CM tabular list places it in category R73, whose Excludes1 note bars the diabetes codes E08-E13. “Unspecified” means the type or cause of the elevation hasn’t been determined.

Three documentation scenarios most commonly support R73.9 at the encounter level:

• A high random blood glucose recorded as hyperglycemia, with no clinical interpretation linking it to a specific glucose disorder
• Transient hyperglycemia, which the ICD-10-CM index assigns to R73.9
• An elevated HbA1c the clinician records as hyperglycemia, with no confirmed diabetes diagnosis and no prediabetes label in the note

Documentation decides the code. A glucose of 130 mg/dL supports R73.9 when the encounter note reads “hyperglycemia, further evaluation needed.” The same reading supports E11.9 only when a physician states that the patient has type 2 diabetes mellitus. A note that says “elevated fasting glucose” points to R73.01 instead, because the tabular list files that phrase under impaired fasting glucose.

R73.9 excludes notes and their coding impact

The Excludes1 note at the R73 category level is the most consequential rule governing ICD-10 Code R73.9. An Excludes1 note means the two conditions are never coded together. R73.9 and an excluded code can’t share the same encounter claim.

The Excludes1 list at R73 covers the whole diabetes mellitus code block plus three related conditions:

Once a diabetes diagnosis is established and coded, the diabetes code itself captures the hyperglycemia. R73.9 and any E08-E13 code can’t appear together on the same encounter claim. Submitting both triggers a CO-11 edit (“The diagnosis is inconsistent with the procedure”) at most clearinghouses.

R73.9 vs R73.09: Choosing the right code

R73.9 and R73.09 sit one character apart but cover different clinical situations. Mixing them up is a frequent R73 error, particularly when the note carries a prediabetes label or an abnormal glucose tolerance result.

Prediabetes has its own subcode, R73.03, which took effect on October 1, 2016, the start of FY2017. When a clinician documents “prediabetes” explicitly, R73.03 is correct.

Impaired fasting glucose takes R73.01, and impaired oral glucose tolerance takes R73.02. R73.09 covers the remaining abnormal glucose findings, such as abnormal glucose NOS. R73.9 is correct only when the note names no specific glucose disorder.

R73.9 vs E11.9: When to escalate the diagnosis

R73.9 versus E11.9 is a decision coders often misjudge. Using R73.9 when the documentation supports E11.9 (type 2 diabetes mellitus without complications) can underrepresent the patient’s condition. Using E11.9 without documentation support leads to medical necessity denials.

The ICD-10-CM Official Guidelines set the rule: code what the physician documented, and leave the reading of lab values to the physician. A fasting glucose of 128 mg/dL does not automatically produce a diabetes code. The physician’s encounter note must include a diabetes diagnosis statement.

Use this decision sequence before assigning either code:

1. Check the encounter note: Does the clinician state a diagnosis of diabetes mellitus? If yes, assign the appropriate E-series code. If no, proceed to step 2.
2. Check the lab values: Is the HbA1c at or above 6.5%, or the fasting glucose at or above 126 mg/dL? If yes but no clinician diagnosis statement exists, do not assign an E-series code. R73.9 or R73.09 applies.
3. Check the specific glucose finding: Does the note use a named category (“prediabetes,” “impaired glucose tolerance,” “impaired fasting glucose”)? If yes, R73.03, R73.02 or R73.01 applies in place of R73.9.
4. Assign R73.9: When elevated glucose is documented without a specific glucose disorder label and without a confirmed diabetes diagnosis.

Per the CMS ICD-10-CM coding guidelines, coders should not interpret lab results independently of physician documentation. The ADA’s clinical threshold (HbA1c 6.5% or FPG 126 mg/dL) is a clinical anchor, not an automatic coding trigger.

The chart below maps that sequence onto the code each branch lands on.

Complete R73 subcode reference

The R73 category contains five billable subcodes. Coders navigating elevated glucose findings need to review all five before settling on R73.9.

Coders sometimes use R73.9 as a catch-all when any glucose value looks high. That habit creates audit exposure. When the chart contains a prediabetes label or an OGTT result, the more specific subcode applies, and R73.9 on that claim is a coding error. Verify against the CDC/NCHS ICD-10-CM web tool when subcode selection is uncertain.

Documentation requirements for ICD-10 Code R73.9

ICD-10 Code R73.9 is straightforward to apply when the clinical record contains the right elements. Missing any of the following creates both a coding error and a denial risk. Per medical billing compliance standards, every diagnosis code on a claim needs supporting documentation in the record.

• Lab value with reference range: The specific glucose result (fasting, random, or HbA1c) must appear in the record with the laboratory’s reference range. A result flagged “H” (high) in the lab panel alone is insufficient without the clinician’s interpretation.
• Clinician interpretation statement: The note must include the physician or provider’s assessment of the finding. “Hyperglycemia, monitoring” or “hyperglycemia, etiology under investigation” are sufficient. A lab result pasted into a note with no provider comment is not.
• Absence of diabetes diagnosis: The note must not use diabetes, type 2 diabetes, DM, or T2DM to describe the patient’s current condition. If those terms appear, an E-series code is required.
• Encounter context: Whether the elevated glucose is the primary reason for the visit or an incidental finding affects how R73.9 is sequenced. Principal diagnosis selection follows the UHDDS definition when the encounter is inpatient.

How to document hyperglycemia correctly

A single phrase usually separates documentation that supports R73.9 from documentation that invites an audit. Compare these three notes:

• Supports R73.9: “Random glucose 168 mg/dL, hyperglycemia. No current diabetes diagnosis. Will recheck in 3 months.” This note grounds the finding, states no diabetes, and documents a follow-up plan.
• Triggers E11.x review: “Patient has DM2. FBG elevated at 182 mg/dL.” Even if the coder intended R73.9, the DM2 reference requires an E11-series code and R73.9 cannot appear alongside it.
• Triggers R73.03 instead: “Prediabetes confirmed. Patient counseled on lifestyle interventions.” The word “prediabetes” is the trigger. R73.03 is more specific and correct here.

Payer policies and medical necessity

Payer acceptance of ICD-10 Code R73.9 as a primary diagnosis varies by payer and by the service being billed. Medicare Administrative Contractors (MACs) publish Local Coverage Determinations (LCDs) that specify which services R73.9 supports as a covered indication.

These are the service categories where R73.9 most commonly appears as a covered primary or supporting diagnosis:

• Glucose laboratory tests (CPT 82947, 82950, 82951): Medicare and commercial payers generally accept these with R73.9 as the primary diagnosis. The lab order should tie to monitoring or evaluating the elevated glucose finding.
• HbA1c testing (CPT 83036): Accepted when R73.9 supports the need to monitor glycemic status before a diabetes diagnosis is established. Some MACs require an LCD-specified frequency limitation.
• Diabetes self-management training (G0108, G0109): R73.9 alone may not qualify for DSMT services under Medicare’s NCD (40.1) without a diabetes diagnosis. Verify individual MAC LCDs before billing this pairing.
• Evaluation and management (99202-99215): R73.9 works as the primary diagnosis when the note shows elevated glucose was the chief reason for the visit.

Commercial payer policies differ from Medicare LCDs. Always verify the specific plan’s coverage policy for the service being billed. Payers scrutinize R73.9 less as a secondary diagnosis in a broader metabolic workup. It draws the most review as the sole primary diagnosis on a service with stricter coverage criteria.

Common claim denials for ICD-10 Code R73.9 and how to avoid them

Denials tied to ICD-10 Code R73.9 follow predictable patterns. Each one has a corresponding CARC code that tells you exactly what the payer objected to. Denial management workflows that catch these patterns before submission cost far less than appeals after the fact. Our reference on CARC denial codes explains each code in full.

Submitting through a clearinghouse that runs claim edits against LCD databases catches many of these before they reach the payer. Pabau, the practice management platform we build, connects to the Claim.MD clearinghouse to flag excluded code combinations and run real-time eligibility checks. CO-11 edits on R73.9 claims then surface at the scrubbing stage, before adjudication.

CPT codes commonly paired with R73.9

The CPT codes below are the ones most often billed alongside ICD-10 Code R73.9, based on standard coding references. Quantitative blood glucose testing under 82947 is the most direct pairing, since it monitors the finding itself.

For practices submitting through a medical claims clearinghouse, real-time eligibility checks can confirm a pairing is covered before submission.

Payer-specific LCD confirmation is advisable before billing G0108 or G0109 (diabetes self-management training) with R73.9 as the sole supporting diagnosis. Those services are generally tied to a confirmed diabetes diagnosis under Medicare’s NCD requirements.

How claims management software prevents R73.9 denials

Practices that see elevated glucose patients in preventive, primary care and metabolic health settings code R73.9 often. The usual audit failure is a correct code whose clinical record can’t support it on review. Connecting the signed note to the claim closes that weakness.

Pabau’s claims management software works with Claim.MD to run pre-submission edits against the ICD-10 code set. It flags excluded pairings, such as R73.9 with any E08-E13 code, before the claim reaches the payer.

The audit trail records which provider signed the note, which codes were assigned, and when the claim went out. That is the documentation chain payers ask for in a post-payment audit, so clean first claims and faster denial resolution both follow from it.

Catch R73.9 coding errors before they become denials

Pabau integrates with Claim.MD to scrub ICD-10 code combinations, run real-time eligibility, and flag excluded pairings at submission. See how it works for metabolic health and primary care workflows.

Book a demo

Conclusion

R73.9 holds up on a claim when the note does three jobs. It records the glucose value with the clinician’s reading of it. It stays silent on diabetes, and it names no more specific glucose disorder.

When one of those fails, recode before submission instead of appealing afterward. R73.01, R73.02, R73.03 or the E-series code the note supports will pay on the first pass, where R73.9 would be denied.

The Excludes1 clash with E08-E13 is the one error a pre-submission check should never let through. Book a demo to see how Pabau flags R73.9 conflicts before your claims reach the payer.

Continue your research

Need to understand how clearinghouse edits catch code errors? Submitting clean claims explains what payers check at adjudication and how pre-submission scrubbing reduces rework.

Choosing a clearinghouse for diagnosis-heavy claims? Claim.MD clearinghouse guide covers how ERA/835 remittances surface CARC denial codes and what to do next.

Comparing billing platforms for metabolic health services? Best medical billing software compares platforms that handle complex ICD-10 pairings and LCD compliance for US practices.

Frequently asked questions