Course overview
Lesson 8 of 9 · 2 promptsAI for Paramedics
LESSON 08 OF 9

Incident Reports And Admin

2 prompts for Paramedics

Prompts for Paramedics: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Write An Exposure Or Incident ReportUse this when you need a factual, blame-free report after a needlestick, injury, or safety event.
  2. 02Draft A QA Case SummaryUse this when your service is reviewing a run and you need a neutral summary of what happened and when.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Write An Exposure Or Incident Report

Use this when you need a factual, blame-free report after a needlestick, injury, or safety event.

Prompt

Role You are a paramedic crew lead drafting a factual, blame-free exposure or incident report for your service records, occupational health follow-up and any required notification.

Context you provide

  • {{event_type}} — needlestick, sharps injury, body fluid exposure, lifting injury, vehicle incident, other
  • {{date_time_location}} — shift date, time, scene or station
  • {{people_involved}} — crew, roles, witnesses
  • {{what_happened}} — plain sequence in your own words
  • {{ppe_and_equipment}} — what was in use, what failed or was removed from service
  • {{immediate_actions}} — first aid, washing, reporting, isolating equipment
  • {{injuries_or_symptoms}} — reported by whom and when
  • {{notifications}} — supervisor, infection control, occupational health
  • {{follow_up_needed}} — testing, vaccination, referral, time off

Instructions

  1. Ask for any missing inputs, then draft the report.
  2. Write chronologically in past tense, using the voice your service requires.
  3. State only observable facts and direct quotes. Separate what you saw from what you were told.
  4. Note contributing conditions such as lighting, staffing, equipment or fatigue, without assigning fault.
  5. List equipment or PPE removed from service and why.
  6. List follow-up actions taken and outstanding, each with an owner.

Output format Sections: Event Summary, Sequence Of Events, People Involved, Exposure Or Injury Detail, Immediate Response, Contributing Factors, Notifications, Follow-Up Actions. Bullets under each, 250 to 400 words, neutral and factual. No speculation, no opinion about colleagues, no patient identifiers.

Guardrails

  • Do not invent times, test results, lot numbers or regulation references. Mark unknowns as "to be confirmed".
  • Do not assign blame or speculate about cause; report facts and conditions only.
  • Tell the user to check their service reporting policy, occupational health pathway and any local regulatory requirement before submitting.

Example {{event_type}} needlestick during IV cannulation; {{date_time_location}} 14 Mar, 02:10, patient's home, Elm Road.

Open as its own page

02

Draft A QA Case Summary

Use this when your service is reviewing a run and you need a neutral summary of what happened and when.

Prompt

Role You are a clinical quality reviewer for a paramedic service. You produce a neutral, chronological summary of one run so a review panel can see what happened, when, and what the record does not show.

Context you provide

  • {{run_number}} - incident or CAD number
  • {{call_datetime_and_location}} - date, time, general area
  • {{dispatch_information}} - call type, pre-arrival instructions
  • {{crew_and_roles}} - who attended, their role
  • {{patient_presentation}} - age band, chief complaint, first observations
  • {{assessment_findings}} - vital signs, examination, scores used
  • {{interventions_and_times}} - treatments, medications, timestamps
  • {{transport_and_handoff}} - destination, mode, handover
  • {{documentation_available}} - care record, CAD log, extracts
  • {{qa_question}} - what the review must answer

Instructions

  1. Ask for any missing inputs, then restate the run number and QA question in one line.
  2. Build a timeline from supplied timestamps only; write "time not documented" where a time is absent.
  3. Summarise assessment and interventions in sequence without judging clinical appropriateness.
  4. Keep documented facts separate from inference and label each inference as such.
  5. Note gaps, contradictions and missing records as observations, not conclusions.
  6. Close by restating the QA question and what the record does and does not answer.

Output format Headings: Case identifiers, Timeline, Assessment and interventions, Handoff, Documentation observations, QA question and what the record shows. 400 to 700 words, neutral third-person past tense. Leave out clinical advice, opinions on crew conduct and recommendations unless the QA question asks for them.

Guardrails

  • Do not invent times, observations, drug doses or protocol names; mark unknowns as not documented.
  • Do not assign blame or judge the care given.
  • Flag any patient safety or regulatory matter for the clinical governance lead or a licensed clinician.

Example Run 24-1187, 03:40, dispatch chest pain, paramedic plus technician, 62-year-old male, handoff to ED at 04:35, QA question: was the 12-lead completed before transport?

Open as its own page