General, Trauma and Critical Care Surgery Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases come from surgical services that care for injury, acute illness and recovery after operations. Each turns on a decision made with incomplete information, often during a busy shift and across several teams. The organizations and people are fictional, and staff are named by first name and role only. Read each case for the patient first, then the evidence available at each point, then how information moved between people. Protocol references are general on purpose, so you can test your own local rules against the decisions described. The discussion questions suit a group that talks them through.
Case Study 1
A slow night on the surgical ward
Tamarack Valley General Hospital, a 340-bed community hospital with a surgical ward and a six-bed high dependency unit.
The situation
Ellis Brandt, a man in his late sixties, was admitted to the surgical ward after a fall at home. He had bruising across the left side of his chest and a complaint of abdominal discomfort that his admitting team had assessed as expected after the fall. Over the first night, the nursing notes recorded a gradual change. His pain moved toward the upper abdomen, his heart rate crept upward across several checks, and his urine output fell below the threshold on the observation chart. The early warning score rose from two to four across three hours. The night registrar, Ravi, reviewed him once, documented the trend, and planned to recheck at the next round.
The challenge
Each reading, taken alone, sat close enough to acceptable that nobody felt pressed to act. The protocol required escalation to the on-call surgical consultant when the score reached five or when two parameters moved in the same direction across consecutive checks. Priya, the ward nurse, knew the rule but was carrying a full assignment and was reluctant to call a consultant on a trend she had not yet seen confirmed. The team had to decide whether the pattern met the threshold before the next scheduled round.
Analysis
The first question is what Ellis needed from the team at that point. He was not in distress in a way that would prompt an immediate call, but his observations formed a pattern the evidence did not allow anyone to dismiss. A rising heart rate, falling urine output and pain that moves are each nonspecific on their own. Read together over several hours, they describe a patient whose reserve is narrowing. The useful habit is to treat the trend as the finding rather than each reading. Recording the direction of change with times gives the next clinician something concrete to test, instead of a set of reassurances that each look fine in isolation.
Teams grounded in General, Trauma and Critical Care Surgery usually look at the escalation rule before they look at the patient's numbers, because the rule decides who must be told and by when. Here the local protocol named two triggers, a score of five and a sustained directional change across consecutive checks. Ellis met the second trigger before the round, so judgment alone was no longer enough. The coordination problem was that the nurse, the registrar and the consultant each held a piece of the picture, and none had the full sequence in one place. A short structured call would have moved the question to the person with authority to act within minutes.
- Admission after fallAbdominal discomfort recorded as expected; baseline observations taken.
- First night, early hoursHeart rate creeping upward and urine output falling across checks.
- Three hours inEarly warning score rises from two to four; pain moves upward.
- Registrar reviewTrend documented; recheck planned for the next round only.
- Consultant calledEscalation made after the recheck; consultant attends the ward.
Actions taken
- Add the direction and timing of each parameter change to the handover sheet, so the trend is visible without re-deriving it from the chart.
- Require that a rising early warning score with a second parameter moving the same way triggers a direct call to the on-call consultant, with the call logged.
- Give the ward nurse a scripted sentence for escalation, so that raising a concern does not depend on confidence in the moment or on seniority.
- Review the case at the next governance meeting with the timed observation chart, and ask whether the escalation rule was clear, reachable and used.
Results
The consultant was reached by telephone about forty minutes after the registrar's recheck, and came to the ward to review Ellis in person. The plan was revised, the observation frequency was increased, and the team agreed on a clear point at which the next escalation would be made without further discussion. The ward audit later found that the chart had recorded the trend but had not prompted a call. The ward adopted the scripted escalation sentence and a trend column on the handover sheet. Ellis's stay was longer than planned, but he went home in good condition.
Questions for discussion
- Which single observation in the first hours would you have named as the point where the trend became actionable, and what would you have needed to see before calling?
- How should a ward nurse weigh a protocol trigger against a senior colleague's reassurance that the patient is stable?
- What would make your own escalation rule easier to apply at three in the morning with a full assignment?
Case Study 2
A pending scan that did not cross the bedside
Crestline Medical Center, a 520-bed regional hospital with a trauma service, two operating suites and a 32-bed surgical ward.
The situation
Tomasz Keller, a man in his forties, was transferred from the trauma bay to the surgical ward at the end of the evening. He had been assessed after a motorcycle collision. The handover was given verbally at the nurses' station, supported by a printed summary generated from the electronic record. The summary listed his allergies and observation schedule, but it did not include a line stating that a follow-up scan review was pending, or that the trauma team had asked for a repeat assessment before midnight. The receiving nurse, Oscar, was taking over four patients that shift, and the bedside introduction was shortened because the ward was short of staff.
The challenge
The gap was not in the verbal handover alone. The summary was accurate for what it contained, so the receiving team had reason to believe they had the full picture. Oscar did not know that a question was open, and the trauma registrar had left the hospital at the same time. The ward's own handover policy asked for a structured tool, but the tool was used selectively when the ward was busy. The team had to find the open item before the time it was due.
Analysis
Tomasz needed a plan that made the pending review visible to whoever was watching him after midnight. The clinical evidence at handover was reassuring in the usual sense: his observations had been stable through the afternoon and the scan had been performed, but the report was not yet signed. A pending result is a different kind of information from a normal one. It changes what the next clinician should look for, and it has to be carried as an open question rather than a closed fact. When that status is lost in transfer, the patient's risk does not change, but the team's ability to respond to it does.
Handover work tends to treat the summary as a starting point, since the summary only carries what someone thought to type. The applicable standard here was the ward's structured handover tool, which asks for open items, pending results and time-critical actions as separate fields. Those fields were present in the template but had been left blank. The safeguard that would have caught the gap was a read-back, in which the receiving nurse repeats the open items aloud and the giver confirms them. The read-back was not part of the ward routine, and nobody at the station was assigned to notice its absence.
Actions taken
- Add a required field to the handover tool for pending results and open questions, so a blank entry is visible rather than silently skipped.
- Make a spoken read-back of open items mandatory for every transfer into the ward, and record the receiving nurse's name against it.
- Assign the ward's charge nurse to check the open-items list at the start of each shift, with a time limit for resolving each item.
- Audit fifty consecutive transfers each quarter, counting handovers with a complete open-items field and read-backs performed, and report the rate to the quality committee.
Results
Oscar found the gap about twenty minutes before the review was due, when he phoned the trauma bay to ask whether anything was outstanding. The scan report was signed, the surgical registrar reviewed it, and the team reached the decision they had originally planned. No harm came from the delay, but the margin had been narrower than anyone on the ward realized. Next quarter the ward completed a spoken read-back on most transfers, and the first audit recorded a clear rise in complete open-items fields. The committee asked for two more quarters of audit before calling the change settled.
Questions for discussion
- Which fields in your own handover tool would be most likely to be left blank under pressure, and what would make a blank field obvious to the receiver?
- When the giver and receiver disagree about whether an item was handed over, who in your service has the authority to settle it?
- How would you design a read-back that adds protection without becoming one more box ticked at the bedside?
Case Study 3
Three beds, one trauma list and a full queue
Ashgrove General Hospital, a 412-bed regional hospital with a ten-bed intensive care unit and two operating rooms.
The situation
Ashgrove General runs a ten-bed intensive care unit, and three of those beds are protected for patients recovering from major trauma operations. In the second week of a rising referral period, transfers from two smaller hospitals arrived at the same time as several urgent cases from the local emergency department. Two trauma patients were waiting for emergency operating time, one elective list had already been partly filled, and only one bed was free in critical care. Gwen, the bed manager, had to decide how to sequence admissions, which elective cases could move, and whether the protected beds could be released without weakening recovery care.
The challenge
The pressure came from three directions at once. Critical care could accept only a limited number of new patients without moving someone out, and the step-down area had no capacity to receive them. Operating room staff could run the emergency cases, but the anesthesia team was already committed to the elective list. Hana, the consultant intensivist, was concerned that releasing a protected bed too early would leave the next trauma admission without a safe place to recover.
Analysis
The patients in this queue did not differ in a way that the bed board captured. One was a trauma patient with an urgent need for operating time and a predictable recovery requirement. Another was an elective case whose delay carried a lower immediate risk but a real cost in pain and planning. The clinical evidence the team could use was the recovery profile of each patient, the expected length of critical care need, and how likely a delay was to cause deterioration. A bed count alone does not capture any of that, so the allocation decision has to rest on information the bed board does not show.
The surge plan gave the team a sequence to follow. Time-critical trauma cases came first, a protected bed could be released only with the intensivist's named sign-off, and elective cases were reviewed each morning against the bed forecast. Triage meant ranking the queue by clinical urgency, which protected the trauma patients but left the emergency department holding patients for longer. Rescheduling electives freed operating room time and a probable bed, but it moved patients who were already prepared. Opening a second step-down area was the most flexible option and the one with the most staffing cost, so it was held for the next day unless the queue grew.
- Forecast Publish the bed picture by mid-morning, with protected beds and time-critical queue shown.
- Decide Release protected beds only with named intensivist sign-off and a plan.
- Reschedule Move elective cases only after patients agree to new dates.
- Review Compare admissions, delays and bed use at the end of each day.
Actions taken
- Publish a daily bed forecast by mid-morning that shows protected beds, expected discharges and the queue of time-critical admissions in one view.
- Set a rule that a protected bed is released only with the intensivist's named sign-off and a documented plan for the next trauma admission.
- Review elective lists each morning with the surgical operations lead, moving cases only where the patient has been told and agrees to the new date.
- Open the second step-down area only when the queue passes an agreed threshold on two consecutive days, with staffing confirmed first and the decision logged.
Results
Three days in, the flow had settled. Two protected beds were released with sign-off, one elective list was moved by a day with the patient's agreement, and the trauma admissions were placed without a transfer to another hospital. The second step-down area was not opened, because the queue fell back before the threshold was reached. Hana noted that the protected beds had been released more slowly than she would have liked, and the team agreed that the next surge would need the forecast in place earlier. Gwen kept a log of decisions, later used in the review.
Questions for discussion
- If the queue had grown by another two admissions overnight, which of the three options would you have reached for first, and what would have changed your answer?
- Who in your organization is authorized to release a protected bed, and does that person have the information needed to decide quickly?
- How would you show a patient who is waiting for an elective date that the delay was a fair decision rather than an arbitrary one?
Case Study 4
Two sites, one return rate and an unexplained gap
Brackenridge Health, a 290-bed hospital whose general surgery and trauma service covers a north and a south site.
The situation
Brackenridge Health reviewed its general surgery and trauma outcomes after the quality office noticed a difference that the monthly summary had hidden. Over three quarters, the north site recorded eleven unplanned returns to the operating room from 212 operations, while the south site recorded four from 187. Critical care transfers within the first day showed a similar spread. The quality lead, Nadia, pulled anonymized case records for each event and asked the two site leads, Farid and Imogen, to agree on a shared review. Nothing in the data pointed to a single surgeon, and the case mix at the two sites was broadly similar on paper.
The challenge
The difficulty was that the indicators could not explain themselves. Unplanned returns can reflect a bleed that was not anticipated, a delay in recognizing a complication, a late decision to re-examine, or a documentation pattern that classified events differently at each site. The two sites also used different triggers for the critical care referral, and the handover records were not stored in the same format. Any change the service made would have to be justified against causes that were not yet known.
Analysis
For the patients, the question is whether the differences in return rates reflected care that was less safe, or whether they reflected different thresholds for going back to the operating room. Those are not the same problem. The anonymized case review showed that a number of north site returns followed a decision to re-examine early, which may be good practice, while several south site cases had a longer gap between the first warning sign and the first documented assessment. The evidence supported a closer look at timing and at the reasons recorded for each decision, rather than a judgment about the number alone.
Coordination was the weak point the review kept returning to. Each site had a complication pathway on paper, but the triggers for calling a senior surgeon differed, and the south site relied on the ward registrar to decide when a case was complex enough to escalate. Protocol compliance could be measured only where the escalation time was recorded, which was inconsistent. The sites agreed to write one shared definition of an unplanned return, to record the time of first concern, and to use a common escalation threshold for the next quarter. That agreement was the first step, not the solution.
Actions taken
- Agree a single written definition of an unplanned return and an unplanned critical care transfer, and apply it retrospectively to the last three quarters.
- Add two timed fields to the complication record, the time of first concern and the time of first documented senior review, and make both mandatory.
- Run a monthly review of every case with a gap longer than the agreed threshold, using the anonymized record and the reasons given at the time.
- Track the timed fields and the unplanned return rate on a control chart for each site, and review the chart at each quarterly governance meeting before changing anything else.
Results
Two quarters on, the timed fields were complete for most cases at both sites, and the gap between first concern and senior review fell at the south site. The control charts showed the north site's return rate moving toward the shared mean, though the sample was small and no single month was read in isolation. Farid and Imogen agreed the escalation threshold had been the main lever, and Nadia noted that the review had changed how surgeons spoke about early re-examination. The service will keep the control charts and decide the next change once the data are steady.
Questions for discussion
- Which of the indicators in this review would you trust least for comparing two sites, and what would you need to change in the record to make it more reliable?
- When a surgeon chooses early re-examination, how should a review distinguish sound judgment from a delayed recognition of a complication?
- What would convince your own governance group that an improvement cycle has worked, and how long should the team wait before deciding that?
Case Study 5
A disclosure request on the first day
Larkfield Community Hospital, a 260-bed hospital with a general surgery service, a trauma referral pathway and a monthly ethics committee.
The situation
Marguerite, a woman in her seventies, was admitted after a fall with an injury that the surgical team judged would need a planned decision about surgery. On the first day she had capacity to take part in the discussion, and she named her son, Dev, as the person she wanted kept informed. She asked that her daughter, Lina, not receive details of her condition, citing a long disagreement between them. Lina arrived that evening and asked to be present for the consent conversation. The ward had no advance directive on file, and the emergency assessment described the patient as settled and clear.
The challenge
Two duties pulled against each other. The patient's wish to limit disclosure was clear and recent, and confidentiality applied to her as an adult with capacity. Lina had a reasonable expectation of involvement, and she was not wrong that the decision might affect the family's plans for care at home. The team also could not confirm, from the records, whether the patient's capacity would remain stable through the period when consent was needed, which made the timing of the conversation a question in its own right.
Analysis
Marguerite's needs were partly clinical and partly about control. The evidence the team had was a recent capacity assessment, a documented wish about information sharing, and a set of observations that were reassuring for the moment. None of those pieces, on its own, decided whether Lina should be in the room. What the team needed was a clear record of what Marguerite understood, what she wanted shared and with whom, and how she wished to hear about any change. A shared decision is only as good as the patient's own voice in it, so the conversation had to start with her, alone, before anyone else was included.
The applicable protocol was the hospital's consent policy, which asks for capacity to be assessed for the specific decision and for the patient's preferences about disclosure to be recorded and respected unless a clear safety reason requires otherwise. The policy also expects a second clinician to be present for a significant consent discussion. Here the team's duty was to keep the patient's confidentiality intact while still allowing Lina to be involved if Marguerite agreed. The ethics committee had a monthly slot, but the decision was needed sooner, so Priyanka, the attending surgeon, and Bruno, the nurse manager, agreed a same-day escalation to the on-call ethics adviser.
Actions taken
- Hold the first part of the consent conversation with Marguerite alone, and record in her own words what she understood and what she wanted shared.
- Confirm the capacity assessment is specific to the decision in front of her, and repeat it if the conversation is delayed or her condition changes.
- Explain to Lina, with Marguerite's agreement, what can be shared and why, and offer her a separate conversation about her own concerns.
- Refer the question of disclosure and timing to the on-call ethics adviser the same day, and write down the advice and the reasons behind the final plan.
Results
Marguerite spoke with the team alone for about twenty minutes. She confirmed that she still wanted Dev to be the main contact, and she agreed that Lina could be told the general outline of the decision without the details of her history. The ethics adviser reviewed the record that afternoon and supported the plan. Lina was unhappy with the arrangement, but she accepted a separate meeting with the social worker. The consent discussion went ahead with Lina present only for the parts Marguerite had agreed to, and the notes recorded each step.
Questions for discussion
- Where would you draw the line between a patient's right to limit disclosure and a family member's reasonable need to know, and what would change that line?
- How would you confirm that a capacity judgment still holds when a consent conversation is delayed by a day or more?
- Which colleague in your service should be the first call when a family member and a patient give conflicting instructions, and what should that call include?
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.