Emergency Medical Services and Paramedic Care Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
The five cases come from Harlow Valley Ambulance Authority, a fictional county service covering rural highway, small town, and suburban districts with two receiving hospitals. Each describes a decision crews, dispatchers, and receiving teams meet on ordinary shifts. Names and figures are invented, but the pressures are familiar. Read each case with the local protocol set beside you. Ask what the patient needed, what the evidence showed at the time, how people communicated, and which written rule applied. The cases move from delayed escalation through handover risk, capacity strain, quality review, and a consent question late in a long shift.
Case Study 1
Delayed escalation after a slow change in presentation
Harlow Valley Ambulance Authority, a county EMS provider with four station areas and two receiving hospitals, reviewed here through its Whitfield Creek crews.
The situation
Mid-shift, a crew of two paramedics, Dana and Luis, was sent to a house in the Whitfield Creek district for Ernest, a man in his seventies who lived alone and had been unsteady for two days. His daughter had called after noticing he sounded less like himself. When the crew arrived he was sitting in his chair, alert, and insisted he was fine. His speech was a little slower than the daughter described, and his grip on the left side seemed weaker when he reached for the clipboard. The crew completed the local stroke screen, found it borderline, and documented the findings as recorded. They did not notify the receiving hospital or request a second unit.
The challenge
The crew had two conflicting pictures: a reassuring set of readings and a daughter's account of a change from his baseline. Their protocol allowed a documented borderline screen to be rechecked, but the rule did not say how often or who should be told. Ernest was refusing transport, and the crew had to decide whether his capacity to refuse was adequate, whether to keep trying to persuade him, and whether a handover of concern to the hospital and the dispatch supervisor was warranted.
Analysis
Teams grounded in Emergency Medical Services and Paramedic Care usually start by separating what the patient needed from what the crew could measure in the room. Ernest needed a clear answer to whether a change from his baseline was a new problem, and the evidence in front of the crew was mixed. A single borderline screen does not rule out a developing deficit, especially when a family member describes a shift in speech and balance over two days. The clinical record should have carried the daughter's timeline as a finding in its own right, with the time she last saw him as the reference point rather than the time of the crew's arrival.
Coordination failed quietly here. Dana and Luis each assumed the other would raise the concern with the hospital, and neither did. The local protocol asks crews to escalate when a screen is borderline and collateral history points the other way, but it lists no owner for that call and no time window for a repeat assessment. Applying the protocol well would have meant a documented repeat screen before the crew cleared the scene, a direct call to the receiving emergency department with the daughter's timeline, and a request that the dispatch supervisor be informed so a second unit could be considered.
- Daughter's first callReports a change in speech and balance over two days.
- Crew arrivalPatient alert, declines transport, screen borderline.
- Repeat screen omittedNo timed recheck before the scene is closed.
- Refusal documentedCapacity reasoning recorded, no second clinician reached.
- Hospital reviewAdmitted for further assessment after the family raised concern.
Actions taken
- Require a documented repeat screen whenever a borderline result sits alongside a collateral history of change, with the repeat timed and recorded before the scene is closed.
- Name one clinician as owner of each escalation decision on a shared call, and state that role at the start of handover so neither assumes the other has acted.
- Add a direct call to the receiving emergency department for any patient with a changed baseline reported by family, passing on the collateral timeline before the ambulance leaves the scene.
- Review every refusal against the capacity checklist with a second clinician reached by phone, and record who was present, what was explained, and when the offer of transport was repeated.
Results
The service's clinical lead reviewed the call with both crew members and the hospital's emergency department. Ernest was admitted the same day for further assessment, and the team confirmed the daughter's timeline had been the most useful piece of information on scene. In the next quarter, the service audited 46 refusal records from the district and found that 9 had a repeat screen documented, a figure the team considered too low. After the protocol was revised, 38 of the next 41 borderline screens with family concern carried a timed repeat and a named owner.
Questions for discussion
- Which findings in this call should have triggered a repeat assessment, and who on the crew was responsible for making that call?
- How would the handover have changed if the daughter's timeline had been recorded as the primary complaint rather than background?
- What separates a legitimate refusal from one that needs a second clinician to review it, and how should the protocol define that line?
Case Study 2
Handover gap between a transporting crew and an emergency department
Harlow Valley Ambulance Authority, the same county provider, reviewed here through its transfer standards at Pinecrest Regional Medical Center.
The situation
A paramedic named Lena transported a woman in her late sixties to Pinecrest Regional Medical Center after a fall at home. The patient, Mrs. Feeney, was alert on arrival but unsure of the day, and her daughter had told Lena that her mother fell twice that morning and seemed sleepier than usual. Lena wrote the daughter's comments on the back of the transfer sheet and planned to read them out during handover. The receiving triage nurse, Kwame, took a verbal handover in the corridor while another ambulance was waiting, and the back page was not read. Lena returned to station at the end of her shift with no written confirmation that the note had reached the nurse.
The challenge
The handover had a clear structure on paper, yet the one fact most relevant to the patient's safety lived on a page nobody read aloud. The receiving team had to decide how far to trust the verbal account, whether a patient with new reports of falls and drowsiness needed earlier reassessment, and how the crew's responsibility ended once the stretcher moved. Both teams followed a local handover standard requiring a spoken summary and a written record, but it does not say what happens when the two disagree.
Analysis
Mrs. Feeney's needs were simple to describe but easy to lose in transit. She had a recent fall, a change in orientation from her usual state, and a family report that she was sleepier than normal. Each of those is a reason to reassess early, and together they made the back page of the transfer sheet the most important document in the bay. The evidence that mattered was not the crew's observation at the scene, which was accurate, but the daughter's account of a pattern across the morning. A handover that carries only the crew's own findings gives the receiving team a snapshot where a timeline was needed.
The failure was shared, not one person's lapse. The local standard asks for a spoken summary and a written record, and both were present, but nothing in the sequence required the receiving nurse to confirm that the written record had been read. Lena had a sound instinct to read the note aloud, and Kwame had a busy bay and a waiting ambulance. A simple read-back, in which the receiver repeats the two or three most critical facts, would have caught the gap in the time it took to move the stretcher. The same step also gives the crew a clear point at which their responsibility transfers.
Actions taken
- Require a read-back of the two most critical facts, spoken by the receiving clinician, before any crew member leaves the bay or the corridor.
- Put every collateral report, including family observations, on the first page of the transfer sheet rather than the back, and flag any new report of falls or drowsiness with a boxed header.
- Set a rule that any patient reported to have fallen more than once, or to be less alert than usual, is reassessed by a clinician within a fixed time of arrival, whatever the queue.
- Audit handovers from crews to the emergency department each month, sampling at least 20 transfers and recording whether the written note was read aloud and confirmed.
Results
The department adopted the read-back within the first month. Over the following quarter the audit sampled 60 transfers, and a spoken read-back was documented in 52 of them, up from 19 of 58 in the baseline month. Mrs. Feeney was reassessed in the corridor and reviewed by the medical team within the hour. The bay lead said the most useful change was moving collateral reports to the front of the transfer sheet, because crews stopped treating the back page as optional.
Questions for discussion
- Which single element of this handover would you change first, and what evidence would show that the change worked?
- When a verbal account and a written record disagree, who should the receiving clinician trust, and how should that be documented?
- How should a crew close its responsibility for a patient in a crowded corridor without leaving a gap that the receiving team cannot see?
Case Study 3
Peak demand exceeds available ambulances in one district
Harlow Valley Ambulance Authority, reviewed here through the Eastfield station and its dispatch cover decisions.
The situation
The Eastfield station normally covers its district with three ambulances and a rapid response car. In the third week of the quarter, a power outage and a multi-vehicle collision on the highway pushed call volume to more than twice the usual overnight rate. Dispatch held 14 calls in queue at the peak, and one ambulance stayed at the hospital for nearly two hours while the emergency department was full. The station supervisor, Ravi, had two crews available, and the rapid response car was the only unit that could reach the outlying villages within the response target. Patients were waiting longer for a first contact.
The challenge
The supervisor had to decide how to spread scarce crews without making the wait for the sickest callers longer than it needed to be. Options on the table included holding the rapid response car for high-priority calls, asking a neighboring station for cover, and moving a crew from a planned transfer. Each option would reduce risk in one place and increase it in another, and the local dispatch protocol gives priority rules but no guidance on what to do when every crew is committed.
Analysis
The evidence in the dispatch log was clear about the spread of waiting times and less clear about harm. Most queued calls were lower acuity, but a minority were high priority, and the log did not show how long those callers waited for a first contact. Treating every call as the same made the wait look uniform when it was not. Patient needs should drive the rule: a caller with a probable time-critical problem needs a fast response even if it means a longer wait for a lower-priority transfer. The team had to separate delay that changes the path of care from delay that only inconveniences the family.
Coordination was the lever the station controlled most directly. Ravi kept a single board that showed each crew's status, the hospital turnaround times, and the calls waiting for a unit, and he asked the hospital liaison to flag any ambulance held beyond the handover target. The local protocol sets clear priority codes but treats cover moves as a supervisor's judgment, with no minimum time for a neighboring station to respond. A written trigger for asking a neighbor, such as more than three high-priority calls waiting for the same district, would have turned a judgment into a shared decision. Crews should also know which transfers can be moved without harm.
- Monitor the queue Dispatch reviews waiting calls and priority codes every fifteen minutes.
- Trigger cover request Crosses the written threshold, so the neighboring station is asked.
- Hold or release Rapid car held for time-critical calls, transfers deferred if stable.
- Review and record Log each request and outcome, then review delays at the weekly meeting.
Actions taken
- Set a written trigger for requesting cover from a neighboring station, such as a fixed count of high-priority calls waiting in one district, and log each request and its outcome.
- Hold the rapid response car for calls coded as time-critical, and release it only when the dispatcher confirms no other time-critical call is waiting.
- Review scheduled inter-facility transfers at the start of each shift, and defer those that are stable and not time-bound, with the receiving unit informed of the revised time.
- Ask the hospital to flag any ambulance held beyond the handover target to the dispatch supervisor within the hour, and review each delay in the weekly operations meeting.
Results
The district's cover requests were logged in the following month, showing 11 requests in total, 7 of which led to a crew moving within the target time. Average waiting time for high-priority calls fell in the busy weeks that followed, although it stayed above the service's goal. The rapid response car was held for time-critical calls on 40 occasions and released to other work only after dispatch confirmed the queue. Two scheduled transfers were deferred, and the receiving units accepted both without complaint. Ravi said crews noticed the trigger first, because it made the decision visible.
Questions for discussion
- At what point in this shift should a supervisor have asked a neighboring station for cover, and what information would have justified it?
- Which scheduled transfers in your own service could be deferred safely, and who would need to agree to that?
- How should a rapid response unit be allocated when its best use depends on calls that have not yet been received?
Case Study 4
Uneven documentation and response times across four stations
Harlow Valley Ambulance Authority, reviewed here through its quality team and the indicators for all four station areas.
The situation
The quality team reviews anonymized indicators each month for four station areas. Over the previous twelve months, 3,412 patient records were sampled, and 571 of them lacked a documented reassessment after first contact. The rate varied widely between areas. Riverside recorded the most complete notes but the longest time from call to arrival, while Northgate was faster on scene and had the highest share of refusals without a second clinician's review. Riverside and Northgate were not the only areas with gaps, but they showed the clearest contrast. The service's medical director, Simone, asked for a cause before any target was set.
The challenge
The indicators pointed in different directions, which made it tempting to treat each one as a separate problem. Improving response times in one area might worsen documentation if crews had less time at scene. The team had to find a process cause that explained both patterns, decide which records were reliable enough to compare, and set measures that would not reward the wrong behavior. Simone needed to avoid a conclusion based on station culture when the difference could come from case mix or the software used to record notes.
Analysis
Patient needs were the starting point, and the indicators only mattered insofar as they described care that reached people in time. A reassessment after first contact is a safety check, not paperwork, and a missing entry may mean the check did not happen or only that it was not written down. The evidence therefore had to be read carefully. The team compared a sample of the 571 gaps against the electronic timestamps and found that about a third had a reassessment recorded on paper that was never transferred. That changes the question from whether crews reassessed to whether the record can carry what they did.
Process causes showed up when the indicators were laid next to the way each area worked. Riverside used a single shared tablet that crews filled in before leaving the hospital, which delayed the handover but kept notes complete. Northgate's crews wrote their notes after returning to station, so the record was thin at the hospital but the vehicle was back in service sooner. The protocol requires documentation before the end of the shift but does not specify where, and the two areas had built different routines around that gap. Shared standards for timing and location would make the comparison fair.
Actions taken
- Agree one documentation standard across all four areas that sets when notes are completed and where, with a single electronic field for reassessment after first contact.
- Audit a random sample of thirty records per area each month against electronic timestamps, and report the share where the recorded reassessment matches the timestamp.
- Stratify all indicators by case mix and by recording device before comparing areas, so that a difference in software or patient complexity is not read as a difference in care.
- Set a baseline for the next two review cycles without targets, then agree a single improvement measure with a named owner and a review date for each area.
Results
The first audit under the new standard found the reassessment field matched the timestamp in 84 of every 100 sampled records, against a much lower rate before the change. Some of the earlier gap was a recording habit rather than missed care, which the team could only see after the timestamps were compared. Northgate's response times stayed the same, and the team agreed that speed was not the problem to fix there. A refusal review target was set for the following cycle, and Simone asked that the next report include case mix alongside every indicator.
Questions for discussion
- Which indicator in your own service would be most misleading if it were compared across areas without adjusting for case mix?
- How would you decide whether a documentation gap reflects missed care or a recording habit?
- What should a service do when two areas show opposite strengths, and what would make a shared target fair to both?
Case Study 5
Advance wishes, family pressure, and a patient who fluctuates
Harlow Valley Ambulance Authority, reviewed here through its medical direction and advance statement procedures.
The situation
Mr. Adeyemi is in his eighties and lives with his son, who called the emergency line after his father became drowsy and disoriented. A paramedic, Chiara, and her partner, Owen, found him in bed, confused about the time but able to name his son. A written advance statement from his primary care office was in a folder on the kitchen table, and it asked that he not be taken to hospital unless he asked to go. His son was distressed and insisted on transport. He was lucid for a short time and then drifted again. The son asked to be told everything the crew had found, including what his father had said earlier.
The challenge
The crew had to weigh a written wish from a time when the patient could express it against a present situation in which his capacity was unclear, while his son was asking for information and for a decision. Their duties pointed in several directions: to respect the patient's expressed wishes, to act in his best interest when he could not decide, to keep his health information private from a family member who was not named as his representative, and to involve the right people before leaving.
Analysis
Mr. Adeyemi's immediate need was an accurate picture of what was happening to him, and that picture was unstable. The crew's evidence was real but short-lived: he was confused at one point, clearer at another, and the reasons for the change were not established on scene. Capacity is decision specific and can fluctuate, so a moment of clarity does not automatically settle whether he can refuse transport now. The advance statement carried weight as evidence of what he wanted when he could express it, but the crew still needed to ask whether its circumstances matched the present situation. Those are clinical judgments and should be recorded as such.
Communication with the son was the part most likely to go wrong. Owen explained that the crew could not discuss the patient's health details with the son without his father's agreement, and the son heard this as a refusal to help. A better opening would have separated what the crew could share (that they were assessing, what the next steps were, how to reach the receiving team) from what needed the patient's consent. The local protocol calls for medical direction when a patient's capacity and expressed wishes conflict, and the crew should have called the on-call physician before deciding and documented that conversation.
Actions taken
- Document capacity separately for each decision, with the time, the questions asked, the answers given, and the observations behind the conclusion, rather than a single yes or no.
- Before transporting against a written advance statement, or without clear consent, contact the on-call physician and record the advice, the time of the call, and who agreed to the plan.
- Agree a short script for family members that explains what the crew can share, what needs the patient's permission, and how the family can reach the receiving team with questions.
- Ask the service's medical director to review the case at the next governance meeting, focusing on advance statement handling and the escalation step for conflicting capacity and wishes.
Results
Mr. Adeyemi was taken to the emergency department after the physician was reached by phone, and the crew's record showed the call and its outcome. His advance statement was reviewed with him by the primary care office the following week, when he was clearer, and he confirmed the wording and added a named representative. The son received a short written summary of what the service could share, and the review noted that the son's concerns were resolved without a formal grievance. The governance meeting agreed to add a conflict step to the protocol and to include advance statements in crew training.
Questions for discussion
- When a patient's written wishes and present capacity seem to conflict, what evidence should move the crew toward one or the other?
- How much of a patient's information can a crew share with a family member who is distressed but not named as a representative?
- At what point should a crew stop discussing a decision on scene and hand it to a physician, and how should that handover be recorded?
Learning Resources
Healthcare CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.