clinical-note-extract
Extract structured data from clinical notes with span-level provenance and null-safety. Use when users say "extract [variables]…
Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say "code this encounter for procedures", "what CPT codes apply", "assign HCPCS codes", "code this op note", or when turning visit notes or
$ npx -y skills add anthropics/healthcare --skill procedure-coding --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/procedure-codingContext preview
The summary Claude sees to decide when to auto-load this skill.
Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say "code this encounter for procedures", "what CPT codes apply", "assign HCPCS codes", "code this op note", or when turning visit notes or
name: procedure-coding description: Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say "code this encounter for procedures", "what CPT codes apply", "assign HCPCS codes", "code this op note", or when turning visit notes or operative reports into claim-ready procedure codes.
Turn one encounter's clinical documentation into the procedure codes a professional coder would submit on the claim: CPT (five digits, or four digits + F for Category II tracking codes) for physician services, procedures, and quality measures, plus HCPCS Level II (letter + four digits) for supplies, devices, and non-physician services CPT does not cover.
Read the documentation and list each distinct billable service performed at this encounter. Work by category:
Leave off the list: services planned but not performed, results referenced from a prior date, and items already bundled into a procedure's global package.
HCPCS Level II codes (one letter + four digits) cover items CPT does not. Check the documentation for these specifically:
**Do not output quality-reporting G-codes (G8-/G9- range) or non-covered-item codes.** These report participation in a quality program or a coverage determination; whether they belong on the claim depends on the practice's program enrollment and the payer, not on the clinical documentation. A data point appearing in the note (BMI in vitals, medication list reviewed, tobacco status in social history) is not by itself a reason to report the corresponding quality code.
Category II tracking codes are reported when the encounter is part of a quality-reporting workflow, not whenever the data point happens to appear in routine vitals or history. Output a ####F code only when the note shows the measure was deliberately captured for reporting: a quality-measure or health-maintenance section, measure-specific attestation language, or a structured screening result.
For every item on your abstracted list, search before you commit.
**HCPCS Level II (letter + four digits):** use `search_codes` for the supply, device, drug, or service name, passing the encounter date as `as_of`. Confirm with `validate_code` and the same `as_of`.
**CPT (five-digit and ####F):** if a CPT lookup connector is available (`cpt_search_codes`), use it with the service in plain words taken from the note and confirm with `cpt_lookup_code`. If no CPT connector is available, propose CPT codes from your knowledge of the current code set and state that they are pending verification again
One plugin for healthcare work: skills for payer, provider, pharma, and general engineering, with hosted MCP servers connected. Skills only load when relevant, so the bundle stays cheap.
Extract structured data from clinical notes with span-level provenance and null-safety. Use when users say "extract [variables]…
Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial…
Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says,…
Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document…
FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation,…
Connect to a hospital's FHIR R4 server (Epic, Oracle Health/Cerner, MEDITECH, athenahealth, or any SMART-on-FHIR endpoint), pull…