Healthcare Quality, Safety and Infection Control Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
The five cases below are composite scenarios set in fictional facilities. Each puts a team in front of a judgment that sits between a clinical picture and the systems meant to support it: when to escalate, how to hand over a patient, how to ration scarce capacity, what an outcome trend signals, and how to talk with a family when the path forward is contested. Every analysis works through patient needs, the evidence available at the time, team coordination, and applicable protocols. Read them as sequences of judgment, and look for where the process carried the risk.
Case Study 1
A slow drift the ward chart did not show
Thornmere Community Hospital, a 240-bed acute hospital serving a mixed urban and rural catchment.
The situation
Tomas, a retired machinist in his late sixties, was admitted to the medical ward at Thornmere Community Hospital with a respiratory complaint that the admitting team judged to be stable. Over the first two shifts his observations drifted. His respiratory rate climbed, his oxygen saturation sat lower than it had at admission, and he became quieter and less interested in his surroundings. Each nurse recorded the numbers accurately, but the ward's early warning score stayed in the low range because no single parameter crossed its threshold. The overnight doctor was asked about the trend only once, by phone, and was told the patient was comfortable.
The challenge
The team had to decide whether this was a slow change in a frail older man or the early shape of a deterioration that needed senior review. Investigations were available but sat in a queue behind other requests, and nobody had yet ranked them. The escalation protocol asked staff to act on a sustained trend as well as a single breach, but the electronic chart did not display trends, so the pattern was visible only to someone who scrolled back through every set of observations.
Analysis
Teams grounded in Healthcare Quality, Safety and Infection Control usually start by separating what the observations show from what they seem to mean. Tomas's needs were not in question. He needed a clear picture of his breathing, reliable oxygenation, and someone who would notice a change early. The evidence was in the chart already: each observation was small, but the direction over several hours was consistent. A single set of numbers can sit comfortably inside its normal range while a sequence of readings reveals a slope. Reviewing the trend, rather than the latest value, is the habit the protocol was written to build.
The coordination failure was less about any one conversation than about how information was passed along. The nurse who recognized the pattern believed the overnight doctor had been informed, because the day team had mentioned a concern at handover. The doctor, however, received a single phone update framed around a stable overall picture. Under the local protocol, a sustained upward trend in respiratory rate with falling saturation should prompt a bedside review and a documented escalation, regardless of whether any single value crossed the line. Applying it would have changed the conversation from whether the patient was comfortable to what the trend required.
Actions taken
- Add a trend rule to the ward chart so that three consecutive observations moving in the same adverse direction generate a visible prompt for the bedside nurse.
- Require that any handover concern is stated as a specific trend with a named owner for review, recorded on the handover sheet before the shift ends.
- Set a standard script for overnight telephone updates that begins with the trend, the time it started, and what has already been done, so the doctor hears the pattern first.
- Audit every escalation decision made in the next quarter against the protocol, recording whether the trend was documented, and report the result to the ward governance group.
Results
In the first full quarter after the changes, the ward documented 34 escalations based on a sustained trend, compared with 9 in the quarter before. The audit found that the trend prompt fired reliably, but the overnight script was used in only about two thirds of calls, so the team retrained the night staff and added the script to the telephone card at the nurses' station. The ward's review of Tomas's admission concluded that a senior look at the first visible trend would likely have shortened the period of deterioration. The change made the pattern harder to overlook.
Questions for discussion
- Which signals in the chart were available to the night team, and which were visible only to someone reviewing the full sequence?
- How would the telephone update have differed if the overnight doctor had been asked for a decision rather than an opinion?
- What would a trend rule need to avoid so that it generates prompts staff stop reading?
Case Study 2
A pending result missed at the night handover
Larkfield Health System, three hospitals sharing one electronic record and a central patient safety office.
The situation
Ines, a woman in her fifties, was moved to the step-down unit at Larkfield North Hospital after a stay in a higher-acuity area. Her evening handover was given verbally at the bedside and recorded in the electronic handover tool as a short list. One item, a result that had been requested earlier in the day and was still pending, was not on the list. The outgoing nurse had been caring for two other patients during the final half hour, and the incoming nurse did not ask about pending results because the tool's prompt was not part of the unit's routine. The result returned after midnight with a value that needed review by the on-call physician.
The challenge
The gap was small and easy to miss, which is what made it dangerous. The unit's handover template had no mandatory field for pending results, the verbal handover was not timed, and the incoming nurse had a full set of observations to complete in the first hour. The team also needed to decide who owned the pending item once the patient had moved shifts: the day nurse who ordered the request, the night nurse who received the patient, or the on-call physician. The file did not say.
Analysis
Ines needed a result read by someone with the authority to act on it, within a time that matched its significance. The evidence existed in the record, but it sat outside the list that everyone was using to plan the night. Good handover practice treats pending items as a category of their own, because they are the information most likely to change after the giver has left. When the pending result was reviewed, it was the physician's assessment that mattered, and the nurse's role was to make sure the result reached that assessment without delay.
The group protocol asks for a structured handover covering current status, pending tasks, and a named owner for each open item. The unit had adopted the format but had left the pending-tasks field optional, so the form could be finished with the urgent items and nothing else. The incoming nurse was expected to ask questions, yet the unit's culture treated questions at handover as a sign of inexperience. A safeguard that depends on the receiver's confidence is weaker than one built into the form.
Actions taken
- Make pending results a mandatory section of the handover form, with a field for the clinician who owns each item and the time it was requested.
- Require a read-back at the bedside, where the incoming nurse repeats the pending items aloud and the outgoing nurse confirms them before leaving the room.
- Hold a short weekly review of handover near misses on the unit, led by the charge nurse and recorded in the same format as incident reports.
- Set a shared expectation that questions at handover are routine, and have the charge nurse model one question per handover during the first month of the change.
Results
Over the following quarter the unit audited 380 handovers, and the pending-results field was complete in 94 of every 100 at the end of the period, compared with roughly 60 in the audit before the change. The read-back step took about a minute per patient and staff often described it as slowing them down, but the audit showed most missed items surfaced at that step, so it stayed. The near-miss review logged 7 events in the period, and each one traced to a field left blank or an item not read back.
Questions for discussion
- Who should own a pending result when the patient moves between shifts, and how would your unit make that owner visible on the form?
- What would you expect to see in an audit that distinguishes a handover that is complete on paper from one that is complete in practice?
- How can a team make questions at handover feel routine to a newly qualified nurse without turning the handover into an interrogation?
Case Study 3
Monitor allocation during a weekend staffing shortfall
Corvane Regional Health, a network of two acute hospitals and one community site.
The situation
Corvane Regional Health's medical ward at its main hospital ran short of nurses on a weekend in the middle of a seasonal surge. The ward had 24 beds, three vacant nurse positions filled by agency staff who were not yet on shift, and only six portable continuous monitoring units shared across three wards. Eleven patients on the ward had been flagged by the early warning process as needing closer observation. The site's bed manager had two requests from the emergency department for admissions that would need the same monitoring units. The weekend staffing sheet had been drafted before the surge began.
The challenge
The nursing supervisor, Marisol, had to choose how to protect the patients already on the ward without stalling admissions from the emergency department. Monitoring could be concentrated on the highest-need patients, but the early warning process did not rank the eleven flagged patients against each other. Agency staff would arrive mid-morning with no familiarity with the unit, and the ward's escalation contacts were limited to one senior doctor covering two sites.
Analysis
The patients who most needed monitoring were not necessarily the ones who had waited longest. Two patients had early warning scores rising across consecutive sets, and one had a documented history of sudden change despite a stable score. The other eight were low and steady. Allocating monitors by arrival time would have favored the longest wait, which is not the same as greatest risk. The evidence supported a clinical ranking, reviewed at each handover, that weighed the trend, the history, and the concern raised by the patient's own nurse.
The site's surge protocol allowed the supervisor to request cover from a pool of float nurses and to pause elective admissions, but it required a documented risk assessment before either step. Coordination was the constraint. The bed manager and the ward supervisor were not in the same conversation until the second hour, so each was working from a different picture of the ward's capacity. Agency staff needed a structured orientation before they could take responsibility for a monitored patient, and the orientation took time that the ward did not have. Good decisions here depended on making those trade-offs visible to everyone at once.
- 1Flag and rank patientsEarly warning flags were reviewed against trend and history at handover.
- 2Request float coverSupervisor asked the pool for two nurses before pausing any admissions.
- 3Hold non-urgent admissionsEmergency requests were paused for a defined window and redirected where possible.
- 4Move monitors by rankUnits were reassigned to the highest-ranked patients as the board was updated.
- 5Log decisions and reviewEvery pause, cover request, and reassignment was recorded for the end-of-shift review.
Actions taken
- Rank the flagged patients at each handover using a written rule that combines the trend, the reason for the flag, and the bedside nurse's view, then record the order.
- Ask the emergency department to hold non-urgent admission requests for a defined window, and agree in advance which requests the supervisor can escalate to the on-call senior doctor.
- Start agency orientation before the shift begins, using a one-page card that lists the flagged patients, the monitoring equipment locations, and the contacts for escalation.
- Review the surge decisions at the end of the shift with the bed manager present, and log the cover requested, the admissions paused, and the reason for each.
Results
The ward kept all eleven flagged patients under observation for the surge period, but the ranking changed the order in which monitors were moved. Two patients whose scores had been rising were moved to monitored beds within the first hour, and four non-urgent admissions were held for about six hours. Float cover arrived for the second half of the weekend shift, which reduced the number of patients each agency nurse was responsible for. No flagged patient deteriorated without a recorded escalation. The supervisor's summary noted that the hardest part was making the trade-offs visible to the bed manager.
Questions for discussion
- Which information about the flagged patients would have let the supervisor rank them without a second conversation?
- How should a service decide when a shortage justifies holding admissions, and who should be asked before that decision is made?
- What does an agency nurse need to know on arrival before taking responsibility for a monitored patient?
Case Study 4
Why three similar wards reported different infection rates
Brayford Vale Hospital, a 310-bed teaching site with a standing infection prevention committee and an analytics team.
The situation
Over several months the infection prevention team at Brayford Vale Hospital noticed that three medical wards with similar patient mix reported very different rates of hospital-onset infections. The quarterly figures for the wards were anonymized in the report, but the committee could see that one ward had about twice the rate of the other two. Patients on the high-rate ward were not systematically older or sicker, based on the risk adjustment the team used. Staff turnover was higher on that ward, and two of its bays had been rearranged during a building project the previous season.
The challenge
The committee had three possible explanations and limited time to test them. The indicator definitions were the same across wards, but the way cases were identified and reviewed had not been checked against each other. Dorota, the improvement lead, needed to design a review that could separate a true difference in practice from a difference in measurement, without adding a burden that would change what staff did.
Analysis
Patient needs were the anchor. Every patient in the wards deserved the same baseline protection, and the infections in question were ones that a stable system should rarely see. The clinical evidence in the record was thin, though, because the case reviews relied on a single reviewer who had read the notes for the high-rate ward more often than for the others. Before attributing the gap to practice, the team had to confirm that the cases were found in the same way, with the same window and the same definition, and that the review criteria had been applied the same way on each ward.
The infection prevention protocol set expectations for isolation signage, hand hygiene audits, and device review, and each ward reported against it. In practice the ward managers recorded audit results in different ways, and the high-rate ward relied on a rotating group of bank and agency staff whose induction depended on who was rostered that week. A fair comparison needed a shared audit tool, shared sampling days, and a joint review in which the managers saw each other's data first. That is a coordination task before it is a statistical one.
- Week oneJoint review of a shared case sample using one definition.
- Weeks two to fourStandard audit sheet and sampling calendar piloted on all three wards.
- First full quarterPilot data checked for measurement differences before any comparison.
- Each month thereafterTwo measures per ward reviewed against targets and triggers.
- Following two quartersTrigger breaches lead to a practice review and a recorded decision.
Actions taken
- Run a two-week joint case review in which the three ward managers and the infection prevention nurse examine a shared sample of cases using one definition and one tool.
- Standardize the audit sheet and sampling calendar across the three wards, then pilot them for one full quarter before any ward comparison is published.
- Set a monthly indicator review with two named measures per ward, each with a target, an owner, and a trigger for a deeper look at practice.
- Add a monitored induction card for bank and agency staff on the high-rate ward, and track whether it was completed before each staff member's first full shift.
Results
After the joint review, the committee found that about a third of the gap came from how cases were identified and recorded, and the remainder reflected a real difference in audit compliance on the high-rate ward during the period of rearranged bays. The ward's rate fell toward the others over the following two quarters, though the committee was careful not to credit a single change. Compliance with the induction card reached nearly all new starters within the first month, and the monthly review has continued with the same two measures per ward.
Questions for discussion
- Which parts of an indicator definition would you check first before accepting that two wards with similar patients truly differ?
- How should a quality team weigh a finding that a gap is partly measurement and partly practice when both need action?
- What would make a monthly indicator review useful to ward managers rather than something they attend mainly to report upward?
Case Study 5
A daughter's call and a patient's request for privacy
Ridgemont Care Partnership, a community hospital and home nursing service serving a rural county.
The situation
Desmond, a retired teacher in his late seventies, had been on the medical ward for three weeks with a set of long-term conditions that had worsened. The multidisciplinary team recommended a period of step-down care in a rehabilitation unit before he went home. Desmond had capacity, understood the recommendation, and said clearly that he wanted to go straight home with visits from a community nurse. His daughter, Lucia, telephoned the ward twice in one day asking for a full update, and said she was worried he could not manage alone. Desmond had asked the team not to share details of his care with her, and the record contained that instruction in his own words.
The challenge
The team had to balance his right to decide with the safety concern in the recommendation, while respecting his instruction about information without leaving his daughter with nothing. Lucia's worry was real and specific, and it might have carried useful information about how he had been managing at home before admission. The discharge coordinator, Imran, had to decide what could be shared, what should be asked, and who needed to hear about the concern, all within the same afternoon.
Analysis
Desmond had two needs that were not in conflict on paper but were in tension in practice. He needed a safe route home, and the assessments in his record described real difficulty with daily tasks and a recent pattern of unplanned attendances. He also had a clear, informed preference, and capacity is decision specific, so the team's job was to test whether his choice was informed rather than to override it. The assessments had been completed by different disciplines on different days, and the team had not yet brought the findings together in one conversation with him. A shared decision needs that conversation before anyone reopens the question.
The confidentiality position was governed by the service's information sharing policy, which allowed staff to share limited information with family members when the patient agreed, and to share more when the patient lacked capacity and a legal authority existed. Desmond's instruction was clear, so the default was to say nothing specific about his care. The policy also required staff to listen to family concerns and record them, and to escalate a concern to the senior clinician when it suggested a risk to the patient's safety. Lucia's worry was exactly that kind of concern, so the team needed to hear it without disclosing anything.
Actions taken
- Hold a joint conversation with Desmond, with his permission, that brings the physiotherapy, nursing, and social work findings together and sets out the options in plain terms.
- Ask Desmond what, if anything, he is comfortable sharing with Lucia, and record his answer in his own words so the next person does not have to guess.
- Return Lucia's call with a message that acknowledges her concern and explains how the team will respond within the limits Desmond has set.
- Record Lucia's concern and the team's response in the notes, and flag it to the senior clinician for the discharge review, with the reasons for each choice.
Results
Desmond met with the physiotherapist, the nurse, and the social worker the next morning. He chose to go home with community nursing visits three times a week and a daily check call from Lucia, which he had agreed to after the conversation. He also accepted an early review at two weeks. The senior clinician recorded that his decision was informed and that the risk had been discussed with him directly. Lucia was told the team could not share his details, but that her concern had been passed on, and she later told the ward she felt listened to.
Questions for discussion
- When a patient with capacity limits what a family member may hear, what obligations does the team still carry toward that family member?
- How should the team record a decision that the patient makes with capacity but that the team considers risky?
- What would have changed in this case if Desmond had lost capacity during the admission, and who would have been asked to decide?
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.