Seriousness criteria is a regulatory classification framework that categorizes an adverse event (AE) as 'serious' based on specific patient outcomes. These outcomes include death, a life-threatening condition, required inpatient hospitalization or prolongation of existing hospitalization, persistent or significant disability/incapacity, or a congenital anomaly/birth defect. This framework is distinct from severity, which describes the intensity of a medical event.
Glossary
Seriousness Criteria

What is Seriousness Criteria?
A regulatory classification framework defining an adverse event as 'serious' if it results in death, is life-threatening, requires inpatient hospitalization, causes persistent disability, or is a congenital anomaly.
The determination of seriousness triggers expedited reporting obligations to regulatory authorities, typically within 7 or 15 days, as defined by ICH E2A and E2D guidelines. Automated pharmacovigilance systems must accurately extract and classify these criteria from unstructured clinical narratives to ensure compliance with global safety reporting mandates and to support robust signal detection workflows.
Frequently Asked Questions
Clear, regulatory-focused answers to the most common questions about the classification framework that defines a 'serious' adverse event in pharmacovigilance.
The seriousness criteria are a regulatory classification framework defined by the ICH E2A guideline that categorizes an adverse event (AE) as 'serious' if it meets one or more of six specific outcomes: results in death, is life-threatening, requires inpatient hospitalization or prolongation of existing hospitalization, results in persistent or significant disability/incapacity, is a congenital anomaly/birth defect, or constitutes an 'other important medical event' that may jeopardize the patient or require intervention to prevent one of the other outcomes. This framework is legally distinct from 'severity,' which describes the intensity of a medical event. The criteria are the backbone of Individual Case Safety Report (ICSR) expedited reporting requirements globally, dictating which cases must be submitted to regulators within 15 calendar days.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Seriousness vs. Severity vs. Expectedness
A comparative analysis of three distinct pharmacovigilance concepts that are frequently conflated during adverse event assessment and regulatory reporting workflows.
| Feature | Seriousness | Severity | Expectedness |
|---|---|---|---|
Definition | A regulatory classification based on patient outcome or intervention required | A clinical measure of the intensity or grade of an adverse event | A regulatory determination of whether an event is listed in the product's reference safety information |
Primary Purpose | Determines expedited reporting obligations to regulators | Guides clinical management and dose modification decisions | Distinguishes labeled reactions from unlisted ones for aggregate analysis |
Governing Framework | ICH E2A and 21 CFR 312.32 | CTCAE grading scales and clinical judgment | Investigator's Brochure or prescribing label |
Assessment Criteria | Death, life-threatening, hospitalization, disability, congenital anomaly, or other medically important event | Mild, moderate, or severe intensity grading based on functional impairment | Consistency with nature and severity described in reference safety information |
Temporal Stability | Fixed at the time of event occurrence based on outcome | May fluctuate over the course of the event as symptoms evolve | Changes only when the reference safety information is updated |
Regulatory Consequence | Triggers 15-day expedited reporting for unlabeled serious events | No direct regulatory reporting implication | Determines whether an event is classified as 'unexpected' for expedited reporting purposes |
A Mild Event Can Be Serious | |||
A Severe Event Can Be Non-Serious |
Core Principles of Seriousness Determination
The classification of an adverse event as 'serious' is a foundational pharmacovigilance activity that triggers expedited reporting timelines and shapes a product's safety profile. These criteria are defined by global regulatory authorities to standardize risk assessment.
The Six Regulatory Criteria
An adverse event is classified as serious if it meets one or more of these standardized outcomes:
- Death: The patient died due to the adverse event.
- Life-Threatening: The patient was at immediate risk of death at the time of the event.
- Inpatient Hospitalization: Required admission to a hospital or prolonged an existing stay.
- Persistent or Significant Disability/Incapacity: A substantial disruption of a person's ability to conduct normal life functions.
- Congenital Anomaly/Birth Defect: An adverse outcome in a child whose parent was exposed to the drug.
- Other Medically Important Event: An event that may not be immediately life-threatening but may jeopardize the patient and require intervention to prevent one of the above outcomes.
Expedited Reporting Triggers
The determination of seriousness directly dictates the regulatory clock. For serious and unexpected adverse events, sponsors must submit an Individual Case Safety Report (ICSR) to regulators within 15 calendar days of first awareness. Non-serious events are reported in periodic aggregate reports like the PBRER, not on an expedited basis. This distinction is critical for compliance with ICH E2A and E2D guidelines.
Seriousness vs. Severity
A frequent point of confusion in pharmacovigilance is the distinction between seriousness and severity. Seriousness is a regulatory definition based on the outcome of the event (e.g., death, hospitalization). Severity describes the intensity of a medical event (e.g., mild headache vs. severe migraine). A severe migraine is not a serious adverse event unless it meets one of the six criteria, such as requiring inpatient hospitalization.
Extraction from Unstructured Text
Automated systems must identify seriousness criteria from narrative clinical text. This involves Medical Named Entity Recognition to extract mentions of outcomes like 'intubated' or 'admitted to ICU' and mapping them to the regulatory framework. Negation detection is critical to avoid flagging historical events or ruled-out diagnoses as current serious outcomes. Contextual models like BioBERT fine-tuned on pharmacovigilance corpora are used for this task.
The 'Required Intervention' Clause
The criterion 'Other Medically Important Event' serves as a safety net. It applies when an event does not result in death, hospitalization, or disability but requires medical or surgical intervention to prevent one of those outcomes. Examples include:
- Allergic bronchospasm requiring emergency room treatment.
- Blood dyscrasias or seizures that do not result in hospitalization.
- Development of drug dependency or abuse.
Impact on Signal Detection
Seriousness criteria act as a primary filter in quantitative signal detection. Algorithms like Empirical Bayes Geometric Mean (EBGM) and Proportional Reporting Ratio (PRR) are often run specifically on the subset of serious cases in databases like FAERS and EudraVigilance to identify the most clinically impactful safety signals. This stratification reduces noise from non-serious, trivial events and focuses analytical resources on potential risks to patient safety.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us