🏥 ICD-10-CM, LOINC & Clinical Terminology Scraper (NLM)

🚀 Export billable clinical codes in seconds. Query the official NLM Clinical Tables API for ICD-10-CM diagnoses, LOINC lab observations, RxTerms drugs, disease names, conditions, and procedures. No API key, no UMLS download, no parser headaches.

The ICD-10-CM, LOINC & Clinical Terminology Scraper queries the National Library of Medicine's Clinical Tables Search Service and returns standardized US clinical codes as flat rows. Six tables are supported in one Actor: ICD-10-CM (billable US diagnosis codes), LOINC (laboratory and clinical observations), RxTerms (drug names with dose, strength, route), disease_names (curated disease dictionary), conditions (common patient-reported conditions), and procedures (common medical procedures with ICD-9 codes).

Each table returns its own purpose-built schema while sharing a common table and scrapedAt envelope, so consumers can union the output or filter to a single vocabulary. Coverage is tens of thousands of rows per table, totaling well over 100,000 standardized clinical codes across the six tables. The Clinical Tables API is the same backend that powers the NLM autocomplete widgets used inside FHIR pickers and EHR build-out tools.

🎯 Target Audience	💡 Primary Use Cases
Health-tech teams, EHR integrators, billing & RCM vendors, clinical-decision-support builders, public-health researchers, FHIR app developers	Diagnosis-code autocomplete, lab-code lookup, RxTerms-to-RxNorm bridge, disease-name normalization, procedure code translation, FHIR ValueSet builds

📋 What the Clinical Terminology Scraper does

Six lookup workflows in one Actor:

• 🏥 ICD-10-CM. Billable US diagnosis codes (A00.0 → Z99.x).
• 🧪 LOINC. Laboratory and clinical observation codes with property, system, scale type, method, and class.
• 💊 RxTerms. Drug display name plus strength and form, joined to RxCUIs.
• 🩺 disease_names. Curated disease dictionary with consumer-friendly names and synonyms.
• 🤒 conditions. Common patient-reported conditions.
• 🩻 procedures. Common medical procedures keyed to ICD-9 procedure codes.

Each row carries the table name, the run timestamp, and the table-specific columns (e.g. code + description for ICD-10-CM, code + longName + component + system + class for LOINC, name + strengthAndForm + rxcui for RxTerms).

💡 Why it matters: clinical-code vocabularies live behind UMLS licensing, monthly release dumps, and ad-hoc autocomplete widgets. This Actor flattens all six into one API surface and one Apify dataset, ready for FHIR, billing, or analytics work.

📊 Data fields

Each record includes: code, description, scrapedAt, table. All 4 field names come from a real production run, so what you see here is what lands in your dataset.

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🌐 Open the Actor. Go to the ICD-10-CM, LOINC & Clinical Terminology Scraper page on the Apify Store.
3. 🎯 Pick a table. Choose one of the six tables and supply an optional search term.
4. 🚀 Run it. Click Start and let the Actor walk the NLM API.
5. 📥 Download. Grab results in the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to a billable code export: 3-5 minutes. No coding required.

🔗 Recommended Actors

• 💊 RxNorm Drug Concepts Scraper - Standardized US drug vocabulary
• 🧬 UniProt Protein Scraper - Protein knowledgebase entries
• 🤗 Hugging Face Model Scraper - AI model registry metadata
• 🛡️ urlscan.io Threat Intelligence Scraper - Live web scan data
• 🌐 RDAP Domain Lookup Scraper - Modern WHOIS replacement

💡 Pro Tip: browse the complete ParseForge collection for more reference-data scrapers.

⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the U.S. National Library of Medicine, the National Institutes of Health, the World Health Organization, the Regenstrief Institute, or any government agency. All trademarks mentioned are the property of their respective owners. Only publicly available NLM Clinical Tables data is collected.

🆘 Need Help?

If you hit a bug, have questions about setup, or need a scraper we haven't built yet, open our contact form or write to parseforge@protonmail.com. We also take on paid custom data projects.

For faster answers, join our Discord. It's the best place to get support and suggest new actors.