By Lauren LeMoine, PharmD, MBA
Senior Director of Clinical Strategy, Bluesight

For years, hospital and health-system pharmacy leaders have treated the 340B Drug Pricing Program as a dependable source of margin: enroll eligible sites, capture the savings, and manage the compliance requirements that come with them. That assumption no longer holds. 

In recent conversations with health-system pharmacy leaders about the financial outlook into 2027, pressures run through 340B. Some leaders report that the first question their CEO asks, every time, is whether 340B is going away.

With tens of millions of dollars in 340B-driven revenue at risk in some systems, a single system-wide answer is no longer enough for this nuanced landscape.

Converging pressures are compressing the 340B spread

The financial value of 340B rests on the spread between a covered entity’s discounted purchase price and payer reimbursement. Four distinct pressures are now simultaneously compressing that margin. 

First, CMS’s proposed CY 2027 Outpatient Prospective Payment System (OPPS) rule threatens 340B reimbursement through potential payment reductions alongside site-neutral policies. The proposal draws on hospital acquisition cost survey findings — including data showing average 340B acquisition costs about 33% below the average sales price (ASP) — to justify lower payment rates, following legal precedent regarding statutory survey requirements.

Second, the Inflation Reduction Act’s Maximum Fair Prices (MFPs) and statutory non-duplication rules, combined with the 340B rebate pilot, introduce cash-flow delays and operational friction rather than direct payment rate cuts. Moving from upfront 340B discounted pricing to retrospective rebates ties up working capital and requires claim-level visibility to reconcile whether an MFP refund or a 340B discount applies to a given drug. 

Third, drug manufacturers are increasingly enforcing aggressive claims-data submission requirements and contract-pharmacy restrictions (State 340B Anti-Discrimination Laws & Litigation, 2024–2026), creating compliance hurdles and straining resources that directly threaten eligibility and access.

Additionally, the One Big Beautiful Bill Act (OBBBA) poses a threat to 340B eligibility itself. Medicaid funding cuts and coverage losses are expected to lower Medicaid patient volumes, risking that hospitals fall below the statutory Disproportionate Share Hospital (DSH) percentage thresholds required for 340B program participation.

Payers and pharmacy benefit managers (PBMs) are adding pressure directly through aggressive contract terms and retrospective rebate demands. Several health systems report receiving letters and disputes from PBMs demanding expected rebates on 340B-acquired drugs, creating friction around contract pharmacy restrictions and claims data transparency. Each dispute puts dollars at risk and raises the stakes for documenting exactly which drugs, for which patients, were purchased under the program. Weak documentation and lack of granular claims visibility now represent direct financial exposures rather than mere compliance gaps.

The exposure runs to tens of millions, and it is uneven

Pharmacy leaders are now placing concrete numbers on this multi-layered exposure. Some health systems estimate potential OPPS losses — combining 340B reimbursement cuts and broader site-neutral shifts — in the tens of millions of dollars. Others report upwards of $60 million in 340B-driven revenue at risk. 

For systems already operating near break-even on Medicare and Medicare Advantage populations, losses of this magnitude leave virtually no margin to absorb the shock. Crucially, this impact is far from uniform. Safety-net providers, rural referral centers, and disproportionate-share hospitals face distinct, highly variable risk profiles depending on their specific payer mix, service mix, and 340B utilization.

System-wide generalizations are no longer actionable. Site-level financial analysis is now an urgent operational requirement to identify where revenue, savings, and working capital are most at risk.

From all-or-nothing to site-by-site 340B decisions

Because financial pressures vary significantly by facility, health systems are shifting away from blanket, system-wide participation toward evaluating 340B as a series of site-specific business decisions. Very few organizations maintain a uniform profile across all locations, and net value differs widely. 

For instance, a community hospital generating $400,000 to $500,000 annually with minimal contract pharmacy volume may find that ongoing administrative, audit, and compliance burdens outweigh the net return, making program exit a rational choice. In other cases, leaders are assessing whether specific drugs should be shifted to non-340B account purchasing when the administrative burden eclipses program savings.

Conversely, maintaining aggressive 340B participation remains compelling in high-volume safety-net environments. A large health system with a 30% Medicaid share and $200 million in total 340B opportunity can comfortably absorb a $65 million OPPS headwind while still preserving $135 million in crucial net savings. Ultimately, local payer mix, site designation, clinical service lines, and compliance overhead should inform whether a site expands, modifies, or exits 340B participation.

Margin is not the only consideration. For Part B drugs, moving from 340B to WAC can shift cost to patients through the 20% coinsurance. Many health system leaders are uncomfortable passing drug costs to the communities they serve, while acknowledging that a health system that cannot sustain itself cannot serve anyone.

Why 340B is pulling pharmacy into the revenue cycle

Navigating these site-by-site financial decisions requires complete, unblinded visibility into a drug’s entire journey — pulling pharmacy strategy directly into the revenue cycle. A drug’s net 340B value depends on where it was purchased, the specific care setting, the primary payer billed, and whether claims are correctly adjudicated without retrospective dispute.

Consequently, pharmacy leaders are stepping into a shared stewardship role for site-of-care determinations, prior authorizations, and denial management. For example, transitioning patients to ambulatory or home infusion settings simultaneously alters site-neutral payment rules and 340B eligibility. Effective health systems position this collaboration as supporting revenue cycle teams through joint oversight rather than taking over existing workflows.

Many leaders want visibility across the full path, from drug purchase, to patient intake, through remittance reconciliation, sometimes referred to as cradle-to-grave stewardship. For 340B, that visibility answers the questions with the most financial weight: what a site saves after administrative cost, what the exposure is to payer rebate demands and audits, and where a drug’s purchasing status can be defended.

Making the ROI case to executives

Establishing this end-to-end visibility requires dedicated analytics and compliance investments, which pharmacy leaders are increasingly justifying through clear ROI metrics. In one system, funding a $70,000 dedicated analyst position directly protected up to $20 million in vulnerable 340B savings, marking a 285-to-1 return on investment. 

Successful leaders build executive credibility by framing compliance tools and personnel in C-suite terms like margin preservation, break-even timelines, and risk mitigation, aligning cross-functional stakeholders well before bringing proposals to the executive suite.

Sustaining these ROI gains over time requires cohesive infrastructure rather than piecemeal fixes. Dedicated staffing alone cannot deliver long-term results without integrated analytics and unified technology partners, as disconnected point solutions leave critical handoffs unmonitored. The health systems best positioned to navigate 340B’s changing landscape will be those that achieve seamless, end-to-end operational visibility — from initial patient intake and purchasing through final remittance reconciliation.

Questions to pressure-test your 340B strategy

For teams re-evaluating their 340B strategy, these questions frame the financial analysis:

• What does each site save under 340B, net of administrative and compliance costs?
• Which drugs and services drive that value, and which would still make sense at WAC?
• How much revenue is exposed to payer and PBM rebate demands or audits, and how well are 340B purchases documented?
• What data and IT support are needed to answer these questions with confidence?
• How effectively are the pharmacy and revenue cycle teams collaborating to manage patient intake, prior authorizations, and defense of retrospective rebate disputes?

As the OPPS rule and related policy changes take shape, 340B is likely to remain central to hospital finance. For many organizations, the question is shifting from whether to participate to how, where, and at what cost, and who is accountable for the answer. Systems that can show site-level results, net of cost, will be better positioned to defend the program or exit parts of it with confidence.

References

American Hospital Association v. Becerra. (2022). No. 20-1114. Supreme Court of the United States.

Centers for Medicare & Medicaid Services. (2026). Medicare program: Hospital outpatient prospective payment and ambulatory surgical center payment systems and quality reporting programs.

Health Resources & Services Administration. (2026). 340B Rebate Model Pilot Program.

Inflation Reduction Act of 2022. Pub. L. No. 117-169. 117th Congress.

Social Security Act § 1847A: Use of average sales price payment methodology. 42 U.S.C. § 1395w-3a. U.S. Congress.