Back toAll articles

Cost Plus Drugs and NADAC: A Practical Guide to Drug Pricing Data

Understanding cost plus drugs requires more than looking for a single prescription drug price. The NADAC dataset published by CMS provides a structured reference for reading acquisition cost, pricing unit, and effective date together.

Cover Image for Cost Plus Drugs and NADAC: A Practical Guide to Drug Pricing Data

Understanding cost plus drugs requires more than looking for a single prescription drug price. Healthcare data users need to distinguish among acquisition-cost references, product identifiers, pricing units, classifications, and dates. The National Average Drug Acquisition Cost (NADAC) dataset provides a structured reference for that work.

NADAC is published by the Centers for Medicare & Medicaid Services (CMS), within the U.S. Department of Health & Human Services. It contains weekly reference data for a calendar year. The data can support analysis of drug pricing and prescription drug costs, but each record must be read in context.

QOPE brings selected public healthcare datasets into a more accessible environment. Its Drug Pricing data in QOPE includes fields such as NDC, drug name, NADAC per unit, pricing unit, OTC indicator, classification, pharmacy type, explanation code, effective date, and as-of date.

Table of contents

What NADAC data represents

NADAC means National Average Drug Acquisition Cost. It is reference data about drug acquisition cost, rather than a universal patient price or a single amount for every pharmacy.

The official CMS catalog describes NADAC as “weekly reference data for the calendar year.” In practical terms, a NADAC file can contain multiple observations for a product across different effective dates. A current analysis therefore needs to preserve the date associated with each value instead of treating the dataset as a timeless price list.

The catalog is organized by calendar year. For example, the official catalog page titled “NADAC (National Average Drug Acquisition Cost) 2026” describes the 2026 dataset as weekly reference data for that calendar year. The page lists a CSV resource and identifies CMS as the publisher.

The calendar-year structure matters when comparing files or building a historical analysis. A 2026 catalog dataset should not automatically be treated as a complete history of earlier years, and a value from one period should not be presented as though it applies indefinitely. Consult the original CMS or Medicaid.gov page when official verification is required.

Who publishes the official dataset?

The official NADAC catalog entry is published by the Centers for Medicare & Medicaid Services, part of the U.S. Department of Health & Human Services. The catalog identifies Medicaid.gov as the contact point and provides a public CSV distribution.

This is U.S.-specific public healthcare data. Its terminology and administrative context should not be generalized to drug-pricing systems in other countries. An international analyst can still use the data for research involving the United States, but comparisons with other jurisdictions require attention to each country’s definitions, reimbursement structures, and price references.

QOPE is separate from CMS and from the official catalog. QOPE organizes information from authoritative public sources and presents selected fields in an accessible environment. Users should consult the original public source when official verification is required.

How to read the main fields

A NADAC-oriented drug pricing record brings several concepts together:

  • NDC: The National Drug Code identifies the drug product at the code level represented in the record. It is useful for distinguishing products that may have similar names.
  • Drug name: The text description helps identify the product represented by the record.
  • NADAC per unit: The numeric reference value is paired with a pricing unit. It should be interpreted together with that unit.
  • Pricing unit: This explains the basis on which the per-unit value is stated. A value cannot be interpreted responsibly without knowing whether the unit is, for example, a tablet, milliliter, or another listed measure.
  • OTC indicator: This indicates the classification supplied for over-the-counter status in the record.
  • Classification: This provides the record’s relevant product classification.
  • Pharmacy type: This describes the pharmacy-type field supplied with the record.
  • Explanation code: This provides additional context attached to the record.
  • Effective date: This indicates the date associated with the reference value.
  • As-of date: This records the applicable “as of” context available in the data.

These fields answer different questions. The NDC identifies the product code; the drug name describes the product; the NADAC per unit gives the reference value; and the pricing unit tells you how to interpret that value. The dates help establish when the reference applies.

Worked example: reading one NADAC record

Consider a single record with the following values:

  • Drug name: OZEMPIC
  • NDC: 0169-4132-12
  • NADAC per unit: 10.34250
  • Pricing unit: ML
  • Effective date: 2026-08-25

Start with the product identity. The drug name is OZEMPIC, while the NDC is 0169-4132-12. The NDC gives the record a specific product-code reference; it is more precise than relying on the name alone when several presentations or codes may exist.

Next, interpret the numeric value with its unit. The record states 10.34250 as the NADAC per unit and identifies the pricing unit as ML. Read together, these fields describe a reference amount per milliliter. Separating the number from “ML” would remove information needed to understand what the value represents.

The effective date, 2026-08-25, places the reference in time. If another record for the same NDC has a different effective date, the two records may represent different weekly observations. A historical comparison should retain both dates rather than collapsing them into one undated figure.

What does this record tell you? It identifies a particular product code, provides a product name, states a NADAC reference value on a milliliter basis, and associates that value with an effective date.

What does it not tell you? It does not, by itself, describe a patient’s final payment, establish a pharmacy’s transaction amount, or answer every question about reimbursement. It also does not make the value interchangeable with another product presentation whose NDC, package, concentration, or pricing unit differs. Those interpretations require additional information beyond this single row.

This example shows why drug pricing analysis should treat identity, unit, and date as a connected set. Searching by a familiar brand name alone can obscure product-level distinctions. Reading the NDC without the drug name can make the result harder to interpret. Reading the numeric value without the pricing unit can make the result misleading.

Using NADAC for cost-plus comparisons

Cost-plus models generally invite a comparison between a reference acquisition cost and an additional amount such as a dispensing fee, service charge, or other component. NADAC can provide one reference point for that analysis, but a comparison must preserve the exact product, unit, and date.

A pharmacy reference from another source may use a different product definition, package size, update schedule, or pricing basis. Before comparing values, align:

  1. The product identifier or other product-level reference.
  2. The drug name and presentation.
  3. The pricing unit.
  4. The relevant effective date.
  5. Any classification or pharmacy-type context.
  6. The purpose of each price or cost measure.

This approach helps prevent a common analytical error: placing two numbers side by side because they share a drug name while overlooking differences in units or product codes. For a broader introduction to this type of comparison, see WAC, ASP, AWP, and NADAC Drug Pricing: Comparing Public Measures.

NADAC can also support research into prescription drug prices when the analyst clearly labels the measure being used. Calling a NADAC value a “price” without explaining its reference basis can blur the distinction between acquisition-cost data and other price concepts.

A date-aware approach to weekly data

Because NADAC data are published weekly, date handling is central to responsible use. A useful workflow is to treat the effective date as part of the observation, not as supplementary metadata.

For each product-level question, ask:

  • Which calendar-year dataset contains the record?
  • What effective date is attached to the value?
  • Is the comparison using the same product code?
  • Is the pricing unit consistent?
  • Does the as-of date add context to the observation?
  • Are explanation code and pharmacy type relevant to interpretation?

The official catalog page for the 2026 file states that the dataset was last updated on August 25, 2026, while the catalog was last checked on August 26, 2026. These are catalog-specific timestamps, so readers should check the official page for the current listing before relying on changing availability or update information.

Common drug pricing research questions

Can NADAC help compare prescription drug costs?

Yes, NADAC can serve as a reference in an analysis of prescription drug costs, provided the analyst preserves the product identity, unit, and date. It should be described as NADAC reference data, not treated as a universal transaction amount.

Why does the pricing unit matter?

A numeric value has limited meaning without its denominator. “Per unit” must be read alongside the dataset’s pricing-unit field. Comparing a milliliter-based value with a tablet-based value without adjustment can produce an invalid conclusion.

Why use the NDC instead of the drug name alone?

The NDC provides a product-code reference that can distinguish records associated with different product presentations. A brand or generic name may not contain enough detail for a precise record-level comparison.

Look up a specific product in the Drug Pricing dataset, where NDC, drug name, pricing unit, and effective date can be reviewed together. The dataset catalog lists the other public sources QOPE organizes.

FAQ

What is NADAC?

NADAC is National Average Drug Acquisition Cost reference data published weekly for a calendar year by the Centers for Medicare & Medicaid Services.

Is NADAC useful for cost-plus drugs analysis?

It can be used as one reference in cost-plus drugs research when the analyst matches the product, pricing unit, and effective date and distinguishes the reference from other pricing measures.

What should I record when saving a NADAC observation?

At minimum, retain the NDC, drug name, NADAC per unit, pricing unit, effective date, and as-of date, along with relevant classification or explanation fields.

QOPE is not affiliated with CMS, the FDA, or any government agency. QOPE organizes selected public healthcare data and does not replace official sources.

Explore Drug Pricing data in QOPE.

Sources

Follow QOPE in GoogleAdd QOPE as a preferred source