Cardiac Care Support Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
The five cases below follow patients and staff across one regional heart service, from a step-down unit and an outpatient diagnostic center to a community follow-up clinic. Each case centers on a decision that looked routine at the time and became harder once the details were laid out. Read each one for four things: what the patient needs at that moment, what the clinical evidence shows, how information moves between team members, and which local protocol sets the boundaries of the next step. The people and organizations are fictional.
Case Study 1
A slow afternoon on the step-down unit
Calder Ridge Regional Hospital, a 240-bed acute care hospital with a 22-bed cardiac step-down unit
The situation
Dolores, a 71-year-old retired schoolteacher, was admitted to the step-down unit after a day of chest tightness that eased with rest. Overnight she reported two shorter episodes, and by the morning round her blood pressure was steady and she described herself as better. The day nurse, Hannah, noticed something different in the early afternoon. Her breathing rate had crept up, she had become quieter and reported new breathlessness walking to the washroom, and her early warning score had moved from 2 to 4. Hannah repeated the observations, checked the cardiac monitor, and recorded the change in the nursing notes.
The challenge
The question for the team was whether a change this size warranted a senior review now or could wait for the scheduled ward round at the end of the day. Tomas, the cardiology registrar, had seen Dolores that morning and judged her stable. The repeat results were still abnormal but not dramatically so, and the unit's escalation policy listed the score threshold and new symptoms as separate triggers that needed to be weighed together.
Analysis
Dolores's needs were less about any single number than about the direction of travel. A score of 4 is not alarming on its own, but a score that has risen across the afternoon, paired with new breathlessness in an older patient with known heart disease, is a trend that deserves a second look. The evidence the team had was partial. The observations were recorded at intervals, the monitor showed rhythm changes that were not clearly new, and Dolores was minimizing her symptoms. Teams grounded in Cardiac Care Support usually start by separating what changed from what was merely recorded, then asking which findings the patient's own account might be hiding.
Coordination was where the afternoon could have gone wrong. Hannah had the observations and a sense that something had shifted, but the registrar was on another floor and the on-call cardiologist was in clinic. The escalation policy asks for a bedside review within the hour when a rise of two points comes with a new symptom, and a phone conversation alone does not meet that. The first call was framed as a question about whether the change could wait, and that gave the registrar room to agree it could hold. A short structured message stating the trend, the symptom and a specific request would have removed that room for interpretation.
- Morning roundObservations stable and symptoms reported as improving.
- Early afternoonScore rose from 2 to 4 with new breathlessness on walking.
- Mid afternoonNurse repeated observations and phoned the registrar, asking whether it could wait.
- Late afternoonRepeat results still abnormal, so the nurse called again.
- Early eveningBedside review within the hour and closer monitoring agreed.
Actions taken
- Add a one-line trend statement to every escalation call, covering the direction of change, any new symptom and the specific review being requested. Audit ten calls a month for completeness.
- Set a rule that a score rise with new symptoms triggers a bedside review within the hour, written on the unit board and reinforced at each shift huddle for the next three months.
- Have the charge nurse review the escalation log weekly, comparing time from trigger to bedside review, and report any case that exceeded the standard to the clinical governance meeting.
- Ask the evening team to repeat the full trend chart, not only the latest score, at handover for any patient escalated that day, and record who received the update.
Results
Dolores was reviewed at the bedside within the hour and her plan changed to closer monitoring, with a senior check that evening. The team agreed the first call was the weak point. After the unit adopted the one-line trend statement, completeness in the audit rose from 58 percent to 91 percent of sampled calls over the next quarter. Hannah's notes became the model for the handover template. Governance also noted that the threshold was clear on paper but applied unevenly across shifts, and that is now a standing agenda item.
Questions for discussion
- Which details in Hannah's observations would have been easiest to dismiss at the end of a busy shift, and how should a team train for that?
- How should the unit weigh a patient's own minimization of symptoms against a rising score when the two point in different directions?
- What would a fair escalation threshold look like if it had to work equally well on day, evening and night shifts?
Case Study 2
A verbal handover that never reached the bedside
Port Haddon Medical Center, a 180-bed community hospital with a 28-bed cardiac telemetry ward
The situation
Walter, a 68-year-old, was on a telemetry ward for fluid build-up linked to his heart function. Two days into the admission, his care plan included a repeat assessment of fluid balance and weight at a set time that afternoon, and his daughter, Mei, had asked to be called before any change in his plan. Ravi, the day nurse, handed over at shift change. The handover was spoken from a printed sheet, and the oncoming nurse, Simone, took notes on the sheet. The assessment and the daughter's request did not appear on the sheet. Ravi had them in his head, but not in the spoken handover.
The challenge
The gap surfaced in the afternoon, when the oncoming nurse had no sign that the assessment existed. Simone assumed the task had been completed earlier, because the fluid balance chart looked current. The team had to reconstruct the afternoon, establish which safeguards had worked and which had not, and propose changes that could be measured without turning the review into a search for someone to blame.
Analysis
Walter's needs were specific and time sensitive. His fluid balance and weight were the evidence that the care plan was working or needed adjusting, and both depended on readings taken at set times and charted in a consistent way. The missing assessment mattered because the trend it would have added was the main thing the team was watching. A single weight reading tells little on its own; a sequence of them, read against intake and output, tells a story about whether a patient is moving in the right direction. A useful habit here is to ask what the evidence was for, then who was relying on it and when.
The handover standard on this ward asks for three things to be spoken aloud: current status, pending tasks with their owners and times, and any family or patient request that alters the plan. The pending task was present in the record but was not spoken, so the receiving nurse had no prompt to look for it. The request from Mei was similarly outside the spoken structure. The safeguards that did work were the read-back at the bedside and the charge nurse's check of the afternoon task list, which caught the gap before the assessment was overdue by more than a short window. The risk sat in that gap.
Actions taken
- Rebuild the handover sheet with fixed headings for pending tasks, family requests and time-critical checks, so that a missing item leaves a visible blank rather than silence.
- Require a read-back of every pending task at the bedside during the first month, with the receiving nurse signing the sheet against each item.
- Track how often a handover omits a pending task or family request, aiming to halve the baseline rate within two quarters and reporting it monthly.
- Pair each handover at the station with a five-minute walk-round for patients with a family request on file, so the conversation and the chart are checked together.
Results
Walter's afternoon assessment was completed on time once the charge nurse found the gap. His weight trend prompted a same-day review of his plan, and Mei was informed as she had asked. No lasting harm was recorded. Over the following two months the revised sheet was in use on every shift, and the audit found omitted items in 14 of 120 handovers, down from 37 of 120 before the change. The walk-round caught two further gaps in its first month, and both were corrected before the next shift. The ward now reports omissions at its monthly quality meeting alongside falls and call-bell response times.
Questions for discussion
- Which items on a handover sheet tend to be left out because they feel like background rather than tasks, and how would you test for that?
- When a family request is recorded in the chart but not spoken, who in the team carries responsibility for it at the moment of handover?
- How much should a team rely on a read-back when the receiving nurse is also managing a busy bedside?
Case Study 3
Deciding who waits when the clinic runs short
Marrowgate Heart Diagnostics Center, an outpatient imaging and monitoring service with four examination rooms
The situation
Marrowgate runs four examination rooms with a staff of six technologists and two nurse navigators. Over the past several months, referrals rose by about a third, and the waiting list reached 1,140 people, with the median wait stretching past what the service had set as its target. Routine follow-up scans and new referrals with possible symptoms were sitting in the same queue, ordered only by arrival. Two technologists were off on extended leave, and one room had been out of service for repairs for most of the month. Dariusz, the service manager, asked for options that would not simply push the problem onto the patients who could least afford to wait.
The challenge
The options on the table were tighter triage, fixed scheduling blocks for new referrals, and reallocating routine follow-up to a longer interval. Each one protected something and put something else at risk. Two of the three options were already being discussed informally at the front desk. The team needed a method for comparing them that kept the people with new symptoms from being pushed down the list by people who were simply overdue.
Analysis
The clinical question behind each referral is different, and a queue sorted by arrival hides that. A new referral with possible symptoms of heart strain or irregular rhythm carries information about risk that a routine follow-up does not. The evidence for ordering the list was uneven. Referral letters varied in detail, some omitted symptoms, and the service had no shared score for urgency. Routine follow-up patients were not free of risk, since a planned scan can show a change that matters. Triage based only on the letter would miss some of that, so the decision needed a clinician review of each new referral before it was placed in the queue.
Coordination ran through two people who did not share a schedule. The navigators knew which patients had called twice, but the technologists controlled the room calendar, and the referral review happened on Thursdays only. Local policy for the service set a target that urgent referrals be seen within a fixed number of working days, and it also required that any routine follow-up be rebooked rather than dropped. Those two requirements pulled against each other when capacity fell. A reasonable fix would be to give the navigators a standing short block of the schedule for urgent cases and to make the rebooking step visible on the same board the technologists use.
- Triage by risk Clinician reviews each new referral for symptoms before it enters the queue.
- Protect urgent slots Hold a fixed share of technologist time for urgent referrals each week.
- Rebook follow-ups Routine patients keep a confirmed slot rather than disappearing from the list.
- Audit missed cases Review each month which urgent patients waited longer than the standard allows.
Actions taken
- Introduce a three-point urgency field on every referral, completed by the navigator at intake and checked by a clinician for any new symptom, so the queue reflects risk rather than arrival order.
- Reserve a fixed share of technologist time each week for urgent referrals, starting at one session in five, and review that share at the monthly capacity meeting against actual demand.
- Move routine follow-up patients into a confirmed rebooking window with a letter explaining the new slot, so that no patient falls off the list when a room is unavailable.
- Audit every urgent referral that waited beyond the standard each month, with a short written reason for each, and send the findings to the clinical governance group.
Results
Marrowgate chose a mixed approach. New referrals with symptoms moved into a protected daily block, and the navigators began calling routine patients to offer a confirmed slot within a fixed window rather than leaving them on an open list. A locum technologist covered the room that had been out of service. Waiting times for urgent referrals fell back inside the service target within two months, and the routine list shortened more slowly. Two patients overlooked in the first month were found in the monthly audit and seen the following week, which changed how the list is reviewed.
Questions for discussion
- Which of the three options would you test first at Marrowgate, and what early signal would tell you it was costing the wrong patients?
- How much weight should a service give to arrival order when urgency is not recorded consistently in referral letters?
- When a routine patient is rebooked into a later window, what should the service tell that patient, and who should be responsible for saying it?
Case Study 4
Why outcomes differed across three county clinics
Lindmere Community Cardiology Service, a group of six cardiologists serving three county clinics
The situation
Lindmere reviewed anonymized records from 2,300 follow-up visits over a full year of activity across its three clinics. Leadership had noticed that outcome measures for patients with heart failure looked strong overall but varied widely between sites. One clinic reported timely repeat assessments after an abnormal result in most cases, another in fewer than half. Documentation of shared plans, medication reconciliation and referral letters also differed. Julian, the clinical lead, wanted to know whether the variation reflected who each clinic saw or how each clinic worked, before anyone changed a staffing pattern or a template.
The challenge
The indicators were anonymized and aggregated, which made it impossible to see individual cases and easy to overread small differences. Each clinic had a different mix of patients by age and by the number of conditions they carried. The team had to separate process causes that the service could change from case mix that it could only adjust for, and then design a cycle of changes that could be monitored without creating new work for the clinicians who would be measured.
Analysis
Behind every indicator is a patient who was supposed to be contacted, reviewed or given a shared plan, and the gap between clinics was a gap in those contacts. The clinical evidence the service relied on was sound: outcome measures were recorded in a standard way. The weakness was in the process data. A repeat assessment marked as not done might have been completed on paper, or might have been missed. Without a way to tell the difference, the team could not say which patients had their needs met. A manual chart sample suggested the true rate sat between the two reported figures.
Coordination across three sites depended on a shared template and a rotating monthly call. The template asked for the review date after an abnormal result, but the field was optional and two clinics used a free-text note instead. Local protocol required a documented shared plan at every review for patients with a new diagnosis or a change in their care plan, and the cardiologists understood that requirement. What varied was who entered the plan, and whether the nurse who saw the patient between visits could see it. A named coordinator at each clinic, with template access and a short checklist, would address most of the variation.
Actions taken
- Create a single review-tracking field in the shared template, marked as required, and retire the free-text note so that every abnormal result has a recorded follow-up plan or a documented reason.
- Pilot a named coordinator at the two lower-performing clinics for one quarter, with a weekly check of open follow-ups against the template and a short note to the lead cardiologist.
- Agree on five measures before the pilot starts, including timely review after abnormal results, completion of shared plans and the rate of missing template fields, and keep the definitions fixed.
- Report results at each monthly call with run charts rather than league tables, and review any clinic whose measure moves outside its usual range for two consecutive months.
Results
The first run chart showed that most of the gap at the two lower clinics came from missing follow-up plans rather than from slower clinical review. Once the coordinator added a plan or a documented reason to each open case, the proportion of abnormal results with a recorded follow-up rose steadily over the pilot quarter, and the difference between sites narrowed. Outcome measures moved only slightly, as the team had expected from the case mix. The service kept the template change and extended the coordinator role to the third clinic at the next planning round.
Questions for discussion
- If the two lower clinics had turned out to serve older, more complex patients, how would the team's reading of the matrix change?
- What is the risk of treating a free-text note as an acceptable substitute for a structured field, and who bears that risk?
- How should a service decide how long a pilot needs to run before a change is judged to have worked?
Case Study 5
A family request that conflicts with a patient's stated wishes
Ashbourne Community Hospital, a 150-bed hospital with an outpatient heart failure clinic and a palliative liaison service
The situation
Amara, a 79-year-old former nurse, has advanced heart failure and attends the outpatient clinic every few weeks. Over the past several months she has told Oluwaseun, the consultant cardiologist, that she wants to avoid hospital stays where possible and be involved in every decision about her care. She has capacity, and her wishes are recorded in her own words at three reviews. Her son, Felix, who helps with appointments and medication collection, has asked the team to share all test results with him and to pursue any option that might extend her life. Amara has said she is content for Felix to attend appointments but has asked that results be shared with her first.
The challenge
The team had to decide what Amara's own preferences required of them, what Felix could properly be told, and when the disagreement needed to go beyond the clinic. Felix was not wrong to be worried, and his request was not unreasonable on its face. The difficulty was that the sharing of results was tied to a consent decision Amara had already made, and a family member's expectations were pulling against it.
Analysis
Amara's needs are both clinical and personal, and the two are hard to separate in a condition like hers. The evidence about her prognosis is uncertain, and the clinic's notes were careful to describe the options as ranges of outcomes rather than predictions. That uncertainty is part of why her own stated view carries weight. A capacity assessment done at one visit is evidence about that visit, and a team that treats it as a permanent answer will struggle when circumstances change. The team's duty was to keep her informed in a way she could take in, and to record what she had decided, not to let the loudest voice in the room set the agenda.
Communication choices carried most of the weight here. Oluwaseun could agree to Felix's attendance at appointments while keeping results with Amara, and that distinction needed to be stated plainly to Amara and Felix, not left as a quiet compromise. The local confidentiality policy allows information to be shared with a family member when the patient agrees, and it asks that the agreement be recorded. Beatriz, the discharge coordinator, suggested a short written statement of who could receive what, signed by Amara. Because the disagreement concerned the plan itself, the policy directed a joint discussion with the ethics service and the palliative liaison nurse before any change.
Actions taken
- Hold a joint meeting with Amara, Felix, Oluwaseun and Beatriz, and begin by asking Amara how she wants information shared before discussing any clinical options.
- Write a short statement of what Felix may receive, what stays with Amara, and when the arrangement will be revisited, and ask Amara to sign it so that the agreement is on file.
- Convene the joint discussion with the ethics service and the palliative liaison nurse before any change to the plan, and record the reasons for the decision in Amara's own words where possible.
- Set a review point four weeks after the meeting, or sooner if her condition changes, and document who will be present so that the next conversation does not start from the beginning.
Results
The joint meeting took place in the following week. Amara confirmed her wish to keep results with her first and agreed that Felix could attend appointments and ask questions on her behalf, with her permission recorded each time. Felix said he felt more included, though he still disagreed about some options, and that disagreement was written into the notes as his view. The ethics service confirmed the team's approach was consistent with local policy. The review point was kept, and the arrangement has held without a further escalation.
Questions for discussion
- How should a team decide whether a family member's disagreement is a concern about information or a challenge to the plan itself, and what changes once that is clear?
- When a patient's recorded wishes are several months old, what should prompt the team to revisit them rather than simply rely on the record?
- What would you need to see in the notes to be confident that a patient's view was heard rather than only written down?
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.