Nursing root cause analysis should explain how an adverse event, near miss or recurring safety problem developed within a work system. A strong analysis does not stop at the last person involved. It reconstructs what happened, tests contributory factors and identifies changes that could make safer action more reliable.
For UK nursing work, this systems perspective is especially important because the NHS Patient Safety Incident Response Framework (PSIRF) emphasises proportionate, system-based learning rather than assuming that every event has one identifiable root cause (NHS England, 2022b).
What a strong analysis needs
- A neutral, clearly bounded safety event.
- A verified chronology separating facts from assumptions.
- Comparison with the expected care process.
- Analysis of interacting patient, task, team, technology, environment and organisational factors.
- Causal claims supported by evidence rather than hindsight.
- Safety actions linked directly to modifiable contributory factors.
- Named measures for implementation and unintended effects.
- Confidentiality and governance appropriate to the case.
Root cause analysis is a systems-learning method
The AHRQ Patient Safety Network describes root cause analysis as a structured method for examining serious adverse events and identifying underlying system problems rather than stopping at individual mistakes (Agency for Healthcare Research and Quality [AHRQ], 2019).
That distinction matters in nursing. A delayed time-critical medicine might involve an interrupted medicine round, an unclear electronic alert, pharmacy delay, incomplete handover and competing deterioration calls. The nurse’s action remains part of the event, but it is not necessarily a sufficient explanation.
Use terms such as contributory factors or system factors when several conditions interacted. Do not force the case into one final “root” if the evidence supports a more complex explanation.
Recognise the limits of traditional RCA
Traditional RCA can imply a straight causal chain ending in one root. Healthcare often behaves differently: staff adapt continuously to changing demand, incomplete information, limited resources and competing priorities.
In the UK, PSIRF replaced the Serious Incident Framework and supports a broader set of proportionate patient-safety learning responses (NHS England, 2022b). A university brief may still ask specifically for RCA, but the paper can demonstrate critical understanding by explaining this contemporary context.
A fishbone diagram or five-whys exercise can organise thinking, but neither tool proves causation. Triangulate them with the chronology, records, relevant policy and accounts from people involved where authorised.
1. Define the event neutrally
Describe what happened without embedding blame or an unsupported explanation. Include the relevant care process, timing, setting and outcome.
A prescribed time-critical medicine was administered 95 minutes after its scheduled time during an evening shift.
This establishes the event without deciding that the delay occurred because someone “forgot,” was “careless” or failed to follow policy.
2. Build a verified chronology
Place the relevant events and conditions in time order. Distinguish:
- confirmed facts;
- information that is missing;
- reasonable but unverified explanations; and
- later interpretations.
A chronology may reveal where information was unavailable, responsibility changed, competing work emerged or escalation became delayed.
3. Define the expected process
Compare the event with relevant professional standards, local policy, clinical guidance, equipment instructions or an approved pathway.
Do not assume that a written policy describes what was realistically achievable under the conditions present. The gap between work as imagined and work as done may itself be a useful finding.
4. Map contributory factors
| Domain | Question | Example |
|---|---|---|
| Patient | Did acuity, communication or treatment complexity affect the process? | Rapid deterioration required urgent reassessment. |
| Task | Was the task clear, workable and appropriately prioritised? | Time-critical status was not visually prominent. |
| Team | How did handover, delegation or hierarchy influence action? | Responsibility was not reassigned during escalation. |
| Technology/tools | Did equipment or software support safe action? | An urgent alert resembled routine notifications. |
| Environment | Did interruptions, layout, noise or workload matter? | The medicine round was repeatedly interrupted. |
| Organisation | Did staffing, supply or governance influence the event? | No backup process covered competing urgent work. |
Not every domain has to be included in every incident. Prioritise the factors supported by the available evidence.
5. Test rather than assume causation
For every proposed factor, ask:
- What evidence supports it?
- Did it occur before the outcome?
- How could it plausibly have influenced the event?
- Is there contradictory evidence?
- Would changing this condition reasonably reduce recurrence?
Labels such as “poor communication” or “staff error” are conclusions unless the analysis specifies what information or action was missing, when it was needed and how that influenced the event.
Use five whys carefully
The five-whys technique can expose deeper conditions beneath an immediate failure, but healthcare events often branch rather than follow one straight line.
If missed observations appear connected to workload, unclear delegation and an interface problem, selecting only one branch would oversimplify the case. Stop asking “why” when the answer becomes speculative or too distant from the evidence to guide action.
“Staff did not follow policy” should not be the final explanatory step. Ask why the expected process was difficult, confusing or less likely under the conditions present.
Use fishbone diagrams as maps, not proof
A fishbone diagram can help organise possible factors and prevent the loudest explanation from dominating. However, it does not show timing well, can imply that every branch has equal importance and may become a brainstorming list without evidence testing.
Use it alongside the chronology and narrative analysis. Do not put “human error” at the end of every branch; examine the conditions that made the action more likely.
6. Design stronger safety actions
Weak actions often tell staff to be more careful, repeat training or read a reminder. These may contribute to a wider intervention, but they depend heavily on memory and attention.
Stronger actions change the conditions in which work occurs, for example:
- simplifying or standardising a process;
- redesigning an electronic alert;
- changing equipment location;
- creating a reliable backup workflow;
- reducing unnecessary task complexity; or
- adding a forcing or constraint mechanism where appropriate.
Every recommendation should address a factor supported by the analysis rather than a generic aspiration.
The NHS patient-safety learning response toolkit provides system-based methods and guidance for developing safety actions (NHS England, 2022c).
7. Define implementation and evaluation
For each action, identify:
- a responsible owner;
- implementation timing;
- a process measure;
- an outcome measure; and
- a balancing measure for possible unintended effects.
For example, a redesigned medicine alert might be evaluated through the proportion of time-critical medicines administered within the required window, staff interaction with the alert and any increase in inappropriate interruptions or alert burden.
Without follow-up, the RCA remains an investigation report rather than a safety-improvement process.
Involve patients, families and staff compassionately
People affected by an incident may hold information that is not visible in the clinical record. NHS England guidance emphasises compassionate involvement of patients, families and staff following patient-safety incidents (NHS England, 2022a).
Academic analysis should recognise this human dimension without claiming interviews or involvement that did not occur. If the assessment uses a fictional or supplied case, analyse only the information provided.
Protect confidentiality and governance
Do not copy identifiable clinical records into an academic assignment. Remove names, record numbers, exact locations and unusual details that could identify a patient, family member or staff member.
Distinguish an educational analysis from a formal organisational investigation. Students should not conduct a real incident inquiry without appropriate authority, governance and supervision.
UK and international context
RCA terminology remains common internationally. US assignments may refer to sentinel events, RCA and corrective actions. UK assignments should recognise PSIRF and proportionate learning responses. Other jurisdictions may use different regulatory or health-system frameworks.
Follow the framework required by the brief and cite the authority relevant to that jurisdiction. International evidence can still be used, but transferability should be considered rather than simply changing country names.
Common RCA mistakes
- Blaming the practitioner closest to the outcome.
- Beginning with a preferred explanation.
- Using one evidence source only.
- Calling policy non-compliance the root cause.
- Forcing one root when several factors interacted.
- Ignoring patient, family or staff perspectives.
- Using training as the only recommendation.
- Failing to define how actions will be measured.
- Inventing incident evidence to fill gaps in a case.
Suggested paper structure
- Introduction: method, event and purpose.
- Anonymised event description and scope.
- Expected care process.
- Verified chronology.
- Contributory-factor analysis.
- Critical evaluation of the analytical tools.
- Priority safety actions.
- Implementation and measurement.
- Limitations and governance.
- Conclusion.
If the brief also assesses leadership, ethics or professional standards, integrate those requirements into the relevant analysis rather than adding disconnected sections.
Final RCA checklist
- The event statement is neutral and specific.
- The chronology separates facts, assumptions and gaps.
- The expected process is supported by appropriate standards or guidance.
- Contributory factors cover the relevant work-system domains.
- Causal claims are supported and alternative explanations considered.
- Recommendations address supported, modifiable factors.
- System redesign is considered before relying on reminders or training alone.
- Every action has ownership and measurement.
- Confidentiality is protected.
- The paper accurately distinguishes RCA from current UK PSIRF practice where relevant.
Frequently asked questions
Is root cause analysis still used in nursing?
Yes. RCA remains widely used and discussed internationally. In current UK NHS practice, however, PSIRF supports a broader range of system-based learning responses rather than treating single-root RCA as the default approach.
What is the difference between RCA and quality improvement?
RCA examines why a safety event occurred and identifies contributory conditions. Quality improvement tests changes over time. An RCA can generate actions that later become an improvement project.
Can five whys be used on its own?
It may help with a simple problem, but complex healthcare incidents usually benefit from a chronology and wider systems framework as well.
Should individual error be mentioned?
Yes, when relevant. A systems approach does not remove professional accountability; it avoids pretending that the final individual action is always a complete causal explanation.
Project-specific support
If an existing patient-safety paper needs a clearer chronology, systems analysis or action plan, use the support-process guide or send the brief through the contact page. The site’s student feedback and review policy explains how feedback may be handled; it is not presented as a page of verified testimonials.
Related Nursing Guides
- Fishbone Diagram Healthcare Example: A Nursing QI Guide
- How to Diagnose and Fix DNP Project Manuscript Problems
- How to Write a Nursing Quality Improvement Project: 12 Steps
Conclusion
Nursing root cause analysis is most defensible when it explains a safety event through interacting work-system conditions rather than one convenient cause. Build a verified chronology, test contributory factors, acknowledge uncertainty and connect measurable safety actions directly to the evidence. In UK work, recognise the contemporary PSIRF context and keep conclusions proportionate to the information actually available.
References
- Agency for Healthcare Research and Quality. (2019). Root cause analysis. PSNet. https://psnet.ahrq.gov/primer/root-cause-analysis
- NHS England. (2022a). Engaging and involving patients, families and staff following a patient safety incident. https://www.england.nhs.uk/patient-safety/patient-safety-insight/incident-response-framework/engaging-and-involving-patients-families-and-staff-following-a-patient-safety-incident/
- NHS England. (2022b). Patient Safety Incident Response Framework. https://www.england.nhs.uk/long-read/patient-safety-incident-response-framework/
- NHS England. (2022c). Patient safety learning response toolkit. https://www.england.nhs.uk/publication/patient-safety-learning-response-toolkit/
