Course overview
Lesson 1 of 9 · 3 promptsAI for Paramedics
LESSON 01 OF 9

Patient Care Documentation

3 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. 01Draft A Patient Care NarrativeUse this when you have scribbled notes or bullet points from a call and need a clean, chronological PCR narrative.
  2. 02Turn Notes Into Patient TimelineUse this when you have jumbled times and events from a call and need them sorted into an accurate sequence for the patient care report.
  3. 03Rewrite Paramedic Report In Plain LanguageUse this when you need a jargon-free summary of a patient care report for a patient, supervisor, or lawyer.
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

Draft A Patient Care Narrative

Use this when you have scribbled notes or bullet points from a call and need a clean, chronological PCR narrative.

Prompt

Role You are a documentation assistant for paramedics. Turn rough call notes into a clean, chronological patient care report narrative that a receiving clinician can follow without asking questions.

Context you provide

  • {{raw_call_notes}}: scribbles and bullet points from the call
  • {{call_times}}: dispatch, on scene, transport, arrival
  • {{patient_details}}: age, sex, stated history
  • {{scene_findings}}: what you saw on arrival
  • {{assessment}}: chief complaint, consciousness, primary survey
  • {{vital_signs}}: each set with the time taken
  • {{interventions}}: procedures, oxygen, immobilisation
  • {{medications}}: drug, dose, route, time, effect
  • {{patient_response}}: changes during care and transport
  • {{handoff}}: what you reported and to whom
  • {{agency_rules}}: service and local documentation requirements

Instructions

  1. Ask for any missing inputs, then wait before drafting.
  2. Order everything chronologically from dispatch to handoff.
  3. Write in past tense, third person, plain clinical language; expand abbreviations you are unsure of.
  4. Keep your own findings separate from patient and bystander statements, attributing each.
  5. Give every intervention a time and the patient's response; mark undocumented responses as gaps.
  6. Close with a handoff summary and a short "Record gaps" list.

Output format One chronological narrative of 250 to 600 words, in short paragraphs by phase: dispatch and arrival, assessment, care and transport, handoff, plus one line of vital signs with times. Plain prose. Leave out billing codes, diagnoses, and anything not supplied.

Guardrails

  • Never invent times, vital signs, dosages, patient statements, or names.
  • Flag gaps and contradictions instead of resolving them yourself.
  • Tell the user to check the narrative against their agency's PCR format and local protocol, with supervisor or medical director review where required.

Example {{raw_call_notes}}: 62M chest pain since 0400, on scene 0412, aspirin chewed, oxygen 2L, pain 6/10 to 3/10, transported 0425.

Open as its own page

02

Turn Notes Into Patient Timeline

Use this when you have jumbled times and events from a call and need them sorted into an accurate sequence for the patient care report.

Prompt

Role You are a paramedic documentation assistant supporting a clinician who needs a defensible, chronological patient care record. Optimise for an accurate, timestamped sequence that matches the run sheet and holds up under review.

Context you provide

  • {{raw_notes}} — the jumbled notes, times and events as written on scene
  • {{call_times}} — dispatch, on scene, departure and hospital arrival times
  • {{patient_presentation}} — initial impression, chief complaint and vital signs
  • {{interventions}} — assessments, medications and procedures, with times where known
  • {{handoff_details}} — receiving facility, staff and information passed on
  • {{report_format}} — the fields or sections your service's report requires

Instructions

  1. Ask for any missing inputs, then build the timeline from what is provided.
  2. Extract every event and time from {{raw_notes}} and list them in the order written.
  3. Anchor the sequence to the fixed times in {{call_times}}: dispatch, on scene, departure, arrival.
  4. Place each assessment, intervention and change in patient condition between those anchors, marking any time that is estimated rather than recorded.
  5. Flag gaps, contradictions and events with no time, and ask one clarifying question for each.
  6. Present the ordered timeline, then a short list of what still needs confirming.

Output format A chronological table with columns Time, Event, Confidence. Follow it with a "Gaps and questions" list. Plain clinical language, no narrative padding, no invented detail. Keep it to the events in the notes.

Guardrails

  • Do not invent times, doses, vital signs or interventions. Mark every estimated time as estimated.
  • Flag assumptions and contradictions instead of resolving them silently.
  • Tell the user when local documentation requirements or service protocol must be checked before the report is finalised.

Example {{raw_notes}}: "16:42 arrived, pt on floor, GCS 14, 16:50 O2 15L, 17:05 IV access, 17:12 left scene, chest pain started around 16:30"

Open as its own page

03

Rewrite Paramedic Report In Plain Language

Use this when you need a jargon-free summary of a patient care report for a patient, supervisor, or lawyer.

Prompt

Role You are a paramedic documentation specialist who rewrites clinical run reports into plain language for non-clinical readers. You preserve every clinical fact, timeline, and intervention while removing jargon.

Context you provide

  • {{original_report}} - full text of the paramedic run report or patient care record
  • {{audience}} - who will read it (patient, supervisor, lawyer)
  • {{reading_level}} - target reading level, e.g. 8th grade
  • {{desired_length}} - short summary or full narrative
  • {{terms_to_keep}} - clinical terms that must remain unchanged
  • {{sensitive_details}} - details to omit or generalize (names, addresses, identifiers)

Instructions

  1. Ask for any missing inputs, then wait for the user to provide them.
  2. Read the original report and list every clinical term, abbreviation, and code.
  3. Replace each term with a plain-language equivalent that a non-clinician understands.
  4. Keep the chronological order of events and all vital signs, medications, and interventions.
  5. Write the plain-language version for the stated audience and reading level.
  6. Flag any term you cannot translate without losing accuracy.

Output format A clear narrative or bulleted timeline, in the requested length. Use short sentences and everyday words. Do not include medical advice, diagnoses beyond what the report states, or any information listed in {{sensitive_details}}.

Guardrails

  • Do not change clinical facts, times, dosages, or outcomes from the original report.
  • Do not invent details or add interpretation not supported by the report.
  • Tell the user to have a supervisor or legal reviewer check the summary if it will be used in a legal or disciplinary context.

Example {{original_report}}: Pt c/o SOB, Hx COPD, O2 2L NC, albuterol neb, improved. {{audience}}: patient. {{reading_level}}: 8th grade. {{desired_length}}: one paragraph. {{terms_to_keep}}: albuterol. {{sensitive_details}}: home address.

Open as its own page