Gynecology and Reproductive Medicine Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
Gynecology teams make many small decisions that shape a patient's experience: which message gets flagged, which slot gets offered, which symptom gets read as routine. The five cases come from fictional services and follow one thread, from a single phone call to a long review of outcomes. Each asks what the patient needs, what the record shows, how the people involved coordinate, and which local protocol sets limits. Most turn on thin handovers, loosely applied triage rules, and conversations that began before anyone had the full picture. Read them slowly and note where the team could have known sooner.
Case Study 1
Repeated calls for worsening pelvic pain
Quillfeather Gynecology Unit, an outpatient service attached to a regional hospital, with a telephone triage line staffed on weekdays.
The situation
Ilse was booked for a routine review after a call about irregular bleeding between cycles. The intake nurse, Marcus, logged the call as routine and offered the first clinic slot, three weeks out. Over the next nine days she rang twice more. The second call added one-sided lower abdominal pain that made sitting through a work meeting difficult. The third call was taken by a booking clerk who added a note but left the category unchanged. Nobody had read the three entries together, and the unit's escalation guide was never applied to the sequence.
The challenge
The team had to decide whether a pattern of changing symptoms across contacts should move Ilse up the list even though no single call crossed a threshold. Marcus was confident the bleeding alone was routine. Yuki, the clinic lead, was not yet in the loop. The registrar on call could be reached, but the protocol did not say how to weigh a trend against single-call criteria.
Analysis
From Ilse's side of the phone, the picture was simple: the bleeding had changed, a new pain had joined it, and she kept calling because the first answer had not settled anything. Her needs that week were practical as well as clinical, including how soon she would be seen and what should prompt a faster call. Teams grounded in Gynecology and Reproductive Medicine usually begin by reading the record as a timeline, since the evidence here lives in the change between contacts. The documented facts were specific enough to matter, even without a diagnosis. They meant the triage category needed review, not carry forward from the first note.
The coordination problem was that each person held one piece. Marcus saw the first call, a booking clerk saw the third, and the clinic lead saw neither in sequence. The escalation guide asks staff to flag any patient whose symptoms are changing or whose contacts repeat within a short window, and it names the registrar as the decision maker. That wording is useful, but it depends on someone noticing the repetition. Protocols that rely on one reader tend to fail quietly, so a shared contact log should surface repeat calls to the triage lead each day.
Actions taken
- Add a repeat-contact field to the intake form so that any second call about the same complaint within a set window appears on the triage list automatically.
- Agree in writing who reads the day's contact log and makes the same-day decision, with a named backup for leave days, and review the rota monthly.
- Re-score the open triage category at each new contact and record the reason in one line, so the reasoning is visible to the next person who calls.
- Track the share of repeat-contact patients reviewed within the agreed window each month, with a target set by the clinic lead and reported to the governance meeting.
Results
Ilse was seen the same afternoon once the registrar read the log in full. The review confirmed that the picture had changed enough to warrant it, and she was given a direct number for the team. Over the following quarter, the share of repeat-contact patients reviewed within the agreed window rose from under half to most, and the intake form flagged eleven cases that would previously have stayed routine. A staff huddle also showed that two people had not realized the escalation guide covered trends, which the clinic lead now reads aloud at each shift start.
Questions for discussion
- Which entries in a contact log would you read first when a patient's symptoms appear to be changing between calls?
- How would you decide whether a trend across contacts should override a triage category that was correct at first contact?
- What information should a booking clerk be expected to pass on, and what should stay with the triage lead?
Case Study 2
A shift handover that lost a pending result
Brinmoor Gynecology Service, a short-stay ward of twenty-two beds in a mid-sized teaching hospital.
The situation
Brinmoor's short-stay ward admits women for planned gynecology assessments and for observation over short stays. Mariam had several open items at the end of a long day shift. The written summary listed her diagnosis, her prescribing review and her discharge plan, but it did not mention a laboratory result still pending from the afternoon. The verbal handover was brief because the incoming nurse, Tobias, was called to a bed alarm as the outgoing nurse, Ruth, began speaking. Ruth assumed the summary covered everything, and Tobias read it as complete. The pending result returned overnight and sat unread until the morning ward round.
The challenge
The question for the team was not whether anyone had acted badly. Each person had done a reasonable thing with the information in front of them. The harder question was how a result that carried a time-sensitive instruction could pass between two shifts without anyone holding it, and what the ward had built to catch exactly this. Shanice, the ward manager, needed to decide whether the gap was an individual lapse or a design problem in the handover tool itself.
Analysis
Mariam's needs were ordinary and specific: to know what was still open, to have someone accountable for the pending result, and to hear the plan from a person rather than a page. The record was detailed, but the one fact that mattered for safety sat in a laboratory report that had not traveled with her. Handover reviews often list missing or unclear pending items among the most common sources of communication error, so a tidy summary proves little. Good handover practice treats the summary as a starting point and checks it against the open items in the chart before judging how complete it is.
The handover protocol on the ward asks for a structured verbal report using a fixed set of headings, with pending results named explicitly and an owner assigned for each. In this case the structure existed on paper but was not used under pressure, because the verbal report was interrupted and nobody paused to resume it. Coordination depends on what happens when the process breaks, and here the ward had no rule for a handover that was cut short. A simple change would be to require the outgoing nurse to read pending items aloud and the incoming nurse to repeat them back before the summary is accepted.
- Name open items Read every pending result and task aloud, with the time it is expected back.
- Assign one owner Give each open item one named person and a check time.
- Read back The receiver repeats each open item before accepting the handover.
- Audit the record Compare summary with the chart and log gaps.
Actions taken
- Add a pending-items box to the written summary that must be filled in, even if the answer is none, so a blank field is visibly different from a forgotten one.
- Require a read-back of all open items at every shift change, and record the outcome in the handover tool so the rate can be audited each month.
- Set a target that at least ninety-five percent of audited handovers name every pending result, and report the monthly figure at the ward governance meeting.
- Protect the handover window by moving bed alarm response to a named floating nurse during the change, so the verbal report is not interrupted in future.
Results
Mariam's result was reviewed at the start of the morning round, and the plan for her discharge was adjusted to fit it. No harm reached her, but the team recorded the event as a near miss. In the three months after the changes, the ward's audit found that the share of handovers naming every pending result rose from about six in ten to nearly nine in ten. The pending-items box also exposed two earlier gaps that had been invisible. Tobias said the read-back felt slow for a week and then became the part he trusted most.
Questions for discussion
- Which of the four steps in the cycle would your own ward find hardest to sustain during a short-staffed shift, and why?
- How would you design the audit so that a blank pending field is counted as a gap rather than as a missing form?
- What should happen to a handover that is interrupted, and who should have the authority to pause the shift change?
Case Study 3
Rationing a shared imaging list under pressure
Tallow Ridge Reproductive Clinic, a regional outpatient service with four consulting sessions a week and one shared imaging list.
The situation
Demand at Tallow Ridge had risen steadily over twelve months, driven by referrals for heavy bleeding, pelvic pain, and follow-up after earlier assessments. The clinic runs four consulting sessions a week and a single shared imaging list each morning. In the latest quarter, the waiting list for new appointments reached 620 people, and roughly one in five referrals were marked urgent by the referring clinician. The imaging list was full for six weeks ahead. Staff sickness had removed one sonographer's sessions for a month, so the list shrank at the moment it was needed most.
The challenge
Dimitri, the operations lead, had to choose how to spend a fixed number of imaging slots and a limited pool of consulting sessions. Every option protected some patients and delayed others. A first-come queue looks fair but lets a worsening complaint wait behind a stable one. Clinician-led triage is more responsive but adds decision load to people already short of time. The team needed a method that could be explained to patients and defended at governance.
Analysis
The clinical question under the queue is which patients carry the most risk from waiting. Heavy bleeding with a change in pattern, new pelvic pain, and referrals marked urgent should not sit behind routine follow-up, even though follow-up is easier to schedule. The evidence at the clinic was mostly the referral letter and the triage note, and both varied in quality, so no single field could rank people reliably. Protocol-based triage works only when the inputs are complete, which argues for a short structured checklist completed at booking rather than a memory of the phone call.
Coordination here runs across three desks. The booking team holds the waiting list, the imaging coordinator controls the shared list, and the consulting clinicians decide who is seen first within their sessions. Each desk applies the local access protocol, but they apply it at different points, and a patient can be urgent at one desk and routine at another. The protocol sets an urgency band and a maximum wait for each, which is a sound basis. What it leaves open is who may move a patient between bands under pressure, so only the clinic lead now does so, with a written reason.
Actions taken
- Complete a structured urgency checklist at booking for every referral, so the same inputs are captured whether the referral arrives by letter or by phone.
- Reserve two imaging slots each morning for protocol-urgent referrals, released to general booking only after reserved slots have gone unused for one working day.
- Redirect stable referrals needing heavy imaging to a partner list through a written agreement with a fixed monthly allocation, reviewed at the access meeting.
- Track the median wait for each urgency band monthly and set a maximum that triggers a clinic lead review whenever an urgent patient waits longer than agreed.
Results
Within the quarter, the reserved slots cleared the urgent backlog, and no urgent referral waited beyond the agreed maximum after the first month. The partner list took about one in eight of the stable imaging referrals, which freed sessions for patients who needed them more. The waiting list fell from 620 to under 450, although routine follow-up for some patients stretched by a few weeks. Dimitri noted that the checklist took roughly two minutes per referral, and that the clinicians who had resisted it became its strongest users once they saw urgent cases surface earlier.
Questions for discussion
- How would you weigh a stable patient's wait against the imaging demand that a single urgent referral creates, and who should make that call?
- What information would the booking checklist need to capture so that two referrals with similar letters could still be ranked differently?
- What risks does a partner list introduce for continuity of care, and how would you monitor them?
Case Study 4
Uneven follow-up outcomes across three sites
Oakhollow Reproductive Medicine Group, a network of three outpatient sites sharing one referral pathway and a central audit team.
The situation
Oakhollow's audit team noticed that patients referred for abnormal bleeding had very different experiences depending on which site saw them first. Over twelve months the network received about 2,300 referrals through a shared pathway, and the audit team pulled anonymized indicators for each site. The pattern was not dramatic, but it was consistent: one site triaged quickly and documented thinly, another documented thoroughly but followed up late, and the third sat in the middle on most measures. Records were anonymized before review, and the team looked only at process indicators, not individual cases.
The challenge
The audit lead, Priyanka, had to decide what the variation meant before anyone changed a process. Thin documentation might mean poor care, or it might mean a site with a busier front desk and a different template. Late follow-up might reflect a staffing gap, or a choice to hold patients for a second look. The indicators could not separate those explanations alone, and the network had no agreed threshold for when a difference became a problem worth acting on.
Analysis
For the patients behind these numbers, needs were consistent across sites: a timely triage decision, a clear account of next steps, and no need to repeat their history. The clinical evidence the team could use was mostly process evidence, such as time to triage, completeness of the first record, and whether a planned follow-up actually occurred. Those are imperfect proxies for outcome, and the team said so in the review. Still, they point at where the care pathway is failing people, which is more useful than a headline rate. A review should name its proxies and keep them apart from conclusions about care.
The shared pathway depends on three teams, the front desk that books triage, the clinicians who make the decision, and the administrators who send follow-up letters. Each site has its own local variation in how these steps are split, and the network protocol describes the intended sequence without saying who checks it. Coordination failures tend to hide in the gaps between desks, so the review mapped every handoff against the protocol's timeline. The late follow-up at one site traced to a letter queue that only one administrator cleared, and the thin records at another came from a template that had quietly lost a required field.
Actions taken
- Map each handoff in the referral pathway against the protocol timeline at every site, naming the person responsible for each step and the expected time.
- Replace the thin-record template with a version that requires the four core fields before a visit can be closed, and test it on one site first.
- Share the letter queue across at least two administrators with a daily clearance target, so that one absence no longer delays follow-up for a whole site.
- Set a monitored target for each indicator, reviewed monthly, and run a plan-do-study-act cycle on any indicator that stays below its threshold for three consecutive months.
Results
After two cycles of changes, the triage window was met in most referrals at every site, and the gap in follow-up letters closed when the queue was shared. The template change lifted record completeness from 5 to 8 on the audit scale, though the repeat contact rate barely moved, which suggested patients were calling about something the records did not capture. The team added a question about what patients had been told at the first visit, and the repeat rate began to fall in the following quarter. The network now reviews the indicators monthly, with one shared threshold.
Questions for discussion
- Which of the three site profiles would you expect to show the most risk of patients falling out of the pathway, and what evidence would confirm it?
- How would you decide that a difference between sites is real rather than a product of case mix or small numbers?
- What should a plan-do-study-act cycle record beyond the indicator itself, so that the next review can tell whether the change or something else moved the result?
Case Study 5
Shared information when a daughter attends
Ferncliff Gynecology Service, a hospital clinic with a monthly multidisciplinary meeting and a patient liaison officer.
The situation
Odile, a patient in her late fifties, attended a complex review with her adult daughter, Lena, who had driven her to the appointment and sat in on earlier visits. Odile had asked the team, privately and before the consultation, that the detailed results not be discussed in front of Lena and that Lena not receive the written letter. Lena had asked, in the waiting area, to be given everything. The clinician, Hamid, now had two requests that pulled in opposite directions. The record showed that Odile had been assessed as able to make her own decisions, and no other relative held any formal authority.
The challenge
The duties here were not all the same weight. The team owed Odile confidentiality and respect for a decision she was entitled to make, and they owed Lena honest support as a family member without any right to her mother's records. The question was how to honor Odile's wishes without leaving Lena with the impression that the team was hiding something dangerous. Priya, the patient liaison officer, wanted the discussion documented before anyone spoke to Lena again.
Analysis
Odile's needs were the center of this decision, and her stated wishes carried real weight. She had been assessed as able to decide for herself, she had told the team what she wanted shared and with whom, and that instruction was recent. The clinical facts were not in dispute. What the team had to weigh was whether the detail of a results discussion could be separated from the family conversation without leaving Odile unsupported. Ethical guidance in this area generally treats a competent patient's instruction on disclosure as binding unless a specific legal or safety threshold applies, and this record showed none.
The service's consent and confidentiality protocol asks for three things before information goes to a relative: a documented instruction from the patient, a check that the relative is recorded as a contact rather than a decision maker, and a named clinician who owns the conversation. Here the first two existed, but the third was unclear, because Hamid was carrying the consultation alone while the liaison officer was in another clinic. The protocol also says disagreements over disclosure go to the multidisciplinary lead, and that step had not yet been taken. Escalation was the missing move, not a different answer.
- 1Confirm the instructionRecord the patient's stated wishes, when they were given and the exact information covered.
- 2Check decision authorityConfirm the relative is a contact only, not a decision maker.
- 3Separate the conversationsHold results with Odile alone, then agree what family may hear.
- 4Escalate the disagreementRefer to the multidisciplinary lead today rather than waiting for the next scheduled meeting.
- 5Document and closeRecord each decision, who was told what, and the next review point.
Actions taken
- Agree with the patient, in a private conversation, which information may be shared with Lena, which must stay private, and how she wants new results handled.
- Record the agreed boundaries in a consent note that the whole team can see, with a review point at the next visit and a named clinician responsible for it.
- Give Lena a written contact route for general questions about the service, so that she has a legitimate way to raise concerns without receiving her mother's results.
- Take any unresolved disagreement to the multidisciplinary lead within the same working day, and log the time taken to reach a decision as a governance measure.
Results
Odile's boundaries were recorded, and the results discussion took place with her alone before Lena joined. Lena was unhappy at first, but she accepted the written contact route and asked for general information about the service. The multidisciplinary lead reviewed the case by the afternoon and agreed with the approach. Over three months, the audit found that disclosure disputes were resolved on the same day in every logged case, and that complaints about information sharing fell to a single case. The intake form now asks about family involvement at the first visit.
Questions for discussion
- What would you say to Lena in the first minute of the conversation, so that she understands the boundary without feeling shut out?
- When a competent patient's instruction on disclosure conflicts with a relative's expectations, what would make you ask the multidisciplinary lead to step in?
- How should a service record a patient's wishes about disclosure so that the instruction stays current across several clinicians and visits?
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.