On August 3, 2026, HRSA published a revised notice establishing a 340B Rebate Model Pilot Program with a January 1, 2027 effective date. Manufacturer plan submissions are due August 24, 2026. Approvals follow by September 24. Covered entities will then receive 90 days notice before the model takes effect for selected drugs.
The program covers approximately 5.5 percent of total 340B sales — the drugs selected under Medicare’s Drug Price Negotiation Program for 2026 and 2027. The remaining 94.5 percent continue under the upfront discount model.
The stated goal is to help manufacturers avoid paying duplicate discounts on drugs covered under both 340B and Medicare price negotiations. That is a legitimate concern. The mechanism chosen to address it — requiring covered entities to purchase at wholesale acquisition cost and wait for a manufacturer rebate after dispensing — is not the right answer to the underlying problem. And understanding why requires understanding what the underlying problem actually is.
The problem is data — not discounts
The 340B duplicate discount dispute exists because manufacturers and covered entities are working from different data sets with different methodologies and reaching different conclusions about the same transactions.
Manufacturers claim duplicate discounts are occurring — that the same drug transaction is receiving both a 340B discount and a Medicaid rebate. Covered entities dispute the methodology used to identify those transactions. The disagreement is not primarily about whether covered entities are acting in bad faith. It is about whether the data being used to identify duplicate discounts is accurate, complete, and agreed upon by both parties.
That is a data transparency problem. The rebate model does not solve it. The rebate model shifts the financial risk of the dispute onto covered entities — by requiring them to purchase at WAC and wait for a rebate — while leaving the underlying data disagreement entirely unresolved.
An FQHC that purchases a negotiated drug at WAC, dispenses it to a 340B eligible patient, submits a rebate claim, and waits for the manufacturer to approve and pay that claim is now carrying the cash flow risk, the administrative burden, and the dispute resolution risk that previously sat with the manufacturer. The data disagreement that caused the problem in the first place has not been resolved. It has been repriced — and the price has been transferred to the covered entity.
What a neutral clearinghouse actually solves
The tool that resolves a data disagreement is not a financial mechanism. It is a data mechanism — a neutral intermediary that both parties trust to certify whether a given transaction is a legitimate 340B claim and whether a duplicate discount has occurred.
That model exists. A neutral 340B clearinghouse platform is already operational, with partnerships across health centers, primary care associations, and hospital systems in multiple states. The platform certifies 340B claims, prevents duplicate discounts, and provides manufacturers, PBMs, and health plans with a centralized platform to review and verify claims.
The principle behind the clearinghouse model is straightforward. If both the manufacturer and the covered entity can see the same transaction data — certified by a neutral intermediary neither party controls — the question of whether a duplicate discount occurred becomes answerable with evidence rather than assumption. The dispute does not disappear. It becomes resolvable.
The rebate model does not give both parties access to the same data. It gives manufacturers the ability to withhold the discount upfront — shifting cash flow burden to covered entities — and then adjudicate rebate claims through a process that covered entities do not control and cannot independently verify.
That is not transparency. It is a financial restructuring that happens to use transparency language.
The cash flow problem is not theoretical
The administrative and financial burden of the rebate model on covered entities is documented in the public record. Published analysis calculated that a rebate model covering only the 10 drugs selected for Medicare price negotiations in 2026 would affect the average 340B hospital’s cash flow by between $2.34 million and $4.67 million per year.
HRSA’s own analysis has been publicly challenged as understating the true costs — ignoring compliance expenses, cash flow disruption, and administrative burden that covered entities would absorb.
For FQHCs — organizations operating on thin margins, serving Medicaid-dominant patient panels, and depending on 340B program revenue to cross-subsidize services that would otherwise be unfundable — the cash flow impact of purchasing negotiated drugs at WAC and waiting for rebate payment is not a minor operational adjustment. It is a working capital problem that hits hardest at the organizations the 340B program was designed to protect.
What FQHCs need to do before August 24
The August 24 manufacturer submission deadline is not an FQHC deadline — it is the date by which manufacturers who want to participate in the pilot must submit their plans to HRSA. FQHCs cannot prevent manufacturers from participating.
But FQHCs can take three actions before August 24 that position them to manage the pilot’s impact:
First — identify which drugs in your formulary are subject to Medicare Drug Price Negotiation for 2026 and 2027. HRSA has published the list. These are the drugs that could be included in the rebate pilot if their manufacturers submit and receive approval. Knowing your exposure before implementation is the starting point for financial planning.
Second — assess your cash flow capacity. If selected drugs move to a rebate model on January 1, 2027, how long can your organization carry the WAC purchase cost before rebate payment arrives? That is a treasury question that belongs in front of the CFO now — not in December.
Third — monitor HRSA’s publication of approved manufacturer plans. Approved plans are due by September 24. Those documents will determine which specific drugs, which covered entity types, and which distribution channels are affected. The 90-day notice requirement means covered entities will have until late December at the earliest before implementation — but only if they are watching for the approved plans when they publish.
The larger question the pilot is asking
HRSA has stated that the rebate pilot represents more than a narrow solution for negotiated drugs — it is a test of broader claims-level transparency and oversight mechanisms for the 340B program as a whole.
That framing is important. If the pilot is evaluated as a success — even at 5.5 percent of 340B sales — the model has established a precedent for expansion. The 94.5 percent of 340B sales still operating under the upfront discount model could be subject to a future rebate structure if the pilot produces the data transparency outcomes HRSA is seeking.
The covered entity community has consistently argued that data transparency is the right goal — and that a neutral clearinghouse is the right mechanism to achieve it. That argument is now more urgent than ever. The pilot creates a two-year window — with interim findings due and a full evaluation by April 30, 2028 — in which the clearinghouse model and the rebate model will be operating in parallel in the 340B market.
The outcome of that comparison will shape the program for the decade that follows.
The rebate model is HRSA’s answer to a data transparency problem. The covered entity community has a different answer — one that is already operational in states where FQHCs have chosen to lead on transparency rather than wait for a federal mandate to impose it. The next 18 months will determine which answer the program adopts at scale.