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.

Using Causality Assessment Tools for Adverse Events in Clinical Trials

Introduction: The Importance of Causality Assessment

When an adverse event (AE) occurs in a clinical trial, one of the most important steps is assessing whether the event is related to the investigational product or to other factors such as underlying disease, concomitant medication, or procedures. Regulatory agencies such as the FDA, EMA, MHRA, and CDSCO require that sponsors and investigators use causality assessment tools or structured methods to evaluate the relationship between AEs and study drugs. This assessment influences not only regulatory reporting (e.g., expedited reports of SAEs and SUSARs) but also overall drug safety profiles and labeling decisions.

Several standardized tools exist to support causality judgments, the most widely used being the WHO-UMC causality scale and the Naranjo algorithm. These tools aim to reduce subjectivity and ensure consistency across investigators and sponsors. This article provides a step-by-step guide on causality assessment tools, how they are applied in clinical trials, regulatory expectations, and best practices for accurate attribution of AEs.

The WHO-UMC Causality Assessment Scale

The World Health Organization – Uppsala Monitoring Centre (WHO-UMC) scale is one of the most widely applied frameworks for AE causality assessment. It categorizes events into the following levels:

• Certain: A clinical event with a plausible time relationship to drug administration, not explained by other factors, with clear response to withdrawal (dechallenge).
• Probable / Likely: A reasonable temporal relationship to drug intake, unlikely explained by other conditions, with response to dechallenge.
• Possible: A reasonable time relationship but could also be explained by other drugs or conditions.
• Unlikely: Time to drug intake makes causal relationship improbable, and alternative explanations are more likely.
• Conditional / Unclassified: More data required for assessment.
• Unassessable / Unclassifiable: Insufficient or contradictory information prevents judgment.

This structured approach ensures regulators and sponsors can see a transparent, reproducible rationale for causality assignments. For instance, if a patient develops elevated liver enzymes after starting the study drug, and the values normalize after discontinuation, the event may be classified as “Probable” or “Certain” depending on supporting data.

The Naranjo Algorithm

Another commonly used tool is the Naranjo algorithm, a questionnaire-based method that scores causality based on 10 questions, such as whether the AE appeared after drug administration, whether the AE improved upon withdrawal, and whether rechallenge produced the event again. Scores categorize causality as “Definite,” “Probable,” “Possible,” or “Doubtful.”

While widely used in post-marketing settings, the Naranjo algorithm is sometimes considered too simplistic for complex trial data. Nevertheless, it remains valuable in providing a structured framework for causality decisions.

Other Causality Assessment Tools

In addition to WHO-UMC and Naranjo, several other tools are applied in specific therapeutic areas:

• RUCAM (Roussel Uclaf Causality Assessment Method): Designed for drug-induced liver injury (DILI).
• Bayesian and probabilistic models: Emerging approaches that integrate large datasets and prior knowledge.
• Algorithmic causality scales: Adapted for oncology and immunotherapy-related AEs.

Selection of the tool depends on the therapeutic area, regulatory requirements, and availability of objective data. For example, oncology trials often integrate CTCAE severity grading with causality assessments to build a more comprehensive safety profile.

Regulatory Expectations and Inspection Findings

Regulators expect consistency, documentation, and rationale in causality assessments. Key expectations include:

• FDA: Requires causality fields in IND safety reports and reconciliation with narratives.
• EMA: Mandates causality assignment in EudraVigilance submissions for SUSAR reporting.
• MHRA: Frequently cites missing or inconsistent causality documentation in inspections.
• ICH E2A/E2B: Identifies causality as a required data element for safety reporting.

For example, during an EMA inspection of an oncology trial, auditors cited a sponsor for failing to justify why multiple cases of hepatotoxicity were classified as “Unlikely.” The lack of documented rationale highlighted the importance of using structured causality tools.

Public trial registries such as the WHO International Clinical Trials Registry Platform emphasize the role of standardized AE documentation, reinforcing the need for reliable causality assessment methods across studies.

Challenges in Causality Assessment

Despite structured tools, causality assessment faces several challenges:

• Subjectivity: Different investigators may interpret scales differently without proper training.
• Incomplete data: Missing lab results or diagnostic confirmation complicates judgments.
• Multiple drugs: Patients on concomitant medications pose attribution challenges.
• Rechallenge limitations: Ethical considerations often prevent rechallenge, reducing certainty.

To mitigate these issues, sponsors should develop SOPs, train investigators, and require documentation of rationale for each causality judgment.

Best Practices for Applying Causality Tools

Sponsors and CROs can improve causality assessments by implementing best practices such as:

• Train investigators on WHO-UMC and other tools before trial initiation.
• Require narrative justification for each causality classification.
• Use drop-down menus in eCRFs with WHO-UMC categories to reduce variability.
• Perform data manager and medical monitor review of causality consistency.
• Reconcile causality across eCRFs, narratives, and pharmacovigilance databases.

For example, in a Phase III diabetes trial, causality assessments were cross-checked against concomitant medication records, ensuring consistency and reducing misclassification.

Key Takeaways

Causality assessment tools are critical for ensuring accurate, consistent, and regulatory-compliant AE documentation. The WHO-UMC scale, Naranjo algorithm, and specialized methods provide structured frameworks to reduce subjectivity and support regulatory reporting. Sponsors and investigators must:

• Apply causality assessment tools consistently across trials.
• Document rationale for each judgment.
• Train site staff to ensure uniform understanding and application.
• Reconcile causality across systems for regulatory submissions.

By adopting these practices, clinical teams can strengthen pharmacovigilance, meet regulatory expectations, and safeguard patient safety in clinical trials.