Transplant and Surgical Oncology Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
These five cases come from a transplant and oncology surgery service, where one patient may move through clinic, imaging, the operating room and a waiting list within weeks. Each is written by a practitioner who sat close enough to the decisions to see where the system held and where it strained. The situations are fictional, but the pressures are familiar: late-recognized symptoms, handovers that drop a line of information, demand beyond capacity, inconsistent outcome data, and consent conversations that need more time than the schedule allows. Read each case for patient need first, then evidence, then team and protocol.
Case Study 1
Escalation delayed by unclear ownership of a symptom call
Wrenfield Regional Hospital, a 480-bed tertiary hospital with a hepatobiliary oncology surgery service and a liver transplant program.
The situation
A patient in his early sixties was under surveillance at Wrenfield Regional Hospital after a liver lesion was found during routine imaging. He was on the transplant assessment pathway and his scans were reviewed every few months by the hepatobiliary team. Over a span of three weeks he reported new abdominal fullness, a loss of appetite, and a temperature that came and went. The nurse navigator logged the calls, but the messages were filed as stable because his routine blood tests had not changed. A repeat scan was booked for the following month. The on-call hepatology fellow saw the notes at the end of a long shift and did not have the full imaging history in front of them.
The challenge
The team had to decide whether a set of soft, cumulative changes justified moving him up the escalation ladder before the scheduled scan, and who would own that decision. Local protocol required same-day review for any new fever in a patient with a known lesion, but the nurse line had recorded the fever as intermittent and under a threshold on the last call. Nobody was sure whether the transplant coordinator or the hepatology team held responsibility for the call-back.
Analysis
The patient's needs were easy to state and hard to weigh. He needed a reliable view of whether his liver lesion was changing, and he needed someone to take his symptoms seriously before the next scheduled scan. The evidence was fragmented across three systems: nurse call notes, a surveillance imaging report, and a laboratory trend that looked flat only when read in isolation. Taken together the entries described a trajectory, not a set of separate events. Reading the record in sequence changed how the same facts looked. The team needed to accept that a stable blood result does not cancel a symptom history.
Teams grounded in Transplant and Surgical Oncology usually start by mapping who owns each escalation decision, because the failure here was less about clinical judgment than about unclear ownership. The local protocol set a same-day review threshold for new fever, but it did not say whether a nurse navigator could trigger that review. The transplant coordinator assumed hepatology had the call, and hepatology assumed the navigator had already referred. Under the protocol, a documented handover naming one accountable clinician would have closed that gap. The review that followed recommended one escalation owner per pathway and a same-day clinician review for any new fever, whatever the latest laboratory value showed.
Actions taken
- Name one accountable escalation clinician for every surveillance pathway, and write that name into the patient's shared record so that any caller can see who must be contacted.
- Add a fixed set of symptom prompts to the nurse navigator's call template, including new fever, early satiety, and weight change, each with a required same-day clinician review trigger.
- Present each surveillance patient's imaging history and recent symptom log side by side at the weekly hepatology huddle, so that on-call clinicians review the full trajectory rather than the latest message alone.
- Audit every symptom call on these pathways for the next two full months, recording time to clinician review, and report the results at the monthly governance meeting.
Results
Over the following quarter the navigator template was revised and the single-owner rule covered three surveillance pathways. In the audit period, median time from a flagged symptom call to clinician review fell from about two working days to under six hours, and no symptom call sat in the queue without a named owner. The original patient was brought in for an earlier scan, and the imaging showed a change the laboratory trend had not revealed. The team did not treat the outcome as proof that the new process was sufficient, and they continued to review each call weekly.
Questions for discussion
- Which single role in your service would be best placed to own escalation for a surveillance patient, and what would that person need in front of them to decide?
- How would you weigh a set of small symptom changes against a stable laboratory trend when the two point in different directions?
- What would your team need to change in the handover template so that an overnight clinician sees the imaging history without searching for it?
Case Study 2
A handover field left empty before a night shift
Ashgrove Harrow Medical Center, a 620-bed academic hospital with combined abdominal oncology surgery and kidney transplant services.
The situation
A woman in her fifties was three days out from a planned abdominal oncology operation at Ashgrove Harrow Medical Center when her care moved from the day team to the night team. The day team used a structured handover tool with fields for active problems, pending results, and escalation thresholds. On this occasion, the escalation section was completed in a free-text box that the electronic system did not carry forward to the night view. The night clinician therefore received a summary that looked complete but lacked the call-out criteria that day staff had agreed on at the bedside. Nobody noticed until the overnight nurse asked why a specific observation had not triggered a call.
The challenge
The gap was small and easy to miss, which is what made it dangerous. The night team had no reason to doubt the summary, and the nurse had no direct access to the day team's notes. The unit needed to decide how to close the gap without adding so much documentation that handovers took longer and became less accurate. Two options were on the table: tighten the template, or move the escalation criteria to a shared bedside board.
Analysis
The patient needed her early warning signs read against thresholds that had been agreed for her specific operation and recovery, not against generic ward defaults. The evidence in this case was mostly observational: a trend in recorded vital signs over the first night, a small rise in a laboratory marker that the day team had flagged as worth repeating, and a nursing note describing reduced mobility. Each item was documented somewhere, but only the observations had clear call criteria attached to them. Safety depends on which facts travel with the patient. Criteria left in free text stay behind, and the data arrive without their meaning.
The ward's handover protocol required structured fields for escalation criteria and an explicit read-back between clinicians at the bedside. Read-back was done for medication and fluid orders but had been skipped for observations, which the team had treated as routine. Under the protocol, the day clinician should have verbally confirmed the call-out thresholds with the night nurse, and the nurse should have repeated them back. Instead the handover was completed in the electronic tool alone, which allowed the form to be marked finished with an empty escalation field. The team coordination failed quietly, because each person assumed another had confirmed the criteria.
- 1Day team completes formEscalation thresholds entered as free text, not structured fields.
- 2Electronic summary generatedFree-text criteria absent from the night view, summary looks complete.
- 3Verbal read-back skippedObservations treated as routine, so thresholds were not repeated aloud.
- 4Night nurse notices gapDiscovered only when an expected observation failed to trigger a call.
Actions taken
- Add a required read-back step for escalation thresholds to the electronic handover form, so that the form cannot be closed while the escalation field is empty or unconfirmed.
- Post the agreed call-out criteria for each patient on a bedside board visible to nurses and clinicians, and check the board together at the start of every shift change.
- Run a five-minute structured handover huddle at the bedside for patients with a surgical oncology operation in the previous five days, led by the outgoing nurse and receiving clinician.
- Track the proportion of handovers with a completed escalation field and a confirmed read-back, reporting the rate monthly with a target agreed at the start of the review period.
Results
Within the first full month, the electronic form blocked closure on eleven handovers where the escalation field was empty, all of which were corrected before the shift ended. The bedside board and huddle were adopted on the surgical oncology ward first and then extended to the kidney transplant unit. The proportion of handovers with a confirmed escalation read-back rose from roughly six in ten to above nine in ten over the review period. Night staff reported fewer repeat questions about call criteria, though the huddle added a few minutes at each change.
Questions for discussion
- Where in your own handover process do escalation criteria live, and who is responsible for confirming them out loud?
- How would you balance the time a structured huddle takes against the risk of a missed threshold on a busy shift?
- Which field in a shared record would you trust least to carry a patient's call-out criteria across a shift change, and why?
Case Study 3
One operating room down and a growing cancer list
Pell Harbor Cancer and Transplant Institute, a 210-bed specialty center with two shared operating rooms and a dedicated transplant assessment clinic.
The situation
Pell Harbor's two shared operating rooms had been booked solid for most of the quarter, and the surgical oncology waiting list grew faster than the team could clear it. In the third week, one room was taken out of service for a planned equipment repair that ran longer than estimated, and two experienced scrub nurses were off with illness at the same time. The list held nineteen cases with cancer diagnoses and several more transplant assessments that could not be delayed without risk. Patients who were booked for the following week began asking whether their dates would hold. The service coordinator had to decide which cases moved, which stayed, and which needed a conversation before anything changed.
The challenge
Three options were available, and each protected something different. Moving the lowest-acuity cases to later dates protected the urgent cancer work but risked the patients who were waiting longest. Sending cases to an outside center protected schedules but added transfer time and a second set of handover risks. Keeping the full list and running extended sessions protected access but tired a team that was already short. The coordinator needed a decision by the end of the day.
Analysis
Clinical urgency was the first sorting tool, and it was more useful than waiting time alone. Cancer cases with a documented risk of progression while waiting needed a fixed reassessment point, and the service's own tumor board notes gave clear grounds for ordering several cases ahead of others. Transplant assessments were harder to rank. Delay did not always cause immediate harm, but it extended time on a list where a patient's condition could change without warning. The evidence available to the coordinator was incomplete. Some referrals lacked recent imaging, and a few had been listed under provisional diagnoses that the tumor board had not yet confirmed.
The unit's capacity protocol set an order of priority: urgent oncologic cases first, then time-sensitive transplant work, then routine elective operations. It also required that any change to a booked date be discussed with the treating team and documented with a reason. Those rules held up in principle, but they did not say how to weigh two urgent cases against each other when a single room was available. The coordinator, the anesthesia lead, and the nurse manager made the call together in a short meeting. They kept the two most time-sensitive oncology cases in the remaining room and moved three elective cases with clinician sign-off.
- Early in the quarterRooms booked near full, oncology waiting list growing steadily.
- Third weekRoom taken out of service and two scrub nurses off sick.
- Same morningCoordinator convened the three-person huddle and sorted urgent cases.
- By end of dayDecision recorded, with patients contacted and rationale documented.
- Following weekBuffer session absorbed the repair delay without moving oncology cases.
Actions taken
- Adopt a written tie-break rule for urgent oncology cases competing for one room, naming the clinical criteria and the clinician who signs off the final order.
- Hold a standing forty-minute capacity huddle each weekday morning with the coordinator, anesthesia lead, nurse manager, and one transplant coordinator, using a single shared list.
- Set a booking buffer of one elective session per week that stays unfilled, so that a room closure or staffing gap does not force a cascade of date changes.
- Require that every postponed case receive a documented clinician conversation, a new target date, and a named contact, and audit those records monthly for completeness.
Results
Over the next six weeks the buffer session absorbed two equipment delays without moving any oncology case, and the repaired room returned to service on schedule. Elective waiting time rose from about five weeks to about six, but no urgent cancer case waited longer than the target set at the outset. The audit found that all postponed patients had received a documented conversation, though three of those notes did not name a contact. The nurse manager reported that the morning huddle had reduced last-minute rota gaps, and the buffer was kept as a standing feature.
Questions for discussion
- What criteria would you use to rank two urgent cases competing for one room, and who should be allowed to overrule the ranking?
- How much unfilled capacity is reasonable to hold back in a service that is already short of staff?
- When a postponed patient receives a new date, what does a good conversation about that change include?
Case Study 4
Inconsistent readmission rates across five surgical sites
Northfield Cancer Surgery Network, five affiliated sites sharing one multidisciplinary tumor board and a central data office.
The situation
Northfield's data office compiled indicators for major abdominal cancer operations across its five sites. The figures were anonymized by site code, and they showed wide variation. Time from first referral to tumor board review ranged from under two weeks at one site to more than five weeks at another. Unplanned readmission within the first month after surgery was higher at two sites than at the rest, but the gap narrowed when case mix was considered. The steering group had seen similar patterns before and had attributed them to differences in patient populations. This time they asked for a process review before accepting that explanation.
The challenge
The indicators pointed in several directions at once. A low readmission rate at one site might reflect good discharge planning, or it might reflect a site that sent patients home earlier to a different service. The steering group needed to know whether the variation came from clinical decisions, from pathway timing, or from how the data were recorded. Without patient-level detail, each explanation sounded plausible, and the network had to pick one review method that would separate them.
Analysis
For patients, the measures that matter most are not abstract. A person waiting for a tumor board decision needs to know the plan and the timeline, and a person going home after major surgery needs the right support in the first weeks. The clinical evidence in the indicators was thin on the second point. Readmission counts did not record the reason for return, and several sites coded symptoms differently. A longer wait for review might reflect a careful assessment for a complex case, or it might reflect a missing scan. The data could not yet separate those stories, so the variation stayed unexplained.
The network's referral protocol set a target for time to tumor board review and required that every case presented before surgery carry a documented multidisciplinary decision. Both rules were in place at every site, but compliance was checked by a monthly spreadsheet that each site filled in differently. Site C often recorded the board date as the date the referral was logged, which shortened its apparent wait. Site E recorded the date of the final decision, which lengthened its wait. Neither site had acted in bad faith. The team coordinators had never been asked to use the same definition, and the protocol did not spell one out.
Actions taken
- Write a single shared definition for each indicator, covering the start and end points of every interval, and circulate it to all five site coordinators before the next data pull.
- Pull patient-level records for the two sites with the widest variation and abstract the readmission reason, referral date, and tumor board date for every case in the review window.
- Map the referral pathway at each site in a single session with coordinators, surgeons, and a data analyst, noting every point where a case waits for a person, a test, or a decision.
- Run a monitored cycle in which one change is tested at one site for a fixed period, with the same indicators reported monthly and a pre-agreed rule for stopping or extending it.
Results
After the definitions were agreed, the apparent gap in review timing narrowed by more than half, which showed that much of the variation had come from measurement. The patient-level review found that the readmission difference at one site was concentrated in a small group of cases with delayed discharge planning, not in the operations themselves. The network tested a single change there: a discharge planning check at the tumor board, reported monthly for a fixed period. Readmissions at the test site fell, and the steering group agreed to extend the trial while watching other sites.
Questions for discussion
- Which indicator in your own service would be most misleading if its start and end points were defined by different people?
- How would you decide when a local variation is worth a patient-level review and when it is better left alone?
- What would you need to see in a monthly report before agreeing to extend a trial that has only been running for a short time?
Case Study 5
A sister asks for a brother's cancer history
Juniper Valley Transplant Center, a single-site program handling roughly 2,300 patient contacts in a twelve-month period.
The situation
A man in his late forties had been referred to Juniper Valley Transplant Center for kidney transplant assessment. His history included a surgically treated skin cancer and a prior bowel cancer that had been followed up closely. The transplant selection committee wanted an oncology review before a decision on listing, and the surgical oncology team had records that the transplant team could read but had not previously used. His sister had volunteered to be a living donor and had asked the coordinator directly what was wrong with her brother's history. The patient had asked that his cancer details not be shared with her until he had decided how much to tell her himself.
The challenge
The transplant team needed the oncology history to judge eligibility, and the committee could not decide without it. The patient had a right to control who learned his diagnoses, and his sister had a reasonable interest in understanding a decision that would shape her own choice to donate. The coordinator was caught between a request for information and a request for silence, and the donor evaluation could not proceed until the team had settled both.
Analysis
The patient's needs were clear on paper and tangled in practice. He wanted a transplant assessment that took his history seriously, and he wanted to choose the pace and the audience for disclosure about his cancers. The clinical evidence was partly settled: prior treatment records, follow-up reports, and the oncology team's written view on the length of surveillance he had completed. Those documents answered some questions about eligibility, but they did not answer the question of what his sister should be told. That question belonged to the patient, and the team's job was to help him reach an answer he could live with, not to fill the gap himself.
The center's consent and confidentiality policy allowed a patient to set limits on family disclosure, and it required that any request from a potential donor be routed through the named coordinator and logged. The policy also said that a donor candidate's own assessment should be kept separate from a recipient's clinical details. Those rules gave the team a path, but they did not say what to do when the patient was unwilling to share and the donor was unwilling to wait. The coordinator had been trying to answer the sister's questions informally, which felt kind but created a record with no clear decision behind it.
- Clarify limits Confirm what the patient allows the donor to learn, in writing.
- Route requests Send every family or donor question through the named coordinator.
- Review the record Check the log before any reply, and note what has already been shared.
- Escalate or revisit Refer to ethics when agreement stalls, and revisit limits at each stage.
Actions taken
- Route every family or donor request for clinical information through the named transplant coordinator, and log each request with the patient's stated limits on disclosure before any reply is sent.
- Arrange a joint conversation with the patient, the coordinator, and a clinician from each relevant team, with the patient deciding in advance what the donor may hear and who should be present.
- Keep donor evaluation and recipient clinical records in separate sections of the file, and let the donor team see only the information the patient has agreed to share.
- Escalate to the center's ethics consultation service if the patient and donor cannot agree on disclosure within the review window, and record the reason for escalation in the case file.
Results
The joint conversation took place within the week, and the patient chose to share the broad outline of his history with his sister while keeping specific details private. The donor team accepted that limit and proceeded with its own evaluation, which the coordinator logged separately. The transplant committee reviewed the oncology evidence at its next meeting and agreed a listing decision with conditions for follow-up. Over the following quarter, the center reported no further informal disclosures from the coordinator team, and the consent log was used to answer two similar requests without escalation.
Questions for discussion
- When a patient limits what a family member may learn, what obligations does the team carry toward the donor, and how would you explain those limits to the donor?
- Who in your service should hold the record of what has been disclosed, and how would you keep that record accurate over a long assessment?
- At what point would you stop trying to reach agreement locally and move the case to an ethics consultation?
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.