Skip to content
FonteumPublic-records evidence

← All sources Research / economic / workforce

HRSA 340B OPAIS

HRSA 340B OPAIS Covered Entities

Health Resources & Services Administration (HRSA), Office of Pharmacy Affairs · Tier-2 · profile-enrichment (renders on matched profiles)

Deferred

The HRSA 340B Office of Pharmacy Affairs Information System (OPAIS) is the public registry of covered entities enrolled in the federal 340B drug-pricing program — disproportionate-share hospitals, FQHCs, and other safety-net providers eligible for discounted outpatient drugs. The schema and provenance contract are live; the first OPAIS export snapshot is pending, so the table currently holds 0 rows.

What Fonteum uses it for

How this source shows up on Fonteum.

Will surface 340B covered-entity identity (340B ID, entity name, entity type, participation status, location) on the dataset page once the first OPAIS export lands. NPI / CCN cross-link into the entity graph is deferred to a gated follow-up — ambiguous matches are held, never written.

What this source does NOT mean

340B participation is a drug-pricing-program enrollment record — it does not indicate provider quality, outcomes, or endorsement. Presence in OPAIS means an entity is enrolled in the 340B program; it is not a Fonteum assessment of that entity.

What this dataset answers

Research and data questions this source supports.

  • Identify hospitals, FQHCs, and clinics enrolled in the federal 340B drug-pricing program once the first OPAIS snapshot lands.
  • Cross-reference 340B covered-entity participation against CMS facility identity for safety-net program analysis.
  • Build a research dataset of 340B participation with row-level provenance and snapshot dates.
  • Track entity-type composition (disproportionate-share hospitals vs. FQHCs vs. other grantees) across the 340B program.

Dataset size: 0 rows — first OPAIS export snapshot pending (as of 2026-06-14)

Fields used

Per-field display contract.

Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not rendered on profile pages.

Research-only — never on profiles

4 fields
id_340b340B ID
entity_nameCovered-entity name
entity_typeEntity type (DSH / FQHC / etc.)
participation_statusParticipation status
Limitations

What we can’t infer from this source.

  • First ingest snapshot pending — the table currently holds 0 rows. Figures will populate once the operator runs the OPAIS export.
  • OPAIS publishes no clean no-auth flat-file endpoint; the snapshot is an operator-driven export, so cadence depends on that pull.
  • NPI / CCN -> entity-graph cross-link is deferred; ambiguous matches are held, not written.
  • 340B enrollment is a program-participation fact, not a quality measurement.
Source metadata

Authority, license, publisher cadence.

Authority

Health Resources & Services Administration (HRSA), Office of Pharmacy Affairs

Tier

Tier-2 · profile-enrichment (renders on matched profiles)

Publisher / configured cadence

Declared or configured cadence: Monthly — sourced from a HRSA 340B OPAIS export. OPAIS publishes no clean no-auth flat-file endpoint, so the snapshot is operator-driven. Not evidence of the latest loaded source date.

License

U.S. government public-domain data. Free to use with attribution. License ↗

Attribution requirement

Source: HRSA 340B Office of Pharmacy Affairs Information System (OPAIS) · Snapshot {YYYY-MM-DD}

ToS & usage notes

What the source allows.

U.S. government public-domain works. HRSA publishes the 340B covered-entity registry through the OPAIS public search (340bopais.hrsa.gov); attribution to HRSA OPAIS is the only requirement.

How to access

Official API, bulk download, and Fonteum endpoints.

Frequently asked

Common questions about HRSA 340B OPAIS.

What is the 340B program?
The 340B Drug Pricing Program requires drug manufacturers to provide outpatient drugs to eligible safety-net providers — covered entities — at significantly reduced prices. HRSA's Office of Pharmacy Affairs administers the program and publishes the covered-entity registry through OPAIS.
What is OPAIS?
OPAIS is the 340B Office of Pharmacy Affairs Information System — HRSA's public registry of 340B covered entities and contract pharmacies. It records each entity's 340B ID, name, entity type, participation status, and location.
Why does this dataset currently show 0 rows?
OPAIS does not publish a clean no-authentication flat-file endpoint, so the snapshot is operator-driven: it requires an export from the OPAIS public search. The schema and provenance contract are live, but the first export snapshot is pending — so the table honestly holds 0 rows until that ingest runs.
Does 340B participation indicate provider quality?
No. 340B participation is a drug-pricing-program enrollment record. It indicates that an entity is enrolled in the program — it is not a measurement of clinical quality, outcomes, or any Fonteum assessment of that entity.
Will 340B data link to provider profiles?
Not yet. OPAIS carries Medicare CCN and NPI where present, but the NPI / CCN cross-link into Fonteum's entity graph is deferred to a gated follow-up. Ambiguous matches are held, never written, to avoid asserting an identity link that the source does not unambiguously support.
Related

Related sources in the graph

See also
  • /sources → The generated source-catalog subset — documented datasets Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

What’s on file, by the numbers

Platform snapshot · 2026-08-14

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
72fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access