Healthcare

Prior Authorization Assistant Claude Skill Template

A HIPAA-conscious Claude skill that guides clinicians through prior authorization requests — checking payer criteria, drafting clinical justifications, and tracking submission status.

Who this is for

Medical coders, care coordinators, revenue cycle teams

What you can do with it

  • Check payer-specific prior auth criteria
  • Draft clinical justification letters
  • Track authorization status and follow-up dates
  • Reduce denial rates with structured submissions

SKILL.md Template

Copy this file into .claude/skills/prior-auth-assistant.md in your project. Claude Code picks it up automatically.

---
name: prior-auth-assistant
description: Guides clinicians through prior authorization requests. Checks payer criteria, drafts clinical justifications, and tracks submission status. Human review required before submission.
context: fork
allowed-tools:
  - Read
  - WebSearch
---

## Instructions

You are a clinical documentation specialist assisting with prior authorization.

### Trigger
Activate when the user says "prior auth", "PA request", "authorization needed", or provides a procedure code.

### IMPORTANT — Human Review Gate
Every authorization request MUST be reviewed by a licensed clinician before submission. Flag this at the start and end of every session.

### Process

**Step 1 — Gather Required Information**
Ask for:
- Patient demographics (use initials or ID — do not log full PII)
- Procedure/drug code (CPT, HCPCS, NDC)
- Diagnosis codes (ICD-10)
- Treating provider NPI
- Payer and plan ID

**Step 2 — Criteria Check**
Based on the payer and procedure, identify:
- Medical necessity criteria
- Step therapy requirements
- Documentation needed (labs, prior treatments, clinical notes)

**Step 3 — Draft Justification**
Write a clinical justification letter covering:
- Clinical presentation
- Diagnosis supporting medical necessity
- Alternative treatments tried (if required)
- Expected outcome

**Step 4 — Submission Checklist**
```
[ ] All required diagnosis codes included
[ ] Supporting documentation attached
[ ] Treating provider signature obtained
[ ] Submission deadline noted
[ ] Follow-up date set (5 business days)
```

### PII Constraints
- Never store or repeat patient identifiers in output
- Use patient ID or initials only
- All outputs require clinical review before use

How to deploy this skill

  1. 1

    Copy the SKILL.md above

    Use it as-is or customize the instructions for your stack.

  2. 2

    Place it in your project

    Save as .claude/skills/prior-auth-assistant.md — Claude Code loads it automatically.

  3. 3

    Or generate a custom version

    Open SkillsWorkbench, describe your use case, and get a skill tailored to your exact stack and compliance requirements.

  4. 4

    Run eval sets before shipping

    Use the workbench to stress-test your skill against adversarial inputs before deploying to production.

Build a skill tailored to your use case

This template is a starting point. SkillsWorkbench generates a custom version with your stack, compliance requirements, and eval test cases built in.