CPT® Code 80307

• CPT 80307 Definition: Presumptive drug testing performed using instrument chemistry analyzers (or equivalent high-complexity instrumented methods) to provide qualitative (present/absent) screening for any number of drug classes in a single testing session. It is generally reported once per date of service because the service is bundled per day rather than per drug class.
• Method (What makes 80307 “high complexity”): 80307 reflects testing performed on larger, instrumented laboratory platforms (for example automated immunoassay analyzers). It is distinct from the simpler presumptive codes 80305 (visual read) and 80306 (instrument-assisted read) by virtue of the instrumented chemistry analyzer methodology. Facilities performing 80307 must meet applicable laboratory certification rules and claims must be supported by the appropriate laboratory credentials.
• When it is typically medically necessary: Common medical uses include (1) evaluation of suspected overdose or poisoning in urgent settings, (2) monitoring adherence and safety in chronic opioid therapy, and (3) structured monitoring in substance use disorder treatment programs when results affect clinical decisions (dose adjustment, safety counseling, diversion risk mitigation). Payers generally expect documented clinical rationale rather than routine “screen everyone” protocols.
• Documentation requirements that drive payment: A valid provider order is expected, along with chart documentation supporting medical necessity and retention of the test report. LCD/Article guidance emphasizes that the ordering clinician’s record must support why the test was needed on that date, and the performing laboratory must retain the order and report. Missing or inadequate orders are a common denial reason in payer medical review.
• Billing frequency limitations: Presumptive testing codes 80305–80307 are typically treated as one per patient per date of service. Billing multiple presumptive tests on the same date is generally not payable under typical Medicare and payer edits. Frequency beyond common policy norms (for example very frequent ongoing monitoring) increases audit risk and should be supported with specific risk stratification and clinical rationale.
• Medicare coverage framework: Medicare Part B covers medically reasonable and necessary drug testing under contractor guidance (LCDs/Articles) rather than a single national policy, and expects an order from the treating provider, proper documentation, and adherence to coding and frequency rules. Non-medical purposes (employment, law enforcement, purely administrative testing) are not covered as clinical diagnostic services.
• Medicaid & commercial payer variation: Medicaid programs and commercial payers often publish explicit utilization limits or prior-authorization rules for ongoing monitoring. Managed care reimbursement policies may set annual limits and state-specific caps. You should check the member’s plan policy to confirm frequency limits, covered indications, and whether confirmatory (definitive) testing is restricted to specific circumstances.
• Payment mechanics (fee schedule, not RVU): 80307 is paid under laboratory fee schedules rather than physician work RVUs. Medicare fee schedule publications (including state implementations) show substantially higher payment for 80307 compared with 80305/80306 because of the instrumentation and lab complexity. There is no separate professional component; the performing lab bills the global service.

CPT 80307 is a presumptive (screening) drug test code that describes qualitative drug class screening performed by instrument chemistry analyzers or similar instrument-based methodologies. In practical terms, it represents a laboratory-run drug screen that reports whether one or more drug classes are present or absent in a specimen (commonly urine, but potentially other specimen types depending on the laboratory method). Because it is presumptive, the result is typically qualitative: “positive” or “negative” for each drug class included in the method, rather than an exact concentration.

The key billing concept is that 80307 is reported as a single bundled service per date of service for the presumptive session, regardless of the number of drug classes included. In other words, you do not bill multiple units because the panel screens multiple classes. The code selection is driven by the methodology (instrumented analyzer) rather than the number of substances screened. Medicare coding policy manuals and contractor billing guidance reinforce that presumptive testing is bundled per day and that multiple presumptive services on the same date are generally not payable.

How 80307 fits among presumptive codes (80305–80307): CPT uses three sibling presumptive codes distinguished mainly by the level of instrumentation and interpretation method. CPT 80305 describes a test read by direct optical observation (a visually read cup/card). CPT 80306 describes an instrument-assisted read. CPT 80307 is reserved for instrumented chemistry analyzers or similar laboratory instrumentation. Coverage and coding guidance generally expects providers to choose the code that matches the method actually used, and to avoid billing more than one presumptive code on the same day for the same patient.

Presumptive vs definitive testing: Presumptive testing is designed for screening and triage. Definitive testing identifies specific drugs or metabolites with higher analytic specificity and may include quantitation, depending on the method and payer coding system. Medicare and many payers generally permit at most one presumptive and one definitive test per date of service when medically necessary, but do not expect routine “screen + confirm everything” behavior without a documented rationale. This principle appears in contractor guidance and is also reflected in payer medical coverage criteria emphasizing that the test must be used to guide treatment decisions.

Specimen validity and related checks: Many laboratories perform validity checks (for example assessing adulteration indicators) as part of their standard workflow. Contractor guidance and payer policies often treat these checks as inclusive to the drug testing service rather than separately billable add-ons for routine use. As a result, documentation should reflect that the reported presumptive result is based on an acceptable specimen, but billing should follow payer rules on what is bundled or separately payable.

Documentation & Ordering Requirements

80307 is frequently reviewed because drug testing is susceptible to both overutilization and documentation gaps. Successful reimbursement depends on a simple standard: the record should allow an external reviewer to answer what was ordered, why it was needed, what was performed, and how the result affected care. Medicare contractor billing guidance for urine drug testing emphasizes that the test must be ordered by the treating provider and supported by documentation establishing medical necessity for the date of service.

• Provider order: Maintain a clear, authenticated order (paper or electronic) from the treating clinician. Policies often expect that the order identifies the testing scope (drug classes or testing intent) and ties it to the clinical purpose. A vague “UDS” order may be challenged if payer policy expects specificity or if utilization is high.
• Medical necessity in the clinical note: The progress note should document the clinical rationale. Examples that typically align with medical necessity include: monitoring adherence and safety for controlled substances; evaluating unexpected behavior (early refill requests, lost prescriptions, signs of intoxication); reassessing risk during initiation or escalation of opioid therapy; or assessing suspected overdose in acute settings. Payer coverage criteria often emphasize suspicion/risk and intended clinical use of results rather than routine blanket screening.
• Retention of the test report: The ordering provider should retain the report in the medical record (or have reliable access) and the performing laboratory should retain the order and results consistent with applicable requirements. Contractor guidance frequently focuses on whether the performing entity can produce the order and test report upon request.
• Frequency justification: If testing is repeated at short intervals, document why the patient’s risk level and clinical situation justify the frequency. Examples include early phases of treatment, recent positive results, evidence of instability, or safety concerns requiring closer monitoring. Frequency limits are often explicit in managed care reimbursement policies; exceeding those limits typically requires strong justification and may still require prior authorization or appeal.
• Laboratory certification alignment (CLIA): 80307 generally requires an appropriately certified laboratory environment. If testing is performed in-office, documentation and billing must reflect the correct CLIA certificate level and payer requirements. State Medicaid guidance and other payer guidance emphasize CLIA compliance and correct billing for waived vs non-waived testing, including when modifier QW is required.

Documentation is especially important when both presumptive and definitive tests are performed on the same date. While this can be clinically appropriate (for example, a presumptive screen triggers definitive confirmation for an unexpected positive), payers often scrutinize whether confirmation was limited to clinically necessary cases rather than routinely performed for every screen. A defensible record typically includes: the initial screen result, why confirmation was required, and how the confirmed result influenced management.

Payer Policies & Coverage

Medicare (Part B) framework: Medicare covers drug testing when it is medically reasonable and necessary and ordered by the treating provider, with coverage details often implemented through contractor LCD/Article guidance rather than a single national coverage decision for routine screening. Contractor billing and coding articles stress adherence to coding rules (including unit limits) and documentation requirements, and clarify that non-medical purposes are not covered as clinical diagnostic testing.

Typical Medicare coverage scenarios: Medicare commonly recognizes drug testing as reasonable and necessary when used for (1) monitoring compliance and safety in chronic pain management with controlled substances, (2) monitoring and treatment planning in substance use disorder, and (3) evaluation in certain acute scenarios (for example suspected poisoning). The claim should include diagnoses and clinical documentation consistent with these indications.

Frequency controls: Even when an indication is covered, frequency can be denied if it exceeds policy expectations. Medicare coding policy emphasizes that presumptive testing is a bundled per-date-of-service service and generally expects one presumptive test per day. Managed care plans often add annual limits and state-specific rules. A practical compliance approach is to design testing frequency using a documented risk stratification model (stable vs higher-risk) and to reassess and document changes over time.

Commercial payers: Commercial payer medical policies commonly require documented suspicion or monitoring rationale and enforce the one-per-day presumptive rule. They may also restrict extensive definitive panels or require that definitive testing be targeted to positives or clinically ambiguous findings. In practice, commercial denials often fall into two categories: (1) “not medically necessary” due to lack of documented risk/indication, or (2) “frequency exceeded” due to repeated testing without documented changes in risk profile.

Medicaid and managed Medicaid: Medicaid programs frequently publish utilization limits (annual caps and/or per-month limits) and may require prior authorization beyond thresholds. Managed Medicaid reimbursement policies sometimes consolidate those rules and list state-specific exceptions. For providers with multi-state populations or reference laboratories servicing multiple states, operational controls (eligibility checks, benefit configuration, and prior-auth workflows) are critical to avoid predictable denials.

Payment basis: 80307 is paid under laboratory fee schedules, and published fee schedules demonstrate a significant payment differential between 80307 and lower-tier presumptive codes, reflecting method complexity. These payment differences are one reason payers apply stricter documentation and utilization oversight to high-complexity presumptive testing.

Modifier Usage

Modifiers are not the primary driver of correct 80307 billing; the primary driver is correct code selection and correct frequency. Because 80307 is generally intended as one service per date of service, modifiers will rarely convert an otherwise nonpayable second presumptive test into a payable service. Nevertheless, certain modifier concepts appear in payer rules and in CLIA-related billing requirements.

• Modifier QW (CLIA-waived): QW applies to tests that are CLIA-waived and billed to payers (notably Medicare) that require the waived modifier. Most 80307 testing is not waived because it is instrumented analyzer testing, but payer and Medicaid guidance emphasizes verifying whether the method is waived and, if waived, billing it correctly. Providers should rely on official waived-test lists and state Medicaid guidance when configuring claims.
• Modifier 91 (repeat clinical diagnostic test) and similar repeat modifiers: Repeat modifiers are designed for clinically necessary repeated testing on the same date. For 80307, repeated same-day billing is generally inconsistent with the “one per date of service” presumptive structure and will usually be denied by payer edits even if a repeat modifier is appended. If there is a rare scenario requiring rerun on a new specimen for clinical reasons, the documentation burden is high and payment is still uncertain because the unit limit is inherent to the code’s use and payer edits.
• Modifier 59 (distinct service): Modifier 59 is not a routine modifier for 80307. It should not be used to attempt to bill more than one presumptive drug screen on the same date. In narrow payer-specific scenarios, it may be used to distinguish services when a payer incorrectly bundles different code families; however, the more reliable solution is usually to ensure the claim and documentation clearly show presumptive vs definitive service and to appeal incorrect bundling.

Operational takeaway: For 80307, focus on (1) correct code selection (80305 vs 80306 vs 80307), (2) CLIA compliance and QW where applicable, and (3) documented medical necessity and frequency support. Modifiers are secondary and should be used only when aligned with payer policy and the facts of the encounter.

Comparisons to Related Codes

flowchart TD
    A[Presumptive Drug Screen Ordered] --> B{What method was used?}
    B -->|Visual read<br>cup/card/dipstick| C[CPT 80305]
    B -->|Instrument-assisted read| D[CPT 80306]
    B -->|Instrument chemistry<br>analyzer| E[CPT 80307]
    E --> F{Same patient,<br>same date of service?}
    F -->|First presumptive test| G[Bill 80307 x1]
    F -->|Already billed<br>presumptive today| H[Do NOT bill again]
    G --> I{Unexpected or<br>ambiguous result?}
    I -->|Yes, clinical need documented| J[May order definitive testing]
    I -->|No| K[Use result for<br>clinical decisions]

80307 vs 80305 vs 80306: These are all presumptive screening codes. The practical distinction is method complexity and instrument reliance. 80305 generally corresponds to visually read point-of-care tests; 80306 corresponds to instrument-assisted reading; and 80307 corresponds to instrument chemistry analyzers or similar instrumented laboratory workflows. Correct selection depends on how the test was actually performed, not on how many drug classes were included. In each case, the service is reported as a single presumptive test per date of service for that patient.

80307 vs definitive testing (contextual overview): Presumptive testing indicates potential presence/absence of drug classes and can have cross-reactivity or limited specificity depending on assay design. Definitive testing is used to confirm and identify specific drugs/metabolites with higher specificity. Payers often expect definitive testing to be targeted (for example confirm unexpected positives) rather than performed reflexively for every presumptive test without a documented reason. Contractor guidance and payer medical policies emphasize using test results for clinical decision-making rather than for routine, non-indicated screening.

80307 and E/M services on the same date: The lab test is separately billable from an office visit when the practice is the performing lab and meets certification requirements, and when the test is medically necessary and ordered. The ordering and clinical interpretation of results generally contributes to medical decision-making for the visit, but the test itself is billed as the laboratory service by the performing entity. Contractor guidance on pathology/lab coding and billing articles address how lab services are reported and documented; the most common billing errors involve missing orders or billing by an entity that did not actually perform the test.

Clinical Use Scenarios (with Coding Rationale)

Scenario 1: Emergency department evaluation for suspected overdose

Clinical situation: A patient presents with altered mental status and suspected poisoning/overdose. The clinician needs rapid screening information to support immediate decisions (airway management, antidotes, and differential diagnosis). A hospital laboratory runs an instrument-based presumptive screen on an analyzer and reports qualitative results.

Coding logic: The laboratory reports 80307 once for that date of service because the presumptive screen is bundled per day and methodology matches instrument analyzer testing. Documentation should include the provider order and the acute indication supporting medical necessity. Contractor billing guidance emphasizes that the service must be ordered and medically necessary, and that non-medical purposes are not covered; acute diagnostic evaluation is generally aligned with covered clinical testing.

Scenario 2: Chronic opioid therapy monitoring in an established patient

Clinical situation: A patient on long-term opioid therapy is monitored for adherence and safety. The clinician orders a presumptive drug test because of a risk factor (for example, inconsistent refill timing or concerning behavior). The practice uses an instrumented analyzer method (or sends to a lab that uses such a method).

Coding logic: The performing laboratory bills 80307 once for that date. The key compliance components are (1) a documented order, (2) chart documentation tying the test to clinical risk and intended use of results, and (3) results retained in the record. Payer medical policies and contractor guidance repeatedly focus on necessity and documentation rather than routine protocols.

Scenario 3: Substance use disorder program monitoring

Clinical situation: A patient enrolled in treatment has periodic monitoring. The frequency may be higher during initiation and stabilization and lower during maintenance. A reference lab runs an instrumented presumptive test.

Coding logic: The lab bills 80307 once per date of service, but program frequency should be aligned with payer rules. Managed Medicaid reimbursement policies may set annual caps and state-specific limits, which means the same clinical protocol can be payable in one state and denied in another if the cap is exceeded without prior authorization.

Scenario 4: Low-risk routine screening at an annual physical (often not covered)

Clinical situation: A generally healthy patient receives a drug screen without documented risk factors, suspicion, or a management need. This is often considered routine screening without medical necessity.

Coding logic: Even if a test was performed, many payer policies treat routine, non-indicated screening as not medically necessary. Contractor guidance focuses on clinical diagnostic use ordered by the treating provider for patient care; testing performed for administrative or non-medical purposes is not covered as a diagnostic benefit.

State-Specific Rules & Variations

State variation is most pronounced in Medicaid programs and managed Medicaid plans, which frequently publish specific numeric limits and prior authorization triggers. Even when code definitions are national, utilization controls can differ substantially by state and by managed care organization. Reference laboratories and multi-site practices should implement benefit-aware ordering rules to reduce predictable denials.

• State Medicaid bulletins (example): Louisiana has published Medicaid policy updates limiting presumptive urine drug testing frequency and also limiting definitive testing frequency. Such bulletins are authoritative for that state’s Medicaid program and are often enforced through claims edits.
• Managed Medicaid reimbursement policies (example): Managed care policies may set a default annual limit (for example a fixed number of payable dates of service per year) while also listing state-specific exceptions. These policies matter operationally because even within Medicaid, coverage may vary between fee-for-service Medicaid and managed plans.
• CLIA compliance reminders (example): State Medicaid agencies can publish reminders clarifying which tests require what level of certification and how to bill waived tests. These are particularly important for office-based testing, where the most common compliance errors involve billing non-waived tests under a CLIA waiver or failing to follow waived-billing rules.

Practical approach for multi-state operations: configure ordering and billing systems to (1) identify payer type (Medicare, Medicaid FFS, managed Medicaid, commercial), (2) apply state-specific Medicaid caps where applicable, (3) prevent duplicate same-day presumptive billing, and (4) prompt clinicians to document risk and rationale when frequency increases. The overarching goal is consistent: match utilization to clinical risk and payer rules, and ensure the record supports why each test was medically necessary.