Applying Root Cause Analysis for Inspection Findings in Clinical Trials

Why Root Cause Analysis Matters in Regulatory Inspections

Root Cause Analysis (RCA) is the foundational step in responding to inspection findings. Regulatory authorities like the FDA, EMA, MHRA, and PMDA expect a structured RCA to accompany Corrective and Preventive Action (CAPA) plans. An RCA that fails to identify the real cause of a deviation or noncompliance often results in ineffective CAPA—and repeated observations in future audits.

The goal of RCA is not just to correct what went wrong, but to understand why it happened. It transforms audit responses from reactive fixes into systemic improvements, strengthening trial quality and regulatory credibility.

Key Principles of Effective RCA

Before exploring the tools and techniques, it is essential to understand the guiding principles of RCA:

• Fact-Based: Decisions should rely on objective evidence, not assumptions or opinions.
• System-Oriented: Focus on process and system flaws rather than individual blame.
• Repeatable: RCA methodology should be consistent across observations and auditable.
• Traceable: Every step should be documented clearly to support the CAPA plan.

Common Triggers Requiring RCA

In clinical research, the following inspection findings typically trigger a mandatory RCA process:

• Improper informed consent procedures
• Protocol deviations or violations
• Incomplete or missing source documentation
• Drug accountability issues
• Late or missed safety reporting (SAE/ SUSAR)
• GCP non-compliance identified in audit trails

Popular RCA Tools in Clinical Trial Settings

Several industry-standard tools are used for RCA. Here’s how each can be applied in clinical trial contexts:

1. 5 Whys Technique

This simple yet effective method involves asking “Why?” five times (or as many times as needed) to drill down to the root of the problem.

Example:

• Why was the SAE reported late? – The site coordinator submitted it after the deadline.
• Why did the coordinator delay the report? – They weren’t aware of the 24-hour reporting requirement.
• Why weren’t they aware? – They didn’t receive training on the new SOP update.
• Why didn’t they receive training? – The SOP distribution tracker wasn’t updated.
• Why wasn’t it updated? – The document control system lacks automated alerts.

2. Fishbone (Ishikawa) Diagram

This tool helps visualize contributing factors by organizing them into categories such as People, Process, Systems, Materials, and Environment.

Use case: Unblinded data accessed during a blinded study due to misconfigured system access. Categories might include:

• People: Staff unaware of user role restrictions
• Process: No SOP for blinded access management
• Systems: EDC lacked access restriction by default
• Training: No role-based training provided

Documenting RCA Results

All RCA efforts must be thoroughly documented. A sample RCA report format includes:

• Observation summary (as per inspection)
• Date RCA was performed
• Team members involved
• RCA method used (5 Whys, Fishbone, etc.)
• Identified root cause(s)
• Linkage to corresponding CAPA items

Case Study: RCA for Protocol Deviation in Subject Visit Windows

Observation: Several subject visits were conducted outside of protocol-defined visit windows without documentation or PI justification.

RCA Outcome:

• Study calendar had calculation errors for visit windows
• CRAs failed to flag visit discrepancies during monitoring
• Site staff were unaware they needed PI notes for deviations

Resulting CAPA: Correction of calendar template, CRA re-training on monitoring logs, updated SOP for visit deviation management.

Integrating RCA with CAPA Plans

Each root cause must map to at least one corrective and one preventive action. Avoid generic actions that don’t address the true cause.

Example:

Tips for Effective RCA During Inspections

• Involve cross-functional teams to get full context
• Don’t rush—take time to validate each level of reasoning
• Use real documentation and data to support conclusions
• Avoid surface-level conclusions like “human error” without deeper exploration

Conclusion: RCA as a Driver of Quality, Not Just Compliance

Root Cause Analysis should not be viewed as a box-checking exercise. When applied correctly, it uncovers hidden vulnerabilities in clinical trial processes and enables long-term improvements. By institutionalizing robust RCA practices, sponsors and sites not only address inspection findings effectively but also build a culture of quality that stands up to regulatory scrutiny.