CPT® Code 96375

Add-On Code

Quick Reference

• What it represents: Each additional sequential IV push of a new substance/drug after an initial IV push service in the same encounter.
• Add-on code: Never bill alone. Report only with an appropriate “initial” parent code (commonly 96374, or an initial infusion when an infusion is the primary service).
• Not for repeats of the same drug: For a repeat IV push of the same medication in a facility setting, the repeat-push concept is addressed differently (see 96376 discussion), and payers commonly deny “same-drug” use of 96375.
• Documentation must show sequence: Medication name, dose, route, and the order and timing of pushes should be clear enough for an auditor to reconstruct what was administered and when.
• Facility vs professional billing matters: Many payer policies specify these drug administration codes are not separately payable to the physician in facility settings, where the facility bills the administration service.

CPT 96375 is a high-frequency revenue-integrity code in emergency medicine, infusion centers, and outpatient practices because it sits at the intersection of coding hierarchy, sequence/timing documentation, and payer edits. Most denials occur for predictable reasons: the add-on is billed without a valid parent service, charting fails to establish a sequential push of a new substance, or the claim is submitted on the wrong biller (for example, a professional claim in a hospital outpatient setting where the payer expects the facility to bill the drug administration).

This guide expands the core rule into operational steps: identify the initial service for the encounter, confirm that each additional push is (1) sequential, (2) a different drug, and (3) supported by time/sequence documentation. It also explains common payer policy positions and how to build documentation that survives routine post-payment review.

IV Push Billing Decision Tree

flowchart TD
    A[IV Push Administered] --> B{Is this the first<br/>IV push in the encounter?}
    B -->|Yes| C[Bill 96374<br/>Initial IV Push]
    B -->|No| D{Is it a different<br/>drug/substance?}
    D -->|Yes| E[Bill 96375<br/>Sequential new drug add-on]
    D -->|No| F{Facility setting?}
    F -->|Yes| G[Consider 96376<br/>Facility repeat-push logic]
    F -->|No| H[Not separately billable<br/>as 96375]
    C --> I{Additional pushes<br/>in encounter?}
    I -->|Yes| D
    I -->|No| J[Claim complete]
    E --> I

1. Official Definition & Clinical Use of CPT 96375

CPT 96375 is defined as: “Therapeutic, prophylactic, or diagnostic injection (specify substance or drug); each additional sequential intravenous push of a new substance/drug”. The words that drive compliance are each additional, sequential, intravenous push, and new substance/drug.

Add-on structure. 96375 is an add-on code and must be paired with an appropriate primary drug administration service (for example, an initial IV push such as 96374 when that is the initial service for the encounter). If it appears without a parent code, claim systems commonly reject it because add-ons do not represent standalone billable procedures.

Clinical reality. In practice, 96375 is used when a patient receives an initial IV push of one medication and then receives a subsequent IV push of a different medication during the same encounter. A typical ED scenario is an antiemetic IV push followed by an analgesic IV push after reassessment. The key is that these are two distinct medications administered one after the other through the IV route, rather than the same medication repeated.

Non-chemotherapy family. 96375 belongs to the therapeutic/prophylactic/diagnostic injection and infusion code family (96360–96379) rather than chemotherapy administration codes, and coding guidance emphasizes applying the correct hierarchy based on the service intensity and definition.

2. Documentation Requirements (Sequence & Timing)

Documentation is what converts a “medication administration event” into a defensible 96375 claim line. Payers often do not dispute that drugs were given; they dispute that the record proves the second administration qualifies as a billable sequential push of a new drug.

Minimum elements per push

For each IV push documented in the chart, include:

• Drug name (and concentration if relevant)
• Dose and units
• Route (IV push)
• Administration time (or start time; push is typically brief)
• Who administered and evidence that the administration met supervision/monitoring expectations
• Indication/medical necessity (symptom treated or clinical purpose)

Medicare and MAC education materials emphasize sequence and timing for infusion/injection coding and the importance of capturing enough information to establish the relationship between initial and subsequent services.

Establishing “sequential” vs “concurrent”

“Sequential” means one service is completed before the next begins. For IV pushes, the easiest way to demonstrate sequential administration is to document distinct administration times (for example, “10:15” then “10:30”). When timestamps are missing or identical, payer reviewers may interpret the administrations as concurrent or may conclude the record does not support a sequential code. If medications are given through separate IV sites at similar times, documentation should clarify that separate access sites were clinically necessary; otherwise, sequence ambiguity can trigger bundling edits.

15-minute concept and time clarity

Many coding resources treat infusions of 15 minutes or less as IV push equivalents for code selection purposes, which makes timing documentation important for correct classification. If infusion start/stop times are absent, reviewers may downgrade an infusion claim to a push model or deny add-on time-based services. The operational takeaway is simple: document times consistently, and when an infusion occurs, document start and stop times so the service cannot be misclassified.

Audit-proofing tip: If you bill 96375, your chart should make it obvious (1) what the initial drug was, (2) what the subsequent new drug was, and (3) that the subsequent administration occurred after the initial push was completed. MAC education materials repeatedly highlight sequence and documentation as the basis for correct add-on reporting.

3. Billing Guidelines, Bundling Rules, & Modifiers

The billing rules for 96375 are built around three pillars: add-on structure, hierarchy/sequence, and bundling edits.

Add-on code billing mechanics

Because 96375 is an add-on, it is reported in addition to the initial administration code for the encounter and is not subject to multiple-procedure reduction logic in the same way as primary procedures. The parent code depends on what service was “initial” under hierarchy rules, which can vary when infusions are also performed (for example, an initial infusion may supersede an IV push as the “initial” service). MAC guidance and payer policies discuss this hierarchy approach and how subsequent services attach to the initial.

Sequential vs concurrent and “new drug” requirement

96375 requires the subsequent IV push be a new substance/drug. If the same drug is administered again, many coding frameworks do not allow 96375, and payer policies commonly enforce that by denial. Facility-only repeat-push logic is typically handled differently (see the 96376 comparison section).

Bundling of routine supplies and incidental services

Routine supplies (IV start kits, tubing, syringes), typical line maintenance, and related minor services are generally considered integral to the administration service and are not separately billable under standard bundling logic. Similarly, minimal “keep vein open” fluids between pushes are commonly treated as incidental hydration rather than separately payable hydration therapy in many coding policies.

Modifier 59 and distinct-service logic

Distinct-service modifiers typically matter most when a second “initial” administration code is needed on the same date of service due to a truly separate encounter or separate IV access site. MAC education describes the concept that a second initial code may require a distinct-service modifier to avoid duplicate denial when circumstances justify it. In routine single-encounter scenarios, 96375 itself usually does not need modifier 59, because its add-on nature already implies it is a subsequent service.

E/M services on the same day

Drug administration services are valued to include typical pre- and post-service work and minimal supervision/assessment. Payer policy documents and NCCI-based concepts frequently describe how low-level E/M services (notably 99211) are not separately payable with drug administration and that any separate E/M must be significant and separately identifiable, commonly requiring modifier 25 on the E/M code. A common compliance approach is to bill an E/M only when there is documented decision-making beyond the inherent work of administering the medication (for example, a separately documented evaluation of a distinct complaint or a medically necessary reassessment that changes management, not merely routine monitoring).

4. Medicare (2026) Guidelines and MAC Policy Themes

Medicare’s drug administration logic typically tracks CPT definitions and is operationalized through MAC education, NCCI edits, and claims processing rules. Noridian’s educational materials on injection/infusion services are frequently used as reference points for sequence rules, bundling, and the distinction between chemotherapy-level and non-chemotherapy services.

“Initial” vs “sequential” in Medicare processing

Medicare commonly allows only one “initial” administration per patient per day per encounter logic, unless documented circumstances justify a second initial service as distinct (for example, a separate return encounter later the same day). In that framework, 96375 attaches as the sequential add-on for each additional new-drug IV push after the initial service.

Facility vs professional billing expectation

In hospital outpatient departments and similar facility settings, the facility typically bills the drug administration services. The NCCI-based concepts and payer policies repeatedly emphasize that professional billing of these services in facility settings is generally not appropriate, because it would duplicate facility payment. This is one of the most common reasons for denial when clinicians attempt to bill 96374/96375 on a professional claim tied to a hospital place of service.

Complex vs non-complex administration clarification (2025 onward)

Noridian’s guidance references broader CMS clarifications on how to evaluate whether administration services meet “complex” chemotherapy-level definitions versus routine therapeutic administration codes. Operationally, if an IV push qualifies under chemotherapy administration criteria (based on intensity and monitoring requirements described in payer guidance), chemotherapy push codes may apply rather than 96374/96375. The practical relevance for 96375 is boundary-setting: it remains the correct add-on for routine therapeutic sequential pushes of new drugs, but it should not be used to represent services that meet chemo-level administration definitions.

5. Private Insurer Policies (Aetna, BCBS, UHC, Cigna)

Most commercial payers follow CPT hierarchy concepts but implement them through payer-specific reimbursement policies and claims edits. Two common themes appear in major payer documents: (1) professional billing limitations in facility settings, and (2) bundling of supplies and low-level E/M with drug administration services.

BCBS policy approach

BCBS policies often outline initial versus sequential logic in a way that mirrors CPT definitions and explicitly discuss that sequential IV push add-ons apply after the initial service and require proper identification of substances and timing. BCBS Oklahoma’s therapeutic injection and infusion coding policy is an example of a payer document that summarizes the initial-versus-sequential structure and reinforces correct categorization.

UnitedHealthcare professional reimbursement approach

UnitedHealthcare’s professional reimbursement policy states that certain injection and infusion administration codes (including the 96372–96379 family) are not intended to be reported by the physician in facility settings, aligning payment responsibility with the facility in those scenarios. UHC’s policy also discusses bundling concepts and emphasizes that routine supplies and related services are included in the administration payment and are not separately reimbursed. For office settings, UHC also describes the need for modifier 25 on a separately identifiable E/M when it is legitimately billed with drug administration.

Other large payers often adopt similar logic even when document formatting differs: they expect one initial service per encounter/day unless clearly distinct, they enforce “new drug” rules for sequential codes, and they apply bundling to minimize line-item fragmentation. The compliance strategy is therefore consistent across payers: match the code to the clinical sequence, document timing and necessity, and bill the correct entity (facility vs professional) for the administration.

6. Typical 2026 Reimbursement & RVUs (MPFS & OPPS)

Payment behavior for 96375 differs materially between the physician fee schedule world and the hospital outpatient prospective payment system world.

MPFS (professional / non-facility) concept

Under MPFS concepts summarized in fee schedule materials, 96375 tends to have low total RVUs and minimal or no physician work component because it primarily reflects clinical staff time and practice expense in an office setting. The ASH summary of the CMS 2025 MPFS final rule provides a reference table of values used to understand relative magnitude and typical payment ranges for codes such as 96374 and 96375. In facility settings, the professional practice expense component is typically not paid, which is why many payers do not reimburse the professional claim for these administration services in hospital outpatient settings.

OPPS (facility) packaging concept

Under OPPS, add-on drug administration codes are often treated as packaged services. Noridian’s OPPS status indicator reference describes packaging status logic (including “N” packaged concepts), which helps explain why add-on codes like 96375 may not generate separate APC payment even though they are still reported for data and rate-setting. Facilities often still report 96375 to represent the clinical work performed, but payment is commonly wrapped into the broader visit or primary service payment.

Practical takeaway: For many payers, 96375 is a “documentation-sensitive” code with relatively modest standalone payment in non-facility professional settings and frequent packaging in facility payment models. Billing accuracy still matters because coding errors can cause denials, recoupments, or distort facility cost reporting.

7. Common Audit and Denial Issues with Sequential IV Pushes

Denials for 96375 are usually traceable to one of a handful of repeatable patterns. Addressing these patterns systematically can meaningfully reduce rework and appeal volume.

Denial pattern: add-on without parent

Because 96375 is an add-on, claims lacking the appropriate initial administration service frequently deny outright. Prevent this by validating that the claim includes the correct initial code for the encounter’s hierarchy and that it is not being suppressed by payer edits.

Denial pattern: “same drug” billed as 96375

96375 requires a new substance/drug. If the same medication is pushed twice, payers may deny the second administration when billed as 96375 because it conflicts with the descriptor requirement. If the scenario is a facility repeat-push situation, ensure that facility reporting follows the appropriate facility-only repeat structure rather than treating it as a “new drug” sequential push.

Denial pattern: timing/sequence not supported

When the record does not clearly show sequential order—especially when timestamps are missing or identical—reviewers may determine the service is not supported or is improperly characterized as sequential. Standardize nursing documentation so medication administrations appear with distinct times and a clear order of events. Where infusions occur, document start/stop times to prevent push/infusion misclassification.

Denial pattern: billed on professional claim in a facility setting

Professional claims for administration services in hospital outpatient settings are frequently denied under payer policies that assign those services to the facility. UHC’s policy language is explicit about this expectation and is representative of how other payers approach professional billing in facility contexts.

Denial pattern: E/M unbundling

Billing low-level E/M services with drug administration codes can deny because administration services include typical minimal visit work. If an E/M is legitimately separate, ensure it is clearly documented and billed with modifier 25 as required by payer rules.

Operational control example: “Two pushes, one claim”

Good chart: “Ondansetron 4 mg IV push at 10:12 for nausea; pain reassessment at 10:25; ketorolac 15 mg IV push at 10:28 for pain; patient monitored, no adverse reaction.”

Why it supports 96375: Two distinct drugs, clearly sequential, documented timing and necessity; aligns with sequential add-on concept.

8. Related Codes: 96374 (Initial IV Push) vs 96375 vs 96376

Correct use of 96375 depends on understanding the “initial” and “repeat” concepts around it. The following comparison focuses on functional differences rather than memorizing descriptors.

The practical decision tree is: determine which service is “initial” for the encounter, then decide whether each additional push is a different medication (96375) or a repeat of the same medication under the applicable reporting rules (often facility-only repeat structure). When the setting is a hospital outpatient department, also confirm whether the claim is being submitted by the correct entity—many commercial payers expect the facility, not the physician, to bill the administration service.

9. Recent Changes in 2025–2026 Guidance

For 96375 specifically, 2025–2026 is best described as a period of clarification and enforcement rather than descriptor changes. The add-on definition and “new drug” requirement remain stable. What has evolved is how consistently payers apply hierarchy and intensity concepts across drug administration services.

Complex administration boundary-setting. CMS-related clarifications summarized in MAC educational materials emphasize evaluating the intensity of monitoring and supervision when determining whether chemotherapy-level administration codes apply versus routine therapeutic administration codes. For organizations administering biologics or high-risk therapeutics, the main operational impact is ensuring the correct administration family is used and that documentation supports whichever family is billed. This does not change how 96375 works; it reinforces that 96375 is for routine therapeutic sequential pushes of new drugs and should not be used when the service clearly meets a different code family’s definition.

Reimbursement dynamics and packaging. Fee schedule and OPPS packaging concepts continue to shape the financial reality of add-on administration codes. MPFS value tables and OPPS status indicator references help teams understand why professional payment can be modest in non-facility settings and absent/packaged in facility settings.

Compliance trend. Across payers, 96375 scrutiny tends to rise when the claim pattern suggests stacking (multiple sequential administrations without clear medical necessity) or when documentation does not clearly support timing and drug distinctions. The most reliable mitigation remains robust MAR charting, clear reassessment notes when clinically relevant, and internal claim edits that prevent add-ons without parents and prevent professional billing of administration codes in payer-defined facility contexts.