CPT® Code 82962

Last Updated: January 2026 | Verified for 2026 AMA, CPT & CMS Guidelines

Quick Reference: CPT 82962

• Test type: Quantitative fingerstick (capillary) blood glucose performed with a hand-held glucose monitoring device cleared by the FDA for home use (point-of-care).
• When it is used: Immediate glucose data to guide clinical decisions (diabetes management, suspected hypo-/hyperglycemia, medication adjustment, acute symptoms).
• CLIA status: CLIA-waived when performed with a waived/home-use device and in a site that holds a CLIA Certificate of Waiver. Medicare recognizes certain waived codes without needing modifier QW, and 82962 is on that exempt list .
• Medicare coverage anchor: National Coverage Determination (NCD) 190.20 sets the medical-necessity framework for blood glucose testing and includes guidance on reasonable frequency and indications .
• Bundling hotspot: Fingerstick glucose performed as part of PET scan preparation is considered integral and should not be reported separately, per Medicare NCCI policy .
• Common denial drivers: Missing CLIA number, non-covered ICD-10 diagnosis, screening vs diagnostic miscoding, duplicate same-day testing without a repeat modifier, or billing when the service is bundled into another procedure . CPT 82962 describes a quantitative blood glucose test performed with a glucose monitoring device cleared by the FDA specifically for home use. In practice, it is the standard code for an in-office fingerstick glucometer reading when a point-of-care result is needed. The phrase “home use” often confuses coders: it refers to the device clearance, not the location where the test is performed. If a clinic uses a home-use-cleared glucometer (the common scenario), 82962 is generally the correct reporting pathway for the clinic-side glucose measurement .

This guide focuses on the compliance points that most often determine payment: (1) documentation and CLIA elements that prove the test is a valid waived laboratory service; (2) diagnosis coding and coverage criteria for Medicare and commercial payers; (3) bundling rules (especially PET-related edits); and (4) how to use modifiers when the same patient has multiple glucose measurements on the same day.

1. Code Definition & Clinical Use

CPT 82962 is defined as “Glucose, blood by glucose monitoring device(s) cleared by the FDA specifically for home use.” It represents a quantitative glucose value produced by a point-of-care device, typically using capillary blood from a fingerstick. The defining feature is the device category (home-use-cleared meter), not the patient setting. Coding authorities and payer policies repeatedly treat 82962 as appropriate for office/clinic testing when the clinic uses that kind of device .

Typical clinical scenarios include:

• Diabetes follow-up: A same-visit glucose check to contextualize symptoms, diet, medication adherence, or to support medication titration.
• Symptom evaluation: Immediate testing for dizziness, diaphoresis, confusion, tremor, or weakness when hypoglycemia is in the differential.
• Treatment monitoring: Re-check after intervention (oral carbohydrate, insulin adjustment) when a new value is required to confirm response.
• Procedure-adjacent assessment: Select contexts where glucose changes management (with the crucial caveat that some procedures already include the glucose check under NCCI policy; see coverage section) . A frequent compliance mistake is using 82962 as a substitute for formal laboratory glucose testing. 82962 is a point-of-care measurement; it does not replace ordered lab glucose in settings where the clinical question requires a laboratory analyte with the lab’s method, quality controls, and specimen handling. Conversely, when the clinical purpose is immediate decision-making in a clinic, 82962 is often the most accurate code match.

2. Documentation & CLIA-Waived Rules

Because 82962 is a clinical laboratory service, payment depends on (a) medical necessity and (b) laboratory compliance elements. The documentation standard is straightforward: a reviewer must be able to see why the test was ordered, that it was performed, and what the result was.

Minimum documentation elements

• Reason/indication: A documented diagnosis or symptom rationale (for example: “Type 2 diabetes follow-up,” “suspected hypoglycemia,” “evaluate dizziness”).
• Order and performance: An order can be explicit (provider order) or implied within the clinical note depending on practice policy, but the record should show the clinic intended to perform a glucose test for patient care.
• Result with timestamp: Record the glucose value and time (especially when multiple values occur the same day).
• Clinical action (when relevant): If the result prompted treatment or a change in plan, note it. This becomes critical when a payer challenges repeat testing or high frequency.

CLIA requirements and the QW nuance

The clinic must hold an appropriate CLIA certificate for the complexity level of the testing performed; for waived glucose meter testing, that generally means a CLIA Certificate of Waiver. Claims frequently deny when the CLIA number is missing or mismatched. Many payer guidance documents emphasize that the diagnosis on the claim must support medical necessity and that laboratory services are subject to coverage rules and frequency review .

Medicare often requires modifier QW to identify waived tests. However, CMS publishes a list of codes that are recognized as waived without appending QW, and 82962 is included on that list. CMS’s MLN guidance states these codes “don’t require a QW modifier to be recognized as a waived test” . This means Medicare systems can recognize 82962 as a waived-service code without QW, assuming the CLIA elements are present.

Operational best practice: Even though QW is not required by Medicare for 82962, confirm whether a specific commercial payer’s claims edits expect QW across all waived tests. Some payer policies explicitly discuss how waived tests are handled and may apply their own formatting rules .

3. Common ICD-10 Diagnoses & Indications

Diagnosis coding is the most common driver of denials for office glucose tests. Many payers only reimburse 82962 when linked to a covered indication. Medicare’s NCD 190.20 provides the national framework for when blood glucose testing is reasonable and necessary, including diabetes, suspected hypo/hyperglycemia, and other conditions that affect glucose metabolism .

In day-to-day billing, the most common ICD-10 groupings are:

• Diabetes mellitus (E08–E13): Type 2 diabetes without complications (E11.9), with hyperglycemia (E11.65), Type 1 diabetes codes (E10.-), and diabetes with complications when relevant.
• Hypoglycemia and glucose regulation disorders (E15–E16): For example E16.2 (hypoglycemia, unspecified) when evaluating symptomatic episodes.
• Prediabetes and abnormal glucose findings (R73.-): R73.03 (prediabetes) and related abnormal glucose codes for monitoring of known abnormal findings.
• Screening (Z13.1): Encounter for screening for diabetes mellitus (use with caution; see coverage section on Medicare screening rules) . Commercial payer guidance often lists extensive ICD-10 ranges considered medically necessary for outpatient glucose testing, including diabetes, endocrine disorders, metabolic conditions, and other risk states . The practical rule is to code the most specific known condition that actually motivated testing. If the test was performed to evaluate symptoms, and the result immediately established a condition (e.g., documented hypoglycemia), then coding that established diagnosis is typically stronger than coding only a symptom. If the condition is not yet established, the symptom code may be appropriate for the initial test, but repeat testing without a clearer clinical anchor is more vulnerable to denial under medical-necessity review principles described in Medicare policy .

4. Medicare & Payer Coverage: Frequency, Screening, Bundling

Medicare diagnostic coverage and frequency logic

Medicare covers diagnostic glucose testing when it is reasonable and necessary under NCD 190.20. The NCD’s language supports glucose testing for diabetes and related clinical circumstances and also discusses reasonable frequency patterns, including a commonly cited example: for stable diabetic patients not self-testing, periodic clinic testing such as quarterly monitoring may be reasonable. The policy also implies that unusually frequent testing should be justified by clinical changes, therapy adjustments, or unstable disease .

Separately, Medicare Administrative Contractors may publish billing and coding articles emphasizing that claims must include appropriate ICD-10 codes and that frequency of laboratory services is subject to review. These articles often function as practical enforcement documents: they remind providers that absent a covered diagnosis, testing is not medically necessary and may require an ABN for beneficiary liability .

Medicare screening benefit: what to watch

Medicare’s diabetes screening benefit is distinct from diagnostic testing. Screening coverage rules define eligibility (risk factors, prediabetes) and frequency. NIDDK’s professional guidance summarizes how Medicare expects screening claims to be coded and which CPT codes are typically used for the benefit . Importantly, screening coverage frequently relies on laboratory-based glucose codes (for example fasting plasma glucose or glucose tolerance testing). If a clinic uses a fingerstick meter for screening and bills 82962 with Z13.1, payment can be inconsistent because Medicare’s screening frameworks commonly emphasize lab-based codes and specific billing conventions . When a screening fingerstick produces an abnormal finding, subsequent testing should generally shift to diagnostic coding (e.g., R73.03 or an appropriate diabetes code) rather than continuing to bill screening.

Bundling and “not separately billable” scenarios

Although 82962 is typically separately payable from an E/M service, there are important exceptions. Medicare’s NCCI policy specifically addresses PET scans: a fingerstick glucose performed to prepare for a PET study is considered integral and should not be separately reported with 82962 (or 82948) . This is a common denial scenario: clinics or outpatient departments may attempt to bill the glucose check in addition to the PET code, and the glucose line is denied as bundled.

Another bundling risk is duplicate same-day testing across settings: for example, a clinic bills 82962, while a laboratory panel performed the same day includes glucose. Even when both values exist clinically, payers may treat them as duplicative unless documentation shows distinct purpose, timing, and a clinical reason why both were needed. When a payer challenges frequency or duplication, the underlying theme is the same: billing should reflect distinct medically necessary services, not routine redundancy.

Claims hygiene for 82962: Ensure the CLIA number is present, the diagnosis is covered, and the test is not integral to another procedure under NCCI policy. If multiple same-day tests occur, use repeat-test conventions and document timing and rationale .

5. Modifier Usage (QW, 59, 91)

Modifier QW (CLIA-waived test)

QW indicates a waived methodology for Medicare billing. CMS guidance clarifies that certain codes, including 82962, are recognized as waived without requiring QW . Practically, that means Medicare payment should not depend on QW for 82962. However, some payer systems or intermediaries may still accept QW and ignore it. The more important compliance element is that the performing site is properly certified and the claim includes the CLIA number.

Modifier 91 (Repeat clinical diagnostic laboratory test)

Use modifier 91 when the same laboratory test is repeated on the same patient on the same day to obtain additional clinical results (not to correct an error or perform quality control). For 82962, this is most common when a second glucose value is needed after treatment, or when monitoring is clinically required during the same date of service. Documentation should show the timing and reason for repeating the test (symptoms persisted, post-treatment confirmation, or a new clinical episode). This aligns with Medicare’s broader principle that repeat testing must be medically necessary and supported by record evidence .

Modifier 59 (Distinct procedural service)

Modifier 59 is used to indicate that two services normally bundled were distinct. For glucose testing, its most defensible use is when two different glucose testing methodologies (or two different contexts) are billed on the same day and there is a legitimate reason for both, such as an immediate fingerstick followed by a confirmatory lab glucose performed later with a different specimen and a different clinical purpose. Medicare billing guidance frequently cautions against using modifiers to bypass edits unless the circumstances truly meet criteria, and supporting documentation is essential . In routine office practice, 59 is not required to bill 82962 alongside an E/M service.

6. Comparison to Related CPT Codes

Select the glucose code based on the method and clinical context. The most important distinction is whether testing is performed using a home-use-cleared point-of-care device (82962) versus a laboratory method or a structured glucose tolerance procedure.

If your clinic workflow is “fingerstick in the room for an immediate number,” 82962 is usually the correct code. If your workflow is “venipuncture and lab analyzer,” it is generally not. When both occur, document why both were needed and expect payers to evaluate duplication.

7. Clinical Use Cases & Coding Examples

Case 1: Diabetes follow-up in primary care

Scenario: Patient with Type 2 diabetes comes for quarterly follow-up; clinic performs a fingerstick glucose using a home-use-cleared meter.

Billing: 82962 plus the appropriate E/M code. Diagnosis: E11.9 (or a more specific diabetes code).

Why it pays: Diagnostic glucose testing for diabetes aligns with NCD 190.20 principles and common payer covered indications .

Case 2: Symptomatic hypoglycemia with repeat confirmation

Scenario: Patient becomes diaphoretic and shaky in clinic; initial fingerstick is low; after oral carbohydrate, repeat glucose confirms improvement.

Billing: 82962 for the first test and 82962-91 for the repeat on the same day. Diagnosis: E16.2 (hypoglycemia) or most specific appropriate diagnosis.

Why it pays: Repeat testing is supported when a new clinical result is necessary for patient care; modifier 91 communicates repeat diagnostic testing .

Case 3: Screening request in an at-risk Medicare beneficiary

Scenario: Patient requests diabetes screening; clinic considers a fingerstick test during a preventive visit.

Billing caution: Medicare screening frameworks have specific coding conventions and often emphasize lab-based glucose screening codes; verify benefit rules and correct screening diagnosis reporting before billing. Consider directing the patient to an eligible screening lab test pathway consistent with Medicare screening guidance .

Compliance tip: If screening is likely non-covered, obtain appropriate beneficiary notice and document the screening intent.

Case 4: PET scan pre-check (bundled)

Scenario: Fingerstick glucose is performed immediately prior to PET imaging as part of the imaging protocol.

Billing: Do not bill 82962 separately for the PET-related glucose check; it is integral to the imaging service per Medicare NCCI policy .

Case 5: Duplicate same-day lab glucose plus fingerstick

Scenario: Clinic performs fingerstick glucose for immediate decision, then orders a confirmatory laboratory glucose later the same day due to an unexpected result.

Billing: Avoid routine duplication. If both are billed, document distinct purpose/timing/specimen and consider modifier 59 on the secondary service only when criteria truly apply, recognizing payer scrutiny of modifier usage .

Best practice: When clinically acceptable, separate dates or use a clear confirmatory pathway to reduce “duplicate analyte” denials.

Across all cases, payment success for 82962 is typically driven less by the code itself (which is stable) and more by the supporting claim logic: correct diagnosis, correct CLIA elements, correct modifier selection for repeats, and avoidance of known bundling scenarios.