Why Incomplete SAE Reporting to IRBs Appears in Regulatory Audit Findings

Introduction: The Importance of SAE Reporting to IRBs

Serious Adverse Events (SAEs) represent critical safety data that must be reviewed by Institutional Review Boards (IRBs) or Ethics Committees (ECs) to safeguard participant welfare. Regulatory agencies including the FDA, EMA, and MHRA mandate complete and timely reporting of SAEs to IRBs in compliance with ICH GCP. Failure to ensure proper reporting is one of the most frequently cited audit findings in clinical trials.

Audit reports often reveal incomplete, delayed, or missing SAE submissions to IRBs, undermining ethical oversight and patient safety monitoring. These findings are often categorized as major deficiencies that can impact trial credibility, delay approvals, or trigger regulatory enforcement.

Regulatory Expectations for SAE Reporting to IRBs

Authorities define specific expectations for IRBs and sponsors regarding SAE reporting:

• All SAEs must be reported promptly to IRBs as per national and protocol-defined timelines.
• IRBs must review SAE reports and assess their impact on participant safety and trial continuation.
• Documentation of SAE submissions must be filed in the Trial Master File (TMF).
• Sponsors must verify site compliance with SAE reporting requirements during monitoring visits.
• SAE trends and cumulative safety data must be reviewed by IRBs at continuing review meetings.

The Health Canada Clinical Trials Database emphasizes complete and timely SAE reporting to IRBs as a critical element of participant protection.

Common Audit Findings on Incomplete SAE Reporting

1. Delayed Submissions

Auditors frequently identify SAE reports submitted weeks or months after occurrence, violating timelines.

2. Missing SAE Reports

Inspections often reveal SAEs documented in source data but not submitted to IRBs.

3. Incomplete Documentation

Audit reports regularly cite SAE reports lacking critical details such as onset date, outcome, or causality assessment.

4. Sponsor Oversight Gaps

Sponsors are cited for failing to verify site compliance with SAE reporting requirements during monitoring visits.

Case Study: FDA Audit on Incomplete SAE Reporting

During an FDA inspection of a Phase II cardiovascular trial, inspectors found that multiple SAEs were documented in patient medical records but not reported to the IRB. The sponsor had no process to reconcile site safety data with IRB submissions. This was categorized as a critical finding, requiring immediate corrective measures and suspension of new subject enrollment.

Root Causes of Incomplete SAE Reporting

Root cause investigations typically identify:

• Lack of SOPs specifying SAE submission timelines and documentation requirements.
• Poor site training on SAE reporting obligations to IRBs.
• Over-reliance on investigators without sponsor verification of reporting practices.
• Absence of electronic systems to track SAE submissions to IRBs.
• Weak communication between sponsors, CROs, and IRBs regarding safety data.