Inferensys

Glossary

Expectedness

Expectedness is a regulatory determination of whether an adverse event's nature, severity, or outcome is consistent with the information listed in a product's reference safety information, such as the investigator's brochure or prescribing label.
Wide-angle shot of a modern WeWork open floor plan with creative walls covered in AI system architecture diagrams, product team collaborating in standing desk area with industrial lighting.
PHARMACOVIGILANCE DETERMINATION

What is Expectedness?

Expectedness is a regulatory determination of whether an adverse event's nature, severity, or outcome is consistent with the information listed in the product's reference safety information, such as the investigator's brochure or prescribing label.

Expectedness is the binary classification of an adverse event as either 'expected' (listed) or 'unexpected' (unlisted) based on its alignment with the Reference Safety Information (RSI) . This determination is critical because unexpected serious adverse reactions trigger expedited reporting timelines to regulatory authorities, typically within 7 or 15 days, whereas expected events follow routine periodic reporting schedules.

The assessment requires precise comparison of the reported event's verbatim term against the RSI's listed adverse reactions, considering both the event's clinical diagnosis and its severity grade. An event is deemed unexpected if its nature or intensity is inconsistent with the RSI, even if the general class of reaction is mentioned. This determination is distinct from causality assessment, which evaluates whether the drug caused the event.

REGULATORY CLASSIFICATION

Core Characteristics of Expectedness

Expectedness is a binary regulatory determination that categorizes an adverse event based on its consistency with the product's Reference Safety Information (RSI). This classification directly dictates the expedited reporting obligations of a clinical trial sponsor or marketing authorization holder.

01

Reference Safety Information (RSI) Benchmark

The determination of expectedness is strictly relative to the product's Reference Safety Information (RSI). For investigational drugs, this is the Investigator's Brochure (IB); for marketed products, it is the local prescribing information or Summary of Product Characteristics (SmPC). An event is 'expected' only if its nature, severity, specificity, and outcome are consistent with the descriptions in these specific documents. Any event absent from the RSI, or occurring with greater severity or specificity than listed, is classified as 'unexpected'.

02

Nature, Severity, and Specificity

Expectedness is not a simple keyword match. It requires a clinical comparison of the observed event against the RSI listing:

  • Nature: The medical diagnosis or syndrome (e.g., 'aplastic anemia' vs. a listed term of 'anemia').
  • Severity: A Grade 4 event may be unexpected if the RSI only lists Grade 1-2 events.
  • Specificity: A specific diagnosis like 'Stevens-Johnson Syndrome' is unexpected if the RSI only lists a general term like 'rash'.
  • Outcome: An event resulting in death may be considered unexpected if the RSI only describes non-fatal occurrences.
03

Expedited Reporting Trigger

The expectedness classification is the primary gatekeeper for expedited safety reporting. According to ICH E2A guidelines, only Suspected Unexpected Serious Adverse Reactions (SUSARs) must be reported to regulatory authorities on an accelerated timeline (7 or 15 calendar days).

  • Expected + Serious: Does not qualify for expedited reporting; handled in periodic aggregate reports.
  • Unexpected + Serious: Qualifies as a SUSAR and triggers immediate unblinding and rapid regulatory submission.
04

Class Effects and Labeling Precedent

An event cannot be automatically classified as 'expected' based solely on a class effect or its occurrence with other drugs in the same pharmacological class. The event must be explicitly documented in the specific product's own RSI. Similarly, a sponsor's prior knowledge of an event from a different clinical trial does not make it expected for the current protocol unless the IB has been formally updated to include it. The RSI is the sole authoritative source.

05

Unblinding for SUSAR Determination

In blinded clinical trials, determining expectedness for a serious adverse event often necessitates emergency unblinding of the individual patient's treatment assignment. If the event is unexpected per the IB, the investigator or sponsor must break the blind to confirm whether the patient received the active drug or placebo. Only if the patient was on the active drug is the event a SUSAR requiring expedited reporting. Placebo events are not reportable as SUSARs.

06

Automated Expectedness Logic

AI-driven pharmacovigilance systems automate expectedness assessment by:

  • Semantic Matching: Comparing extracted adverse event terms against the RSI using medical ontologies like MedDRA.
  • Severity Classification: Parsing CTCAE grades from unstructured text to compare against the RSI's severity profile.
  • Rule Engines: Applying deterministic logic that flags any event not found in the RSI term list as 'unexpected' for immediate human review.
  • Contextual Analysis: Detecting negation and uncertainty to avoid misclassifying historical or hypothetical events.
EXPECTEDNESS IN PHARMACOVIGILANCE

Frequently Asked Questions

Clarifying the regulatory definition and operational application of expectedness in adverse event reporting and signal detection workflows.

Expectedness is a regulatory determination of whether the nature, severity, specificity, and outcome of an observed adverse event are consistent with the information listed in the product's Reference Safety Information (RSI) , such as the Investigator's Brochure (IB) for investigational drugs or the Summary of Product Characteristics (SmPC) or Prescribing Information (USPI) for marketed products. An event is 'expected' if its clinical description aligns with the RSI; it is 'unexpected' if it diverges in nature, severity, or frequency from what is documented. This binary classification is the primary driver of expedited reporting obligations, as unexpected serious adverse reactions trigger accelerated 7-day or 15-day reporting timelines to regulatory authorities under ICH E2A and E2D guidelines.

REGULATORY DISTINCTION

Expectedness vs. Causality Assessment

A comparison of two distinct pharmacovigilance concepts: the regulatory determination of whether an adverse event is listed in reference safety information versus the clinical evaluation of the likelihood that a drug caused the event.

FeatureExpectednessCausality Assessment

Primary Domain

Regulatory

Clinical

Core Question

Is this event in the label?

Did the drug cause this event?

Reference Source

Investigator's Brochure, Prescribing Label, SmPC

Patient history, temporal relationship, dechallenge/rechallenge data

Evaluator

Drug safety associate, regulatory affairs

Clinician, medical reviewer

Standardized Framework

Listedness/Unlistedness per reference safety information

WHO-UMC criteria, Naranjo scale, French imputability method

Temporal Dependency

Considers Alternative Etiologies

Impact on ICSR

Determines regulatory reporting obligations

Determines case narrative and signal strength

Binary Outcome

Data Source for Automation

Structured label sections, MedDRA-coded term lists

Unstructured clinical notes, narrative text, temporal event sequences

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.