Root Cause Analysis (RCA) for ASCs

When an RCA is required

An RCA is expected after any sentinel event and is best practice for any significant adverse event or recurring near miss. Joint Commission requires "a thorough and credible" RCA and action plan within 45 calendar days of a sentinel event. CMS expects equivalent rigor through QAPI. The AHRQ and IHI publish methodology guidance widely used in healthcare RCAs.

Principles

• System-focused. Root causes are properties of the system, not the person at the sharp end.
• Multidisciplinary. The team includes the people closest to the work.
• Confidential. Conducted under peer-review privilege where state law permits.
• Time-boxed. Initial findings within 14 days; final report within 45.
• Actionable. Every root cause yields at least one strong action.

Step 1 — Define the event

A precise, factual statement: "On 2026-03-04 at 09:42, during a scheduled left knee arthroscopy on patient X, the surgical site was prepped on the right knee. The error was identified during time-out and corrected before incision." No causes, no opinions — the facts only.

Step 2 — Reconstruct the timeline

Build a minute-by-minute timeline from chart entries, logs, the OR record, witness interviews. Distinguish what was recorded from what was recalled . The act of building the timeline almost always exposes the contributing factors.

Step 3 — Identify contributing factors

Two tools cover most ASC events:

5 Whys

Ask "why" iteratively until you reach a system-level answer.

Fishbone (Ishikawa)

Group contributing factors under standard categories: People , Process , Equipment , Environment , Materials , Communication .

Step 4 — Determine root causes

A root cause is a finding the system itself owns. "The nurse forgot" is not a root cause; "the time-out checklist did not include surgical site verification with the consent form" is.

Step 5 — Generate corrective actions

Each root cause must produce at least one action. Each action must be specific, measurable, owned, and dated. Read: corrective & preventive action .

Action strength hierarchy

An action plan composed entirely of training is a sign the team did not reach the system level.

Worked example: medication error

Event: A patient received a 10x dose of an opioid in PACU. Naloxone was administered, the patient recovered.

Contributing factors (fishbone): Materials — multidose vial of higher concentration kept in same bin as low-concentration pre-fills; Process — bin labeled by drug, not by concentration; Communication — no alert when pre-fills depleted.

Root causes: Storage configuration permitted look-alike substitution. Inventory system did not flag depletion.

Actions (strong/intermediate): Remove higher-concentration vial from PACU. Auto-alert on pre-fill par level breach. Standardize PACU opioid concentration to a single SKU.

Follow-up measure: Zero look-alike opioid storage events for 6 months; weekly par-level audit pulls into QAPI.

Common pitfalls

• Stopping at "human error" or "did not follow policy."
• Action plan composed entirely of "re-education."
• No measure of effectiveness.
• RCA team without a member who actually does the work.
• Findings that name an individual rather than a process.

FAQ