Study guide

3.2 Adverse Event Classification and Reporting

Certified Clinical Research Coordinator CCRC

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Scientific Concepts and Research Design

1.1 Protocol Elements 1.2 Study Design and Objectives 1.3 Study Endpoints and Biostatistics

2 Chapter 2: Ethical Principles and Guidelines

2.1 Ethical Principles (Declaration of Helsinki, Belmont Report) 2.2 Informed Consent Process and Documentation 2.3 Vulnerable Populations and Assent

3 Chapter 3: IRB/IEC Oversight and Participant Safety

3.1 IRB/IEC Functions and Oversight 3.2 Adverse Event Classification and Reporting 3.3 Safety Monitoring and Safety Reporting

4 Chapter 4: Participant Rights and Ethics

4.1 Participant Rights and Confidentiality (HIPAA/GDPR) 4.2 Conflicts of Interest 4.3 Ethical Scenarios in Clinical Trials

5 Chapter 5: Product Development and Regulatory Framework

5.1 Drug and Device Development Phases 5.2 U.S. and International Regulatory Frameworks 5.3 Investigational Product Investigator's Brochure (IB)

6 Chapter 6: Investigational Product Accountability

6.1 Investigational Product Labeling and Storage 6.2 Investigational Product Receipt, Dispensing, and Accountability 6.3 Investigational Product Return and Destruction

7 Chapter 7: Regulatory Submissions and Actions

7.1 Regulatory Submissions (IND, NDA, IDE, PMA) 7.2 Regulatory Actions and Compliance 7.3 Pharmacokinetics and Pharmacodynamics in Product Development

8 Chapter 8: Clinical Trial Operations and GCP Principles

8.1 Introduction to ICH E6 GCP Principles (including R3 updates) 8.2 Investigator Responsibilities under GCP 8.3 Sponsor Responsibilities and Oversight

9 Chapter 9: Essential Documents and Site Qualification

9.1 Essential Documents (Pre-study, During, Post-study) 9.2 Site Selection and Qualification 9.3 Quality Management and Standard Operating Procedures (SOPs)

10 Chapter 10: Protocol Deviations and Amendments

10.1 Protocol Adherence and Compliance 10.2 Protocol Deviations and Violations 10.3 Protocol Amendments and Version Control

11 Chapter 11: Monitoring Visits and Audits

11.1 Monitoring Preparation and Visit Types 11.2 Monitoring Visits (SIV, IMV, COV) 11.3 Regulatory Inspections and Site Audits

12 Chapter 12: Study and Site Management - Startup

12.1 Site Startup Operations 12.2 Site Budget and Contract Management 12.3 Site Staffing, Training, and Documentation

13 Chapter 13: Enrollment and Recruitment

13.1 Enrollment Management and Strategies 13.2 Participant Recruitment and Retention 13.3 Participant Compensation and Ethics

14 Chapter 14: Daily Trial Coordination

14.1 Visit Scheduling and Logistics 14.2 Equipment Maintenance and Calibration 14.3 Specimen Handling and Shipping (IATA/dangerous goods)

15 Chapter 15: Quality Improvement and Site Closeout

15.1 Participant Safety Management 15.2 Quality Improvement and Site Audits Preparation 15.3 Study and Site Closeout Procedures

16 Chapter 16: Source Documentation and Case Report Forms

16.1 Source Documentation Standards (ALCOA-C) 16.2 Case Report Forms and eCRF Completion 16.3 Electronic Data Capture (EDC) Systems

17 Chapter 17: Data Management and Queries

17.1 Data Management Processes 17.2 Data Queries and Discrepancy Resolution 17.3 Data Correction and Audit Trails

18 Chapter 18: Data Privacy and Records Retention

18.1 Data Privacy and Confidentiality 18.2 Records Retention and Archiving 18.3 Compliance in Clinical Trial Informatics

3.2 Adverse Event Classification and Reporting

Key Takeaways Explain This Topic AI

An Adverse Event (AE) is any untoward medical occurrence that does not necessarily have a causal relationship with the treatment.

Seriousness is a regulatory definition triggering specific reporting requirements, whereas severity describes the clinical intensity of an event.

Suspected Unexpected Serious Adverse Reactions (SUSARs) require expedited reporting by the sponsor to regulatory authorities: 7 calendar days for fatal or life-threatening cases and 15 for the rest (ICH E2A).

Last updated: October 2026

Understanding and Classifying Adverse Events

Patient safety is the paramount concern in any clinical trial. A central component of ensuring safety is the systematic identification, classification, and reporting of adverse events. Clinical Research Coordinators (CRCs) must master the terminology and regulatory requirements surrounding safety reporting to ensure compliance and protect trial participants.

Defining Adverse Events (AEs) and Adverse Drug Reactions (ADRs)

An Adverse Event (AE) is defined as any untoward medical occurrence in a patient or clinical investigation subject administered a pharmaceutical product, and which does not necessarily have a causal relationship with this treatment. An AE can therefore be any unfavorable and unintended sign (including an abnormal laboratory finding), symptom, or disease temporally associated with the use of a medicinal (investigational) product, whether or not considered related to the medicinal (investigational) product.

An Adverse Drug Reaction (ADR) , on the other hand, implies causality. In the pre-approval clinical experience with a new medicinal product, all noxious and unintended responses to a medicinal product related to any dose should be considered adverse drug reactions. The phrase "responses to a medicinal product" means that a causal relationship between a medicinal product and an adverse event is at least a reasonable possibility.

Severity versus Seriousness: A Critical Distinction

One of the most common errors in clinical research is confusing the severity of an adverse event with its seriousness. These terms are not synonymous in regulatory language.

Severity refers to the clinical intensity of the event. It is a clinical grade. Common grading scales include the Common Terminology Criteria for Adverse Events (CTCAE), which categorizes severity as:

Mild (Grade 1): Asymptomatic or mild symptoms; clinical or diagnostic observations only; intervention not indicated.

Moderate (Grade 2): Minimal, local or noninvasive intervention indicated; limiting age-appropriate instrumental activities of daily living.

Severe (Grade 3): Severe or medically significant but not immediately life-threatening; hospitalization or prolongation of hospitalization indicated; disabling.

Life-threatening (Grade 4): Life-threatening consequences; urgent intervention indicated.

Death (Grade 5): Death related to AE.

Seriousness , conversely, is a regulatory definition based on patient/event outcome or action criteria. It serves as a guide for defining regulatory reporting obligations. An adverse event is considered a Serious Adverse Event (SAE) if it results in any of the following outcomes:

Results in death.

Is life-threatening: The patient was at immediate risk of death from the event as it occurred (it does not include an event that, had it occurred in a more severe form, might have caused death).

Requires inpatient hospitalization or prolongation of existing hospitalization.

Results in persistent or significant disability/incapacity.

Is a congenital anomaly/birth defect.

Is an important medical event: Events that may not be immediately life-threatening or result in death or hospitalization but may jeopardize the patient or may require intervention to prevent one of the other outcomes listed above (e.g., allergic bronchospasm requiring intensive treatment in an emergency room or at home).

Example: A subject experiences a severe headache that lasts for three hours but resolves with over-the-counter medication at home. The event is severe in intensity but is not serious because it did not result in death, hospitalization, or disability.

Causality Assessment and Expectedness

Two judgments shape safety reporting. For every SAE, the investigator includes an assessment of causality in the report to the sponsor (ICH E6(R3) 2.7.2(b)). Expectedness is judged against the reference safety information, chiefly by the sponsor when it decides on expedited reporting to regulators (3.13.2(c)).

Causality answers the question: Is there a reasonable possibility that the investigational product caused the adverse event? Investigators typically classify causality as:

Not Related / Unlikely: The event is clearly due to extraneous causes (e.g., underlying disease, environment).

Possible: The event follows a reasonable temporal sequence from administration, but could also be reasonably explained by the subject's clinical state or other therapies.

Probable / Definite: The event follows a reasonable temporal sequence, abates upon withdrawal of the drug (dechallenge), and cannot be reasonably explained by the known characteristics of the subject's clinical state.

Expectedness asks: Is the nature or severity of the event consistent with the applicable product information? For an unapproved investigational drug, the reference document is the Investigator's Brochure (IB). If the event is not listed in the IB, or occurs with greater severity or specificity than described, it is considered unexpected .

Expedited Reporting: The SUSAR

When an event is Serious, Unexpected, and Suspected to be related to the investigational product, it is classified as a Suspected Unexpected Serious Adverse Reaction (SUSAR) . SUSARs represent significant, unforeseen safety signals and trigger expedited reporting requirements to regulatory authorities (like the FDA or EMA) and all participating investigators.

Event Characteristic Expedited Reporting Timeline (FDA 21 CFR 312.32)

Fatal or Life-Threatening SUSARs Must be reported to the regulatory agency no later than 7 calendar days after the sponsor's initial receipt of the information.

All other SUSARs Must be reported no later than 15 calendar days after the sponsor determines that the information qualifies for reporting.

Under ICH E2A, the sponsor's clocks run from its first knowledge that a case qualifies: no later than 7 calendar days for fatal or life-threatening SUSARs (followed by as complete a report as possible within 8 more days) and 15 calendar days for all others.

At the site, ICH E6(R3) 2.7.2(b) requires every SAE to be reported to the sponsor immediately after the investigator reasonably becomes aware of it; in the US, FDA guidance anticipates that the initial report will generally not exceed 1 calendar day. The CRC often prepares the report, but the investigator keeps responsibility for safety reporting (2.7.2(d)), and the sponsor's own deadlines depend on that speed. The sponsor then evaluates the SAE, determines if it is a SUSAR, and files the expedited IND safety report with the FDA.