Navigating the Challenges of 340B Pharmacies

HRSA audits, manufacturer contract pharmacy limits and PBM reimbursement pressure are different problems. Here is what covered entities build for each one.

The 340B Drug Pricing Program creates real opportunity for covered entities - discounted medications, extended reach into underserved communities, and revenue that funds broader services. But that opportunity comes with a compliance burden that too many organizations are not fully prepared for. Regulatory scrutiny is increasing, operational requirements are intensifying, and the organizations that are not building serious internal systems are falling behind.

Key Takeaways

HRSA audits are resource-intensive and unforgiving. Organizations without clear documentation trails, patient eligibility records, and diversion prevention systems are exposed.
The core eligibility and patient definition standards are HRSA sub-regulatory guidance and have been relatively stable. What shifts regularly is manufacturer policy, litigation, state law, and audit interpretation - that is where attention belongs.
EHR integration with 340B requirements is one of the most common operational failures. Systems that do not communicate create inventory tracking problems and audit risk.
Contract pharmacy networks require active management, not just initial setup. Compliance, reporting, and relationship management are ongoing responsibilities.
Two separate financial pressures get conflated: PBM discriminatory reimbursement and 340B-specific fees, and manufacturer restrictions on contract pharmacy pricing. They have different sources and different remedies.

What the 340B program was built to do

Established in 1992 under the Public Health Service Act, the 340B program enables eligible healthcare organizations to purchase prescription medications from manufacturers at discounted rates. Covered entities - federally qualified health centers, disproportionate share hospitals, and other safety-net providers - use those savings to stretch limited resources and improve medication access for patients who cannot easily afford care otherwise.

The program works when covered entities run it with rigor. It creates serious problems when they treat compliance as an afterthought.

The three categories of challenge

Regulatory compliance

HRSA audits. Covered entities must maintain compliance across eligibility verification, patient identification, and diversion prevention. HRSA audits verify all of it, and the process is resource-intensive even for well-prepared organizations. Teams that have not built systems for documentation, audit trails, and evidence management find themselves scrambling when an audit arrives. Build your internal controls against the published HRSA audit protocols and the Apexus 340B University materials rather than against internal assumptions, and involve 340B counsel before an audit, not after the findings letter.

A shifting environment - but not in the way most people assume. It is worth being precise here, because the imprecision causes real problems. Much of what governs 340B eligibility and the patient definition is HRSA sub-regulatory guidance, not binding regulation. The 1996 patient definition guidance remains the operative standard; the 2015 proposed omnibus guidance that would have replaced it was withdrawn in 2017 and never took effect. So the core eligibility framework has actually been fairly stable.

What does change frequently is everything around it: manufacturer policy on contract pharmacies and data submission, the outcomes of ongoing litigation, state legislation on contract pharmacy protection and PBM conduct, and how auditors interpret existing guidance in practice. Those are the things worth tracking actively - and the reason a program built on one manufacturer's current policy is a program that will need rebuilding.

Operational requirements

Inventory management. Tracking 340B-eligible prescriptions separately from non-340B prescriptions is not a small task. Fluctuating patient demand, multiple dispensing locations, and varying payer rules all complicate oversight. Without precise tracking, organizations risk both compliance failures and financial waste.

EHR integration. Incorporating 340B requirements into existing electronic health record systems is one of the more persistent operational challenges covered entities face. Many pharmacy management platforms were not built with 340B compliance in mind, which means additional software layers or custom integration work. The organizations that handle this well use solutions that work alongside their existing EHR rather than requiring a full replacement.

Financial stability

Reimbursement variability. Reimbursement rates from payers and pharmacy benefit managers vary significantly. Two distinct pressures often get conflated here, and they have different sources and different remedies.

The first is PBM conduct. Some PBMs reimburse claims identified as 340B at lower rates than the same claim from a non-340B pharmacy, impose 340B-specific fees or differential DIR, or write 340B-specific terms into network contracts. This is a contracting and state-law problem. The remedies are contract review before signing, claim-level auditing to detect differential reimbursement after the fact, and the 340B non-discrimination statutes a growing number of states have enacted - check whether your state has one and what it actually covers.

The second is manufacturer contract pharmacy restrictions. Beginning in 2020, a number of drug manufacturers - not PBMs - unilaterally began limiting 340B pricing on drugs dispensed through contract pharmacies, typically by restricting entities to a single contract pharmacy, conditioning access on 340B ESP claims data submission, or excluding certain products. That is a manufacturer policy question, it is the subject of ongoing litigation between manufacturers, HRSA, and covered entities, and the remedies are entirely different: tracking each manufacturer's current policy, deciding on data submission, evaluating whether an in-house or wholly-owned pharmacy changes your exposure, and following state contract pharmacy protection laws.

Managing both - and ensuring that 340B-purchased drugs generate appropriate reimbursement - requires strong claims processing and ongoing payer relations.

Contract pharmacy network management. For covered entities using contract pharmacy arrangements, building a solid network is only the first step. Managing those relationships while maintaining compliance around inventory, data reporting, and audit readiness is an ongoing operational responsibility. A contract pharmacy arrangement that is not actively managed becomes a compliance liability.

Two pressures that did not exist when most 340B programs were designed

Most covered entities built their 340B operations around two assumptions: that contract pharmacy access would remain broadly available, and that the discount would arrive embedded in the purchase price. Both assumptions are now contested, and a program that has not reexamined them is planning against a world that has moved.

Manufacturer contract pharmacy restrictions. Starting in 2020, a growing number of drug manufacturers unilaterally imposed conditions on 340B pricing for drugs dispensed through contract pharmacies. The specific terms differ by manufacturer and have been revised repeatedly, but the recurring patterns are limiting an entity to a single designated contract pharmacy, conditioning continued access on submission of claim-level data through a third-party platform, and carving out particular products or classes. Grantee types have sometimes been treated differently from hospitals. The legality of these restrictions has been litigated extensively between manufacturers, HHS, and covered entities, with mixed results across circuits, and the question is not settled. Several states have responded with contract pharmacy protection laws of their own, which adds a state-by-state layer to what was previously a federal-only analysis. Practically: maintain a current inventory of which manufacturers restrict you, on which products, and under which conditions, and revisit it on a schedule rather than when a price change appears on an invoice.

The rebate model. The second pressure is a proposed change to when the discount arrives. Under a rebate model, an entity would purchase at something closer to list price, submit claim-level data, and receive the discount back afterward rather than at the point of purchase. For organizations operating on thin margins, that is a working capital question before it is a compliance question - and it introduces a failure mode the upfront model does not have, where a data problem means the money never arrives rather than merely creating audit exposure. Status here is genuinely unsettled and has been moving. We cover the mechanics, the policy posture, and what to prepare for in The 340B Rebate Model: What Covered Entities Need to Know.

Both of these raise the value of the same underlying capability: clean, complete, claim-level data that ties each dispense to an eligible patient, an eligible prescriber, and an eligible location. That was always good practice. It is now the thing that determines whether you get paid.

What strong 340B management looks like

The organizations that run 340B programs successfully tend to share a few characteristics. They have dedicated compliance infrastructure - not just a part-time staff member who also handles other duties. They have invested in data management that connects patient eligibility, dispensing records, and audit documentation in one place rather than across disconnected spreadsheets and systems. And they treat compliance as a continuous operating discipline rather than something to address when HRSA sends a letter. Entities without the internal bandwidth to build all of that in-house often bring in a partner, which is what our 340B program management service is for.

Jacob Sacks, Founder & CEO of Remy: "In today's regulatory environment, 340B consultants can't afford to be results-driven. You need to be results determined."

That distinction matters. Results-driven means optimizing for the outcome you want. Results-determined means building the systems that make that outcome repeatable - even when regulations shift, payers push back, or audits arrive.

How infusion and telemedicine extend what 340B makes possible

For covered entities that have built solid 340B operations, the natural next step is putting those discounted drug acquisitions to work through clinical service expansion. Infusion sites allow covered entities to administer biologics for conditions like rheumatoid arthritis, Crohn's disease, and multiple sclerosis using 340B-purchased medications, and the combination of discounted acquisition and infusion reimbursement creates a meaningful revenue and care access opportunity.

The word "partnership" does a lot of quiet work in that sentence, so be specific about what it requires. Any offsite infusion location must be registered as a child site on the entity's record in HRSA's Office of Pharmacy Affairs database before 340B drugs are purchased for it, must operate within the entity's scope of project, and may furnish 340B-purchased drugs only to individuals who meet the 340B patient definition. An informal arrangement with a neighboring practice or a management company is not a substitute for registration - it is a diversion finding waiting for an auditor.

Telemedicine expands geographic reach without the overhead of additional physical locations, extending patient engagement beyond the clinic walls and improving continuity of care.

Neither of those opportunities is accessible to organizations that are struggling with the compliance fundamentals. Getting the 340B foundation right is what makes the expansion possible.

Starting with a clear-eyed assessment

Every organization's 340B program has different strengths and different vulnerabilities. The right starting point is an honest look at where the gaps are - in compliance documentation, in EHR integration, in contract pharmacy management, in reimbursement capture - before trying to optimize what is already working.

If your organization is facing pressure from HRSA, navigating a contract pharmacy dispute, or simply trying to build a more durable compliance infrastructure, contact Remy for a free assessment of where your program stands and what a stronger system looks like.