Healthcare Compliance

340B claims data requirements put hospital discounts under stress

Hospitals that do not meet Lilly’s 340B compliance requirements stand to imminently lose price discounts, raising margin, cash-flow and operational concerns.

Published June 3, 2026 5:08 pm | Updated June 19, 2026 12:29 pm

June 18 update

Eli Lilly has followed through with cutting off 340B discounts for certain hospitals that have yet to submit the required claims data (see the original story below), provider advocacy groups said Thursday.

“As a result of Lilly’s decision to deny hospitals access to 340B pricing for the company’s products unless they submit millions of lines of patient claims-level data from their in-house retail and mixed-use pharmacies, affected hospitals now must purchase those drugs at the significantly higher wholesale acquisition cost, eliminating the statutory 340B savings they should be receiving,” 340B Health said.

The Health Resources and Services Administration (HRSA), the federal agency that oversees 340B, has not publicly responded to Lilly’s actions since the company said hospitals needed to submit data for all 340B claims starting Feb. 1. That marked an escalation from previous manufacturer mandates that applied to 340B contract pharmacy claims.

Other companies since have demanded that hospitals submit in-house pharmacy data as well.

“If HRSA allows this unlawful conduct to stand, many other drugmakers are poised to follow suit, dramatically increasing costs for safety-net providers and threatening healthcare access for millions of patients,” Maureen Testoni, president and CEO of 340B Health, said in a written statement.

The American Hospital Association said Congress needs to intervene.

“Congress should immediately use its oversight authority and demand HHS take a position on drug companies’ attempts to hijack the 340B program through burdensome claims-data demands,” Rick Pollack, AHA president and CEO, said in a written statement.

Waiting on HRSA to respond

During a session at HFMA’s Annual Conference this month, Testoni contrasted HRSA’s inaction around the recent claims demands of Lilly and other manufacturers with the agency’s response to prior attempts by manufacturers to unilaterally implement a rebate model. (HRSA now appears ready to sign off on a rebate model after the agency ensured it would have oversight of the implementation.)

“When manufacturers first came out with this rebate concept that they want to do themselves, HRSA turned on a dime to get out an enforcement letter against the manufacturers, which then resulted in in litigation,” Testoni said. “But now they’ve just been very silent, and I don’t know if they want to see if Lilly’s really going to pull the trigger before they get involved in litigation or not, but it makes it difficult.”

Testoni anticipated the issue ending up in federal court but said the legal strategy won’t be clear until HRSA comes out for or against the manufacturers’ actions.

She traced Lilly’s strategy to decisions by two appeals courts amid litigation in recent years concerning manufacturer efforts to restrict 340B contract pharmacy discounts. The court rulings supported the right of manufacturers to require that covered entities submit contract pharmacy data.

However, “there wasn’t really a decision around the burden, and what they’re trying to do now is way more burdensome,” Testoni said.

Original story

Provider advocates criticized Eli Lilly for ramping up pressure on hospitals to comply with a new policy regarding claims submission in the 340B Drug Pricing Program.

The drug manufacturer said holdout hospitals will lose 340B discounts on all Lilly products unless the hospitals quickly comply with a mandate issued earlier this year to submit claims data for in-house pharmacy drugs. A notice to that effect was sent June 1 to the Health Resources and Services Administration (HRSA), the federal agency that oversees the 340B program.

Lilly said 30% of 340B covered entities have not complied with the new requirement. The risk of immediate exclusion is limited to certain large health systems, per the company’s notice. Those organizations have been notified that they have five business days from the date of the notice to come into compliance.

“A large majority of covered entities accepted Lilly’s offer and submitted data without incident,” the letter to HRSA states. “A minority of entities — led by the country’s largest and best-resourced hospitals and organized through their trade associations — continues to refuse to submit data.”

HRSA has not responded to the notice except to say it is reviewing the policy to determine next steps.

Lilly justified the policy, which began Feb. 1, as necessary to avoid duplicate discounts for drugs included in both 340B and the Medicare price negotiations under the Inflation Reduction Act.

Manufacturers also have expressed concern about overlap in discounts between 340B and the Medicaid Drug Rebate Program. Another issue they hope to mitigate via enhanced claims data submission is diversion, whereby a 340B drug is dispensed to someone who does not meet the program’s definition of an eligible patient.

What Lilly’s 340B claims data policy requires

Compliance with Lilly’s policy entails submitting both pharmacy and medical claims data within 45 calendar days of the original dispense date for most drugs, and 60 days for certain infused, injected or clinically administered specialty medications.

Among more than 10 data elements to be submitted through the 340B ESP platform with each claim are the quantity dispensed, the duration of the supply, the refill code and the medical modifier.

The provider advocacy group 340B Health described the new policy as requiring hospitals to “turn over millions of lines of patient claims data.”

The American Hospital Association (AHA) called on HHS and HRSA to intervene.

“This administration has repeatedly shown that it is willing to be tough on drug companies to protect America’s patients from profiteering and price gouging,” the AHA stated. “On behalf of the hospitals and health systems that serve America’s rural and most underserved communities, we ask HHS to show that same toughness here and prevent Lilly from moving forward with this illegal and harmful policy.”

Current or pending legislation exempts covered entities in 10 states from requirements for 340B claims submission. Lilly thus has not implemented the new mandate for providers in Colorado, Maine, Nebraska, North Dakota, Oregon, Rhode Island, South Dakota, Tennessee, Vermont and West Virginia, along with federally qualified health centers in New Mexico.

Other drug companies follow suit

The new policy expands previous requirements by Lilly and other manufacturers for claims data on drugs dispensed at contract pharmacies.

“Although platform details and product scope differ, the common thread is straightforward. Access to discount pricing is increasingly conditioned on the ability to produce verified claim-level data on schedule and through a specified portal,” the law firm of Frier Levitt, which represents providers in 340B litigation, wrote in a March analysis.

Novo Nordisk implemented a similar policy to Lilly effective April 1 (but does not list North Dakota and West Virginia as exempted states). AstraZeneca ended exemptions for in-house pharmacy drugs with respect to its reporting requirement effective May 1, and Bristol Myers Squibb acted likewise.

“If the federal government does not act, hundreds of other drugmakers could do the same, massively increasing costs,” 340B Health wrote in its statement on Lilly’s expanded requirements.

In a May letter to Lilly, the AHA said providers understand the need for program integrity measures. A better approach than requiring claims submissions to manufacturers, however, would be to install a third-party data clearinghouse that would have federal oversight.

“This ‘clearinghouse’ would identify any instances of duplicate discounts or diversion, while limiting the costs imposed on 340B hospitals and protecting their legitimate interests in maintaining data and patient privacy,” the AHA wrote.

Such an approach would be “less burdensome and expensive than Lilly’s unilateral claims-data policy, but it provides the same transparency that both the AHA and Lilly are committed to ensuring.”

Operational and compliance challenges for hospitals

The Frier Levitt analysis states that if a provider loses access to 340B discounts, it first should look to HRSA’s 340B administrative dispute resolution (ADR) process.

“Because the U.S. Supreme Court has held that there is no private right of action under the 340B statute, the ADR process is the principal federal mechanism for covered entities to enforce their pricing rights,” the analysis states.

The firm says providers should ensure they are operationally ready for the new requirements to become commonplace.

“Pharmacy, revenue cycle and compliance teams should be able to connect each dispense to a qualifying encounter, a prescriber and a clearly identified payer, then furnish those data elements in the format and cadence the manufacturer requires,” according to the analysis. 

What hospitals should monitor next

The various manufacturer policies may be the precursor to a larger change if, as expected, HRSA pushes through a comprehensive 340B rebate model. Providers would need to float the full price for a covered drug, then submit claims data to receive a rebate.

After an initially proposed rebate model was scuttled by litigation in early 2026, HRSA drafted another model in the spring. Seeking to address one of the issues that led to the legal challenges, the agency subsequently solicited stakeholder comments via a formal request for information.

Despite receiving more than 5,000 public comments, HRSA took only five weeks from the comment deadline to send the model to the Office of Management and Budget for a final review, which is in progress. The model is expected to be formally published over the summer, potentially leading to a 2027 start date.

Advertisements

googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text1' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text2' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text3' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text4' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text5' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text6' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-text7' ); } );
googletag.cmd.push( function () { googletag.display( 'hfma-gpt-leaderboard' ); } );

{{ loadingHeading }}

{{ loadingSubHeading }}

We’re having trouble logging you in.

For assistance, contact our Member Services Team.

Your session has expired.

Please reload the page and try again.