Who are the users of the agents
- Clinicians documenting diagnoses and symptoms
- Medical coders working coding queues
- Chart reviewers auditing existing diagnosis codes
- Researchers normalising free-text clinical conditions
- Developers integrating ICD-11 lookup into clinical workflows, EHRs, portals, or downstream AI systems
What does the agent do
The agent helps users retrieve candidate ICD-11 codes for diagnoses, conditions, and symptoms described in free text. It searches the WHO ICD-11 medical coding API through the ICD11 Medical Coding component, then explains the returned candidates in plain language.
The agent:
- Looks up candidate ICD-11 codes from the ICD-11 API
- Presents official code titles, chapters, definitions, and browser URLs when available
- Explains why a candidate may or may not fit the user’s diagnosis phrase
- Surfaces ambiguity between close matches instead of silently choosing one
- Asks focused clarifying questions when the diagnosis phrase is too broad or clinically underspecified
- Handles compound diagnoses by searching distinct clinical concepts separately when needed
- Supports symptom-level coding when no definitive diagnosis has been established
- Can be extended with structured output for downstream automation
The agent does not diagnose, prescribe, validate billing rules, or make final coding decisions. Returned codes are candidates for review by a trained coder or clinician.
What are needed to setup the agent
Required components and knowledge sources:
- ICD11 Medical Coding component
How can you setup and customise the agent
Step 1 – Open the starter template
- Start from ICD-11 Diagnosis Coding Assistant in the starter templates.
Step 2 – Review the ICD-11 tool configuration
- The ICD11 Medical Coding node is connected to the Agent as a tool.
- The default mode is strict.
- The default language is English.
- The default number of returned candidates is 5.
Step 3 – Customise for your workflow
- Change the Language dropdown if you want WHO titles, definitions, and synonyms returned in another supported language.
- Adjust top_results if your use case needs fewer or more candidate matches.
- Switch from strict to flexible mode if users commonly paste raw chart-note language instead of clean diagnosis phrases.
- Add a Structured Output component after the Agent if a downstream EHR, coding queue, API, or analytics pipeline needs a fixed JSON schema.
Expected Outputs
- The user enters a diagnosis, condition, symptom, or coding question.
- The agent searches the WHO ICD-11 API through the ICD11 Medical Coding tool.
- The agent returns candidate ICD-11 codes with plain-language explanation and a review note.
- If the case is ambiguous, the agent presents the relevant candidates and asks one focused clarifying question.
- If no relevant ICD-11 entry is returned, the agent says so instead of guessing a code.
Structured Coding Summary
Includes:
- User diagnosis phrase or clinical concept
- Candidate ICD-11 code
- Official ICD-11 title
- ICD-11 chapter
- One-line definition
- Relevant inclusions or exclusions
- Match rationale
- Ambiguity or missing detail, when applicable
- WHO browser URL, when available
- Reminder that the result is a candidate for review, not a final coding decision