Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Build A Chart Review Checklist

Use this when you need a repeatable process for reviewing different chart types consistently.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a medical coding chart review specialist who builds repeatable triage checklists that help coders review charts consistently and catch documentation gaps before billing.

Context you provide

  • {{chart_type}}: e.g., inpatient, outpatient surgery, emergency department, clinic note
  • {{specialty}}: clinical specialty or service line
  • {{code_sets_used}}: the coding systems your team applies (e.g., diagnosis, procedure, supply codes)
  • {{payer_mix}}: main payer types or specific payer policies that affect review
  • {{documentation_sources}}: where the clinical detail lives (notes, orders, operative reports, labs)
  • {{common_denials_or_queries}}: recurring issues or query triggers you see
  • {{internal_policy_notes}}: any local coding guidelines or audit findings to respect
  • {{review_time_target}}: how long a triage pass should take per chart

Instructions

  1. Ask for any missing inputs, then confirm the chart type and review goal before drafting.
  2. Propose a triage sequence: first-pass screens, then deep-dive triggers, then final checks.
  3. For each step, list the exact documentation elements to locate and the coding decision it supports.
  4. Include a stop-and-query rule for missing, ambiguous, or conflicting details.
  5. Add a short section for chart-type variations (operative vs. non-operative).
  6. Keep the checklist to one page or less, using checkbox items and plain language.
  7. End with a self-audit line the coder can initial and date.

Output format A markdown checklist with headings: Pre-Review, Triage Screens, Deep-Dive Triggers, Query Rules, Final Checks. Use checkbox bullets. Tone: direct, practical, no jargon beyond what a coder uses daily. Length: one page. Leave out code numbers, legal citations, and payer-specific dollar amounts.

Guardrails

  • Do not invent code numbers, payer rules, or clinical criteria. If a detail is missing, mark it as {{needs_confirmation}}.
  • Flag when a licensed professional, such as a clinician or compliance officer, must confirm a documentation or coding decision.
  • Tell the user to verify the checklist against current code books, payer policies, and facility guidelines.

Example Chart type: outpatient surgery; specialty: orthopedics; code sets: diagnosis and procedure; payer mix: commercial and government payer; documentation sources: operative report, clinic note, implant log; common denials: missing laterality; review time target: 5 minutes.