Patient Definition and Eligibility: Scoping Program Boundaries

Not legal or compliance advice: The patient definition is one of the most consequential and legally sensitive areas of the 340B program. Before implementing, changing, or defending any eligibility logic, consult your organization's legal counsel, 340B compliance officer, external auditor, HRSA Office of Pharmacy Affairs (OPA), and Apexus. Verify all interpretations against the most current guidance.

Why patient definition sits at the center: Section 340B of the Public Health Service Act restricts drug resale and limits 340B-priced drugs to patients of the covered entity. That word carries the program's conceptual weight. How your organization operationalizes it defines the program's boundaries — and, by extension, the responsible scope for business development.

Statutory and guidance foundations

Section 340B of the PHS Act allows covered entities to purchase certain outpatient drugs at reduced prices, subject to prohibitions against drug diversion and duplicate discounts.

HRSA's long-standing conceptual framework for the patient definition appeared in the 1996 "Notice Regarding Section 602 of the Veterans Health Care Act of 1992; Patient and Entity Eligibility" (often referred to as the 1996 patient definition guidance).

Interpretive debates and policy updates have occurred: The 1996 guidance has been the practical reference point for decades, but its interpretation has been tested in litigation and reexamined by HRSA. Before codifying internal logic, verify the current state of guidance with counsel and HRSA OPA.

A durable way to think about the conceptual elements typically examined:

1. A relationship between the individual and the covered entity. The individual receives care through the covered entity such that the entity maintains records of that care.
2. Responsibility for the individual's care. The covered entity — through its professionals, or through professionals whose relationship supports a responsibility-of-care nexus — is responsible for the care that gives rise to the prescription.
3. A qualifying service. For grantees, the service generally must fall within the scope of the federal grant or project. For hospital-type entities, additional considerations apply.

Conceptual elements, in practical terms

Relationship and records

An established relationship is typically evidenced by registration as a patient, a clinical encounter documented in the entity's health record system, and ongoing or plausible continuity of care. Walk-in, event-based, or one-off encounters require particular care.

Responsibility for care

The professional who writes the prescription must be connected to the covered entity in a manner that supports the entity's responsibility for the care. Common arrangements include employed clinicians; clinicians under written contract or credentialing arrangement with the entity; and referrals in some circumstances. The operational question is: can you produce records showing the nexus between this prescription and the covered entity's care responsibility?

Qualifying service and scope

For grantees (FQHCs, look-alikes, Ryan White clinics), the service generally must be within the grant's scope of project. For hospitals (DSH, CAH, SCH, RRC, free-standing cancer hospitals, children's hospitals), additional conceptual elements apply, including that services be provided at a registered 340B site and appropriately reflected on the Medicare cost report. Outpatient status is central for hospital types.

Operationalizing eligibility determinations

EHR configuration

• Patient registration workflows produce records supporting the "relationship" element.
• Encounter documentation produces records for "responsibility for care."
• Provider credentialing and affiliation data must be accurate and current.
• Service line and location metadata must reflect which sites are registered 340B locations.

Pharmacy systems and accumulators

• Dispensing software must be configured so that eligibility logic maps to the EHR and patient record evidence.
• Accumulator logic must reflect policy decisions cleanly.
• For contract pharmacy arrangements, TPA configurations must mirror the entity's eligibility logic, not vendor defaults.

Eligibility rules documentation

Every rule embedded in systems should be documented in plain language, version-controlled, and reviewed regularly. Each rule template should capture: applies to; policy basis; guidance basis; systems where implemented; owner; last reviewed; known edge cases and handling; and test method and frequency.

Plain-language first: If a compliance officer cannot describe the rule without opening the EHR or TPA configuration, the rule is not documented.

Auditable prescription qualification logic

For each 340B-qualified prescription, a program should be able to produce, on request: the patient's registration and visit history; the prescribing provider's relationship to the entity at the time; the location and service line associated with the encounter; and the basis for concluding the prescription qualifies.

Edge cases

Referrals

When a covered entity refers a patient externally, or receives a patient referred in, the eligibility question hinges on who is responsible for the care and whether records support that responsibility. Counsel involvement is strongly recommended before any referral-based eligibility logic is relied upon for non-trivial volume.

Inpatient-to-outpatient transitions

The 340B program applies to outpatient drugs. Patterns to watch include discharge prescriptions written before outpatient status is established; "meds-to-beds" programs; and transitional care encounters.

Telehealth

Telehealth encounters generally should be treated using the same conceptual framework — relationship, responsibility, and qualifying service — with attention to the patient's location, the provider's location and licensure, how the encounter is recorded in the EHR, and state-by-state rules on telehealth practice.

Employee prescriptions

Employees may receive care at the entity as patients. The eligibility logic is the same. The pitfall is treating employees as categorically eligible or ineligible rather than evaluating the encounter.

Walk-ins and event-based encounters

Health fairs, vaccination events, street-medicine programs, and school-based events can present eligibility-definition challenges. Outreach is mission-central for many entities; it is also a frequent source of audit findings when documentation does not keep up with clinical activity.

Discharge prescriptions at contract pharmacies, specialty with payer-restricted networks, and research

The interplay between inpatient care, outpatient discharge, and contract pharmacy dispensing requires deliberate policy. Limited distribution networks can dictate where prescriptions can be filled. Care delivered under research protocols may or may not fit within the qualifying service element.

When in doubt, the conservative answer is usually the right one: Over-extending eligibility can produce diversion findings. Under-extending can leave patient access on the table. Edge cases should be resolved through documented analysis with counsel.

Data feeds needed

At a minimum, a defensible program will maintain or access:

• Patient registration and demographics.
• Encounter and visit data.
• Provider roster with covered-entity relationship type and effective dates.
• Location / site roster mapped to OPAIS.
• Scope-of-project or service-line data.
• Prescription data from EHR prescribing and pharmacy dispensing.
• Medicaid coverage data.
• Accumulator and TPA data.
• Referral and care-coordination data where relevant.

Common pitfalls

Narrowing scope unintentionally

• Overly rigid EHR templates that exclude legitimately eligible encounters.
• Registration workflows that miss eligible patients.
• Scope-of-project mapping out of sync with actual services.
• Overly cautious TPA defaults that systematically underclaim.

Over-extending scope

• Relying on referrals without documentation supporting responsibility for care.
• Treating employees or walk-ins as categorically eligible without encounter-level documentation.
• Telehealth logic that ignores patient location or site-of-service rules.
• Discharge prescriptions treated as outpatient without a clear policy boundary.
• Assuming a new clinic is an eligible child site before OPAIS registration is effective.
• Letting vendor defaults drive inclusion logic.

Policy-practice drift

Eligibility policy is often correct on paper and incorrect in practice because EHR configuration changed without compliance involvement, a TPA update altered default behavior, a new site or service was launched without eligibility review, or staff turnover left the rules in memory rather than documents.

Treating eligibility as a one-time project

Patient definition and eligibility logic are living systems that must evolve with clinical program changes, new sites, guidance updates, system upgrades, and referral arrangements.

Connecting eligibility to business development

Each BD move has an eligibility dimension: adding a child site; launching a specialty service line; contracting with a new contract pharmacy; expanding telehealth; launching outreach programs; or acquiring another entity. A BD plan that does not include an eligibility review is incomplete.

A suggested periodic review checklist

• Reconfirm alignment between current HRSA guidance and internal policy.
• Walk through each conceptual element against current practice.
• Review each edge-case policy.
• Validate provider roster documentation.
• Validate site roster against OPAIS.
• Reconcile scope-of-project with actual services.
• Test eligibility logic in EHR and dispensing systems.
• Review a sample of 340B-qualified prescriptions end-to-end.
• Refresh training.

When to involve counsel

Counsel involvement is especially important for close-call eligibility decisions, interpreting current HRSA guidance, telehealth expansion, research-related prescriptions, acquisitions and affiliations, responses to manufacturer audit inquiries, and any HRSA audit engagement.

References

• Section 340B of the Public Health Service Act, 42 U.S.C. § 256b.
• HRSA, "Notice Regarding Section 602 of the Veterans Health Care Act of 1992; Patient and Entity Eligibility," 1996.
• HRSA Office of Pharmacy Affairs (OPA), 340B Drug Pricing Program guidance, program notices, FAQs, and audit protocols.
• Apexus Answers, the HRSA-designated Prime Vendor Program resource.
• HHS Office of Inspector General (OIG) reports on 340B.
• For grantees, the applicable federal program authority (e.g., Section 330 for health centers; Ryan White HIV/AIDS Program legislation).
• For hospitals, applicable Medicare cost report and outpatient facility guidance.

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.