340B is often discussed as though a retail pharmacy simply “uses 340B.” That framing obscures the actual responsibilities. The federal program enrolls eligible covered entities, not ordinary pharmacies. A community pharmacy may dispense on a covered entity’s behalf under a registered contract-pharmacy arrangement, but the arrangement, dispensing workflow, records, Medicaid handling, and economics all need to be understood before anyone relies on it.
Answer first: an independent pharmacy considering 340B work should begin with the covered entity’s eligibility and registration, the written agreement, the patient and prescription workflow, the treatment of Medicaid claims, auditable records, and a financial model that separates program requirements from the parties’ commercial terms. HRSA administers 340B; it requires covered entities to prevent diversion and duplicate discounts and to maintain auditable records. It does not make a contract pharmacy automatically eligible to buy or retain 340B drugs in its own right.
This is general operational education, not legal, reimbursement, accounting, or 340B compliance advice. Covered entities and pharmacies should obtain counsel and experienced 340B compliance support for their specific structure, state law, payer arrangements, and contracts.
Contents
- What 340B is—and is not
- Roles in a contract-pharmacy arrangement
- Core compliance controls
- What to review in the agreement
- Financial and operational diligence
- Questions and documents to request
- FAQ
Key takeaways
- 340B eligibility belongs to a qualifying, enrolled covered entity; a pharmacy’s role depends on the agreement and registration.
- Contract-pharmacy arrangements must be registered in HRSA’s system, and the covered entity must certify that a fully executed agreement is in place.
- Diversion and duplicate-discount prevention are core federal program requirements; the workflow must produce auditable evidence.
- Contract terms can allocate work and payment, but they do not replace federal, state, payer, privacy, or professional obligations.
- Independent pharmacies should model labor, inventory, reversal, reconciliation, technology, and audit costs before accepting a proposed fee structure.
What 340B is—and is not
Section 340B of the Public Health Service Act requires manufacturers participating in Medicaid to enter pricing agreements under which covered outpatient drugs are sold to eligible covered entities at no more than the statutory ceiling price. HRSA’s Office of Pharmacy Affairs administers the program. The program is therefore not a retail-pharmacy discount card, a general payer benefit, or a universal prescription discount.
The first practical distinction is between the covered entity and the contract pharmacy. Eligible entities include specified safety-net providers and hospital categories defined in statute. They register and recertify through HRSA’s Office of Pharmacy Affairs Information System (OPAIS). A retail pharmacy may contract to provide dispensing services for an enrolled covered entity. HRSA says a covered entity that plans to use a contract pharmacy must register the arrangement online and certify that a fully executed agreement is in effect. A pharmacy should not assume a verbal launch plan, a wholesaler setup, or a third party administrator’s dashboard is proof that the arrangement is active and properly registered.
That distinction also matters for ownership, purchasing, and accountability. HRSA’s contract-pharmacy guidance describes a “ship to/bill to” arrangement in which the covered entity retains title to 340B drugs while the pharmacy houses and dispenses them. Actual operational and title arrangements should be confirmed in the parties’ agreement and validated with counsel; a pharmacy should not infer a universal model from another organization’s workflow.
Roles in a contract-pharmacy arrangement
A sound launch names responsibilities rather than relying on labels. The covered entity ordinarily remains responsible for its program eligibility and for ensuring compliance with 340B requirements. The pharmacy is responsible for the dispensing work it agrees to perform and for its professional, privacy, controlled-substance, recordkeeping, and state-law obligations. A split-billing vendor or administrator may support data matching and replenishment, but software output does not transfer program responsibility or prove that a particular transaction is compliant.
HRSA’s public materials state that covered entities must keep OPAIS records accurate, register contract pharmacies, recertify eligibility annually, prevent diversion to ineligible patients, prevent duplicate discounts, and maintain auditable records. Build the operational map around those statements. Identify who receives the prescription data, who evaluates patient and provider relationships under the entity’s policy, who maintains the Medicaid exclusion information, who approves replenishment, who resolves reversals, and who owns a response to an audit request.
| Control area | Why it matters | Evidence to request | Primary reviewer |
|---|---|---|---|
| Entity eligibility and OPAIS record | Confirms the participating entity and listed location | Current OPAIS record and renewal responsibility | Covered entity compliance lead |
| Contract-pharmacy registration | Confirms the arrangement is registered | Registration confirmation and executed agreement | Legal/compliance |
| Patient eligibility workflow | Supports diversion controls | Written policy, data fields, exception process | Covered entity compliance lead |
| Medicaid claims handling | Addresses duplicate-discount risk | State-specific instructions and OPAIS/MEF process | Billing and compliance |
| Reconciliation and audit trail | Shows how dispensing and replenishment are supported | Reports, retention policy, sample reconciliation | Operations and finance |
Core compliance controls: diversion, duplicate discounts, and records
HRSA describes diversion as transferring or reselling 340B drugs to ineligible patients. Whether a prescription is eligible depends on the program’s requirements and the covered entity’s documented patient-definition process; a contract pharmacy should not make its own informal shortcut. Ask how eligibility is determined, what source data is used, how exceptions are handled, and who has authority to override a match. The point is not to turn front-counter staff into program lawyers. It is to ensure that the workflow sends uncertain claims to the designated reviewer rather than silently treating every fill as eligible.
Duplicate discounts occur when a manufacturer provides a 340B price and a Medicaid rebate is also claimed for the same drug. HRSA states that covered entities report their Medicaid fee-for-service billing method through the Medicaid Exclusion File. HRSA’s FAQ adds that 340B drugs may not be used for Medicaid fee-for-service patients at a contract pharmacy unless there is an arrangement among the pharmacy, covered entity, and state Medicaid agency to prevent duplicate discounts, which the covered entity reports to HRSA and HRSA approves. This is a federal baseline, not a substitute for reviewing the applicable state Medicaid and managed-care rules. Do not assume that a rule for fee-for-service answers a managed-care question.
Records should let a qualified reviewer follow a transaction from prescription through dispense, reversal or return when relevant, claim adjudication, accumulation or replenishment logic, and any exception. Retention periods, access, confidentiality, and the format of data delivery should be specified in the agreement and aligned with applicable law. If a vendor controls the data, the pharmacy and covered entity need to know how records will be produced if the vendor relationship ends.
Review the agreement as an operating document
Contract-pharmacy agreements can look commercially routine, but their clauses determine whether the workflow can withstand a reconciliation, dispute, audit, or termination. HRSA says it will not review contracts and encourages covered entities to have counsel review them. That is a useful warning: an OPAIS registration is not a negotiated risk assessment.
Terms that require legal review
Have counsel examine the scope of services; ownership and custody language; privacy and business-associate provisions where applicable; confidentiality and data-use rights; indemnification; insurance; audit access; record retention; amendment rights; governing law; dispute resolution; limitation of liability; notice; and termination. None of these clauses has a one-size-fits-all answer. A pharmacy should not represent that a provision is enforceable or unenforceable without jurisdiction-specific advice.
Terms that require financial modeling
Model dispensing fees, percentage-of-revenue arrangements, claim fees, technology charges, transaction minimums, reversal handling, replenishment timing, inventory carrying cost, chargebacks, audit recoupments, and termination runout. GAO’s 2018 review of a nongeneralizable sample of 30 contracts found that nearly all included a flat fee per eligible prescription and some included a percentage of revenue; it does not establish a market rate. Use it only as evidence that payment structures vary. Your model should use the actual proposal, expected mix, staffing requirement, and cash timing.
Terms that require operational review
Operations should test the actual handoffs: prescription capture, patient match, replenishment, refill and reversal behavior, partial fills, transfers, returns, inventory segregation or virtual inventory logic, payer edits, exception escalation, dashboard access, and outage procedures. Ask to see training materials and a sample reconciliation before signing. A workflow that works only when one administrator is present is not a reliable pharmacy process.
Avoid two common mistakes in financial analysis
First, do not treat the covered entity’s 340B acquisition economics as the pharmacy’s margin. The pharmacy’s compensation follows its agreement, while its labor, physical capacity, technology, insurance, and compliance costs remain real. Second, do not treat a successful first month as proof that the arrangement is sustainable. Reversals, payer changes, delayed replenishment, audit requests, and contract amendments can alter the economics.
Build a simple scenario model before launch: expected eligible fills by payer and drug class; fee revenue; incremental technician and pharmacist time; inventory and return exposure; administrator fees; reconciliation time; anticipated exception rate; and a conservative contingency for audit or dispute work. Then decide who can change the model’s assumptions and how often results will be reviewed. Document assumptions rather than presenting projections as facts.
Set a governance rhythm before the first claim
Schedule a launch review, a 30-day reconciliation review, and a recurring quarterly meeting with the covered entity. Each meeting should compare the written workflow with actual exceptions: claims that could not be matched, reversals, Medicaid questions, changed prescriber or clinic relationships, missing data, and unresolved vendor tickets. Keep a concise decision log that records what was decided, who approved it, and the effective date. A decision log does not cure an unsupported process, but it prevents a pharmacy from relying on memory when personnel or systems change.
Separate observations from conclusions. A dashboard may show that a claim accumulated, yet a compliance determination may require facts the dashboard does not contain. Likewise, a low exception rate can reflect a well-designed process or simply a process that is not identifying exceptions. Escalate ambiguous situations to the covered entity’s designated compliance contact and qualified advisers. The goal is a defensible process that surfaces uncertainty early, not an informal system that treats silence as approval.
Before you sign: questions and documents to request
- Which covered entity and site will this agreement serve, and can we verify the current OPAIS record?
- Who is responsible for contract-pharmacy registration, recertification, and updates when locations or contacts change?
- What written patient-eligibility and exception process will the pharmacy follow?
- How are Medicaid fee-for-service and managed-care claims handled in this state and arrangement?
- What data does the pharmacy receive, who owns it, and how can records be exported at termination?
- How are reversals, returns, partial fills, transfers, and claim corrections reconciled?
- What fees, offsets, technology charges, audit costs, and termination obligations apply?
- Who answers an audit, who pays for remediation, and how quickly must records be produced?
Request the executed agreement, current registration confirmation, written workflow and training materials, fee schedule, data-flow diagram, sample reconciliation, record-retention policy, privacy documentation, state-specific Medicaid instructions, insurance requirements, audit protocol, and termination/runout plan. If a counterparty cannot explain a required workflow in writing, that is a reason to pause, not a reason to fill the gap with assumptions.
Frequently asked questions
Can an independent pharmacy enroll in 340B on its own?
Only entities that meet the statutory and program eligibility requirements can enroll as covered entities. A retail pharmacy may provide dispensing services under an arrangement with an enrolled covered entity; verify the specific structure and registration.
Must a covered entity use a contract pharmacy?
No. HRSA’s FAQ says covered entities may choose how to provide pharmacy services, subject to federal and state law.
Does a contract pharmacy always receive a percentage of 340B savings?
No. Payment is contractual. GAO found varying arrangements in its reviewed sample, including flat fees and some percentage-based structures. The actual agreement controls.
Who should lead a 340B contract review?
Use a cross-functional review: qualified healthcare counsel for legal terms, the covered entity’s compliance lead for program controls, finance for economics, and pharmacy operations for the dispensing workflow.
Conclusion
A 340B contract-pharmacy arrangement should be evaluated as a compliance-sensitive service relationship, not a generic revenue opportunity. Verify the covered entity and registration, map the patient and Medicaid workflow, insist on auditable records, model the actual economics, and give legal, financial, and operational reviewers defined roles. For related payer-contract considerations, read Dispense Times’ PBM contract review checklist.
References
- Health Resources and Services Administration. 340B Program Requirements. Accessed July 19, 2026.
- Health Resources and Services Administration. Contract Pharmacies. Accessed July 19, 2026.
- Health Resources and Services Administration. 340B Frequently Asked Questions. Accessed July 19, 2026.
- U.S. Government Accountability Office. Drug Discount Program: Federal Oversight of Compliance at 340B Contract Pharmacies Needs Improvement. GAO-18-480. Published June 21, 2018.
- U.S. Government Accountability Office. Drug Discount Program: Agency Oversight Has Improved, but Actions Needed to Address Weaknesses. GAO-26-108784. Published October 23, 2025.
