Obstetrics and Maternal-Fetal Medicine Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
This set of five case studies is written for clinicians, midwives, and service leads who work where pregnancy care meets hospital systems. Each case starts with a situation drawn from a fictional unit, then moves through the patient's needs, the clinical evidence available at the time, team communication, and the local protocols that shaped the outcome. The aim is not a single right answer. Each case asks you to reconstruct the reasoning, name where the system helped or failed, and propose changes you could defend to colleagues.
Case Study 1
A returning patient whose concern was read in pieces
Harrowgate Regional Women's Care Unit, a 40-bed obstetric unit with a midwife-led triage area and an on-call senior team covering about 60,000 residents.
The situation
A woman in her late twenties attended the triage area of Harrowgate's unit in the third trimester after noticing that her baby had moved less over the previous day. She had an uncomplicated pregnancy so far, with one earlier visit recorded as normal. At triage, the midwife documented her reported symptoms, recorded observations, and reviewed the monitoring record. The initial assessment was reassuring, and she was asked to return if symptoms persisted. Over the next several hours she returned twice, each time describing a new headache and some swelling in her hands that had not been there before. Each attendance was handled by a different clinician on a different shift.
The challenge
The difficulty was not any single decision but the pattern across three attendances. Each clinician saw a snapshot, and the earlier readings did not travel with the patient in a form the next person could easily compare. The team had to decide whether the combination of symptoms warranted escalation to the senior obstetric and maternal medicine team under the unit's guidance, and how quickly. Staff on the afternoon shift were also managing a full labor ward, which shaped how much time anyone could spend on the record.
Analysis
The patient's needs were clear once the three attendances were read together, though no single attendance made them obvious. Reduced fetal movement, new headache, and swelling of the hands are each common enough to be explained away alone, but taken together they point toward a need for a senior review of the whole picture rather than another routine recheck. The clinical evidence sat in the record: serial observations that were each within the range the triage tool treated as low concern, yet had moved in the same direction over time. Trend, not threshold, was the signal the unit's guidance asked staff to act on. A reader who looked only at the most recent set of numbers would have seen nothing alarming.
Teams grounded in Obstetrics and Maternal-Fetal Medicine tend to ask first what the record shows across time, then who owns the decision at this point in the pathway. Here the local escalation protocol named the senior registrar as the person to contact when two or more concerning features appeared across attendances, yet nobody at the second or third attendance had the full sequence in front of them. Verbal handover between shifts was brief and focused on the most recent set of observations, so the earlier concern did not travel. The protocol was sound on paper. Its weak point was the link between documentation and the decision to call.
- First attendance, morningReduced movement reported; observations reassuring; advised to return if persisting.
- Second attendance, middayNew headache and hand swelling; separate clinician; earlier entry not compared.
- Third attendance, afternoonSymptoms persisting; trend visible in record but not presented at handover.
- Senior review requestedEscalation occurred after the third set of concerns, later than the protocol intended.
Actions taken
- Introduce a single shared trend view in the triage record that displays serial observations and symptoms on one screen, so each clinician sees the sequence rather than only the latest entry.
- Add a prompt to the escalation protocol requiring senior review when a patient returns to triage with a persisting symptom, even if each individual reading looks reassuring.
- Replace verbal handover of antenatal concerns with a structured written summary that lists open symptoms, the time each was first reported, and the agreed next review point.
- Audit triage returns over the next quarter, recording how often a second attendance with unresolved symptoms led to escalation, and report the findings to the unit governance meeting.
Results
In the first quarter after the changes, the unit reviewed 14 repeat triage attendances with persisting symptoms. Escalation to a senior review occurred at the second attendance in 11 of those cases, compared with 4 of 13 in the audit period before the changes. Two patients were reviewed earlier than the previous pattern would have allowed. The handover summary was used at most shift changes, and the governance group asked for another quarter of data before drawing firm conclusions.
Questions for discussion
- What features in the first attendance would have justified applying the protocol's threshold, and how would you record that judgment?
- Where in your own unit does handover carry the sequence of concerns, and where does it carry only the latest reading?
- Which of the four actions would meet the most resistance from your colleagues, and what evidence would you bring to address it?
Case Study 2
A handover that dropped the next review time
Millbrook Community Maternity Service, a two-ward unit with an antenatal clinic and a labor and delivery area, delivering around 9,000 births annually.
The situation
At the end of a busy day shift on the antenatal ward at Millbrook, a midwife handed over the care of a woman in her early thirties whose pregnancy had been flagged for closer monitoring. The handover was given verbally at the nurses' station, with the patient's file open but not walked through line by line. The outgoing midwife mentioned that a repeat review was due later that evening and that the woman had been told to come back if she felt unwell. The incoming midwife had three other patients to receive in the same half hour. The written sheet listed the name and bed, but not the review time or the threshold for calling the registrar.
The challenge
The gap was small and easy to miss. Nothing in the handover was wrong, but the most time-sensitive part, when the next check was due and what would trigger escalation, lived only in the outgoing midwife's memory. The incoming midwife was receiving several patients under time pressure and had no reason to ask for a detail that seemed routine. The question for learners is how the process should have protected that information, and what the unit's handover standard required in practice, not only on paper.
Analysis
The patient needed two things from the handover: an accurate picture of where her care stood, and a clear point at which someone would check again. The clinical evidence in the file supported closer monitoring, with the earlier readings recorded and the reason for review documented. What was missing was not evidence but its translation into a handover. A review time that exists only as a sentence in conversation is easy to lose when the conversation is interrupted. The safety question is whether the next person could act without reconstructing the plan, and here they could not. The patient had been told to return if she felt unwell, which placed the burden of detection on her at home rather than on the team.
The unit's handover standard called for a structured tool covering current status, pending actions with times, and escalation criteria. The incoming midwife was given the situation in summary and was not walked through the framework. Under time pressure, a verbal handover tends to compress toward what the speaker feels is most important, and the speaker's sense of importance was shaped by a patient they had already been worried about all day. Coordination depends on shared expectations about what must be said, and in this case that expectation stayed implicit. The standard existed, but it was used as a checklist for the paper sheet rather than as a conversation both parties worked through together.
Actions taken
- Require that every handover for a patient with a scheduled review includes the time of the review and the escalation threshold, read aloud and confirmed back by the receiving clinician.
- Move the handover sheet into the electronic record so pending actions appear as timed prompts on the receiving clinician's task list, with an alert if an action passes its due time.
- Run structured handover as a seated, two-person exchange at the station for patients flagged for closer monitoring, with a protected window that is not interrupted by admissions.
- Measure handover completeness each month by sampling ten handovers from the antenatal ward, checking for timed actions and escalation criteria, then share results with both shifts.
Results
Over the following quarter, the ward audited 40 handovers for patients flagged for closer monitoring. Timed actions were recorded in 31 of them, compared with 9 of 40 in the baseline sample. The electronic task prompt flagged two reviews that had passed their due time without documentation, and in both cases the registrar was contacted within the hour. The unit noted that gaps still appeared when patients moved between wards, and a separate project was set up for transfers.
Questions for discussion
- Which information in your own handover tool is most likely to be lost when the receiving clinician is busy, and how would you know?
- How should a unit weigh the time cost of a structured handover against the risk of a missing review time, and who should make that call?
- If a patient is told to return when unwell, what does the team need to have done so that the advice is not the only safeguard?
Case Study 3
Triage choices during an unplanned staffing shortfall
Calder Bay Maternity Center, a 22-bed unit with a shared operating suite and a consultant schedule covering two sites.
The situation
Calder Bay's unit had a planned staffing model built around an average daily birth count, and for a period of several weeks the count ran well above that average. Two midwives were off sick in the same week, and one senior obstetric post was covered by locum cover that had not yet been inducted onto the local protocols. The charge midwife had to decide each shift which triage calls came first, which antenatal appointments could move, and how the single scanning room should be used. Requests arrived from the labor ward, community midwives, and the emergency department, each with a fair claim.
The challenge
No single option was clearly safe. Delaying routine appointments could hide deterioration in women with complex histories, while protecting the triage queue could leave planned care unseen for longer. Staff were already working extended shifts, and the risk of fatigue was rising alongside the workload. The charge midwife had authority to reassign staff but not to add posts, and the next decision on temporary cover sat with a general manager who was off site until the following week.
Analysis
The patient needs in this case were not equal. Women with a pregnancy flagged for closer review carried a higher chance of needing an unplanned senior assessment, and their appointments could not be moved without a documented clinical reason. Women seen in triage with new symptoms had time-sensitive needs that could not wait for a routine slot. The local risk tool sorted women into tiers and was useful for ordering demand, but it did not say how much capacity to protect. Triage was a judgment laid over that tool. Each tier was reasonable on its own, and that was the difficulty.
The applicable protocols gave the team a clear order of priority for emergencies and a broad framework for planned care, but they assumed the consultant schedule would be filled. With the locum not yet inducted, the escalation route for a complex triage case ran through an unfamiliar name and an unfamiliar phone number. Coordination had to be rebuilt each shift. The charge midwife held short daily huddles that brought together the labor ward, community midwives, and the scan lead, and those huddles became the place where competing claims were settled rather than argued in corridors. The huddle worked because it made the trade-offs visible to everyone with a stake in them.
- Publish capacity Post staffed hours for triage, scanning, and clinics each day.
- Triage and defer Sort requests by risk tier and move only what has a documented reason.
- Review deferrals Clinician checks each moved appointment and confirms a rebooking window.
- Escalate shortfall Report sustained gaps to management with what was deferred.
Actions taken
- Publish a daily capacity sheet listing staffed hours for triage, scanning, and clinics, so every request is weighed against the same numbers.
- Set a rule that any appointment moved for capacity reasons must be reviewed by a clinician within a defined period, and the reason recorded in the patient's notes.
- Agree in advance which triage categories may be redirected to emergency cover and which must stay on the unit, then brief locum staff on that list.
- Escalate a sustained shortfall to the general manager as a formal capacity risk after two consecutive shifts below minimum safe staffing, with a written note of what was deferred.
Results
In six weeks the unit recorded 37 deferred antenatal appointments, 29 of which were rebooked within the agreed period after clinician review. Eight were not, and the audit traced those to a single shift in which the capacity sheet had not been updated. The triage queue was cleared within the target time on 19 of 24 shifts. The general manager approved temporary cover after the second escalation, which brought the scanning room back to its planned sessions. The daily huddle grew shorter as disputes were settled before it began.
Questions for discussion
- Of the three options in this case, triage redirection, appointment deferral, and temporary cover, which carries the least hidden risk for women with complex histories, and why?
- How would your service know that a deferred appointment had become a missed one, and who would be responsible for noticing?
- What minimum staffing evidence would you need before asking for permanent posts rather than temporary cover?
Case Study 4
Inconsistent risk assessment completion across three units
Tarn Valley Perinatal Network, a group of three maternity units sharing a regional audit team and one outcomes dataset.
The situation
Across the three units of the Tarn Valley network, a quarterly dashboard showed a pattern the regional quality lead did not like. One unit recorded a documented risk assessment within the target window for most women, a second for about two thirds, and the third for fewer than half. Unit-level outcome numbers were small, so any single change could be explained by a handful of cases. The rate of unplanned transfers to a higher-level unit also differed between sites. The audit team held anonymized records for 4,300 women across the network but had not compared process steps side by side.
The challenge
The variation could reflect differences in patient populations, differences in how the risk assessment was recorded, or differences in how quickly staff acted on it. Small unit numbers made it hard to say which explanation was most likely. The network lead wanted a review that would separate real process differences from data artifacts, and that would produce a plan the units could run themselves rather than one imposed from the center.
Analysis
Before any process can be judged, the population has to be described. The three units served different catchments, with one taking a larger share of women with known complexity and referrals from outside the network. Some difference in transfer rates may therefore be legitimate case mix rather than poor practice. The clinical evidence is only as good as the indicators themselves. A documented risk assessment counts as complete if the field is filled, but a field can be filled in a way that does not reflect what was discussed. Good analysis starts by stratifying indicators by case mix and reading a sample of records to see what entries mean in practice.
Team coordination differed in ways the dashboard could not show. At one unit the risk assessment was completed by the first clinician who met the woman, with the next shift checking the entry at a set point. At another it was completed by whoever had time, often late in a busy session, and no one owned the check. The applicable protocol set a common completion window and named the responsible role, but it did not say how an incomplete assessment should pass between shifts. Process causes were therefore likely to sit in the gap between the protocol and the daily routine of each site, where local habits had filled the space the standard left open.
Actions taken
- Agree a shared definition of a complete risk assessment across all three units, including what must be documented and by which role, and retire the local variants.
- Stratify the indicators by case mix in the quarterly report, so that differences in transfer rates are compared among women with similar starting risk rather than across the whole network.
- Run a monthly sample review of twenty records per unit, checking whether the documented assessment matches the notes, and feed findings back to the clinical lead within the week.
- Pilot a named check point for incomplete assessments at each handover for one quarter, then compare completion and transfer rates with the two comparison units before extending it.
Results
After one quarter of the shared definition and sample review, completion rates moved closer together across the three units, with the lowest site rising by roughly a fifth. The sample review found that about one in six entries were marked complete without matching detail in the notes, which the dashboard had not shown. Stratified transfer rates narrowed the gap, though one unit still ran higher among women with the highest starting risk. The check point will run for a second quarter before any network-wide change. Small numbers at each site keep all results provisional.
Questions for discussion
- What would a completed risk assessment have to contain in your own service for an auditor to accept it without reading the notes?
- How would you separate a real difference in transfer rates from a difference in the mix of women each unit sees?
- Who should own the monthly sample review in your network, and what would make its findings change practice rather than sit in a report?
Case Study 5
A disclosure request that split the care team
Ashford Vale Birth Services, an independent community midwifery service with a shared-care agreement with a regional maternal medicine center.
The situation
A woman in her mid-thirties was referred to the shared-care team after a series of results prompted a recommendation that her pregnancy be followed at a regional maternal medicine center. She speaks English as a second language and uses a professional interpreter for longer conversations. Her husband attends most appointments and has been answering questions for her. At a recent visit she asked, through the interpreter, that one result not be shared with her husband or her mother, who planned to attend the next appointment. Two team members disagreed about including the husband in discussing the recommended plan.
The challenge
The team had to balance her stated wish for confidentiality against the husband's role in her care, the mother's expectation of attending, and the duty to make sure she understood the plan well enough to consent to it. It was not clear whether her wish reflected a personal preference, pressure from family, or worry about how the family would react. Her understanding of the recommendation was itself uncertain, and the interpreter was booked only for the current appointment.
Analysis
Her needs were both clinical and communicative. The recommendation for a higher level of review rested on evidence that had to be explained in a form she could follow, and consent to any plan depends on understanding the options, not on the presence of a family member. Confidentiality is her right, but it is not absolute, and the team was not in a position to guarantee what would be shared with relatives who had no formal role. The evidence was reasonably clear that a planned review at a regional center was advisable, but not how she would want it explained. The first task was to find out what she wanted known, by whom, and in what language.
The shared-care agreement set out who holds the record, how information flows to the regional center, and when local ethics advisers should be involved. It did not say what to do when a patient's stated wish about disclosure sits against the expectations of a family member who has been present throughout. The two team members who disagreed were each acting from a legitimate duty. One prioritized the husband's role as a support, the other the patient's autonomy. The team lead used the escalation route to request a review with the on-call ethics adviser and the interpreter service's lead before the next appointment, rather than deciding the point between two people at the desk.
Actions taken
- Arrange a private conversation with the patient, with a professional interpreter, to confirm what she wants shared, with whom, and whether she wants family present for the plan discussion.
- Document her stated preferences and the reasons she gave in her own words, and record that the interpreter confirmed the meaning, so the next clinician can see what was agreed.
- Escalate the disclosure question to the on-call ethics adviser before the next appointment, and ask the regional center's team how they handle family members present at planned reviews.
- Review the shared-care agreement after this case so that the protocol names who decides when a patient's disclosure wish conflicts with family involvement, and how that decision is recorded.
Results
The private conversation took place in the second week of the referral. She wanted the result discussed only with herself and the midwife, and she agreed her husband could attend the plan discussion. Her mother was not included. The interpreter's note recorded her own wording for the regional center. The ethics adviser agreed the approach fit the agreement and asked the team to review how the question was first raised. Staff felt the process was slower but produced a plan the patient described as her own.
Questions for discussion
- When a patient's stated wish about disclosure conflicts with a family member's expected role, what should the first clinician in the room do before any decision is recorded?
- How would you tell whether an interpreter is conveying a patient's own preferences or summarizing the family's view?
- What should a shared-care agreement say about who decides when consent, confidentiality, and family involvement point in different directions?
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.