Ophthalmology, ENT and Sensory Care Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases come from the working life of eye, ear and sensory services, where a single phone call, a missed line in a handover note or a full clinic list can change what a patient receives and when. The organizations are fictional, but the pressures will be familiar to anyone who has worked a triage desk or run a referral pathway. Each case sets out a situation, names the difficulty, and then examines patient needs, clinical evidence, team coordination and the protocols that govern the decision. Discussion questions work best with a colleague.
Case Study 1
Changing eye symptoms in a patient awaiting review
Calder Vale Eye and Ear Unit, a hospital outpatient service with a walk-in eye desk, two eye clinics and an on-call rota for urgent referrals.
The situation
A woman in her sixties called the walk-in eye desk at Calder Vale on a Monday to say that the vision in her left eye had been blurred for three days and that a shadow seemed to be moving across it. Her notes showed a stable review eight weeks earlier with no open actions. Amira, the triage nurse, took the call. The local protocol lists sudden or progressive loss of vision in one eye as a same-day assessment criterion, but the patient described the change as gradual and asked to wait for her next appointment in three weeks, as she had no transport that week. Amira wanted a second opinion before deciding.
The challenge
The symptoms could reflect several conditions, some of which are time sensitive and some of which are not, and the description alone does not separate them. Amira had to decide whether to book a same-day slot, ask the on-call ophthalmologist for telephone advice, or accept the patient's preference and bring her forward within the week. A delay could leave a serious change unrecognized, while an unnecessary same-day referral would pull a slot from an urgent list and cause a second journey the patient could not manage.
Analysis
Teams grounded in Ophthalmology, ENT and Sensory Care usually start by separating what the patient needs from what the system would prefer. Here the patient needs a reliable assessment within a window that matches the risk, and she also needs transport she can actually use. The clinical evidence is thin: a history of a blurred area with a moving shadow, no measured change in the notes, and no examination since the last review. Amira cannot rule out a change that matters, so the record should say so rather than label the call routine. Her safest first move is to treat the description as evidence and ask for the earliest examination the protocol allows.
The protocol gives Amira more room than she first assumed. Sudden or progressive loss in one eye sits on the same-day list, but the criterion depends on the history she records, so her note must capture onset, pace and any new shadow in words the on-call clinician can act on. The ophthalmologist on call needs a short written summary before a phone decision, and the booking clerk needs to know which slot class to use. Calder Vale's escalation policy expects a named clinician to own any deferral, so the decision to wait belongs to a person, not to the calendar. Writing that owner into the record closes the loop.
Actions taken
- Record onset, pace and any new visual change in the patient's own words, then read the note back to her to confirm it matches what she described.
- Call the on-call ophthalmologist with the summary before any decision is made, and document the advice, the time of the call and the name of the clinician who gave it.
- If the examination cannot happen within the protocol window, book the earliest slot, arrange transport through the clinic's support scheme, and set a recall that a named clinician checks.
- Ask the service lead to review all same-day criteria next month against this call, so the wording used at the desk matches what the protocol actually asks staff to detect.
Results
The on-call ophthalmologist advised the earliest available examination that week, and the clinic found a transport gap that the desk had not considered. The patient was seen on the fourth day after the call. The examination found a change that needed prompt follow up, and the clinician arranged the next step the same afternoon. A desk audit later showed that three similar calls in the previous quarter had been closed as routine without a named owner. The service lead changed the desk script so that onset, pace and the clinician's name must be entered before a call can close.
Questions for discussion
- Which features in the first call would have moved this patient to a same-day slot, and which would have kept her in the routine pathway?
- How should a desk decide between a protocol criterion and a patient's stated preference when the two point in different directions?
- What would a named owner for each deferral change about the way your own service records routine calls?
Case Study 2
A handover gap after a same-day eye list
Tidewell ENT and Eye Clinic, a day unit running two operating lists each week, a shared recovery bay and a written handover standard.
The situation
On a busy Thursday, a man in his forties had a same-day eye procedure at Tidewell and went home in the afternoon. The operating team completed a standard handover to the recovery nurse, Oksana, but the note sent to the patient's general practice listed only the planned follow up date. The case was handed over at shift change by the day coordinator, Marcus, who had not been present for the list. Two days later, the patient phoned the unit with new symptoms that were not mentioned on the discharge sheet and were not in the summary the practice had received.
The challenge
The gap was small on paper. A line about an instruction to report a specific change had been left out of the handover, and the discharge sheet carried the same omission. Nobody had deliberately withheld it. The question for the team is which safeguard should have caught it, why none did, and what a change to the process would look like if it was measurable rather than another reminder to be careful.
Analysis
Patient needs in a same-day eye or ear service concentrate in the first days after discharge, when a person who was told to expect some change must recognize the one change that is not expected. The clinical evidence sits in the gap between what the operating team recorded and what the patient later reported. He did not know which symptom mattered, and the practice did not know which symptom to watch for. The unit's notes were accurate as far as they went, which is why a routine audit of completeness would have passed them. Reading the record alone shows what was written, not what the next clinician needed.
The applicable protocol requires a written handover that names the symptoms to report and the person to call, and the unit had both in its template. The operating team filled the clinical fields and left the patient-facing section for the discharge nurse, who was not on the list that day. Shift change then moved the case to a coordinator who relied on the notes, and the practice received a summary built from the same notes. Each step was reasonable, yet no one owned the check that the patient's own instructions matched the handover. A closed loop would name one person to confirm the patient-facing content before discharge.
- 1Operative list completedClinical fields filled; patient-facing section left for discharge.
- 2Discharge sheet writtenWarning section left generic, so the key change was not named.
- 3Shift handover givenCoordinator worked from notes and had no direct patient contact.
- 4Practice summary sentSummary built from the same notes, carrying the same gap forward.
- 5Patient calls with symptomNew symptom was absent from every written record the patient held.
Actions taken
- Add a required field to the discharge template that lists, in plain language, the two or three changes that mean the patient should call the unit the same day.
- Read the completed discharge sheet back to the patient and carer before they leave, and tick the entry on the sheet only after they have repeated the key warning in their own words.
- Send the practice a summary generated from the discharge sheet, not the operative note, and copy the same text to the patient's record within the same working day.
- Audit a monthly sample of same-day discharges, counting how many patients repeat the warning correctly on the next-day call, and report any shortfall against the agreed threshold to the governance meeting.
Results
The unit made the discharge sheet's warning section mandatory and added the read-back step in the first month. The next-day call audit found that the patient repeated the warning correctly in forty four of the fifty sampled cases, while the earlier sample had found the warning was rarely recalled. The patient who called on the second day was assessed the same day, and the new symptom was managed without delay. Governance asked for two more quarters of audit.
Questions for discussion
- Which single sentence on the discharge sheet would have been most useful to the practice, and who should have been responsible for writing it?
- How would your unit tell the difference between a handover that is complete on paper and one the next clinician can act on?
- What would you need to measure for a read-back step to be judged a success rather than simply recorded as done?
Case Study 3
Choosing how to ration a stretched eye clinic
Brindle Lane Sensory Care Group, a community service running eye clinics and hearing assessments across three sites with a shared pool of clinicians.
The situation
At Brindle Lane, the waiting list for hearing assessment and the eye clinic had both grown over the winter months, and the two services shared one audiology technician and two optometrists on Fridays. A referral backlog of about 1,200 patients had built up, of which roughly one in ten carried a clinical flag from the triage tool. The service manager, Dariusz, was asked to find capacity without extending the hours, and the staff group had already said that the existing clinic lists could not absorb more new patients without longer waits for review appointments.
The challenge
Three options were on the table. The first was to triage the backlog more tightly so that only flagged patients were booked. The second was to move routine reviews into a shared scheduling pool across both services. The third was to pause new eye referrals for a fixed period. Each option protected something and put something else at risk, and the team had to decide which risk they were willing to carry before the next list was built.
Analysis
The flagged minority needs assessment within a clinically set window, while most of the rest have stable needs that can wait for a planned review without harm. The evidence the team has is a triage tool score, a referral date and a short free-text note, which is enough to sort urgency roughly but not enough to rank patients finely. Overreliance on the score would move people with real need down the list because their notes were brief. Any allocation rule should keep the flagged patients fixed, then use the referral date as the tie-breaker, with the free-text note used only to escalate.
The applicable protocols set the floor. The triage policy requires that flagged patients are seen within the window it names, and the local capacity policy says that any change to shared sessions must be agreed with both service leads and recorded. That second requirement is where the options are tested. Moving routine reviews into a shared pool touches two rotas, a technician's training schedule and the optometrists' scope at each site. Coordination has to happen before the list is built, not after patients have been told a date. A short signed decision by both leads keeps the reasoning visible when a patient asks why they waited.
- Start of quarterFlagged list fixed and pooled review trial agreed by both leads.
- Third weekWaiting times for routine reviews checked at both sites.
- Fifth weekTechnician log shows rebooking takes longer than assumed.
- Sixth weekBooking template changed to capture rebooking time directly.
- End of quarterTrial reviewed; pause on new referrals never needed.
Actions taken
- Hold the flagged list fixed and book it first, using the triage window as the only hard rule, so that no change to the shared pool can move a flagged patient down.
- Pool routine reviews across both sites for one trial period, with a written rule for the tie-breaker based on referral date, and review the rule at the end of each month.
- Pause new routine eye referrals only if the pooled list passes the agreed waiting threshold for two consecutive weeks, and tell referrers in writing the date the pause began.
- Ask the audiology technician and both optometrists to log the time spent on rebooked patients for four weeks, so the trial's cost to clinic time is measured rather than estimated.
Results
The flagged list stayed fixed, and the pooled review trial ran for the planned period. Across the trial the waiting time for routine reviews fell by roughly a fifth at the smaller site and stayed level at the larger one. The pause on new eye referrals was never triggered. The technician's time log showed that rebooking took about eleven minutes per patient, more than the team had assumed, which led to a change in the booking template. Dariusz said the written decision was the part that made the compromises easy to explain to referrers.
Questions for discussion
- Which of the three options would your own team have chosen first, and what evidence would have changed that choice?
- When a flagged list is kept fixed, who is accountable for the patients left waiting behind it?
- How would you judge a capacity trial a success if the waiting time improved but the time spent on rebooking rose?
Case Study 4
Unexplained variation in unplanned return visits
Pellow Street ENT Service, a hospital outpatient department with three satellite clinics and a shared audit team of two analysts.
The situation
The governance group at Pellow Street reviewed quarterly indicators for its outpatient ear and balance clinics and noticed that the rate of unplanned return visits within the window varied sharply between the main site and its three satellite clinics. Over the most recent full period, the main site recorded a return rate of about one in nine patients, while one satellite recorded nearly one in five. The audit team, led by Priya, had anonymized the data at patient level, so the review could look at process without naming individuals. The group had to decide whether the gap reflected case mix, clinic practice or recording.
The challenge
Return visits are a blunt measure. A patient may come back because the first visit was incomplete, because the clinic gave advice that did not hold, or because the patient's condition changed and the return was appropriate. Without a way to separate these, a lower rate at one site could reflect better care, shorter follow up or coding habits. The group needed a process explanation that would survive scrutiny before it asked any clinic to change how it worked.
Analysis
Patients returning unexpectedly need a visit that answers the question they came with, and a clinic that can tell, at the first contact, whether a return is likely. The evidence available is limited to the indicator, the coded diagnosis and the clinic letter. Each of these is incomplete in a different way. Coding varies with the clerk, letters are written by different clinicians, and the indicator counts a return whether or not it was planned. The first task is to pull a sample of returns from each clinic and read the notes against a common checklist, so that the group compares like with like before it compares rates.
The local quality policy requires a documented improvement cycle with a named owner, a baseline and a review date. The governance framework also expects agreement from the clinicians who will carry out any change. The main site uses a shared triage nurse and a single follow up booking team, while the satellites rely on the clinicians' own diaries. That difference alone could produce a different return pattern, so the group should check how bookings are made before it blames either practice. Joint review meetings with the satellite leads, held in the same week as the audit, keep the findings from being read as a judgment on any one team.
Actions taken
- Pull a random sample of unplanned returns from each clinic, and have two reviewers read each record against one common checklist before any rate is compared.
- Classify each return as planned, avoidable, clinically appropriate or uncertain, and record the booking route the original visit used, so the cause can be traced to a step in the process.
- Agree one follow up pathway with the satellite leads, with a single booking route and a written trigger for early review, then run it for one quarter in two clinics.
- Chart the unplanned return rate monthly on a shared run chart with the baseline and target marked, and review it at the governance meeting with the audit team present.
Results
The sample review found that a large part of the apparent difference came from how returns were recorded rather than how patients were managed. One satellite had been coding planned reviews as unplanned returns, and the main site had been booking follow up through a route that delayed early recall. The shared pathway ran for one quarter in two clinics. Genuinely unplanned returns fell at the satellite with the highest rate, and the group agreed to extend the trial. The indicator was rewritten so that planned reviews are excluded.
Questions for discussion
- Which part of the indicator would you check first before accepting that two clinics are performing differently?
- How much weight should a sample review carry when the reviewers know which clinic each record came from?
- What would a run chart need to show, over how many months, before you were willing to call a change an improvement?
Case Study 5
Shared decisions when a family disagrees about treatment
Ashgrove Hearing and Vision Hub, a community service offering pediatric and adult sensory assessments with an on-site social work liaison.
The situation
A seventeen year old, Teo, attended the Ashgrove sensory clinic with his mother, Adaeze, after a referral for progressive loss of hearing in one ear. Teo was competent to understand the options described to him, and he asked the clinician, Yusuf, to speak with him alone. He wanted to decline a planned further assessment and asked that his mother not be told his reasons. Adaeze held parental responsibility and expected to be part of any decision about her son's care. The clinic had a consent and confidentiality policy, but its wording on how to handle a conflict between a young person and a parent was general.
The challenge
Two duties pull in different directions. Teo's confidence must be respected unless there is a safety reason to share, and his mother has a legitimate interest in his health and a legal role that the team cannot ignore. The clinician must decide what to say to Adaeze, whether Teo's wish to decline is informed and stable, and when the matter should go to the safeguarding lead or the medical director rather than stay with the clinic team.
Analysis
Teo's needs are twofold. He needs a clear account of what the assessment would tell him and what declining would mean for his hearing over time, and he needs to feel that his view counts without being cornered. The clinical evidence in the record shows a progressive pattern and a referral that asked for timely review, but it does not show whether Teo understood the implications of delay. That is the evidence the clinician should gather first. A private conversation that tests understanding in his own words is more useful than a written summary, and it gives the team something to weigh when the question of disclosure arrives.
The consent and confidentiality policy presumes that a competent young person decides about their own care, and that information is shared only with a lawful basis or a safety reason. It also sets out a route for conflict: the clinician records the assessment, discusses it with a senior colleague, and documents who was told what. Coordination matters here because the social work liaison at Ashgrove knows the family history and the mother's concerns, while the clinician knows what Teo said. Neither has the full picture alone. A joint discussion lets the team agree on what to disclose and why, and it puts the decision with a named person.
- Understand the person Test understanding privately and record the person's own account.
- Share permitted information Agree with the person what can be told to family and why.
- Involve senior support Bring in a senior colleague and the liaison for a joint decision.
- Record and review Write the disclosure decision, its reasons and a review date.
Actions taken
- Speak with Teo alone, check his understanding of the options and of declining in his own words, and record that conversation in the clinical notes with the time and the clinician's name.
- Tell Adaeze, with Teo's agreement, what the clinic can and cannot share, and explain that her views will be heard even where the decision rests with her son.
- Hold a same-day discussion with the senior colleague and the social work liaison, and write down the disclosure decision, its reasons and the named person responsible for it.
- Escalate to the safeguarding lead or the medical director if Teo's understanding is doubtful, if his safety is at risk, or if the team cannot agree a disclosure plan within two working days.
Results
Teo's understanding was judged sound on the second conversation, and the team recorded that he wished to decline the further assessment for now and to revisit the decision at a set review. Adaeze was told what would stay confidential and what would be shared for safety. She was not satisfied, and the clinic offered a joint meeting, which she declined. The disclosure decision was recorded with its reasons and a named clinician. The clinic's policy wording was revised to give a short route for conflicts between a young person and a parent.
Questions for discussion
- What would have changed in your approach if Teo had asked for the conversation to stay entirely private, with no safety concern at all?
- How does a team decide when a young person's understanding is good enough to rely on, and who should be asked to check that judgment?
- Where should a disclosure decision be written so that a later reviewer can see the reasons without reading the whole record?
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.