Eli Lilly issues data sharing ultimatum to 340B hospitals
Decision brief
Answer first · skim in under a minute
Structured plan for Eli Lilly issues data sharing ultimatum to 340B hospitals
Eli Lilly issues data sharing ultimatum to 340B hospitals: five business days to deliver claims-level data for in-house and pharmacy dispenses, or wholesalers pull discounted pricing for an initial wave of holdouts.
Contents12 sections
Key Takeaways
- Policy effective Feb. 1, 2026, requires claims data for in-house and pharmacy 340B dispenses.
- Lilly reported about 70% compliance (~2,300 entities) and ~1,000 holdouts after two reminder rounds.
- Initial noncompliant systems faced a June 8, 2026, wholesaler eligibility cutoff.
- Ten states with claims-submission restrictions were carved out of Lilly's mandate.
What exactly did Eli Lilly tell 340B hospitals?
On June 1, 2026, Lilly said it would instruct wholesalers to end 340B pricing for an initial set of covered entities that still refused claims-data submission.
Those entities received five business days to accept Lilly's offer by submitting the outstanding data.
The company said it would extend the same course to remaining holdouts in subsequent weeks.
Why does Lilly say it needs claims-level data?
Lilly frames the data as necessary to identify unlawful duplicate discounts, audit covered entities, and support Inflation Reduction Act compliance.
The Feb. 1 expansion asked for the same de-identified claims detail for in-house pharmacy dispenses that many entities already send for contract pharmacies.
Broader 340B pricing fights continue in court; a March 2026 Reuters report covered revived False Claims Act overcharge allegations against other manufacturers.
How large is the noncompliance pool?
Lilly told HRSA leadership that about 70% of distinct covered entities—roughly 2,300—had complied.
About 1,000 entities remained after two rounds of reminder letters.
The first enforcement wave targeted predominantly large, well-resourced health systems, according to company characterizations repeated in trade coverage.
- ~2,300 compliant distinct entities
- ~1,000 holdouts after reminders
- Five business days from notice to June 8 cutoff for the first wave
Which states are exempt from Lilly's data mandate?
Lilly did not implement the new mandate for covered entities in Colorado, Maine, Nebraska, North Dakota, Oregon, Rhode Island, South Dakota, Tennessee, Vermont, and West Virginia.
Federally qualified health centers in New Mexico were also carved out under pending or current state restrictions.
Those carve-outs show how state pharmacy and claims laws still shape manufacturer 340B operations.
What should hospital finance and pharmacy leaders do now?
Inventory which Lilly NDCs move through 340B and estimate margin impact if wholesaler eligibility is pulled.
Confirm whether your entity already submits claims feeds that meet Lilly's schema for in-house dispenses.
Document legal review of state restrictions before deciding whether to share data or litigate.
What remains unproven about manufacturer data mandates?
HRSA has not publicly blessed manufacturer cutoffs tied to in-house claims feeds as a settled compliance tool.
Hospitals argue administrative burden and patient-access harm; manufacturers argue duplicate-discount waste.
Until courts or HHS issue clearer rules, both sides will keep using commercial use and litigation.
How does the Inflation Reduction Act connect to Lilly's data ask?
Lilly has argued that claims-level detail is required not only for classic duplicate-discount policing but also for manufacturer obligations that flow from the Inflation Reduction Act drug-pricing architecture.
Without a clear view of which 340B claims overlap with Medicaid rebates or other discount pathways, manufacturers say they cannot reliably prove compliance in audits.
Hospital groups counter that manufacturers are using data demands as a commercial tool to shrink 340B volumes rather than as a narrow anti-fraud control.
What happens operationally when wholesaler eligibility is pulled?
When a manufacturer instructs wholesalers that a covered entity is no longer 340B-eligible for its products, purchases typically flip to wholesale acquisition cost until the entity is restored.
Finance teams should model days of cash tied up if high-cost Lilly products suddenly lose 340B ceiling pricing mid-cycle.
Pharmacy leaders should also confirm whether contract-pharmacy networks can still access inventory under non-340B terms without creating diversion or accumulation errors.
Documented escalation paths to counsel matter because restoration timelines after late data submission are not standardized in public guidance.
Covered entities in the carved-out states still need separate playbooks because Lilly's mandate does not apply uniformly nationwide.
Related NovaPharma coverage
- Lilly 340B and Ebola vaccine news roundup
- Eli Lilly gene therapy cholesterol deals
- Lilly vaccine research and buyouts
Frequently Asked Questions
What deadline did Eli Lilly set for 340B claims data?
Lilly notified an initial set of holdout covered entities that they had five business days to submit outstanding claims data or lose 340B pricing eligibility at wholesalers around June 8, 2026.
How many covered entities had not complied?
Lilly said about 70%, or roughly 2,300 distinct entities, had complied with the Feb. 1, 2026, policy, leaving about 1,000 covered entities still noncompliant after reminder letters.
Does federal law require manufacturers to participate in 340B?
Manufacturers that want Medicaid coverage for their outpatient drugs generally must offer 340B ceiling prices to eligible covered entities. Disputes now focus on data conditions attached to those discounts.
Primary Sources
Eli Lilly pipeline snapshot
One-screen view of active programs, phases, and recent catalysts from public sources.
Sources & references 1 primary sources
Sources verified at publication. See our editorial policy and data sources.
This article follows our editorial standards. Report a correction via editorial contact.
