A Medicare Administrative Contractor sends your practice an additional documentation request covering 41 claims billed with an IV push code over the last eight months. You have ten business days to respond. Your biller pulls the encounter notes, discovers that CPT 96374 was reported on twelve of those dates without a documented start time, and now three people are digging through nursing flow sheets, a scanned paper log from your old process, and a shared spreadsheet somebody built to track drug waste.

This guide is for the administrator or billing lead who owns that mess. It covers what CPT 96374 describes, the documentation your coders need before they can assign it, who touches that documentation between the infusion chair and the remittance advice, and the HIPAA obligations that attach to every one of those handoffs. It is administrative guidance, not clinical guidance. Nobody here is telling you which code fits a given patient encounter.

What CPT 96374 Describes, in One Paragraph

CPT 96374 is the code for a therapeutic, prophylactic, or diagnostic injection administered as an intravenous push — single or initial substance or drug. CPT's injection and infusion guidelines define an IV push as an injection in which the administering professional is continuously present to observe the patient, or an infusion of 15 minutes or less. Two related add-on codes exist: one for each additional sequential IV push of a new substance or drug, and one, reportable only in a facility setting, for an additional push of the same substance more than 30 minutes after the prior administration. The drug itself is reported separately with the appropriate HCPCS code and units. Your clinical staff documents what happened; your coders map that documentation to codes using the current CPT guidelines and each payer's policy.

That is the snippet answer. The operational reality is that CPT 96374 lives or dies on documentation created by people who do not think of themselves as billing staff.

The Documentation Elements Your Coders Will Ask For Every Single Time

Build your infusion documentation template around what a coder and an auditor both need. If any of these are missing, the claim goes to a work queue and your days-in-AR number gets worse.

Order, substance, dose, and route

A signed or authenticated order from a qualified provider, the specific substance or drug administered, the dose, and the route. "IV meds given" is not a code-supporting entry. Your coders cannot infer a push from a note that does not distinguish push from infusion.

Timing and continuous presence

Start time, stop time, and — for a push — documentation reflecting that the administering professional was continuously present, or that the administration ran 15 minutes or less. Practices that struggle with denials on IV push codes almost always struggle with time capture first. If your nurses chart times at the end of the session from memory, you have a documentation problem that will surface in an audit.

Sequence when multiple services occur

When a patient receives more than one injection or infusion in a session, the order and timing of each administration determines how add-on codes are reported. Your flow sheet needs to preserve sequence, not just a list.

Site of service and supervision

Office-administered drug administration generally requires the supervision level your payer specifies. Document who was present and available. This is also the field that most often diverges between your appointment system and your claim.

Waste and discarded drug

If your practice buys and bills, waste documentation drives units on the drug line, not the administration line. Keep the two records adjacent but distinct so a coder does not conflate them.

How Practices Decide Which Administration Code Goes First

CPT's guidelines establish a hierarchy for facility reporting — chemotherapy and complex biologic administration ranks above therapeutic infusions, which rank above pushes, which rank above subcutaneous and intramuscular injections. Physician offices apply a different instruction: the initial code reflects the primary reason for the encounter, regardless of the order in which services were delivered.

Practically, that means two staff functions must be separated in your workflow. Clinical staff record what happened and when. Coding staff apply the hierarchy or the primary-reason rule, check National Correct Coding Initiative edits, and confirm payer-specific policy. Do not let your scheduling template or your EHR's charge-capture shortcut pick the initial code by default. Charge-capture automation that assigns CPT 96374 whenever a nurse checks an "IV" box is how practices end up with a pattern an auditor can spot from a spreadsheet.

Write your policy down. Name the person who resolves coding questions, the reference they use, and the turnaround time. When a payer asks why a code was selected, "our coder applied the current CPT guidelines and documented her rationale in the encounter" is a defensible answer. "That's how it's always been in our fee schedule" is not.

Who Touches CPT 96374 Data Between the Chair and the Remittance

Here is the part that gets skipped. Every claim carrying CPT 96374 generates a data trail that leaves your building, and each stop on that trail is a HIPAA question.

  • Your EHR and practice management host. Business associate. You should have a signed agreement and know where the data resides.
  • Your clearinghouse. Business associate. Claims, remittances, and eligibility responses all pass through.
  • Your billing or RCM outsourcer. Business associate, and the one most likely to hold copies of clinical documentation in a system you have never audited.
  • Coding audit and consulting firms. If a consultant reviews 50 infusion charts to check your IV push reporting, that firm is a business associate. A statement of work is not a BAA.
  • Denial management and appeals vendors. These often receive full chart excerpts, not just claim data.
  • Infusion pump, cold-chain monitoring, and inventory platforms. Ask whether the feed includes patient identifiers. Frequently it does.
  • Answering services and after-hours triage. Post-administration callbacks generate PHI in a vendor's phone system.
  • Document scanning, storage, and shredding vendors. Paper flow sheets are still paper.

Run that list against your executed agreements this quarter. If any vendor on it is missing a signed BAA, or you are working off a 2016 template that predates your current data flows, you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX — one-time purchase, no subscription. HHS also publishes sample business associate agreement provisions that show the required elements, though sample text alone will not describe your actual vendor relationship.

Copay Assistance and Manufacturer Hubs: Authorization Territory

Buy-and-bill practices routinely enroll patients in manufacturer copay programs, patient assistance foundations, or nurse-support hubs tied to a specific drug. Those entities are usually not treating you as a covered entity's business associate, and the disclosure is usually not treatment, payment, or health care operations from your side.

That means a signed HIPAA authorization, not a BAA. The authorization needs to name the recipient, describe the information disclosed, state the purpose, carry an expiration event, and include the patient's right to revoke. Front-desk staff should not be faxing enrollment forms containing diagnosis, drug, and administration history to a manufacturer portal on a verbal okay.

Assign one person to own the authorization inventory for these programs. Store executed authorizations where a records request can find them, and set a review date. Programs change vendors; your authorization language should still describe who actually receives the data.

The 30-Day Clock When a Patient Asks for Their Infusion Records

A patient who was billed for an IV push and disputes the charge will ask for the record. Under the HIPAA right of access, you generally have 30 days to provide it, with one 30-day extension if you notify the patient in writing of the reason and the new date. Fees are limited to a reasonable, cost-based amount. The OCR guidance on individuals' right of access is the reference to keep on hand, and access failures have been a persistent enforcement theme.

Two operational traps here. First, infusion documentation often lives partly outside the note — nursing flow sheets, MAR entries, pump logs, scanned paper. The designated record set includes records you use to make decisions about the individual, and a patient asking for "my infusion record" is asking for those, not just the visit summary. Build a pull list so staff do not have to improvise.

Second, amendment requests. A patient who says the documented administration time is wrong is making an amendment request under the Privacy Rule, which carries a 60-day response window with a possible 30-day extension. That request needs to reach your privacy officer, not sit in a billing queue as a "complaint." Document your decision and, if you deny it, the reason and the patient's rights.

Payer Audits and the Minimum Necessary Question

Responding to an ADR or a commercial payer audit is a payment disclosure and does not require authorization. It does require judgment about scope. Sending an entire longitudinal chart when the payer asked for the documentation supporting six dates of service is a minimum necessary problem you created for yourself, and it puts unrelated conditions in a third party's hands.

Standardize the response packet: the order, the administration record with times, the encounter note for those dates, the drug administration and waste log, and nothing else unless the request names it. Review the minimum necessary standard with whoever assembles these packets, and log what you sent and when. Also verify the transmission channel — audit responses uploaded to a payer portal are one thing; a stack of records left on a fax queue overnight is another.

A 30-Day Cleanup Plan for Infusion Billing and Its Vendor Chain

  1. Week 1 — Sample ten charts. Pull ten encounters billed with CPT 96374 in the last quarter. Check for order, substance, dose, route, start and stop time, sequence, and supervision. Score the gaps by field, not by chart.
  2. Week 2 — Fix time capture. If timing is your weak field, change the workflow, not the training slide. Times should be entered at administration, in the system of record, by the person administering.
  3. Week 3 — Map the data. List every entity that receives infusion documentation or claim data. Note the transmission method for each. Flag anyone without an executed, current BAA.
  4. Week 4 — Close the paper. Decide where flow sheets live, who scans them, how long you retain them, and how a records request finds them. Update your access and amendment procedures accordingly.

Feed the results into your risk analysis rather than filing them as a billing project. Drug administration workflows create PHI in systems that rarely appear on a security inventory — pump software, inventory platforms, the shared drive holding the waste log. If your risk analysis and policy set have not been refreshed since your infusion service changed shape, automating the risk analysis and policy documentation is a faster path than rebuilding it in a word processor. And check the OCR breach portal for how comparable practices have failed — vendor incidents and misdirected records dominate.

The Short Version

CPT 96374 is a small code with a long tail. Your clinical staff produce the documentation, your coders apply the guidelines, your vendors move the data, and you answer for all three when a payer audits or a patient asks for the file. Tighten the documentation template, name the owners, and make sure every entity in the chain has a current agreement on file.

Start with the agreements, because that is the gap you can close this week. If your vendor list has holes, build the BAA you actually need and get it signed before the next audit letter arrives.