HRSA Auditors Are Now Showing Up at Mobile Units
In March 2026, a federally qualified health center (FQHC) in Georgia learned the hard way that a trailer on wheels is still a 340B child site in HRSA’s eyes. The entity had registered the mobile unit to deliver vaccines and primary care through a rotating schedule across three rural counties. During a routine HRSA audit, the Office of Pharmacy Affairs (OPA) asked for provider-patient encounter documentation tied to specific prescription fills at a contract pharmacy in Atlanta. The center couldn’t produce the encounter logs. HRSA moved the audit into “for-cause” review and disallowed $489,000 in purchases as diversion. That episode has been circulating through every FQHC 340B administrator listserv since spring.
It wasn’t a one-off. HRSA’s auditors in 2026 have clear instructions to verify how mobile health units (MHUs) connect back to parent covered entities. Program integrity is being tested not just on clinic walls but on wheels. The question has shifted from “is this provider employed?” to “did this prescription originate from a qualifying encounter logged under the registered mobile site on the date of service?”
Eligibility Verification in Motion
HRSA’s 2025 revisions to its audit protocol quietly added language requiring auditors to “confirm patient eligibility for prescriptions originated through satellite and mobile service locations.” For years, entities stretched broad internal interpretations of “eligible site” under Section 340B(a)(4). When HRSA resumed full enforcement last summer after pandemic leniency ended, it began asking for exact proof of site registration matching each service date and location, no gray space left.
Mobile health administrators now need to treat each stop as if it’s a temporary clinic site. The provider’s NPI, encounter type, and patient chart note must link directly to the parent entity’s cost report or HRSA-registered grant. Crossing county lines? Pharmacy systems must record where each prescription physically originated. HRSA reviewers are cross-referencing mobile visit logs with dispensing data from contract pharmacies, and mismatches trigger diversion flags faster than anyone expected.
The biggest trap? EHRs that default mobile encounters to the parent address. It seems easy until audit day. HRSA’s 2026 guidance emphasizes “source verification of encounter origination,” which means you can’t justify location data later. The encounter metadata has to live inside the original clinical note. Look, if it’s not in the EHR, it doesn’t exist.
Dispensing Documentation and Audit-Ready Chains of Custody
Dispensing documentation for mobile prescriptions is where most covered entities start to wobble. HRSA expects three parallel datasets that reconcile: the patient encounter, the prescription, and the 340B purchase record. When a mobile prescriber sends an e-script to a contract pharmacy, the entity must document that the patient met the eligibility conditions under 42 U.S.C. §256b(b) at that moment. If the split-billing software or capture system can’t confirm it, that transaction is ineligible, no middle ground.
By early 2026, OPA contractors began asking covered entities to show daily reconciliation reports for mobile dispensations. That was new. HRSA had previously accepted quarterly reviews, but heightened access to manufacturer-reported ceiling price data changed that. HRSA hasn’t revealed every trigger it uses to flag anomalies, but it’s obvious: sudden spikes in 340B purchases tied to mobile encounters bring immediate scrutiny.
Covered entities are adapting. GPS-tagged encounter verification, batch reconciliation scripts, automated crosswalk logs, these tools are now standard in most 340B management platforms. What sounded futuristic in 2022 is just routine now. And with pharmacy closures and PBM consolidation shrinking dispensing options, those documentation tools are no longer just compliance extras, they’re what keep 340B programs operational in a contracting network.
Contract Pharmacy Integration and HRSA’s New Scrutiny
The conversation about mobile health units naturally spills into contract pharmacy oversight. HRSA’s 2026 audit wave has been relentless toward mobile prescribers using nontraditional dispensing routes. Meanwhile, manufacturers keep advancing carve-out strategies that isolate contract pharmacy utilization, responding to the surge of PBM-affiliated specialty pharmacies. Drug Channels’ April 2025 analysis counted more than 1,900 specialty locations dominated by integrated PBMs. That dominance leaves covered entities navigating razor-thin compliance margins, as independent contract pharmacies keep disappearing.
HRSA hasn’t softened its position. Auditors now require proof of referral or documented care pathways when a mobile prescriber routes a patient to a contract pharmacy not physically connected to the provider. Covered entities must demonstrate that each prescription clearly emerged “in the context of medical services” tied to the registered grantee or hospital, not just any clinician in a van that day. Pharmacy data feeds need to allow HRSA to match every dispense to a specific encounter record.
Some administrators now run internal “contract pharmacy integration audits” every two months, using 340B ESP and TPA data to head off HRSA findings before they start. The discipline pays off. When HRSA spots documentation gaps in mobile records, it often extrapolates across all contract pharmacy sites, so one missed eligibility tag can balloon into a network-wide disallowance, sometimes devastatingly so.
The broader backdrop is PBM consolidation reshaping 340B economics. As Drug Channels’ May 2026 video update captured, vertical integration is tightening every corridor of the pharmacy market. HRSA’s insistence on airtight data trails between mobile care and contract pharmacies mirrors that compression: fewer players, higher scrutiny, no forgiveness for sloppy records.
What Covered Entities Should Do Now
Any organization running mobile units under a 340B registration should run an internal “2026-style” mock audit immediately. Start with encounter mapping. Confirm every mobile site appears correctly in HRSA’s 340B OPAIS system with accurate parent-child ties. Then check that prescription data brings the correct site identifiers into your split-billing platform. Scan your daily purchase logs for anything that could mimic contract pharmacy over-dispensing. If your system still relies on manual back-matching, you’re already behind HRSA’s current enforcement curve.
And push your pharmacy partners harder. They have to validate their own receipt-of-prescription workflows before HRSA does. Because when an auditor shows up, yes, even at that trailer parked outside a school gym, they’ll want the full chain visible: provider, patient, site, encounter, prescription, dispense, and purchase record. Only when all six connect do you have a 340B-eligible claim you can defend. Anything short of that, and your mobile unit becomes not a compliance innovation but the loose hinge in your whole program.
Sources
- The Top 15 Specialty Pharmacies of 2025: PBM-Affiliated Pharmacies Dominate While Health Systems and Independents Gain Ground (Drug Channels, 2025-04-21)
- PBM Shakeout: How Vertical Integration Is Reshaping What’s Next (VIDEO) (Drug Channels, 2026-05-20)
