Neurology and Neurodiagnostic Technology Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases come from a neurology service in a regional hospital that runs a neurodiagnostic lab for EEG, nerve conduction studies, and monitoring, and takes referrals from outpatient clinics. None of them turns on a single judgment. They concern the work around it: who notices a change, how a request moves through a queue, what a handover carries and what it drops, how a service checks whether its results are holding, and how a team talks with a patient when the next step is unclear. Read each one with the local protocols open and follow the information.
Case Study 1
A changing history and a routine referral
Tamsin Ridge Regional Hospital, a 320-bed hospital with a neurology clinic and an inpatient ward for neurological care
The situation
Ruben, a retired surveyor in his sixties, was referred to the neurology clinic after two months of intermittent weakness in his left hand and a change in his handwriting that his wife had noticed. The referring physician had requested an outpatient review and a routine brain imaging order. Over the next three weeks his picture shifted. Episodes became more frequent, he reported difficulty fastening buttons, and on one visit he described a brief loss of speech that cleared within minutes. The nurse coordinator, Priya, logged each change in the shared record. The imaging request, though, sat in routine scheduling because the requisition had no field for changing urgency. Gareth, the triage lead, saw the notes only during the weekly review.
The challenge
The team needed to decide whether the pattern changed investigation priority and whether it met the threshold for same-day escalation under the local transient neurological symptoms protocol. That protocol set urgent routes for new focal symptoms, but it depended on someone recognizing the change and writing it in the right field. Priya was not sure whether a fluctuating speech episode counted as a new event, and the on-call neurologist was in a clinic across the site. Ruben was managing at home and had asked whether he needed to come in sooner.
Analysis
Teams grounded in Neurology and Neurodiagnostic Technology tend to read a changing history as a sequence, and this case rewards that habit. The clinical evidence was a trajectory: rising episode frequency, a new fine motor complaint, and a brief language disturbance. Any one of these might be put down to fatigue or anxiety, but together they described a pattern that the local protocol treats as time sensitive. The information existed in the record already. It was spread across three entries written by three people, so no single reader saw the full sequence. Ruben's needs were equally clear: an honest account of what would happen next, a named person to call, and some evidence that his own report had been heard.
Coordination and protocol are where the delay accumulated. The referral form gave no route to raise urgency once new information arrived, so the imaging order kept its routine priority. The protocol placed the escalation decision with the attending neurologist, but the attending was never told that the speech episode was new. A written trigger list, held by the nurse coordinator, would have turned that dependency into a routine step. Any reported change in speech, new weakness, or rising episode frequency would route straight to a same-day review without waiting for a physician to read the full file. Nobody in this case acted carelessly. The system relied on memory and on the order in which people happened to read the notes.
- 1Symptoms reportedLeft hand weakness and handwriting change recorded in primary care notes.
- 2Routine imaging orderRequisition lacked urgency field, so the request stayed in routine scheduling.
- 3Episode pattern changedFrequency rose and a brief speech loss was logged by the coordinator only.
- 4Attending not informedEscalation decision depended on the attending reading all three entries.
- 5Trigger list proposedWritten criteria would route any new focal change to same-day review.
Actions taken
- Add an urgency upgrade field to the imaging requisition so new clinical information can raise priority without a new referral. The nurse coordinator owns the field.
- Write a one-page trigger list for transient neurological symptoms that names the criteria for same-day review, including any new speech change, new weakness, or rising episode frequency. The attending signs it off.
- Contact the patient the same day with a named contact and a clear statement of the next step, and document the call in the shared record so the next reader sees it.
- Run a short case review in the weekly meeting that reads the full entry sequence aloud, so the team practices reading changes as a timeline rather than as separate notes.
Results
Within the quarter the clinic added an urgency upgrade field to the requisition, and the trigger list was adopted with small edits. Ruben's imaging was moved to an urgent slot, and the attending saw him the same day the speech episode was entered. Follow-up identified a cause that needed a different plan, and his care moved to a specialist pathway. The team was candid with Ruben that the delay had happened. The coordinator now reads the full entry sequence before each triage decision, and the clinic tracks how many new focal referrals reach a physician the same day.
Questions for discussion
- Which fields in a referral form would need to change for a speech episode to reach the attending without a verbal handover?
- How should a service weigh a patient's own account of a change against a clinician's view that symptoms are stable?
- What would a trigger list need to include to guide escalation without generating unnecessary same-day reviews?
Case Study 2
The handover that left out the pending study
Calder Bay Health Partners, a district hospital group with a 22-bed neurology ward and a shared neurodiagnostic lab
The situation
Mei, a patient in her forties, had been admitted to the neurology ward for prolonged monitoring after an unexplained episode of altered awareness at home. A monitoring study had been ordered earlier in the day, and a fall risk flag had been set on her record during the afternoon. At the end of the day shift, Anil, the outgoing nurse, completed the structured handover sheet in a hurry and gave a verbal report at the bedside desk. The sheet listed her medications and observations but described the monitoring study as already under way. The fall risk flag was not mentioned. Joanna, taking over, assumed the equipment had been checked and began her rounds.
The challenge
The review had to explain how a gap that several safeguards were meant to catch had reached the bedside, and then decide what would change. The unit's handover sheet, read-back rule, and charge nurse review were all in place. The difficulty was that each depended on someone else noticing the omission first. The team also had to keep the patient's needs at the center of the discussion, since the monitoring was still required and the fall risk was still active when the gap came to light.
Analysis
Handover is often described as a list of tasks, but for Mei the need was a set of open questions: what was pending, what had changed since the last review, and which risks were still active. The clinical evidence in the record was clear about the monitoring plan, yet the verbal report reduced it to a single line. The fall risk flag had been set for good reason and was dropped from the conversation entirely. Nurses on a neurology ward rely on the record for detail and on the report for priority. When those two diverge, the oncoming nurse works from information that looks complete but is not.
The protocol required that open items be read aloud and acknowledged by the receiving nurse, yet in practice the acknowledgment was often a nod. The structured sheet was designed to prompt for pending tasks, but Anil filled it in at the end of a busy shift and treated the study as already in progress. Several safeguards existed: the sheet, the read-back rule, and a charge nurse who reviewed high-risk patients at the start of each shift. None of them fired, because each relied on another person to notice the gap first. The most useful change is structural. A pending item should be a required field with a named owner and a time, so that its absence is visible rather than assumed.
- Earlier that shiftMonitoring study ordered and fall risk flag set in the record.
- Ten minutes before changeSheet completed quickly, with the study listed as already under way.
- At the bedside handoverVerbal report omitted the pending check and the fall risk flag.
- Forty minutes after handoverOncoming nurse found the equipment check had not been done.
- Same shift reviewCharge nurse flagged the gap before any harm reached the patient.
Actions taken
- Make each open item on the handover sheet a required field with an owner and a time, so a pending study cannot be left out by omission. Owners sign each item at the bedside.
- Require the receiving nurse to ask one question about each open item rather than accept a nod, and record the answer on the sheet. Read-back becomes a check, not a formality.
- Audit ten handovers per month on the neurology ward for omitted pending items and fall risk flags, and report the count to the nursing quality group.
- Run a short simulation during the monthly nursing huddle using a de-identified handover scenario with a deliberately missing item, and ask staff to name the gap.
Results
After the sheet change, the first monthly audit found fewer omitted items than the baseline month, and each remaining case was reviewed with the nurses involved. The owner field was used on most shifts, though the evening team needed a reminder about the time column. The patient's monitoring was completed without further gaps, and the fall risk flag was restored at the start of the next shift. Staff said the question-based read-back took longer but reduced follow-up calls. The charge nurse still reviews high-risk patients at the start of each shift, now with the sheet open.
Questions for discussion
- Which items on a handover sheet are most likely to be dropped under time pressure, and how would a team find out?
- How should a read-back differ from a simple confirmation, and what does the receiving nurse need to hear in order to act?
- What measure would show whether a handover change is working on the ward without adding a reporting burden for nurses?
Case Study 3
Choosing where scarce EEG time should go
Brindle Lake Regional Health, a 260-bed hospital whose neurodiagnostic lab serves routine and urgent referrals
The situation
Brindle Lake's neurodiagnostic lab runs routine and urgent EEG, nerve conduction studies, and a small sleep monitoring service, with two EEG rooms and four technologists. In the last twelve months the lab received 1,140 referrals, and the routine waiting list reached 412 requests. Then one technologist left, and a second EEG machine went out of service for repair for most of the quarter. Marisol, the lead technologist, and Owen, the service manager, were asked to restore access without extending hours beyond what staffing allowed. About 37 urgent requests arrived each week, and each needed a slot within the regional target window.
The challenge
The choice was not simply how many patients could be seen. Options included tighter triage, block booking, reallocating nerve conduction time, and sending routine studies to an outside partner. Each would move risk somewhere else. The team had to protect urgent patients first, avoid letting routine waits grow without oversight, respect the regional urgency categories and the competence rules for staff working across studies, and keep the referring clinics informed about what would change for their patients.
Analysis
Patient needs differ sharply between the two queues. Urgent referrals usually come with a specific clinical question that a timely result will help answer, and delay can change what the clinician is able to do next. Routine referrals wait for diagnostic clarity, and a long wait can mean repeat visits, lost follow-up, and growing uncertainty for the patient. The evidence available to the lab was thinner than it should have been. Referral forms carried a clinical question, but urgency was self-declared, and only about 60 percent of referrals had been checked against the regional criteria. A waiting list count alone hides that gap.
Coordination determined which options were realistic. Tighter triage only works if referring clinicians supply a clear question and a review date, so the team needed the clinic liaison in the decision. Block booking protects urgent slots but risks idle time when no urgent cases arrive. Reallocating nerve conduction time would leave another service short, which the protocol on shared equipment does not allow without a formal agreement. An outside partner could absorb routine studies, but only under a quality agreement covering reporting, indicators, and who reviews returned results. The combined approach the team chose used all four options in a limited way, with the partner restricted to routine work.
Actions taken
- Adopt a daily triage huddle of twenty minutes with the lead technologist, a referring clinic liaison, and the service manager, to assign urgent requests to protected slots before routine bookings are made.
- Require referral forms to state the clinical question and a review date, and send incomplete forms back to the clinic within one working day rather than placing them in the queue.
- Sign a four-week overflow agreement with a partner laboratory for routine studies only, with shared quality indicators and a named contact who reviews every returned report.
- Review the waiting list weekly by age of referral and urgency category, and publish the oldest routine wait alongside the total, so the count does not hide the longest delays.
Results
After six weeks, urgent requests were seen within the protected window in nearly every case, and each exception was documented and reviewed at the huddle. The partner laboratory handled a share of routine studies, and the total waiting list fell. The oldest routine waits, however, stayed longer than the service wanted. The referral return rule added work for the clinic liaison until a shared template was agreed. One referring clinic said the forms were clearer, while another asked for a phone route for urgent questions. Marisol and Owen agreed to keep the daily huddle through the quarter and to revisit overflow terms when the second machine returned.
Questions for discussion
- What information would a referring clinician need to supply so that urgency is a judgment the lab can check rather than a label it accepts?
- When a waiting list falls but the oldest waits rise, what does that suggest about how capacity is being allocated?
- What conditions should a partner laboratory meet before routine patients are sent there, and who checks them?
Case Study 4
Wide variation in waits across three clinics
Saltmarsh Neurology Group, a network of three outpatient clinics sharing one neurodiagnostic lab
The situation
Saltmarsh Neurology Group runs three outpatient clinics and draws on one shared neurodiagnostic lab, with fourteen neurologists and a quality committee that meets monthly. Its quarterly indicators showed wide variation. Median time from referral to first clinic visit ranged from about three weeks at the fastest clinic to almost six weeks at the slowest. The rate of studies requested a second time, usually because the first report was unusable, differed between sites as well. Across the period the group handled 2,340 referrals. Nadia, the quality lead, and Tobias, the data analyst, prepared an anonymized extract with patient identifiers removed and small counts suppressed.
The challenge
The committee wanted to know whether the variation reflected differences in process or differences in the patients each clinic saw, and what to do about it without blaming individual clinicians. The data were coarse. Wait times did not separate urgent from routine referrals, and the letter completeness indicator was not measured at all. The committee also had to respect the data governance protocol, which limits how small groups can be reported and requires that any change be tested before it is spread.
Analysis
The variation matters because it falls on patients who are waiting for diagnostic clarity. A long wait for a first visit can mean more uncertainty, a delayed plan, and a family that carries the question alone. Repeat requests for studies mean repeat visits and another period of waiting. Clinical letters that omit a documented plan slow the primary care response, even when the clinical work itself was sound. The indicators are blunt, though. Wait time can reflect case mix, since one clinic may receive more urgent or complex referrals, so the first task is to compare like with like before drawing any conclusion about performance.
The likely causes sit in process rather than in individual skill. Triage practice differed: one clinic assigned urgency from the referral text, another from a phone call, and the committee had no shared definition. Letter templates also varied, and two of them lacked a required field for the next step. Studies were sometimes ordered without a check of prior results, which tends to produce repeat requests. The governance protocol limits how small subgroups can be reported and asks for changes to be tested in one setting before spreading. That fits a monitored cycle, with a stop rule set in advance.
- Plan Agree one triage template and one letter template across all three clinics.
- Pilot Run both templates in one clinic for six weeks with a named champion.
- Check Compare waits, repeat requests, and letter completeness against the baseline.
- Act Adopt, adjust, or stop each change at the monthly committee meeting.
Actions taken
- Pull the anonymized indicators for each clinic by urgency category, so that wait times are compared within like cases before any clinic is described as slower than another.
- Audit a random sample of twenty clinical letters per clinic against a short completeness checklist, scored by two reviewers who do not work in the clinic being audited.
- Test one shared referral triage template and one letter template in a single clinic for six weeks, with a named clinician champion who reports problems at the weekly huddle.
- Set a monitoring plan with four indicators, a baseline, and a stop rule, and bring the results to the quality committee at the end of each cycle for a decision.
Results
Once waits were compared within urgency categories, the gap narrowed but did not close, which suggested that triage practice explained part of the difference. In the pilot clinic, the share of letters missing a documented plan fell, and repeat requests for one study type dropped over the test period. The committee noted that the sample was small and the pilot team was stable, so the result was treated as promising rather than proven. The second clinic began its test in the following cycle with a champion from its own staff. The indicators now sit on one dashboard, so each change can be read against the baseline.
Questions for discussion
- Which indicators in this network would be most affected by case mix, and how would a team separate that effect from differences in process?
- How should a committee decide whether a pilot in one clinic is strong enough to justify a change across the network?
- What should a stop rule specify so that a change is not kept only because the team has already invested effort in it?
Case Study 5
A patient, her son, and the limits of sharing
Ardenvale Specialist Neurology Centre, a tertiary service with a multidisciplinary clinic for complex neurological conditions
The situation
Ingrid, a woman in her forties living with a progressive neurological condition, attends the tertiary clinic with her adult son, Felix, who helps with transport and appointments. At the last visit Ingrid asked the team not to share her test results with Felix, and the note recorded that request in her own words. Felix had phoned the clinic twice to ask about the results and had been told the team could not discuss them. Samuel, the consultant neurologist, wanted to explain the planning options to both of them. Hannah, the specialist nurse, held the record of Ingrid's preference, and Kwame, the social worker, had been asked to look at the caring arrangement at home.
The challenge
Ingrid has capacity and has made a clear choice, so the duty is to respect her confidentiality while helping her plan with the support she wants. The difficulty is that the plan depends on Felix, and he has a reasonable expectation of being informed. The team also had a research sample to collect at the same visit, under a separate consent. The question was how to keep the options open without pressing Ingrid, and at what point the matter needed to go to the information governance lead or the ethics committee.
Analysis
Ingrid's needs are practical as well as informational. Her condition will shape planning decisions over time, and Felix is the person who will help carry them out. Withholding everything could leave her with less support than she wants. Her own written preference is the clearest evidence the team has, and it does not say that Felix should be excluded from all contact, only that results are hers to share. That distinction matters. Clinicians need to separate what Ingrid has agreed to share from what Felix has asked for, and avoid implying that a family member holds decision authority he has not been given.
Coordination here depends on one record that everyone reads the same way. Hannah had documented the preference and passed it to the reception team, but Samuel's notes did not mention it, so the phone calls were handled inconsistently. The confidentiality protocol requires a documented conversation before any sharing, and the research consent is a separate decision that cannot be made under family pressure. Suitable choices are a joint conversation only if Ingrid chooses it, a separate appointment for the research question, and a written summary she has approved. Escalation is warranted if her preference changes, or if the family's requests continue after she has been clear.
Actions taken
- Record Ingrid's preference in her own words in the shared record, noting who she named and mark it as the current instruction on sharing.
- Hold a joint conversation only if Ingrid chooses it, with Hannah present to explain the plan in plain terms and Ingrid deciding what is said before Felix joins.
- Take the research consent in a separate appointment, with written information sent in advance and enough time for Ingrid to decide without family present, and confirm she can withdraw at any point.
- Refer the question of sharing with a family member to the information governance lead and the ethics committee if Ingrid's preference changes or if pressure from family continues, and document each step.
Results
Two weeks later, Ingrid chose a joint conversation with Felix. Before it, the team had prepared a short written summary of what she had agreed to share. In the meeting Samuel explained the planning options, and Ingrid kept detailed results private, which Felix accepted without pressure. Ingrid declined the research study for the time being and asked to be contacted again after her next review. The information governance lead confirmed that no formal referral was needed at that stage. Hannah now checks the sharing preference at each appointment, and the template asks whether the patient wants family present.
Questions for discussion
- How should a team distinguish between a family member's practical role and any formal authority to receive clinical information?
- What does a documented preference need to say to be useful to a colleague who was not present when it was given?
- When a patient declines research participation, what duties remain for the team to keep that option open without pressure?
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.