One of the most misunderstood aspects of the 340B program is how a patient becomes 340B eligible. Eligibility is often oversimplified or assumed based on insurance status, income level, or where a prescription is filled. In reality, 340B patient eligibility is a highly specific, encounter-driven determination that must be proven through documentation, data integrity, and consistent application of policy.
Eligibility is not permanent, global, or patient-specific in the way many assume. A patient does not become “a 340B patient” forever. Instead, eligibility is determined for each prescription or drug administration, based on whether the covered entity can demonstrate that it met the program’s patient definition requirements at the time of care.
This article explains how a patient becomes 340B eligible, what must be documented, how eligibility is operationalized in real-world systems, and where organizations most often create compliance risk.
Want to validate your patient eligibility framework?
Contact Cooper Strategy
The Foundation of Patient Eligibility in 340B
Eligibility Is Encounter-Based, Not Patient-Based
The most important concept to understand is that 340B eligibility is tied to an encounter, not to a patient’s identity or insurance coverage. A single patient may have:
- One eligible encounter
- One ineligible encounter
- Multiple eligible encounters over time
Each prescription or administration must be evaluated independently.
Insurance Status Does Not Determine Eligibility
Patients do not become 340B eligible because they are uninsured, underinsured, Medicaid, or commercially insured. Insurance status is irrelevant to patient eligibility, except for duplicate discount prevention considerations.
The 340B Eligible Patient Definition Explained
Core Patient Definition Requirements
For a patient to be 340B eligible, 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 patient was not an inpatient at the time the drug was ordered or administered
If any element is missing, the patient is not eligible for that prescription or administration.
Responsibility for Care
Auditors focus heavily on whether the covered entity can demonstrate responsibility for the patient’s care. This is proven through:
- Encounter documentation
- Clinical notes
- Orders and care plans
- Referral documentation
- Provider attribution
Responsibility for care cannot be inferred or assumed.
Step-by-Step: How a Patient Becomes 340B Eligible
Step 1: The Patient Receives a Qualifying Outpatient Service
Eligibility begins when a patient receives a healthcare service from a covered entity in an outpatient setting. This may include:
- Clinic visits
- Infusion appointments
- Emergency department encounters
- Observation services
- Specialty consultations
The service must be documented and tied to the covered entity.
Step 2: The Service Is Provided at an Eligible Location
The encounter must occur at a site that:
- Is registered in HRSA’s 340B database
- Appears on the most recently filed cost report (for hospitals)
- Is properly mapped in internal systems
Care delivered at unregistered sites does not establish eligibility.
Step 3: An Eligible Provider Delivers or Directs Care
The provider involved must be:
- Employed by or contracted with the covered entity
- Acting within the scope of services
- Properly mapped in eligibility systems
Provider misalignment is a frequent cause of eligibility failure.
Step 4: The Service Results in a Drug Order or Administration
Eligibility requires a direct link between the encounter and the medication. This includes:
- Prescriptions written as a result of the visit
- Drugs administered during the visit
- Specialty medications initiated through referral pathways
Drugs unrelated to the encounter do not qualify.
Step 5: The Covered Entity Maintains the Medical Record
The covered entity must maintain access to the medical record related to the care that generated the drug order. This includes:
- Encounter notes
- Orders
- Referral documentation
- Relevant clinical information
If the medical record resides exclusively outside the covered entity, eligibility is compromised.
Step 6: The Patient Is Not an Inpatient
If the patient is an inpatient at the time the drug is ordered or administered, the patient is not eligible for 340B pricing. Correct classification of:
- Admissions
- Observation
- ED visits that convert to inpatient
is critical.
Referral-Based Eligibility
How Referrals Can Establish Eligibility
A patient may become eligible through referral-based care when:
- The covered entity provides the qualifying service
- The referral is documented
- Responsibility for care is clear
- The covered entity maintains relevant medical records
Referral eligibility is one of the most audited areas of 340B.
Common Referral Pitfalls
Eligibility fails when:
- Referrals are undocumented
- External specialists are not mapped
- Encounter documentation is incomplete
- Care coordination is unclear
Strong referral workflows are essential.
Eligibility Over Time
Eligibility Is Not Permanent
A patient may be eligible for one prescription and not for another, even within a short time frame. Eligibility depends on:
- Timing of the encounter
- Relationship to the prescription
- Outpatient status
Assuming ongoing eligibility creates risk.
Lookback and Timing Considerations
Covered entities must define:
- How far back an encounter may establish eligibility
- How long eligibility remains valid
These rules must be documented in policy and applied consistently.
Common Reasons Patients Fail Eligibility Reviews
Missing Encounter Documentation
Without a documented encounter, eligibility cannot be proven.
Incorrect Site Registration
Care delivered at unregistered sites does not qualify.
Provider Mapping Errors
Unmapped or misclassified providers invalidate eligibility.
Inpatient Misclassification
Inpatient status disqualifies eligibility.
Weak Referral Documentation
Referral-based eligibility without documentation fails audits.
Operationalizing Patient Eligibility
Role of Technology
Eligibility determination relies on:
- EHR data
- TPA logic
- Split-billing configuration
- Integration accuracy
Technology must reflect policy.
Role of Policy and Training
Staff must understand how their documentation impacts eligibility.
Role of Internal Audits
Routine sampling verifies eligibility accuracy and detects risk early.
Cooper Strategy helps organizations design defensible patient eligibility frameworks.
Contact us to learn more
Conclusion
A patient becomes 340B eligible only when the covered entity can prove, through documentation and data, that it provided qualifying outpatient care that resulted in the prescription or administration of a drug. Eligibility is encounter-based, time-bound, and highly scrutinized.
Organizations that apply eligibility rules consistently, document care thoroughly, and monitor performance continuously are best positioned to protect compliance and sustain 340B program value.
Frequently Asked Questions About How Does a Patient Become 340B Eligible?
Does a patient stay 340B eligible once they qualify?
No. Eligibility is not permanent. A patient may qualify for one prescription based on a specific encounter and not qualify for another. Each prescription or administration must be evaluated independently using patient definition criteria, outpatient status, and documentation.
Can uninsured patients automatically qualify for 340B?
No. Insurance status does not determine eligibility. An uninsured patient must still meet all patient definition requirements, including having a qualifying outpatient encounter with the covered entity that resulted in the drug order.
Can referrals from external providers make a patient eligible?
Yes, but only if the covered entity provided the qualifying service, documented the referral, maintained responsibility for care, and retained relevant medical records. Referral-based eligibility requires strong documentation and system controls.
Why is inpatient status so important for eligibility?
340B applies only to outpatient drugs. If a patient is an inpatient when a drug is ordered or administered, eligibility fails regardless of documentation quality. Correct classification of inpatient, observation, and outpatient status is critical.
How can Cooper Strategy help ensure patient eligibility compliance?
Cooper Strategy evaluates patient definition logic, audits encounter documentation, strengthens referral workflows, validates provider mapping, and helps organizations build policies and monitoring processes that support defensible eligibility determinations.