Cardiology and Cardiovascular Care Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases draw on several cardiac services of the kind found in mid-sized regions, rebuilt from working experience with details changed. Each one turns on a point where good care depends less on a single clinician's knowledge than on how the team passes information along, applies local protocols, and notices when a picture has changed. The early cases concern recognition and handover, the middle pair capacity and measurement, and the last the conversations that shape consent. Each analysis examines patient needs, clinical evidence, team coordination, and the protocols in force.
Case Study 1
A chest pressure pattern that kept changing overnight
Westbrook Valley Medical Center, a 310-bed community hospital with a cardiac observation unit.
The situation
Ray Okafor, a man in his late fifties, came to the emergency department at Westbrook Valley with pressure in the chest that had come and gone for two days. It was worse on stairs and eased when he sat down. The first electrocardiogram was read as nonspecific, and the first blood marker result, drawn early, was within range. He was moved to the cardiac observation unit with a plan to repeat both tests. Joanna, the night charge nurse, noticed that his pain had returned in the early hours and that his blood pressure had shifted. Samuel, the overnight physician, was covering three bays. The chart showed the repeat tracing had been ordered but not yet performed.
The challenge
The question was whether a changing story, set against a reassuring first result, justified moving Ray up the escalation pathway before the repeat tests came back. Samuel had a reasonable read that the pattern could still be stable, and the protocol asked for serial testing before a cardiology call. Joanna had a different concern. She could not tell from the chart who owned the repeat test, whether the on-call cardiologist knew about the change, or what the criteria required once symptoms recurred. Each option cost time or trust.
Analysis
Ray needed three things that were simple to name and hard to deliver at once: a clear owner for the next test, a time frame matched to how his symptoms were behaving, and someone ready to act. The evidence was thin. One nonspecific tracing and one early marker result cannot exclude a developing problem, and the record offered no comparison with an earlier tracing. Recurrent pain that changes in pattern is the kind of signal that local protocols tend to treat as a reason to re-evaluate rather than to wait. Westbrook's pathway named recurrence of symptoms as a trigger for urgent cardiology review, and Joanna's report met that trigger on its face.
Teams grounded in Cardiology and Cardiovascular Care usually start by separating what is known from what is assumed. Here the assumption was that the repeat test was already in progress, when no one had confirmed it was queued. The fix is partly structural: a named owner for each pending investigation, a written escalation trigger that a nurse can invoke without waiting for a physician to agree the change is meaningful, and a closed loop back to the first clinician. Joanna's call was correct under the protocol. The gap was that it went to a general line rather than the on-call cardiology contact, and the physician was not told the symptom pattern had changed.
Actions taken
- Create a single pending investigations list at each handover that names an owner, an expected time, and the result that will trigger review.
- Write a nurse-initiated escalation step into the observation protocol so that a recurrence of symptoms prompts a direct call to the on-call cardiology contact.
- Require documentation of any change in symptom pattern in the physician's note, with the time it was reported and the person informed.
- Audit twenty observation stays per quarter for tests ordered but not completed within the stated window, and report the count to the department's safety meeting.
Results
Ray moved to the step-down unit once the repeat tracing and a second cardiology review confirmed the change. The department then audited twenty-two observation stays over the following quarter and found four with a pending test and no named owner. The pending list was adopted in the third week after the review, and the escalation step went through the protocol committee by the end of the quarter. Joanna called the change a relief more than a victory, since the call she had wanted to make at three in the morning was now one she was expected to make.
Questions for discussion
- Which parts of the first assessment could have been reread against the earlier tracing, and who would have needed to ask for it?
- How should a nurse weigh a change in symptoms against a reassuring result when the protocol gives no explicit trigger?
- What would a pending investigations list need to show for a covering physician to trust it at three in the morning?
Case Study 2
A handover gap for a patient awaiting a scheduled test
Ridgeline Heart and Vascular Institute, an inpatient and outpatient cardiology unit with a 28-bed telemetry ward.
The situation
Dolores Haines, a woman in her seventies with heart failure, moved from the telemetry ward to a general medical bed ahead of an early imaging test. Her day nurse, Tomas, wrote a handover note listing her overnight plan and the test time. The note did not carry the trend. Her weight had risen steadily over two days, and that trend sat only in the flowsheet. The verbal handover at the end of the shift was cut short when a bed alarm sounded, and the night nurse, Priti, took the bed without the trend. By the early hours Dolores was more breathless at rest, and the change was not picked up until the test team began preparing her.
The challenge
The safety question was not whether one nurse made an error. It was whether the handover structure made it likely that a trend would be dropped. The day team believed the trend had been passed on verbally. The night team believed the written note was the handover. Neither belief was checked. The safeguards on paper were a template, a verbal exchange, a bedside check, an escalation pathway, and a patient conversation. On this night, each one was weaker than it looked.
Analysis
Dolores needed continuity more than anything else. Her trend over two days was the central clinical evidence: a steady weight gain and a change in her breathing at rest, arriving at a planned test that would be harder to rebook if her condition moved. Heart failure care depends on noticing small changes over time, and a single weight reading means little without the one before it. The flowsheet held both readings, so the evidence existed in the chart and was absent from the conversation. The handover template displayed only the most recent value by default, which made the trend invisible to anyone who did not open the flowsheet.
Handover works best when it is treated as a designed step rather than a courtesy. Ridgeline's protocol required a structured exchange using the standard tool, a named field for trends, a read-back of the top three concerns, and a bedside check for any patient with a pending investigation. The verbal part happened, but it was cut short and no read-back was recorded. The escalation pathway for a weight change was clear on paper, yet it depended on a nurse recognizing the trend and deciding it qualified. Both nurses acted in good faith. The structure left the critical item to memory, and memory was the first thing the interruption removed.
Actions taken
- Make the structured handover tool display the last three values of any trended measure, so that change is visible at a glance.
- Require a read-back of the top three concerns for every handover involving a patient with a pending test, and record it in the chart.
- Add a bedside check at the start of each night shift for patients with a test before eight in the morning, confirming the trend and the plan together.
- Track handover omissions through a monthly audit of ten randomly selected transfers, reporting the count and the item missed to the nursing quality committee.
Results
The unit changed its template within the first month and added the read-back field to the handover audit. In the quarter after that, four of ten sampled transfers omitted a trend item, down from seven of ten in the baseline sample. Read-backs were recorded in nine of ten handovers involving pending tests. Dolores's test was rescheduled to the afternoon of the same day, and she was reviewed at the bedside before going down. The nursing lead, Marisol, said the most useful change was seeing the last three values on the screen before anyone asked for them.
Questions for discussion
- Which safeguard in this case depended most on memory, and what would it take to move that step into the record?
- If the verbal exchange had been complete, would the template still have hidden the trend, and what would you change first?
- What should a bedside check at the start of a night shift confirm that the written handover cannot?
Case Study 3
Scheduling options when echocardiography capacity falls short
Lakeshore Cardiac Diagnostics, an outpatient imaging and clinic service serving three counties.
The situation
The imaging lab lost one of its two sonographers to extended leave at the start of the quarter. The remaining sonographer, Kwame, covered the outpatient list and urgent inpatient requests. The routine wait for an outpatient echocardiogram rose from about three weeks to over nine. The active waiting list held 1,200 patients, of whom 180 were marked higher risk on the referral letter. Three options were on the table: keep first-come scheduling, triage by referral urgency, or send some studies to a partner imaging center across town under an agreed turnaround. Each option changed who waited, how long, and who carried the decision.
The challenge
Ada, the clinic manager, had to protect the patients most at risk from delay without creating a system that shortchanged routine patients. Ivan, the consultant cardiologist and clinical lead, argued that referral letters were unreliable for triage because many referrers used different thresholds. Ada worried that a triage list would feel arbitrary to patients and to staff. The partner center had capacity, but its report format differed, so any study sent out would need a check on return before it could enter the record.
Analysis
Patient needs in a queue are not uniform. A person with a recent change in breathlessness or a known valve concern is waiting for information that may change the plan, while a person due a routine review is waiting for reassurance. The evidence was imperfect. Referral letters stated the reason for referral but rarely the symptom pattern, and nobody had recorded how often a routine study changed management. A look back at last quarter's referrals showed the most common reason for escalation was new symptoms recorded after the letter was written. That pointed to asking the triage questions at booking, using a short set, rather than trusting the letter alone.
Teams that handle capacity well usually ask who a decision protects before they ask which option is fairest. Lakeshore's imaging access policy said urgent studies took precedence, but it did not define urgent and said nothing about partner centers. Each option had a coordination cost. First-come scheduling kept the process simple but let higher-risk patients wait behind routine ones. Triage by letter was quick but inherited each referrer's habits. Outsourcing added a handoff with its own report format and a review on return. The working answer combined a short booking screen, a clinical review of flagged cases within two working days, and a fixed monthly allocation to the partner center.
- 1Referral receivedLetter reviewed for reason for referral and any stated urgency.
- 2Booking screenFive questions asked on the phone about symptom change and past studies.
- 3Clinical lead reviewFlagged cases reviewed within two working days by the consultant.
- 4Slot or partner routeLocal list if capacity allows, otherwise a fixed partner allocation.
- 5Result filedReport entered in the record and sent to the referring clinician.
Actions taken
- Add a five-question booking screen covering recent symptom change, prior study results, and the reason for referral, asked at the point of booking.
- Set a written definition of urgent imaging that the clinical lead and referring teams agree on, reviewed every six months.
- Send a fixed weekly allocation of routine studies to the partner center using one shared report template, with results back in the clinic within three working days.
- Report waiting time by priority band each month, and review any high-priority patient who waits beyond the agreed interval at the governance meeting.
Results
Within the first month the screen was live, about a third of the active list was reclassified. Seventeen patients moved up to urgent review, and two of them had new findings that changed their plan. Routine waits fell from nine weeks to just under six, and the high-priority wait stayed inside the agreed interval for most months. Kwame said the list finally felt like a plan rather than a queue, though about one in ten partner reports still needed a second check before filing.
Questions for discussion
- Which of the three original options would have served the high-risk patients best, and which would have served the routine list best?
- What would a clinical lead need to see before accepting a partner report without a second check?
- How should a service decide how long routine patients can wait once the urgent list is protected?
Case Study 4
Uneven outcomes across three heart failure clinics
Saltmarsh Regional Health Network, three cardiology clinics and one hospital-based heart failure service.
The situation
The network's heart failure service reviewed readmissions within thirty days of discharge across roughly 2,300 index admissions in the previous twelve months. Rates ranged from 14 percent at the largest clinic to 26 percent at the newest one. The indicators were anonymized before they reached the quality lead, Priya, who reviews them monthly. She noticed that the newest clinic also had the lowest documented rate of early follow-up contact and the highest share of records where the discharge summary was missing at the time of review. The clinical lead at that clinic, Gareth, believed his patients were simply sicker on arrival. Leadership wanted a plan within the quarter.
The challenge
The data supported several explanations. Case mix might differ, since the newest clinic took more referrals from a rural catchment with longer travel times. Documentation might differ, which would make outcomes look worse without changing care. Or the discharge pathway might differ in ways that mattered, such as the timing of the first contact. Priya needed to separate these before proposing changes that would reach every clinic. Gareth needed a fair hearing, and the other clinics needed to know the review was not a judgment of their practice.
Analysis
The patients in this service need a bridge between hospital and home: a clear medication plan, a contact who knows them, and an early check. Readmission is a blunt measure of whether that bridge held, but it is the outcome the network had agreed to track. The clinical evidence on transition care points in a fairly consistent direction, so the team looked at process as well as outcome. Without adjusting for case mix, a gap of that size could reflect the population each clinic serves. Two process measures were added alongside the outcome: the share of patients contacted within the first few days, and the share with a complete discharge summary on file.
Process questions are often more useful than outcome questions. Saltmarsh's transition protocol assigned the first contact to the discharging ward, but the newest clinic received patients from that ward in batches, and its nurses were not on the notification list. The discharge summary was dictated but often arrived after the first clinic visit, so there was no written plan at the visit. Priya proposed a monthly audit of forty records per clinic, a shared notification list, and a summary-before-visit rule. Gareth raised a fair point: the rule would not help if the summary itself was late. The disagreement was useful because it showed the process had three owners and no single point of accountability.
- Week oneBaseline indicators and records reviewed with the three clinic leads.
- Week threeNotification list extended to clinic nurses and first contact tracked.
- Week sixSummary timing added to the monthly audit for the newest clinic.
- End of month twoCase mix comparison completed and shared at the governance meeting.
- End of quarterPilot reviewed and extension to other sites decided by the committee.
Actions taken
- Add the clinic nurses to the discharge notification list so that every admission generates a contact task on the day of discharge.
- Set a target that discharge summaries reach the clinician before the first clinic visit, and report the share meeting it each month by clinic.
- Run a case mix comparison using age band, admission route, and travel distance, so that outcome differences are read against each clinic's population.
- Pilot the changes at the newest clinic for one quarter with forty records reviewed monthly, then decide whether to extend them to the other two sites.
Results
After the first quarter, early contact at the newest clinic rose from about half of patients to most of them, and summaries available before the first visit improved by roughly a fifth. The readmission gap narrowed but did not close. After adjustment for case mix, the newest clinic still sat above the network median, so the team began to ask whether its catchment needed a different follow-up pattern rather than the same one. Gareth and Priya presented both findings to the quality committee together, which was the first time the indicators were discussed as a shared problem rather than a ranking.
Questions for discussion
- Which of the three explanations for the gap could the existing data rule out, and which would need new information?
- What would make a summary-before-visit target fair to a clinic that does not control when summaries are dictated?
- How should a network decide whether a remaining gap after adjustment reflects a process problem or a real population need?
Case Study 5
A family request that conflicts with a patient's stated wishes
Tidewater Heart Center, a specialist cardiac unit with a structured advance care planning program.
The situation
Edwin Park, a retired engineer in his seventies with advanced heart disease, had told his cardiology team that he wanted to take part in decisions but did not want detailed outcome figures. He had completed a short written statement naming his daughter, Lucia, as the person to receive information. During an admission he became confused for a period and could not join a conversation about a new plan. His son, Ben, arrived from overseas and asked the team to explain every option in full, including the ones his father had set aside. Lucia supported part of the request but said she was unsure what her father would want now. The ward had the statement but no capacity assessment for that period.
The challenge
The team had three duties pulling in different directions: respecting Edwin's stated preference for limited detail, sharing information with the family member he had named, and involving him as far as he could take part. They also had to decide whether the confusion was temporary and whether the decision could wait. Ben's request was sincere, but it was not the same as a request from the patient. The question was less who had the most authority in the room than which process would hold up if the decision were reviewed later.
Analysis
Edwin's needs were both clinical and personal. He needed a plan that matched his condition and a way to take part without being overwhelmed. The clinical evidence was clear that his options were limited, but how it should be shared depended on what he had asked for. A duty to disclose material information sits alongside the patient's right to decide how much he wants to hear, and a relative's request does not discharge it. His confusion raised two separate questions: whether he could decide at that moment, and whether his earlier wishes still applied. Capacity is decision specific and time specific, so the team had to assess it for this decision rather than assume it.
Tidewater's policy let a named representative receive information when the patient lacked capacity, but it did not say what to do when that representative disagreed with a written earlier preference. Three questions get mixed together in cases like this: what the patient can decide now, what he decided earlier, and whom he asked to speak for him. The team agreed the written statement should shape what was offered, Lucia would receive what Edwin had authorized, and Ben's questions would be recorded, answered, and checked against his documented wishes. They escalated to ethics consultation and palliative care the same day for a second structured review.
Actions taken
- Complete a capacity assessment for the specific decision, record the time and the person who assessed it, and repeat it when the patient's condition changes.
- Share information with family only within the scope the patient authorized, and document that scope so every clinician uses the same boundary.
- Hold a structured family meeting with a named facilitator, a written summary of what was said, and a follow-up plan agreed before anyone leaves the room.
- Refer unresolved conflicts between a written preference and a family request to ethics consultation within one working day, and record the advice in the chart.
Results
The decision waited two days until Edwin regained enough clarity to take part in a short conversation. He asked that Lucia hear the options in plain language, that he be told the main risk, and that detailed figures be left out unless he asked for them. Ben accepted a second meeting, where his questions were answered and written down. The ethics service supported the approach and asked for the policy to address this kind of conflict. The revision reached the governance committee by the end of the quarter. Lucia said the most useful part was knowing what her father had asked for.
Questions for discussion
- When a written preference and a family request point in different directions, which information should the team share first, and why?
- What evidence would convince you that a period of confusion was temporary rather than a change in how the patient decides?
- How could a family meeting give a grieving relative a real voice without letting one person set the agenda?
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.