The 340B network as a graph — which DSH hospitals route through which contract pharmacies, what the revenue implication is, and who's exposed to manufacturer restrictions.
What it is
340B Contract Pharmacy Map turns HRSA's 340B Office of Pharmacy Affairs (OPAIS) data — public, downloadable, and almost never used at scale — into a navigable network graph. Every 340B covered entity is mapped to every contract pharmacy it uses; every contract pharmacy is reverse-indexed to the covered entities it serves; manufacturer restriction status (Lilly, Sanofi, Novo Nordisk, AstraZeneca, Boehringer Ingelheim, and a growing list) is overlaid by entity and pharmacy.
For PE firms doing 340B-dependent platform deals (community oncology, FQHC roll-ups, dialysis adjacencies), the map sizes the revenue at stake from any given manufacturer restriction and identifies covered-entity concentration risk. For pharma manufacturers, the same data answers the inverse question: which entities and pharmacies represent the largest exposure to a proposed restriction, and where the litigation risk concentrates.
Sold under named institutional license. Pricing scales with whether the buyer needs the entity-side cut, the manufacturer-side cut, or both.
Primary data sources
- HRSA OPAIS — Covered entity database, contract pharmacy database, registered relationships
- Manufacturer 340B restriction notices — Active restrictions by manufacturer and product
- CMS Medicare cost reports — DSH percentage, hospital size and case mix
- Federal Register and HRSA dispute postings — Active disputes and policy developments
Buyers
- Healthcare PE firms underwriting 340B-dependent platform deals
- Pharma trade and government affairs
- Specialty pharmacy strategy
- 340B program directors at large covered entities
- Healthcare attorneys advising on 340B disputes
Methodology
Graph is rebuilt monthly from the OPAIS public extract. Manufacturer restriction overlays carry effective dates and source citations.
Inquire about access
340B Contract Pharmacy Map is sold under named institutional license. Pricing is scoped per engagement. Reach out with the institutional context (organization, role, intended use) and we'll route a relevant scope of work.