canonical: https://jentic.com/apis/icd10api.com/icd10api # Icd10api IntelliLynx ICD-10 The IntelliLynx ICD-10 API suggests treatment plan steps for a diagnosed condition identified by its ICD-10 code. A single POST call takes the code as a query parameter and optional free-text notes in the body, and returns a plan array where each item carries a step and its notes. It is a narrow, single-purpose service meant to sit beside a clinical record system rather than replace one. ## For AI agents Send an ICD-10 code, with optional clinical notes, and get back a list of suggested treatment plan steps for that condition. ## Scope Does not look up or validate ICD-10 code descriptions, store patient records, or prescribe medication. Use for suggesting treatment plan steps from a known ICD-10 code only. ## Capabilities - Suggest treatment plan steps for a condition from its ICD-10 code - Pass free-text clinical notes alongside the code to give the suggestion more context - Return each plan item as a step with its own notes for display or review ## Use cases ### AI agent drafting care plans through Jentic A developer building a clinical documentation assistant wants their agent to draft a first-pass treatment outline once a diagnosis is coded. Through Jentic the agent searches for 'suggest a treatment plan for a diagnosis', loads the suggest_treatment operation with its input schema, and sends the ICD-10 code with any notes. The returned plan steps are shown to a clinician as a draft, not applied automatically. Example prompt: Call POST /suggest-treatment with code set to E11.9 and notes describing the patient's recent HbA1c result, then list each returned plan step for clinician review ### Care plan templates in an EHR add-on An electronic health record add-on offers clinicians a starting checklist when they enter a diagnosis code. The add-on calls the IntelliLynx ICD-10 suggestion endpoint with the code and renders the plan array as editable steps. Clinicians keep, edit, or discard each step before saving the plan to the chart. Example prompt: Send POST /suggest-treatment with code set to J45.909 and render each step from the plan array as an editable checklist item ### Coding education and review Training tools for medical coders and students show what a typical treatment outline looks like for a code they have just assigned. The tool sends the code to the IntelliLynx ICD-10 API and displays the suggested plan steps next to the code. Learners compare the outline with the case notes they were given. Example prompt: Call POST /suggest-treatment for code I10 and display the step and notes fields of each returned plan item beside the case ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/suggest-treatment` | Suggest treatment plan steps for an ICD-10 code | ## Key resources - **Treatment suggestions** — Suggest treatment plan steps for an ICD-10 code with optional notes ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 62 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 41 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/icd10api.com/icd10api/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the IntelliLynx ICD-10 API by hand means writing a client for its single POST operation, passing the code as a query parameter, and parsing the plan array yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it with no credential to manage. - **Permission scoping:** The spec exposes one operation, POST /suggest-treatment, with the ICD-10 code in the query string rather than the URL path, so rules bound which operations your agent may call, not which codes it sends. Allowing that one operation gives the agent exactly the suggestion call and no other route on the host. - **Credential handling:** The IntelliLynx ICD-10 spec declares no credential, so there is nothing to store, and your own Jentic One instance still routes the call outside the agent's prompt, logs, and context. - **Discovery method:** Agents search Jentic by intent such as 'suggest a treatment plan for a diagnosis' or 'treatment steps for an ICD-10 code', and Jentic returns the suggest_treatment operation with its input schema so the agent sends the code correctly. ## Related APIs - **Infermedica API** — Symptom assessment and triage that suggests likely conditions - **RxNorm API** — Normalized drug names and identifiers from the National Library of Medicine - **Cloud Healthcare API** — Stores clinical data in FHIR, HL7v2, and DICOM stores on Google Cloud ## FAQ ### What authentication does the IntelliLynx ICD-10 API use? The OpenAPI spec for the IntelliLynx ICD-10 API declares no security schemes, and the suggest-treatment operation is listed with no auth requirement. If the provider issues keys for production use, check with them directly, since the spec does not describe one. ### Can I get treatment suggestions for a diagnosis code with the IntelliLynx ICD-10 API? Yes. POST /suggest-treatment takes the ICD-10 code as the required code query parameter and an optional JSON body with a notes string. The response holds a plan array where each item has a step and notes. Treat the output as a draft for a clinician to review, since the spec makes no claim about clinical validation. ### What are the rate limits for the IntelliLynx ICD-10 API? The OpenAPI spec does not specify rate limits. Check the provider site at https://www.icd10api.com for current limits before sending a high volume of codes. ### Is there an IntelliLynx ICD-10 MCP server? You don't need an MCP server to give your agent the IntelliLynx ICD-10 API. Jentic connects it directly from the API Directory: import it and your agent calls the treatment suggestion operation when it needs it, discovered on demand without loading extra tool definitions into its context. ### Can I limit what my agent is allowed to do with the IntelliLynx ICD-10 API? Yes. Write a rule that allows only POST /suggest-treatment, the single operation in this spec, and the agent can request plan suggestions and nothing else through this binding. Every call it makes is logged, so you can review which codes it sent. ### How do I request a treatment plan through Jentic? Search Jentic for 'suggest a treatment plan for a diagnosis', load the suggest_treatment operation, and execute it with the code query parameter and an optional notes body. To run it on your own infrastructure, install Jentic One from its GitHub repo.