ICD-10-CM Clinical Coding Assistant
Convert clinical notes into verified, billable ICD-10-CM diagnoses.
The skill restricts lookup to the ICD-10 connector and explicitly stops when it is unavailable instead of coding from memory. It requests no shell or self-directed network access, so permissions and data flow are partly visible. Points are deducted because sensitive clinical-data handling, user confirmation, result review, recovery, and rollback are not specified, and the license is unknown.
The three-step workflow, stop condition, and some failure feedback are clear, and the main path is mostly self-consistent. Points are deducted because there are no skill-level tests or execution evidence, connector availability is not verified by the supplied files, and preserving dots conflicts with the final-check instruction to remove dots.
Trigger phrases, input types, outpatient scope, and non-fit areas are reasonably explicit, and the skill states that it does not replace certified coder review. Points are deducted because Chinese-language support is not described and the core function depends on an external ICD-10 connector whose reachability from mainland China is unverified.
The documentation covers purpose, workflow, connector dependency, scope limits, and output format with a readable structure. Points are deducted because versioning, changelog, maintenance ownership, and update path are unclear, while license information is unknown or reduced to broad service terms.
The intended output is a short diagnosis-code list usable in a claims workflow, with explicit emphasis on documented specificity and current-code lookup. Points are deducted because static review cannot verify actual outputs, the dot-format rule is contradictory, specialty coverage is limited, and certified coder review remains necessary.
The supplied skill and README provide auditable workflow, tool names, and limitations, while repository CI files offer governance context. Points are deducted because no key-path test suite, real execution result, or independent corroboration is provided, limiting verifiability to static evidence.
- Static files do not establish that the connector is available, codes are correct, or output formatting is consistent.
- Clinical notes may contain sensitive health information; confirm data handling, access controls, and provider compliance boundaries before use.
- The README claims validation but supplies no reproducible, skill-specific test evidence.
- Resolve whether ICD-10 dots must be preserved or removed in the final output.
- Reachability of the core connector service from mainland-China networks is unspecified and may affect usability.
What it does & when to use it
This skill extracts billable ICD-10-CM diagnosis codes that belong on an outpatient claim for the documented encounter. It first determines which conditions were relevant to the visit, then selects one complete code for each diagnosis at the specificity supported by the note. It avoids inferring severity, subtype, laterality, chronicity, or complications that the clinician did not document. Each code must be searched and validated through the ICD-10 Codes connector, making the skill suited to claim-oriented coding workflows that require a current code set.
Reads a clinical note and its assessment; separates the first-listed diagnosis, conditions evaluated or managed during the visit, and information that should remain off the claim; searches the ICD-10 Codes connector with search_codes; confirms codes with lookup_code or validate_code; and returns complete billable ICD-10-CM codes labeled First-listed and Secondary.
- A professional coder needs to assign first-listed and secondary diagnoses from an outpatient clinical note.
- A claims team needs to check whether documented diagnoses support billable ICD-10-CM specificity.
- A clinical operations user wants to turn a request such as “code this encounter” into claim-ready diagnosis codes.
- An auditor needs to prevent suspected diagnoses, untreated history, or clinician-unlinked complications from being added to an outpatient claim.
Pros & cons
- Provides a clear encounter-focused method for selecting diagnoses.
- Uses documented specificity and defaults to unspecified codes when the note is undetailed.
- Requires connector-based search and validation for every code.
- Defines an output format that distinguishes the first-listed diagnosis from secondary diagnoses.
- Depends on the ICD-10 Codes connector and does not produce codes when that connector is unavailable.
- The source provides no test-suite, platform-coverage, or accuracy results.
- The scope is ICD-10-CM diagnosis coding, not CPT or HCPCS procedure coding.
- The README describes the broader healthcare collection; sibling-skill capabilities should not be attributed to this skill.
How to install
This skill is included in the anthropics/healthcare collection. The README documents: /plugin marketplace add anthropics/healthcare and /plugin install healthcare@healthcare. The source does not document a separate installation procedure for the icd10-cm skill.
How to use
Install the collection, enable the ICD-10 Codes connector, provide the clinical note, and use a request such as “Code this encounter” or “Assign ICD-10 codes from this clinical note.” If the connector is unavailable, the skill should stop and request that it be installed or enabled rather than producing codes from memory.