Every year, the 340B Coalition Summer Conference offers a useful gut-check on where the program actually stands – not the policy-paper version, but the version covered entities are living through in real time. This year, that gut-check was louder than usual.
Here’s what stood out from the sessions, the hallway conversations, and our booth, and what it suggests covered entities should be prioritizing for the rest of the year.
Rebate uncertainty has become the dominant emotional undercurrent
If there was a theme that cut across nearly every conversation, it was this: nobody feels like they have solid footing under the current rebate model discussions. One of the most telling moments of the conference wasn’t a product session at all – it was a room full of covered entities gathering simply to talk through how unsettled the situation feels and compare notes on what, if anything, anyone actually knows.
That’s not a small thing. When an industry’s default response to policy uncertainty is “let’s get in a room and commiserate,” it tells you the anxiety is systemic, not isolated to a handful of outlier entities.
This isn’t compliance reluctance, it’s a data trust problem
A recurring and important nuance: covered entities aren’t resistant to compliance. They understand what’s required of them and, generally, want to hold onto their pricing. What’s generating real hesitation is what happens to patient data once it leaves the four walls of the hospital.
Manufacturer claims-data demands have moved from a periodic audit request to, in some cases, a condition of continued 340B pricing. And entities are increasingly asking hard questions about downstream use, retention, and control once that data changes hands.
Tampa General Hospital’s lawsuit against Eli Lilly is the clearest illustration of where this tension can lead. After Lilly began requiring claims-level dispensing data as a condition of 340B pricing and cut off TGH’s discounts when the hospital didn’t comply, TGH filed suit, becoming, by most accounts, the first hospital system to challenge a manufacturer’s data demands directly in court rather than through a trade association. TGH says the change has raised its costs on Lilly products by 25–50%, and the American Hospital Association has since pushed HHS to weigh in on the broader practice, which several other manufacturers have since adopted in some form.
Whatever the outcome, TGH v. Lilly has become the reference point the rest of the industry is watching closely. It’s less a one-off dispute and more a signal that the manufacturer-data-demand issue has moved from “concerning trend” to “active legal battleground.” Covered entities should expect this to keep evolving through the back half of the year.
Budgets are frozen, and the posture is defensive
The financial mood on the floor was consistent: budgets are tight, hiring is frozen even where headcount is clearly needed, and the operating instinct right now is to hold steady rather than take on new initiatives – including ones that could genuinely help. It’s an understandable response to a year with an ever-evolving amount of change.
That posture has real implications for how covered entities should be thinking about technology and process investments right now. A purchase that’s framed purely as “compliance overhead” is a hard sell in a budget freeze. A purchase that’s framed around protecting or recovering margin – in a year where every dollar of 340B savings is under more scrutiny than ever – is a very different conversation.
MFP reconciliation is the operational question nobody has fully solved
On the exhibit floor, one of the most common questions wasn’t about a specific vendor’s feature set. It was some version of “what are you doing about MFP reconciliation?” That’s a meaningful data point on its own. It suggests the industry has moved past debating whether Medicare’s Maximum Fair Price interactions with 340B pricing matter, and into the much harder phase of figuring out how to operationalize it without introducing new compliance risk or losing savings in the process.
There’s also a set of entities that are moving toward consultants over software to help navigate this as the rules are still shifting. That’s a reasonable response to genuine ambiguity, but it’s worth covered entities asking themselves whether a manual, relationship-dependent process will scale once MFP reconciliation requirements stabilize into something that needs to run reliably, every cycle, with an audit trail behind it.
A word of caution on AI in the compliance stack
One point worth flagging from the pre-conference Apexus 340B University sessions: as AI tools proliferate across the 340B software landscape, entities should be deliberate about where AI is actually being used to make or influence compliance and audit decisions versus where it’s simply summarizing or surfacing information for a human to review. Your regulatory posture depends on being able to explain, defend, and reproduce every decision behind a claim. That bar doesn’t change just because a tool is faster.
What this means for the rest of the year
Pulling these trends together, a few priorities stand out for covered entity teams heading into H2:
- Get ahead of manufacturer data demands before they force your hand. Understand exactly what data is being requested, why, and what contractual and legal protections exist around its use – before a discount gets cut off, not after.
- Build the business case for 340B and purchasing technology around margin, not just compliance. In a budget-frozen environment, a tool that protects or recovers revenue will get funded faster than one that’s positioned purely as risk mitigation.
- Start operationalizing MFP reconciliation now, even in an unsettled environment. Whatever process you stand up today doesn’t need to be final, but it does need to be documented, repeatable, and ready to scale as the rules solidify.
- Treat AI in your compliance stack as a research assistant, not a decision-maker, until you can fully explain and defend its role in an audit.
- Lean on partners who can absorb some of the uncertainty with you. This has been a genuinely difficult year to navigate solo. The teams that come out ahead won’t be the ones who moved fastest. They’ll be the ones who built defensible, reproducible processes while everyone else was still deciding what to do.
The overall read from the conference: the challenges are real and the anxiety is justified, but none of it is unsolvable. The entities that treat this as a moment to build sturdier infrastructure, rather than simply waiting for clarity that may not arrive on a convenient timeline, will be in a meaningfully stronger position by year’s end.
To learn more about how Bluesight’s 340BCheck can support your 340B program, ensure compliance, and protect meaningful margin, reach out today.