340B and patient affordability: what the savings are actually for

One of the most persistent misunderstandings about 340B, inside health systems as much as outside them, is the assumption that the program automatically lowers what a patient pays. It does not. The statute governs what the covered entity pays the manufacturer. What the patient pays is determined by their benefit design, their plan's cost-sharing rules, and whatever the entity chooses to do with the margin.

That gap between program savings and patient cost is not a loophole. The statute was written that way on purpose. But if patient affordability is actually a goal, somebody inside the organization has to build that connection deliberately. It will not happen by itself.

Where the money actually sits

A covered entity acquires an eligible drug at the 340B price and is reimbursed by the payer at whatever the contract says. The difference is program savings. Those savings are institutional funds. They are typically used for the range of things the program was intended to support: sustaining services that do not cover their own cost, funding clinical pharmacy positions, supporting charity care and financial assistance, and keeping access open in settings that would otherwise close.

Every one of those is a legitimate use. None of them is the same as reducing a specific patient's copay for a specific drug.

The mechanisms that do reach the patient

Where entities choose to direct program savings toward affordability, these are the usual routes:

• A discounted or sliding-scale price for uninsured and self-pay patients. The most direct mechanism. It requires a written policy defining eligibility and the discount schedule, and it needs to be applied consistently.
• Funding financial assistance and charity care. Program savings underwrite a patient assistance fund the entity administers under its own criteria.
• Funding the staff who do access work. Less visible but often the highest impact: the navigators, technicians, and financial counselors who get patients enrolled in manufacturer assistance, foundation support, and copay programs. This is affordability delivered through labor rather than through price.
• Keeping a service open. An infusion center that stays open because the program supports it delivers affordability in the form of travel time, lost work, and access that would otherwise not exist locally.

Why the connection has to be documented

Program integrity is not only about eligibility and duplicate discounts. Entities are increasingly asked, by boards, by state legislatures, and in the public conversation about the program, to describe what the savings do. An entity that cannot answer that question specifically is in a weak position, regardless of how compliant its program is.

What a defensible answer looks like:

1. A written policy stating how program savings are used, approved at the right level of the organization.
2. A defined patient eligibility standard for any discount or assistance program funded by savings, applied uniformly.
3. Documentation that ties specific spending back to the program: positions funded, assistance dollars disbursed, services sustained.
4. Reporting on a regular cadence to whoever governs the program, typically a committee that includes pharmacy, finance, and compliance.
5. Consistency between what the policy says and what actually happens, which is the part that fails most often.

The compliance boundaries to respect

Affordability programs built on 340B savings still have to respect program rules. The ones that cause trouble most often:

• Patient definition. The discount can only follow a drug dispensed to an individual who meets the patient definition at an eligible site. Extending a 340B-funded discount to someone outside that boundary is a program problem, not just a policy problem.
• Duplicate discounts. Medicaid exclusion file management and carve-in or carve-out decisions have to be current, and the affordability program has to sit on top of that, not around it.
• Contract pharmacy. If the affordability mechanism runs through contract pharmacy, the qualification logic, the fee structure, and the patient-facing discount all need to be documented and reconcilable.
• Consistency with financial assistance policy. A 340B-funded discount program that contradicts the organization's own financial assistance policy is an audit finding waiting to happen, in either direction.

A practical starting point

If your entity cannot currently describe, in one page, how program savings connect to patient affordability, write that page before you do anything else. It does not require new spending. It requires deciding what the savings are for, writing it down, assigning ownership, and reporting against it.

The organizations that handle this well are not necessarily spending more of their savings on patients. They are the ones that can explain, precisely and on request, what they are doing and why. That is an increasingly valuable position to be in.

Robert Walters, PharmD, MBA is the founder of Walters Rx Strategy and is Apexus Advanced 340B Certified. He spent fifteen years leading health-system pharmacy operations across acute care, a cancer center, infusion, and emergency department pharmacy. Book a consult or read more insights.

This article is general and informational. It is not legal, regulatory, clinical, or medical advice, and it does not recommend or promote any specific product or therapy.