ICH E3 requires other serious adverse events to receive focused safety reporting, including patient-level listing and narrative treatment when needed to understand the event and its relationship to study treatment. ICH E3 distinguishes deaths from other serious adverse events for listing purposes; a fatal serious event may be referenced in both contexts, so counting and cross-references must remain clear.
ReviewedEvidence2 sourcesSectionWriting & Style
Quick answer
Serious adverse events in a CSR need clear summary, patient-level listing, and selected narratives so reviewers can follow what happened and how the cases were assessed.
Key details
Core IssueICH E3 requires other serious adverse events to receive focused safety reporting, including patient-level listing and narrative treatment when needed to understand the event and its relationship to study treatment.
Registerscholarly, professional, or research/report writing
Important caveats
Scope Boundary
ICH E3 distinguishes deaths from other serious adverse events for listing purposes; a fatal serious event may be referenced in both contexts, so counting and cross-references must remain clear.
Further guidance
Content
Separate overall safety summaries from the patient-level serious-event listing, and use narratives for the cases that require chronological clinical explanation.
Purpose
Serious adverse events in a CSR need clear summary, patient-level listing, and selected narratives so reviewers can follow what happened and how the cases were assessed.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
ICH E3 section 12.3.3 calls for analysis and discussion across deaths, other serious adverse events, and other significant adverse events after the relevant case listings and narratives. This is an interpretive synthesis, not a duplicate death/serious-event listing or a replacement for individual patient narratives.
ICH E3 section 12.2.3 calls for analysis of adverse events beyond their tabular display, focusing on patterns important to safety interpretation. Do not treat the analysis as a substitute for the event display or patient-level listing, and do not imply causality beyond what the study evidence supports.
ICH E3 section 12.2.1 calls for a brief summary of adverse events within the safety evaluation before more detailed displays and analyses. Keep this section a high-level summary; it is not a substitute for detailed adverse-event displays, patient-level listings, serious-event treatment, or narratives.
ICH E3 section 12.2.2 provides for structured display of adverse events as part of the clinical study report safety evaluation. A summary display is distinct from patient-level adverse-event listings and from narratives of selected serious or otherwise significant cases.
ICH E3 section 12.3.1.3 distinguishes other significant adverse events from deaths and other serious adverse events for focused safety reporting. Do not merge this category with all adverse events, deaths, or other serious adverse events; ICH E3 gives these safety groupings separate reporting roles.
ICH E3 places patient-level adverse-event listings in the report appendices and calls for listings that identify individual patients and relevant event details supporting review. A listing is not the same as a summary adverse-event table or a selected patient narrative; each serves a different level of safety reporting.
ICH E3 section 12.4.1 points to a by-patient listing of abnormal laboratory values in section 14.3.4 and distinguishes that safety display from the broader listing of individual laboratory measurements. This page is about the dedicated abnormal-value listing under ICH E3 14.3.4; it is distinct from the full individual-measurement appendix under 16.2.8 and from analytical discussion in section 12.4.2.
ICH E3 section 11.4.2.7 identifies special efficacy-analysis considerations for active-control studies intended to support equivalence. This is a CSR efficacy-results reporting issue for active-control equivalence designs; it does not define a universal equivalence margin or replace protocol-level design justification.
