A payer audit letter lands on your desk requesting the complete records for 42 infusion encounters, all of them billed with an add-on IV push line. You have 30 days to respond, the nursing flowsheets for eleven of those dates live in a scanned PDF folder on a shared drive, and your outside coding contractor has been pulling those files remotely for two years. Before you answer the letter, you need to know two things: what the 96375 CPT code description actually requires from your documentation, and who has been touching that documentation along the way.

This guide is for practice administrators, billing leads, and privacy officers who own infusion documentation end to end. It covers the operational mechanics of the add-on code, the records that support it, and the vendor exposure that comes with every one of those records.

Quick Answer: What the 96375 CPT Code Description Says

CPT 96375 is an add-on code in the therapeutic, prophylactic, and diagnostic injection and infusion family. The published descriptor language covers an intravenous push, each additional sequential intravenous push of a new substance or drug, and it is listed separately in addition to the code for the primary procedure.

Three operational facts follow from that descriptor:

  • It never stands alone. An add-on code requires a reported primary service on the same encounter. A claim carrying the add-on line with no qualifying primary line will not survive edits.
  • "Sequential" and "new substance or drug" are documentation requirements, not billing assumptions. The chart has to show the sequence and identify each substance separately.
  • Units are driven by discrete administrations, each of which has to be visible in the record with its own supporting detail.

Nothing in this article tells you which code fits a given patient encounter. That determination belongs to the clinician's documentation, your certified coders, current CPT guidance, and the payer's published policy — in that order.

What Your Coders Need in the Chart Before Anyone Builds a Claim

Add-on infusion and injection lines are among the most frequently reviewed items in outpatient claims because the supporting facts are granular and easy to omit. Build your internal documentation checklist around what the descriptor language demands.

The five data points auditors look for

  1. The substance or drug, named specifically, not "IV meds" or a shorthand initialism your nurses use in the infusion bay.
  2. Route and method of administration, distinguishing push from infusion, because the two map to different code families.
  3. Time. Start and stop times for infusions; administration time for pushes. Ranges written after the fact in round numbers draw scrutiny.
  4. The order. A signed, dated provider order that matches what was administered.
  5. The administering clinician's authenticated signature and credentials on the flowsheet or MAR entry.

If your infusion suite still runs on paper flowsheets that get scanned nightly, your coders are working from an image. Images are not searchable, they get filed under the wrong encounter, and they get emailed around when someone is in a hurry. Every one of those failure modes is both a billing problem and a privacy problem.

Sequential versus concurrent, and why it is a workflow question

The distinction between sequential and concurrent administration lives entirely in the timestamps your nursing staff record. If two administrations show identical start times because the flowsheet defaults to the check-in time, no coder can tell what happened, and no auditor will give you the benefit of the doubt.

Fix this at the point of capture. Audit ten infusion encounters a month for timestamp integrity and report the results to your clinical lead, not just to billing. Coders cannot repair documentation they did not create, and they should never be asked to.

Role Assignments: Who Owns Each Step

Most denials on add-on infusion lines trace back to an unowned handoff. Write the owners down.

  • Scheduling / front desk: verifies benefits and prior authorization for the drug, flags site-of-service requirements, and confirms the encounter type before the patient sits down.
  • Administering nurse: records substance, route, and times contemporaneously and authenticates the entry before leaving the shift.
  • Ordering provider: signs the order and any changes made mid-encounter.
  • Coder: selects codes from documented facts, applying current CPT guidance and payer policy; queries the provider when the record is ambiguous rather than inferring.
  • Billing lead: reviews edit rejections, tracks add-on line denial rates monthly, and escalates patterns.
  • Privacy officer: owns who can access infusion documentation, how it leaves the practice, and which vendors hold a signed agreement.

CMS publishes the code-pair edits that govern which lines can be reported together on the same date of service. Your billing lead should be able to name where those edits live — the National Correct Coding Initiative edit files on CMS.gov — and should be checking them against your clearinghouse's edit set at least annually.

The Records Request That Follows the Claim

Billing an add-on line invites documentation requests. Payer medical review, post-payment audits, and recovery contractor reviews all ask for the same underlying artifacts: the order, the flowsheet, the MAR, the drug label or NDC record, and the encounter note.

Send what was asked for, not the whole chart

The reflex in a busy billing office is to export the full chart and let the payer sort it out. That reflex creates unnecessary disclosures. HIPAA's minimum necessary standard applies to disclosures for payment purposes, and "the payer asked broadly" is not a documented justification on its own.

Build a standing audit-response packet definition for infusion encounters: which documents go, which do not, and who signs off before transmission. Log every response — date, recipient, encounter list, transmission method. When a second request arrives 14 months later, that log is the only thing that will tell you what already left the building.

The patient-facing side of the same records

The same flowsheets are subject to the individual right of access. When a patient requests their infusion records, your 30-day clock runs regardless of whether a payer audit is in progress on the same dates. Do not let an active audit become the reason an access request sits. Right-of-access enforcement has been one of OCR's most consistent activities, and the HHS breach portal is a useful monthly reminder of what happens when records handling goes sideways at scale.

Vendor Exposure: Who Actually Touches Your Infusion Documentation

Walk the path a single add-on IV push line travels and count the outside organizations that see identifiable data along the way. In a mid-sized specialty practice, the list usually runs longer than the administrator expects:

  • The outsourced coding firm that reads the flowsheet
  • The billing company that builds and submits the claim
  • The clearinghouse that routes it
  • The document management or scanning vendor that houses the imaged flowsheets
  • The release-of-information vendor that fulfills audit and patient requests
  • The IT support contractor with administrative access to the shared drive
  • The denial-management or A/R recovery firm that works aged claims
  • Any analytics vendor receiving encounter-level utilization data

Each of those is a business associate. Each one needs a signed agreement in place before it receives protected health information, and each agreement needs to actually describe permitted uses rather than sitting in a drawer as a two-page relic from 2014.

If you just read that list and realized two or three of your vendors have no executed agreement — or have one that predates the current requirements — you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX the same afternoon. It is a one-time purchase, not a subscription, which matters when you need three agreements this quarter and nothing next quarter.

Subcontractors are the gap nobody checks

Your coding firm may use offshore reviewers. Your billing company may use a third-party statement printer. Both are permitted, both require downstream agreements, and neither will volunteer the information. Add one question to your annual vendor review: list every subcontractor that accesses our data, by name and country. File the answer. Ask again next year.

Four Failure Modes Specific to Infusion Suites

The whiteboard. Infusion bays run on visibility. A board listing patient names, drugs, and chair times, mounted where the waiting area can see it, is an incidental-disclosure argument you will lose. Move it, angle it, or switch to initials plus chair number.

Texting times to the coder. When a coder queries a missing stop time, the fastest answer path is a text from a personal phone. That text now contains PHI on an unmanaged device. Route queries through your EHR's messaging or a managed channel and say so in writing during onboarding.

Shared workstation logins. Nurses documenting on a shared infusion-bay terminal under one login destroys attribution. That breaks the signature requirement your coders rely on and destroys your audit trail at the same time. Unique credentials are not optional.

The email attachment to the payer. Someone will attach a 40-page PDF of flowsheets to an unencrypted email because the portal was slow. Give them a faster sanctioned option, or the unsanctioned one wins every time.

A 30-Day Cleanup Plan

Week 1. Pull your last 25 encounters containing add-on IV push lines. Check each for named substance, route, times, signed order, and authenticated signature. Score them. Share the score with clinical leadership without naming individuals.

Week 2. Inventory every vendor that touches infusion documentation. For each, confirm an executed agreement, its date, and whether it names subcontractor obligations. Flag the gaps.

Week 3. Write the audit-response packet definition. Decide what a standard payer request receives, who approves outbound transmissions, and where the disclosure log lives.

Week 4. Close the vendor gaps and update your risk analysis to reflect the infusion documentation flow — including the scanned-image folder everyone forgot was in scope. If your risk analysis has not been touched since your last EHR upgrade, automating the risk analysis and policy set gets you a defensible baseline faster than rebuilding the spreadsheet.

Where the 96375 CPT Code Description Meets Your Compliance Program

The 96375 CPT code description is a billing artifact, but everything that supports it is a privacy artifact. Times, drug names, orders, and signatures are protected health information from the moment they hit the flowsheet until the retention clock runs out. Practices that treat coding accuracy and records handling as two separate projects end up with clean claims and leaky files, or tight security and endless denials.

Run them together. One documentation standard, one vendor list, one disclosure log. When the next audit letter arrives requesting 42 encounters, you will spend your 30 days assembling records instead of reconstructing who had access to them.

Start with the vendor list, because it is the piece most practices have never fully written down. If a name on that list lacks a current agreement, build and export a Business Associate Agreement before that vendor sees another flowsheet.