The 340B Drug Pricing Program requires participating manufacturers to sell covered outpatient drugs to qualifying entities—safety net hospitals, federally qualified health centers, certain other providers—at prices not exceeding a statutory ceiling derived from Medicaid rebate calculations. These prices, known as 340B ceiling prices, can be sixty to ninety percent below WAC for drugs with significant Medicaid rebate obligations. They are never published. They are not reflected in NADAC, which covers retail pharmacy only. They appear in ASP calculations only to the extent that 340B sales are included in manufacturer-reported average sales data—which is a contested methodological question. The result is a pricing obligation of enormous scale that is essentially invisible in the public benchmark data that platforms like MedPricer use as their analytical foundation.
Scale of the 340B Program and Its Pricing Implications
340B has grown from a modest safety net program into a substantial pharmaceutical market channel. By recent estimates, 340B purchases represent between five and eight percent of all outpatient drug purchases in the United States, with the share higher for certain therapeutic categories heavily used by safety net populations. For manufacturers of drugs used disproportionately in oncology centers and safety net hospitals—which are major 340B covered entities—the program’s pricing obligations can be a meaningful fraction of total unit sales.
A manufacturer whose drug is heavily used in the 340B channel is, in effect, selling a substantial portion of its volume at a price that may be sixty, seventy, or eighty percent below WAC. That obligation affects gross-to-net calculations profoundly but is not separately disclosed. The ASP impact is technically included in the ASP calculation, but only to the extent that 340B purchases are part of the sales data manufacturers report—a methodological question that HRSA and CMS have debated for years without definitive resolution.
What MedPricer’s WAC-ASP Spread Tells and Doesn’t Tell
For analysts using MedPricer’s cross-benchmark data, the 340B blind spot means that a widening WAC-ASP spread cannot reliably be attributed to PBM rebate dynamics alone. If a drug’s ASP is declining relative to WAC, the signal is consistent with several mechanisms: increasing PBM rebates, growing 340B volume, Medicaid rebate escalation, or some combination. The spread is real and observable. The attribution is not.
This is not a failure of MedPricer’s methodology—it is a function of the public data environment. No external dataset can distinguish between a dollar of gross-to-net driven by PBM rebates and a dollar driven by 340B obligations. But the analytical implication is important: cross-dataset drug pricing signals should be interpreted with awareness that the 340B channel is a substantial, confidential, and analytically unobservable component of the real pricing landscape.
The Policy Contest Over 340B and Its Data Implications
Manufacturers have increasingly restricted 340B pricing to certain dispensing configurations, particularly limiting contract pharmacy arrangements through which 340B entities use community pharmacies to dispense drugs at 340B prices. The legal battles over these restrictions—Novartis, AstraZeneca, and others against HRSA—are fundamentally disputes about the boundaries of 340B obligations.
The pricing implications of these restrictions are not visible in public benchmark data. If a manufacturer successfully limits 340B volume, the effect on ASP would be a modest upward pressure—fewer low-price 340B sales in the average. An analyst observing ASP stabilization for a drug whose manufacturer has implemented 340B restrictions might attribute it to contracting dynamics rather than channel mix changes. Without 340B volume data—which HRSA does not publish at the drug level—the two interpretations cannot be distinguished from external data.
The Analytical Workaround
Sophisticated users of MedPricer’s platform can develop proxy approaches to the 340B blind spot: tracking the share of prescriptions dispensed through safety net facilities for specific drugs, correlating ASP trajectory changes with known manufacturer 340B policy announcements, and building drug-specific models of likely 340B exposure based on covered entity utilization data that HRSA publishes in aggregate form. These workarounds are laborious and imprecise. They are also the best available approach given the structural confidentiality of 340B pricing.
What MedPricer’s dataset provides is the baseline against which these proxy corrections can be applied—the observable WAC-ASP spread that represents the sum of all gross-to-net mechanisms, of which 340B is one. That is analytically useful even if it requires supplementary work to disaggregate the 340B component from PBM and Medicaid rebate dynamics.
