When HRSA Walks Your Floors
In early 2024, HRSA’s audit team walked through a hospital pharmacy in Ohio with clipboards and tablets, asking for proof, right then, of how the facility’s split-billing tool assigned dispenses between WAC, GPO, and 340B accounts. The mixed-use area included an outpatient infusion suite that also served inpatients on weekends. The compliance officer thought the carve-outs were clean. HRSA didn’t. A month later, the entity received a draft finding stating “ineligible outpatient use due to incomplete documentation of patient encounter status within same care episode.” That case prompted HRSA’s latest mixed-use clarification memo, issued quietly in February 2025, which tightened expectations for how covered entities segment their pharmacy inventory in dual-use settings.
Here’s the real takeaway: split-billing tools aren’t compliance shields. They’re only as defensible as the mapping logic, encounter data feeds, and reconciliation practices sitting underneath them. HRSA’s recent audits make it clear that configuration itself is now a compliance subject, not just a technical setting buried in IT.
What the 2025 Mixed-Use Memo Actually Said
HRSA’s February 2025 clarification expanded on its 2010 and 2015 guidance by requiring that “mixed-use areas physically located within a hospital setting must demonstrate patient-status verification at the time of dispensing, not retrospectively.” That one sentence overturns years of standard practice where teams ran accumulations later, after discharge files settled. HRSA now expects entities to show encounter-level support tying each 340B-accumulated dispense to an outpatient medical record that actually existed at administration time. No hindsight fixes.
This shift tracks with the 2023 OIG report showing 19% of sampled hospitals couldn’t validate outpatient eligibility for infusion center doses billed to 340B. HRSA’s tolerance for “best-effort mapping” is done. They expect what auditors call a “closed loop” data chain connecting EMR, ADT, charge capture, and dispense records in real time. While the memo didn’t change 340B law, it absolutely raised the documentation bar for split-billing vendors and hospital IT teams.
And vendors are spinning fast. Customers of Macro Helix, Sentry Data Systems, and Verity Solutions report interface build times doubling since February because HRSA’s language forced changes in when accumulators post credits. Hospitals that depended on overnight ADT updates now face compliance exposure unless they retool for live patient-status triggers. No safety net there.
An Infusion Center Lesson, the Hard Way
I worked with a children’s hospital last fall that learned this the painful way. Their biggest problem wasn’t software error, it was workflow drift. Nursing staff prepped outpatient doses early, then a patient got admitted before infusion. The 340B engine had already claimed that drug as eligible based on outpatient scheduling data. HRSA saw the timestamps and found inpatient billing status at administration. That one event opened the floodgates, 14 more discrepancies popped up. The software did what it was told. The workflow didn’t.
We rebuilt everything. Pharmacy stopped batch-prepping until the ADT feed confirmed outpatient status in real time. Added a 15‑minute lag to catch last‑minute admissions. Was it convenient? No. But disqualifications dropped to almost zero. HRSA now wants that level of operational discipline, proof of control chains, not promises of intent.
Location mapping trips people up too. HRSA’s memo requires that “spatial commingling of inpatient and outpatient activities” be either physically or procedurally walled off. Some hospitals are literally sketching bay maps and labeling cabinets; others do it through strict location codes in their systems. Either approach works, but lack of documentation doesn’t. A screenshot of your split‑billing screen won’t save you.
How to Build a Split-Billing Setup That Survives 2025
Ignore the vendor hype. HRSA doesn’t care how “intelligent” your accumulator algorithm sounds if the data trail doesn’t match reality. A defensible 2025 setup has four fixed points: accurate outpatient encounter identification from the EMR; a real‑time or near‑real‑time ADT integration; auditable mapping between location codes and account assignment; and a reconciliation log proving no dispense hits two accounts. Miss one, and you’re looking at a diversion citation.
Stop letting vendors run the black box. I’ve sat in audit reviews where compliance teams couldn’t explain how their own tools decided eligibility. If your vendor hides logic under “proprietary,” that’s a compliance red flag. HRSA expects you, not your software partner, to own the risk. And yes, auditors are now requesting the logic documentation itself. Seen it first‑hand.
It’s expensive, absolutely. One DSH hospital in Missouri spent $180,000 reconfiguring Epic interfaces to stream patient‑status data in real time, plus $40,000 a year maintaining custom location logic. That wiped out a quarter’s oncology‑drug savings. Still, weighed against a $2 million payback demand? You do the math.
Looking Ahead: HRSA, Courts, and the 340B Tug-of-War
HRSA hasn’t codified mixed‑use or infusion‑center rules in regulation. This is still all interpretive guidance. If the D.C. Circuit’s reasoning in AstraZeneca v. HHS (2024) holds, the next legal fight could focus on whether HRSA overstepped by enforcing guidance that lacks regulatory muscle. Covered entities love that argument, until an audit finding lands. Legal theories don’t erase a signed compliance certification in the HRSA portal.
Manufacturer pressure muddies it further. Genentech and Johnson & Johnson already cite mixed‑use compliance as justification for their contract pharmacy restrictions. Expect similar tactics ahead, requests for “evidence of compliance” before honoring 340B pricing. Split‑billing systems will become proof vaults. Which means IT, compliance, and finance can’t operate in silos anymore. HRSA’s 2025 landscape punishes isolation.
The only path that actually works now? Full transparency. Treat your split‑billing logic like code you’re willing to show a regulator. Document every rule, generate reconciliation reports someone actually reads, and stay aligned across departments. HRSA’s patience is thin, and the next audit wave focused on infusion centers will expose whether anyone’s really adapted. Look, by this point, if your configuration still depends on faith instead of data, you’re not ready. And HRSA’s no longer waiting.