340B Eligibility Requirements for Infusion Centers

The 340B program is a federal drug pricing mechanism, so eligible healthcare organizations can buy outpatient drugs at prices well below market. Congress requires pharmaceutical manufacturers that participate in Medicaid to sell outpatient drugs to eligible entities at discounted rates, often well below wholesale acquisition cost, and the savings are meant to extend services and get reinvested in patient care. For most medical specialties, that discount is a helpful line item. For infusion centers, a service line's survival can depend on that discount, because the drugs dispensed in infusion settings are routinely among the most expensive therapies in medicine. The spread between the 340B acquisition cost and the amount a payer reimburses is frequently the margin that makes a high-cost infusion program viable. A hospital-based oncology program with 340B eligibility can extend that eligibility to its ambulatory infusion capacity and protect that margin, while a partnership with a platform that lacks 340B status sacrifices it outright, which is why getting eligibility determination right is a strategic question for an infusion operator, not a paperwork exercise.

Which entity types are eligible to participate, and where independent infusion centers stand

Participation in 340B is not open to any healthcare organization that wants in. The Public Health Service Act limits who can join to specific covered entity types, and most independent or partnership-model infusion centers just don't appear on that list by default. HRSA's roster of eligible entity types includes disproportionate share hospitals, children's hospitals and freestanding cancer hospitals, critical access hospitals, sole community hospitals, rural referral centers, Federally Qualified Health Centers and FQHC look-alikes, and a set of community health centers and federal grantees that covers Ryan White HIV/AIDS Program grantees, family planning clinics, tuberculosis clinics, black lung clinics, Native Hawaiian Health Centers, Urban Indian Organizations, STD clinics, and hemophilia treatment centers.

What that list leaves out matters as much as what it includes. A freestanding ambulatory infusion center with no affiliation to one of these entity types, and no status as a federal grantee, has no direct route into the program. Eligibility runs through the covered entity itself, not through the infusion service it happens to provide. If an infusion program is already embedded in a hospital system, the entity-type hurdle is usually cleared before anyone thinks to ask the question. If you're an independent infusion center, you need to ask whether a qualifying affiliation exists or can be built, because operating outside one of these entity categories means operating outside the program. Even if an organization qualifies as a federal grantee, it still has to register through the Office of Pharmacy Affairs Information System, known as 340B OPAIS, on a quarterly schedule with fixed enrollment deadlines. Meeting the criteria does not activate eligibility by itself. It takes a formal registration act.

Hospital-specific thresholds that DSH and children's hospitals must clear

Carrying the label of disproportionate share hospital or children's hospital gets an organization partway there, not all the way. Hospital eligibility first requires a structural test: the facility must be owned or overseen by a local or state government, operate as a private nonprofit under contract with a unit of local or state government, or hold official governmental authority delegated to it as a public or private nonprofit. DSH hospitals, children's hospitals, and freestanding cancer hospitals all have to clear those two tests. DSH hospitals carry one additional number to hit: a disproportionate share adjustment percentage greater than 11.75%.

That percentage doesn't get calculated once and forgotten. Hospitals file a Medicare Cost Report annually, and the formula in that report produces the disproportionate share percentage that determines both entity type and 340B eligibility. You file the Medicare Cost Report year after year, not once at intake. Hospitals that clear the entity-type and threshold tests still face one more constraint: they cannot obtain covered outpatient drugs through a group purchasing organization. That restriction reaches into vendor relationships and purchasing infrastructure, and infusion programs housed inside hospital systems tend to underestimate how much it reshapes the way drugs actually get bought.

Patient-level eligibility: the three conditions that must hold for every dispensed drug

Entity-level eligibility solves only part of the puzzle. Every single drug dispensed under 340B pricing has to be tied to a patient who independently meets a three-part relationship test, and failure at this level is the most common source of audit findings in the entire program. The first condition is that the covered entity maintains health records documenting that individual's care. The second is that the healthcare provider is either employed by the covered entity or delivers care under a contractual arrangement, such as a referral for consultation, where responsibility for the patient's care still sits with the covered entity. The third is that the patient receives healthcare services from the covered entity that go beyond the simple act of dispensing a drug.

That third condition carries a hard exclusion, so infusion centers need to sit with it closely. An individual does not count as a patient of the covered entity if the only service received is a drug dispensed for the patient to self-administer or take home. For infusion settings, where the line between dispensing a drug and administering it can blur operationally, this rule has teeth. A patient who qualifies in January can turn into a compliance problem in March if the documentation supporting ongoing care responsibility lapses. If an infusion program runs recurring treatment schedules, with the same patient receiving dozens of infusions a year from a provider employed by the covered entity and records generated at every visit, it tends to fit this framework well. But that fit only holds as long as the documentation discipline behind it holds too.

Which drugs are covered and which are excluded under the program

Satisfying entity-level and patient-level requirements still doesn't guarantee that a given drug qualifies for 340B pricing. The program only covers "covered outpatient drugs" as defined under federal law, and several drug categories common in infusion settings carry exclusions or special rules. The covered universe is broad: FDA-approved outpatient prescription drugs, brand-name and generic and over-the-counter alike, listed on HRSA's official database, spanning chronic and acute illness medications, specialty drugs, orphan drugs, and treatments for conditions like HIV/AIDS, cancer, and cardiovascular disease.

The word "outpatient" is doing real work in that definition. Drugs administered in inpatient settings do not count as covered outpatient drugs for 340B purposes, so if a hospital-based infusion program operates across both inpatient and outpatient environments, it has to separate its purchasing streams accordingly. Orphan drugs add another layer of complexity. Children's hospitals, freestanding cancer hospitals, and certain other entity types face restrictions on orphan drug eligibility that don't apply to DSH hospitals or FQHCs. That means the exact same drug can be 340B-eligible for one entity type and excluded outright for another, so drug-level eligibility has to be confirmed per drug and per entity type. Applying a blanket purchasing approach across an entire infusion formulary, assuming that what qualifies for one drug qualifies for all of them, is a structural compliance error.

Site registration requirements for offsite infusion locations and child sites

A covered entity can clear every entity-level, patient-level, and drug-level requirement and still not be able to purchase 340B drugs at a particular location. Eligibility doesn't automatically travel with the covered entity's umbrella. Every offsite location has to be registered as a child site in HRSA's database before 340B purchasing can happen there.

That requirement appears most often when organizations expand. A hospital system adding an ambulatory infusion center in a separate building, or an FQHC opening a satellite infusion clinic, has to treat child-site registration as a prerequisite to purchasing, not something handled after the doors open. You register through 340B OPAIS, and that system runs on a quarterly enrollment schedule. A site that misses a registration window doesn't get a workaround. It waits for the next quarterly cycle before it can buy a single 340B-priced drug. The consequence of missing this step isn't a compliance footnote, it's a physical block on the supply chain. Infusion drugs don't arrive at a discount until the site itself is registered, no matter how eligible the parent organization is.

Annual recertification and the ongoing compliance obligations that sustain eligibility

340B eligibility is not a status an organization earns once and keeps forever. It has to be actively renewed and backed by compliance infrastructure on a continuous basis, and a lapse in either one can retroactively invalidate purchases that already happened. HRSA requires every registered covered entity to recertify its eligibility annually and to keep its database information current. If that database holds outdated information, it can block purchases just like an unregistered child site, until someone fixes it.

Sustaining compliance takes a real operating program: policies and procedures tailored to the organization's specific entity type, regular internal audits that catch problems before HRSA or a manufacturer audit finds them first, correct identification and flagging of 340B-eligible prescriptions at the point of dispensing, and recordkeeping thorough enough to produce on demand. HRSA's attention concentrates on two failure modes above all others: diversion, providing 340B drugs to patients who don't meet the patient-eligibility test, and duplicate discounts, where a single drug receives both a 340B discount and a Medicaid rebate. Both are failures of ongoing process rather than mistakes made at initial enrollment, and both trace directly back to the same documentation discipline that protects patient-level eligibility. If an infusion center runs high volumes of recurring biologic treatments, a single documentation gap can spread across hundreds of patient encounters and stop being small. It can produce a repayment demand of real financial weight.

How the contract pharmacy dispute affects infusion centers that rely on dispensing partners

An infusion center can meet every entity, patient, drug, and site requirement in the program and still run into a wall that has nothing to do with eligibility. Even when your eligibility is airtight, manufacturer policies on how drugs move through contract pharmacies can still limit your access to 340B pricing. A substantial number of manufacturers have put policies in place that refuse or restrict 340B pricing for drugs dispensed through contract pharmacies, and they often limit a covered entity to a single contract pharmacy or make access to multiple contract pharmacies conditional on submitting claims data.

Federal appellate courts have largely sided with manufacturers on this point so far. The Third Circuit and the D.C. Circuit have both upheld manufacturer restrictions, reasoning that Section 340B doesn't prohibit manufacturers from attaching conditions to distribution, as long as those conditions don't push the contract price above the ceiling price or cut off a covered entity's access to 340B pricing. State legislatures have pushed back with laws reopening contract pharmacy access, but that fight is far from settled. The Eighth Circuit upheld an Arkansas law barring manufacturer restrictions for contract pharmacy users, but a federal judge blocked a similar law in West Virginia with a preliminary injunction, because it likely conflicted with federal statute, and cited audit rights as one ground among several. A newer complication is arriving on top of this litigation: HRSA's 340B Rebate Model Pilot Program requires eligible manufacturers to submit plans by August 24, 2026, for an effective date of January 1, 2027. Under that model, covered entities pay full wholesale acquisition cost upfront, and they receive a rebate, equal to WAC minus the 340B ceiling price, within 10 calendar days of submitting claims data to the manufacturer. If an infusion program carries large drug inventories, that structure introduces real cash-flow timing exposure even when every other eligibility requirement checks out. None of this is a reason 340B eligibility is unavailable to a qualifying infusion center. It's a structural risk to how much of the eligible savings that center can actually capture.

What infusion center operators should do first when evaluating 340B participation

Eligibility under 340B is layered, and any single layer can disqualify a program on its own, so the order in which an infusion center investigates these questions matters. Starting anywhere other than the entity-type question wastes time and risks building false confidence on an unstable foundation. The organization itself must fall within one of the covered entity categories defined under the Public Health Service Act, or it must have a qualifying affiliation with an entity that does. If the organization is a hospital type, the next step is confirming the structural ownership criteria and checking whether the disproportionate share adjustment threshold is met, using the Medicare Cost Report as the primary document for that determination. From there, the infusion center needs to check whether the specific drugs it wants to buy under 340B count as covered outpatient drugs for its entity type, because you have to confirm orphan drug exclusions and the inpatient-outpatient boundary drug by drug, not assume them across the whole formulary. After that comes site registration: every location where 340B drugs will be purchased or administered needs to be registered as a child site in HRSA's 340B OPAIS database, with address-level matching verified against the wholesaler database. The infusion center also has to evaluate whether its care model, including how providers are employed or contracted, how health records are kept, and how much care it delivers beyond drug dispensing, actually supports patient-eligibility documentation at the volume it intends to operate. Finally, you need to assess the contract pharmacy landscape for your specific formulary: which manufacturers currently restrict contract pharmacy distribution, and whether the center's dispensing arrangements fall inside those restrictions.

None of this works as a one-time checklist completed before launch and then set aside. Annual recertification and the compliance infrastructure behind it need to be designed into the operating model from the start, because documentation and audit-readiness requirements are active from the very first 340B purchase, not phased in later. For infusion centers that do qualify, the consequences extend well past the pharmacy counter: drug acquisition cost, claim submission modifier requirements, and audit exposure all flow directly into billing operations. The revenue cycle infrastructure supporting a 340B infusion program has to be built around that complexity from the ground up. So many of these thresholds carry real legal weight, from DSH percentages to contract pharmacy litigation still being decided in federal court, so if you're an infusion center operator evaluating participation, you benefit from dedicated 340B compliance counsel well before you purchase the first drug under the program.