National Drug Codes (NDCs) identify a specific product and package — meaning the same Metformin from two different manufacturers carries two different codes, and a 30-count vs. 90-count bottle of Lipitor™ are treated as completely unrelated drugs. That makes even simple questions impossible to answer from your data alone.
RxMap converts every NDC into a standardized ingredient name, strength, and dose form, and returns your file enriched and ready to analyze. How many patients took a statin last year? Which generic costs the least to acquire? Questions like these go from hours of manual work to straightforward analysis — no code, no API, no data team required.
| ndc_code | rxcui | IN_ingredient | SCD_semantic_clinical_drug |
|---|---|---|---|
| 00093-0058-01 | 161 | Acetaminophen | Acetaminophen 325 MG Oral Tablet |
| 0069-3060-20 | 617314 | Atorvastatin | Atorvastatin 10 MG Oral Tablet |
| 00006-0117-31 | 29046 | Lisinopril | Lisinopril 5 MG Oral Tablet |
Built for
Working with MEPS, Medicare Part D, Medicaid SDUD, NHANES, or SEER-Medicare? These public datasets ship with NDC codes. RxMap adds the drug-level identifiers your study needs.
Analyzing publicly available medication data for a thesis, dissertation, or course project — without a team of data engineers behind you.
You work in Excel, Stata, SAS, or R and need a clean NDC crosswalk — but writing API calls or maintaining a script isn't your job. RxMap handles it in one upload.
Drug utilization, formulary analysis, adherence studies — any work that starts with raw NDC data and needs normalized drug identifiers to move forward.
Working with NADAC, Medicaid reimbursement files, 340B pricing, or CMS Part D drug spending data? RxCUI is the join key between NDC-level claims and any drug cost reference. RxMap builds that bridge in one upload.
Formulary design, step therapy analysis, generic substitution reporting — all start with NDC codes from your claims system. RxMap converts them to analyzable drug identifiers so you can work in the tool you already use.
National Drug Code (NDC) identifiers pinpoint a specific product from a specific manufacturer in a specific package. That's great for tracking shipments. It's terrible for answering research questions.
When every NDC has an ingredient, a strength, and a dose form, these go from impossible to a five-minute pivot table.
Every manufacturer, every package size — one ingredient code. Group 400+ Metformin NDCs into a single count without maintaining a lookup table.
Join your NDC list to CMS NADAC (National Average Drug Acquisition Cost) or 340B ceiling prices using RxCUI as the bridge. Identify acquisition cost differences across generic manufacturers in seconds.
Link claims NDCs to a common drug identifier to calculate adherence across prescriptions, refills, and fill gaps — even across different manufacturers.
Map brand-name NDCs to their Semantic Clinical Drug (SCD), then cross-reference formulary tiers to surface generic substitution opportunities and quantify the savings potential.
MEPS, Medicare Part D, Medicaid SDUD, NHANES, and SEER-Medicare all include NDC codes. Upload your extract — RxMap adds the drug-level columns your analysis requires. No API access. No coding.
State PDMPs log every controlled substance dispensed by NDC. Map those NDCs to RxNorm ingredients and drug classes to identify opioids, benzodiazepines, and stimulants across your entire dataset at once.
Every dataset below ships with NDC codes as its drug identifier. RxMap converts those codes into analyzable drug data — no programming required.
Any file with an NDC column works — CSV, Excel, or TSV. The tool is data source agnostic.
From ingredient-level counts to brand-specific package lookups — each column answers a different research question.
The active pharmaceutical ingredient (e.g., Metformin). Aggregates across all formulations and manufacturers.
Use this to: Count all prescriptions for a drug regardless of manufacturer or package.
Specifies the exact salt or ester form (e.g., Metformin Hydrochloride).
Use this to: Use when the exact salt form matters for your study (e.g., distinguishing iron formulations).
Ingredient + strength + dose form, without brand. Best for generic-level analysis.
Use this to: Use as your primary analysis key for generic-level drug comparisons.
Generic pack with quantity information.
Use this to: Use for supply chain and dispensing volume analyses.
Brand-name drug with ingredient, strength, and dose form.
Use this to: Use for branded vs. generic substitution studies.
Branded pack with quantity. Aligns with specific product packages as sold by brands.
Use this to: Use to link to specific branded packages as dispensed.
Structured strength field from RxNorm RxTerms — machine-readable and consistent across products.
Use this to: Filter or stratify by dose. Compare 10 mg vs. 20 mg prescriptions.
Standardized dose form from RxNorm RxTerms.
Use this to: Filter to oral-only, injectables-only, or topicals across your entire dataset.
CSV, Excel, or TSV. Select the column containing NDC codes. We count the rows and show your exact price before you pay.
$0.01 per NDC code, $5.00 minimum. Secure card payment. Your file is processed immediately after confirmation.
Your original file as an Excel workbook — enriched with 8 new columns covering ingredient, strength, dose form, and branded and generic formulations. Open it directly in Excel, Stata, SAS, or R. Your analysis starts here.
No subscriptions. No accounts. Pay only when you convert.
$5.00 minimum per upload
Results available for 24 hours after processing. Do not upload identifiable patient data. Terms of Service
RxMap accepts CSV (.csv), Excel (.xlsx), and tab-separated values (.tsv). Your file must have column headers in the first row. Files can contain any number of additional columns — only the NDC column is required.
After uploading, you'll see a column selector that shows all detected columns. You choose which one contains NDC codes. RxMap will preview the first few values to help you confirm.
Only NDC codes are sent to the server — your original file is processed locally in your browser and is never uploaded. Results are available for 24 hours and then automatically deleted. We do not retain, sell, or use your data for any purpose other than returning your enriched results.
Not all NDC codes are in RxNorm (e.g., some OTC products, dietary supplements, or very old codes). Unmatched rows will have blank RxCUI columns in the output — your original data is always preserved.
Some NDCs — particularly combination products or repackaged drugs — map to more than one RxNorm concept. RxMap handles this by adding separate numbered columns for each result: SCD_1, SCD_2, etc. If every NDC in your file has only one match, the columns are not numbered.
Processing time depends on file size. Small files (< 100 NDCs) typically complete in under 30 seconds. Larger files may take a few minutes. The results page updates in real time.
Yes. MEPS (Medical Expenditure Panel Survey), Medicare Part D, Medicaid State Drug Utilization Data (SDUD), NHANES, and SEER-Medicare all include NDC codes. Export the relevant columns to a CSV or Excel file, upload it to RxMap, select the NDC column, and download the enriched result with RxCUI identifiers, drug names, Strength, and Dose Form — ready for your analysis in Stata, SAS, R, or Excel.
Yes — this is one of RxMap's primary use cases. Upload the NDC column from your claims extract (CSV or Excel), select it in the column picker, and download the enriched file with RxCUI, Ingredient, Semantic Clinical Drug, Strength, and Dose Form added to every row.
Yes. CMS publishes NADAC (National Average Drug Acquisition Cost) weekly with NDC codes as the primary key. Upload your NDC list, get RxCUI values back from RxMap, then use RxCUI as a common join key to NADAC or any RxNorm-referenced pricing file. The same approach works for Medicaid reimbursement rates, 340B ceiling prices, and CMS Part D drug spending data. RxCUI is the standard bridge identifier between NDC-level claims and drug cost reference databases.
RxNav (the NLM's web interface) looks up one NDC at a time. RxMap processes your entire file in bulk — hundreds or thousands of NDCs in a single upload. It also handles deduplication, multi-drug NDCs, and outputs a clean Excel file ready for analysis.
No. RxMap is an independent service that queries the publicly available NLM RxNorm REST API. We are not affiliated with NIH, FDA, or NLM.
RxMap is a bulk NDC-to-RxCUI crosswalk tool operated by Medication Data Science Inc. It was built to solve a practical problem: publicly available health datasets (MEPS, Medicare Part D, Medicaid SDUD, NHANES) use NDC codes as their drug identifier, but those codes are too manufacturer- and package-specific to support meaningful analysis without normalization.
RxMap queries the NIH National Library of Medicine RxNorm API for every NDC in your file and returns a clean Excel workbook with standardized RxNorm identifiers — no programming, no API access, no data team required.
RxMap is not affiliated with NIH, FDA, or NLM. It is an independent tool that uses the publicly available RxNorm REST API.
Drug data is sourced from RxNorm, maintained by the NIH National Library of Medicine as part of the Unified Medical Language System (UMLS). Drug class data (ATC, VA class) is sourced from the NLM RxClass API.