340B Participation Strategy for PE-Backed Infusion Platforms

340B participation shapes how private equity values and acquires infusion businesses, because the discount it creates can be the single biggest driver of profit in a high-volume infusion operation. The mechanism is straightforward. Covered entities buy infused biologics at 340B ceiling prices, bill payers at ASP-plus rates or a contracted equivalent, and keep the difference. That spread sits on top of whatever the clinic earns for administering the drug, and in oncology or specialty infusion, it often outweighs the administration fee itself.

That is why PE acquirers build deal models around it. HRSA's 2025 covered-entity purchase data put 340B purchases at $100 billion for the year, up from $81.4 billion in 2024. That growth isn't a one-year spike. The program has compounded at roughly 22% a year since 2010. The spread available to covered entities has grown into a pool of capital large enough to reshape acquisition strategy across the sector.

Outpatient infusion sits at the center of that growth. Oncology drugs, biologics, and specialty infusion therapies administered outside the hospital are the fastest-growing segment of 340B purchases, and that is exactly the therapy mix PE-backed platforms have spent the last several years rolling up. As of April 1, 2026, the program counted 15,249 covered entities and 49,214 associated sites. That footprint is wide enough that due diligence on an infusion target now routinely includes a direct question: does this business already have 340B eligibility, or a credible, near-term path to it. The answer often determines the price a buyer is willing to pay.

How the regulatory environment has shifted since platforms modeled their 340B assumptions

Three federal actions are now landing on the same infusion claim at close to the same time: a Medicare payment cut, a rebate model pilot, and the arrival of IRA drug price negotiation in Part B. Platforms that built their 340B margin assumptions before these three moved into motion are working from numbers that no longer match where reimbursement is headed.

Start with the Medicare cut. CMS has proposed reducing Medicare payment for 340B-acquired drugs from ASP plus 6% down to ASP minus 33.4%, a change projected to cut $4.85 billion from reimbursement in 2027. At the same time, CMS would raise the annual remedy offset from 0.5% to 3%. Both changes reduce what a covered entity collects on the same unit of drug it already bought at a discount.

Then add the IRA. Starting in 2028, negotiated prices under the Inflation Reduction Act will apply for the first time to Part B drugs administered in hospital infusion centers. That compresses the reimbursement ceiling on exactly the high-volume infusion drugs that generate the largest 340B spreads, at the same moment the discount itself is under separate pressure from the Medicare rate cut.

Both of these changes depend on a single billing element doing its job correctly. CMS discontinued the JG modifier on January 1, 2025, which left the "TB" modifier as the only identifier marking a claim as 340B-acquired on paper. Every one of the three regulatory shifts described above requires that modifier to be applied correctly, on every claim, at scale. A platform that cannot audit TB modifier accuracy systematically is exposed twice: once to underpayment, and once to the kind of documentation gap that invites false claims scrutiny.

2028 is where all of this converges. Negotiated IRA prices, the 340B discount, and the revised Medicare payment rate will all apply to the same infusion claim in the same year. Any platform that has not run a model combining all three at once is missing a piece of its own forecast, and that gap will not stay hidden once 2028 arrives.

The rebate pilot's operational implications for platforms with and without working capital

The 340B Rebate Model Pilot launched January 1, 2027, and it changes how cash moves through a covered entity's purchasing cycle in a way that punishes organizations without reserves and potentially rewards those with deep working capital, provided the treasury and compliance functions are built for it.

Under the pilot, covered entities purchase drugs at full wholesale acquisition cost (WAC) through their wholesaler account, then request a rebate after the drug has been dispensed to a patient. Manufacturers must pay an approved rebate within 10 days of approval, but the entity still has to front the full, undiscounted cost before it sees a dollar back. The Advisory Board's analysis quoted community health center leaders describing that upfront WAC outlay as "like a death blow" for organizations that cannot absorb the capital hit. The drugs currently in the pilot include Eliquis (Bristol Myers Squibb), Enbrel (Immunex/Amgen), Farxiga (AstraZeneca), Imbruvica (Pharmacyclics/AbbVie), Januvia (Merck), Jardiance (Boehringer Ingelheim), the Novolog and Fiasp product lines (Novo Nordisk), and Stelara and Xarelto (Johnson & Johnson).

The legal uncertainty that had kept platforms from planning around this with any confidence is gone. On July 21, 2026, the D.C. Circuit affirmed that Section 340B permits rebate models, and that manufacturers cannot implement them on their own without HHS Secretarial approval. The court declined to rule on whether HHS should approve the specific proposals manufacturers have put forward, but the structural question, whether rebate models are legal at all, is settled. Platforms can now build plans against a fixed legal framework, not a pending lawsuit.

Two details widen the exposure. The drugs in the pilot also sit on CMS's Medicare Drug Price Negotiation Selected Drug List, so they face rebate-model restructuring and IRA price negotiation at once. HRSA has also signaled it may expand the pilot to additional drugs or future price applicability years, so a platform modeling only the current drug list is modeling a list that may not stay current.

For a well-capitalized PE platform, the WAC-to-rebate float is a cash flow problem that money can solve, in a way it cannot for an under-resourced community clinic. But that only holds if treasury functions can track when rebates get approved, carry the float across every drug in the pilot without disrupting daily operations, and reconcile rebate claims at the volume a large infusion platform generates. Absent that infrastructure, the same float that looks like an advantage on paper turns into the same cash crunch smaller entities are describing now.

How manufacturer restrictions on contract pharmacy access have narrowed the margin opportunity

Federal rulemaking isn't the only thing compressing 340B margin. Manufacturers have been narrowing the contract pharmacy channel on their own, and that narrowing is visible in platform economics well before it appears in any proposed rule.

Drug Channels Institute's analysis of the contract pharmacy market found that nearly 60% of all U.S. pharmacy locations now operate as 340B contract pharmacies. That market is heavily concentrated: five for-profit chains and PBMs, CVS Health, Walgreens, Walmart, Express Scripts/Cigna, and Optum Rx/UnitedHealth Group, together account for more than three-quarters of all contract pharmacy relationships. The same companies that administer commercial payer drug benefits are also the main conduit through which covered entities reach contract pharmacy access. A platform's 340B margin, in other words, can run through the same corporate structure as the payer it's trying to get paid by. So platforms need to know whether their contract pharmacy arrangements rest on stable footing or sit exposed to a PBM's own policy shifts.

Several manufacturers, including Johnson & Johnson, Eli Lilly, Bristol Myers Squibb, Novartis, and Sanofi, have proposed or already put in place restrictions on contract pharmacy access. J&J's lawsuit against HHS over its restriction policy was decided in HHS's favor, but that single ruling hasn't settled how manufacturers behave across the board, and the litigation landscape keeps moving.

The practical risk for a PE platform is specific to each drug, not the program as a whole. If a manufacturer restricts access to a high-volume biologic administered at a contract pharmacy site, the 340B spread on that drug can disappear entirely, with no rulemaking timeline and no regulatory appeal available to bring it back.

Covered entity eligibility and site registration as an ongoing operational discipline, not a diligence checkbox

340B eligibility is a compliance position that has to be actively maintained: patient qualification logic that holds up under audit, child site registration in OPAIS completed before a single 340B-purchased drug is administered, and documentation at every site that can survive scrutiny at any time.

Growth makes this harder, not easier. Every new site a PE platform adds, whether through acquisition or de novo buildout, has to be registered as a child site before first use. The compliance clock doesn't start when the site goes live. It starts at the first administration of a 340B-purchased drug. A platform moving fast on expansion can create exposure simply by outpacing its own registration paperwork.

The TB modifier compounds the stakes here. Because it's now the only identifier marking a claim as 340B on its face, a platform needs the ability to audit modifier application across every site and every claim it submits. A gap in that auditing is a revenue problem, since an incorrect modifier often means an incorrect payment, and it's an enforcement problem, since an incorrect modifier on a submitted claim can read as a false claim.

This changes what due diligence on an acquisition target should actually look like. Confirming that a target "participates in 340B" tells an acquirer almost nothing about whether that participation is defensible. The real diligence question is narrower and harder to answer quickly: does the target have auditable patient qualification logic, correct OPAIS registration across every site, and modifier application that would hold up if a payer or HRSA came looking.

How infusion-specific billing errors compound 340B exposure into a larger revenue problem

The claims carrying a 340B discount are the same claims most exposed to the billing errors that already run through high-cost infusion: J-code unit errors, TB modifier disputes, prior authorization failures, and site-of-care denials. Regulatory pressure on 340B doesn't land on a clean set of claims. It lands on top of error rates that already exist, and the two combine into a bigger revenue gap than either would cause alone.

The J-code unit error deserves particular attention because of how it repeats. A single unit-count mistake on a high-dose biologic infusion can underpay a claim by a meaningful amount, and because infusion patients return for the same drug on a recurring schedule, one wrong unit conversion baked into the charge master repeats on every visit. So the underpayment stays invisible until a targeted audit surfaces it.

Medicare pays for J-code infusion drugs based on ASP, and ASP updates quarterly. Catching underpayment requires reconciling claims against the updated ASP rate every quarter, not reviewing the contract once a year. A platform on an annual reconciliation cycle is carrying a built-in lag between when underpayment starts and when anyone notices it.

TB modifier disputes need their own track, separate from clinical denials. When a payer challenges or rejects a TB modifier, the response that wins is compliance documentation, not a clinical appeal. Sending a modifier dispute through a generic denial workflow slows resolution and lowers the odds of winning it back.

Newly approved drugs add another layer, because they don't get a permanent J-code right away. Until one is assigned, billing has to use an unlisted or NOC code, J3490, J3590, or J9999, and claims in that category draw automatic scrutiny and demand heavier documentation. So it falls hardest on exactly the newer, high-cost drug classes that generate the largest 340B margins.

Infusion-specific platforms exist for this reason. Ruby RCM is built around infusion and buy-and-bill workflows specifically, with J-code unit reconciliation, TB modifier auditing, and denial routing that separates modifier disputes from clinical denials and coding errors. That line-level distinction matters because a general-purpose RCM system, built to handle billing broadly, isn't structured to catch the specific failure points that recur in infusion claims. For platforms running high-volume 340B dispensing, the margin depends not just on what the drug cost to acquire but on whether claims get processed accurately and denials get caught before they turn into write-offs. Revenue lost to a misapplied TB modifier, an underpaid remit, or a preventable denial can erode the 340B spread faster than new patient volume can rebuild it.

Requirements for a Credible 340B Participation Strategy at a PE-Backed Platform

A real 340B participation strategy for a PE-backed infusion platform in 2026 is a risk-adjusted operating model that stress-tests margin against the Medicare rate cut, the rebate pilot's cash flow structure, IRA price negotiation reaching Part B, and manufacturer restrictions on contract pharmacy access, with a specific operational response attached to each exposure.

Model the 2028 convergence now, before it arrives. A financial model should apply the proposed Medicare rate cut, the IRA negotiated prices on the applicable drug list, and the rebate pilot's WAC float to the same high-volume infusion claims at the same time. Platforms that run this combined model first will have a clearer basis for capital allocation and for screening acquisition targets than those still modeling each pressure separately.

Segment the drug portfolio by exposure rather than treating 340B margin as one uniform number. Drugs on the Medicare Drug Price Negotiation Selected Drug List face both IRA negotiation and rebate pilot restructuring at the same time, so a platform's real exposure concentrates in that subset of its portfolio. Mitigation effort should concentrate on that subset of the portfolio.

Build the working capital structure the rebate cycle actually demands. The pilot requires paying full WAC upfront and recovering the discount later as a rebate, so treasury has to confirm it can carry that float on every pilot drug without straining daily operations, and the platform needs the administrative capacity to submit, track, and reconcile rebate claims at volume. Real-time visibility into rebate approval status, wholesaler remittance timing, and payer-specific payment patterns is what prevents that float from becoming a structural disadvantage instead of the cash flow edge a well-capitalized platform should be able to turn it into.

Treat site registration and patient qualification as infrastructure the whole platform depends on, not a one-time step. Every site needs confirmed OPAIS registration and scope-of-project coverage before any 340B-purchased drug is administered there, and a systematic audit comparing registered sites against actual operating locations belongs at the front of any growth plan, not somewhere behind it.

Build TB modifier auditing into the billing workflow itself. With the modifier now the sole 340B identifier on a claim, platforms need a standing process for confirming correct application before submission, with modifier disputes routed through a dedicated compliance track.

Assess contract pharmacy exposure drug by drug. For each high-margin drug moving through the contract pharmacy channel, a platform should know whether the manufacturer behind it has proposed or already enacted a restriction, and should have a plan ready for the spread on that drug disappearing without warning.

Ruby RCM's infusion-specific infrastructure, covering benefits verification, prior authorization lifecycle management, J-code and modifier-level claim auditing, root-cause denial routing, and AR prioritization by claim value, handles the revenue cycle side of this work. The 340B compliance side, OPAIS registration, patient qualification, and inventory integrity, calls for a complementary compliance system that a platform should evaluate alongside any RCM vendor it chooses.

The platforms best positioned for what's coming won't be the ones with the largest 340B purchase volumes. They're the ones with the clearest view into what that volume actually depends on: correct site registration, accurate modifier application, working capital built for a rebate cycle, and a portfolio mapped by regulatory exposure rather than treated as one undifferentiated revenue stream.