| Course | HLTH 6882 Improving Healthcare Performance Through Social Entrepreneurship |
|---|---|
| Week | Week 4 |
| Paper type | Root cause analysis paper |
| Length | About 1,050 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | graduate health administration program |
| Updated | October 2026 |
Free sample paper for HLTH 6882 Week 4
Root Cause Analysis: Why Specialist Slots Booked Six or More Weeks Ahead Go Unused at Prairie Bend
Student Name
Walden University
HLTH 6882: Improving Healthcare Performance Through Social Entrepreneurship
Instructor Name
Month Day, Year
Root Cause Analysis: Why Specialist Slots Booked Six or More Weeks Ahead Go Unused at Prairie Bend
Introduction
Last week's gap analysis found that slots booked 43 or more days before the session day at Prairie Bend Community Hospital's visiting specialist clinic were lost at a rate of 37%, and that these bookings make up most of the clinic's lost slots. This analysis asks why, using a five whys chain. It follows one rule: no answer is accepted until it is checked against the clinic's own records or a documented interview, and only then is the next why asked. One tempting branch, that transport explains the loss, was tested and abandoned, and it is shown below. All figures come from the composite organization and are illustrative.
A Caution About the Method
Five whys is a simple tool with known weaknesses. A critique in a leading quality and safety journal argued that it tends to follow a single causal path when most problems have several, and that its conclusions depend heavily on what the people asking already believe (Card, 2017). This analysis responds in two ways. It requires evidence at every step, so an answer cannot rest on belief alone, and it records a branch that the evidence did not support, so the reader can see that more than one path was tried.
The Chain
The chain runs from the observed problem to a cause the organization controls. Each row gives the question, the answer and the evidence that confirmed it before the next question was asked.
Table 1
Five Whys Chain for Lost Long-Lead Slots, With Evidence (Illustrative)
| Why? | Answer | Evidence |
|---|---|---|
| 1. Why are slots booked 43+ days ahead going unused? | Most end as no-shows; the rest as late cancellations not refilled. | Report pull, 12 months: of 318 lost long-lead slots, 223 (70%) were no-shows and 95 (30%) late cancellations. |
| 2. Why do those patients not come or cancel late? | By the session day, many had forgotten the date, had already been seen elsewhere, or no longer needed the visit. | Sample of 60 scheduler call-back notes: 25 forgot or were unsure of the date, 16 seen elsewhere or symptoms resolved, 11 had a conflict, 8 unreachable. |
| 3. Why are so many visits booked so far ahead? | Each referral is booked into the next open slot as soon as it arrives, so early session days fill and later referrals land further out. | Referral log: median 3 days from referral to booking; median 48 days from booking to visit for orthopedics, 31 for cardiology. |
| 4. Why is every referral booked as soon as it arrives? | Booking closes the referral in the log, and the scheduler, who also covers registration, books when there is a free moment rather than on a schedule. | Interview with the scheduler (by role); referral log shows bookings scattered across registration lulls. |
| 5. Why has that practice never changed? | Nobody chose it; it was the default when the clinic opened, there is no written booking policy and no one reviews kept slots by lead time. | No booking policy on file; outpatient manager's monthly report shows booked and arrived counts only. |
Reading the Chain
The first two answers describe what patients do, and they are important evidence, but they are not where the chain should stop. A chain that ends at patients forgetting has found a symptom that no organization can change directly. The third answer moves from patient behavior to the clinic's own process: visits are booked far ahead because of how referrals are handled, not because patients ask for distant dates. The fourth explains the booking practice in terms of the scheduler's divided job and the referral log's design. The fifth reaches a condition the hospital owns: an unwritten booking rule that nobody chose deliberately and nobody measures. That is consistent with work on advanced access, which treated long waits as a product of scheduling rules that clinics can redesign rather than as a fixed feature of demand (Murray & Berwick, 2003).
The second step also connects to the literature. A systematic review found long lead time to be one of the factors most often linked to missed appointments (Dantas et al., 2018), and the reasons in the call-back notes, forgetting a date and having been seen elsewhere, are the reasons one would expect to grow as the wait grows.
The Abandoned Branch: Transport
The first explanation offered by several staff was transport: the clinic serves two rural counties, and many patients are older adults who may not drive. If transport were the main cause, lost rates would rise with distance. They barely do. Patients living under 15 miles from the hospital lost 24.0% of their slots, those living 15 to 30 miles away lost 25.0% and those over 30 miles lost 27.0%. Only 108 of the 480 lost slots belonged to patients living more than 30 miles away. In the 60 call-back notes, only 4 patients mentioned a ride as the reason, all of them within the conflict category.
Transport may matter for some patients, and the call-back notes are a small sample, but the data does not support it as the main cause of the loss. The branch is therefore abandoned here, and any change built mainly around transport would contradict this analysis.
The Root Cause
The root cause is a booking rule: every referral is booked into the next available slot on arrival, with no limit on how far ahead a visit can be booked and no list of patients who could fill a slot at short notice. Under that rule, the clinic's monthly session pattern guarantees that a large share of visits are booked six weeks or more ahead, and those are the visits that are lost. The rule persists because it was never written down or reviewed, and because the clinic's monthly report does not show lost slots by lead time.
This is not a finding about the scheduler, who follows the only practice the clinic has ever had while also covering registration. Directing the change at a person would leave the rule in place for the next one. The rule itself is something the outpatient manager can change, and the next weeks will look at how a peer hospital handles the same problem and what a different rule would look like.
References
Card, A. J. (2017). The problem with 5 whys. BMJ Quality & Safety, 26(8), 671-677. https://doi.org/10.1136/bmjqs-2016-005849
Dantas, L. F., Fleck, J. L., Cyrino Oliveira, F. L., & Hamacher, S. (2018). No-shows in appointment scheduling: A systematic literature review. Health Policy, 122(4), 412-421. https://doi.org/10.1016/j.healthpol.2018.02.002
Murray, M., & Berwick, D. M. (2003). Advanced access: Reducing waiting and delays in primary care. JAMA, 289(8), 1035-1040. https://doi.org/10.1001/jama.289.8.1035
Reading the HLTH 6882 Week 4 instructions
The root cause assignment traces why a measured problem happens, using evidence. Start from the specific stratum your gap analysis identified rather than the whole problem. Ask why, answer, and check the answer against records, a count or a documented interview before asking the next why. Show the evidence beside each answer. Continue until you reach a rule, process or design that the organization itself controls, rather than stopping at a patient behavior. Record any branch you tested and rejected, with the data that rejected it. Acknowledge the method's limits. State the root cause as a condition, not as a person to blame, and avoid naming individuals. Keep the chain readable from top to bottom.
How the HLTH 6882 Week 4 example is put together
The introduction names the long-lead stratum and the evidence rule. A short section cites Card on the weaknesses of five whys and explains the response. Table 1 presents five questions, answers and evidence, from a 12-month report pull to call-back notes, the referral log, a scheduler interview and the absence of a written policy. A section reads the chain, explaining why it does not stop at patient forgetfulness and linking to Dantas and colleagues and Murray and Berwick. The transport branch is tested against distance data and call-back reasons and abandoned. The final section states the booking rule as the root cause and explains why the scheduler is not to blame.
Reading the HLTH 6882 Week 4 rubric
Credit follows the evidence column: a chain in which every answer is asserted reads as opinion arranged vertically. Stopping too early costs the most; a chain ending at patient forgetfulness has found a symptom nobody can change, while one ending at a booking rule has found something a manager owns. A rejected branch earns more than its length suggests, because it shows willingness to lose an attractive explanation. Blame directed at a named role pulls the analysis toward a people problem and loses points. Acknowledging the method's limits shows maturity. Clear presentation of the chain, accurate figures and a root cause stated as a controllable condition complete what is assessed.
HLTH 6882 Week 4 help from the desk
Root cause chains often stop at the second why, such as patients forget, and propose reminders. Others assert every answer from experience without checking. Some blame a person. Start with the specific problem your data revealed, write the first why, then go to the records before writing the answer. If you cannot check an answer, mark it as unconfirmed and look for another source. Stop only when the answer names something a manager could change by deciding to. Test any popular explanation against your data and keep the rejected branch in the paper. We can build a root cause analysis from your organization's records with evidence beside every step.
Get a HLTH 6882 Week 4 example written to your instructions
Include the gap findings from Week 3, the prompt and the rubric; the chain opens where your data concentrate and tests every rung. A first analysis is free and arrives in 24 to 48 hours. The scheduler interviewed here is a composite role, and no conversation with real staff sits behind any rung.
More HLTH 6882 papers and graduate health administration program samples
- HLTH 6882 Week 1: Healthcare Organization Profile
- HLTH 6882 Week 2: Performance Definition Post
- HLTH 6882 Week 3: Performance Gap Analysis Paper
- HLTH 6882 Week 5: Peer Benchmark Comparison Paper
- HLTH 6882 Week 6: Healthcare Change Proposal Paper
- HLTH 6882 Week 7: Improvement Pilot Design Memo
- HLTH 6882 Week 8: Improvement Business Case Paper
- HLTH 6882 Week 9: Change Resistance Peer Reply
- HLTH 6882 Week 10: Improvement Measurement Plan
- HLTH 6882 Week 11: Final Improvement Proposal Paper
- HLTH 6100 Week 4: Mitigation Funding Position Paper
- HLTH 6880 Week 4: Social Enterprise Business Model
- HLTH 6200 Week 4: Flood Likelihood Note
- HLTH 6840 Week 4: Policy Criteria Memo
HLTH 6882 Week 4 questions, answered
Where can I find a free HLTH 6882 Week 4 sample paper?
The five whys chain and its evidence table are posted on this page without charge.
What root cause does the HLTH 6882 Week 4 analysis find?
An unwritten rule that books every referral into the next open slot on arrival, so many visits land six weeks or more ahead.
What evidence supports each step?
A report pull, a sample of call-back notes, the referral log, a scheduler interview and the absence of a written booking policy.
Which branch is abandoned?
Transport, because lost rates barely change with distance and few call-back notes mention rides.
Why does the analysis avoid blaming the scheduler?
The scheduler follows the only practice the clinic has had; blaming a person would leave the rule in place.