Diversified Support Services Data: Labor Ledgers, Safety Records, Business Registers and Service-Sector Revenue · Head-to-head
CMS National Average Drug Acquisition Cost (NADAC) vs DailyMed Structured Product Labeling Repository
Which diversified support services data: labor ledgers, safety records, business registers and service-sector revenue data fits your job: CMS National Average Drug Acquisition Cost, or DailyMed Structured Product Labeling Repository. API, files, or your warehouse. Daily, weekly, or hourly.
CMS National Average Drug Acquisition Cost (NADAC)
DailyMed Structured Product Labeling Repository
Where the fields line up
1 shared field — join on these.
| Field | CMS National Average Drug Acquisition Cost | DailyMed Structured Product Labeling Repository |
|---|---|---|
NDC | 11-digit National Drug Code identifying the specific package. | National Drug Code linked to the SPL document - the bridge to acquisition-cost, dispensing and catalog panels. |
What each contains
Pick by fit, not by loyalty.
| CMS National Average Drug Acquisition Cost | DailyMed Structured Product Labeling Repository | |
|---|---|---|
| Documented fields | 12 | 11 |
| Shared columns | `NDC` - the 11-digit National Drug Code, the single join key between the two records | `NDC` - linked to the SPL via label-to-NDC mapping files and lookup endpoints |
| Identity | `NDC Description` - labeler-defined product description per package | `setid` (stable UUID per label document), `title` naming product and labeler, `application number` (NDA/ANDA) |
| Money columns | `NADAC Per Unit` in USD, `Corresponding Generic Drug NADAC Per Unit`, quoted on `Pricing Unit` (EA, ML or GM) | None - no financial fields anywhere in the dictionary |
| Document columns | None beyond the description text | `spl_version` and `published_date` for the revision trail, `packaging` descriptions |
| Segment dimensions | `Pharmacy Type Indicator` (C/I chain vs independent), `OTC` flag, `Classification for Rate Setting` (brand/generic) | `drug class` pharmacologic indexing, `RxCUI` and `UNII` identifiers, `REMS` participation flag |
| Provenance / dating | `Effective Date` for the rate, `As of Date` for the weekly file, `Explanation Code` for how the rate was set | `published_date` per version plus full set-ID history; prior versions archived |
| Join keys | Keys on `NDC` + `Effective Date` + `As of Date`; no other shared vocabulary | Keys on `setid`, cross-mapped outward to `NDC`, `RxCUI`, `UNII` and drug class |
What each does better
NADAC
It is the buy-side number. Nothing else at this grain states what retail community pharmacies actually paid: a survey-weighted national average per unit, in dollars, quoted on a stated unit (EA, ML or GM), with a brand/generic classification for rate setting and the corresponding generic's NADAC riding alongside the brand row.
It moves weekly, and it dates itself honestly. Each record carries an Effective Date for the rate and an As of Date for the weekly file, so a time series can be built without guessing which snapshot a row came from; the 2026 edition stood current as of August 19, 2026. Thirteen-plus annual consolidated editions from 2013 onward make year-over-year work straightforward.
It flags the segment. The C/I pharmacy type indicator separates chain from independent participation, and the OTC flag splits prescription from over-the-counter shelf - two cuts DailyMed has no reason to make.
DailyMed SPL
NLM is candid that the repository does not hold a complete listing of all FDA-regulated labeling, but as a public corpus of submitted labels it has no peer.
Versioning. Every label is a document under a stable setid with a numbered spl_version and a published_date; prior versions persist in Labeling Archives and each set exposes its own history.
Identity plumbing. RxCUI concept codes, UNII ingredient identifiers, FDA application numbers, pharmacologic classes and packaging descriptions hang directly off the label record, plus a REMS participation flag. That makes DailyMed the spine for building a retail drug knowledge base; NADAC deliberately carries none of this.
Where they're equivalent
In governance more than content. Both come from US federal health agencies and were verified field-by-field during the August 2026 research pass, so both field dictionaries can be trusted at the column level. Both score 9/10 on Datadory's rubric - top decile territory against the 7.81 catalog average, and two of the eight 9-scoring records in this slice. Both cover the United States market. Both are complete enumerations of their own domain rather than samples: every NDC that surfaced in the weekly surveys on one side, every submitted label in the repository on the other. And both ship stable schemas whose meanings hold edition to edition, which is why either can anchor an automated pipeline.
Where equivalence stops is unit of analysis. They agree on the country and, via the NDC, on the product - nothing else in the two dictionaries means the same thing.
Or take both in one feed
Run it in reverse for pricing questions - take the NDCs that moved most in the latest NADAC week, then read their labels to find what changed: new pack sizes, new strengths, a rebranded labeler.
Three cautions from the field dictionaries. First, grain mismatch: one SPL set ID can stand behind many NDCs, so a naive join fans out and inflates counts - aggregate deliberately. Second, NADAC's NDC identifies one package; package-level matching matters because the same product can carry different NDCs per pack. Bridge the two on purpose, and neither side misleads.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Do NADAC and DailyMed Structured Product Labeling Repository cover the same drugs?
Not the same lists. NADAC covers the drug products that turned up in CMS's surveys of chain and independent retail community pharmacies - roughly 30,000-plus NDCs per annual cycle, prescription and OTC. DailyMed holds 158,748 labels spanning human and animal Rx and OTC products, medical gases, devices, cosmetics, dietary supplements and medical foods, and NLM cautions it is not a complete listing of all FDA-regulated labeling.
Can I join NADAC to DailyMed Structured Product Labeling Repository on NDC?
Partially, and only with care. The 11-digit NDC is the one column both records carry in common. Build the bridge through DailyMed's NDC mapping files rather than assuming a one-to-one merge.
Which dataset goes further back in time?
DailyMed's history runs deeper: current labels are versioned, prior versions sit in Labeling Archives, and each set ID carries its own history. NADAC starts in 2013, with thirteen-plus annual consolidated editions plus weekly deltas - and even inside that span, Effective Date was not recorded before June 7, 2017, so earlier rows lack the field.
Which should a reimbursement analyst sample first?
Add DailyMed when the question is what the product actually is - strength, dosage form, packaging, ingredients or REMS status. Most pricing work ends up needing both.
Can I get both NADAC and DailyMed SPL data from Datadory?
Yes - sample both, pick by fit, or take both in one feed. Datadory normalizes each record to its documented field dictionary, attaches sample rows for validation, and ships them alongside the rest of the diversified support services catalog, delivered daily, weekly, or hourly - your call.