Pharmacy Practice and Pharmaceutical Sciences Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
Pharmacy practice sits where medicines, records, and people meet, so its decisions rarely arrive as single events. A pharmacist checks a supply, notices that a history does not match, and passes a concern to someone who can act on it. The five cases below come from community, hospital, and family-facing settings, all fictional. Each asks what the team knew at a given point, who owned the next step, and which protocol or safeguard should have carried the information forward. Read them as working records rather than verdicts.
Case Study 1
A pattern in refills nobody owned
Harrowgate Community Pharmacy, an independent group of eleven branches serving a mixed urban and rural catchment under a shared referral protocol.
The situation
Walter, a retired joiner in his seventies, has collected repeat supplies from the Ashgrove branch for four years. Over six weeks, his pharmacist Priya noticed three changes in the refill record. He asked for an extra supply of a simple pain reliever twice, he did not collect one new prescription, and a neighbor began picking up his items. When Priya phoned, he described tiring on the stairs and eating less, and he laughed it off. His general practice had booked a routine review five weeks away. Nothing in the record was alarming on its own, and Walter was clear that he wanted to manage his own affairs.
The challenge
Priya has to decide whether the combined picture justifies contacting the practice before the scheduled review. Her colleague Tomasz argues that the review is close and that a phone call might damage Walter's trust. The local escalation protocol lists triggers such as sudden change in function or unexplained weight loss, but it does not say how to weigh several soft signals together. Priya has no direct examination findings, and the surgery is not open again until the next working day.
Analysis
Patient needs come first here, and they are easy to lose in a refill record. Walter wants to keep his independence, and the signals he gives are partial. Pharmacists trained in Pharmacy Practice and Pharmaceutical Sciences learn to treat timing and pattern as evidence: an earlier request for supply, a skipped collection, and a change in who collects are each small, but together they describe a change in how the person is managing. The clinical evidence is indirect. Priya can record what she saw and heard, avoid guessing at causes, and recognize which observations belong to the prescriber rather than to her.
The team question is who owns the next step. In this branch the referral protocol assigns clinical concerns to the registered prescriber, but it also expects the pharmacist to make contact when a patient may be at risk from a change they cannot describe. Good coordination here means a short, factual message to the practice that separates what was observed from what is inferred, names the person who should act, and asks for a response time. Tomasz's concern about trust is legitimate, so the call should be framed as a shared check on Walter's wellbeing, with his agreement recorded where it can be obtained.
Actions taken
- Phone the practice the same day with a written summary of the refill changes, the telephone observations and the date of the next scheduled review, and ask for a named clinician to call back.
- Speak with Walter before making the call, explain what the team has noticed in his own words, and record whether he agrees to the contact being made.
- Add a dated entry to the patient record describing each observation separately from any assumption, so the next person to collect has the same picture Priya had.
- Review the escalation protocol with the branch team and propose a written threshold for combined soft signals, then test it against the last six months of refill records.
Results
Priya phoned the practice that afternoon. The duty clinician brought the review forward by two days and arranged a home visit, which Walter accepted after a conversation he described as more reasonable than expected. The follow-up identified a change that the team had no way of seeing from the pharmacy, and the plan was adjusted in the following week. The branch added a combined-signals prompt to its refill review, and across the next quarter it logged fourteen entries that met the new threshold, three of which led to contact with a prescriber. Tomasz later noted that the call had not damaged the relationship.
Questions for discussion
- At what point in Walter's refill history would you have made the first call, and what would have changed that point?
- How should a pharmacist record an observation that is accurate but cannot yet be explained?
- What would a written threshold for combined soft signals need to include to avoid triggering contact for every minor change?
Case Study 2
A supply note that stopped at the shift change
Rosemere General Hospital, a 260-bed acute site with a central pharmacy team, two ward satellites, and a shared discharge medicines service.
The situation
Mrs. Ilse Varga, a patient on a medical ward, was moved to a surgical bay in the middle of the afternoon. The morning pharmacist, Marcus, had raised a query with the prescriber about a medicine that might interact with another on her chart, and the answer had not yet come back. He wrote a handover note listing three open reviews, but the query was not in it. The bay nurse gave the usual supply at the evening round. The evening pharmacist, Dana, found the query the next morning while preparing discharge medicines, after the evening supply had already been given. No harm was recorded, but the gap was real.
The challenge
Dana has to decide what to do with a query that was never handed over. The prescriber is off the ward until the next afternoon, the patient is due home that day, and the discharge list has been drafted from a record that omits the open question. The team must decide whether the supply already given changes the plan, who tells the patient, and how the omission is reported without turning the handover into a blame exercise.
Analysis
Patient needs in a handover are often described as information, but here they were a sequence of decisions still waiting to be made. Mrs. Varga's safety depended on a query that existed only in Marcus's notes and memory. The clinical evidence was real but unfinished: an interaction concern had been identified, not resolved. Good handover practice asks first whether an open question is visible to the person who will act on it, because a pending decision that is not written down disappears during a busy shift.
Team coordination failed at the point where responsibility moved, not in the skill of either pharmacist. The applicable protocol expects open queries to be listed with an owner, a due time, and a plan if the answer is not received before transfer. The handover note followed the format but did not follow the content standard. Safeguards that could have caught this include a read-back of open items at bedside handover, a daily reconciliation between the ward chart and the discharge list, and a rule that queries awaiting a prescriber response stay on the ward supply hold until resolved. None is complicated, so their absence is informative.
Actions taken
- Contact the prescriber about the outstanding query at the start of the next working day, and record the answer on the chart before any discharge medicines are finalized.
- Add a required field to the pharmacy handover template for open queries, with an owner, a due time, and a note on what to do if the answer has not arrived.
- Introduce a short verbal read-back of open pharmacy items at each ward handover, with the receiving nurse or pharmacist repeating each item in their own words.
- Audit handover notes against the template for the next quarter, reporting the proportion that list every open query, and share the results at the monthly pharmacy governance meeting.
Results
The discharge was delayed by half a day while the prescriber reviewed the query. The reply confirmed the concern was real but low risk, and the plan was adjusted without further supply changes. Dana documented the timing of the evening supply and the morning discovery. The team's report to the governance group described the failure as a handover design gap, not an individual error. Across the audit period the template was completed in most notes, and open queries appeared in the handover in a higher share of cases than before.
Questions for discussion
- Which open items on a ward chart should always be visible in a handover, and which can reasonably be left out?
- How would the team's response change if the prescriber had been reachable that evening?
- What does a useful handover read-back sound like when the receiving clinician is under time pressure?
Case Study 3
Triage choices when compounding demand outstrips staff
Larkfield Regional Compounding Service, a central unit preparing sterile medicines for three hospitals and two community clinics, staffed on weekdays by six technicians and three checking pharmacists.
The situation
On a Monday after a public holiday, the compounding unit received 214 requests before midday, against a planned load of about 160. Six technicians were rostered, but one was off sick, and one of the three checking pharmacists had been released to cover a ward. Requests came from three hospitals and two community clinics. Most were routine batches for clinic stock, but several were urgent orders for patients on wards with a fixed administration time, and the queue had begun to grow. The oldest routine order was almost a day old.
The challenge
The lead pharmacist, Ruth, must set the order of the queue for the rest of the day. Routine clinic batches can wait, but some are needed for afternoon clinics. Urgent requests must be protected without letting the queue become a series of exceptions. The options include strict urgent-first ordering, batching identical preparations, sending overflow to a partner unit, and pausing new routine intake. Each one carries a cost to quality, traceability, or the working relationship with the clinics.
Analysis
Patient needs in this unit are ranked by time sensitivity, and that ranking is only as good as the priority codes that arrive with each order. The evidence Ruth can use is the unit's own record of time to dispatch, the approved use-by information for each preparation, and the checking log, which shows how much pharmacist time each product type consumes. Clinic batches look efficient on paper, yet a batch that misses an afternoon clinic can leave a patient without supply for the rest of the week. Quality is not only the accuracy of each item but whether the right item reaches the right ward while it is still usable.
The unit's escalation protocol allows the lead pharmacist to change queue order, but it does not allow checks to be skipped to clear a backlog, and it requires any rescheduled order to be communicated to the originating ward or clinic. Coordination therefore has three parts: technicians need a clear sequence to work through, checking pharmacists need a limit they can sustain without fatigue errors, and clinics need early notice. The partner unit can take overflow only under a written agreement covering standards, turnaround, and sign-off, which takes time to arrange and is best set up before the peak rather than during it.
- 1Protect urgent slotsReserve fixed hourly capacity for time-critical requests before any routine work.
- 2Batch routine preparationsCombine identical orders while keeping separate records and checks for each.
- 3Use partner overflowSend next-day routine work out under a written agreement on standards.
- 4Pause new routine intakeHold non-urgent requests briefly, with notice to clinics, until the queue recovers.
- 5Review and record decisionsLog each reschedule and reason so the next peak has evidence to use.
Actions taken
- Protect the urgent queue by setting a fixed number of slots for time-critical requests each hour, reviewed by the lead pharmacist at the top of every hour.
- Batch identical routine preparations into single production runs, provided each batch keeps its own record and labelling check, and tell the clinics which afternoon collection times are affected.
- Contact the partner unit before noon to confirm overflow capacity for next-day routine orders, with a written agreement on turnaround, checking standards, and who signs for returned work.
- Pause non-urgent new requests from clinics for the rest of the day with a clear notice, and resume normal intake once the queue returns to its usual length.
Results
Ruth protected the urgent slots and moved two routine batches to the partner unit. One clinic collection was rescheduled to the following morning and accepted without complaint, while the other clinic asked for written notice next time. The queue cleared by late afternoon with no urgent request missed. The review afterwards found that the batching decision had saved a checking session but added a labelling step the team had not costed. The unit now records the reason for each rescheduled order.
Questions for discussion
- How should a compounding unit weigh a delayed routine batch against a rushed urgent one when both matter to patients?
- What information should a clinic receive when its routine collection moves, and who should give it?
- Which safeguards must stay fixed on the busiest day, even when they slow the queue?
Case Study 4
Uneven discharge discrepancy rates across three wards
Brackenridge Health Partnership, a group of three acute hospitals sharing a pharmacy quality team, a discharge medicines service, and a monthly governance review.
The situation
Over the most recent reporting period, the partnership's post-discharge call service identified medicine discrepancies in 4.1 per 100 discharges from Ward B, against 1.2 on Ward A and 1.9 on Ward C. The figures were anonymized before they reached the quality team, which saw only ward codes, discharge counts, and discrepancy categories. Ward B had the same nursing establishment and a similar case mix on paper. The quality lead, Oksana, noticed that Ward B also had the highest share of discharges completed in the evening. The review had been requested after two consecutive governance meetings showed the gap.
The challenge
Oksana has to explain the variation to the governance group without assuming that Ward B is careless. The indicators are small in number, the categories are recorded differently by each ward, and the call service only reaches patients who answer the phone. She must decide which process causes to test first, who should own the test, and how to tell whether any change is real within the reporting cycle.
Analysis
Patient needs here are easy to describe in aggregate and hard to see in individuals. A discrepancy on a discharge list is a question about whether the person at home has the right instructions and supplies, which matters most for people taking several medicines who have recently changed. The evidence is indirect, drawn from call outcomes and anonymized categories rather than observed practice. Before deciding anything, the review separated the rate from the case mix, asking how many discharges were complex, how many involved a change in medicines, and which errors were documentation rather than supply.
Team coordination is where the likely causes sit. The discharge protocol assigns reconciliation to the ward pharmacist when one is available and to the discharging prescriber otherwise, but Ward B's evening discharges often have neither in the room. Likely process causes include a late discharge decision, a reconciliation step that depends on a pharmacist covering another ward, and a discharge summary template that Ward B had modified locally. Each can be tested with a small change and a clear measure, without changing staffing before the evidence supports it.
- Start of cycleAnonymized records sorted by timing, change type, and error category.
- Third weekEarly reconciliation prompt tested on evening discharges on Ward B.
- Sixth weekTemplate change agreed and checked for use across all three wards.
- End of first cycleWard B compared with its baseline and the other two wards.
- Following quarterTargets reviewed at governance, with judgment held until two full cycles.
Actions taken
- Pull the anonymized discrepancy records for the last four reporting periods and sort them by timing of discharge, medicine changes, and error type, so each ward's pattern can be compared fairly.
- Test an earlier reconciliation prompt on Ward B for two cycles, with the pharmacist reviewing evening discharges by phone before the patient leaves, and record each use.
- Agree a single discharge summary template across the three wards, removing local edits unless the clinical lead approves them, and check that the change is actually in use.
- Set a monitored target for each ward's discrepancy rate and review it monthly at governance, with a rule that any change is judged over at least two full reporting cycles.
Results
The sorting showed that most of Ward B's excess discrepancies came from evening discharges that involved a medicine change, and that most of those were documentation errors rather than supply problems. The early reconciliation prompt reduced the evening share in the first cycle, but the second cycle was affected by a staffing gap that the test could not control. The team kept the template change, extended the review to Ward C, and reported the findings as a process problem. Ward B's rate moved toward the partnership average, though the partnership has not yet confirmed that the change is durable.
Questions for discussion
- What would distinguish a real difference between wards from a difference in case mix?
- How many reporting cycles does a small improvement need before a team can trust its measure?
- Which parts of the discharge process would you protect from local modification, and which should stay open to it?
Case Study 5
Confidentiality and capacity in a family setting
Corran Park Pharmacy, an independent community pharmacy with a home delivery service and a medicines support clinic, serving about 4,200 registered patients.
The situation
Fenna, a woman in her sixties, has collected her medicines at Corran Park for many years. Her adult son, Lars, manages the household and has begun asking the pharmacy for information about her supplies, sometimes by phone and sometimes in person. Fenna asked the pharmacist, Ahmed, to keep her supplies and changes private from Lars. Ahmed noticed that she had recently stopped collecting one item, and that the home delivery address had changed to Lars's house. The pharmacy has no written consent on file for family contact. In conversation she was calm and clear about her wishes, but she also said she was tired of managing everything.
The challenge
Ahmed must decide whether Fenna's wishes can be respected, whether her decision to stop an item is one she can make, and what he can share with Lars. Her prescriber has not yet reviewed the change, and the home delivery arrangement means the pharmacy has to rely on information from a third party. The pressure to protect a long relationship sits alongside a duty not to hide a possible risk from the team that treats her.
Analysis
Fenna's needs include privacy, a sense of control, and a safe supply of medicines. Her stated decision is the starting point, but capacity is decision specific and should not be assumed from age, family pressure, or distress. The evidence in front of Ahmed is an observed change in collection, a changed delivery address, and a conversation, which together justify checking her understanding without concluding that she cannot decide. Pharmacists in this position are expected to separate a person's right to refuse information from the team's duty to act on a risk, and to document which one they are relying on.
Coordination matters because Fenna's care spans the pharmacy, her prescriber, and the home delivery arrangement. The local confidentiality policy allows disclosure without consent only where there is a serious risk to the person or others, and it requires the pharmacist to record the reasoning and inform the lead clinician. The policy also says that a person with capacity can name who should be told and who should not. Lars is not a registered carer, so Ahmed cannot share clinical details with him on the strength of his calls alone. A safe route is a prompt referral to the prescriber, a documented conversation with Fenna about what she wants shared, and a review of the delivery address with her present.
Actions taken
- Speak with Fenna privately, confirm in her own words what she wants shared and with whom, and record her answers in the patient profile with the date.
- Refer the stopped item and the capacity question to the prescriber the same day, with a clear summary of what was observed, what Fenna said, and what has not yet been checked.
- Check the delivery address change directly with Fenna, away from any third party, and confirm whether she wants deliveries to continue to Lars's home or go to another address.
- Agree in writing with the lead pharmacist which calls from family members may be answered, which must be referred, and what the escalation route is if a safety concern is raised.
Results
Ahmed spoke with Fenna in a private consultation room. She confirmed that she wanted the stopped item discussed with her prescriber and that she did not want Lars given clinical detail. The prescriber reviewed her case within the week, arranged a longer appointment, and agreed a review date. Fenna chose to have deliveries sent to a neighbor's address. The pharmacy's family-contact guidance was updated, and staff now record who is authorized to receive information. The case was discussed at governance as a consent and communication question, not a confidentiality breach.
Questions for discussion
- What evidence would move Ahmed from respecting Fenna's wishes to acting against them?
- How should a pharmacy record a family member's calls when the patient has not yet said what can be shared?
- When does a sensible delay become a failure to escalate, and who should decide where that point lies?
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.