Most people don’t spend much time thinking about 340B. If you’re not counting on it or actively fighting it, you don’t need to. But right now, federal courts, state legislatures, pharmaceutical manufacturers, pharmacies, hospitals, and regulators are all fighting over it.
Over the past several months, a program that rarely attracts mainstream attention has found itself at the center of lawsuits, regulatory scrutiny, appellate court battles, and increasingly public disputes between some of healthcare’s most powerful stakeholders.
State officials are scrutinizing how 340B-related dollars move through parts of the healthcare supply chain. Manufacturers continue pushing back against state efforts to preserve contract-pharmacy access. The Fourth Circuit is reconsidering challenges to state contract-pharmacy laws. What was once a relatively technical policy discussion now carries implications for hospital finances, pharmacy networks, state policy, and access to care.
For many hospitals and health systems, 340B is woven into the economic reality of serving communities where reimbursement often fails to cover the cost of care. Hospital leaders may not spend much time discussing the program publicly, but they understand exactly what is at stake when access to 340B savings becomes uncertain.
If your organization depends on 340B funding, now is a good time to think through what happens if some of that funding becomes less available. The effects would not stop at pharmacy operations. Revenue strategies, managed care plans, community programs, and organizational priorities could all be affected.
The current disputes revolve around a simple question: who controls the value created by 340B?
Once significant economic value accumulates around any part of healthcare, stakeholders begin competing to influence how that value is distributed. And that’s why a program most Americans have never heard of now appears in courtrooms, legislative chambers, regulatory investigations, and boardroom discussions across the country.
Why 340B matters far beyond traditional safety-net providers
The easiest way to misunderstand 340B is to think of it as a drug discount program. Though it’s technically accurate, it misses why the program generates so much attention whenever its future appears uncertain.
Congress created the 340B program in 1992 to allow certain hospitals and healthcare organizations serving vulnerable populations to purchase outpatient drugs at discounted prices. The goal was to help covered entities stretch limited resources further and support care for underserved communities.
While the program is often associated with traditional safety-net providers, its financial impact now extends across a much broader range of hospitals and health systems. Meanwhile, healthcare grew more expensive to deliver. Hospitals today operate in an environment where:
- Labor costs continue to rise
- Supply costs remain elevated
- Reimbursement often fails to keep pace with inflation
- A growing share of patients receive coverage through programs that frequently reimburse below the cost of care
Rural and community hospitals face those pressures, and so do academic medical centers, but safety-net providers often feel them most acutely.
Against that backdrop, 340B savings became more than a purchasing mechanism. The savings help support services that may not otherwise generate enough revenue to remain viable. They can contribute to pharmacy access programs, community outreach initiatives, specialty services, uncompensated care, and other investments that support a provider’s broader mission.
Reasonable people can disagree about how the program should operate. They can debate oversight, transparency, and accountability. What is increasingly difficult to dispute is that substantial economic value now flows through the program.
Why contracting with pharmacies became the legal flashpoint
Most of the current legal battles surrounding 340B trace back to a relatively simple operational reality.
As healthcare delivery evolved, many hospitals and covered entities found themselves serving patients across larger geographic areas than their own pharmacy infrastructure could support. Contracting with retail pharmacies became a practical way to improve access to medications without building and operating additional pharmacy locations.
Those arrangements attracted relatively little controversy until 2020. Several pharmaceutical manufacturers began restricting shipments of 340B drugs to pharmacies working on behalf of covered entities. This is where the debate turns to congressional intent.
The manufacturers’ argument
The 340B statute requires manufacturers to provide discounted drugs to covered entities, but Congress could not have anticipated the extensive pharmacy contracting arrangements that developed over the following decades. Manufacturers argue those arrangements expanded the program beyond what Congress originally described.
The hospitals’ argument
Many hospitals rely on pharmacy partners to serve patients across broad geographic regions. Restricting those arrangements would limit access to 340B savings and weaken a program that helps support patient care, community programs, and other safety-net services. Contracting with pharmacies was a practical adaptation to the way healthcare is delivered today.
Cue the wave of litigation, regulatory disputes, and state legislative activity.
When state 340B laws worked — and what other states can learn
As manufacturers challenged those laws, a pattern began to emerge. Courts paid close attention to how the laws were written. If you’re involved in state-level 340B advocacy, the courts may already be providing a drafting guide.
Arkansas and Louisiana were early examples. Both states passed laws requiring manufacturers to honor 340B pricing for covered entities, even when those entities contracted with pharmacies to dispense medications on their behalf. Manufacturers challenged both laws.
In 2024, the Eighth Circuit upheld Arkansas’s statute. In early 2026, the Fifth Circuit upheld Louisiana’s law. Both courts viewed the laws as state regulation of pharmacies rather than state regulation of the federal 340B program.
West Virginia and Maryland also attempted to preserve access to 340B pricing in contracted pharmacy arrangements. However, as every high school English teacher knows, word choice matters, and the courts focused in on how the laws were written.
The Fourth Circuit focused on the fact that the West Virginia and Maryland laws tied their requirements directly to the federal 340B program. Maryland’s statute repeatedly referenced terms such as “340B manufacturer,” “340B drug,” and “covered entity.”
That’s where the court drew the line. In its view, the states were doing more than regulating pharmacies. They were effectively adding requirements tied to participation in a federal program.
So this is where we are. Hospitals want to preserve access to a program they depend on. Manufacturers want limits on obligations they believe Congress never imposed. States are trying to protect arrangements that help keep services available in communities where access to care is already fragile. Federal appeals courts are deciding who gets the final say.
Everyone involved has a theory about what Congress intended. Coincidentally, those interpretations tend to produce outcomes that are financially beneficial to the people advancing them.
Billions of dollars are at stake and the arguments come down to commas, not literally in this case, but it has happened.
A new question: who ultimately receives the benefit?
When Congress created 340B in 1992, the path was relatively straightforward. Manufacturers sold drugs, hospitals purchased them at a discount, and patients received care. But healthcare doesn’t work that way anymore.
Huge corporations own health plans, PBMs, pharmacies, and provider organizations. Everyone is looking for ways to control a bigger share of healthcare spending.
As a result, the same company may touch multiple points in the same transaction. They insure the patient and process the claim. They own the pharmacy dispensing the medication and may even employ the physician writing the prescription. It almost makes you long for the halcyon days when hospitals expanded their geographic footprint through friendly relations with retail pharmacies.
Once 340B savings enter a vertically integrated healthcare company, how do you know where the money ends up?
Following the money used to be easier. A discount created in one part of the transaction can now move through multiple affiliated companies before anyone tries to determine who actually benefited from it.
According to complaints filed by three separate hospital systems, CVS and its subsidiaries allegedly “implemented a secret pricing scheme for 340B drugs, which required cooperation among its affiliated entities within the 340B drug supply chain.”
In fact, the complaints state it directly: “this scheme could not function without vertical integration. It requires a PBM willing to artificially slash reimbursement rates after the point of sale, a contract pharmacy willing to accept that reduced rate, and a captive TPA willing to mask the true transaction from the Covered Entity.”
Has healthcare become so complex that covered entities can no longer easily determine whether they are receiving the full benefit of the program?
What hospitals and health systems should do now
For hospitals and health systems that rely on 340B savings, the lesson is simple: things that once felt settled no longer are. Manufacturers, courts, regulators, and providers are all challenging long-held understandings about how the program works and who benefits from it.
If your organization depends on 340B savings to support patient care, community programs, specialty services, or uncompensated care, now is not the time to assume those resources will simply continue to be available.
The future of 340B is being decided in places most patients will never see. That doesn’t mean every hospital CEO needs to become a 340B policy expert. It does mean understanding where your organization’s 340B savings come from, how those savings reach your balance sheet, and what could threaten them.
