Why HRSA Keeps Targeting Specialty Drug Transactions
HRSA auditors have clearly shifted focus. Since 2022, covered entities say nearly every onsite review digs deeply into specialty prescriptions, especially high-cost therapies like Humira, Stelara, and biologic oncology agents. The reason’s obvious: one misclassified specialty script can turn into a six-figure repayment. In February 2024, HRSA cited “incorrect accumulation methodology for limited-distribution products” at 19 of 50 FQHCs. That line didn’t exist a few years back. It’s there now because specialty integration is messy. Too many programs still treat specialty as retail when the data, dispensing, and ownership structures are entirely different. That disconnect is what drives the findings.
I watched this unravel at a DSH system that acquired a hospital-owned specialty pharmacy. They mapped specialty orders to their existing 340B retail flag and assumed their split-billing vendor could track NDCs the same way. Wrong. The configuration pulled accumulations from an infusion center feed using EMR encounters instead of pharmacy claims. HRSA tagged it as diversion because the prescriber encounter didn’t meet 1996 patient definition criteria in that mixed record environment. That error cost the hospital $1.2 million in corrective repayments. This wasn’t bad intent; it was a simple feed error mapping specialty dispense data to the wrong eligibility table. Painful lesson learned.
Audit Triggers That Don’t Show Up in HRSA’s Guidance
HRSA’s 340B Program Audit Guide still doesn’t use the word “specialty.” But the triggers are built in. Any drug over $10,000 per unit automatically lands in the audit sample. Reviewers request manufacturer data for limited-distribution drugs and compare that to wholesaler shipment records. If those datasets don’t line up, you’re already in trouble, long before the patient definition test even comes up.
Manufacturers know it. Since AbbVie, Novartis, and Amgen tightened data submission requirements, HRSA has quietly coordinated those sets. When a covered entity buys Humira on a 340B account but can’t provide manufacturer-required contract pharmacy data, HRSA asks for proof the drug was given at a registered child site. No proof? HRSA assumes diversion. The courts haven’t settled this; AstraZeneca v. HHS remains legally untested on the agency’s reach over manufacturer restrictions. From an audit standpoint, though, HRSA enforces its interpretation. You either operate conservatively or document obsessively. Pretending the gray area doesn’t exist is what gets programs cited.
OIG’s 2023 report said most entities “cannot demonstrate internal consistency in 340B eligibility determinations for specialty products requiring physician oversight.” Translation: eligibility rules differ by staff or site. Audit triggers usually come from EHR-pharmacy mismatches, duplicate accumulations on split fills, or unverified refill authorizations routed through specialty hubs. HRSA doesn’t care that your EMR module can’t handle patient reassignment logic. If the record doesn’t tie the prescriber to an eligible encounter, you fail, full stop.
Configuring Split-Billing Systems That Actually Hold Up
Most 340B programs use split-billing platforms when they add infusion or specialty services. The best treat those systems as compliance infrastructure, not just finance tools. Start with rule sets: if you’re using Macro Helix, Verity, or Sentry, define specialty accumulators by prescriber and location, not NDC alone. Map infusion centers and specialty pharmacies as distinct pools even when they share an EHR feed. HRSA likes that distinction; it mirrors how patient definition evidence is reviewed. Combine everything into one accumulator and your audit defense collapses.
The worst setup I’ve seen tried automating split-billing purely off wholesale purchase history. That ignores accumulation timing and leaves you unable to reconcile reverse distribution credits. Specialty returns are frequent; biologics expire, dosage switches happen with biosimilars. Every time you return 340B product, you need a documented reversal in the accumulator. HRSA auditors now ask for screenshots showing negative accumulations tied to those reversals. If your vendor can’t do that, you need another vendor. Yesterday.
Also: isolate limited-distribution feeds. Specialty distributors like Cardinal Health Specialty or ASD Healthcare don’t always pass 340B identifiers to your main wholesaler. If your split lives at the master account level, those shipments default to GPO pricing. That silent shift can erase half a million in 340B savings annually. The right approach? Direct subaccount tied to your 340B ID in OPAIS and explicit data-sharing agreements between your specialty distributor and your split-billing vendor.
How HRSA Tests Your “Proof” Chain
Auditors want a straight line from purchase to patient. They’ll check three things: a 340B-eligible encounter in the EMR, a dispensing record that matches the acquisition account, and a financial transaction showing reinvestment of 340B savings. Policy binders aren’t enough anymore, they want transaction-level evidence. For home-shipped specialty fills, expect extra scrutiny. The 1996 patient definition doesn’t mention home delivery, yet HRSA uses the “responsibility for care” test. If your clinicians directed therapy and documented it, your fill is defensible. If the hub or manufacturer nurse line managed ongoing care, expect HRSA to call it a non-patient fill. Three entities were cited for exactly that in 2023.
Data consistency is the other proof point. Accumulations must reconcile with purchase data, dollar for dollar. If not, HRSA demands a written explanation. Over-accumulations triggered by refill syncs are now findings, not warnings. A children’s hospital I worked with had $320,000 overstated accumulations for IVIG because nurses pre-labeled doses and the system read labels as dispenses. HRSA didn’t care the doses weren’t given; they reduced the eligible accumulations and required repayment. Brutal, but predictable.
Programs that stay clean maintain continuous reconciliation between specialty inventory, accumulations, and eligibility logs. Real-time integrations, not monthly uploads. They test manufacturer restriction feeds each quarter to prove data’s updating correctly. HRSA doesn’t mandate that level of rigor, but in practice it’s what separates clean exits from repayment letters. Look, compliance isn’t about perfection, it’s about being able to prove your story when someone else is asking the questions.
Specialty 340B is Worth the Pain
Getting specialty drugs right takes stubborn patience and a vendor who understands 340B audit data, not just pharmacy workflow. Done right, you preserve the only margin keeping some rare disease programs alive. Don’t lose that to lazy mapping or outdated split configs. Once HRSA writes a finding, debate’s over, you’re writing a check. And that’s the line nobody wants to cross.