On July 31, 2026, HRSA revived the 340B rebate pilot. It starts January 1, 2027, on the 25 drugs that already carry a negotiated Medicare price. This post explains what changed, why the rebate submission itself is now a compliance record, and how our claims, audit, and financial infrastructure is built around that reality.
A Quick Summary of What’s Changed
Today, 340B and Medicare’s Maximum Fair Price (MFP) run on different clocks. The 340B discount applies at point of purchase, while the MFP refund (if one applies) comes weeks or months later. When a manufacturer can’t confirm a claim was 340B, it often withholds the refund and leaves the covered entity to prove a negative.
Starting January 1, 2027, that changes for 25 pilot drugs. Both the 340B rebate and the MFP refund become retrospective: you buy at WAC, submit the claim data, and the manufacturer decides both concessions off the same record. The timing mismatch behind most duplicate-discount disputes disappears on those drugs.
The rebate submission is now your compliance record
Under the previously proposed Pilot model, a manufacturer that suspects a rebate claim wasn’t 340B-eligible could deny it, leaving you to dispute the denial afterward. Under the newly proposed Pilot, manufacturers cannot deny a rebate for eligibility, diversion, Medicaid duplicate discounts, or a missing WAC purchase. Such concerns now go to HRSA, through an audit or dispute process.
Every rebate submission is now a claims-level 340B assertion, on standardized fields, sitting in front of HRSA. The rebate and the compliance record aren’t two separate things anymore. Getting the submission right the first time matters more than being ready to argue a denial later.
A few dates worth knowing
- September 24, 2026. HRSA posts which manufacturer plans it approved.
- December 2026. Manufacturers send covered entities their required 90-day notice.
- January 1, 2027. The pilot goes live on the 25 selected drugs.
Bluesight’s Strategy
Over the past year, many vendors pitched deduplication and reconciliation tools built for the old timing mismatch. We didn’t build one, and we told customers why: the two programs were converging, and a tool built for a mismatch that was about to disappear would have gone stale right when you needed it most. Instead, we put the work into claims ingestion, the one piece that holds up regardless of how the regulation landed.
We’ll learn exactly where to route your 340B claims data on the same timeline as everyone else. What’s different about Bluesight is that our claims ingestion, purchasing decision support, and audit logic have been in progress since early 2026.
Roadmap: Bluesight’s Procurement Intelligence is Ready to Support You
- Claims first: 837 medical claims are already in pilot, NCPDP pharmacy claims are next. One claims integration feeds both the 340B and MFP sides, so the data exists before either program needs it.
- Deduplication, finalized as a mechanism, not a guess: In a world with a 100% overlap between 340B rebates and MFP, once a claim is tracked, checking for duplication stops being a probabilistic guess and becomes a direct lookup: does the same claim data show up as tracked in both places? That’s the model we’re building toward and are ready to back it up with the needed claims data.
- Decision support before the money moves. For each NDC, the question isn’t just what a rebate is worth after the fact. It’s what to buy in the first place: WAC, assume a rebate to negotiated MFP, or assume a rebate to 340B ceiling. We’re building that comparison based on your actual claims and payer mix, for that drug, at your site.
- Financial reconciliation closes the loop. After making the right purchase decision, you need to match what you paid at WAC against what was actually rebated or refunded, on both the 340B and MFP side. No rebate-only platform ever sees your invoice, meaning this reconciliation only happens where the invoice data already lives.
- Registering as a Third-Party Support Entity (TPSE): On the Medicare side, refund payments, remittance detail, claim status, and the manufacturer credit ledger all move through a federal system. By registering as a TPSE, Bluesight will help make this data visible to you. This is particularly valuable for reconciliation challenges such as a manufacturer reversing a payment it later decides was a 340B claim.
Questions about how this affects your organization and how Bluesight can support you? Reach out to our team.