Prepare a prior authorization request that gets approved first time
Matches the payer's coverage criteria to the documentation you have, finds gaps before submission, and drafts the request and peer-to-peer prep notes.
The prompt
Help me prepare a prior authorization request.
Payer and plan: [e.g. "Medicare Advantage HMO", "state Medicaid MCO"]
Service requested: [CPT/HCPCS code(s), drug name, imaging study, DME, or procedure]
Diagnosis codes as documented by the provider: [ICD-10]
Payer's coverage criteria: [PASTE the medical policy or criteria checklist]
Documentation we have: [SUMMARY - prior treatments tried and dates, test results, notes, as recorded by our clinicians]
Urgency: [standard / expedited - and the provider's stated reason if expedited]
Submission method: [portal, fax, electronic PA]
Do this:
1. Build a criteria crosswalk table: Payer criterion | Where it is met in our documentation (cite the note and date) | Status (met / partly met / missing).
2. List each gap and what document or information would close it. Do not suggest altering or adding clinical facts; only point to what may already exist in the chart or needs the provider's input.
3. Draft a concise letter of medical necessity summary for the provider to review and sign, using only the facts I gave you, with [PROVIDER TO CONFIRM] where needed.
4. Give a submission checklist: correct codes, NPI and tax ID, site of service, units, dates, and attachments.
5. Draft talking points for a peer-to-peer review in case of denial, organized by criterion.
6. Note expected decision timelines to [CONFIRM] with the payer and when to follow up.
The clinical justification must come from the treating provider; this prompt only organizes the documentation.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- e.g. "Medicare Advantage HMO", "state Medicaid MCO"
- ICD-10
- PASTE the medical policy or criteria checklist
- portal, fax, electronic PA
- PROVIDER TO CONFIRM
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Run a health check on my project and find what is going wrongScores your project across scope, schedule, budget, risk, team, and stakeholders, and pinpoints the real problems behind the noise.
- Audit my project plan for missing owners, deadlines, and unaddressed risksChecks your plan or tracker for tasks with no owner, no deadline, vague deliverables, and risks nobody is managing.
- Turn a problem into an action plan with clear success measuresA structured plan to solve a work problem: steps, owners, dates, checkpoints, and the evidence that will show it is really solved.