The "assumed eligibility" era ended today; as of May 1, 2026, AstraZeneca, BMS, and Organon have officially joined Eli Lilly’s February 1st precedent by mandating claim-level data for in-house and mixed-use dispenses as a hard condition of 340B access.
For years, 340B has operated largely at the program level—eligibility defined by entity status, contract pharmacy relationships, and compliance with established guidelines. If a healthcare facility was on the HRSA list and the patient met the three-part definition, they were eligible to buy the drug at the 340B discount. Oversight was retrospective: manufacturer and HRSA audits happened after the fact.
That model is changing. We almost saw this "go live" with the Rebate Model. It's been in play with manufacturers who require contract pharmacy designations and ESP submissions for 340B pricing.
And now, 340B utilization at mixed-use pharmacies has been placed under the same data microscope.
Across multiple manufacturers, new requirements are aligning around a different standard: one where eligibility is not assumed but demonstrated—not just at the pharmacy dispense level, but at the medical claim level, within defined timeframes, and with increasing precision.
If you're wondering why manufacturers are increasingly requesting claims level data (CLD), you're not alone. These data requests first surfaced under the 340B Rebate Model, when the requirements for the initial drugs included expanded data fields usually reserved for medical claims.
The answer lies in the Inflation Reduction Act (IRA) and the introduction of the Maximum Fair Price (MFP). As of 2026, manufacturers face a new financial threat often called the "Triple Dip." They are desperate to avoid paying three separate concessions on the same vial:
By demanding granular data for mixed-use and in-house dispenses, manufacturers are building a forensic ledger. They are no longer just auditing for 340B diversion; they are de-duplicating claims to ensure they aren't paying multiple times for a single administration.
This isn't just an administrative hoop. it’s a manufacturer-driven payment integrity play.
For the pharmacy director and the compliance team, these mandates transform 340B from a mission-critical savings program into an immense administrative burden. The shift to CLD in the in-house and mixed-use setting is not necessarily a simple reporting update; for most hospitals, it is an operational pivot that their current infrastructure not built to support.
Medical claims for clinician-administered drugs often require a direct, forensic interface with the Electronic Medical Record (EMR). By conditioning pricing on a 45-day validation window, manufacturers are inadvertently weaponizing data latency—perhaps betting that the natural lag between a pharmacy dispense, medical data, and claim portal submission will result in a "rejection by default."
This forces hospital staff into a reactive cycle of chasing denials and managing complex data feeds across fragmented platforms like 340B ESP and Truzo, diverting focus from patient care to the manual defense of their statutory right to pricing.
When claims are not submitted accurately or within required timelines, the consequence is missed eligibility at the point of validation—and ultimately, missed 340B savings. This introduces a new level of financial sensitivity to operational performance.
Leaders need to understand not just whether the program is compliant, but how it is performing claim by claim, submission by submission.
The emerging model is characterized by:
This reflects a shift toward more precise, more controlled program oversight. It suggests that the capabilities required to run a high-performing 340B program are changing.
As this model takes hold, the distinction between programs will increasingly come down to technical and operational readiness.
Today's pharmacy leaders must evaluate 340B TPAs at a higher standard:
These are not new questions. But they are becoming more consequential.
For many organizations, these changes are prompting a closer look at how their 340B infrastructure is built.
Systems that were sufficient under a less time-sensitive, less granular model may not provide the level of visibility or control now required. Manual workarounds that once bridged gaps may become harder to sustain.
What’s emerging instead is a need for:
This is exactly where purpose-built platforms are starting to separate themselves—those designed to expose every claim, support real-time insight, and handle submission requirements as part of the daily workflow, not as a downstream afterthought.
The updates from AstraZeneca, Bristol Myers Squibb, and Organon are not isolated events. They are indicators of where the 340B program is heading.
That direction is more structured. More time-bound. More dependent on data integrity at the claim level. The burden of proof is aggressively shifting to the covered entity side of the table before 340B pricing is granted.
For covered entities, the focus now is less about reacting to individual policy changes and more about aligning operations with that trajectory. Because as validation moves to the claim level, performance does as well.
At PharmaForce, our ClaimsConnect infrastructure was engineered specifically to bridge the gap between your 340B data and the manufacturer portal of choice, ensuring your data is captured and validated before the 45-day clock slams shut.
The mandate has moved inside hospital walls. Your technology must move with it.
Secure your 340B savings. Request a conversation with a PharmaForce expert today.