Eleplan Data API
ICD-10 codes, drugs, conditions, and benefits — Eleplan-curated from CMS, the NIH/NLM, and the FDA into one key, clean JSON, semantic search. Stop parsing government files; start shipping.
$0 to start · no card · live in 2 minutes
$ curl data.eleplan.com/v1/icd10/E11.9
{
"code": "E11.9",
"title": "Type 2 diabetes mellitus without complications",
"billable": true,
"chapter_range": "E00-E89",
"synonyms": ["Type 2 diabetes", "T2DM", "NIDDM"],
"risk_adjustment": {
"cms_hcc_v28": {
"hcc": "HCC38",
"label": "Diabetes with Glycemic, Unspecified, or No Complications",
"raf": 0.166
}
}
}Four datasets. One key. One bill.
98,000+codes
Semantic search, full hierarchy, billable flags, instructional notes, and CMS-HCC risk adjustment (RAF).
/v1/icd10/search
27,000+medications
Every strength + form, ATC + FDA class, FAERS safety signal, and a multi-drug interaction checker with risk scoring. Built on RxNorm + OpenFDA.
/v1/drugs/products/search
1,000+conditions
Plain-language references, grounded in MedlinePlus (NIH) and mapped to ICD-10.
/v1/conditions/search
2,800+programs
Federal + state assistance with structured eligibility and an "am I eligible?" engine.
/v1/benefits/search
Sourced from the authorities — cleaned, cross-walked, and kept current by Eleplan.
Every dataset starts from its canonical source, then we normalize the formats, resolve the cross-references (ICD-10 ↔ HCC, drug ↔ RxNorm, condition ↔ code), validate, and version it — so you ship against one clean, current shape instead of a dozen government file formats.
It’s the same data discipline behind Eleplan — the platform families and care teams use to manage serious, complex care. This API is its data layer.
See what Eleplan does →How it’s built
We didn’t scrape this. We built it.
Anyone can download a government CSV. The hard part — the part that makes it usable — is everything after. Built the way the commercial clinical databases are (First Databank, Medi-Span) — multi-source, normalized, cross-walked — but open, semantic, and free.
RxNorm drug identity, openFDA labels, RxClass therapeutic classes, 20M FAERS safety reports, CMS ICD-10 + risk adjustment — combined, not just cited.
Collapse salt forms to base ingredients on RxNorm identity — one clean record per drug, not 135k duplicate NDC stubs.
Drugs ⇄ ICD-10 indications, products ⇄ ingredient hubs, conditions ⇄ codes — the relationships that live in no single source.
Free-text label warnings become typed fields — a scored, pairwise drug-interaction graph built from narrative text.
Every record vectorized with pgvector, so you search by meaning — “what lowers blood sugar” → metformin.
Tracked sources, last-checked dates, scheduled rebuilds — and cross-walked mappings reconciled against a second, independent authority (NLM MED-RT / UMLS). Corroborated, not generated once and trusted.
That’s the difference between a data dump and a data product.
Built once isn’t enough.
The corpus audits itself.
Government data drifts — programs close, thresholds change, eligibility gets rewritten. So this doesn’t ship once and rot. Scheduled workers re-check every source against its authority, and an AI layer turns the eligibility prose no API could parse into fields you can filter.
Every source is re-pulled on a schedule — a weekly federal sweep, hourly rolling state shards — then reconciled against the upstream. A program that disappears from the authority retires itself, and every record carries the date it was last verified.
A model reads each program’s eligibility prose and extracts typed gates — age, income, condition — so “who qualifies” becomes a field you can filter, not a paragraph you parse. Conservative by design: it surfaces requirements, it never invents them.
Income eligibility is computed as a share of the official HHS Federal Poverty Level — pulled straight from the ASPE guidelines API and refreshed every year, no annual hand-edit — for the contiguous states, Alaska, and Hawaii.
Federal listings from SAM.gov, the USA.gov Benefit Finder model, and state assistance networks — fused, cross-walked to ICD-10, and corroborated against a second source before anything ships.
An eligibility layer that stays true to the agencies — without you watching the agencies.
Search 98,000+ codes in plain English.
Type a condition the way a person would. The API resolves it to the right ICD-10 code — with a featured best match and the full hierarchy behind it.
Live results from the ICD-10 dataset — every code links to its free public reference page. The production API returns the same JSON, authenticated by key.
Check drug interactions in one call.
Pass a medication list — get the interactions between them, a duplicate-therapy check, and a risk score, synthesized from FDA labeling. Powers /v1/drugs/interactions.
Comma-separate 2+ medications — generic or brand.
Explain a condition in one call.
Search a condition in plain language — get a clear summary, its ICD-10 codes, and the medications used for it, grounded in MedlinePlus (NIH). Powers /v1/conditions/search.
Live results from the Conditions dataset — plain-language summaries from MedlinePlus (NIH), each mapped to ICD-10 and the medications used for it. Every result links to its free public page.
Find assistance programs in one call.
Search federal & state assistance programs in plain language — get who qualifies, how to apply, and the conditions each one covers, cross-walked to ICD-10. Powers /v1/benefits/search.
Live results from the Benefits dataset — federal & state assistance programs with eligibility and how-to-apply, each mapped to ICD-10 and the conditions it covers. Every result links to its free public page.
Write, not just read.
Beyond the four read datasets, push your own notes and documents straight into a project — auto-OCR’d, parsed, and indexed alongside everything else. Powers POST /v1/ingest.
POST /v1/ingest
curl -X POST https://data.eleplan.com/v1/ingest \
-H "Authorization: Bearer elp_..." \
-H "Content-Type: application/json" \
-d '{
"project_id": 1234,
"items": [{ "title": "Visit summary", "body": "..." }],
"files": [{ "filename": "labs.pdf", "mime": "application/pdf",
"data_url": "data:application/pdf;base64,..." }]
}'Any clinical document, turned into structured data.
Send a PDF, scan, photo, or recording. We OCR it, summarize it, and extract the medications, events, and contacts inside — stored securely against your account. Powers POST /v1/documents.
POST /v1/documents
curl -X POST https://data.eleplan.com/v1/documents \
-H "Authorization: Bearer elp_..." \
-H "Content-Type: application/json" \
-d '{
"filename": "discharge.pdf",
"data_url": "data:application/pdf;base64,..."
}'
# → { "document_id": 8412, "status": "processing",
# "link": "https://eleplan.link/aB12xY" }126,000+ pages you
don’t have to build.
Every ICD-10 code, drug, condition, and assistance program has a public, human-readable reference page — fully indexed, always current, and free with every plan. Deep-link or embed ours.
The hard parts, already done.
Query in plain language — "type 2 diabetes", "knee pain" — and get the right code. pgvector under the hood, not keyword matching.
Verified data with last-checked dates. We track the source so you don’t parse government files yourself.
Clean, typed JSON with hierarchy, eligibility, and relationships — the parts that are hard to build, done.
A single API key spans every API — the four datasets, ingest, and document processing (OCR + clinical extraction). Scope it per API, with its own monthly limit.
Not just names. Every strength and form, ATC + FDA class, real-world FAERS safety signal, ICD-10 cross-walks, and a multi-drug interaction checker with risk scoring.
126,000+ ICD-10, drug, and condition pages — public, indexed, human-readable. Deep-link them or embed ours, free on every plan.
One request. Clean JSON.
Authenticate with a bearer token, hit an endpoint, get typed JSON. No SDK required — though they’re coming.
# One key, every dataset. Each returns { results, bestMatch }.
AUTH='-H "Authorization: Bearer elp_live_..."'
curl $AUTH "https://data.eleplan.com/v1/icd10/search?q=type+2+diabetes"
curl $AUTH "https://data.eleplan.com/v1/drugs/search?q=metformin"
curl $AUTH "https://data.eleplan.com/v1/conditions/search?q=type+2+diabetes"
curl $AUTH "https://data.eleplan.com/v1/benefits/search?q=food+assistance"Every parameter and field — across every API.
$ curl data.eleplan.com/v1/icd10/E11.9 \
-H "Authorization: Bearer elp_live_..."
{
"code": "E11.9",
"title": "Type 2 diabetes mellitus without complications",
"billable": true,
"risk_adjustment": { "cms_hcc_v28": { "hcc": "HCC38", "raf": 0.166 } },
…
}That’s one field group. The full reference covers every parameter and response field — across ICD-10, drugs, conditions, benefits, ingest, and the Documents API.
Full API reference — free with an API key →Every parameter and field across every API, in your dashboard.
5,165 healthcare icons — free.
One coherent, fully-accessible family across 21 clinical domains — symptoms, meds, vitals, labs, behavioral, cognitive, dementia, caregiving, RPM/CCM, AI signals, and more. Outline + filled, theme-colored SVG. Continuously AI-curated — recurring passes refine naming, categories, and search. Use them in any app, commercial or not.
Start free. Scale when you ship.
$0
For prototyping.
$19/mo
For reference data at scale.
$49/mo
For products in production.
Custom
For scale + SLAs.
The reference data behind modern health products — without the 50-state, multi-agency grind.
Get an API key