Dermatology and Aesthetic Medicine Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
Dermatology and aesthetic medicine look straightforward from the outside, yet a good share of the risk in these services sits in the spaces between people: the nurse line and the referral list, the afternoon clinician and the evening nurse, the booking form and the consultation room. The five cases here come from clinics and units of different sizes, and each one asks a practitioner to work the way a team would. The diagrams summarize the reasoning and do not replace it. Where a judgment could reasonably have gone another way, the analysis says so.
Case Study 1
A changing lesion waiting in a message queue
Pellham Ridge Skin Clinic, an outpatient practice of 14 clinicians attached to a regional hospital network, handling about 9,000 patient contacts in a typical year.
The situation
A man in his late fifties was referred for a pigmented lesion on his upper back. At intake the nurse recorded that the lesion looked irregular in outline and uneven in color, but that the patient reported no recent change. He was placed on the routine waiting list, which ran about six weeks. During that wait he sent two messages to the clinic's nurse line. The first said the lesion had started to bleed after rubbing against his shirt. The second, a week later, said it had grown and that a new smaller spot had appeared close by. Both messages were logged as general enquiries and answered from the standard script. Neither reached the triage clinician.
The challenge
The triage team had to decide whether the messages changed how the referral should be ranked, how quickly the waiting appointment could move, and whether to ask for an earlier review. The local protocol ranked urgency from the referral letter and any update logged in the record. Here the update existed, but it sat in a channel the ranking step never read. The question was less about what the lesion looked like than about who was responsible for reading new information once a patient was already waiting.
Analysis
The first need was a timely review by someone able to judge the lesion, not reassurance delivered through a message queue. In a waiting lesion, clinical evidence rests largely on how it has changed, so a reported change is clinical information in its own right. Practitioners grounded in Dermatology and Aesthetic Medicine tend to treat a patient's account of change as a signal to be routed, not a comment to be filed. The protocol in use ranked urgency from the referral letter alone. That gap sits at the center: the signal arrived through a channel the protocol did not read, and nobody answering the messages had instructions to pass them on.
Coordination broke down at a predictable point. The nurse line and the referral queue were run by different staff, and neither could see the other's notes. The triage protocol stated that any reported change in a waiting lesion should reach a clinician the same working day, but that instruction sat in a section the nurse line did not use. The reviewing clinician said the rule would have applied had anyone read the messages as clinical. A stronger arrangement would route every message that mentions a waiting lesion to a named clinician, with a written reply time and the decision recorded, whether or not the clinician judged the change urgent.
Actions taken
- Add a flag to the referral queue so that any inbound message referencing a waiting lesion is copied to the triage clinician within one working day.
- Rewrite the nurse line script so staff ask directly about bleeding, growth, and new lesions, and record each answer in the structured triage form.
- Set a review of all waiting lesion referrals by the clinician each week for the first quarter, counting how many had a documented change at intake.
- Agree in writing which staff member owns the waiting list after a referral is accepted, and name a backup for leave periods.
Results
The clinic reviewed every open waiting-lesion referral in the first week after the change. Two of the twenty-three files held messages that had never reached a clinician. One of those patients was seen earlier than the original booking and referred on for specialist assessment. Nobody could say whether the earlier review changed the outcome, and the team did not claim it had. The audit over the following two months showed that messages about waiting lesions reached a clinician the same working day in every sampled case.
Questions for discussion
- Which parts of a triage protocol should be written for nurses to act on, and which should stay with the clinician who reads the referral?
- How should a team weigh a patient's own report of change against an image or record that looks stable?
- Who should own a message that arrives after a referral is already waiting, and what reply time is reasonable?
Case Study 2
A planned call-back lost at shift change
Westbrook Lane Aesthetic and Skin Unit, a private day unit of about 40 staff that runs elective sessions and medical skin reviews on one floor.
The situation
Westbrook Lane's afternoon list ends with a few elective sessions that often run late. One patient, a woman in her forties, attended a session in which the clinician, Marcus, noticed more redness than expected and recorded that he wanted a nurse to phone her the next morning to check on it. The day charge nurse wrote the shift handover from his notes and summarized the visit as reviewed, no concerns. The follow-up call was not listed. The evening nurse, Ines, had no reason to expect a call and none was made. Two days later the patient came back to the unit with symptoms that needed same-day assessment elsewhere.
The challenge
The review team needed to find where the plan was lost and whether that was a single lapse or a pattern. Staff described the handover as thorough. The template was used, a verbal summary was given, and the record was signed off. Yet the one item that mattered lived in a clinician's note and in a task that had never been created. The team had to separate individual error from a process that made the error easy to make.
Analysis
The patient's need was simple to state and easy to lose: someone had to check a change the clinician had flagged as worth watching. The evidence for that plan was the clinician's own note, which recorded what was seen and what was wanted next. When a handover compresses that note into reviewed, no concerns, the reasoning disappears before it reaches the person who has to act on it. Good handover practice keeps the clinical note in view and treats the summary as a pointer to it. The protocol required the follow-up plan to be carried across, yet the template made that field optional, so the omission was predictable.
The plan lived with two people who did not share one picture of it. Marcus believed the call was booked because he had asked for it. Ines believed a handover with no call listed meant there was none. Neither was careless. The safeguards that should have caught the mismatch were weak: the handover was largely spoken, the template field was optional, and read-back happened informally. Written policy asked a second person to check open call-backs before shift close, but that check only worked when someone remembered to run it. A useful review separates these layers and measures each one, rather than relying on the outcome alone.
Actions taken
- Make the follow-up field mandatory in the handover template, and block shift close until each open clinical check has an owner and a time.
- Require the receiving nurse to read back every call-back by name and time, and record the read-back in the shift log.
- Create a task automatically from any clinician note that includes a planned patient contact, so the plan exists outside the free text.
- Track the proportion of handovers with a completed call-back check each month, aiming for every eligible shift within one quarter, and report it at the unit meeting.
Results
The unit made the follow-up field mandatory and added the automatic task within the first month. In the audit that followed, every eligible shift had a recorded call-back check, against about one shift in three in the earlier sample. Two open call-backs were missed in the first weeks after the change, and both were caught by the second-person check and completed the same day. The team counted that as evidence the safeguard worked, and also as evidence that it was not yet reliable enough to carry alone.
Questions for discussion
- Where should the line sit between a clinician's free-text note and a structured task, and who decides when a plan belongs in both?
- If a safeguard depends on someone remembering to run it, what does that suggest about the process as designed?
- How would you judge whether a handover template serves the receiving nurse or mainly protects the team that wrote it?
Case Study 3
Triage and scheduling choices for a backlog under pressure
Corvan Valley Dermatology Service, a public outpatient service across three sites with a waiting list of about 2,400 people.
The situation
Corvan Valley's outpatient service covers three sites and carries a waiting list of about 2,400 people. For three weeks, two consultant sessions were lost to staff leave, and the only imaging unit used to compare pigmented lesions over time went out for repair. Referrals kept arriving at the usual rate. The service manager, Tomas, had to keep urgent lesion reviews moving while the routine list grew. Some patients were waiting for checks of stable conditions. Others were waiting for specialist review of lesions that had changed. Nursing time was split across three sites, and intake was still filing referrals by the date received rather than by clinical content.
The challenge
Tomas had three levers, and each carried a cost. Tightening triage could move patients out of the queue sooner, but it relied on reading referral content consistently, which the intake team had not been trained to do. Rebuilding the schedule could protect urgent slots, though the elective list would grow longer. Moving nursing time between sites could ease one clinic while weakening another. The decision had to protect the most time-sensitive patients without leaving everyone else with no sense of when they might be seen.
Analysis
The clinical question behind any queue is what the referral describes, not how long a person has waited. Evidence in this setting comes from the referral text: a stable lesion reviewed for reassurance carries a different urgency from one with reported change over a short interval. Protocols usually set urgency bands from this content, so a service that sorts by arrival date is ignoring information it already holds. Good triage starts with the stated concern and only then looks at the calendar. The imaging unit adds a second constraint, because some monitoring reviews depend on comparing images over time, and a queue without that equipment cannot finish those reviews.
Staff coordination was the real bottleneck. Triage nurses, booking clerks, and the clinicians who approve urgency bands each worked from a different list, and none held the full picture. The regional staffing protocol allowed a site to borrow nursing time when it fell below an agreed level, but it required a named lead to make the call and record it. Without a record, borrowed time looked like favoritism between sites. A stronger model gives the clinical lead one shared list, a fixed weekly decision point, and a written rule for when a clinic may borrow staff, so each choice is visible and can be reversed.
- 1Demand arrivesUrgent medical reviews and elective cosmetic bookings both reach the same clinic calendar.
- 2Triage by urgencyClinicians assign urgency from referral content, with a nurse check on incomplete forms.
- 3Protected clinical slotsMedical reviews get protected slots, elective work fills what remains of each session.
- 4Reallocate nursing timeSurplus nursing time moves only after protected slots are confirmed.
- 5Weekly waiting reviewWeekly check of waiting times by urgency band, shared with the clinical lead.
Actions taken
- Retrain the intake team to sort referrals by urgency band using the written criteria, and sample ten referrals a week for consistency.
- Hold back two protected slots each week for urgent lesion reviews, released by the clinical lead on the day they are needed.
- Write a shared-staffing rule that allows nursing time to move between sites only when a named lead records the reason and the expected return date.
- Move the imaging review queue to the site with the working unit for the next four weeks, and notify affected patients of the new location in writing.
Results
Within the first month the service held its urgent lesion slots on every clinic day and cleared the backlog of reviews flagged as changed, though the routine list grew by a small margin. The intake team's sample showed that about four in five referrals now sat in the urgency band the clinician later confirmed. Nursing time moved twice, each time with a recorded reason, and one move was reversed when the receiving clinic's demand eased. Tomas said the elective list was still long, and the service said so in its letters rather than offering a date it could not meet.
Questions for discussion
- When a service must ration a scarce resource, what should patients be able to see about how the decision was made?
- Which parts of a triage decision can be written as criteria, and which must remain with a clinician reading the referral?
- How would you test whether a protected slot is protecting urgent patients or sitting empty?
Case Study 4
Inconsistent review timings across three network sites
Tallow Creek Skin Health Network, three general clinics sharing one referral intake and a small central quality team.
The situation
Tallow Creek's shared intake handled about 3,100 new lesion referrals over the previous six months. The quality team reported that the share with a documented first specialist review inside the agreed window ranged from roughly 58 percent at the smallest site to 81 percent at the largest. Site leads each had an explanation. The smallest site said its patients arrived with more complicated histories. The largest said its clinicians simply recorded reviews more carefully. The middle site had changed its booking tool partway through. Nobody had compared the underlying records side by side, and the indicators had been pulled from three slightly different systems.
The challenge
Ruth, the network's clinical quality lead, had to decide what the variation meant before anyone changed a process. It could reflect case mix, differences in documentation, or real delays in getting patients seen. Each explanation pointed to a different response, and acting on the wrong one could add pressure to clinicians already at capacity or fund a new system that changed nothing. The first task was to make the three sites' indicators comparable.
Analysis
Each indicator stands in for timely, understandable review, and a percentage cannot describe that on its own. The team first compared referral reasons at each site, looking for a higher share of lesions with reported change at one site, since a heavier clinical mix should show up as a different queue, not as a lower score. The case-mix argument weakened once the reasons were compared. The sites were not seeing different patients in any way the data could show. They were counting the same events differently, which is a measurement problem before it is a care problem.
The regional quality framework sets a target window for first specialist review but does not define what counts as a review when the first contact is a telephone triage call. Two sites counted that call as the review. The third waited for the face-to-face appointment, which in practice came weeks later. That single definition difference explained much of the gap, and nobody had written it down. Different booking tools at the three sites also meant one patient could appear as two referrals. A review team should agree the definition and the unit of counting first, then measure again. Only then can a change be judged.
- Start of cycleIndicators pulled for all three sites, with identifiers removed before sharing.
- Second weekQuality team and site leads agreed what counted as a completed review.
- Fourth weekTelephone triage recorded as a review at two sites, face-to-face at one.
- Eighth weekPilot of a shared referral log across all three sites begins.
- Three months laterIndicators rechecked against the new definition, with variation narrowing.
Actions taken
- Agree one written definition of a completed first review, covering telephone triage, and apply it to all three sites from the next audit period.
- Link referral records across sites using a shared patient reference, so one person's journey is counted once and cannot split into duplicates.
- Run a monthly sample of twenty referrals per site, checked by a second reviewer against the agreed definition, and feed results to site leads.
- Pilot one change at the smallest site, a fixed daily slot for triage review, and compare its window performance with the other two sites over the cycle.
Results
Once the sites applied one definition, the gap between highest and lowest narrowed to under ten percentage points, from a spread of about twenty-three before. The shared patient reference found roughly forty duplicate records, which had inflated the count at one site. The pilot daily triage slot at the smallest site improved its window performance modestly, though the sample was small and the report said so. Ruth kept the monitoring running for another cycle before deciding whether to extend the slot to the other sites.
Questions for discussion
- When sites report different results for the same indicator, what should a quality team check first before proposing a change?
- How much weight should a shared definition carry against established local practice when the two disagree?
- What would a pilot need to show before a team could responsibly extend it across every site?
Case Study 5
Confidentiality and a finding during a family-booked consultation
Linden Court Cosmetic and Medical Dermatology, a small clinic combining medical skin reviews with elective aesthetic consultations, staffed by about 22 people.
The situation
About a fifth of Linden Court's consultations are booked by someone other than the patient, usually a partner or a parent. A woman in her thirties attended an aesthetic consultation that her partner had booked and paid for, and he asked to stay in the room. During the examination the clinician, Priya, noted a pigmented area that did not match the cosmetic concern and wanted it reviewed by the medical team. When the partner asked what she had found, the patient said quietly that she did not want him told about it yet. He remained in the room and was waiting for an answer.
The challenge
Priya had three duties that did not point the same way: the patient's right to confidentiality, the clinic's responsibility to act on a finding that needed review, and the partner's reasonable interest as the person who had paid. She also had to judge whether the patient was speaking freely. The consent policy covered the cosmetic work but said little about what to do when a booker is present while a medical finding is discussed.
Analysis
Her stated wish was simple: a private decision about a finding on her own body. The clinical evidence concerned the finding, which needed a timely medical review whatever the patient wanted anyone else to know. Those two things can coexist. A review can be arranged without giving its reason to a third party, and the patient can be told what the clinic must do and why. Good practice in this area separates who needs to know from what the patient wants said. Priya needed agreement to a review and an honest account of what would follow if the patient declined.
The applicable protocols were the clinic's confidentiality policy, its consent standard for elective work, and its safeguarding procedure. Together they set a clear order. Consent to share with a third party belongs to the patient, so the partner could not be given the finding without her permission. The clinical finding, though, had to reach the medical lead the same day, and the consent question could not delay that handoff. Safeguarding applied if the patient's account suggested pressure, control, or fear of the partner's reaction. In that case the safeguarding lead took over under the local procedure, and the clinician did not try to settle the matter alone.
Actions taken
- Arrange a medical review of the finding by the clinic's medical lead within the same working day, without disclosing its reason to anyone not authorized by the patient.
- Speak with the patient privately, without the partner present, to confirm what she wants shared and to explain plainly what the clinic must do.
- Refer the questions about pressure or fear to the safeguarding lead, using the local procedure, and do not make a judgment about the relationship alone.
- Update the consent form so that a booker's presence, and what they may be told, is recorded before any consultation starts.
Results
The patient agreed to the medical review and asked that her partner not be told the reason. Priya recorded that choice, the medical lead saw her later the same working day, and the review was booked with no reference to the cosmetic appointment. Asked directly about safety, she said she was not afraid of her partner but wanted her privacy respected. The safeguarding lead received that statement and added a note to the file. The consent form now asks at booking whether anyone else will attend and what they may be told.
Questions for discussion
- When a third party pays for a consultation, what should a clinician settle before any finding is discussed?
- How far should a patient's own statement that she feels safe shape a decision to escalate?
- Which parts of a confidentiality decision belong in written policy, and which must stay with the clinician in the room?
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.