Introduction
Understanding what the eligibility requirements are for 340B is foundational to every compliant program. Eligibility is not a single test or a checkbox—it is a multi-layered framework that determines whether a covered entity can participate in the program, whether a patient qualifies for 340B-priced drugs, and whether a specific prescription or administration can be replenished at 340B pricing.
As oversight increases and audits become more detailed, covered entities must be able to demonstrate eligibility with precision. Vague interpretations, inconsistent documentation, or overreliance on vendor logic expose organizations to findings, repayment risk, and program removal.
This article provides a comprehensive, operationally focused explanation of 340B eligibility requirements, with particular emphasis on the 340B eligible patient definition, how eligibility is proven, and where programs most often fail.
Need help validating your eligibility framework? Contact Cooper Strategy
Eligibility Requirement One: Covered Entity Qualification
What Is a Covered Entity
To participate in 340B, an organization must qualify as a covered entity under federal statute. Covered entities fall into defined categories such as:
- Disproportionate Share Hospitals
- Children’s hospitals
- Critical Access Hospitals
- Sole Community Hospitals
- Rural Referral Centers
- Federally Qualified Health Centers
- Look-alike clinics
- Ryan White HIV/AIDS Program grantees
- Other eligible federal grantees
Eligibility is tied to entity type, statutory requirements, and program-specific qualifications.
Maintaining Covered Entity Status
Eligibility is not permanent. Covered entities must:
- Maintain qualifying status year over year
- Recertify eligibility regularly
- Ensure HRSA database accuracy
- Notify HRSA of changes affecting eligibility
Failure to maintain status can result in removal from the program.
Eligibility Requirement Two: Proper Site Registration
Eligible Outpatient Sites
Only registered outpatient sites are eligible to use 340B drugs. Covered entities must ensure that:
- Each site is registered in HRSA’s database
- Each site appears on the most recently filed cost report (for hospitals)
- The site provides outpatient services
- The site remains active and operational
Purchasing or dispensing 340B drugs at unregistered sites is considered diversion.
Child Site Alignment
Child sites must align across:
- HRSA registration
- Cost report listings
- EHR and billing system location codes
- TPA site mapping
Misalignment creates eligibility failures even when care is legitimate.
Eligibility Requirement Three: The 340B Eligible Patient Definition
Understanding the Patient Definition
The 340B eligible patient definition is the most scrutinized eligibility requirement. To qualify, all of the following must be true:
- The covered entity provided a healthcare service to the patient
- The service resulted in the prescription or administration of the drug
- The covered entity maintains the medical record
- The individual is not receiving care as an inpatient
Eligibility must be demonstrated at the encounter level.
Responsibility for Care
Auditors expect covered entities to prove responsibility for care through:
- Documented encounters
- Clinical notes
- Care plans
- Referral documentation
- Provider attribution
Assumptions or general care relationships are insufficient.
Referral-Based Eligibility
Referral-based prescriptions can qualify if:
- The covered entity provided the qualifying service
- The referral is documented
- The covered entity maintains relevant medical records
- The referral represents continuity of care
Referral capture requires especially strong documentation controls.
Eligibility Requirement Four: Provider Eligibility
Rendering and Prescribing Provider Requirements
Providers must be:
- Employed by or contracted with the covered entity
- Acting within the scope of the covered entity’s services
- Properly mapped in systems
Incorrect provider mapping invalidates eligibility.
Provider File Accuracy
Covered entities must maintain:
- Accurate NPIs
- Start and end dates
- Specialty and role designations
- Location affiliations
Outdated provider files are a leading cause of eligibility failure.
Eligibility Requirement Five: Outpatient Status
Outpatient vs. Inpatient Distinction
340B drugs may only be used for outpatient care. Covered entities must correctly classify:
- Observation stays
- ED visits
- Same-day admissions
- Provider-based departments
Misclassification is treated as diversion.
Mixed-Use Environments
In mixed-use settings, eligibility depends on:
- Accurate encounter classification
- Correct site-of-service mapping
- Reliable split billing
Eligibility cannot be assumed based on location alone.
Eligibility Requirement Six: Duplicate Discount Prevention
Medicaid Considerations
Covered entities must ensure that 340B drugs are not subject to duplicate discounts. This requires:
- Accurate Medicaid carve-in or carve-out designation
- Alignment with billing practices
- Proper managed Medicaid handling
Eligibility fails if duplicate discounts occur.
Eligibility Requirement Seven: Purchasing and Replenishment Integrity
Alignment Between Eligibility and Purchasing
Eligibility determinations must align with:
- Accumulation logic
- Replenishment models
- Inventory management
Purchasing 340B drugs without eligible usage is noncompliant.
Documentation of Replenishment
Covered entities must be able to reproduce:
- Eligibility decisions
- Accumulation records
- Purchasing activity
- Reconciliation outcomes
Eligibility must be defensible through data.
Common Eligibility Failures Auditors Identify
Missing or Incomplete Encounter Documentation
Without encounter-level documentation, eligibility cannot be proven.
Incorrect Site Registration
Using 340B drugs at unregistered sites is diversion.
Provider Mapping Errors
Unmapped or misclassified providers invalidate claims.
Weak Referral Documentation
Referral capture without documented responsibility for care fails audits.
System Integration Gaps
Inconsistent data across systems undermines eligibility determinations.
Building a Defensible Eligibility Framework
Standardize Eligibility Policies
Policies should clearly define:
- Patient eligibility criteria
- Referral requirements
- Provider eligibility
- Documentation standards
Monitor Eligibility Continuously
Daily exception reporting and routine audits detect issues early.
Train Staff Regularly
Eligibility is operational. Staff must understand how their actions affect compliance.
Validate Vendor Logic Independently
Covered entities remain responsible for eligibility decisions—even when vendors manage systems.
Want an eligibility readiness assessment? Contact Cooper Strategy
Conclusion
The eligibility requirements for 340B extend far beyond participation status. Covered entities must prove, at the encounter and prescription level, that each use of 340B pricing meets statutory and programmatic standards.
Organizations that build strong eligibility frameworks—supported by accurate data, consistent documentation, and active oversight—are best positioned to protect compliance, maximize savings, and withstand audit scrutiny.
Frequently Asked Questions About What Are the Eligibility Requirements for 340B?
What is the most important eligibility requirement for 340B?
The most critical requirement is the 340B eligible patient definition. Covered entities must prove that they provided the care that resulted in the prescription or drug administration, maintain the medical record, and ensure the patient was outpatient. Most audit findings stem from failures in patient definition documentation.
Can referral prescriptions qualify under 340B eligibility rules?
Yes, but only when the covered entity can document responsibility for care. This requires a qualifying encounter, documented referral, continuity of care, and access to relevant medical records. Referral capture is a high-risk area that demands strong documentation and system controls.
Are provider employment arrangements part of eligibility?
Yes. Providers must be employed by or contracted with the covered entity and acting within its scope of services. Provider mapping errors frequently invalidate eligibility even when care is legitimate.
How do site registrations affect eligibility?
Only registered sites may use 340B drugs. If care occurs at an unregistered site, eligibility fails regardless of documentation quality. Site alignment across HRSA, cost reports, and internal systems is essential.
How can Cooper Strategy help ensure eligibility compliance?
Cooper Strategy evaluates eligibility frameworks, validates patient definition logic, audits referral capture processes, reviews provider mapping, and strengthens documentation standards. We help covered entities build defensible eligibility programs that support compliance and audit readiness.