Healthcare Administration and Hospital Management Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
Hospital administration sits between clinical judgment and the systems that let it work. The five cases below involve fictional organizations, but the pressures will be familiar to anyone who has run a ward roster or an escalation policy. Each case gives a situation, the challenge that followed, two analysis passes that look at patient needs, clinical evidence, team coordination, and the protocols that apply, four actions taken or proposed, the results, and three questions for discussion. Watch for where information got lost, who held authority to act, and which safeguard was meant to catch the problem.
Case Study 1
The slow climb on a medical ward
Alderpoint Regional Hospital, a 380-bed teaching hospital with four adult medical wards and a rapid response team
The situation
On a Tuesday evening shift, the nurse caring for a 71-year-old man admitted two days earlier under general medicine noticed that his breathing rate and oxygen requirement had drifted upward across three sets of observations. His early warning score rose from 3 to 5 over about four hours. That was still below the escalation threshold in the ward protocol, which calls for an urgent medical review at 7. The charge nurse, Dana, was covering 26 patients across two units, and a transfer from the emergency department was waiting. The covering resident had been called to a different ward twice that shift. Nobody was obviously wrong, and that was part of the problem.
The challenge
The team had to decide whether a score still under the threshold, paired with a trend no single observation captured, justified calling for review now. Dana wanted the resident to see the patient in person rather than by phone, but the resident was not free for another hour. The daughter, who was at the bedside, asked twice whether someone would look at her father again. The team had to balance an escalation that might be unnecessary against a delay that might cost time they could not recover.
Analysis
Teams grounded in Healthcare Administration and Hospital Management tend to read the trajectory before the threshold. The most useful evidence in this case was the direction of three consecutive observations, not any single value, and the rising oxygen requirement that the nurse documented alongside them. The escalation policy gave the nurse a firm floor, but it also contained a clause allowing any staff member to call for review on clinical concern regardless of score. That clause was rarely discussed on the ward. Patient needs here were timely reassessment and a family that felt heard, and neither was served by waiting for the score to cross the line.
Coordination failed less through neglect than through unclear ownership of the decision. The nurse assumed the charge nurse would make the call, the charge nurse assumed the resident would see the patient before the next round, and the resident was managing a deteriorating patient elsewhere. A structured step, a spoken statement of the trend and the response being requested, would have put the question in front of someone with authority. The ward's protocol already named a rapid response pathway for concern without a score threshold, but staff had rarely used it, and the policy assumed nurses would know when a concern was clinical enough to justify it.
Actions taken
- Add a required escalation statement to the early warning chart, asking the nurse to name the trend and the response requested before the score is accepted as final.
- Run a fifteen minute simulation for each ward team on using the clinical concern pathway, with the charge nurse and covering resident in the same session.
- Require a called resident to give a review time, and hand any open concern to a named colleague if that time slips beyond thirty minutes.
- Review escalation timing monthly against the ward's own data, tracking time from first abnormal trend to documented review, and report the median to the nursing governance group.
Results
Within the first two months after the changes, the ward logged more rapid response calls, most judged reasonable in retrospect. Median time from first documented abnormal trend to a completed review fell from ninety minutes to under forty. Staff reported that the required statement made them slower to dismiss a patient, though some found the extra step tedious on busy shifts. The daughter was contacted at each review, and her complaint about waiting did not recur. The group kept the simulation and will review whether the thirty minute rule adds pressure on residents already stretched across units.
Questions for discussion
- Which parts of the escalation policy depended on individual judgment, and how would you test whether staff understood them?
- How should a service decide when a trend deserves review even though no single measure has crossed a threshold?
- What would need to change about resident workload before a thirty minute review window becomes realistic?
Case Study 2
A handover that left out the pending question
Corvane Valley Medical Center, a 460-bed hospital with a surgical ward, a step-down unit, and a shared transfer desk
The situation
A patient in his sixties was moved from the surgical ward to the step-down unit late in the evening, after a planned operation. The outgoing nurse gave a verbal handover at the bedside and wrote a summary in the electronic record. Both covered the patient's vital sign trend, his current monitoring plan, and his mobility. Neither mentioned that a blood test requested earlier in the day had not resulted, or that the surgical registrar had asked for the result to be reviewed before a decision about his next step. The receiving nurse, Gwen, did not know the result was pending. The gap surfaced when the morning team asked for the result.
The challenge
The receiving team had no reason to suspect a gap, because the handover looked complete and the patient was stable on arrival. The outgoing nurse had been on shift for twelve hours and had left the result off a list of open items. The registrar had not documented the request in the task list, only in a conversation at the nurses' station. Any fix had to work at two in the morning when staff were stretched, and it had to satisfy the hospital's safety policy requiring documented handover of pending investigations.
Analysis
The patient's needs at transfer were ordinary on paper: a stable set of observations, mobility with help, and a plan that the record described in detail. What the record did not carry was the open question. Pending results are part of the clinical evidence a receiving team needs, because they determine whether the next decision is ready to be made or is waiting on someone. Here the evidence existed in the laboratory system and the registrar's request existed in a verbal exchange, so two sources of truth each held half of the picture. Neither was wrong. Together they created a gap that no single reviewer would have seen.
The hospital's handover standard requires a structured tool, a bedside exchange for high-risk transfers, and a documented list of pending investigations with a named owner. The surgical ward followed most of it. The gap came from the third element: the registrar's request lived in conversation, so it never reached the task list that the protocol treats as the handover record. Coordination depended on memory at every step. A check-back, in which the receiving nurse repeats back the open items and the outgoing nurse confirms them, is the safeguard the policy describes, but the unit had dropped it during busy periods because it added minutes to every transfer.
- 1Verbal request madeRegistrar asks for the result to be reviewed before a decision.
- 2Task list omissionConversation at the nurses' station never reaches the electronic record.
- 3Summary omits open itemWritten handover covers trends and plan but not the pending question.
- 4Bedside exchange onlyBedside exchange runs without a check-back to confirm open items.
- 5Gap found by morningTeam asks for the result and finds it still unreviewed.
Actions taken
- Make the pending investigations list a required field in the transfer form, so that an open result cannot be left off by omission.
- Require any verbal request from a senior clinician about a pending result to be entered as a task before the end of that shift.
- Restore the two minute check-back at the bedside for transfers out of surgical wards, and audit whether it happens on every eligible transfer.
- Track the rate of transfers with an unreviewed result at arrival each month, with a target of zero, and present the trend at the patient safety huddle.
Results
In the first quarter after the changes, the transfer form flagged open results on most transfers, and the audit found that the bedside check-back took place on roughly four in five eligible moves. Two transfers still arrived with an unreviewed result in that period, both caught within the hour. The safety huddle agreed to count near misses alongside actual delays, since the first measure alone would have missed the cases caught by luck. Gwen said the check-back felt slower at first, but that the receiving team now asked better questions.
Questions for discussion
- Which elements of a handover standard are most likely to be skipped under pressure, and what data would reveal that skipping?
- How should a unit decide whether a verbal request from a senior colleague counts as part of the formal handover record?
- What trade-offs does a bedside check-back create for a receiving team that is already managing its own admissions?
Case Study 3
Imaging queue during an unplanned staffing gap
Thornhill Valley Health Services, a three-site network with a main campus scanner suite and a satellite clinic
The situation
In the third week of a cold season, the diagnostic imaging department at Thornhill Valley saw referrals rise about a fifth above its usual weekly volume. At the same time, one of its three scanners went out of service for an unplanned repair, and two of the six sonographers were on leave with no cover booked. The waiting list for routine outpatient studies grew from about 400 to over 600 within ten days. Referrals were marked urgent, routine, or soon, but the marking was done by the referring clinicians and was not always consistent. Thornhill's operations manager, Marcus, had to decide where scarce scanner time and staff hours should go over the coming fortnight.
The challenge
The options were not equal in risk. Moving everyone to the oldest request would clear the queue but might leave a suspected urgent case waiting behind routine follow-ups. Extending evening hours depended on overtime from sonographers already stretched, and the satellite clinic's scanner could take some work but needed a radiographer who was off that week. Marcus also had to avoid a pattern in which urgent referrals were quietly reclassified to routine to get them seen sooner, which would make the waiting list look shorter than it was.
Analysis
The patient need at the center of this problem was timely access for studies that change a near-term decision. The referral marking was the only structured evidence, and it was unreliable in a predictable way: clinicians marked a referral urgent when they were worried, and the same worry appeared in different words across the three sites. A triage tool with clear criteria, reviewed by a radiologist, would convert that inconsistency into something the scheduler could act on. It would not remove judgment. It would make the judgment visible, so a routine referral with a red flag could move up without a call to the referrer.
The department's access policy ranks urgent and soon referrals ahead of routine studies and requires that any change in priority be documented with a reason and the name of the person who made it. Those rules were sound, but the policy assumed a sonographer or scheduler could reach a referring clinician within the working day, and during the shortfall that was often not true. Staff coordination also suffered from the lack of a shared daily huddle across the three sites. Each site was making reasonable local choices that, added together, moved routine work unevenly and left the main campus scanner overbooked.
- First two daysUrgent list reviewed and scanner time protected for suspected cases.
- Day threeCross-site huddle starts; routine work begins moving to the satellite.
- End of first weekScanner returns after quality check; overtime cap takes effect.
- Second weekTriage checklist applied at booking; reclassifications reviewed weekly.
- End of the fortnightWaiting list reviewed against the plan and shared with clinicians.
Actions taken
- Adopt a short triage checklist with clear criteria for urgent and soon referrals, reviewed by a radiologist, and apply it at booking rather than after the study is requested.
- Hold two daily cross-site huddles during the shortfall, with the scheduler, a sonographer lead, and one radiologist, to rebalance routine work before the afternoon list is set.
- Move routine studies to the satellite scanner on two half days a week, only for patients whose referrals are already reviewed as routine and whose travel is confirmed.
- Cap voluntary overtime for sonographers at a fixed number of hours per fortnight, and bring the repaired scanner back only after a documented quality check of image output.
Results
Within the fortnight, urgent and soon referrals were seen within their target windows, and the number of urgent referrals reclassified during the period fell to a handful, each with a recorded reason. The routine waiting list stopped growing, then came down by about a third, though it did not return to its earlier level before the period ended. Overtime stayed within the cap, and two sonographers said the fixed limit made it easier to refuse extra shifts without guilt. The satellite scanner ran below plan, mostly because patients on the routine list had not confirmed transport.
Questions for discussion
- When a triage checklist and a clinician's judgment disagree, which should the scheduler follow, and who should be told?
- What would a fair fallback look like for a patient whose satellite appointment is cancelled because transport was not confirmed?
- How would you show a hospital board that protecting urgent work came at a real cost to routine timeliness?
Case Study 4
Uneven return visits across four medical wards
Sennet Harbor Hospital, a 310-bed acute care hospital with four adult medical wards and a shared discharge office
The situation
Over most of a year, the quality office at Sennet Harbor noticed that unplanned return visits within thirty days of discharge varied widely between the four adult medical wards. The rate on the best ward was about half the rate on the worst. The wards admitted similar patient mixes by age and diagnosis group, but the quality team had not adjusted for severity. Ward managers each had a theory: one blamed late afternoon discharges, another blamed the community nursing referral process, and a third suspected documentation. Data were pulled from the record for 1,240 discharges across the period, with names and identifiers removed before review.
The challenge
Real differences in care had to be separated from differences in who was discharged and how outcomes were recorded. Anonymized indicators could show that one ward had more returns, but not why. A quality improvement effort that jumped to a fix, such as moving the discharge time or adding a call, could disrupt wards that were already performing well. The team also had to avoid a process in which a single ward became the scapegoat for the hospital-wide average.
Analysis
Patients who return within thirty days are often people whose discharge plan had a weak point: a medication question nobody answered, a follow-up booked for a day the patient could not attend, or a community nurse who had not received the handover. Those needs are specific and checkable. The indicator alone does not show them. The team pulled a sample of returns and matched each to the discharge summary, the time the summary was sent, and whether the patient had a documented teaching conversation. Early patterns were suggestive but not conclusive, because the sample was small and some summaries had been filed under the wrong ward.
Discharge protocol at Sennet Harbor requires a summary to reach the patient's primary clinician and the community team on the day of discharge, along with a teaching record covering the plan in plain language. Wards met the first requirement in about nine of ten discharges according to the audit, but the timing varied sharply. The ward with the highest return rate sent summaries late in the afternoon, often after the community referral had been triaged for the next morning. Coordination across the discharge office, the wards, and community services depended on whoever was on shift, and no one owned the handover standard across all four.
Actions taken
- Adjust the return rate for severity and age using a standard case-mix method, and publish both the raw and adjusted rates for each ward each month.
- Start a plan-do-study-act cycle on summary timing, aiming for summaries sent before the afternoon community triage, with a weekly run chart shared with ward managers.
- Introduce a single teaching record template with five fixed fields, and sample twenty completed records per ward each fortnight to check completeness.
- Name one owner for the handover standard across all four wards, with a balancing measure tracking discharges delayed by the new timing rule.
Results
After three cycles, the summary timing measure moved in the right direction on the highest-return ward, and the gap between best and worst wards narrowed on the raw measure but held steady after adjustment. That was an important finding: part of the difference was real process variation, and part was severity. The teaching record sample showed completeness rising from about six in ten to nearly nine in ten. The balancing measure showed a small rise in afternoon discharge delays, which the group judged acceptable for now and planned to revisit.
Questions for discussion
- Which indicators should a hospital publish without adjustment, and which only after severity adjustment, to avoid misleading ward comparisons?
- How would you decide whether a small sample of returns is enough to justify changing a discharge process?
- Who should own a standard that crosses several wards, and what authority does that owner need to enforce it?
Case Study 5
Confidentiality and shifting capacity on a medical ward
Calder Ridge Regional Hospital, a 240-bed hospital with an ethics consult service and a patient advocacy office
The situation
A woman in her late seventies was admitted to a medical ward after a fall at home, and her ability to follow discharge conversations came and went. On good days she was clear that she wanted to return home with support. On other days she became confused about where she was and who had visited. Her husband, who was her main carer, asked the team for a full update on her condition and plan, and said he should be the one to decide where she went next. The patient had told a social worker earlier that she did not want her husband to know the details of a private matter that had come up in the assessment.
The challenge
The confidentiality request, made on a good day, still deserved weight, and the team could not assume her capacity had lapsed. Sharing information without her agreement could break trust and the duty of confidentiality. Refusing her husband any information could leave him unable to plan for her safe return, and the ward had already received two complaints about poor communication from families that week.
Analysis
Her needs were both practical and personal. She needed a safe discharge plan, and she needed a decision made on her own terms. The evidence the team could rely on was her own recorded statements, which were consistent on good days, and the notes of a senior clinician's assessment of decision-specific capacity carried out at a time when she was clearer. Fluctuating presentation does not mean the request is void. It means the team has to time its conversations, record what she understood, and check whether her preference holds on the days when she is able to state it, rather than letting one day define the whole picture.
The consent and capacity policy places the duty to assess decision-specific capacity with the treating clinician, requires confidentiality requests to be recorded with scope, and says a family member may be given information only where the patient agrees or where disclosure is needed to protect her. The social worker had recorded the request but not its scope, and the ward nurse did not see it in the handover. The husband's role as carer was real, but it did not give him authority to decide for her. Escalation options included a second senior opinion, the ethics consult service, and the patient advocacy office, which could support her in stating her wishes.
- Assess capacity Repeat the decision-specific assessment during a period of clear engagement.
- Record the scope Write down exactly what may be shared and with whom.
- Meet with family Explain limits, with the patient present where she agrees.
- Escalate promptly Ethics consult and advocacy referral within one working day.
Actions taken
- Ask the treating clinician to repeat the decision-specific capacity assessment during a period when she is recorded as engaged, and to write down the exact scope of what she wants shared.
- Meet the husband with the patient present where possible, explain the limits of what can be shared, and agree a plan for the information she has agreed to share.
- Refer the case to the ethics consult service and the patient advocacy office within one working day, recording the question as a conflict between confidentiality and family involvement.
- Add a confidentiality flag and scope field to the ward handover template, so that any restriction on information sharing reaches the nurse on every shift.
Results
The capacity review was repeated in the second week, when the patient was judged able to state a clear preference about going home with a package of support, and it was recorded with the specific information she agreed to share. The husband received an update on the plan and the practical arrangements, but not on the private matter. He was unhappy about this and said so, and the ethics service spent time with him explaining the reasoning. The patient later said she felt the team had listened, and the complaint about communication was withdrawn.
Questions for discussion
- How should a team record a patient's confidentiality request when the request is made during a period of reduced engagement?
- What would you say to a spouse who believes his role as carer should give him full access to information?
- At what point does an unresolved disagreement between a patient's wishes and family expectations justify formal escalation, and who should make that call?
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.