DEV Community

Tosh
Tosh

Posted on

ChatGPT Prompts for EMTs and Paramedics: Patient Communication, Documentation, and Decision Support

ChatGPT Prompts for EMTs and Paramedics: Patient Communication, Documentation, and Decision Support

Emergency medical services operates in compressed time with incomplete information. The communication with patients and families, the clinical documentation, and the decisions made in minutes can affect outcomes for hours or days afterward. These prompts help compress the cognitive load during high-stress moments.


Patient communication script for a specific condition

When you need to explain what's happening and what you're doing:

"Write a patient communication script for someone experiencing [condition: chest pain / difficulty breathing / severe injury / altered mental status / etc.]. What I'll tell them: [describe what's actually happening medically and what care is needed]. They're likely [scared / confused / in pain]. Write a short script that: acknowledges what they're experiencing, explains briefly what we're doing and why, tells them what to expect next, and gives them something to focus on. Under 100 words, words most people understand."

Patients who understand what's happening cooperate better and are less likely to refuse care.


Handoff report structure (SBAR)

The critical information transfer to the receiving facility:

"Write a handoff report in SBAR format for a patient you're transporting to [ED / receiving facility]. Situation: [brief context]. Background: [relevant history and exam findings]. Assessment: [your clinical impression]. Recommendation: [what you think should happen next — your request]. Include: vitals, treatments given, patient's response, any changes en route. Make it concise but complete — under 2 minutes to present."

Handoffs that follow a clear structure ensure nothing critical gets lost between teams.


Difficult family conversation script

When family is upset, refusing care, or asking difficult questions:

"Write a script for a difficult conversation with a patient or family member. The situation: [describe — patient refusing transport / family demanding we do something not medically indicated / family angry about response time / etc.]. What I want to accomplish: [acknowledge their feelings, set boundaries, explain why we're doing what we're doing]. Write a calm, respectful script that: validates their emotion without agreeing to unsafe requests, explains our position clearly, and offers what we can do. Under 150 words."

Conversations that validate emotion while maintaining professional boundaries de-escalate more often than defensive ones.


Crew safety assessment note

When something doesn't feel right:

"Document a scene safety concern for [situation: aggressive patient / hazardous environment / infection risk / etc.]. What you observed: [describe specifically]. Why it's a concern: [what could go wrong]. Action taken: [did you retreat, call police, wear extra PPE, etc.]. Document this as a brief, factual safety note for the run report. No assumptions — just what you observed and why you made the call you did."

Safety documentation that's specific protects both the crew and the patient.


Clinical decision documentation

When your assessment changes your care plan:

"Document your clinical reasoning for [decision: decision to not transport / decision to transport emergent vs. non-emergent / decision to request advanced life support / decision to administer a specific medication / etc.]. Patient presentation: [describe]. Assessment: [your clinical impression]. Rationale: [why you made this decision — specific to this patient, not generic]. Write this as a brief clinical note that explains your thinking — not a justification, just the thought process."

Documentation that captures clinical reasoning is stronger than documentation that only lists actions.


System error or near-miss report

When something went wrong or almost did:

"Write a confidential safety report for [incident: equipment failure / communication breakdown / near-miss medication error / dispatch error / etc.]. What happened: [describe sequence of events]. Why it happened: [root cause — system failure, not just human error]. Impact: [what could have happened / what did happen]. Recommendation: [what could prevent this next time]. Write this as a learning opportunity, not a blame assignment."

Near-miss reporting that's non-punitive actually gets used to improve systems.


Off-duty response decision framework

When you encounter an emergency off-duty:

"Help me think through whether to respond off-duty to [situation: cardiac arrest at grocery store / motor vehicle accident I witness / person in distress on the street / etc.]. Factors to consider: [scene safety, available resources, your fatigue level, local protocols about off-duty response, liability, family expectations]. Write a decision framework that covers: when responding is appropriate, when it creates more problems, what to do if you do respond, and how to document it. This is for my own thinking."

Off-duty response decisions are personal and complex. A clear framework helps you think it through.


Get the full toolkit

500+ prompts for emergency responders and healthcare professionals: https://toshleonard.gumroad.com/l/rzenot

Better patient communication. Clearer documentation. Safer decisions.

Top comments (0)