Rx. Radar

Public data methodology

This page explains how Rx Radar sources, reviews, publishes, and corrects its public HCPCS Level II code pages.

What is published

Public lookup covers source-backed CMS drug codes. The current search-index cohort contains 51 reviewed code pages. Other CMS drug-code lookups remain noindex until they pass the same review.

Review process

  1. Official CMS record

    The page must have a current final or revised CMS ASP payment-limit row, an approved alphanumeric HCPCS Level II code, a stated billing unit, and a stable source-file receipt. Numeric CPT codes are excluded.

  2. Package identity verification

    At least one package mapping is checked against public FDA NDC Directory and NIH DailyMed records. Source hashes and identifiers are retained so the facts can be reproduced and checked.

  3. One canonical code page

    Every supported code uses one stable uppercase URL. Lowercase variants redirect to it, and invalid codes return a real not-found response.

  4. Reviewed release

    Pages, the directory, sitemap, metadata, and crawler rules are released as one reviewed snapshot. A failed build leaves the prior deployed snapshot in place.

Sources and limits

CMS
ASP Pricing Files and NDC-HCPCS crosswalk records provide payment-limit and billing-unit context.
FDA
NDC Directory records provide public package-identity context, not real-time supply, wholesaler availability, or local access.
DailyMed
NIH DailyMed structured labels help verify package descriptions and ingredient identity.

CMS Medicare Part B payment-limit context only; not coverage, coding, billing, patient eligibility, MAC/payer, claim, or actual-payment determination. Verify HCPCS, units, and payer requirements.

Corrections

If a public page needs another look, contact Rx Radar with the code and source detail. We review the evidence before changing a published snapshot. You can also browse the public code pages.