
Sauna reads the order and the payer's coverage criteria, assembles the clinical documentation that meets it, drafts the prior-auth request, and tracks every pending case so nothing stalls a patient's care.
What it does
Pulls the order, chart notes, and prior conservative-treatment history from Google Drive, drafts the prior-auth request, and checks each payer criterion off against documentation.
Keeps an Airtable board of every open authorization by patient, payer, status, and due date, and nudges you on cases approaching the appointment with no decision yet.
Flags requests where the documentation doesn't yet meet a coverage criterion and drafts the peer-to-peer talking points or the extra note to request from the provider.
Posts approval, denial, or pend status to Slack and drafts the patient message so scheduling and the clinician know where the auth stands.
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.
“We need prior auth for this MRI — check the payer's criteria, pull the conservative-treatment history from the chart, draft the request, and tell me what's still missing.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. It checks each coverage criterion against actual chart documentation and tells you which ones still lack support instead of papering over the gap.
No. It assembles and drafts the packet; you review and submit through the payer portal or fax.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring