Plastic, Reconstructive and Cosmetic Surgery Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
The five cases below come from fictional services that provide reconstructive, plastic and cosmetic surgical care. Each one follows a team through a decision made with incomplete information, limited capacity, or competing duties. None of them has a single correct answer. Instead, each case asks you to weigh patient needs, the clinical evidence available at the time, the way the team communicated and shared responsibility, and the local protocols that define what the team is allowed and expected to do. Work through the analysis before reading the actions, then compare your reasoning with the team's choice.
Case Study 1
A flap check that looked almost right
Corran Vale Hospital, a 480-bed general hospital with a 26-bed plastic surgery ward that takes reconstructive admissions from the regional trauma unit.
The situation
On the fourth evening after a free tissue transfer to repair a lower leg wound, the night nurse, Tomasz, noticed that the patient's foot felt cooler than the other side and that capillary refill had slowed across three checks. The patient described pain that seemed out of step with how the dressing looked. The day team had reviewed her that morning and recorded stable observations, but nobody had looked at the trend. Tomasz had worked on the ward for six years and was unsure whether he was seeing normal variation or the start of a problem. He recorded his concern, but two of the earlier entries that night had no time attached.
The challenge
The on-call resident was in the operating room with an emergency and could not attend for at least an hour. The ward protocol sets hourly observations for the first five days after this type of reconstruction and names a consultant escalation threshold, but that threshold is written around a sustained change, not a single reading. The patient was comfortable, asking when she could go home, and the team was reluctant to alarm her without good reason.
Analysis
The central question is whether the trend is real. A single cool reading or slow refill time means little alone, but several hours of movement in one direction carries real weight. Pain out of step with the visible appearance also deserves attention, since pain relief can blunt reports and a comfortable patient is not automatically a stable one. The evidence was incomplete as well. Two checks without timestamps meant the rate of change could not be established, and the decision depends on speed as much as direction.
Team coordination and local protocol decided what happened next. The protocol gave the nurse in charge authority to call the on-call plastic surgery team directly, without waiting for the resident to leave the operating room. The weak point was that Ruth, the nurse in charge, was covering two rooms and had not been told the night entries were incomplete. Teams grounded in Plastic, Reconstructive and Cosmetic Surgery usually start by asking who owns each decision and how quickly that person can be reached, then write the escalation trigger in plain terms so it does not depend on individual confidence. A structured handover turns a vague worry into a request a senior clinician can act on.
- Record trend Note times and direction across at least three consecutive readings.
- Call early Use the protocol route to reach the on-call team without waiting for handover.
- Review in person Surgical team examines the patient and sets a clear return threshold.
- Reset interval Agree the next observation schedule and document who will respond.
Actions taken
- Tomasz repeated the full observation set at the next hour, recorded a time against every entry, and phoned Ruth with the direction of change rather than a single reading.
- Ruth used the protocol's escalation route to call the on-call plastic surgery team and asked for a bedside review within the hour, not at the end of the operating list.
- The surgical team examined the patient in person, agreed a shorter observation interval, and wrote the criteria for returning to the operating room on the bedside plan.
- The ward changed its night handover sheet so that each observation carries a time, a trend arrow, and a named person to call when two readings move the same way.
Results
The surgical team reached the bedside within the hour and found a change in the limb that justified returning the patient to the operating room that night. The outcome was not fully settled when this case was written up, and the team said so openly in the review. The patient was told the reasons in plain language, and her family was updated the next morning. In the following quarter, the ward audited night entries and found that every observation carried a time, and that escalations were made earlier in cases where a trend was recorded.
Questions for discussion
- Which details in the night record would you need before judging the trend, and how could you collect them without delaying review?
- How should a nurse weigh a patient's reassurance against a worsening trend when deciding whether to escalate?
- What would you change in the protocol if the on-call team could not be reached for the first hour of a night shift?
Case Study 2
A monitoring instruction that never reached the ward
Brackwater Hill Hospital, a 360-bed hospital whose plastic surgery unit admits post-operative patients from the recovery room and runs a separate same-day case clinic.
The situation
On a Friday evening, a man in his forties returned from the recovery room to the plastic surgery ward after reconstruction of a crushed hand. The recovery nurse, Kiran, gave a verbal handover to the ward nurse, Dee, by telephone while the patient was still on the stretcher. Kiran covered pain, fluid balance and the planned surgical review. He did not mention the surgeon's written request for checks of hand color and warmth every thirty minutes during the first night. That request sat on a separate operating note, which had not yet been scanned into the patient record.
The challenge
Dee was receiving two new admissions and a discharge in the same hour. The handover template had a field for monitoring frequency, but it was often left blank when information came by telephone. Nobody on the evening team knew the operating note existed. The patient was settled and comfortable, so the routine four-hourly observations went ahead as normal. The gap only became visible at morning rounds, when the surgical resident asked for the half-hourly sheet and none existed.
Analysis
The patient's needs were specific. Changes in color or warmth can be the earliest visible sign that something needs attention, and they are easier to act on when caught early. The surgeon's request reflected that risk and set a monitoring interval to match it. Against that, the routine four-hourly schedule left a far longer gap between checks, and a comfortable patient offered no reason to shorten it. The information needed to make the right decision existed, but it was in the wrong place, on paper that had not reached the ward.
The handover failed as a process, and both nurses were working within habits the system had built. Kiran assumed the operating note would reach the record before the patient arrived. Dee assumed a verbal handover covered everything that mattered, because the template existed and most fields were filled. The transfer protocol requires a written monitoring plan in the record before a patient leaves recovery, along with a read-back of any time-critical instruction. Neither step happened here. Structured tools only help when each person knows which items are non-negotiable, and that knowledge belongs to the team rather than to one nurse's memory.
Actions taken
- Kiran and Dee revised the handover checklist together, adding a required field for monitoring frequency and a line for any outstanding operating note, so a blank field prompts a question.
- Operating notes are scanned to the record before a patient leaves recovery, and the recovery nurse reads the document reference aloud during the handover call.
- Every time-critical monitoring instruction is read back by the receiving nurse, who repeats both the frequency and the reason for it before the call closes.
- The ward audits a sample of transfers each month, recording whether a written monitoring plan was present and how long it took to document the first check.
Results
The surgical team reviewed the patient on the morning round and found no change that needed action, but noted that the half-hourly checks had not been carried out. No harm was identified. The revised checklist was used for the next several transfers, and the first audit found that 31 of 40 transfers carried a written monitoring plan. By the end of the quarter, the figure had risen to 38 of 40, and the remaining two were traced to transfers where the operating note was added after the patient had left recovery.
Questions for discussion
- Where in your own service does a verbal handover carry an instruction that has not yet been written down, and who would notice if it went missing?
- How much should a settled, comfortable patient influence the frequency of checks that a specialist has requested?
- Which items should be treated as non-negotiable in a transfer from recovery to a ward, and how would you test whether staff agree?
Case Study 3
Weighing options for a constrained operating schedule
Thornbury Valley Regional Hospital, a 700-bed teaching hospital whose plastic surgery service runs two elective operating sessions and one clinic each week.
The situation
The reconstructive and cosmetic service at Thornbury Valley had a waiting list of 1,840 patients, and the list was growing faster than operating time could absorb. Two of the four weekly operating sessions had been lost when an anesthesia team was moved to the emergency department for the rest of the quarter. The service lead, Meera, an attending surgeon, and the service manager, Hugh, had to decide how to use what remained. Urgent trauma reconstruction, cancer-related reconstruction, and elective revision requests all competed for the same time, and two surgeons were on leave.
The challenge
Waiting times for urgent cases had begun to stretch past the local target, and some patients were waiting because their lists were full rather than because of their clinical priority. A proposal to keep the cosmetic day list running, since it generated income that funded the nurse-led clinics, was on the table. Meera was concerned that the decision would be read as valuing patients by their ability to pay. The protocol required a documented clinical priority for every listed case and a named reviewer for any case moved between lists.
Analysis
The starting point is clinical priority, and the evidence for ranking cases is uneven. Trauma reconstruction and cancer-related work carry time-sensitive risks that a waiting list score does not fully capture, so the reviewing surgeon's documented assessment matters more than queue position. Elective and cosmetic cases matter to patients, but their need is usually less time-critical. The service's own records showed that the urgent list had the most cancellations, which suggested the existing allocation was not protecting the right cases. Any option has to be tested against that picture rather than against capacity alone.
Coordination decided how the options could be run safely. Moving a patient to another hospital adds handover risk and travel burden, so the protocol requires a clinician to confirm that the receiving team has the full record and the surgical plan. Short-notice rescheduling keeps the operating rooms busy but adds repeat assessments and wears down patient trust. Nurse-led follow-up clinics can release surgeon time without changing who decides, provided escalation routes are written down and reachable. The decision is not Meera's or Hugh's alone. Operating room staff, anesthesia, nursing and the referral office each carry part of the consequence, so each option should be costed in staff time as well as in sessions.
Actions taken
- Meera and Hugh agreed a written clinical priority rule for all listed cases, with urgent trauma and cancer-related reconstruction first and a named reviewer for any move between lists.
- Nurse-led follow-up clinics were expanded for stable post-operative review, with written escalation routes to the surgical team and a time limit on the wait for a surgeon review.
- The cosmetic day list was retained at one session in four, with its assessed need documented in the same format as other lists, so funding decisions stayed separate from patient ranking.
- The partner hospital option was limited to patients whose records were complete, with a named clinician confirming the surgical plan before transfer and a review of outcomes at three months.
Results
Within the quarter, the urgent list was protected and no trauma case waited beyond the local target. The elective waiting list kept growing, though more slowly, and the team reported that openly to the finance committee rather than presenting it as solved. The nurse-led clinics released roughly two operating sessions a month for complex work. Hugh noted that the cosmetic list was the most contested decision, and the written rule made it easier to explain. Patient complaints about cancellations fell, and the service agreed to revisit the partner arrangement after its first review.
Questions for discussion
- How would you rank a cosmetic case against an elective reconstruction case when both are clinically stable, and who should check that ranking?
- What information would you need about a partner hospital before agreeing to transfer patients to it?
- When an operating session is lost, which costs should be counted in the decision besides operating time?
Case Study 4
Unexplained variation in unplanned returns across sites
Halden Moor Specialist Hospital, an independent 74-bed facility with plastic and cosmetic surgery lists and a referral pathway from two district hospitals.
The situation
The unit at Halden Moor had recorded 2,310 episodes over the review period, covering reconstructive and cosmetic lists across two operating sites. The clinical governance committee noticed that unplanned returns to the operating room and unplanned readmissions differed by site and by list type, and that patient-reported satisfaction varied more than the case mix seemed to explain. Indicators were anonymized, with surgeons identified only by code and patients by episode number. The quality lead, Ilse, was asked to find out whether the variation reflected differences in patients or differences in how the service worked.
The challenge
Both sites used the same pathway on paper, but each kept its own pre-operative checklist, and discharge criteria had been agreed informally and never written down. The committee had limited time and no appetite for a large project. The clinical nurse specialist, Yusuf, warned that a quick fix could simply move the variation to another point in the pathway. Two surgeons disagreed about whether the satisfaction gap was worth chasing at all.
Analysis
Before looking for process causes, the team needed to know whether the patients were comparable. The case mix review showed that one site received more referrals from district hospitals, with older patients and more complex histories, so part of the variation was expected. The remainder was not explained by age or comorbidity alone. Satisfaction scores told a related story: patients who reported unclear discharge information gave lower scores regardless of outcome. The evidence therefore pointed toward communication and discharge as well as surgical complexity, and the review was designed to test each explanation rather than assume the strongest one.
Process mapping showed where the pathway drifted between sites. The checklists asked different questions about recent symptoms and current medicines, and discharge decisions depended on which clinician was on duty. Follow-up calls were made by the nurse on the list at one site and by a central team at the other, so a patient's concern could reach someone with no access to the operating notes. The applicable protocol sets a standard for discharge information and follow-up timing, but local interpretation of that standard had drifted. Quality work tends to succeed when the people doing the work map the process themselves, because they know where the workarounds are.
- 1Anonymized indicator reviewUnplanned returns and readmissions tracked by site, list type and surgeon code.
- 2Process mappingTeams trace pre-operative checks, discharge criteria and follow-up calls step by step.
- 3Pilot a shared standardOne checklist and discharge standard, tested on one list per site.
- 4Monitor with run chartsMonthly rates and patient-reported scores plotted against the baseline period.
- 5Review and adaptKeep changes that hold, revise those that do not, and record each decision.
Actions taken
- The team mapped the pathway with two nurses and one surgeon from each site, tracing each step from referral to the first follow-up call and marking where information was lost or repeated.
- A single shared pre-operative checklist and one written discharge standard were drafted, then piloted on one list at each site for eight weeks before any wider rollout.
- Follow-up calls were moved to a single named team with access to operating notes, and each call records the patient's main concern and the action taken within one working day.
- Monthly unplanned return rates, readmissions and patient-reported scores were plotted on run charts by site and list type, with a fixed review point at the end of each pilot.
Results
The pilot narrowed the gap in unplanned returns between the two sites, though it did not close it, which the committee had expected given the referral pattern. Patient-reported scores on discharge information rose on the pilot lists, and follow-up calls were answered within one working day in most cases. Two problems surfaced. One site kept using an older checklist for a month, and a locally added question had been dropped without anyone noticing. The committee agreed to extend the pilot and to keep the run charts visible to both sites.
Questions for discussion
- What would you need to see in case-mix data before concluding that a difference between two sites reflects process rather than patient complexity?
- How would you decide which local workarounds to keep when standardizing a checklist across sites?
- Which monitoring signal would tell you early that an improvement has stopped working, and who should be responsible for acting on it?
Case Study 5
A partner's call and a patient's request for surgery
Marlow Ridge Cosmetic and Reconstructive Clinic, a private outpatient clinic with six consulting rooms and an affiliated surgical center two streets away.
The situation
A man in his late twenties attended a first consultation asking for facial cosmetic surgery to change the appearance of his nose and jaw. During the consultation he mentioned that he had recently been seen by a community mental health team for low mood and a persistent preoccupation with his appearance. He had not given consent for that team to share information with the clinic, and he asked that the clinic not contact them. The attending surgeon, Amara, documented the request and the disclosure in separate parts of the record. Three days later, a woman who identified herself as his partner telephoned asking for an update on his booking.
The challenge
The patient had capacity on the information available, and the clinic's policy allowed him to decide what happened to his record. The partner's call raised a separate question. The clinic could not confirm that he was a patient, let alone share anything about his care. Amara was worried that he might be under pressure, and that a decision made quickly could leave him more vulnerable. The consent policy required a documented assessment before any procedure was listed, and that assessment was not yet complete.
Analysis
The duty of confidentiality applies both to the partner's call and to what was disclosed in the consultation, but the patient's own choices shape what can be done with each. He is entitled to make decisions about his own face and to decide whether his previous care is discussed with the clinic. A recent mental health contact is relevant to decision making, since it bears on whether he can give informed consent for an elective procedure and whether his expectations are realistic. Relevance does not, however, give the clinic permission to share that history with anyone else. The consultation record needs to show the reasoning behind each step, not only the outcome.
Shared decision making depends on the patient being able to speak for himself, so the clinic's first task is to create that space. Amara can explain what a realistic outcome looks like, ask open questions about his expectations, and offer a second consultation without a listing decision on the same day. The partner's call should be handled by a rule rather than by individual judgment. Staff can say that they cannot confirm or discuss any patient without consent, take a message, and pass it to the patient. The matter should be escalated to the clinical lead and the information governance lead, who can review the consent position and the safeguarding question together.
- First consultationPatient requests surgery and discloses recent mental health contact with a community team.
- Three days laterA caller identifying as the partner asks for an update on the booking.
- Second consultationPatient attends alone, and the consultant explores his goals with open questions.
- Governance reviewClinical and information governance leads confirm what was authorized and shared.
- Before any listingPre-operative assessment completed with written agreement to involve the community team.
Actions taken
- Amara offered a second consultation without a listing decision, using open questions about the patient's goals and what he hoped would change in his daily life.
- Front desk staff were given a script for unknown callers: no confirmation of patient status, a message taken, and the patient contacted directly through his registered number.
- The clinical lead and the information governance lead reviewed the record together, confirming what the patient had authorized and what, if anything, had been shared.
- The clinic agreed that no listing would be made until the pre-operative psychological assessment was completed with the patient's written agreement to involve his community team.
Results
The patient attended the second consultation alone and asked for time to think about the procedure. He gave written permission for the clinic to contact his community team, and his care was coordinated between the two services. He did not book a procedure that quarter. The partner received no information, and the clinic recorded the call and the response in the governance log. The review found that the first consultation had documented the request well but had not recorded the reasoning behind the decision not to list, and that gap has since been added to the template.
Questions for discussion
- How would you separate what a patient has told a clinician in confidence from what the clinic can say to a family member who is worried about him?
- When does a recent mental health history change the decision to proceed with an elective procedure, and who should make that judgment?
- What would a good script for an unknown caller look like in your own service, and how would you check that staff follow it under 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.