When it comes to 340B, uncertainty has become an excuse. Decision-makers are fatigued: the rules are contested, headlines change weekly, and the safest move can feel like doing nothing. But waiting isn’t neutral—it lets others define your risk, margins, compliance posture, and ultimately how you manage your 340B exposure.
As complexity stacks with the arrival of new programs and policies, the probability of duplicate discounts doesn’t wait for the courts, and diversion risk doesn’t shrink because we’re tired of fighting about it. If you’re a manufacturer, you already know you’re being asked—explicitly or implicitly—to operate in a system where you’re responsible for outcomes you cannot reliably verify. You’re expected to prevent duplicate discounts and diversion, yet you’re often forced to do it with partial visibility, lagging signals, and after-the-fact arguments.
That’s not compliance. That’s guesswork. And guesswork is not a strategy.
The real question isn’t “rebate or not.” It’s “do you have the facts?”
I’m not arguing that one industry-favored model should replace another overnight. Mechanisms will evolve—chargebacks, rebates, hybrids, new infrastructure, new requirements. That’s the nature of a program this large. What doesn’t change is the common denominator across every viable future: data. Claims-level utilization data is the difference between auditing with confidence versus litigating on hunches; resolving disputes quickly versus letting them calcify into policy battles; and shaping the program’s direction versus being shaped by it.
Manufacturers don’t need more commentary about how 340B “should” work. They need the operational capability to understand how their products are actually utilized and discounted across the system. That includes visibility within individual programs and across intersecting programs, dispenses through both contract and entity-owned pharmacies, and utilization billed through either the pharmacy or medical benefit.
Only with that level of transparency can manufacturers confirm that discounts are being applied as intended. Because if you can’t see the utilization, you can’t manage the risk. And if you can’t manage the risk, others will define the rules for managing it.
What should worry manufacturers is not any single policy dispute, but the accumulation of overlapping programs and incentives that can collide on the same unit of drug. Duplicate discount risk was once treated as a narrow Medicaid issue. That era is over. As more pricing and reimbursement models stack—rebates, inflation-related penalties, and competing government price constructs—the “who paid what, when, and why” question becomes harder to answer after the fact. Each new layer creates another chance for unintended duplication.
The pile is still growing as “Most Favored Nation” concepts re-enter in new forms. Whether or not they carry the MFN label, frameworks like GLOBE, GENEROUS, and GUARD reflect the same pressures: importing external price references or constraints into U.S. reimbursement, with new eligibility rules, lookback periods, and reconciliation mechanics. The result is more definitions, more timing mismatches, and more ways for “duplicate discount” to become “duplicate anything.”
When margins tighten, imprecision becomes intolerable. When scrutiny increases, opacity becomes a liability. The companies that will fare best are those that can produce clean, defensible, unit-level answers proactively—not forensically, after the fact.
HRSA’s RFI comment period on the proposed rebate pilot is not a time to sit passively. It is the administrative record being built that will shape what regulators can implement—and what they can’t.
April 20 isn’t just a deadline—it’s a moment when the people who actually run these workflows can put operational reality into the public record. If manufacturers want future guardrails to be workable, they should use this comment window to be specific: what data is required to prevent duplicate discounts and diversion; where can the data be applied and what kind of duplicate discounts or diversion can manufacturers search for; who can participate in the program and with which products; what timelines are realistic for reconciliation; what constitutes an auditable unit-level record; what security and liability standards must apply to any data exchange; and what dispute-resolution process can function at scale.
As valuable as the rebate model is, manufacturers don’t need to bet on a single end-state model to start making progress. They can begin, TODAY, with the foundational step of collecting claims-level utilization data in a consistent, secure way, directly tied to statutory compliance objectives.
Start with the goal, not the ideology: build a defensible view of 340B utilization; identify objective, data-supported patterns that indicate possible diversion or duplicate discounts; establish repeatable, auditable processes for resolving discrepancies; and commit to using facts to inform decisions. Then, if the market or regulators move further toward broader rebate mechanics, you won’t be starting from zero—you’ll be building from a base of visibility, not speculation.
You don’t have to accept a future where your only choices are litigation or blindly extending discounts and price concessions. There is a third path: measured, disciplined action grounded in data. Collecting claims data is not about punishing covered entities or undermining safety-net care. It’s about making the program function the way it is supposed to—delivering the right discounts in the right circumstances. If 340B is going to remain credible and sustainable, transparency can’t be postponed.
Waiting isn’t a strategy. Uncovering the facts is.
