Prompt library · Healthcare

Prompts for Medical Coders

Five copy-paste prompts written for actual day-to-day work. Each names the recommended tool and the expected output shape.

SOAP note from raw vitals and complaint

Recommended tool · Claude · Intermediate
You are assisting a medical coder. From the raw notes below, draft a SOAP note in the format I use: subjective (chief complaint and HPI in 2 sentences), objective (vitals and exam findings in bullets), assessment (differentials ranked by likelihood with 1-line reasoning each), plan (next steps and follow-up). Do not invent values. If a field is missing, say MISSING. Notes:

[paste raw notes here]
Expected output shape

A SOAP-formatted block ready for chart entry, with MISSING flagged where data is absent.

Explain a procedure or diagnosis to a layperson

Recommended tool · ChatGPT · Beginner
Explain [procedure or diagnosis] to a patient with a high-school reading level. Cover: what it is in one sentence, why it's relevant to their situation, what they should expect (3 short bullets), one common myth to dispel, and one clear question to ask their medical coder at the next visit. Keep tone warm but factual. Avoid jargon you don't immediately define.
Expected output shape

A patient-facing explainer in plain language, ~250 words.

Drug-interaction or treatment lookup

Recommended tool · Perplexity · Advanced
I am a medical coder considering [treatment / medication] for a patient with [condition / current meds]. Pull together: known interactions ranked by clinical significance, contraindications I should verify, monitoring parameters, and three patient-counseling points. End with the authoritative sources I should verify against before I act on this. This is for clinical lookup support — every claim must be verifiable.
Expected output shape

A clinical-lookup brief with explicit source citations to verify.

Discharge or after-visit instructions

Recommended tool · Claude · Beginner
Draft after-visit instructions a medical coder can hand to a patient. Context: [diagnosis or procedure]. Cover: what was done, what to do today (4 short bullets), what to do this week, warning signs requiring callback, follow-up timing, and prescription notes if any. Eighth-grade reading level. End with a one-line reminder to call the office with questions.
Expected output shape

A printable AVS-style document ready to hand to a patient.

Pre-authorization or insurance letter

Recommended tool · Gemini · Intermediate
Draft a prior-authorization letter from a medical coder requesting [treatment / medication] for a patient. Cover: medical necessity rationale citing the relevant clinical findings, prior treatments tried and outcomes, why this is the appropriate next step, and references to standard-of-care guidance where relevant. Tone: clinical, factual, defensible. Leave bracketed fields where I need to fill in patient-specific data.
Expected output shape

A formal pre-auth letter with clearly marked fields for chart-specific data.

← Back to tools for Medical Coders