Adverse Event RCA Packet: Evidence Collection, Timeline, and Action Tracker

Purpose and scope

This packet helps clinical teams run consistent, evidence-based root cause analyses (RCAs) after an adverse event. It focuses on collecting timely evidence, conducting humane interviews, mapping causes to systems-level factors, and producing assignable, time‑bound corrective actions with clear owners and verifiable follow-up so improvements persist.

Quick start: RCA initiation checklist & timeline expectations

Use this checklist immediately after an event to preserve evidence, protect patients and staff, and launch an RCA that will lead to meaningful system change.

• Immediate safety: stabilize patient and secure scene (minutes).
• Notify safety team/manager and document initial facts (within 2–24 hours).
• Preserve evidence (EHR snapshots, device logs, specimens, medication packaging) — collect within 24–72 hours.
• Assemble RCA team and schedule first analysis session (within 48–72 hours of notification).
• Conduct interviews with witnesses and involved staff (preferably within 3–7 days; earlier if memory/availability risk exists).
• Complete cause mapping and draft action recommendations (within 7–14 days depending on complexity).
• Assign owners and due dates for actions; publish summary to leadership and affected teams (within 14 days).
• Implement high‑priority actions quickly (target within 30 days). Schedule follow-up audits at 30, 90, and 180 days.

Roles & responsibilities

• RCA Lead: schedules meetings, manages timeline, ensures evidence collection, guides analysis, and coordinates communication.
• Scribe/Analyst: documents timeline, evidence, interviews, and cause map in a shareable record.
• Subject Matter Experts (SMEs): clinical, pharmacy, biomedical engineering, IT, or others providing technical context.
• Frontline representatives: staff who were directly involved or perform the work day-to-day.
• Patient/family liaison: manages compassionate disclosure and coordinates information shared with patients/families.
• Leadership representative: ensures resources for recommended changes and tracks implementation.

Evidence collection checklist (use as a template)

Collect objective, time-stamped evidence first. Preserve originals or immutable exports where possible.

• EHR snapshots (relevant notes, medication administration records, order timestamps).
• Medication and supply logs (batch/lot numbers, pharmacy verification).
• Device logs and downloads (ventilators, infusion pumps, monitors).
• Monitor and alarm logs, telemetry recordings.
• Lab results and imaging with timestamps.
• Staff assignment rosters and staffing levels at time of event.
• Shift handoff notes and transfer records.
• Policy, protocol, and standard work documents relevant to the event.
• Environmental conditions (room setup photos, lighting, signage, supplies placement).
• Video footage if available (ensure legal/HR processes for review).
• Code blue / resuscitation records and team debrief notes.
• Relevant communications (pages, secure messages, phone logs).

Interview guides

Use a conversational, non‑accusatory tone. Explain purpose (learning, system improvement, just culture). Ask open questions, clarify timelines, and avoid asking for speculation without evidence.

General tips

• Begin by explaining why the interview is happening and how information will be used.
• Ask the person to describe what they recall in their own words.
• Use neutral probes: "What did you notice next?" "What options were available to you at that time?"
• Clarify timings: use documented timestamps to anchor memory where possible.
• Document verbatim quotes where relevant and ask for clarification rather than assumptions.

Sample questions for involved staff

1. Tell me, in your own words, what happened from the moment you became aware of the situation.
2. What task were you performing and what was the expected outcome?
3. What information, tools, or support did you have available? Were there constraints?
4. Were any policies, checklists, or standard steps skipped or not followed? If so, why?
5. Were there recent changes (equipment, staffing, process, IT) that might have influenced the event?
6. Is there anything else you think is important that we haven't asked?

Sample questions for witnesses, patients, or families

1. Can you tell me what you saw or experienced?
2. When did you first become concerned and what did you do next?
3. Did anyone explain what happened afterward? If so, what was said?

Cause‑map template and guided prompts

Build a visual map beginning with a concise event statement and a short timeline. Then add causal branches that identify active failures and latent system conditions.

1. Event statement — one clear sentence describing what happened, when, and where.
2. Timeline — list time-stamped actions and observations (use evidence to anchor times).
3. Direct causes / immediate contributing factors — what directly produced the harmful outcome?
4. Contributing conditions — staffing levels, workload, equipment state, workspace design, training, communication breakdowns, IT/UI issues.
5. Latent/systemic causes — policy gaps, procurement choices, supervision, cultural incentives, or organizational priorities that allowed the conditions to exist.
6. Checks and defenses — what barriers existed and why they failed.

Use prompts such as: "Why did that happen?" (repeat to drill down), "What allowed that to exist?", "How often might this occur under current conditions?" Label each causal factor as a skill‑based error, rule‑based error, knowledge issue, design problem, or system/policy gap to guide remedies.

Action recommendation builder (template)

Prefer system-level fixes. Use the hierarchy of controls to prioritize higher-reliability solutions.

Risk‑reduction hierarchy (preferred to least preferred)

1. Elimination/substitution (remove the hazard)
2. Engineering controls (design changes, forcing functions)
3. Administrative controls (standard work, checklists, scheduling)
4. Training/education (supports but does not substitute for system fixes)

Use the table below to document recommended actions:

Prioritization guidance

Prioritize recommendations that combine high expected risk reduction with feasible effort and clear ownership. Use a simple impact vs effort grid to sort actions into:

• Quick wins (high impact, low effort) — implement immediately.
• Strategic projects (high impact, high effort) — require leadership support and resourcing.
• Low-priority (low impact) — track but avoid wasting scarce implementation capacity.

Communication checklist

Transparent, timely, and compassionate communication is essential. Coordinate messages through the patient/family liaison and leadership.

• Immediate internal notification to unit leadership and safety team.
• Disclosure to patient/family: offer explanation, apology, and next steps; document the conversation.
• Internal debrief with involved staff (focus on learning and support).
• Leadership summary with recommended actions and resource needs.
• Regulatory reporting as required (document timing and recipient).

Follow-up audit & sustainment tracker

Document verification activities and sustainment checks so fixes become part of daily work rather than temporary patches.

Recommended follow-up schedule: 30, 90 and 180 days after implementation for high-impact actions; adjust frequency based on risk and results.

Just‑culture guidance

RCA should distinguish between human error, at-risk behavior, and reckless behavior. Focus on system fixes unless evidence shows reckless disregard. Use the RCA to understand how systems and incentives shape behavior and to design safer defaults.

Usage notes & practical tips

• Document everything: timelines, evidence sources, interview notes, and decisions. Records support learning and accountability.
• Prefer concrete, measurable actions with clear owners and verification methods.
• Where possible, pilot system changes on a small scale and measure before broader rollout.
• Include frontline staff in solution design to improve usability and uptake.
• Keep communication simple and empathetic for patients and families; involve risk and legal as required.

Resources & templates

Attach or link the following artifacts to each RCA record:

• Evidence collection log (with timestamps and file references).
• Interview notes and consent/log of who was interviewed.
• Completed cause map (visual diagram) and timeline document.
• Action tracker (spreadsheet or table) with owners and verification methods.
• Communication log for patient/family and internal announcements.

Closing

This packet is a practical starting point—adapt timelines and templates to your facility and regulatory context. The aim is not to punish individuals but to learn, fix systems that allow harm, and reduce recurrence.