Skip to main content
v2026.11,986 entries · CC-BY 4.0

Direct comparison

Apparent Cause vs Root Cause Analysis

ACA suits lower-harm events with an obvious cause; RCA is for sentinel events. The severity triage that decides which one, and what ACA skips.

Written and maintained by CASRAI Editorial Board

Last updated

How do Apparent Cause Analysis (ACA) and Root Cause Analysis (RCA) compare side by side?

The table below compares Apparent Cause Analysis (ACA) and Root Cause Analysis (RCA) across 9 dimensions, from when it's used to escalation.

Side-by-side comparison

DimensionApparent Cause Analysis (ACA)Root Cause Analysis (RCA)
When it's usedNear misses and lower-harm events with an evident, single, uncomplicated causeSentinel events and serious/likely-to-recur events where the cause isn't obvious on its face
Who decidesAssigned by the patient safety/risk management office at intake, via a severity-based screenSame intake screen -- escalated automatically once severity crosses the sentinel/serious-harm threshold
TeamOne reviewer or a very small ad hoc team, often the unit manager or a designated facilitatorMultidisciplinary team: staff who were involved in the event plus people with no stake in the outcome
TimelineUsually completed in a single sittingA formal multi-week process -- Joint Commission guidance allows up to 45 business days for a sentinel event's analysis and corrective action plan
Investigative depthA short chain of 'why' questions to the first plausible, sufficient causeSystematic causal-factor mapping (causal-factor tree / fishbone) across contributing system conditions, not just the first explanation that fits
What it skipsMultidisciplinary team formation, interviews outside the immediate incident, formal systems-level mapping, graded action hierarchyNothing structurally -- full timeline reconstruction, systems-level causal analysis, and a graded action plan are all in scope
Corrective actionsOne or two actions tied directly to the apparent proximate causeAn action plan graded by strength (e.g., the RCA² weak/intermediate/strong hierarchy), targeting system-level contributing factors
DocumentationA brief internal review recordA formal report, often retained under the facility's patient safety work product / PSO framework where one applies
EscalationCan be escalated up to a full RCA if the review surfaces a systemic issueThe end state -- not downgraded to ACA even if the apparent cause looks simple at first

Ask CASRAI · free to try

Ask about Apparent Cause vs Root Cause Analysis

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Common questions

Common questions about Apparent Cause Analysis (ACA) vs Root Cause Analysis (RCA)

How does a hospital decide whether an event gets an ACA or a full RCA?

+

Through a standardized severity screen applied at intake by the patient safety or risk management office -- based on actual and potential harm, not on how much attention the event has drawn. Many programs use a severity-times-probability triage tool for this, an approach popularized by the VA National Center for Patient Safety's Safety Assessment Code matrix.

Does a sentinel event ever get only an apparent cause analysis?

+

No. Sentinel-event status under the Joint Commission's Sentinel Event Policy requires a comprehensive systematic analysis (RCA) and corrective action plan, regardless of how straightforward the apparent cause looks in the first hour.

Can an apparent cause analysis be escalated into a full RCA?

+

Yes, and a well-designed program builds that path in deliberately -- if the reviewer running an ACA finds a pattern or system-level issue that looks like it could recur or cause serious harm elsewhere, the event moves up to a full RCA. Escalation runs one direction: from ACA to RCA, not back down.

What's the risk of using ACA when an event actually warranted a full RCA?

+

The review stops at the first plausible cause and never surfaces the latent system conditions -- staffing, equipment, handoff process -- that a one-person review isn't built to find. The corrective action fixes the symptom, the underlying condition stays in place, and the event recurs.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →