procedure-coding

작성자: anthropic

임상 문서에서 CPT 및 HCPCS Level II 시술 코드를 전문 코더가 청구서를 작성하는 방식으로 할당합니다. 사용자가 "이것을 코딩해 주세요..."라고 말할 때 사용하세요.

npx skills add https://github.com/anthropics/healthcare --skill procedure-coding

Procedure Coding from Encounter Documentation

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.

Step 1 — Abstract every billable service from the note

Read the documentation and list each distinct billable service performed at this encounter. Work by category:

  • Evaluation and management — the visit itself: office, emergency, observation, inpatient, consultation. One E/M code per encounter unless a separately identifiable service is documented. When the visit is for ongoing management of a single serious or complex chronic condition, the complexity add-on may apply alongside the office E/M code.
  • Ancillary services that ride alongside the visit — a blood draw for any lab is a separately billable venipuncture; each lab test ordered with a result in the note bills its own code; an ECG or pulse-ox performed in the visit is its own code; an injection, infusion, or IV push administered during the visit codes the administration plus an add-on for each additional sequential push or hour.
  • Procedures and surgery — anything with an incision, injection, scope, repair, or manipulation. Abstract from the procedure note, not the plan.
  • Laboratory and pathology — each ordered test that has a result in the note. Panels (CBC, BMP, CMP) bill as the panel code, not the components.
  • Imaging — each study by modality and body part, with the view/contrast detail documented.
  • Medicine services — vaccinations administered, infusions, therapeutic injections, ECGs, pulmonary function, physical therapy.

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 — what to look for and what to leave off

HCPCS Level II codes (one letter + four digits) cover items CPT does not. Check the documentation for these specifically:

  • Hospital observation hours — when the note shows the patient was placed in or remained in observation status, code the per-hour observation service (and the direct-referral code when the patient was placed in observation without a preceding ED visit).
  • Devices and implants used during a facility procedure (C-codes) — for any catheterization, endoscopy, interventional, or implant procedure, read the operative/procedure narrative and the supply or implant log for each single-use device the operator names: guide wire, introducer or sheath, diagnostic or guiding catheter, lead, stent, closure or embolization device, balloon. Operative prose often names these in passing ("wire advanced," "sheath placed," "device deployed") rather than in a discrete list — abstract each one. Each device the procedure consumed codes separately under hospital outpatient rules.
  • Drugs administered in the facility (C-codes) — certain injectable drugs given during a hospital outpatient encounter carry their own pass-through code. Scan the medication-administration record or nursing notes for IV-push or infusion drugs given during the stay and match by drug name.
  • Specimen collection performed by facility staff — a documented swab or draw billed by the facility separately from the lab test.
  • Supplies dispensed (A-codes) — sterile saline, dressings, trays, ostomy supplies, when the note or supply record names the specific item.
  • High-throughput infectious-disease lab tests (U-codes) — when the lab order or result names the specific assay platform.
  • Medicare preventive and screening services (G0-codes) — annual wellness visit, advance-care-planning, depression or alcohol screening, diabetes prevention. Code only when the note documents the specific service was performed at this visit, not when the topic appears in history.

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.

CPT Category II (####F) — same rule as quality G-codes

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.

Step 2 — Find each code with the lookup tools

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 against the user's licensed CPT reference — CPT descriptors are AMA-licensed and not bundled with this skill.

One or two searches per item is sufficient. If the right code is not in the first results, refine the query once with more specific wording from the note; then commit or move on. Do not loop on the same item.

Step 3 — Output

After tool calls, output only the codes that belong on the claim, one per line, no other text. List each code once. Do not output J#### or Q#### codes. If a service you abstracted has no matching code in the lookup results and you cannot confidently propose one, omit it rather than guessing.

anthropic의 다른 스킬

access
anthropic
Discord 채널 접근을 관리합니다 — 페어링 승인, 허용 목록 편집, DM/그룹 정책 설정. 사용자가 페어링 요청, 승인, 허용된 사람 확인 등을 요청할 때 사용합니다.
official
session-report
anthropic
~/.claude/projects 트랜스크립트에서 Claude Code 세션 사용량(토큰, 캐시, 하위 에이전트, 스킬, 고비용 프롬프트)에 대한 탐색 가능한 HTML 보고서를 생성합니다.
official
build-mcp-server
anthropic
이 스킬은 사용자가 "MCP 서버 구축", "MCP 생성", "MCP 통합 만들기", "Claude용 API 래핑", "도구 노출" 등을 요청할 때 사용해야 합니다.
official
cookbook-audit
anthropic
Anthropic Cookbook 노트북을 루브릭에 따라 감사합니다. 노트북 리뷰나 감사가 요청될 때마다 사용하세요.
official
handle-complaint
anthropic
들어오는 고객 불만을 처음부터 끝까지 처리합니다 — 맥락을 파악하고, 응답을 작성하며, 운영상의 수정을 제안합니다. 선택적으로 이메일이나 티켓 ID를 받습니다…
official
use-case-triage
anthropic
처리 활동이 PIA, 필수 GDPR DPIA가 필요한지 또는 진행 가능한지 신속히 판단하여 개인정보 처리방침 충돌을 표시하고 적절한 경로로 안내합니다…
official
board-minutes
anthropic
이사회 또는 위원회 회의록을 사내 형식으로 작성합니다. 캘린더에서 예정된 이사회 및 위원회 회의를 자동으로 감지하고, 안건을 요청한 후…
official
renewal-tracker
anthropic
유지 관리되는 갱신 등록부를 기반으로 취소 마감일이 다가오는 계약을 표시하고 통지 기간이 종료되기 전에 경고합니다. 사용자가 요청할 때 사용합니다.
official