Neonatology and Newborn Care Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
Neonatal units run on small signals: a feed that takes longer than expected, a temperature that drifts, a handover that leaves out one line. The five cases below come from fictional services and follow the decisions that shape outcomes for newborns and their families. Each one asks what the team knew at the time, who was responsible for acting on it, and which local protocols set the limits of their options. Read them as a practitioner would, looking for the point where information existed but did not travel. Every case closes with questions for discussion among colleagues.
Case Study 1
Nine hours of small changes before escalation
Larkfield Regional Maternity and Newborn Center, a tertiary unit with 32 cots, a transitional care bay, and an on-call registrar rota.
The situation
A term infant was moved to the transitional care bay in the first afternoon after delivery for observation following a difficult start. Over the next nine hours, the bedside nurses recorded a gradual rise in respiratory rate, feeds that were stopping before the planned volume, and a change in skin color that was easy to miss under the bay lighting. Each reading sat just inside the printed thresholds, so no single entry triggered an automatic review. The evening nurse handed over a picture that looked stable. The on-call registrar, Priya, was reachable by phone but was attending a delivery and could not come to the bedside. Parents were asking whether their baby could go home the following morning.
The challenge
The bedside team had to decide whether a set of acceptable readings added up to a changing condition. Feeding records, the observation chart, and the nurse's own unease all pointed the same way, but the unit's early warning tool scored each parameter separately, so none of them crossed a line. Nobody had written a concern down. The team needed to decide whether to request senior review now, which checks to prioritize, and how to describe the uncertainty to parents who had been told their baby was doing well.
Analysis
The patient's needs here were defined by a direction of travel, not a single threshold. A slowly rising respiratory rate, incomplete feeds, and a change in color each have ordinary explanations early on, so the evidence has to be read together and over time. Teams approaching Neonatology and Newborn Care tend to start by writing the trajectory in plain sentences, then asking which observation would change first if the baby were getting worse. Prioritizing is a question of information value: which single check would most alter the plan without pulling a nurse away from another cot. A trend that is not written down cannot be seen by the next person who opens the chart.
The local deterioration protocol offered two routes. A single parameter outside its printed range required the bedside nurse to call the registrar at once, while a cluster of smaller changes was meant to prompt a documented review within a set period. The team had used neither route because the cluster was spread across three chart sections and two shifts, and no one had put it in one place. Escalation depended on a shared picture that did not yet exist. A short structured call, using the same headings every time, would have let the registrar hear the trend, the nurse's concern, and what the parents had been told in one exchange. The protocol assumed a summary that the team had no habit of producing.
- Afternoon admissionMoved to transitional bay for observation after a difficult start.
- Hours one to threeRespiratory rate edges up; feeds stop short of planned volume.
- Hours four to sixColor change noted, but each reading stays inside printed limits.
- Evening handoverOutgoing nurse describes a stable picture; concern never written down.
- Registrar phonedRegistrar unable to attend; review deferred while attending a delivery.
Actions taken
- At each observation round, the bedside nurse writes a one-line trend summary covering direction of change across the last few readings, not only the latest values.
- When calling the registrar, use a fixed structure: observations over the last six hours, the feeding pattern, the nurse's concern, and what the parents have been told.
- Agree a time limit for documented senior review whenever a cluster of mild changes appears, and record both the decision taken and the reason for it.
- Hold a brief joint debrief with both shifts comparing the picture at handover with the picture at escalation, then add the findings to the protocol review.
Results
The registrar came to the bedside within the hour, reviewed the trend with the nurse, and requested a set of checks that had not been ordered overnight. The baby stayed in the unit for closer observation, and the plan to discharge the next morning was withdrawn. The parents were told that the team was watching a pattern across several readings rather than reacting to one alarming value, and they agreed to the revised plan. In the following quarter, the unit's audit found no further delayed reviews of this type in the sample examined, although the sample was small and the team chose not to present the result as proof that the problem was solved.
Questions for discussion
- Which observations in this case were each within range, and how should a team weigh a group of them that point the same way?
- What would a one-line trend summary need to contain for a registrar to decide on the phone whether to attend in person?
- How should a unit balance the speed of escalation against the cost of calling senior staff for changes that turn out to be normal?
Case Study 2
A handover gap that nearly changed a feeding plan
Ridgeway Newborn Unit, a 28-cot special care unit attached to a community hospital with a shared nursery.
The situation
On a busy weekday the day team handed over the care of a preterm infant to the night team at the change of shift. The verbal handover was given by a nurse who had been asked to cover a second room at short notice. The written handover sheet listed the baby's current observations and the feeding plan in force that morning, but a change made in the early afternoon was recorded only on the main chart. A laboratory result requested later that day was still pending, and it was not mentioned at the bedside. The night nurse, Tomasz, relied on the sheet. The mismatch surfaced only when the overnight feed volume did not fit the sheet.
The challenge
The team needed to establish what had actually been given and what was still outstanding, without assigning blame before the facts were clear. The handover tool had no required field for pending results or for plan changes made during the day. Staff on both shifts were tired and held different views about who should close the loop. The unit manager, Dara, had to decide whether this was a single lapse or a gap in the system, and what to change before the next weekend roster was set.
Analysis
The baby's needs centered on feeding, monitoring, and an open result, so the handover carried three jobs and only one was written in a usable form. The evidence was there once someone looked: the plan had changed, the overnight record did not match it, and the result had not returned. The safety question is what the receiving team needed to act without rebuilding the picture. A useful handover describes what is in motion and names who owns it, not only the current state. Experienced staff find that the most dangerous gaps sit between documents, because each one looks complete when read alone.
The handover protocol used a verbal summary and a written sheet, and both nurses signed it. It did not say how daytime changes should be carried forward or require pending results to be listed separately. The verbal handover was rushed, so the written sheet became the only reliable source, and it was out of date. The night nurse had no reason to doubt it, which is why the safeguard belonged in the form, not in memory. Every pending result needed a named owner until a clinician had reviewed it.
Actions taken
- Add two required fields to the handover sheet, one for care plan changes made that day and one for results requested but not yet returned, each with a named owner.
- Ask the receiving nurse to read the feeding plan and any open results back to the outgoing nurse before accepting the handover, and record that the read back happened.
- Audit a random sample of handovers each week, comparing the chart against the sheet, and report the rate of mismatches at the monthly unit meeting.
- Protect the handover window from new admissions and cover requests where possible, and log each interruption so that the pattern becomes visible to the unit manager.
Results
The senior nurse on duty reviewed the plan with the night team before the next feed, and the feeding plan on the sheet was corrected to match the chart. The pending result returned later in the shift and was reviewed without delay. Over the following weeks, the weekly audit found mismatches in roughly one handover in five at the start, falling to about one in twenty after the form was revised. The read back step was not always completed, and the unit recorded this as an open issue rather than a solved one.
Questions for discussion
- Which items in a handover are most likely to be lost when the verbal summary is rushed, and what makes them easy to drop?
- Who should own a pending result when the clinician who requested it has gone off shift, and how should that be recorded?
- What would persuade a busy team that a read back step is worth the time it takes at the bedside?
Case Study 3
Managing a full unit during a weekend surge
Brightwater Neonatal Unit, a 22-cot special and intensive care unit in a mid-sized hospital with a single transport team.
The situation
Over a weekend, admissions from the labor ward rose and by the second afternoon nineteen of the 22 cots were occupied. Two babies needed close observation while a third was being prepared for transfer to a community hospital. Staffing had been planned for a quieter weekend, and one nurse was on sick leave. The unit had five monitored stations rather than the seven its cots would suggest, so not every occupied cot had continuous observation. A neighboring hospital then asked whether the unit could take a transfer of a baby needing intensive support. The charge nurse, Gwen, had to decide what could be accepted, what could wait, and what the staff on duty could safely cover.
The challenge
Accepting the transfer would have meant the unit ran above its safe staffing ratio for the rest of the shift, and declining it would leave a baby in a hospital without the same level of support. The team had to compare options: holding the transfer, opening an overflow area with a reduced ratio, moving a planned discharge earlier, or asking the transport team to bring the baby to a different unit. Each option carried a different cost for the babies already in the unit.
Analysis
The patients already in the unit had a stronger claim on staff time than the incoming baby, but that claim was not equal across them. Babies with the most monitoring needs and the least stable recent observations were the ones most exposed if a nurse was pulled away, and the chart showed which those were. The first question for the charge nurse was clinical rather than administrative: which babies could tolerate a short period of reduced observation, and which could not. Triage here is a judgment about risk over the next few hours, and it should be written down so the next shift can see what was decided and why.
The unit's capacity escalation policy set out three stages, each triggered by a fixed occupancy level and a staffing ratio. At the second stage, the charge nurse was required to inform the duty clinical lead and the regional transfer coordinator before accepting or declining any transfer, and to record the reasoning. The regional agreement let the sending hospital ask for a decision within a set period but did not oblige acceptance. Coordination therefore depended on a short, honest exchange of information: what the unit could safely cover, what it could not, and what the sending team could offer in the meantime. A decline still needed a plan for the baby.
- Forecast demand Review admissions from the labor ward and planned transfers for the coming week.
- Match staffing Set rosters against expected occupancy, with a named cover plan for absences.
- Triage transfers Rank incoming and current babies by observation need before any decision.
- Review outcomes Check delayed escalations and near misses at the same meeting each week.
Actions taken
- Ask the charge nurse to rank each occupied cot by observation need before accepting or declining any transfer, and to record the ranking at the handover.
- Move the planned discharge of a stable baby forward only after the family has been told, and confirm that community follow up is in place before the bed is released.
- Call the duty clinical lead and the regional transfer coordinator together, using a shared script that states current staffing, open cots, and the earliest safe time for the incoming baby.
- Hold a same-day review of the surge with the staff on duty, recording which options were used, what each cost in observation time, and what to change in the escalation policy.
Results
The unit opened its overflow area with a reduced ratio and moved one planned discharge forward after a family conversation. It declined the transfer once the duty clinical lead agreed that the sending hospital could cover the first period, and a bed was offered within the following day. No baby in the unit had a delayed escalation during the surge, according to the shift record. Staff reported that the shared script shortened the coordination call. Staff also felt the decision had landed too heavily on one charge nurse.
Questions for discussion
- How should a charge nurse weigh the needs of babies already in the unit against those of an incoming baby when both are real?
- What information does a regional coordinator need in order to accept a decline without treating it as a failure?
- Which parts of a capacity policy should be fixed in advance, and which should be left to the judgment of the person on duty?
Case Study 4
Uneven outcomes across shifts in a newborn service
Moorhaven Family Birth and Newborn Service, a community maternity unit with two nurseries and 14 cots.
The situation
A quarterly review at the Moorhaven service showed that the rate of unplanned transfers to a higher level of care varied widely between the two nurseries, and between day and evening shifts within the same nursery. The counts were small, and the team had treated each case as a separate event. The quality lead, Marisol, pulled anonymized records for the previous 12 months and grouped them by shift, staffing mix, time of admission, and whether a senior review had been documented within the expected window. Clinical notes were available for review but had not been analyzed together before. The result was a set of patterns that no one had seen when looking at cases one at a time.
The challenge
The causes could be operational, clinical, or both, and each explanation pointed to a different fix. A staffing gap at evening handover would call for a roster change, while a delay in documented senior review would call for a protocol and a reminder system. The team had to find the likely process causes without concluding too early, design a cycle they could monitor, and agree in advance what result would count as improvement. Several staff were already defensive about the numbers.
Analysis
The patients behind these numbers were newborns whose transfers signaled a change in care before the decision was made. The notes showed more transfers among babies admitted in the evening, when the nursery often ran with one fewer experienced nurse. The evidence was useful but limited, since notes are written under pressure. A quality review therefore has to avoid reading the record as a neat story. Good reviewers separate what was observed from what was assumed, and they test each assumed cause against the records before settling on a fix.
The transfer protocol required a senior review within a set window for any newborn admitted outside the day pattern, and the review was to be documented in the main record. The evening team often completed the review by phone and recorded it in a separate log, which meant the main record did not show it. The handover sheet had no field for reviews done by phone. Several gaps looked like missed reviews when the review had taken place. The protocol was sound, but its documentation step had drifted from how the team worked, so the fix had to follow the work.
Actions taken
- Build a short monthly extract from the main record and the phone review log, matched by anonymized case number, so that reviews done by phone are counted.
- Add a required field to the handover sheet stating whether a senior review has been completed, by whom, and at what time, for every newborn admitted in the evening.
- Run a monitored cycle over the next three months: change one step at a time, record the indicator weekly, and compare each week against the agreed baseline.
- Agree before the cycle starts what sustained improvement means, for example four consecutive months within the agreed range, and report to the governance group if it is not reached.
Results
Most cases that had looked like missed reviews were found in the separate log. The remaining evening cases showed a real delay, and the roster was adjusted to add a second experienced nurse for the first hours of the shift. Over the monitored period, the share of evening admissions with a documented review within the expected window rose, and the unplanned transfer rate moved closer to the day shift figure. The team did not claim a durable change yet, since the period was short and the numbers were small.
Questions for discussion
- What evidence from the records would convince a reviewer that a documented gap reflects a real delay rather than a filing problem?
- How should a service decide which process cause to test first when several explanations are plausible?
- What would make a monitored improvement cycle credible to staff who already feel that the numbers are unfair to them?
Case Study 5
Shared decisions when parents disagree about information
Eastmere Children's and Newborn Hospital, a tertiary hospital with a 40-cot neonatal unit and an ethics advisory service.
The situation
A baby had been on the neonatal unit for several weeks after a complicated birth, and a discharge plan was being drafted that would require both parents to take on new caring tasks at home. The parents had separated during the admission. The mother, Sofia, asked the team not to share certain details of her own health history with the father, who had parental responsibility and had been asking daily for updates. He wanted to attend the family meeting and to be involved in teaching sessions. The nurse who had first spoken with the mother had recorded her request, but it was unclear whether it applied to the discharge conversation.
The challenge
The team had to settle what could be shared with each parent, whether the family meeting could go ahead with both present, and whether the open question needed the ethics advisory service before discharge planning moved on. The consultant neonatologist, Hassan, wanted a workable plan by the end of the week, but the discharge date was only provisional. Neither parent had been told the other's request, and the team had to avoid handling the disagreement in the corridor.
Analysis
The baby's needs were the reason every other question mattered. A newborn going home needs caregivers who can recognize change, act on written instructions, and know who to call. The evidence the team needed was practical: which adult would be doing which tasks, which information each adult already had, and where the gaps were. The mother's request concerned her own health information, not the baby's care, and the team had to keep those two categories apart in its notes. Staff who work in this area often find that consent questions become easier once the plan is described in terms of tasks rather than authority.
The information sharing policy separated a parent's own health information from information about the baby's care. The father's parental responsibility gave him a right to information about the baby and a voice in decisions, but not to the mother's history. The policy also asked staff to escalate unresolved requests to the ethics advisory service rather than settle them informally in the corridor. Coordination meant one named person kept the record of requests and replies, social work supported the parents without deciding for them, and each parent saw the meeting agenda before it began.
Actions taken
- Write down the mother's request in her own words, note when it was made, and confirm with her what she is content for the team to share at the meeting.
- Hold separate conversations with each parent before the joint meeting, so that each knows what the other has been told about the agenda, without repeating any private detail.
- Refer the unresolved question on disclosure to the ethics advisory service with a one-page summary, and continue discharge teaching for the parts of the plan that both parents agree on.
- Agree with the consultant that the discharge date stays provisional until the ethics advice is received and tell both parents the date depends on readiness not on the disagreement.
Results
The mother agreed to share a limited set of details with the father, and the team recorded that boundary in writing so every member of staff could see it. The ethics advisory service gave its advice within the following week, which supported the approach and suggested one further step on who would receive written discharge instructions. Both parents then attended the family meeting, separately for the first part and together for the final section. Discharge planning moved forward, though the date slipped by several days, and the team noted that the parents' relationship stayed difficult throughout.
Questions for discussion
- When one parent's right to information meets another parent's right to privacy, which considerations should set the boundary, and who should own it?
- How can a team keep a confidential detail out of a discharge plan that depends on the same person's participation?
- At what point should an unresolved disagreement be escalated, and what should the escalation note contain so advisers can act without a second meeting?
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.