Pulmonology, Respiratory and Sleep Medicine Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
This set of five case studies follows respiratory and sleep teams through decisions about deteriorating patients, shared responsibility, limited capacity, service quality, and consent. Each case centers on a fictional organization and a decision point that could plausibly arise in practice. For every case, the analysis considers patient needs, the clinical evidence available at the time, how team members coordinate, and which care protocols apply. Read the situation and challenge first, decide what you would do, and then compare your reasoning with the commentary and proposed actions. The figures in each case belong to the fictional services described and should not be taken as benchmarks.
Case Study 1
A worsening cough that waited for a named owner
Calder Point Community Hospital, a 260-bed acute hospital with an ambulatory respiratory clinic and a same-week referral pathway.
The situation
Dennis, aged 67 and a retired roofer, attended the ambulatory respiratory clinic at Calder Point Community Hospital with three weeks of breathlessness on stairs and a cough that had shifted from dry to productive. The first contact was a triage call taken by Ruth, the nurse, who recorded his readings as within acceptable limits and booked a routine review in two weeks. At the second visit he reported waking at night short of breath and needing extra pillows, a detail noted in the free text but not in the structured record. A locum doctor reviewed him at the third contact, documented the symptoms as a chronic obstructive disease flare, and requested a standard chest imaging order that sat unscheduled for four days.
The challenge
The team had to decide which findings justified moving Dennis up the list, which investigations to request first when same-week slots were limited, and whether the local escalation criteria applied to a patient whose readings were acceptable but whose function was falling. Each clinician had a reasonable reading of the record, and none had been asked to own the overall trajectory. The referral to the respiratory team was still waiting for a signature when the decision had to be made.
Analysis
Teams grounded in Pulmonology, Respiratory and Sleep Medicine usually start by separating what the patient reports from what the measurements show, because here the two pointed in different directions. Dennis's readings at triage were unremarkable, but his breathlessness, sleep and cough had all changed across three contacts, and that pattern matters more than any single set of values. His needs were practical as well as clinical, since he could no longer manage stairs and was waking at night. The evidence was also incomplete. The imaging had not been done, and nobody had compared the free text with the structured record. Prioritizing investigations meant asking which result would change the next decision, not which test was most available.
The coordination failure was less about individual judgment than about ownership. The triage call, the locum review and the referral each produced a reasonable entry, but no single person held the overall picture, so the escalation criteria in the local protocol were never tested against the three contacts together. The protocol calls for escalation when symptoms worsen across two contacts, and that would have applied here, but only if someone compared them. A sound response would have named one accountable clinician, moved the referral to same-day review, and recorded in plain language the reason for any delay. Protocols only work when the people applying them can see the same record.
Actions taken
- Add a structured field for sleep disruption and exertional tolerance to the respiratory triage template, so changes across contacts are visible without reading free text.
- Require a named clinician to own the working plan whenever a patient has two or more contacts with a worsening trend, and record that name on the referral before the contact closes.
- Set a rule that imaging or referral orders not scheduled within the protocol window trigger an automatic message to the clinic lead, who must confirm a date or document why not.
- Hold a monthly case review of patients whose escalation was delayed, using the protocol criteria as the agenda, and feed the findings back to triage staff within two weeks.
Results
After the review, the clinic adopted the structured trend field and the named-owner rule. Dennis was seen within the protocol window, and his imaging was completed in the same week. The monthly case review surfaced two more patients with a similar pattern, both waiting on unsigned referrals. Triage staff said the named-owner step felt slower at first but ended the question of who was watching each patient. The lead still audits escalation timing against the protocol each quarter.
Questions for discussion
- Which of the three contacts would you have treated as the point where escalation became necessary, and what would you have needed to see in the record to be confident?
- How would your team decide who holds the overall picture when several clinicians each make a reasonable entry about the same patient?
- What tradeoff would you accept between a faster routine slot and a fuller same-day review when a patient's symptoms are changing but measurements are stable?
Case Study 2
A night handover that left out the device details
Tessaly Health Partners, a three-site hospital group whose respiratory ward runs a 24-bed step-down unit for patients on home breathing support.
The situation
Bridget, aged 74, was moved from the respiratory step-down unit at Tessaly Health Partners to a general medical admissions ward at the end of a night shift. She used a home noninvasive ventilation device during sleep for a sleep-related breathing disorder and had been admitted with new drowsiness and poor sleep. The outgoing nurse, Samir, gave a verbal handover to the admitting nurse, Pilar, during a busy period. The written summary listed her diagnosis and current medicines, but it did not include the device settings she used at home, the time of her morning review, or a sputum result still pending in the laboratory. Pilar learned of these gaps only in the afternoon, when the bedside team asked for the equipment details.
The challenge
The task was to find where information was lost and which safeguards had failed or had never been connected. The handover tool was completed on paper but not used during the spoken exchange, the admitting team had no access to the equipment register, and the pending result had no named owner after the transfer. Both nurses had made reasonable judgments under time pressure, so the review had to separate individual performance from process design.
Analysis
Patient needs in a handover depend on details that are easy to lose because they do not sit under the diagnosis. Bridget's home device settings mattered most for her overnight care, yet they lived in an equipment log rather than the clinical record. The pending result was also relevant, since it would inform the morning review. The evidence the admitting team needed was spread across three sources, and the handover depended on someone remembering to combine them. A good handover carries a short list of what is still open, not only what has already happened.
The weakest point was where responsibility moved. The outgoing nurse assumed the written summary would be read, and the admitting nurse assumed a verbal handover would cover anything urgent. The local handover protocol calls for a structured tool that includes equipment, pending results and escalation thresholds, yet the spoken exchange was never checked against it. Safeguards that did exist, such as a pending results log and an equipment register, were not linked to the handover, so they could not catch the gap. The fix is partly technical, but mostly about making one person accountable for closing each open item before the handover is accepted.
Actions taken
- Add a required field to the handover tool for home equipment settings, with a link to the equipment register, so the admitting team can see them without asking.
- Make every pending result carry a named owner who must be stated during the verbal handover, and transfer that ownership in the electronic record when the patient moves wards.
- Require the spoken exchange to follow the written tool line by line, with the receiving nurse reading back the open items before the handover is accepted.
- Measure handover completeness with a monthly audit of twenty transfers, scoring each on the five tool fields, and report results to the ward leads at the next governance meeting.
Results
The tool change went live in the second month. Over the next audit period, completeness scores rose on all five fields, with the largest gain in equipment details. Ward leads kept the read-back step even though it added under a minute to each transfer. One later handover still missed a result ordered after the handover was signed, so the team added an alert to the receiving ward's inbox.
Questions for discussion
- Which of the four gaps would you have closed first, and how would you decide between fixing the tool and changing how the spoken exchange is run?
- When a safeguard exists on paper, such as a pending results log, how would you test whether it actually connects to the handover?
- How should a team weigh the time cost of a read-back against the risk of an open item going unnoticed during a busy shift change?
Case Study 3
Rationing overnight sleep assessment slots during a demand peak
Marlow Sleep and Lung Clinic, a network of two sleep laboratories and a respiratory outpatient service serving four districts.
The situation
At Marlow Sleep and Lung Clinic, the referral backlog for overnight sleep assessment grew over several months after a partner laboratory closed for renovation. The clinic has two overnight testing beds and a daytime respiratory outpatient service staffed by four clinicians. In the third week of the quarter, the waiting list reached a length that the service lead, Priya, judged could not be cleared without changes. Referrals ranged from people with daytime sleepiness and safety-sensitive jobs to people with mild, stable symptoms and no safety concerns. Slots had been booked in order of arrival, and Priya noticed that some urgent referrals had waited longer than routine ones because the triage form did not require a safety field.
The challenge
The decision had to protect people with the highest clinical and safety need without shutting out routine referrals, using two beds and limited technician time. Options included stricter triage, block booking of testing slots, a shared waitlist with a partner site, telephone pre-assessment to remove low-yield referrals, and an external overflow provider. Each option moved risk to a different group, so the team had to be explicit about who would wait longer.
Analysis
The starting point is the patient's need, and in sleep services that need varies widely. A person with daytime sleepiness who drives for a living carries a different level of risk from a person whose snoring disturbs a partner, yet triage tools based only on referral categories tend to flatten that difference. The referral letter holds the best available clinical evidence, including the sleep history and reason for referral, but it is often incomplete. Priya's team therefore used the triage form as a filter for safety indicators, then used a short telephone assessment to check whether a referral still needed a test.
Scheduling was the constraint that made the options hard to compare. Testing beds, technicians, and the clinician who reads results are booked separately, so a change to one resource altered the others. The local access protocol requires urgent referrals to be seen within a defined window, but it says nothing about a queue that has already passed that window. Moving routine patients to a partner site only works with a shared referral record and agreed criteria, or the partner simply becomes a second queue. The team's choice was most defensible where it kept the protocol's priority rules intact and made the trade-offs visible to referring clinicians.
- 1Safety-focused triageScore referrals for driving, work and safety indicators before any slot is offered.
- 2Telephone pre-assessmentConfirm the clinical question and remove referrals that no longer need a test.
- 3Block booking of bedsReserve fixed weekly slots for urgent cases, with routine referrals filling the remainder.
- 4Shared waitlist with partnerRoute routine cases to a partner under one shared referral record.
- 5External overflow providerLast option, used only when the protocol window is missed.
Actions taken
- Rebuild the triage form so that safety indicators are required fields, and have a clinician check any referral that flags driving or safety-sensitive work within two working days.
- Reserve two fixed weekly sessions for urgent referrals and publish the allocation rule, so referring clinicians know which cases are booked ahead and which join the routine queue.
- Agree a shared referral record and written criteria with the partner site before any routine patients are moved, and review the transfers every month for waiting time and outcome.
- Keep the external overflow provider as a last resort, triggered only when the protocol window will be missed, and report its use to the clinical governance group each quarter.
Results
The clinic rebuilt the triage form and reserved two weekly sessions for urgent cases. Routine referrals stayed in the queue but were offered a telephone pre-assessment first, which removed a noticeable share of them before any testing. The partner site took a small number of stable routine cases under the shared record, and the monthly review found their waiting times were close to the local queue. Urgent referrals were seen within the protocol window in every month after the change. Routine waits stayed long, and Priya said openly that the service had chosen where the wait would fall rather than removing it.
Questions for discussion
- If the urgent sessions were not used in a given week, how would you decide whether to release them to routine referrals?
- What information would you need from the partner site before agreeing that routine patients there were receiving equivalent care?
- How would you explain to a referring clinician why a routine patient was offered a telephone assessment rather than a booked slot?
Case Study 4
Uneven discharge outcomes across the respiratory service
Brindle Lake Respiratory Service, a regional team covering a 120-bed inpatient unit and two community respiratory nursing caseloads.
The situation
Brindle Lake Respiratory Service reviewed its discharge outcomes after the clinical governance group noticed that readmission and missed follow-up rates varied widely between its two inpatient teams. The service runs a 120-bed respiratory unit and supports community nursing caseloads that pick up patients after discharge. An anonymized audit of 312 discharges over the previous several months showed that one team recorded a written action plan for most patients, while the other did so for fewer than half. Follow-up attendance within the target window also differed, and community nurses reported handovers that arrived without a named contact.
The challenge
The group needed to know whether the variation reflected differences in case mix, documentation habits, or the discharge process itself. The indicators were anonymized and aggregated, so the review could not follow individual patients through the system. Staff worried that a quick response would blame a team that was carrying harder cases. The design had to separate likely process causes from case mix and produce a measure the service could track monthly without a large data burden.
Analysis
Patient needs in discharge are shaped by what happens after the ward, so the indicators had to be read with that in mind. A patient sent home with an unclear action plan, or without a named contact, carries risk that does not appear in length of stay. The audit showed the documentation gap but not the clinical evidence behind each decision, so the reviewers kept two questions apart. First they asked whether patients differed in severity and social circumstances. Then they asked whether the process differed regardless of severity, and they compared only patients admitted for the same primary reason.
Ownership looked like the most likely process cause. Team A discharged patients through a ward round that included the community nurse, while Team B sent a discharge letter that the community team often received days later. Team B's protocol required an action plan but did not say who should write it, so it was often completed by a junior doctor who had left the ward before the patient went home. The review found no sign that either team was less careful, only that the handover pathways had different owners at the point that mattered. Any improvement cycle therefore had to change ownership and timing, not only ask for more documentation.
- Before the audit beganAction plans recorded in most discharges from one team only.
- Start of the cycleNamed discharge owner and shared template agreed with both teams.
- In the first monthCommunity nurses confirm receipt of each plan within one working day.
- End of quarterMonthly audit of twenty discharges per team, comparing plan completion and follow-up.
- Next governance reviewDecide whether to extend the cycle to community caseloads.
Actions taken
- Agree one discharge template with both teams, requiring a named owner for the action plan and a named community contact, and remove the option to leave either field blank.
- Assign the action plan to the clinician who is present at the discharge round, and require the discharge letter to reach the community team on the same working day.
- Track four indicators monthly per team: plan completion, receipt confirmation, follow-up attendance within the target window, and readmission, reported as anonymized run charts.
- Set a review trigger so that a team falling below the agreed plan completion rate for two consecutive months meets the governance group to examine process, not individual cases.
Results
Plan completion rose in both teams over the monitored period, and the gap between them narrowed to a level the governance group judged acceptable. Community receipt confirmation improved most, which fits the same-day letter rule. Follow-up attendance moved more slowly and stayed lower for patients with the longest journeys to clinic, which points to transport rather than documentation as the next problem. Readmission counts were too small in each monthly sample to read with confidence, so the group charted them without drawing conclusions. The cycle continues, with the community caseloads now included.
Questions for discussion
- Which indicator would you trust least in a monthly sample of twenty discharges, and what would you do to make it more informative?
- How would you separate a real change in practice from a shift in the patients being discharged during the same months?
- What would you need to see before deciding that the remaining follow-up gap is a transport problem rather than a communication problem?
Case Study 5
A driver's sleep symptoms and a request for silence
Eastbrook Pulmonary Network, a community network of three respiratory clinics and a home support team that covers sleep-related breathing services.
The situation
Gordon, aged 52, works as a long-distance delivery driver. He attended the sleep clinic at Eastbrook Pulmonary Network after his partner raised concern about his breathing at night. The sleep history recorded daytime drowsiness on long routes and several near misses he had mentioned informally, and the assessment led to a referral for further testing. Gordon accepted the plan but asked that his employer not be told, and he asked the clinician, Hannah, to keep the drowsiness details out of any letter that his partner might read. Hannah knew the referral letter would go to his general practitioner, and that his employer's occupational health team might later ask for information with his consent.
The challenge
Hannah had to weigh Gordon's right to decide what is disclosed against a safety risk to other road users, and she had to do so without a clear answer in the local protocol. The duties were not in conflict at every point. Gordon could still be supported to inform his licensing authority himself, and the clinic needed to be clear about what it would do if he declined. His partner had raised the original concern and was waiting for news, which added pressure without changing the duties involved.
Analysis
Consent and confidentiality set the frame. Gordon has decision-making capacity, a right to limit disclosure, and a real interest in keeping his job. His clinical needs are not in question: he needs a diagnostic pathway, practical advice about safe travel, and clear information about how his symptoms bear on driving. The evidence is a sleep history and referral findings, which are enough to raise a safety concern but not enough to judge his fitness with certainty. A shared decision should start with what Gordon understands, what he fears will follow, and what the clinic can offer without depending on disclosure to others.
The team's duties come from local confidentiality policy and from professional guidance on serious risk to others. The local protocol separates a patient's right to decide from a clinician's duty to act when a risk is serious. It asks the clinician first to encourage the patient to inform the relevant authority, record the discussion, and agree a review date. If the patient declines and the risk remains, the case goes to the clinical lead and the information governance contact. Hannah therefore needed a second opinion and a short file note explaining why disclosure was or was not made. Coordination with the general practitioner mattered, since the GP could support Gordon without breaching confidence.
Actions taken
- Use a written agreement form that sets out what the clinic will disclose, to whom, and under which policy, and give Gordon a copy before the next appointment.
- Arrange a same-week conversation with the clinical lead before any disclosure decision is made, and record the reasoning in the file alongside the protocol step that applied.
- Invite Gordon's general practitioner into a joint plan so that ongoing support, review dates and any licensing questions are handled by one named clinician rather than split across services.
- Add a section to the sleep clinic guidance on safety-sensitive occupations, covering consent conversations, escalation steps, and the documentation expected at each stage.
Results
Gordon agreed to inform his licensing authority himself after a second conversation with Hannah and the clinical lead. The clinic recorded his decision, set a review date within the month, and confirmed in writing what it would share if he later withdrew consent. His partner was told only what Gordon had agreed to share. The team later reviewed the case and found the protocol steps had been followed, but the guidance had not explained how to respond when a family member had raised the original concern. The guidance was revised to close that gap.
Questions for discussion
- At what point in Gordon's case would you have considered the duty to others to outweigh his wish to limit disclosure, and what would you have needed to know first?
- How would you handle a partner who asks for updates when the patient has asked the clinic to say nothing?
- What should a written consent agreement contain so that it is useful to the patient, the team and any later reviewer?
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.