Covered entities that participate in the 340B Drug Pricing Program must follow a detailed set of rules set by the Health Resources and Services Administration (HRSA). 340B compliance refers to the ongoing effort to meet those program requirements. It involves verifying patient eligibility, managing contract pharmacies, submitting accurate claims data to manufacturers, and preparing for HRSA audits. Without a strong compliance program, covered entities risk significant financial penalties and loss of program eligibility.
The 340B program was created in 1992 under the Veterans Health Care Act. It was designed to help safety-net providers stretch scarce federal resources further, allowing them to reach more eligible patients and offer more comprehensive services. Over the years, the program has expanded significantly, and oversight has become more rigorous. Today, compliance is not optional. It is a condition of participation.
Understanding the 340B Drug Pricing Program
To understand 340B compliance, it helps to know how the program works. Section 340B of the Public Health Service Act requires pharmaceutical manufacturers to enter into a pharmaceutical pricing agreement (PPA) with the Secretary of Health and Human Services. In exchange, their drugs are covered by Medicaid and Medicare Part B. Under the PPA, manufacturers must provide front-end discounts on covered outpatient drugs purchased by covered entities. These discounts are significant. The 340B ceiling price is calculated as the average manufacturer price (AMP) reduced by the unit rebate amount (URA). The URA is a minimum rebate percentage of 23.1% for most brand-name drugs, 17.1% for brand-name pediatric drugs and clotting factor, and 13% for generic and over-the-counter drugs.
The Office of Pharmacy Affairs (OPA) within HRSA administers the program. Covered entities may register during the first two weeks of any calendar quarter: January 1 through 15, April 1 through 15, July 1 through 15, and October 1 through 15. Once registered, entities must adhere to a wide range of operational and reporting requirements.
The program is not without controversy. Critics, including the Pharmaceutical Research and Manufacturers of America (PhRMA), argue that the program may not always improve patient access or that it can be abused. The Commonwealth Fund, a nonpartisan research organization, has also noted these concerns in its explainer content. For covered entities, this scrutiny makes compliance even more critical.
Who Must Follow 340B Compliance Rules?
Two broad categories of covered entities participate in the 340B program: hospital entities and non-hospital entities. Each type has its own eligibility criteria, but both must follow the same core compliance rules.
Hospital Covered Entities
Hospital covered entities include disproportionate share hospitals (DSHs), children’s hospitals, cancer hospitals exempt from Medicare prospective payment, sole community hospitals, rural referral centers, and critical access hospitals. These hospitals must meet specific ownership and payer-mix criteria to qualify and remain enrolled.
Non-Hospital Covered Entities
Non-hospital covered entities include ten categories, such as Federally Qualified Health Centers (FQHCs), Ryan White HIV/AIDS Program clinics, and AIDS drug assistance programs. These organizations generally qualify based on receiving federal funding. FQHCs, in particular, make up a large portion of the non-hospital covered entity landscape and face unique compliance challenges related to patient definition and contract pharmacy oversight.
Key Areas of 340B Compliance
Compliance touches nearly every part of a covered entity’s 340B program operations. Below are the most important areas that organizations must manage carefully.
Patient Eligibility and Covered Entity Requirements
The most fundamental compliance requirement is ensuring that 340B drugs are used only for eligible patients of the covered entity. HRSA defines an eligible patient as one who receives health care services from the covered entity and who has a relationship with the entity such that the entity maintains records of the care provided. Failure to properly verify patient eligibility is one of the most common findings in HRSA audits.
Manufacturer Agreements and Pricing
Manufacturers are required to provide front-end discounts to covered entities, and the ceiling price is set at AMP minus the URA. Covered entities must ensure they are paying no more than the ceiling price for covered outpatient drugs. However, compliance also means not seeking duplicate discounts. The 340B program and the Medicaid Drug Rebate Program (MDRP) both aim to lower drug costs, but they operate differently. MDRP gives rebates to state Medicaid agencies after drugs are dispensed, while 340B requires front-end discounts directly to covered entities. Entities must have systems in place to prevent a drug from receiving both a 340B discount and a Medicaid rebate.
Registration and Reporting
Covered entities must register with HRSA through the OPA information system (OPAIS) during the designated quarterly windows. Registration includes designating contract pharmacies and providing other operational data. Failure to keep registration information current can lead to compliance findings. Additionally, many manufacturers now require covered entities to submit claims data through platforms like the 340B ESP or TRUZO as part of manufacturer compliance submissions. These submissions help manufacturers verify that discounts are not being claimed inappropriately.
Common Compliance Challenges
Even well-run 340B programs face compliance obstacles. One major challenge is contract pharmacy oversight. Hospitals participating in 340B contract with over 33,000 distinct pharmacies to dispense prescriptions. Managing that many relationships, each with its own data feeds and reconciliation processes, creates significant risk. Duplicate discounts can occur when a 340B drug is also billed to Medicaid. Incorrect patient identification can lead to diversion, a serious violation where 340B drugs are used for non-eligible individuals.
Another challenge is keeping up with evolving manufacturer requirements. More pharmaceutical companies are requesting data submissions through 340B ESP or TRUZO, and each manufacturer may have different rules. Covered entities must track these requirements and submit accurate, timely data. Finally, HRSA audits are becoming more frequent and more detailed. Entities that are not audit-ready may face repayment demands or even termination from the program.
How 340B Compliance Consulting Supports Covered Entities
Given the complexity of 340B program rules, many covered entities turn to specialized consultants for help. These consultants provide services that directly support compliance. Conducting internal compliance audits helps identify gaps before HRSA does. Analytics dashboards give organizations visibility into claims data, financial performance, and capture rates, making it easier to spot anomalies. Support with in-house pharmacy feasibility, setup, and ongoing management ensures that operations follow program rules from day one.
For contract pharmacy arrangements, consultants can manage third-party administrator (TPA) oversight, claims audits, and reconciliation. They also help covered entities navigate manufacturer compliance submissions such as 340B ESP and TRUZO. By building a strong compliance framework, covered entities can participate in the program with confidence and focus on their primary mission: serving patients.
Frequently Asked Questions
What is the difference between 340B and the Medicaid Drug Rebate Program?
The 340B program provides front-end discounts to covered entities at the time of drug purchase, while the Medicaid Drug Rebate Program (MDRP) provides rebates to state Medicaid agencies after the drug is dispensed. Both programs aim to lower drug costs, but covered entities must have systems to prevent duplicate discounts on the same prescription.
What happens during a 340B audit?
HRSA audits review a covered entity’s compliance with patient eligibility rules, contract pharmacy oversight, recordkeeping, and other program requirements. Auditors examine patient records, purchase data, and dispensing logs. If violations are found, the entity may be required to repay discounts or face program termination. Preparation and documentation are essential.
Can a covered entity lose its 340B eligibility?
Yes. If HRSA finds serious or repeated noncompliance, a covered entity can be terminated from the 340B program. Termination means losing access to discounted drugs, which can have a major financial impact on the organization and the patients it serves. Maintaining an ongoing compliance program is the best way to avoid this outcome.
How does contract pharmacy affect 340B compliance?
When a covered entity uses contract pharmacies, it must ensure those pharmacies properly identify 340B eligible patients and do not dispense duplicate discounts. Oversight of contract pharmacies is a significant compliance burden because hospitals alone contract with over 33,000 distinct pharmacies. Robust data sharing and regular audits help manage this risk.
What is a 340B ceiling price?
The ceiling price is the maximum price a manufacturer can charge a covered entity for a covered outpatient drug. It is calculated as the average manufacturer price (AMP) reduced by the unit rebate amount (URA). For most brand-name drugs, the URA is 23.1% of AMP. This formula ensures that covered entities receive a meaningful discount.