Pediatric Medicine and Subspecialties Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases come from pediatric services that care for infants, children and adolescents across a hospital and its outlying clinics. Each turns on a decision that seemed reasonable when it was made and grew harder as the facts moved. Together they cover escalation, handover, capacity, quality review and the conversations that arise when a young person and their family see a problem differently. Read each as the team lived it: who knew what, when, which protocol applied, and where the next decision could have gone differently. All organizations and people here are fictional.
Case Study 1
Escalating a toddler who kept getting worse
Marrowby Regional Children's Hospital, a teaching hospital with a 28-bed general pediatric ward and an emergency department that sees about 31,000 children a year.
The situation
Tomas, a two-year-old boy, was brought to the emergency department on a Sunday evening after three days of fever, reduced feeding and a cough that worsened at night. Priya, the triage nurse, recorded observations that sat just inside the range the local tool flags for review rather than for immediate action. Owen, the junior doctor, examined him, documented a probable viral illness and discharged him with written safety-netting advice. Two days later the family returned overnight because Tomas had become drowsy and was refusing fluids. The second visit was recorded in the main department, while the first sat in the urgent care stream, so nobody had linked the two attendances.
The challenge
The team at the second visit had to decide whether two attendances in one week formed a single trajectory, which tests to prioritize given limited overnight laboratory turnaround, and whether to request senior review under the department's deterioration protocol. The first set of observations was not visible on the new record without a manual search. Owen was unsure whether a return after two days should be treated as a continuation of the earlier illness or as a new presentation, and the notes gave no shared answer.
Analysis
Tomas needed a clear reading of his trend more than any single value. His reduced feeding, his cough and now his drowsiness described a child whose reserve was falling, and drowsiness in particular is the kind of change that many pediatric early warning charts weight heavily because it is hard to attribute to a self-limiting illness. Overnight laboratory results would take time, so the decision could not wait for them. Teams grounded in Pediatric Medicine and Subspecialties usually start by asking what has changed since the last time someone looked, then by placing that change against the escalation criteria rather than against the population of children who attend with fever.
The coordination failure was structural before it was personal. Two attendances were filed in different streams, so the record that the second team opened did not carry the first set of observations, and no one was alerted when a child returned within seven days of discharge. The local deterioration protocol asks for senior review when a child meets a combined threshold of altered alertness and poor intake, and it allows the team to request that review directly without waiting for a formal handover. Owen and the nurse did neither at first, not from carelessness but because the protocol was known as a set of numbers and the situation did not announce itself as one.
- 1First attendanceSingle observations borderline; discharged with written safety-netting advice.
- 2Return visitDrowsy and refusing fluids; earlier observations not linked automatically.
- 3Trend reviewCompare both visits against the early warning chart and feeding history.
- 4Senior escalationCombined threshold met; request senior review without waiting for formal handover.
- 5Priority tests agreedTests chosen against current findings and overnight turnaround, not habit.
Actions taken
- Link any return within seven days to the earlier attendance automatically, so the first set of observations appears on the screen before the second assessment starts.
- Add trend language to the triage tool so a falling feeding pattern or new drowsiness prompts a senior review question, not just a numeric flag.
- Teach the deterioration protocol through short case reviews on the unit, practicing the moment a child's story changes between visits, and record the outcome of each review.
- Track return attendances within seven days for three months and review each one at the monthly governance meeting, with the aim that every return is linked to its index visit.
Results
After the record change went live, returns within seven days were linked to their first attendance on screen, and staff reported less searching across streams. In the first quarter, 14 returns were reviewed, and in nine of them the earlier observations changed the escalation decision. Two children were referred for senior review earlier than the old workflow would have allowed. The trend prompt fired in most triage assessments and produced some false alarms, which the charge nurse now reviews at the start of each shift. The case stays in the governance file as a teaching example for new junior staff.
Questions for discussion
- Which elements of Tomas's second assessment would have changed most if the first visit's observations had been on the screen?
- How should a team weigh a falling trend against observations that each look acceptable on their own?
- When is it appropriate to request senior review directly, and what does a local protocol leave to individual judgment?
Case Study 2
A verbal handover that dropped a parent's concern
Ruddock Children's Network, a community and inpatient pediatric service covering two hospital wards and four outpatient centers, with about 3,400 admissions a year.
The situation
Sunita, a nurse in charge on a 22-bed pediatric ward, handed over at the end of a long day shift. One patient, an eight-year-old admitted for observation after a brief episode of altered alertness and vomiting, had improved through the afternoon. His mother had mentioned to the bedside nurse that his breathing seemed faster when he slept, and the nurse recorded it in the nursing notes. The verbal handover covered the medical plan and the next set of observations, but the family's concern was not spoken aloud, and the planned bedside review was not placed on the ward board. The night nurse, Kwame, took the plan at face value.
The challenge
Kwame had a full list and no reason to doubt the handover. The gap was invisible from the plan itself, since the medical notes were complete, and the concern lived only in a nursing entry that the verbal summary had not pointed to. The team needed to trace where the information had travelled, identify which safeguards had held and which had failed, and propose changes that could be measured without adding paperwork to every shift.
Analysis
The child's needs were modest on paper and specific in practice. He had recently been drowsy and vomiting, and a parent's observation of faster breathing during sleep is exactly the kind of information that changes how a team reads a stable set of numbers. Many pediatric services treat a parent's concern as a formal trigger for review because families see children across time and across settings the ward does not. The clinical evidence for the child was reassuring at the time of handover, which is why the concern was easy to lose. A plan built only on the most recent readings tends to drop information that is slow to show up in the observations.
Several safeguards existed and each had a gap. The structured handover template includes a field for family concerns, but the verbal summary followed habit and skipped it. The ward board and the electronic record are separate systems, so a review written in one did not appear in the other. The network's handover standard asks that time-specific actions be recorded with a named owner and read back, and that read-back did not happen. The failure was not one person's lapse. It was the predictable result of three partial safeguards that depended on each other without checking one another.
- Mid-afternoonMother reports faster breathing during sleep; nurse records it in nursing notes.
- End of day shiftVerbal handover covers the medical plan and observations, not the family's concern.
- Shift changeNight nurse accepts the plan; bedside review missing from the ward board.
- About ninety minutes laterObservations stable; the concern is found only by chance in the nursing record.
- Next morningIncident reported; review finds no harm, a clear near miss, and two process gaps.
Actions taken
- Make the family concern field a required line in the verbal handover script, read aloud by the outgoing nurse and repeated back by the incoming nurse.
- Post every timed observation or review on the ward board at the moment the plan is written, with the owner's initials, so the board and the record cannot disagree.
- Audit 40 handovers each month against the template, scoring read-back, named owners and family concerns, and share the results with the night and day teams.
- Track the proportion of handovers with all required items completed, aiming above 90 percent within two quarters, and review each missed item with the team that made it.
Results
Within the first two months, the template field was completed in 31 of 40 audited handovers, rising to 37 of 40 by the end of the quarter. The ward board and the record matched in every audit after posting moved to the time the plan is written. The child in the original event went home after an uneventful night, so the event was a near miss rather than a harm. Night nurses also began asking families directly what they had seen, a habit the audit did not measure but staff described as the most useful change. Two shifts still missed read-back, and a short reminder card at the station has been added for those teams.
Questions for discussion
- Which single change to the handover would have been most likely to surface the family's concern, and what would it cost the outgoing nurse in time?
- How should a team decide whether a parent's observation has enough weight to delay a plan that the medical notes support?
- What would a reliable check between the ward board and the electronic record look like in a service that uses both?
Case Study 3
Allocating six monitored beds during a demand surge
Oakhollow Child Health Service, a pediatric group with a six-bed monitored bay, two general wards, and a subspecialty clinic that books about 1,800 follow-up visits a month.
The situation
Over one busy stretch, referrals to the high dependency bay rose sharply after several children arrived with breathing difficulty within the same two days. All six monitored beds were occupied by the second evening. Two of the bay's specialist nurses were off sick, and the bed manager, Ruth, had only one agency nurse available for the night. Three patients were ready to be considered for a lower-acuity bed, but two needed continuous observation of breathing effort and oxygen saturation for the next several hours. Meanwhile a child in the emergency department was waiting for a monitored bed, and the subspecialty clinic still had a full morning list of routine reviews.
The challenge
Ruth had to decide who kept a monitored bed, who could step down, and whether the clinic list should move, without any of these choices compromising the children already in the bay. Each option carried a different risk: moving a child too early, leaving a monitored bed empty while nursing cover was thin, or deferring routine care in a way that just pushed demand into the next week. The protocol for minimum staffing on the bay was unclear about what counted as a safe ratio with an agency nurse.
Analysis
The children in the bay needed continuous observation because their breathing could change faster than a scheduled check would show. Clinical judgment about step-down rests on trend, response to the current level of support, and confidence that the next few hours will be quiet. A child who looks settled at one reading but has needed frequent adjustment over the previous shift should not move on the strength of a single number. Equally, a child held in a monitored bed longer than necessary takes capacity that another child with the same needs may be waiting for. The decision works best when the bedside nurse and the registrar describe the same trend.
Three levers were available, and each protects quality differently. Triage by acuity decides who needs the monitored bed first, and it is the only lever that works on the same night. Scheduling is slower: the clinic could move routine reviews to telephone or video, which frees clinician time without touching the bay. Resource allocation means moving staff, and here the minimum staffing protocol set the limit. The bay's protocol says no monitored bed is held without a named nurse, so redeploying from the wards would have left them below their own ratio. Ruth therefore treated staffing as the constraint and moved the clinic first.
Actions taken
- Write down the minimum nurse-to-patient ratio for the monitored bay, and a stop rule that halts new admissions to it when the ratio cannot be met.
- Hold a fixed bed huddle at the same time each day with the bed manager, charge nurse and on-call registrar to review step-down candidates against written criteria.
- Switch non-urgent subspecialty reviews to telephone or video when the surge threshold is crossed, and notify families of the change with a named contact.
- Record every allocation decision and its reason in a shared log, then review the log at the end of each surge to find where criteria were unclear.
Results
The surge lasted eleven days. Two children stepped down to the general ward after their reviews, with a named nurse assigned on arrival. The routine clinic list moved to video for three weeks, and 41 follow-ups were completed without the waiting list growing beyond the agreed limit. One night the bay dipped below its minimum ratio for about two hours before the agency nurse arrived, and the stop rule halted new admissions for that period. The log recorded the decision and its reason. The team agreed the minimum ratio needed a clearer statement for agency staff.
Questions for discussion
- How should a unit decide between a falling ratio and a waiting child when both carry real risk, and who should own that decision?
- What evidence would convince a team that a step-down criterion is too loose or too strict for its own patients?
- How might a clinic that defers routine care support the families who feel the delay most directly?
Case Study 4
Explaining uneven early returns from an assessment unit
Calder Valley Family Health, a pediatric network with a medical assessment unit at its main site and three feeder clinics, serving about 46,000 children across mixed rural and suburban areas.
The situation
Calder Valley's medical assessment unit receives children from three feeder clinics and from the emergency department, and most leave within a day. The network's quality group reviewed anonymized indicators for children discharged from the unit and found that the rate of unplanned return within three days differed across the three feeder sites, at roughly 5 percent, 9 percent and 14 percent. The sites shared one discharge protocol, but the group could not yet tell whether the gap reflected different children, different practice, or the way returns were recorded.
The challenge
The indicator said where the differences were but not why. Small numbers at each site meant that a single unusual month could move a rate noticeably, and the quality group was aware that a naming exercise would damage trust with the clinics. The team needed to separate case mix from process, find the process steps that actually differed, and design a change that clinicians would use and that could be monitored over several months without another large audit.
Analysis
Children returning within three days are not all the same group. Some return because the illness evolved as expected, some because a warning sign was missed or explained poorly, and some because the family could not get advice in the first hours at home. Comparing sites therefore needs adjustment for age band, presenting complaint and time of discharge, because a unit that takes more infants or sees more complex discharges will show more returns for reasons that are not process failures. The clinical evidence on discharge safety-netting is mixed, and most of it describes content rather than outcomes, so the network treated its own indicators as a starting point, not a verdict.
Process differences were more likely to explain the gap. Discharge summaries varied in whether they named the warning signs in plain language, and the safety-netting advice was sometimes given verbally and sometimes in writing. The follow-up telephone call the protocol recommends was made on the working day after discharge at one site and on whichever day the nurse was free at another. Weekend staffing differed as well, with one feeder clinic running a reduced discharge team on Saturdays. Each difference looks small in isolation, but together they describe a set of shared instructions that were being carried out in different ways.
- Plan the change Agree the template wording and the next-day call with clinicians from all three sites.
- Pilot one site Run the pilot for eight weeks while the other sites keep usual practice.
- Study the data Compare return rates and sampled summaries against the baseline and comparison sites.
- Act or adjust Spread the change if the signal holds, or revise the template before trying again.
Actions taken
- Re-cut the indicators by age band, presenting complaint and day of discharge, so that each site is compared with children of similar need rather than with the network as a whole.
- Score a sample of 60 discharge records per site against the shared protocol, checking for named warning signs, written advice and a booked follow-up call.
- Pilot one discharge summary template and a next-working-day call at a single site for eight weeks, with the other two sites continuing usual practice as a comparison.
- Plot the return rate monthly on a run chart and set a stop rule: if the pilot site's rate rises above its baseline for two consecutive months, the team reviews the template before spreading it.
Results
The pilot ran for eight weeks at one site. The return rate there moved from about 9 percent to about 6 percent, a change the team regarded as encouraging but too small to read as settled given the volume. The comparison sites showed no clear change. The next-day call was completed for most discharges at the pilot site, and the warning signs were named in every sampled summary. The run chart is still being watched, and the team has agreed to repeat the scoring at the other two sites before any wider rollout.
Questions for discussion
- Which of the three explanations for the site gap, case mix, process or recording, would be hardest to test with the indicators already collected?
- How can a quality group share uneven results with the sites involved without creating a ranking that undermines the work?
- What would make a run chart more useful than a single before and after comparison for a change that may only move a rate slightly?
Case Study 5
Confidential conversation with a teenager and parents
Pellham Valley Pediatric Group, a regional service with a specialist clinic for long-term conditions and a shared social work and psychology team.
The situation
Mireille, fifteen, has attended a specialist clinic for a long-term condition since she was small. Her parents have managed her attendance and care routine, and at a recent review Mireille told Hannah, the consultant, that she no longer wanted her parents to make decisions about her follow-up, and asked for part of the next appointment to be held without them. Her parents, Lauren and Joseph, disagreed with a proposed reduction in monitoring and were worried about missed visits. Hannah had to weigh Mireille's stated wish, her parents' concern, and clinical information showing that reduced monitoring carried real risk if the condition changed without warning. The specialist nurse, Tunde, and the social worker, Ines, had both met the family.
The challenge
The conversation had three parts that pulled in different directions. Mireille's request for privacy was legitimate for her age and understanding, but a confidentiality promise could not be made without knowing where it would lead if she disclosed a risk. Her parents needed to be heard without being excluded from decisions they still carried responsibility for. The team had to decide what to say in the room, what to record, and when the case should go beyond the clinic's own senior review.
Analysis
Mireille's wish deserves serious weight. At fifteen, a young person can often understand a plan, weigh its consequences and express a stable preference, and in many settings her view counts even while her parents keep formal responsibility. Capacity is decision specific, though, and it is not established by age alone. The team needed to test whether she understood the risk of reduced monitoring, whether her preference was consistent across conversations, and whether pressure from either side had shaped it. The clinical evidence was real but not decisive, and the conversation needed to be honest about what was known and what was not.
Several duties applied at once and do not resolve neatly. The duty to respect Mireille's autonomy and to talk with her alone is real, and so is the duty to share information with her parents where it bears on her safety and where she agrees. Confidentiality limits in local policy should be explained before she discloses anything. Communication choices mattered here: Hannah planned to open the appointment with both parents present, state the boundaries of privacy plainly, hold a short private part with Mireille, and then bring the parents back for a shared plan. Escalation was built into the protocol: if the private conversation revealed a risk to her safety, the social worker and the clinic's senior review would take over.
Actions taken
- Open the appointment with both parents present, state the limits of confidentiality in plain language, and agree the private part before anyone goes into the room.
- Hold a private conversation with Mireille using a set of standard questions on understanding, consistency of her wish and any pressure she feels, and record her answers in her own words.
- Agree in advance with the social worker and senior consultant the point at which a safeguarding concern would be escalated, and tell Mireille and her parents that this threshold exists.
- Hold a joint review within two weeks to agree a shared plan, with a named contact, a written record of what each person decided, and a date to revisit the question.
Results
Mireille had her private time, and she spoke about feeling that her views were dismissed at home. Her answers were consistent across two conversations, and the team judged that she understood the risk of reduced monitoring. The private discussion did not reveal a safety concern, so the case stayed within the clinic's own process. A joint review was held and the plan was adjusted: monitoring was reduced for one period with a named contact and a scheduled check, and Lauren and Joseph agreed to a regular family meeting. The case is not closed, and the question will be revisited at the agreed date.
Questions for discussion
- How should a team test whether a young person's understanding is stable enough to support her preference, without treating her age as the answer?
- Where is the line between respecting confidentiality and sharing information that a parent needs in order to keep a child safe?
- What should a team do when the private conversation and the joint conversation seem to point toward different plans?
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.