← Back to Blog

Partnerships with Specialty Pharmacy and Health Plans

340B Program
The Marketing Lab
Specialty pharmacy and health plan partnerships are often operationally necessary. This piece walks through structure, patient assignment, data flow, contracting areas, and governance.

Not legal or compliance advice: Specialty pharmacy arrangements and payer contracts can implicate federal and state fraud and abuse laws, state pharmacy licensing rules, manufacturer distribution policies, and 340B program integrity requirements. Before signing an agreement, changing a data flow, or adjusting a patient-assignment practice, consult qualified legal counsel, your 340B compliance officer, an external 340B auditor, HRSA OPA, and Apexus Answers.

Covered entities increasingly find that meeting patient needs requires working alongside external specialty pharmacies and engaging more deeply with health plans. The clinical and operational reasons are well understood: limited-distribution drugs, complex therapies, prior authorization burdens, and payer-specific pharmacy network requirements. The 340B angles are more delicate.

Why specialty drugs matter for covered entity mission and operations

Specialty medications represent a small share of prescriptions but a large and growing share of drug spend for patients served by covered entities.

  • Limited distribution networks. Many manufacturers restrict who can dispense specific products.
  • Clinical complexity. Specialty therapies frequently require patient education, injection training, adherence monitoring, and side-effect management.
  • Payer access rules. Health plans and PBMs often steer specialty fills to specific networks.
  • Financial risk concentration. A single specialty therapy can carry a list price that exceeds an entire clinic day of other medications.

Mission framing: Specialty pharmacy engagement should flow from patient-care needs and statutory 340B intent, not from an opportunistic focus on any particular drug class.

Why external partnerships are often operationally necessary

Standing up a fully in-house specialty pharmacy is a significant undertaking. It typically requires URAC or ACHC accreditation, payer network contracting, staffing with specialty-trained pharmacists and technicians, 24/7 clinical coverage, complex IT, and negotiations with manufacturers and hubs. Many FQHCs, Ryan White clinics, critical access hospitals, and sole community hospitals reasonably conclude that a partnership model serves patients more effectively than attempting to build internal capacity from scratch.

Structuring specialty arrangements within 340B rules

Patient assignment

Eligibility determinations do not change because the drug is specialty. Common specialty failure modes include accepting referrals from non-employed, non-contracted specialists and assuming 340B eligibility; dispensing a 340B-purchased specialty drug for a prescription written during a service encounter that does not fit the entity's scope; and rolling prior authorizations through a specialist who does not have a qualifying relationship with the entity.

Documentation habit: For each specialty therapy, map the patient-eligibility logic explicitly: where is the qualifying encounter, who is the responsible provider, what record proves the prescription flows from that encounter, and what audit trail supports the determination.

Data flow

Specialty workflows frequently involve hubs, copay assistance foundations, manufacturer patient-support programs, and TPAs. A typical review should cover what claims and dispensing data flow from the specialty pharmacy back to the covered entity; how the entity validates 340B eligibility before replenishment; how the arrangement handles Medicaid carve-in/carve-out status including managed Medicaid; and how exceptions are represented in reconciliation.

Accumulators, copay cards, and patient assistance

Specialty therapies are often supported by manufacturer copay assistance or independent foundation grants. Accumulator and maximizer programs, copay variability, and foundation eligibility rules can interact with 340B eligibility documentation.

Manufacturer distribution restrictions

Some manufacturers have adopted policies that affect availability of 340B pricing through contract pharmacies, including for specialty products. Policies have evolved and continue to be litigated.

Moving target: Manufacturer restrictions and related litigation change frequently. A specialty strategy that rests on a particular manufacturer's current posture is fragile.

Payer and health plan partnerships

Narrow networks and preferred pharmacy arrangements

A health plan may designate a specialty pharmacy network or a preferred pharmacy for certain conditions. Covered entities should understand whether their in-house or contract pharmacies are included, what terms govern inclusion, and how any reimbursement or effective discount mechanics work.

Value-based and risk-bearing arrangements

Shared savings, capitation, bundled payments, and quality incentive payments are increasingly common. Covered entities should consider whether metrics inadvertently reward behaviors that conflict with 340B patient definitions; how pharmacy savings from 340B purchasing are described; and whether the arrangement creates incentives to steer patients toward or away from specific pharmacies.

ACO alignment

ACOs and similar models can align incentives across primary care, specialty care, and pharmacy. Coordinate 340B policies with ACO participation agreements, including how shared savings are calculated, who bears downside risk, and how pharmacy data is shared.

Fraud and abuse perimeter: Any arrangement that touches referrals, discounts, data sharing with referral sources, or financial flows can implicate the federal Anti-Kickback Statute, the physician self-referral law, state anti-kickback and fee-splitting laws, and state pharmacy licensure rules. Have counsel analyze the arrangement.

Contracting basics (without giving legal advice)

Scope

  • Which drugs or therapeutic categories are covered.
  • Which patient populations or sites are in scope.
  • Whether the arrangement is exclusive, preferred, or non-exclusive.
  • How new products and new sites are added.

Data sharing

  • What data the covered entity receives, in what format, at what frequency.
  • Reciprocal data the entity provides.
  • Data security, HIPAA BAA, and breach notification.
  • Data retention and return or destruction upon termination.

Fees and financial terms

  • Dispensing fees, administrative fees, and any performance-based components.
  • How fees are tested against fair market value standards discussed with counsel.
  • How 340B-related economics are represented.
  • Reconciliation and dispute-resolution mechanics.

Audit rights

  • The covered entity's right to audit the partner's 340B-related operations.
  • Cooperation with HRSA and manufacturer audits.
  • Access to records, systems, and personnel.
  • Frequency, scope, and cost allocation for audits.

Termination

  • Termination for convenience, for cause, and for change in law.
  • Transition assistance and patient-notification obligations.
  • Handling of in-flight prescriptions and replenishment inventory.
  • Survival of audit, data return, and confidentiality provisions.

Pre-signature checklist:

  • 340B compliance officer has reviewed patient-eligibility and data-flow terms.
  • Legal counsel has reviewed fraud and abuse risk.
  • Finance has modeled the reconciliation workflow and staffing implications.
  • Operations has walked the patient experience end to end.
  • The contract aligns with the entity's 340B P&Ps, or the P&Ps have been updated.

Patient experience handoffs

Specialty workflows fail quietly. Build handoffs deliberately:

  • Name an internal owner for each specialty relationship.
  • Define who the patient calls when something goes wrong.
  • Set service-level expectations and review quarterly.
  • Close the loop with the prescribing clinician.
  • Monitor patient-reported experience, not just dispensing metrics.

Data reconciliation habits

  • Monthly reconciliation of eligibility determinations, dispenses, replenishments, and reversals.
  • Independent validation sampling by the 340B compliance team or an external auditor on a documented cadence.
  • Clear escalation paths for discrepancies, with a log reviewed by compliance leadership.
  • Annual review of the partner's own self-audit results and remediation activity.
  • Alignment of reconciliation data with Medicaid exclusion processes.

Common pitfalls

Recurring failure modes:

  • Misaligned incentives. Contract economics that reward volume in ways that strain patient-eligibility discipline.
  • Loss of oversight. Treating the specialty partner as a black box.
  • Duplicate discount risk. Incomplete Medicaid exclusion logic for managed Medicaid specialty claims.
  • Brand and reputation risk. Partner conduct that the community will associate with the entity itself.
  • Assumptions about manufacturer policy.
  • Payer contract creep. Signing a health plan agreement whose fine print affects 340B practices.
  • Referral-source entanglement.
  • Orphaned patients. Transitions that leave patients without refills or contact points.

Governance and oversight

Specialty and payer partnerships warrant attention at the governance level, not just in operations.

  • A standing agenda item in the 340B oversight committee for partner performance.
  • Board-level awareness of material partnerships and any compliance issues.
  • Annual review of the partnership portfolio against mission and access priorities.
  • Documented decision memos when entering, materially modifying, or exiting a partnership.

References

  • Section 340B of the Public Health Service Act, 42 U.S.C. § 256b.
  • HRSA Office of Pharmacy Affairs (OPA) program notices, contract pharmacy guidance, and patient definition materials.
  • Apexus Answers — operational questions on contract pharmacy, specialty workflows, Medicaid exclusion, and audit preparation.
  • HHS Office of Inspector General (OIG) advisory opinions and special fraud alerts relevant to pharmacy arrangements.
  • Federal Anti-Kickback Statute (42 U.S.C. § 1320a-7b) and physician self-referral law (42 U.S.C. § 1395nn), where applicable.
  • State pharmacy practice acts, fee-splitting and anti-kickback statutes, and state-specific 340B reporting laws.
  • URAC and ACHC specialty pharmacy accreditation standards.
  • CMS guidance on ACO, value-based, and Medicaid managed care arrangements.

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.