The Many Faces of 340B

by | Sep 11, 2026 | Government Pricing and 340B

The many faces of 340B. All of them are real. Transparency, tension, and the future of pharmaceutical access.

For life sciences teams

Few programs in healthcare generate as much debate, confusion and financial complexity as 340B. Most of that debate comes from people describing the part of the program they can see.

Ask four stakeholders what 340B is and you get four accurate answers. It is a lifeline for patients who depend on safety-net providers. It is the funding mechanism that keeps those providers solvent. It is a source of opacity and misaligned incentives. It is a revenue engine carrying growing complexity for pharmacies and manufacturers. All four descriptions are true at once, and the gap between them is where the conflict lives.

One program described four ways 340B sits at the center. Around it are four descriptions held by different stakeholders: a lifeline for patients who depend on safety-net providers, a funding mechanism that supports those providers, a market distortion that creates opacity and misaligned incentives, and a revenue engine that adds complexity for pharmacies and manufacturers. All four descriptions are accurate at the same time. 340B ONE PROGRAM A lifeline For patients who depend on safety-net providers A funding mechanism Economic support that keeps those providers open A market distortion Opacity and incentives pointing in different directions A revenue engine Growing complexity for pharmacy and manufacturer All four are true at the same time
FIGURE 1. Most organizations understand their own face of the program with real precision. Very few understand the other three.

What the program was built to do

The original purpose was straightforward. Let eligible safety-net providers purchase outpatient drugs at a discount so they could stretch scarce federal resources and extend services to vulnerable populations. Oncology programs funded care for patients who could not otherwise afford treatment. Rural providers extended reach into communities with little else nearby. Uncompensated care got underwritten.

That is one face of 340B, and it is a good one. It is no longer the only one.

The safety-net view

For disproportionate share hospitals and other covered entities, 340B has become an economic support mechanism rather than a discount program. It offsets declining reimbursement as payer mix shifts, uncompensated care delivered without corresponding payment, labor costs in a market that keeps bidding up clinical staff, and capital needs for growing patient populations.

From inside that position, 340B is not optional. It is operationally necessary, and many would argue that without it portions of the safety net begin to fracture. That view deserves to be understood rather than dismissed, because it is describing something real about how those institutions actually stay open.

The manufacturer view

Manufacturers see the same program from the other end of the transaction, and what they see is exposure they cannot measure. Eligible utilization cannot be validated at the claim level. Claim-level economics and downstream flows are not visible. Medicaid duplicate discount risk sits unresolved on the balance sheet. Contract pharmacy networks have grown in ways that make patient eligibility difficult to establish.

From that position, 340B stopped looking like a targeted safety-net program some time ago. It looks like a broad commercial channel embedded inside the healthcare system, and the financial consequences run straight through Gross-to-Net.

Contract pharmacy is where the argument concentrates

No part of the program has generated more controversy. Contract pharmacy arrangements were originally limited in scope. Today some covered entities maintain hundreds of these relationships, and a few maintain thousands.

Supporters point to access. More dispensing locations means more convenience for patients who would otherwise travel to a single hospital pharmacy. Critics point to opacity. A sprawling network makes it harder to establish which patients are being served, where the economics land and whether the arrangement still reflects safety-net intent.

Both concerns can be true at once. The contract pharmacy debate is not binary. It is a reflection of the program’s broader complexity, and it is unresolvable as long as the underlying transaction data stays fragmented.

Where the 340B discount goes after the manufacturer funds it The manufacturer funds the discount and sells at the 340B price to a covered entity. The covered entity dispenses through a contract pharmacy, which takes dispensing and administrative fees. Nothing in the statute requires the discount to reach the patient. Payer and pharmacy benefit manager reimbursement sits across the last three steps. Manufacturer visibility ends at the covered entity. PAYER AND PBM REIMBURSEMENT SITS ACROSS EVERYTHING DOWNSTREAM Manufacturer Funds the discount Covered entity Buys at the ceiling price Contract pharmacy Dispenses and takes fees Patient No required pass-through Discount funded 340B price paid Fees taken Retail price paid Manufacturer visibility ends here Everything to the right is inferred, not observed
FIGURE 2. The manufacturer funds the discount and then loses sight of it. Nothing in the statute requires the discount to reach the patient.

The eligibility question nobody has settled

This is where the program becomes genuinely hard. One of the largest ongoing disputes is over who actually qualifies as a 340B patient, and the operational definitions are far less clear than most people assume.

As health systems expand physician affiliations, integrated delivery networks, specialty referrals and outpatient relationships, the line between a truly underserved patient and a commercially insured patient treated somewhere inside a covered entity ecosystem keeps blurring. The ecosystem widened. The definition did not.

The 340B patient eligibility spectrum and how the covered entity ecosystem widened across it A spectrum runs from uninsured and underserved patients on the left to commercially insured patients on the right. Three positions sit along it: safety-net, integrated network built from physician affiliations and referrals, and commercial. The covered entity ecosystem originally covered only the safety-net end and has widened to cover most of the spectrum, which is what makes the eligibility definition contested. Three questions follow: program intent, economic fairness, and manufacturer exposure. WHO COUNTS AS A 340B PATIENT Safety-net Uninsured and underserved Integrated network Physician affiliations and referrals Commercial Insured, inside the ecosystem Original scope The ecosystem as it operates today Program intent Was the program built to cover this population? Economic fairness Are discounts applied the way the policy intended? Manufacturer exposure Who carries the cost of eligibility ambiguity?
FIGURE 3. Three questions follow from the same ambiguity, and they are asked by three different parties who rarely agree on the answer.

The PBM and payer layer

Pharmacy benefit managers and payer economics are now deeply entangled with 340B, which makes the accounting question harder than it looks. Manufacturers fund the discounts and absorb the Gross-to-Net pressure. Covered entities capture program economics. Contract pharmacies capture dispensing economics. PBMs manage the reimbursement flows that sit across all of it.

Patients are the intended beneficiaries. Whether they consistently benefit is a separate question, and the honest answer is that nobody can prove it either way at scale, because no single party holds the whole record.

Transparency is the actual issue

The future of this debate will not turn on whether the program should exist, or on whether hospitals or manufacturers are right. It will turn on transparency, because most stakeholders still operate with fragmented data, incomplete visibility, disconnected incentives and limited understanding of downstream economic behavior.

Opacity does not just create inefficiency. It creates distrust, political conflict, compliance risk and financial instability across the entire ecosystem.

Every structural complaint about 340B, from either direction, reduces to the same root. No single party can see the whole transaction, so every party assumes the worst about the part it cannot see.

Where this stands in September 2026

Two things have changed the stakes since this argument started.

The first is scale. HRSA reported that covered entities purchased $100 billion in covered outpatient drugs in calendar year 2025, roughly 23 percent above the prior year, with disproportionate share hospitals accounting for about $79 billion of it. A program of that size is no longer a line item in anyone’s model.

The second is mechanism. HRSA’s revised 340B Rebate Model Pilot Program takes effect January 1, 2027, and it changes how the discount is delivered for a narrow set of drugs. Covered entities in the pilot will purchase at wholesale acquisition cost and claim the difference back as a rebate, which means the discount becomes a claim rather than a price. That is a direct answer to the transparency problem, and it moves cost and administrative burden onto the entities least able to absorb either. I wrote about what that shift does to Gross-to-Net operations in Government Pricing Is No Longer a Calculation.

Both things are true, and that is the whole problem.

Claim-level data is the only credible route to resolving duplicate discounts and eligibility disputes.

The mechanism that produces that data also puts a cash gap and an administrative cost on safety-net providers.

A solution that fixes transparency by weakening the providers it was written to protect has not actually solved anything.

What structural evolution would look like

The path forward is not elimination, and it is not preservation of the status quo. It is structural evolution across five fronts.

  1. Better data visibility. Claim-level transparency that lets every party validate utilization and economics rather than infer them.
  2. Clearer patient eligibility standards. Operational definitions that reflect the program’s original safety-net intent and survive contact with an integrated delivery network.
  3. Contract pharmacy accountability. Frameworks that match the scale the contract pharmacy ecosystem has actually reached.
  4. Duplicate discount mitigation. Systemic solutions rather than retrospective disputes over overlapping discount obligations.
  5. Aligned incentives. A closer relationship between patient benefit and the economics that drive participation.

Most importantly, the path forward requires acknowledging that there are many faces of 340B. Some are good. Some are problematic. Most are complicated. Reducing the conversation to “340B is broken” or “340B is untouchable” misses the reality entirely. This is not a simple issue. It is an ecosystem issue.

Patients + Profitability

At the center of every healthcare economic debate is one question. Are we improving the patient journey while creating a system that can sustain itself?

In the long run, patients and profitability are not competing objectives. Organizations that create operational visibility across the full ecosystem, align channel strategy with both patient and financial goals, and build incentives that serve patients rather than work around them will improve outcomes, reduce unnecessary leakage and hold up financially over time.

340B is no exception. The path forward is not simpler. It is smarter.

The companion piece on how the discount mechanism itself is changing is here. What a pharmacy-counter stop does to the rebate number is in You Can Be Exactly Right About the Wrong Number. The ten places a patient can leave are on the philosophy page, and the terms used here are defined in the glossary. The patient-side view of the same ten exits is at Where did your treatment stop? Reading coverage posture and site-of-care concentration from outside your own data is what NaviCuris is built to do.

Primary sources.

This analysis reflects a commitment to understanding the full 340B ecosystem rather than one side of it. Program figures and terms reflect publicly available federal data and notices as of September 11, 2026, and are subject to change, agency discretion and litigation. This article is commentary, not legal, tax, regulatory or pricing advice. The views expressed are my own and are not made on behalf of any current or former employer. All trademarks belong to their respective owners.

Free by email

The 5 Layers of GTN™, in your inbox

Gross-to-Net from someone who has run it. Tuesdays and Thursdays.

Subscribe on Substack
Disclosure: who pays for this work
LinkedIn Newsletter Podcast YouTube Instagram