latest update:
[RxAtlas]

Coverage · what the dataset can prove

Coverage is the public checklist for evaluating a pack before purchase: exported records, active sources, field groups, workflow fit, and the caveats that limit interpretation.

Record coverage

The public counts below come from export-ready records and the source registry. They update with every snapshot cut instead of being hand-maintained in website copy.

FDA product-NDC rows
135,544

Rows in the current dated release, with one row per openFDA product NDC.

Product NDC coverage
100%

Share of exported FDA product rows carrying the authoritative two-segment product NDC used as the release identity.

SPL link coverage
100%

Share of exported FDA product rows associated with at least one DailyMed SPL set identifier.

Multi-source coverage
82.74%

Share of exported FDA product rows receiving active provenance from more than one contracted public source.

Application-number coverage
72.75%

Share of exported FDA product rows with a served NDA, ANDA, BLA, or source marketing marker.

NADAC price coverage
14.90%

Share of exported FDA product rows with a latest-effective, source-linked NADAC per-unit value.

Freshness policy
Weekly refresh

Maximum age 8 days. Oldest measured source refresh: 2026-09-16.

Weekly releases identify source dates. Product feeds, Drugs@FDA, and REMS use an eight-day bound; PMR/PMC, IID, and CMS SDUD use explicit 100-day bounds.

/drugs records
135,544
active sources
13
provenance rows
3,613,697
These are export-ready counts, not a claim that every field is populated for every record. Field-level coverage is documented in the data dictionary and source notes.

Field coverage

Schema groups come from the exported field model and curated field highlights. They are the default coverage map for filtering, joining, and reviewer audit work.

groupfieldsexamples
Record identity6id, primary_source, source_id, source_record_url
Product names3brand_name, generic_name, manufacturer_name
Product form6dosage_form, route, strength, product_type
Regulatory status3marketing_status, dea_schedule, application_number
Classification3rxcui, atc_code, pharm_class
Provenance2_provenance, _sources
Shortage signals1shortages
Pricing2nadac_per_unit, pricing_unit
Recall signals2has_recall, recall_reason
documented fields
28
domain fields
26
provenance-aware fields
9

Source coverage

Source descriptions make coverage visible before a buyer logs into the portal or downloads the full snapshot.

CMS SDUDcommercial-use cleared

State and national aggregate Medicaid utilization facts at utilization-type, exact NDC11, year, and quarter grain; suppressed measures remain null and reimbursement is not represented as price or coverage.

DailyMedcommercial-use cleared

Structured Product Label titles, versions, and publication dates joined to the SPL set identifiers carried by FDA product records.

Drugs@FDAcommercial-use cleared

FDA application, product-number, submission, and document-metadata records delivered as separate auxiliary tables without claiming product-number-to-NDC applicability.

FDA IIDcommercial-use cleared

Quarterly FDA inactive-ingredient potency and maximum-daily-exposure facts delivered at ingredient/route/dosage-form grain; CAS Registry Numbers are excluded and product applicability is not asserted.

Workflow coverage

These use cases are the workflows this dataset is positioned to support. The same workflow set appears on the homepage, sample page, and agent-facing docs.

Find drug products

Search products by name or NDC code and inspect ingredients, dosage forms, and package identifiers.

Explore related records

Review linked label, RxNorm, and pricing records where available.

Find enforcement and shortage records

Inspect source-reported records linked to products by exact NDC identifiers.

Review data coverage

Check which products have related records and follow their source links.

Limits

Coverage claims should stay bounded by the manifest caveats and source licence terms.

  • RxAtlas is reference data, not medical advice, prescribing advice or reimbursement advice.
  • Buyers remain responsible for validating source terms and regulated use in their own workflow.

Related evaluation guides

Connect this diligence evidence to the relevant integration decision.