Adverse Event RCA Template & Evidence Collection Form

Welcome — use this template to run consistent, timely, evidence‑based RCAs

This template helps teams turn adverse events into lasting safety improvements. It is designed for quick adoption: clear roles, sensible timelines, field‑tested interview prompts, an evidence checklist you can use during chart reviews and device log pulls, and an action tracker that makes ownership and verification explicit. Keep the focus on systems and learning — not blaming individuals.

At a glance: purpose and core commitments

• Purpose: Identify system‑level causes and produce assignable, time‑bound corrective actions with verification steps.
• Core commitments: complete initial fact collection quickly, protect psychological safety, gather evidence before conclusions, name owners for every action, monitor effectiveness.
• Timeline expectations: initial event review within 24 hours; decision whether to launch full RCA within 48–72 hours; full RCA team meeting(s) and preliminary corrective actions within 7–14 days depending on complexity.

Roles and responsibilities (assign at kickoff)

• RCA Facilitator (owner of the process): schedules meetings, guides discussion, keeps focus on systems, protects psychological safety.
• Incident Owner / Local Manager: provides context, implements immediate containment actions, coordinates local resources.
• Clinical SME(s): subject matter experts to interpret clinical decisions and workflows.
• Scribe / Documentation Lead: captures timeline, evidence, contributory factors, and agreed actions in this template.
• Patient/Family Liaison: maintains communication with the patient/family and advises on messaging.
• Quality & Safety Sponsor: ensures actions are resourced and tracked.

Event timeline (use this as the working chronology)

Document observable facts only. Include date/time, location, people present, key decisions, actions taken, times of transfer/medication/alarms, and sources of evidence.

1. Event summary — short plain‑language description (one or two sentences).
2. Chronology (timestamped):
   • HH:MM — Description — Source (chart, monitor log, staff interview)
   • Example: 09:12 — IV infiltration noted; peripheral IV removed — nursing note
3. Key outcomes: patient harm level, transfers, procedures, immediate mitigation performed.

Contributory factors framework

Use categories to organize root causes. Resist premature single‑cause answers — most events have multiple contributing factors.

• People & communication: handoffs, situational awareness, staffing, supervision, training.
• Process & workflow: standard work availability, complexity, ambiguous responsibilities.
• Technology & devices: design, alarms, EMR displays, device logs.
• Environment: layout, lighting, interruptions, supplies.
• Organizational & system factors: policies, staffing models, scheduling, culture, incentives.
• Patient factors: co‑morbidities, language, mobility, cognitive status.

For each category, list observable evidence and then ask 'why' iteratively to surface deeper system drivers.

Evidence checklist (use to guide rapid data collection)

Mark items as Collected, Not applicable, or Pending. Record source, reviewer, and date.

• Clinical chart / progress notes — include timestamps and signature lines.
• Medication administration record (MAR) or eMAR extracts.
• Device logs (infusion pumps, monitors) and alarm histories.
• Orders and reconciliations (paper or electronic).
• Transfer and handoff documentation (SBAR, handoff tools).
• Staff interviews (date/time, role, summary of relevant statements).
• Patient / family interview (consent, summary, wishes regarding disclosure).
• Staffing records and assignments at time of event.
• Relevant policies, protocols, checklists, and care pathways current at event time.
• Environment photos or sketches (room layout, equipment placement).
• Training and competency records for staff involved.
• Previous incidents, audits, or complaints involving similar processes.

Interview guide (suggested prompts by role)

Use open questions; begin with a non‑judgmental statement about purpose. Example: 'We want to understand what happened so we can make the system safer.'

Frontline staff

• Can you describe, in your own words, what happened and what you noticed first?
• What were you doing just before the event? Were there interruptions or competing demands?
• Were there any tools, information, or supplies you needed that weren’t available?
• What do you think contributed to the event — process, tools, communication?

Clinical lead / decision maker

• What options were considered and why was a particular decision made?
• Were there conflicting guidelines, or unclear ownership of steps?

Patient / family (if appropriate)

• What is most important for us to know from your perspective?
• What information would you like about what happened and the follow up?

Action plan template (record every action here)

For each corrective action, capture these fields. Use short, specific language.

• Action: What will change? (e.g., revise order set, implement double‑check)
• Rationale: Which contributory factor does this address?
• Owner: named person or role responsible for completion
• Due date: realistic date for completion
• Verification: how will effectiveness be measured (what metric, sample size, timeframe)?
• Follow‑up: date for outcome review and closure
• Status: Not started / In progress / Complete / Deferred

Example action entry:

• Action: Update EMR medication display to show dose units prominently.
• Rationale: design contributed to misreading of dose.
• Owner: IT Clinical Applications Lead.
• Due date: 2026‑09‑30.
• Verification: user acceptance test with 10 clinicians; monitor medication error reports for 90 days.
• Follow‑up: review results on 2026‑10‑31.

Monitoring plan and closure criteria

Define measurable indicators tied to each action and a minimum review period before closure. Typical verification approaches include audits, direct observation, chart reviews, device log sampling, and staff surveys.

• Specify who will run the measurement, frequency, and acceptance thresholds.
• Closure requires evidence that the action was implemented and a predefined improvement or sustainment for the agreed period.

Sample family communication language

Be honest, compassionate, and non‑speculative. Adapt to local disclosure policy and legal guidance.

"We are very sorry this happened. Our first priority is your family’s well‑being. We are committed to understanding how this occurred and taking steps to prevent it from happening again. We will share what we learn and what we change. Would you like to meet with the care team to discuss this further?"

Document what was said, who said it, and the family’s questions or requests.

Immediate checklist for the first 24 hours

• Ensure patient safety and appropriate clinical care (stabilize, escalate as needed).
• Preserve evidence (charts, device data, samples) and secure access logs.
• Notify designated safety lead and patient/family liaison per policy.
• Assign facilitator and scribe; schedule initial RCA decision meeting.

Documentation & handover

Keep a single living RCA document (this template) updated. At each handoff, note status, outstanding evidence required, and next steps. Attach interview summaries and evidence sources with reviewer initials and dates.

Tips to avoid common pitfalls

• Avoid blaming individuals; ask 'what allowed this to happen' rather than 'who made the mistake'.
• Do not close an RCA on assumptions — collect corroborating evidence first.
• Prioritize a few meaningful actions over many low‑impact changes.
• Make ownership and verification explicit for every action.

Where this template fits in a toolkit

This template can be bundled with incident intake forms, action trackers, audit schedules, and board‑level safety reports so learning cycles are visible and durable across the organization.

Use this template as a starting point. Tailor wording, timelines, and verification thresholds to your organization’s size, risk profile, and regulatory requirements.