CPT® Code 83036

Last Updated: February 2026 | Verified against CMS policy updates, Medicare coverage guidance, and major payer clinical policies

Quick Reference: CPT 83036 (HbA1c)

• Test definition: CPT 83036 reports the Hemoglobin A1c (HbA1c) test, which measures the percentage of hemoglobin that is glycated (glucose-attached). Because red blood cells circulate for roughly 120 days, HbA1c is a practical estimate of average glycemia over the prior ~2–3 months .
• Clinical role: HbA1c is central for diagnosing diabetes and monitoring therapy effectiveness. ADA Standards of Care recommend periodic HbA1c testing for all patients with diabetes, with frequency tied to stability and whether treatment goals are met .
• Typical monitoring frequency: Most policies align to “at least twice yearly if stable” and “quarterly if therapy changes or goals are not met” . Medicare coverage guidance also treats testing more often than every 3 months as unusual outside defined scenarios .
• Medicare screening change: CMS expanded diabetes screening rules effective 01/01/2024 to include HbA1c as an approved screening test and updated screening frequency to allow up to two screenings in a 12-month period for eligible at-risk beneficiaries (bill screening with Z13.1) .
• CLIA-waived point-of-care rule: If HbA1c is performed in a CLIA-waived setting (e.g., physician office using an approved waived device), many payers—especially Medicare—expect modifier QW and the CLIA number on the claim to avoid CLIA-related denials .
• High-frequency audit risk: The most common red flags are (1) too-frequent tests without a “poor control/therapy change” narrative and (2) missing documentation of the order/intent and medical necessity .

1. CPT 83036 Definition and Clinical Role in Diabetes Management

CPT 83036 reports the laboratory measurement of glycosylated hemoglobin (Hemoglobin A1c, HbA1c). The test quantifies the proportion of hemoglobin that is non-enzymatically glycated. Because erythrocytes persist in circulation for approximately three to four months, HbA1c functions as an integrated marker of glycemia over the previous 2–3 months rather than a point-in-time glucose value . The result is typically reported as a percentage (e.g., 6.8%). Higher percentages correlate with higher average glucose exposure, and persistently elevated HbA1c is associated with microvascular and macrovascular complication risk.

Clinical decision-making: HbA1c is used in three high-value clinical contexts: (1) diagnosis of diabetes and prediabetes, (2) monitoring of known diabetes, and (3) treatment adjustment (e.g., intensifying medications, addressing adherence, or balancing hypoglycemia risk). ADA Standards describe HbA1c as a primary tool for assessing glycemic control and recommend a testing cadence based on the patient’s stability and achievement of glycemic targets .

Why HbA1c is different from glucose testing: A fasting glucose is sensitive to short-term diet, illness, and time-of-day effects. HbA1c dampens those fluctuations, capturing cumulative glycemic exposure. This is why payers and clinical guidelines often consider repeated HbA1c testing at very short intervals to be low-yield: the biology of red blood cell turnover means the value does not meaningfully “re-equilibrate” week to week in stable patients . That scientific reality underpins many frequency edits in coverage policies.

Clinical documentation that makes HbA1c orders defensible:

• Current diabetes/prediabetes diagnosis (or screening rationale) documented in the assessment.
• Purpose of the test: diagnosis, routine monitoring, or post-therapy-change reassessment.
• Prior HbA1c value and date when available (supports frequency and clinical necessity).
• Planned action based on the result (e.g., medication adjustment, referral, lifestyle plan).

2. Medicare and Commercial Billing Policies (Frequency Limits, CLIA Rules, Point-of-Care Use)

Medicare routine monitoring policy and “reasonable and necessary” logic

Medicare coverage guidance for glycated hemoglobin emphasizes that HbA1c is primarily a monitoring tool for diabetes management and that frequency should reflect clinical need. In practical claims terms, Medicare contractors commonly treat once every 3 months as the standard upper boundary for routine monitoring in non-pregnant adults, with additional testing requiring justification that management has changed or control is inadequate . Local coverage articles operationalize that expectation by linking increased frequency to diagnosis coding patterns and documentation of poor control or treatment intensification .

Medicare preventive screening policy (effective 01/01/2024)

CMS updated diabetes screening policy in the CY 2024 Physician Fee Schedule rulemaking so that HbA1c is now an approved screening test for Medicare diabetes screening benefits, with a simplified frequency allowing up to two screenings in a 12-month period for eligible at-risk beneficiaries . For billing, the operational distinction is the ICD-10: screening claims should be coded as Z13.1 (Encounter for screening for diabetes mellitus) to separate them from diagnostic/monitoring claims. In audit and denial prevention, this separation matters because a screening A1c billed as if it were disease-management monitoring can collide with frequency edits (or appear unsupported if the patient lacks a diabetes diagnosis).

Commercial payer patterns (example: Anthem clinical UM guideline)

Large commercial payers frequently align their HbA1c medical necessity criteria with ADA-style frequency expectations. For example, Anthem’s guideline describes medically necessary outpatient glycated hemoglobin testing, including indications and practical testing intervals tied to stability vs. uncontrolled status or therapy changes . The operational takeaways for billing are consistent: stable control supports fewer tests, and higher frequency requires a defensible clinical trigger (e.g., not meeting goals, medication change, pregnancy, or another documented risk scenario).

Point-of-care HbA1c and CLIA alignment

HbA1c can be performed in physician offices using point-of-care analyzers or in moderate/high complexity laboratories using automated methods. From a payer perspective, the claim must match the lab’s certification level and the test method. Medicare documentation guidance emphasizes that lab services must be ordered by the treating clinician and documented, and that billing entities must meet CLIA requirements relevant to the service billed . When HbA1c is performed in a CLIA-waived office laboratory environment, modifier QW and CLIA number submission are central to passing automated claims edits (details in Section 5).

3. ICD-10 Coverage Examples and Medical Necessity

Because HbA1c is a disease-management and screening tool, ICD-10 coding is the primary mechanism payers use to assess medical necessity. Medicare coverage materials and contractor policies typically expect that the diagnosis reflects abnormal glucose metabolism, diabetes, prediabetes, or a screening encounter under CMS-defined criteria .

Common “clean” ICD-10 pairings

• Type 2 diabetes: E11.9 (Type 2 diabetes without complications) for routine monitoring; E11.65 (Type 2 diabetes with hyperglycemia) when documentation supports poor control and more frequent monitoring is clinically justified .
• Type 1 diabetes: E10.9 for routine monitoring; E10.65 for hyperglycemia-related poor control scenarios where frequency might exceed routine intervals .
• Prediabetes/abnormal glucose: R73.xx category diagnoses may support periodic monitoring or evaluation, but high-frequency use without additional justification can be scrutinized because the diagnosis does not automatically imply “uncontrolled diabetes” .
• Medicare screening: Z13.1 to bill preventive diabetes screening HbA1c under the post-2024 policy update . High-risk denial pattern: HbA1c ordered “routinely” but billed only with unrelated diagnoses (e.g., hypertension-only coding) is a common medical necessity denial scenario. Medicare documentation policy expects the record to support why the test was ordered and why it was necessary for that patient on that date .

Practical rule: When HbA1c is ordered for metabolic risk evaluation (not established diabetes), the assessment should explicitly document the risk rationale (e.g., prior abnormal glucose, obesity with symptoms, history of gestational diabetes) and the claim should carry a diagnosis code that reflects that rationale. If the clinician’s note supports diabetes risk screening and the patient qualifies, Z13.1 is the cleanest Medicare screening pathway post-2024 .

4. Documentation Standards and Lab Record Requirements

Documentation is the most important “payment defense” for HbA1c, especially when frequency is high or when screening vs. monitoring distinctions matter. CMS documentation guidance for laboratory services emphasizes that the medical record must show the clinician’s order/intent and the medical necessity basis for the test, and that the documentation must be retrievable for audit and review .

What auditors and payers typically want to see

Minimum record elements for CPT 83036:

• Order or documented intent: an electronic order entry, signed requisition, or progress note plan indicating HbA1c was ordered .
• Medical necessity rationale: diagnosis and clinical context that justify HbA1c testing on that date (monitoring vs screening vs diagnostic evaluation).
• Result retention: lab report in the chart or a documented result value in the visit note; record retention standards should allow retrieval for compliance reviews .
• Frequency justification (when needed): evidence of poor control, therapy change, pregnancy, or another trigger that makes a shorter-than-90-day interval reasonable. Why frequency and documentation interact: Quarterly testing is broadly consistent with both clinical guidance and many payer expectations. Once frequency exceeds routine intervals, the record has to answer “why now?” clearly. A brief sentence is often sufficient if it is specific (e.g., “A1c 10.2% last visit; started insulin; recheck sooner to assess response”). If the note does not reflect a trigger, claims above routine frequency can appear indistinguishable from unnecessary repeat testing, which is a classic denial and audit pathway .

5. Modifier Use (e.g., QW for CLIA Waived Labs)

Modifier QW (CLIA-waived testing)

When HbA1c is performed using a CLIA-waived method in a waived setting, claims typically must include modifier QW and the laboratory’s CLIA number. CMS coverage and documentation frameworks emphasize CLIA compliance as a condition of payment for lab services, and contractor processing systems use CLIA status plus modifiers to adjudicate claims correctly . In practice, office labs billing Medicare for point-of-care A1c commonly submit 83036QW (or 83036-QW) plus the CLIA identifier to avoid automated denials.

Modifier 91 (repeat clinical diagnostic test)

HbA1c is normally billed as one unit per date of service. If a legitimate clinical repeat occurs on the same day (rare), modifier 91 may be necessary on the subsequent test to signal it was an intentional repeat to obtain a new result (not a duplicate claim line). The clinical record must explain why a repeat was necessary (e.g., unexpected result and new specimen). If the repeat is due to an internal lab error or quality-control failure, the repeat is not a separately billable “clinical repeat” and should not be billed.

Billing hygiene for waived office testing: The most preventable denials are CLIA/QW-related. For a waived office HbA1c, ensure (1) QW is present, (2) CLIA number is on the claim, (3) the device/method is in fact waived, and (4) the patient record shows order/intent and medical necessity .

6. Frequency Limits and Coverage Triggers (Medicare LCDs and Payer Edits)

Core frequency concept: HbA1c reflects multi-week glycemia, so very frequent testing is biologically less informative in stable patients. Coverage policies translate that clinical reality into utilization edits: routine monitoring is typically treated as quarterly at most, and increased frequency must be tied to a clinical trigger and (often) diagnosis coding that indicates poor control or a need for closer monitoring .

Medicare contractor logic (example: Palmetto local article)

Medicare Administrative Contractors may publish local coverage articles that describe diagnosis groupings, coding expectations, and practical frequency parameters. Palmetto’s HbA1c billing and coding article is a commonly used reference for how contractors operationalize “reasonable and necessary” testing and how they interpret higher frequency scenarios . While exact implementation details vary across MACs, the pattern is consistent: routine frequency is expected, and exceptions require clear evidence of inadequate control, treatment changes, or special circumstances such as pregnancy.

Commercial payer triggers (example: Anthem)

Commercial payers frequently implement similar edits. Anthem’s guideline describes scenarios that make more frequent testing medically necessary (for example, not meeting glycemic goals or after therapy changes) and aligns with a stability-based cadence . When billing at high frequency, the claim and record should make the trigger obvious: document the therapy change, cite the prior elevated HbA1c, and use an ICD-10 code consistent with the patient’s state (e.g., hyperglycemia code when appropriate).

Scenario A: Stable diabetes monitoring

Patient: Type 2 diabetes, stable meds, prior HbA1c at goal.

Approach: HbA1c every 6 months (or at least twice yearly), consistent with ADA frequency guidance for stable control .

Billing tip: Use E11.9 (or equivalent). Avoid ordering/testing every visit without a documented rationale.

Scenario B: Therapy change with poor control

Patient: Type 2 diabetes with persistent hyperglycemia; medication intensified.

Approach: HbA1c at ~3 months is typical; a shorter interval may be reasonable if the record clearly explains why and if local coverage guidance supports the scenario .

Billing tip: Use a hyperglycemia-related diabetes code when clinically accurate and document the change and intended action.

Scenario C: Medicare screening

Patient: Medicare beneficiary at risk for diabetes but without a diabetes diagnosis.

Approach: Bill HbA1c as screening using Z13.1 under the post-2024 CMS screening update .

Billing tip: Keep screening claims distinct from disease-monitoring claims to reduce frequency conflicts and denials.

7. Common Denials and Audit Flags

Most HbA1c denials fall into a few repeatable categories. Addressing them systematically reduces rework and audit exposure.

1) Medical necessity denial (unsupported diagnosis)

If the claim carries diagnoses unrelated to glycemic evaluation (or fails to indicate screening), payers may deny as not medically necessary. CMS documentation guidance stresses that the record must support why the test was ordered and that medical necessity is established by the practitioner’s assessment and clinical rationale . The fix is usually straightforward: ensure the assessment documents the indication and that the claim includes the correct ICD-10 (diabetes, prediabetes/abnormal glucose, or Z13.1 for screening) .

2) Frequency/too-soon denial

Quarterly cadence is widely expected for unstable control and is a common payer boundary for routine monitoring. Tests occurring at shorter intervals without documentation of a trigger are frequently denied or requested for records. Use local coverage guidance and payer policy logic as a pre-check: if you are submitting the “fifth test this year,” the record should read like a clinical story that makes the extra test inevitable (poor control, therapy change, pregnancy, or other special circumstance) .

3) CLIA/QW processing denial for office point-of-care tests

Office labs that omit QW (or omit the CLIA number) commonly encounter CLIA-related denials. The safest operational control is to hardwire the billing system so that any 83036 billed by a waived site automatically appends QW and populates the CLIA number field. Documentation policies reinforce that billing must align with compliance requirements for lab services .

4) Payer-specific “quality reporting” denial (Category II requirement)

Some commercial plans tie A1c billing to quality measure reporting and deny 83036 if the HbA1c result range is not reported using Category II codes. Blue Cross Blue Shield of Wyoming published a provider update stating claims for 83036 will be denied if the Category II result code is missing, requiring corrected claims submission . If you receive a denial indicating “missing A1c result code,” this is the issue; the remedy is typically adding the appropriate CPT II code with a $0.00 charge line and resubmitting, per the payer’s instructions .

Fast denial triage checklist (what to check first):

• Diagnosis: Does the claim include diabetes/prediabetes/abnormal glucose, or Z13.1 for screening?
• Frequency: Is the date too soon vs prior HbA1c? If yes, does the note document a trigger?
• CLIA/QW: If performed in-office waived setting, is QW present and CLIA number submitted?
• Payer-specific add-ons: Does the payer require CPT II A1c result reporting? (Example: BCBS Wyoming)

8. Reimbursement Rates (Medicare Fee Schedule & Payer Variances)

Medicare: CPT 83036 is paid under the Clinical Laboratory Fee Schedule (CLFS), meaning it is reimbursed as a lab test fee rather than via physician work RVUs. Medicare laboratory fee schedule amounts update periodically and can shift year to year. For practical planning, use the most current Medicare fee schedule reference relevant to your locality and confirm payment on remittance advice. A commonly circulated 2025 Medicare fee schedule update document lists the Medicare rate for 83036 and other routine labs, illustrating the order of magnitude and the downward pressure seen in lab fee schedule changes over time .

Commercial payers: Commercial reimbursement varies by contract, site of service, and whether the testing is performed in-office or by a reference lab. While HbA1c is generally a lower-cost routine chemistry test, payer-specific policies can materially affect net payment through denials, resubmission requirements (e.g., CPT II reporting), or frequency edits. Therefore, for revenue integrity, the “rate” is often less important than avoiding preventable denials caused by missing screening codes, missing QW/CLIA elements, or noncompliant frequency patterns .

Bottom line for financial accuracy: The highest-yield improvements for CPT 83036 reimbursement are not “coding tricks,” but consistent alignment with (1) the correct purpose (screening vs monitoring), (2) the correct frequency supported by documentation, and (3) the correct CLIA context when the test is performed in-office. CMS documentation policy makes clear that insufficient documentation can lead to post-payment denials even when claims initially pay, so record completeness matters as much as claim completeness .