Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Code And Document The Visit

ASecurity

Pick the CMT/E&M code for a chiropractic visit and structure the medical-necessity note: CMT by number of spinal regions treated, an E&M only when separately identifiable (with the correct modifier), and a PART-exam-based note (region + functional goal + progress) that supports the code and survives an audit. Reach for it per visit / when coding is unclear. Used by `chiro-billing-compliance-specialist` (primary). Not a coding certification — verify payer policy.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentsgorailsdocumentation

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill code-and-document-the-visit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code And Document The Visit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Code And Document The Visit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-code-and-document-the-visit/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-code-and-document-the-visit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: code-and-document-the-visit
description: "Pick the CMT/E&M code for a chiropractic visit and structure the medical-necessity note: CMT by number of spinal regions treated, an E&M only when separately identifiable (with the correct modifier), and a PART-exam-based note (region + functional goal + progress) that supports the code and survives an audit. Reach for it per visit / when coding is unclear. Used by `chiro-billing-compliance-specialist` (primary). Not a coding certification — verify payer policy."
---

# Skill: code-and-document-the-visit

> **Invoked by:** `chiro-billing-compliance-specialist` (primary).
>
> **When to invoke:** coding a visit, or when CMT vs E&M / a modifier / necessity documentation is unclear.
>
> **Output:** a documentation-supported code path + a medical-necessity note structure. Payer-specific rules carry a retrieval date + `[verify-at-use]`.

## Procedure

1. **Place the visit first.** Traverse [`../../knowledge/billing-and-medical-necessity-decision-tree.md`](../../knowledge/billing-and-medical-necessity-decision-tree.md): acute/new complaint vs scheduled re-exam vs plateau/maintenance. Placement drives everything downstream.
2. **Count the spinal regions treated for the CMT code.** Spinal CMT is coded by regions (the 98940 / 98941 / 98942 family — 1-2 / 3-4 / 5 regions `[verify-at-use]`). The note must name the regions adjusted; code to what was documented, never up to a higher region count.
3. **Add an E&M only if it's separately identifiable.** A distinct, significant E&M service beyond the pre-adjustment assessment may be codeable with the appropriate modifier `[verify-at-use]` — most maintenance/established visits are not. Don't reflexively stack an E&M on every visit.
4. **Document medical necessity on the PART backbone.** Pain/tenderness, Asymmetry, Range-of-motion abnormality, Tissue/tone change — document the findings (commonly ≥2 `[verify-at-use]`) tied to the region coded, plus the functional goal and the progress since last visit. That triad — findings + goal + progress — is the necessity.
5. **Check the plateau.** If the patient has stopped improving toward the functional goal, care is likely supportive/maintenance → coverage changes → ABN + transition to cash (with the practice lead).
6. **Verify the payer's own policy.** Region definitions, modifier rules, documentation frequency, and covered-service definitions are payer- and state-specific and change — cite [`../../knowledge/chiro-payer-and-coding-reference-2026.md`](../../knowledge/chiro-payer-and-coding-reference-2026.md) with a date and flag anything needing a certified coder.

## Worked example

> Established patient, 3 regions adjusted (cervical, thoracic, lumbar), improving.

- Placement → active re-exam-window visit, still improving.
- CMT → 3 regions → 98941 `[verify-at-use]`; no separate E&M (routine follow-up).
- Necessity → PART: cervical tenderness + reduced ROM, lumbar asymmetry; goal: restore ROM; progress: +15° cervical rotation since last visit.
- Plateau check → still improving → active care continues; no ABN yet.

## Guardrails

- **Never up-code the region count or add an unsupported E&M** — the audit that closes practices.
- **If it isn't documented, it wasn't done** — the note is the claim.
- **Region/modifier/necessity rules are payer-specific** — verify, don't recall; certified-coder questions route out.

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →