Integration

ICD-11 API integration

The ICD-API, hosted by the World Health Organization, gives read access to the International Classification of Diseases: search ICD-11 by text and get the best matching code, read any entity of the ICD-11 MMS classification, of the ICF or of the ICD-11 Foundation (titles, definitions, inclusions, exclusions, parents and children) in many languages, follow a code across releases, decode postcoordinated code combinations, read ICD-10 categories, and run the DORIS death certificate checks. Classification content only, no patient records, except the death certificate data a DORIS call sends. The POST forms of the two searches (the same inputs, for long queries) and of DORIS and CodEdit (a whole certificate in WHO's standard format, whose schema the reference does not publish) are not exposed. Authentication is OAuth 2.0 client credentials: register on the ICD-API site and copy the client id and client secret from View API access key.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ICD-11 API.Built from the 21 ICD-11 API tools below, on the connection you add once.

What you can do with ICD-11 API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Code, 3 operations

  • autocode_linearizationAutocode linearizationGETAgents: ask firstReturns the single best matching code of an ICD-11 release (mms) for a short text: the code (theCode), its linearization and foundation URIs, the matched text, a score from 0 to 1 and the match level.
  • describe_codeDescribe codeGETAgents: ask firstDescribes an ICD-11 code, URI or postcoordinated combination: full code, label, linearization and foundation URIs, the stem and each postcoordination axis with its values. With simplify=true, a combination is reduced to one code where possible.
  • get_code_infoGet code infoGETAgents: ask firstLooks up an ICD-11 code or a postcoordinated code combination (stem code with extension codes joined by & or /) in a release: its stem code and id, a simplified form if any, and the value given on each postcoordination axis.

Foundation entity, 3 operations

  • autocode_foundationAutocode foundationGETAgents: ask firstReturns the single best matching ICD-11 Foundation entity for a short text (a diagnosis phrase): the matched text, its foundation URI, a match score from 0 to 1 and the match level.
  • get_foundation_entityGet foundation entityGETAgents: ask firstReturns one ICD-11 Foundation entity by its numeric id: title, definitions, synonyms, narrower terms, inclusions, exclusions and the URIs of its parents and children. The Foundation has no codes; use get_linearization_entity for those.
  • search_foundationSearch foundationGETAgents: ask firstSearches the ICD-11 Foundation by text and returns the matching entities (URI, title, score, matching property values). Add % at the end of a word for a prefix match. The Foundation has no codes; search_linearization returns codes.

Linearization entity, 3 operations

  • get_linearization_entityGet linearization entityGETAgents: ask firstReturns one entity of an ICD-11 release (mms or icf) by numeric id: code, title, definitions, coding notes, inclusions, exclusions, index terms, postcoordination axes, class kind and parent and child URIs.
  • lookup_foundation_entityLookup foundation entityGETAgents: ask firstMaps a Foundation entity to the given ICD-11 release and linearization: returns the linearization entity it falls into (the entity itself or the one it is aggregated into), with code, title and the other entity fields.
  • search_linearizationSearch linearizationGETAgents: ask firstSearches an ICD-11 release (mms) by text and returns matching coded entities: code (theCode), URI, title, chapter, score and the matching terms. Add % at the end of a word for a prefix match. Set highlightingEnabled=false for plain titles.

Icd10 release, 2 operations

  • get_icd10_releaseGet icd10 releaseGETAgents: ask firstReturns the root of one ICD-10 release: title, release id and date and the URIs of its chapters. ICD-10 has no search in this API.
  • list_icd10_releasesList icd10 releasesGETAgents: ask firstLists the ICD-10 releases the API serves (2019, 2016, 2010, 2008): the classification title, the latest release and the URI of each release.

Death certificate, 1 operation

  • check_death_certificateCheck death certificateGETAgents: ask firstChecks a coded death certificate for completeness and inconsistencies (WHO CodEdit) and returns a text report, a tabular report and the ids of the issues found. Sends the certificate data, which is health data, to WHO.

Entity release, 1 operation

  • list_entity_releasesList entity releasesGETAgents: ask firstLists the URIs of one linearization entity in every release that contains it, with the latest release, so a code can be followed across releases.

Foundation, 1 operation

  • get_foundationGet foundationGETAgents: ask firstReturns the root of the ICD-11 Foundation for the latest or a given release: its title, release id and date, the URIs of the top-level entities, the available languages, linearizations and all releases.

Icd10 category, 1 operation

  • get_icd10_categoryGet icd10 categoryGETAgents: ask firstReturns one ICD-10 category (or block or chapter) of a release: code, title, definitions, notes, coding hints, inclusions, exclusions, index terms, class kind and parent and child URIs.

Icd10 category release, 1 operation

  • list_icd10_category_releasesList icd10 category releasesGETAgents: ask firstLists the ICD-10 releases that contain a category code (or a block code range), with the latest one and the URI of the category in each.

Linearization, 1 operation

  • get_linearizationGet linearizationGETAgents: ask firstReturns the root of one release of an ICD-11 linearization (mms or icf): title, release id and date, the URIs of the chapters and the available and pre-release languages.

Linearization release, 1 operation

  • list_linearization_releasesList linearization releasesGETAgents: ask firstLists the releases available for an ICD-11 linearization (mms or icf): its title, the latest release and the URI of each release.

Residual entity, 1 operation

  • get_residual_entityGet residual entityGETAgents: ask firstReturns a residual category (other specified or unspecified) of an ICD-11 linearization entity, with the same fields as get_linearization_entity (code, title, notes, inclusions, exclusions, parents).

Residual entity release, 1 operation

  • list_residual_entity_releasesList residual entity releasesGETAgents: ask firstLists the URIs of one residual category (other or unspecified) of a linearization entity in every release that contains it, with the latest release.

Underlying cause of death, 1 operation

  • compute_underlying_cause_of_deathCompute underlying cause of deathGETAgents: ask firstSelects the underlying cause of death from a coded death certificate with the WHO DORIS mortality rules: returns its code and URI, the stem, reports, and any rejection, error or warning. Sends the certificate data (health data) to WHO.

Use ICD-11 API from Claude Code, Cursor or Codex

Connect ICD-11 API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ICD-11 API operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ICD-11 API

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect ICD-11 API once

    Add your ICD-11 API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

ICD-11 API integration FAQ

What can you do with the ICD-11 API integration?

LiveContext exposes 21 operations on ICD-11 API, covering code, foundation entity, linearization entity and icd10 release.

Popular integrations

Browse the whole catalog