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.

Essential Root Cause Analysis Tools for Clinical Trial Deviation Investigations

Why Root Cause Analysis Is Critical in Clinical Research

When a protocol deviation or non-compliance occurs in a clinical trial, documenting the event is only the first step. Regulatory authorities and Good Clinical Practice (GCP) guidelines require a thorough investigation into the root cause to prevent recurrence and to ensure data integrity and subject protection.

Root Cause Analysis (RCA) is the structured process of identifying why a deviation occurred, rather than just treating the symptoms. RCA plays a foundational role in the development of Corrective and Preventive Actions (CAPA), audit readiness, and continuous quality improvement.

Agencies such as the FDA and EMA expect sponsors and CROs to use RCA tools that are standardized, reproducible, and fit for purpose. Improper or shallow root cause assessments have led to warning letters, delayed submissions, and even study holds.

Key RCA Tools Used in Clinical Research

Various tools and frameworks are available for conducting structured RCA in GCP environments. Below are the most widely used:

• 5 Whys Analysis
• Fishbone (Ishikawa) Diagram
• Fault Tree Analysis (FTA)
• Failure Mode and Effects Analysis (FMEA)
• Barrier Analysis
• Cause and Effect Matrix

Each tool has its advantages depending on the complexity of the deviation and the availability of site or process data.

Using the 5 Whys for Simple Deviation Investigations

The 5 Whys technique is ideal for simple, single-cause deviations. It involves asking “Why?” iteratively (typically five times) to drill down to the core problem.

Example: A subject was dosed without completing a visit ECG.

1. Why was the ECG missed? → Staff forgot to perform it.
2. Why did staff forget? → The ECG checklist wasn’t followed.
3. Why wasn’t the checklist followed? → Staff was covering for a sick colleague and unfamiliar with the workflow.
4. Why was the substitute untrained? → No backup staff training program existed.
5. Why was there no training program? → SOPs didn’t mandate cross-training.

Root Cause: Lack of SOP for backup staff training.
CAPA: Revise SOP, implement training matrix, and add ECG check to the pre-dose checklist.

Fishbone Diagrams for Complex Root Cause Mapping

Also known as the Ishikawa Diagram, the fishbone tool is useful for visualizing multiple potential root causes across categories. This is especially helpful in complex deviations involving people, processes, technology, and environment.

Common categories include:

• People (training, staffing, roles)
• Process (SOPs, workflows, handoffs)
• Equipment (IT systems, monitoring devices)
• Environment (site workload, time pressure)
• Materials (forms, templates, protocol)
• Management (oversight, communication)

Tip: Use fishbone diagrams during cross-functional deviation review meetings to align sponsor, site, and CRA perspectives.

Cause-and-Effect Matrix for Prioritizing Root Causes

When multiple causes are identified, a Cause-and-Effect Matrix helps prioritize them based on severity, occurrence, and detectability. This is especially valuable in evaluating systemic issues or in large-scale deviations across sites.

Example Matrix Structure:

Higher scores indicate higher priority for CAPA planning. This matrix helps sponsors focus their quality improvement resources effectively.

Documentation Expectations for RCA Tools

Regulators expect RCA results to be documented clearly and stored as part of the CAPA record or Deviation Investigation Report. A complete RCA package should include:

• ✅ Description of the deviation
• ✅ Tool(s) used for RCA (e.g., 5 Whys, Fishbone)
• ✅ Identified root cause(s)
• ✅ Supporting evidence (meeting minutes, audit trail)
• ✅ CAPA developed based on the RCA
• ✅ Effectiveness check plan

Note: Avoid listing “human error” as the sole root cause. Regulatory authorities expect deeper process-based or systemic causes, such as inadequate training or poor workflow design.

Regulatory Insights on RCA Expectations

Authorities such as the FDA, EMA, and MHRA have cited sponsors for:

• ❌ RCA tools not used or documented
• ❌ CAPAs developed without identifying true root causes
• ❌ Repetitive deviations with no formal RCA conducted

During inspections, auditors will often request RCA documentation for major deviations, asking how the root cause was determined and how CAPA was linked to it. Using structured tools increases transparency and regulatory confidence.

Conclusion: Embedding RCA Tools into Clinical Quality Systems

Effective use of RCA tools goes beyond fixing a deviation—it helps sponsors and CROs prevent recurrence, improve trial quality, and pass inspections. Whether using the simple 5 Whys or the more advanced Cause-and-Effect Matrix, RCA should be built into every CAPA process, QA review, and deviation SOP.

Invest in RCA training for site staff, CRAs, and QA professionals, and ensure that your quality management system includes templates, timelines, and escalation pathways for RCA execution. A structured, documented approach to deviation investigations will elevate both compliance and credibility in every clinical trial.