SUSAR Reporting & Expedited Timelines: Definitions, Global Workflows, and Inspection-Ready Controls

Published on 16/11/2025

Serious, Unexpected, and Suspected: Mastering SUSAR Reporting and the Global Expedited Clock

What Triggers a SUSAR—and Who Must Receive It

SUSARs—Suspected Unexpected Serious Adverse Reactions—sit at the heart of expedited pharmacovigilance. A SUSAR is a serious adverse reaction (i.e., an AE judged to have a reasonable possibility of causal relationship to the investigational product) whose nature or severity is not consistent with the product’s Reference Safety Information (RSI) in the Investigator’s Brochure (IB) during development or in the authorized labeling/SmPC post-authorization. This triad—seriousness, causality, expectedness—drives whether an expedited report is required

and on which clock.

Seriousness criteria are outcome-based: death, life-threatening at the time of the event, inpatient hospitalization or prolongation, persistent/significant disability/incapacity, congenital anomaly/birth defect, or Important Medical Event (IME) that may jeopardize the subject or require intervention to prevent one of the above. Severity ≠ seriousness; a severe headache is not necessarily serious, while a mild anaphylaxis needing epinephrine is serious (IME).

Expectedness is evaluated against the current, approved RSI version effective at the event onset date. Specificity matters: “rash” in the RSI does not automatically cover “Stevens–Johnson syndrome.” If the RSI states “transaminase increase (mild–moderate),” and the case meets Hy’s Law, that severity is unexpected. The safety file should capture the RSI version, and text used in the decision.

Causality typically maps “possible,” “probable/likely,” or “certain” to the regulatory concept of “reasonable possibility.” For routing, most regions treat either the investigator or the sponsor attribution as sufficient to make a serious event “suspected.” Document both attributions; store rationales in the narrative.

Who gets a SUSAR? During development, expedited reports flow to the competent authorities and national pharmacovigilance systems (e.g., FDA under IND; EU via EudraVigilance), investigators, and IRBs/IECs as applicable. Distribution lists must be jurisdiction-specific and refreshed when sites or authorities change. In global programs, sponsors should maintain a single source of truth for destinations and methods (gateway, portal, CIOMS) and ensure alignment with FDA, EMA, PMDA, and TGA requirements, under the harmonized principles of the ICH and the public-health perspective of the WHO.

“Day 0” starts the clock. Day 0 is the date the sponsor or its agent first becomes aware of a valid case (identifiable patient, identifiable reporter, suspect product, adverse event) that is, or could become, expedited. Time-stamping local time + UTC offset for awareness, medical review, and submission events simplifies cross-region audits.

Development vs post-authorization. This article focuses on development (clinical trial) SUSARs. After authorization, expedited serious reaction rules persist (regional terminology varies), with post-market repositories (e.g., FAERS, EudraVigilance) and periodic reporting (e.g., PBRERs) integrating the picture.

Beating the Clock: Seven-Day and Fifteen-Day Mechanics, Gateways, and Acknowledgments

Timelines at a glance. Fatal or life-threatening SUSARs typically require 7-day initial reporting, with a 15-day follow-up; other SUSARs require 15-day reporting. Local nuances exist; maintain a validated calendar and country annex. The operational goal is to determine seriousness, causality, and expectedness quickly enough to meet clocks without sacrificing accuracy or blinding integrity.

Workflow that meets clocks.

Intake & triage (Day 0): validate minimum criteria; tag potential 7-day cases (death/life-threatening/IME like anaphylaxis); create the ICSR in the PV system (e.g., Argus/ARISg).
Rapid medical assessment: confirm seriousness (criterion, e.g., “life-threatening at onset”), expectedness vs RSI (record version/section), and causality (investigator + sponsor). For blinded trials, use independent unblinded personnel if needed to see arm-level patterns.
Coding and narrative: apply specific MedDRA PTs; populate a concise narrative with chronology, labs (units + ULN), dechallenge/rechallenge, and rationale for decisions.
Electronic transmission: send E2B(R3) messages to authorities/portals; deliver investigator/IRB/IEC notifications per country rule (often CIOMS or line listing). Capture all ACKs and remediate negatives promptly.
Follow-up management: for 7-day initials, schedule the 15-day follow-up; track queries to sites and ensure missing critical fields (e.g., outcome, labs) are chased with due dates.

E2B(R3) discipline. Gateways (EudraVigilance, FAERS, PMDA, TGA) require conformance with E2B(R3) and receiver-specific business rules. Validate mandatory/conditional fields, null flavors, sender/receiver identifiers, and attachments (where permitted). When gateways or national portals are unavailable near deadlines, use a predefined CIOMS fallback and document transport failures, resubmissions, and rationale.

Distribution lists and proof of dispatch. Keep a controlled library of destinations by protocol/country: authorities, investigators, IRBs/IECs, and partners per SDEAs. Automate distribution where possible and archive confirmation (ACKs, portal receipts, email delivery logs) with timestamps. For investigators, ensure site-friendly formats and clear safety letters when the RSI or risk profile changes.

Handling missed deadlines. If a clock is missed, explain and correct: file a deviation with root cause (e.g., late site awareness, misclassification, gateway outage), implement CAPA (e.g., “day-0” alerting, form redesign, gateway monitoring), and document effectiveness checks. Regulators will accept human error; they do not accept unmanaged error.

Linkages to aggregate reporting. Keep counts and narratives consistent with DSUR/PBRER extracts at the Data Lock Point. Record extraction times (local + UTC) and MedDRA versions to defend reproducibility to FDA, EMA, PMDA, and TGA.

Edge Cases and Country Nuances: Getting the Tough Calls Right

Life-threatening ≠ hypothetical. “Life-threatening” means the subject was at immediate risk of death at the time. Avoid upgrading “could have been” scenarios. Justify with clinical facts (e.g., systolic BP, O₂ saturation, airway involvement) in the narrative.

Pregnancy, lactation, and congenital anomalies. Exposure during pregnancy is usually a special situation; report outcomes (spontaneous abortion, congenital anomaly) per regional rules. Create linked maternal/fetal cases; maintain privacy and appropriate de-identification. Where the event meets seriousness and is unexpected/reaction-related, treat as SUSAR.

Medication errors and misuse/abuse. Report harm, not the error alone. If harm results and is related/possibly related, assess expectedness versus RSI. Independently, errors feed risk minimization (labeling, device IFU) and may trigger labeling/education even without SUSAR classification.

DILI/Hy’s Law. For potential drug-induced liver injury, require ALT/AST, total bilirubin, ALP, and INR; rule out cholestasis; consider RUCAM or structured causality. Hy’s Law patterns should be triaged as potential 7-day cases given seriousness and prognostic implications.

Vaccines and high-background events. Myalgia, fever, and headache are common post-immunization; causality relies on time-to-onset, case definitions (e.g., Brighton Collaboration), and background rates. For AESIs such as myocarditis or ADEM, strengthen expectedness tables, ensure adjudication where available, and align with WHO immunization safety guidance.

Device and combination products. Device malfunctions that could lead to death/serious injury may require device vigilance alongside drug SUSAR reporting. Capture device identifiers (model/lot/serial, software version) and route via device channels in parallel to PV where required.

Blinding safeguards. In blinded trials, keep operational teams arm-agnostic. Where unblinded review is necessary (e.g., emerging safety imbalance), use an independent statistician/physician per DSMB/IDMC charter. Share only decisions (continue/stop/enrich) back to the blinded team; record all access and decisions with local time + UTC offset.

Regional notes. Maintain a crosswalk of timing, content, and channel specifics by region. Align U.S. IND safety reporting expectations under 21 CFR 312.32 with EU EudraVigilance procedures and National Competent Authority rules, and with national pathways at PMDA and TGA. For multi-region programs, reconcile any differences via country annexes to the Safety Management Plan and SDEAs.

Literature and partner cases. A single published case can become a SUSAR if serious, unexpected, and suspected. Consolidate duplicate publications; cite the source in the ICSR. For partner/licensee exchanges, SDEAs must define day-0, clocks, duplicate resolution, and redistributions so that neither party misses deadlines.

Privacy and lawful processing. Remove direct identifiers from outbound transmissions; retain linkable keys only where justified and lawful (GDPR/UK-GDPR in the EU/UK; HIPAA considerations in the U.S.). Record cross-border transfer mechanisms and redact narratives consistently.

Audit-Proof Delivery: Evidence, KPIs, Pitfalls, and a Ready-to-Use Checklist

Inspection-ready evidence bundle. Keep a rapid-pull index able to surface within minutes for reviewers at the FDA, EMA, PMDA, and TGA, consistent with ICH principles and the WHO public-health mission:

Approved SOPs/WIs for expedited reporting, RSI governance, coding, narratives, and distribution; change history and training records.
RSI library with effective dates; examples of expectedness assessments citing sections/wording.
Gateway configuration (E2B(R3) profiles), routing maps, credentials, ACK logs (including negative ACK remediation), and CIOMS fallback procedures.
Investigator/IRB/IEC distribution proofs: safety letters, emails, portal receipts, and tracking ledgers.
Case dossiers for sample SUSARs: narratives, coding, causality rationale, timelines (awareness → submission), follow-ups.
Deviation/CAPA files for any late submissions with root cause and effectiveness checks.
Aggregate alignment: DSUR/PBRER DLP extracts, MedDRA version displays, and timestamped manifests.

Program-level KPIs (examples).

On-time rate: % of fatal/life-threatening SUSARs reported within 7 days; % of other SUSARs within 15 days (by region).
ACK health: % positive ACKs on first submit; median hours from transmit to ACK; remediation time for negative ACKs.
Cycle time: awareness (Day 0) → medical review → final submission (median and 90th percentile).
Narrative and coding quality: QC pass rate; concordance on IME/AESI terms; % narratives with explicit RSI citations.
Follow-up performance: % of 7-day initials with 15-day follow-ups on time.
Reconciliation impact: # of SUSARs identified via EDC↔PV reconciliation; % submitted within clocks after identification.
CAPA effectiveness: post-CAPA reduction in late submissions or misclassification (target reductions defined).

Common pitfalls—and durable fixes.

Uncertain day-0 ownership → Define who starts the clock; auto-alerts on minimum criteria; stamp awareness with local time + UTC offset.
RSI misalignment → Embed RSI version capture at onset; maintain controlled cross-walks; retrain sites after IB updates.
Dictionary drift → Lock MedDRA versions across PV and analytics; run migration impact reports; annotate trend breaks in DSUR/PBRER.
Gateway outages near the deadline → Monitor proactively; keep CIOMS/portal fallback; document resubmission logic and communications.
Narrative-field inconsistency → Automated checks that narrative conclusions (e.g., Hy’s Law) match seriousness/expectedness in the case header.
Blinding leaks → Segregate unblinded roles/systems; provide arm-agnostic dashboards; audit access logs.
Poor partner alignment → Mirror SDEA clocks and formats; run joint drills; maintain duplicate-resolution rules and shared distribution lists.

One-page checklist (study-ready SUSAR operations).

Expedited reporting SOP approved; roles/RACI defined; training current across sponsor/CRO/vendors.
RSI library controlled with effective dates; expectedness assessments cite version/section in every case.
Day-0 rules documented; alerting active; timestamps recorded with local time + UTC offset.
Gateway E2B(R3) validated; ACK monitoring live; CIOMS/portal fallback rehearsed.
Investigator/IRB distribution lists current by country; safety letters/templates ready.
Narrative shells (fatalities, anaphylaxis, DILI, pregnancy) standardized; coding QC for IME/AESI terms.
7/15-day calendars active; follow-up tracker ensures second-stage submissions.
EDC↔PV reconciliation running on a cadence; SUSARs detected via reconciliation routed within clocks.
Deviation/CAPA pathway operating; KPIs reviewed in safety governance with documented actions.
Alignment to FDA, EMA, PMDA, TGA, ICH, and WHO demonstrated in artifacts.

Bottom line. SUSAR reporting is a precision discipline: clear definitions, fast but defensible decisions, reliable electronic transmission, and transparent documentation. With RSI governance, day-0 discipline, E2B(R3) rigor, and measured CAPA, sponsors can meet global clocks, protect participants, and withstand inspections across regions while supporting the broader public-health mission.