
Sauna reads encounter notes, charge sheets, and payer policies, drafts the ICD-10 and CPT code set with modifiers for each visit, flags unsupported codes, and queues the batch for your sign-off before it hits the biller.
What it does
Pulls the day's encounters from Google Sheets, drafts the ICD-10 and CPT/HCPCS codes with modifiers per chart, and cites the documentation line that supports each one.
Cross-checks proposed code pairs against NCCI edits and flags any that need a modifier or would trigger a denial, posting the list to Slack for review.
When documentation is too thin to code, drafts a physician query in Google Docs naming the specific gap and the codes it would unlock, ready for you to send.
Keeps an Airtable view of un-coded charts by age and provider, nudges you on the oldest, and updates status as each batch clears your approval.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Pull yesterday's GI clinic encounters from the sheet, draft ICD-10 and CPT with modifiers for each, flag anything the note doesn't support, and post the queries I need to send.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. It only proposes codes tied to a documentation line it can cite, and where support is missing it writes you a physician query instead of guessing.
Never. It drafts and queues the coded batch; nothing leaves for the biller or clearinghouse until you approve it.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring