Assessing the Relationship Between Adverse Events and Investigational Products

Introduction: Why AE–IP Relationship Matters

In clinical trials, one of the most important judgments investigators and sponsors make is whether an adverse event (AE) is related to the investigational product (IP). Regulatory authorities such as the FDA, EMA, MHRA, and ICH guidelines require clear attribution of AEs to the IP, as this impacts expedited reporting, aggregate analyses, drug labeling, and ultimately the benefit–risk assessment of the product. Misclassification of causality can delay safety reporting, distort clinical trial outcomes, and trigger regulatory findings.

Assessing the relationship between AEs and investigational products requires both clinical judgment and systematic methods. This includes reviewing timing, dechallenge/rechallenge data, biological plausibility, and concomitant factors such as underlying disease and concomitant medications. The decision-making process must be documented, transparent, and consistent across all trial sites. This article provides a step-by-step guide on assessing AE–IP relationships, regulatory expectations, examples, challenges, and best practices.

Key Criteria for Determining Relationship to Investigational Product

Investigators and sponsors typically use structured criteria to determine whether an AE is related to the IP:

• Temporal relationship: Did the AE occur shortly after IP administration?
• Dechallenge: Did the AE resolve after stopping or reducing the IP?
• Rechallenge: Did the AE reappear when the IP was restarted?
• Biological plausibility: Is the AE consistent with the pharmacology of the IP?
• Alternative explanations: Could underlying disease, concomitant medication, or procedure explain the AE?

For example, if a subject develops elevated liver enzymes two weeks after starting the IP, and the levels normalize after discontinuation, a “probable” relationship may be established.

Regulatory Requirements for Causality Determination

Authorities emphasize that AE–IP relationships must be consistently documented and justified:

• FDA: Expects causality attribution in IND safety reports and NDA/BLA submissions, with reconciliation across datasets.
• EMA: Requires investigator and sponsor causality in EudraVigilance SUSAR submissions.
• MHRA: Frequently inspects eCRFs and SAE narratives to verify rationale for causality judgments.
• ICH E2A/E2B: Defines causality attribution as a mandatory field in safety reporting standards.

For example, in a 2022 EMA inspection, a sponsor was cited for failing to reconcile investigator-assessed “Not related” AEs with sponsor-identified safety signals in aggregate data, highlighting the importance of transparent reconciliation.

Case Study: Rash Following Immunotherapy

In a Phase II immunotherapy trial, several patients experienced Grade 3 skin rash. Investigators initially recorded the AEs as “Possibly related” to the IP. However, sponsor pharmacovigilance review noted a consistent pattern across multiple patients and classified the events as “Probably related.” The sponsor reported the rashes as SUSARs within 15 days. This proactive reclassification aligned with regulatory expectations and avoided inspection findings.

Challenges in Assessing AE–IP Relationship

Determining whether an AE is related to an investigational product is complex, with several challenges:

• Subjectivity: Different investigators may assess causality differently without training.
• Limited data: In early-phase trials, limited knowledge of the IP’s safety profile complicates judgments.
• Multiple confounders: Concomitant medications and comorbidities can obscure attribution.
• Bias: Investigators may underreport IP-related causality to protect trial continuation.

These challenges underline the need for structured tools (e.g., WHO-UMC scale) and sponsor oversight to ensure objective and consistent assessments.

Best Practices for Establishing AE–IP Relationship

To ensure accuracy and compliance, sponsors and investigators should adopt best practices:

• Use standardized causality assessment tools such as WHO-UMC scale or Naranjo algorithm.
• Require justification for each causality classification in eCRFs.
• Reconcile investigator and sponsor causality in safety databases and narratives.
• Establish SOPs for causality reassessment after unblinding in blinded trials.
• Train investigators and CRAs on causality documentation and regulatory expectations.

For example, in a cardiovascular trial, causality training modules were implemented for investigators, reducing misclassification and inspection findings by 40%.

Regulatory Implications of Misclassification

Incorrect AE–IP causality classification can have serious regulatory consequences:

• Delayed or missed SUSAR reporting.
• Incorrect DSUR/PSUR submissions.
• Inspection findings and regulatory citations.
• Potential delays in trial approval or marketing applications.

Accurate causality assignment is therefore essential not only for compliance but also for ensuring patient safety and maintaining trial credibility.

Key Takeaways

The relationship of adverse events to investigational products is central to clinical trial safety oversight. To ensure accuracy and compliance, sponsors and investigators must:

• Apply structured causality assessment tools.
• Document rationale for AE–IP relationship judgments.
• Reconcile investigator and sponsor causality assessments.
• Train stakeholders on regulatory expectations and best practices.

By applying these practices, trial teams can improve causality accuracy, strengthen regulatory compliance, and protect patient safety across global clinical development programs.