From Reporting to Enforcement: What 43 Manufacturers Now Want From Your 340B Program

43 manufacturers now restrict 340B contract pharmacies. That's the number in the headlines. It isn't the one that should be on your radar this quarter.

The bigger shift is quieter. The largest manufacturers have started demanding 100% of your claims data, contract and in-house, as the condition for keeping your 340B pricing. Reporting used to be a formality. It's becoming the price of admission. That's the move from reporting to enforcement.

We walked through it during Mission Control Monthly, our standing briefing for those who run 340B programs at covered entities where we break down what shifted this month, what it means for a program like yours, and the next move to make—before it shows up in your numbers. Here's Charlie Hirner, SVP of Mission Control, on what changed:

What actually changed

Three things moved in the last quarter, and they compound.

First, the 100% data demand. It's no longer only about contract pharmacy claims. The big manufacturers increasingly want in-house pharmacy data too, or the 340B pricing goes away.

Second, it's already reaching in-house pharmacies. Lilly began removing pricing from hospital in-house pharmacies at the beginning of June.

Third, there's now more than one destination for that data. A second clearinghouse, Truzo, sits alongside ESP, so "where does my data go" isn't a one-answer question anymore.

Miss a submission requirement and the cost is immediate: lost pricing, compressed savings, and less cash flow to reinvest in the patients your program exists to serve.

The part the headlines miss

Here's the context that changes the temperature of this, and it matters: What pharma is actually hunting for in that data is alternate distribution, entities using an in-house pharmacy account to buy drugs and redistribute them to contract pharmacies. That pattern shows up in large DSH hospital systems. It is not what a typical FQHC's in-house pharmacy looks like.

So for most community health centers, the risk profile is different, and lower, than the headlines suggest. That doesn't make the requirement optional. But it should move the conversation from alarm to preparation.

It also leaves a real decision on your desk. Whether to share in-house data is a benefit-versus-risk call, and it's yours to make: can you afford to lose 340B pricing at your in-house pharmacy, or is sharing the data the better trade? We're not going to tell you which way to go. It depends on your entity, your pharmacy mix, and your patients.

What we see as best practice

What we can offer is what good preparation looks like across the 800+ covered entities we watch. They know where their data goes. Contract and in-house claims flow to the right platform, whichever one a given manufacturer requires.

They automate the submission. A policy change becomes a routine data pull instead of a fire drill for a team that's already stretched thin.

They know their own benefit-versus-risk position before they're forced to decide in a hurry. When the next manufacturer changes its terms, the math is already modeled, not improvised at the deadline.

That's where a unified model earns its place: one partner, one data pipe, submitting across contract and in-house pharmacies to ESP or Truzo, so a rule change doesn't quietly cost you the savings your patients depend on. No gaps, no scramble.

Why we see it first

None of this arrives as a headline. It arrives as a term change buried in a manufacturer letter, and most programs feel it one at a time. Reading 340B across 800+ covered entities and more than 1.5 billion claims is how Mission Control spots the pattern before any single program feels it, and it's how our clients have kept a record of zero reported HRSA audit findings over the last decade while the rules keep moving.

The enforcement era is here. The programs that do well in it won't be the ones that react fastest. They'll be the ones that were ready before they had to be.

If you want to know where your program stands, your CSM can walk you through a data-readiness check for your entity.

If you're not a NuvemRx customer, let us know how we can help below.