By Vincent Couey, OmniRx founder. Reviewed by the OmniRx Clinical Review Team. Source-cited from HRSA Office of Pharmacy Affairs, the 340B OPAIS user guidance, and the federal statute. Updated .
Every pharmacy claim run at a 340B price rests on one question: is this entity, at this site, actually eligible right now? Operators keep searching for a real-time 340B eligibility validation HRSA endpoint that returns an instant yes or no. It does not exist in the way the phrase implies. If you need to confirm an entity before applying a discount, the honest path is an OPAIS lookup, and you can run our drug safety and savings tools alongside it. This guide separates the real mechanism from the marketing.
A "real-time" 340B check reads the public OPAIS registry, then your software makes the apply-or-hold decision. HRSA is never queried as a live approval service.
What does real-time 340B eligibility validation actually mean?
Real-time 340B eligibility validation is the act of confirming, at or near the moment of a transaction, that a covered entity and its dispensing location are properly registered before a 340B price is applied. Here is the critical clarification that anchors this whole guide: HRSA does not run a public real-time eligibility-verification API or web service. The OPAIS (the 340B Office of Pharmacy Affairs Information System) is a searchable public database, per the public OPAIS portal maintained by HRSA.
So when a manufacturer, wholesaler, or compliance vendor says they offer "real-time 340B validation," they mean their own software is cross-checking a claim against OPAIS registry data, not pinging an instantaneous HRSA decision endpoint. The distinction matters because it tells you where the truth lives (the public registry) and who owns the logic (your vendor or your team), and it stops you from waiting on an approval signal that will never arrive.
- 340B Program
- A federal drug pricing program created by Section 340B of the Public Health Service Act that requires drug manufacturers to sell outpatient drugs at discounted prices to eligible covered entities.
- Covered Entity (CE)
- An organization that statutorily qualifies for 340B pricing, such as a Federally Qualified Health Center or a Disproportionate Share Hospital, and is registered in OPAIS.
- OPAIS (340B Office of Pharmacy Affairs Information System)
- HRSA's public, searchable registry of covered entities, child sites, contract pharmacies, and manufacturers. It is read for verification; it is not a real-time approval API.
- Authorizing Official (AO)
- The senior officer at a covered entity who is legally responsible for registration and for completing annual recertification in OPAIS.
Which entities are eligible 340B covered entities?
Eligibility is not discretionary; it is defined by statute and enforced by HRSA's Office of Pharmacy Affairs. An organization either fits a listed covered-entity category or it does not. Per the HRSA eligibility and registration guidance, the statutory covered-entity types include:
- HRSA-supported health centers, meaning FQHCs (Federally Qualified Health Centers) and FQHC look-alikes
- Ryan White HIV/AIDS Program clinics and State AIDS Drug Assistance Programs (ADAPs)
- Medicare and Medicaid Disproportionate Share Hospitals (DSH)
- Children's hospitals
- Critical access hospitals
- Sole community hospitals and rural referral centers
- Specialized clinics: hemophilia treatment centers, tuberculosis, black lung, sexually transmitted disease, and family planning
Each eligible entity is registered and then listed in the public OPAIS database. That public listing is the backbone of every verification workflow: if an entity is not in OPAIS with an active registered status, there is nothing to validate in real time, because the registry is the single source of truth.
Q: Does a pharmacy benefit manager (PBM) confirm 340B eligibility for me?
No. A PBM adjudicates the insurance claim and benefit. It does not certify 340B eligibility. Eligibility verification is a separate OPAIS registry match that your 340B software or team performs, regardless of which PBM processed the claim.
How do you verify a 340B covered entity in OPAIS, step by step?
The mechanics of a clean check are short. This is the workflow our software automates, but you can run it by hand for any single entity in roughly five minutes verified 2026-06-10.
Step 1: Open the public OPAIS covered-entity search
Go to the 340B OPAIS public search. No login is required for the public covered-entity, contract-pharmacy, and manufacturer searches. This public access is exactly why "real-time" verification is possible at all: the registry is open to read.
Step 2: Search by 340B ID, name, or address
Enter the covered entity's 340B ID (for example, the format used for community health centers) or search by entity name and address. The 340B ID is the most reliable key because names and addresses drift over time.
Step 3: Confirm registered status and entity type
Open the record and confirm two things: the registration shows an active registered status, and the entity type is one of the statutory categories above. An entity in "terminated" status, or one whose grant or hospital qualification has lapsed, cannot receive a 340B price even if it appears in historical data.
Step 4: Check the child site or contract pharmacy
Eligibility flows from the parent entity to its registered child sites and contract pharmacies. Confirm that the specific dispensing location is listed under the parent's 340B ID. A drug dispensed at an unregistered site is a diversion risk, which is one of the most common audit findings detailed in our 2026 HRSA 340B audit guide.
Step 5: Record the verification date
Capture the date of your OPAIS lookup. Because eligibility can change at the annual recertification window, a verification is a point-in-time snapshot, not a permanent clearance. Audit-ready entities log the lookup date alongside the claim.
Why is 340B recertification annual rather than real-time?
This is the most misunderstood part of the program, and it is the reason "real-time" can only ever mean "real-time registry match." Per HRSA's recertification guidance, recertification is annual, not real-time and not quarterly verified 2026-06-10. Each covered entity's Authorizing Official must annually recertify both eligibility and 340B compliance in OPAIS during a scheduled window assigned to that entity type.
The consequence is blunt: failure to recertify on time results in termination from the program. There is no grace adjudication and no automatic renewal. An entity that misses its window loses access to 340B pricing until it re-registers, which can mean a fresh registration cycle. That is why your verification workflow must treat OPAIS status as something that can flip once a year, not a static fact.
Two related obligations sit alongside the annual cycle. First, an entity must immediately notify HRSA OPA through OPAIS when its eligibility changes, and it must stop 340B purchasing the moment it no longer qualifies; the change cannot wait for the next recertification. Second, HRSA does not take the entity's word for it. The agency verifies eligibility against authoritative sources, and for hospital outpatient sites that means the most recently filed Medicare Cost Report verified 2026-06-10, per HRSA eligibility and registration guidance. A hospital's Disproportionate Share Hospital percentage is read from that filing, not self-attested.
The off-site child-site 90-day window is not the recertification cycle
One window is frequently confused with the annual one and it deserves its own line. Under HRSA's 2023 registration-requirements guidance, published as Federal Register notice 2023-23702 (October 27, 2023), a covered entity that is dispensing 340B drugs at an unregistered outpatient site gets up to 90 days after the relevant Federal Register notice verified 2026-06-10 to either register that site or stop using 340B drugs there. After that 90-day off-site compliance window closes, the entity may face audit and compliance action. This is distinct from the annual recertification cycle: recertification renews a registered entity once a year, while the 90-day window governs how fast a new or unregistered child site must be brought into the registry before its claims become exposure.
Q: If recertification is annual, how is verification "real-time" at all?
The registry is updated continuously as entities register, add child sites, change contract pharmacies, or get terminated. Your software reads the current OPAIS state at the moment of the claim. The eligibility decision (whether an entity qualifies as a category) is annual; the data freshness (what the registry says right now) is continuous. Real-time verification rides on the second, not the first.
For entities that also rely on HRSA grant funding, the recertification rhythm parallels other federal compliance calendars. Our colleagues at GrantProbe cover HRSA community health center grant eligibility, and the documentation discipline carries over almost directly: keep your qualifying status provable, on a calendar, and audit-ready.
Where does real-time 340B verification go wrong?
The failures are specific and preventable. Naming them is more useful than a checklist of platitudes.
- Treating a vendor claim as an HRSA approval. If a platform says "HRSA-validated in real time," read it as "matched against OPAIS." The validation logic is the vendor's, and any error in their OPAIS sync is your audit exposure.
- Verifying the parent but not the dispensing site. A registered parent entity does not make every location eligible. The child site or contract pharmacy must be listed under that 340B ID.
- Caching eligibility past the recertification window. An entity verified in January can be terminated by its annual window. Stale caches apply 340B prices to terminated entities, which is a repayment-grade finding.
- Confusing eligibility with the patient definition. Entity eligibility is necessary but not sufficient. The individual must still meet the HRSA patient definition. Both checks are separate.
- Assuming OPAIS data is instantaneous. Registration changes post on HRSA's schedule, not the moment a hospital signs a contract. Verify against what is published, not what you expect to be published.
- Missing the 90-day off-site window on a new child site. A new outpatient location that is already dispensing 340B drugs has up to 90 days after the relevant Federal Register notice to register or stop. Treat an unregistered site as a hard stop, not a pending detail.
OPAIS and HRSA policy changes, recertification reminders, and audit-readiness guidance for covered entities. Sourced, no spam.
What should real-time 340B verification software actually do?
Software does not create eligibility. It removes the manual lag between a claim and an accurate OPAIS read. After reviewing how entities get tripped up, four capabilities separate a real verification tool from a marketing label.
Continuous OPAIS sync. The system should refresh against the public OPAIS registry on a defined cadence so that a terminated entity is flagged before a claim applies a 340B price. Frame "real-time" as freshness of the registry copy, not a fictional HRSA call.
Site-level resolution. The tool must validate the dispensing child site or contract pharmacy under the parent 340B ID, not just the parent. Site-level resolution is where diversion findings are prevented.
Recertification calendar awareness. Because eligibility can flip annually, the system should track each entity's recertification window and alert before it lapses, so a missed window does not silently become a stream of ineligible claims.
Audit-ready logging. Every verification should be logged with its OPAIS lookup date, status, and entity type, exportable for a HRSA review. A verification you cannot reproduce is a verification HRSA will not credit.
What happens when 340B does not apply?
Plenty of patients and prescriptions fall outside a covered entity's 340B scope: an unregistered site, a terminated entity, a non-qualifying patient encounter, or a drug excluded from the program. In those cases the price defaults to cash or insurance, and that is where ordinary savings tools matter.
For cash-paying patients, a discount card can beat an uninsured retail price. Our colleagues at RxGrab compare the leading prescription discount cards, and their head-to-head on GoodRx versus SingleCare is a useful next read when 340B is off the table. None of that replaces eligibility verification; it is simply the right tool for the patients 340B does not cover.
Inside the program, the next step after eligibility is keeping the rest of your compliance posture clean. Walk our 340B compliance checklist for the audit-ready document set, then review split billing methods to keep 340B and non-340B inventory cleanly separated.
Frequently Asked Questions
Does HRSA offer a real-time 340B eligibility verification API?
No. HRSA does not operate a public real-time eligibility-verification API or web service. The 340B OPAIS is a searchable public registry. When vendors and manufacturers describe real-time 340B validation, they mean third-party compliance or split-billing software cross-checking a claim against the public OPAIS data, not an instantaneous HRSA validation endpoint.
Which entities are eligible 340B covered entities?
Eligibility is set by statute. Covered entities include HRSA-supported health centers (FQHCs) and look-alikes, Ryan White HIV/AIDS clinics and State ADAPs, Medicare and Medicaid Disproportionate Share Hospitals, children's hospitals, critical access hospitals, sole community hospitals, rural referral centers, and certain specialized clinics such as hemophilia, tuberculosis, black lung, sexually transmitted disease, and family planning. Each is registered and listed in the public 340B OPAIS database.
How often must a 340B covered entity recertify?
Recertification is annual, not real-time or quarterly. Each covered entity's Authorizing Official must annually recertify eligibility and 340B compliance in OPAIS during a scheduled window. Failure to recertify on time results in termination from the program.
What does real-time 340B eligibility validation actually check?
It cross-checks a pharmacy or hospital claim against the public OPAIS registry: the covered-entity 340B ID, the registered active status, and whether the dispensing child site or contract pharmacy is listed under that entity. It is a registry match, not a live HRSA approval.
Can a 340B covered entity be terminated for eligibility lapses?
Yes. Missing the annual recertification window causes termination. An entity can also lose eligibility if it no longer meets the statutory grant or hospital criteria, for example loss of FQHC funding or a drop below the required DSH percentage. An entity must also immediately notify HRSA through OPAIS when its eligibility changes and stop 340B purchasing if it no longer qualifies.
What is the 340B off-site child-site 90-day compliance window?
Under HRSA's 2023 registration-requirements guidance, published as Federal Register notice 2023-23702 on October 27, 2023, a covered entity dispensing 340B drugs at an unregistered outpatient site has up to 90 days after the relevant Federal Register notice to register that site or stop using 340B drugs there. This 90-day off-site window is distinct from the annual recertification cycle: recertification renews a registered entity once a year, while the 90-day window governs how fast a new or unregistered child site must be brought into the registry before its claims become exposure.
- Health Resources and Services Administration, Office of Pharmacy Affairs. 340B Eligibility & Registration. hrsa.gov/opa/eligibility-and-registration verified 2026-06-10
- Health Resources and Services Administration, Office of Pharmacy Affairs. 340B Recertification. hrsa.gov/opa/recertification verified 2026-06-10
- 340B Office of Pharmacy Affairs Information System (OPAIS) public portal. 340bopais.hrsa.gov verified 2026-06-10
- Federal Register. Registration Requirements in the 340B Drug Pricing Program, notice 2023-23702, 88 FR (Oct. 27, 2023). federalregister.gov/documents/2023/10/27/2023-23702 verified 2026-06-10
- Health Resources and Services Administration. 340B Drug Pricing Program, Office of Pharmacy Affairs. hrsa.gov/opa verified 2026-06-10