Community and Public Health Practice Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
This set of five cases follows community health and public health teams through situations that test everyday practice. A symptom picture changes faster than a referral pathway, a weekend handover drops a visit plan, a caseload outruns the nursing hours available, a prevention program shows uneven results across its sites, and a young person asks for something the service cannot promise. Each case is told from the side of the people doing the work. The aim is to show how patient needs, clinical evidence, team coordination, and local protocols shape a decision, and where they pull against each other.
Case Study 1
Escalating symptoms on a Friday afternoon visit
Corran Ridge Community Nursing, a district nursing service with six nurses and two case coordinators covering a rural area of about 14,000 residents.
The situation
Lena, the district nurse, had seen Walter, a retired machinist in his late seventies, every second day for three weeks after a short hospital stay. Over that period his ankle swelling had come and gone, but on a Friday afternoon it had spread up his shins, his appetite had dropped, and his daughter reported that he was sleeping in the chair. His oxygen reading had drifted lower at each of the last two visits. Lena had a clinic slot with the general practitioner for Monday and a referral form half-filled on her tablet. The district protocol for deteriorating older adults at home lists triggers for same-day medical review, and the team had not agreed which ones applied.
The challenge
The difficulty was less about any single reading than about how the signs fit together. Walter's swelling, breathlessness on the stairs, and falling oxygen reading could be a slow worsening of a long-standing condition, a new infection, or a medication effect that nobody had yet checked. Lena could not assess him properly by telephone, and the on-call doctor was covering two other districts. Every option carried a cost: an emergency transfer that might be unnecessary, or a wait that might end with an admission over the weekend.
Analysis
Practitioners trained in Community and Public Health Practice tend to begin with the person rather than the protocol. For Walter, the most useful evidence was the trajectory, not any single number. The last three visits showed swelling that was intermittent before it became persistent, a slowly falling oxygen reading, and a change in how he moved around his home. Those changes matter because older adults present with vague or atypical signs, and the family's observation of sleeping in a chair carried information that a clinic reading would not capture. The clinical evidence was incomplete, which meant the team had to decide on what was known and say what was not.
The protocol gave the team a set of triggers, but it did not tell them who should hold the decision when two triggers were ambiguous. Lena's instinct was to call the on-call doctor, and Priya, the coordinator, pointed out that the referral pathway required the general practitioner to accept the referral. The team agreed a sequence: Lena would record the trend against the triggers in the shared care record, Priya would check whether the urgent community response service could visit before evening, and the family would get written advice on which changes meant calling the emergency line. Protocols work when they name who acts, not only the threshold.
Actions taken
- Lena added each escalation trigger from the district protocol to the front of the shared care record, with a tick box for whether it was present at each visit.
- Priya arranged a same-day telephone review with the on-call doctor using the written trend summary, so the decision rested on a single shared picture of the change.
- The team asked the urgent community response service whether it could visit before evening, and recorded the answer, the visit time and the reason in the handover log.
- Lena gave the family a written list of changes that meant calling the emergency line straight away, then phoned them that evening to confirm they understood it.
Results
Walter was reviewed by the on-call doctor that evening and sent to the district hospital for same-day assessment. He stayed two nights. The discharge summary described a change the community team had flagged but could not have confirmed at home. Over the following quarter, the service logged twenty-three trigger reviews in the shared record, and an internal audit found a named decision owner on every one. Lena said the most useful change was the family's written list, which his daughter used twice more before the next scheduled visit.
Questions for discussion
- Which of the listed triggers would you have treated as decisive on that Friday afternoon, and what additional information would have changed your view?
- How should a team decide who owns an escalation when the protocol names thresholds but not responsibilities?
- What does a written family plan need to say to be useful when the person at home is unlikely to read it closely?
Case Study 2
A weekend handover that dropped a visit plan
Marlow Quay Community Health Team, a neighborhood service with nine clinicians and a shared weekend rota serving about 22,000 registered patients.
The situation
Marisol, a senior community nurse, handed over her caseload to Tomasz at the end of a Friday shift. Among her patients was Grace, who was seventy and living alone after a recent fall at home. On Thursday, Grace's neighbor had phoned to say she seemed unsteady and was not eating well. Marisol had changed Grace's visit plan from every third day to daily for the weekend and had written this in the free text of the day's log. The formal handover summary, which the weekend rota is built from, still showed the old frequency. Tomasz read the summary, saw no weekend visits booked for Grace, and did not open the log.
The challenge
The gap was invisible from either side. Marisol believed the change had been passed on because it was in the record, and Tomasz believed the summary was complete because it was the document the team had agreed to use. Grace was not in acute danger at handover, but her needs had changed in ways the weekend team had to know before Saturday. The team had no rule for which changes must be copied into the summary, so the cause was hard to pin down.
Analysis
Patient needs in community settings are often carried in small observations rather than formal assessments. Grace's neighbor noticed unsteadiness and poor intake, which together suggested a change in her ability to manage at home. The clinical picture had not been reassessed, so the team could not say whether the change was temporary or a new trend. What the evidence did support was a simple principle: a person who has recently fallen and is living alone needs a known contact point across the weekend, and the visit frequency was the part of her plan that reflected that need. Any handover that drops frequency drops a safeguard along with it.
The team's handover standard required a structured summary, but it did not define which changes counted as material. The protocol required verbal confirmation of any change in visit frequency for a patient at elevated risk, but the call that Friday was short. Tomasz had no reason to doubt the summary, and Marisol had no prompt to check it. A shared checklist, or a rule that the summary is generated from the log rather than typed separately, would have closed the gap at the point where it opened. The lesson is less about vigilance than about designing the handover so that vigilance is not the only barrier.
- Record changes Enter every change to frequency or risk in a dedicated summary field.
- Reconcile the rota Build the weekend rota only from the reconciled list, checked against the log.
- Read back aloud Outgoing nurse states the three highest-risk changes; receiver repeats them.
- Audit and review Sample handovers weekly and share misses with the whole team.
Actions taken
- Marisol and Tomasz rewrote the handover summary so that any change to visit frequency appears in a dedicated line, not in the free text of the daily log.
- The service agreed that the weekend rota is built only from a reconciled list, and a coordinator checks that list against the log before the Friday shift ends.
- Each handover now includes a two minute verbal read-back in which the outgoing nurse states the three highest-risk changes and the receiving nurse repeats them.
- Over the next quarter the team will audit a sample of handovers each week, measuring how many recorded frequency changes appear in the summary, with a target of every change captured.
Results
Grace was seen on Saturday morning, after her neighbor called the service to ask why nobody had come. Tomasz checked the log, found the change, and arranged the visit within the hour. She was unsteady but not injured. The first audit of the new format, carried out over the following quarter, found that the summary captured every recorded frequency change in the sample reviewed. The read-back added about two minutes to each handover and caught one omission on a different patient in its first month.
Questions for discussion
- Where in your own handover process would a change recorded in free text be least likely to reach the person who needs it?
- What should a verbal read-back include so that it adds protection without becoming a formality?
- How would you weigh the cost of a rewritten summary against the risk of relying on individual memory across a long weekend?
Case Study 3
Choosing which visits to protect during a staffing shortfall
Pellham Row Home Visiting Service, a public health nursing team covering two towns with twelve nurses, a shared transport pool and a central booking desk.
The situation
Pellham Row Home Visiting Service had planned for twelve nurses across the district. In the third week of a seasonal illness surge, four were off sick and one post remained unfilled, leaving seven nurses for a caseload that normally needed nine. The waiting list for home visits had grown to 186 referrals, most of them post-discharge follow-ups, frailty checks and new-parent visits. Two of the vehicles were in maintenance, so visits that required a car had to be sequenced around the shared transport pool. Nasrin, the service manager, had until the end of the day to decide how the next week's schedule would be set, and the regional office expected a written plan.
The challenge
Every option moved risk somewhere else. Cancelling the new-parent visits protected frailty checks but left infants without an early weight and feeding review. Extending the waiting list kept visits within the team's capacity but lengthened the gap for people leaving hospital, where a missed follow-up tends to cost the most. Nasrin could also ask the central booking desk to triage by referral date, which was simple to explain but ignored urgency. The plan had to show the regional office how each group would be treated, and why.
Analysis
Clinical need is not evenly distributed across a waiting list, and a first-come schedule hides that. The post-discharge group carries the highest short-term risk because medication and mobility changes often surface in the first days at home, but frailty checks are where unplanned admissions can sometimes be prevented, and new-parent visits are time-limited in a way that makes a missed window hard to recover. Local records showed that the largest share of urgent escalations came from post-discharge visits delayed by more than two days. That is a local pattern, not a general rule, and it is best read as a reason to look more closely rather than a verdict.
The allocation protocol sets priority bands for home visits, but it was written for normal staffing and says little about what to do when bands compete. Post-discharge visits sit in the top band, so the team could satisfy its own rule by filling those slots while the frailty and new-parent lists slipped. Nasrin proposed covering the top band in full, moving frailty checks to telephone reviews with an agreed escalation script, and offering new-parent visits at the health center alongside scheduled clinic appointments. The regional office wanted the reasoning recorded, so the plan had to name the protocol clauses it relied on and the ones it was setting aside.
Actions taken
- Nasrin ring-fenced the top band so that every post-discharge visit within two days was booked before any other slot was filled, with the booking desk confirming each one.
- Frailty checks moved to a scripted telephone review, with written criteria for same-day home visits and a nurse on call to take any referral the script flags.
- New-parent visits were offered at the health center on the day of a scheduled clinic appointment, with a home visit kept for families who could not attend.
- The team logged every deferred referral with its band, its waiting time and the reason for deferral, and reviewed the log at the end of each week with the regional lead.
Results
Within the first two weeks, the top band had no unvisited post-discharge referrals older than two days. Frailty checks by telephone caught three people whose needs had changed, and two of them were seen the same day at home. Waiting times for new-parent visits rose slightly, and one family reported that the clinic-linked slot suited them better than a home visit. The deferral log showed that the team had deferred ninety-four referrals, and that the regional lead accepted the written rationale without changes. Nasrin noted that the plan worked partly because it named what was being set aside.
Questions for discussion
- Which group on this waiting list would you protect first if the top band had been full, and what evidence would you need before accepting that choice?
- How much of a deferral decision should sit with the manager, and how much should be set by a protocol agreed before the shortage begins?
- What does a deferral record need to contain so that a later reviewer can see who was harmed by delay and who was not?
Case Study 4
Uneven outcomes across four neighborhood prevention clinics
Ashgrove Community Health Partnership, a network of four neighborhood clinics running a structured prevention program for about 9,400 enrolled adults.
The situation
Ashgrove runs a structured prevention program across four neighborhood clinics, and each site reports the same quarterly indicators to the partnership board. Over the most recent period, the two northern clinics completed scheduled reviews on time for most participants, while the two southern clinics fell well short, and the gap had not closed after a refresher session. Dana, the quality lead, pulled anonymized records for 1,240 participants and found that the difference was not in who enrolled but in what happened after the first contact. The board wanted a recommendation before the next meeting, and the southern clinics' staff were already disputing whether the indicator was measured fairly.
The challenge
The obvious explanation, that the southern sites were less skilled, did not fit the data. Their staff had the same training, and their sites scored well on the process indicators they controlled directly. The likely causes sat in the handoffs between clinician, coordinator and participant, where a missed reminder or an unclear owner could stop a review from happening at all. The team had to separate measurement artifacts from real process failures before it could design anything, and it had little time to do so.
Analysis
Participants in a prevention program are not acute patients, but their needs are still specific and they still carry risk. For enrolled adults, the value of a review lies in the conversation about change over time, so a missed review is more than a missed box. The indicator data showed that southern participants who did attend a first contact were nearly as likely to complete later reviews as northern participants, suggesting the early drop-off is where needs are being lost. The evidence also had limits: the indicators counted scheduled reviews, not the quality of the conversations held in them, and the records did not capture why a person had stopped attending.
The partnership's framework requires a named owner for each indicator at each site, and the southern clinics had given review scheduling to whoever was free that morning. The program protocol specifies a reminder at fixed intervals and a clinician review of any participant who misses two consecutive appointments, but the second step depended on a coordinator noticing the missed booking in a shared list that was not sorted by date. That is a process design problem, and it would look the same at any site with the same workflow. Tracing five or six participants from enrollment to their first missed review would show where the protocol steps were actually taken.
Actions taken
- Each site named one owner for review scheduling, and the name appears on the team roster and at the top of the participant list rather than in a general instruction.
- The shared list was re-sorted so that any participant with a missed review appears first, and the coordinator checks that view at the start of every session.
- The team agreed a fixed escalation step after two missed reviews, a clinician conversation booked within five working days, recorded against the participant's file.
- All four clinics report the indicator monthly using the same definition, with a monitoring run of three months to see whether the change moves completion rates in the southern clinics.
Results
After three months, completion of scheduled reviews in the southern clinics rose by a margin the board called meaningful, though it remained below the northern sites. The number of participants flagged after two missed reviews rose at first, which the team read as the new step working rather than a deterioration. Two southern participants who had dropped out were re-engaged that month, and the indicator definition was agreed by all four sites. Dana cautioned the board that three months is a short window, and that the results would need a second cycle before anyone drew conclusions.
Questions for discussion
- What would a fair definition of a completed review look like if two sites served populations with different travel times and work patterns?
- When a process depends on someone noticing a problem in a list, how would you test whether the list itself is the cause?
- How long should a quality cycle run before a team is willing to change its definition of success?
Case Study 5
Confidentiality when a young person asks for secrecy
Wrenfield Family Support Service, a community social and health team giving home-based support to families with complex needs, with eight staff across two districts.
The situation
Kenji, a family support worker, had been visiting Leah for six weeks. Leah was sixteen and living with her grandmother, who was caring for a younger brother and was stretched thin. In the most recent visit, Leah told Kenji she had been staying some nights at a friend's apartment and missing school, and that she did not want her grandmother told. She also described a low mood that had lasted most of the month and said, when asked, that she had thought about hurting herself but would not act on it. She asked Kenji to keep the conversation private. Kenji had to decide what he could promise, what he had to share, and with whom, before his next scheduled visit.
The challenge
The duties pulled in different directions. Leah's wish for privacy was a real interest and a condition of her continuing to engage with the service at all, and breaking it without a reason she understood could end the relationship. Her description of low mood and thoughts of self-harm, however, moved the situation into safeguarding territory, where the service's policy does not allow a worker to hold the information alone. The grandmother was not aware of any of this and had her own needs as a carer.
Analysis
Leah's most urgent need is her safety, the part she wants kept private. Consent in this setting is not a single yes or no. It is an ongoing negotiation in which a young person can agree to some sharing and not other sharing, and in which the worker must be honest about where confidentiality ends. The evidence Kenji had was his own record of her presentation over six weeks, a school attendance concern raised by the education liaison, and her direct words. None of these was a clinical assessment, which is why the safeguarding route, rather than his own judgment alone, was the right place to take the decision.
The service's confidentiality policy allows disclosure without consent where a young person may be at risk of significant harm, and it requires the worker to inform a line manager first. It also expects the worker to explain to the young person what will happen and to agree the route with her where possible. Kenji spoke to Imani, his line manager, that afternoon. She asked him to write up Leah's own words separately from his interpretation, and together they agreed that he would go back to Leah before anyone else was contacted, explaining what had to happen and asking how she wanted it done.
- 1Hear and recordWrite the young person's words and observations separately from interpretation.
- 2Tell her firstExplain what must be shared, why, and invite her views on how.
- 3Inform line managerShare with the line manager; consent is not needed where significant harm is possible.
- 4Agree the routeShare only with people who must act, and update Leah at each step.
- 5Review with supervisorCheck the decision against policy and document the reasons for each disclosure.
Actions taken
- Kenji wrote a dated record of Leah's exact words, what he observed, and what he planned to do next, and filed it before the end of the day.
- He told Leah in person, that same day if possible, which information would have to be shared, with whom, and why, and invited her to suggest the wording.
- Imani arranged a same-week safeguarding discussion with the duty lead and the school's designated contact, limited to what each person needed to act on.
- Kenji agreed a short written safety plan with Leah, listing the adults she could contact at night and the point at which she would call the emergency line.
Results
Leah was not pleased to hear that the grandmother would be told, but she said she had expected it and asked Kenji to be the one who explained. The duty lead agreed that the grandmother should be included in the next conversation, with Leah present. The school arranged a welfare check, and within two weeks Leah had returned to lessons on three days a week. The case was reviewed at supervision, and the team's audit of disclosure decisions found that the written record had been completed on time in every case reviewed that quarter.
Questions for discussion
- At what point would you have stopped negotiating with Leah about what could be shared, and what would have made that point clear?
- How should a worker record a young person's own words when those words are later used in a safeguarding decision?
- What support does the grandmother need from the service, and how should that be arranged without undermining Leah's trust?
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.