Not legal or compliance advice: This article is educational only. It is not legal, regulatory, compliance, or contract-drafting advice. Contract pharmacy arrangements sit at the intersection of evolving HRSA guidance, manufacturer policies, state Medicaid rules, and private contract law. Consult your legal counsel, your 340B compliance officer, your external auditor, HRSA Office of Pharmacy Affairs (OPA), and Apexus before entering, renewing, or modifying contract pharmacy relationships.
Contract pharmacy is one of the most scrutinized, most operationally complex, and most strategically important areas of 340B. For many covered entities, contract pharmacy relationships are how the program actually reaches patients — particularly rural patients, patients without in-house pharmacy access, and patients needing specialty medications. But those same relationships are also the area of the program where the most regulatory activity, manufacturer pushback, and audit findings have concentrated.
A strong contract pharmacy strategy is therefore less about contracting aggressively and more about contracting carefully: fewer, better-managed relationships with clearer terms, better data, and tighter oversight tend to outperform many loose relationships.
The modern contract pharmacy environment traces to HRSA's 1996 guidance allowing covered entities to contract with a single outside pharmacy, and the 2010 guidance that expanded the ability of covered entities to contract with multiple outside pharmacies. Those notices established the operational framework most entities still use — replenishment-model dispensing, a written contract, oversight by the covered entity, and duplicate-discount controls with state Medicaid programs.
Since then, the landscape has changed substantially. Beginning in 2020, multiple drug manufacturers announced restrictions on 340B pricing for drugs dispensed through contract pharmacies, with varying conditions. Litigation, HRSA enforcement activity, and state-level "anti-discrimination" laws have followed. Proposals around rebate-based models have surfaced. This area is in active motion.
Verify current guidance: Any operational decision that depends on a particular manufacturer's position, a particular state statute, or a particular HRSA interpretation must be checked against current sources at the time you decide.
The durable principles — a written contract, oversight, documentation, duplicate-discount prevention, patient definition discipline — remain stable even as the surface rules shift. Build your strategy around the durable principles.
Many covered entities grew their contract pharmacy networks organically. A strategy inverts that. It starts with the patients you are chartered to serve, asks where they actually fill prescriptions and where they need access, and then seeks partners who can serve those patients well. Relationships that do not serve identifiable patient access needs are candidates for consolidation or termination.
Before entering or renewing a contract pharmacy relationship, evaluate the prospective partner across the following dimensions. A weighted scorecard, reviewed by the 340B compliance committee, is a useful format.
Poor data feeds are the single most common upstream cause of 340B compliance findings in contract pharmacy arrangements. A pharmacy that cannot or will not send clean, timely data is not a fit regardless of footprint.
Review whether the pharmacy is already integrated with your TPA and the realistic timeline if not. Confirm it has no material HRSA or OIG findings, that it maintains a documented compliance program, and that it will cooperate with HRSA, manufacturer-initiated, and internal self-audits. Review standard reports and ad-hoc reporting support.
There are two dominant inventory models in contract pharmacy, and the choice has compliance and operational implications.
Replenishment (virtual inventory) model. The pharmacy dispenses from its own commercial inventory. After the fact, the TPA identifies 340B-eligible dispenses, accumulates those units by NDC, and when the accumulation crosses the package size threshold, the covered entity orders a replacement package at 340B pricing. This is the most common model in retail settings.
Ship-to (physical inventory) model. The covered entity maintains a physically segregated 340B inventory at the contract pharmacy. This is more common in specialty and infusion settings.
Each model has its own handling risks. Neither is inherently superior; the right choice depends on drug type, pharmacy operations, and the covered entity's oversight capacity.
Whatever the structure, it should be transparent, reconcilable against dispensing data, and reviewed with legal counsel for fraud-and-abuse and anti-kickback considerations appropriate to your entity type.
Counsel must draft and review: The elements below are educational checklist items, not contract language. Every contract pharmacy agreement must be drafted, reviewed, and negotiated with qualified legal counsel familiar with 340B, your state law, and your entity type.
Durable elements that a well-constructed contract pharmacy agreement typically addresses include: scope; inventory model; administrative fees; data exchange; patient definition and eligibility responsibilities; Medicaid and duplicate-discount prevention; oversight and audit rights; compliance representations; records retention; training; termination; indemnification and insurance; assignment and change of control; and regulatory-change adjustment mechanisms.
Stale contracts are a risk in themselves: Contracts signed in an earlier regulatory era may reference practices or assumptions that no longer hold. An annual legal-and-compliance review of every active contract pharmacy agreement is a reasonable baseline.
Oversight is not a once-a-year event. A layered cadence keeps the relationship healthy and audit-ready.
Preventing duplicate discounts is a core statutory obligation. In the contract pharmacy context, duplicate-discount risk is elevated because the pharmacy is not inside the covered entity's four walls. Durable controls include a clear site-level Medicaid carve-in or carve-out decision; alignment with each state's specific rules and managed Medicaid treatment; TPA logic that enforces the carve decision; regular reconciliation of dispenses flagged as Medicaid; and prompt attention to manufacturer or state dispute notices.
Stale contracts. Agreements signed years ago may pre-date key regulatory developments.
Insufficient oversight. Signing an agreement and checking a monthly dashboard is not oversight.
Inadequate data reconciliation. Small data-feed anomalies compound.
Too many relationships. Each contract pharmacy carries an oversight cost. "Fewer, better-managed" is often the right posture.
Blurred responsibility. Unclear division of labor between the covered entity, the TPA, and the pharmacy produces gaps.
Ignoring manufacturer policies. Track current manufacturer positions through your TPA, Apexus, and legal counsel.
Specialty-pharmacy blind spots. Treat specialty relationships with the same rigor as retail, or more.
Contract pharmacy is where 340B meets the street — where patients actually pick up medication, where data actually moves between systems, where manufacturers actually push back, and where auditors actually look. A smaller, cleaner, better-governed contract pharmacy network, built around genuine patient access, is easier to defend and better serves the mission than a sprawling one built around opportunity.
This article is educational and does not constitute legal, tax, regulatory, compliance, or financial advice. Program rules change; verify current guidance with HRSA's Office of Pharmacy Affairs, Apexus, and qualified counsel before acting.