# Coding and billing support

> Match a documented episode to the right billing code, and flag what the notes do not support.

- Skill: `vstorm-co/coding-and-billing-support` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/coding-and-billing-support`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/coding-and-billing-support/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/coding-and-billing-support

---


# Coding an episode

The rule that decides everything here: **the code follows the documentation, not
the other way round.**

## Work in this order

1. Read what was actually documented — the procedure performed, not the one
   booked.
2. Find the codes the documentation supports.
3. Where the notes are ambiguous, list the candidates and say what would
   disambiguate them.

## Flag rather than fill

If the notes do not support the code somebody expected, say which detail is
missing. "The record does not state laterality, which this code requires" is
useful; guessing the side is a compliance incident.

## Never

- Upcode because a higher code is plausible.
- Add a modifier the documentation does not evidence.
- Infer a comorbidity from a medication list.

## Always end with

The codes, the evidence line for each, and a short list of what a clinician
would need to add to support anything more. Every submission is signed off by a
person; this produces the draft, not the decision.