icd10-cm-skill
Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say "code this encounter", "assign ICD-10 codes", "what diagnosis codes apply", "code this chart", or when turning clinical documentation into claim-ready diagnosis codes. Published by anthropics in healthcare.
Decision snapshot
Is this a fit?
Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is icd10-cm-skill?
Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say "code this encounter", "assign ICD-10 codes", "what diagnosis codes apply", "code this chart", or when turning clinical documentation into claim-ready diagnosis codes. Published by anthropics in healthcare. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Declared skill metadata
- Source file: plugins/healthcare/skills/icd10-cm/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use icd10-cm-skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/healthcare
- Skill file: plugins/healthcare/skills/icd10-cm/SKILL.md
What it does
Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say "code this encounter", "assign ICD-10 codes", "what diagnosis codes apply", "code this chart", or when turning clinical documentation into claim-ready diagnosis codes.
Skill instructions
ICD-10-CM Coding from Clinical Notes Turn a clinical note into the diagnosis codes a professional coder would submit on the claim for that encounter. This happens in two distinct steps: first decide which conditions belong on the claim, then find the exact code for each. Both steps cause errors: coders miss claims by listing the wrong conditions, and by coding the right condition at the wrong specificity. Step 1: Decide what belongs on the claim A claim reflects the encounter, not the patient's chart. Per the ICD-10-CM Official Guidelines for outpatient coding: Code, in this order: 1. The reason for the visit (first-listed diagnosis). When the visit itself is for aftercare, screening, or follow-up, the Z-code IS the first-listed diagnosis — e.g. orthopedic aftercare/hardware removal (Z47.x), suture removal (Z48.02), a scheduled wellness exam (Z00.0x). 2. Conditions evaluated, managed, or treated at this visit — a medication refill or "stable, continue current plan" counts as managed. 3
Verified compatibility and discovery
Frequently asked questions
What is icd10-cm-skill?
icd10-cm-skill is a open-source AI agent skill with Copy skill directory. Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim.
Who is icd10-cm-skill best for?
icd10-cm-skill is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install icd10-cm-skill?
Install or run icd10-cm-skill using Copy skill directory. Check icd10-cm-skill for the latest setup command.
Is icd10-cm-skill actively maintained?
icd10-cm-skill may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.