EU PV Regulatory Intelligence news: EU Commission Implementing Regulation 2025/1466 Other
guides
NextPV Services

ICSR case management: end-to-end adverse event reporting

What does end-to-end ICSR management look like — from adverse event intake to regulatory submission?

Individual Case Safety Report (ICSR) management is the core operational activity of any pharmacovigilance system. Every suspected adverse reaction — whether reported by a healthcare professional, a patient, from the medical literature, or from a clinical trial — must be collected, assessed, documented, and reported to regulatory authorities within strict timelines. Missing a single reporting deadline can result in a major finding during an EMA inspection.

The regulatory framework for ICSR management is defined by ICH E2B(R3) (data elements for electronic transmission), EMA GVP Module VI (EMA/873138/2011 Rev 2) (management and reporting of adverse reactions), and ICH E2A (definitions and standards for clinical safety data).

The ICSR Lifecycle

Receipt and Triage

Adverse event reports arrive from multiple sources:

  • Spontaneous reports: From healthcare professionals, patients, or consumers — via phone, email, web forms, or through regulatory authorities
  • Clinical trial reports: From investigators and clinical research organizations
  • Literature reports: From published medical literature (identified through systematic literature monitoring)
  • Solicited reports: From patient support programs, market research, and social media monitoring
  • Regulatory authority reports: Forwarded by NCAs or through EudraVigilance

Upon receipt, every report must be triaged to determine:

  • Validity: Does the report contain the four minimum elements required for a valid ICSR? Per ICH E2D, these are: (1) an identifiable reporter, (2) an identifiable patient, (3) a suspected adverse reaction, and (4) a suspect medicinal product
  • Seriousness: Is the adverse reaction serious (death, life-threatening, hospitalization, disability, congenital anomaly, or other medically important event)?
  • Expectedness: Is the reaction listed in the product's Summary of Product Characteristics (SmPC) or Investigator's Brochure?
  • Regulatory timeline: Based on seriousness and expectedness, what is the reporting deadline?

Reporting Timelines

Per GVP Module VI:

  • Serious, unexpected (spontaneous): 15 calendar days from Day 0 — submitted to EudraVigilance + applicable NCAs
  • Fatal or life-threatening (spontaneous): 15 calendar days (7-day initial + 8-day follow-up for fatal/life-threatening) — submitted to EudraVigilance + applicable NCAs
  • Non-serious (spontaneous): 90 calendar days from Day 0 — submitted to EudraVigilance
  • Serious (clinical trial — SUSAR): 15 calendar days (7-day for fatal/life-threatening) per ICH E2A — submitted to EudraVigilance + ethics committees + investigators

Day 0 is the date the MAH (or their agent) first becomes aware of the minimum information for a valid case.

Data Entry and Case Processing

Once triaged, the ICSR is entered into the safety database using the ICH E2B(R3) data element structure. Key processing steps include:

  • MedDRA coding: Adverse reactions are coded using MedDRA (Medical Dictionary for Regulatory Activities) at the Preferred Term (PT) level
  • Causality assessment: The case processor and/or medical reviewer assess the relationship between the drug and the adverse reaction using established methods (e.g., WHO-UMC system, Naranjo algorithm)
  • Narrative writing: A concise case narrative summarizing the event, patient history, drug exposure, reaction details, and outcome
  • Follow-up: When initial information is incomplete, follow-up requests are sent to the reporter to obtain missing details

Medical Review

A qualified medical professional reviews the case to:

  • Confirm the MedDRA coding is appropriate
  • Assess causality and seriousness independently
  • Identify any signals or patterns requiring further evaluation
  • Approve the case for submission

Expedited Reporting via EudraVigilance

Completed ICSRs are submitted electronically to EudraVigilance in the ICH E2B(R3) XML format, either through EVWEB or the EudraVigilance gateway. The system returns acknowledgments (ACKs) confirming successful receipt — these must be monitored to ensure no submissions fail silently.

For US-marketed products, ICSRs are also submitted to the FDA through the FDA Adverse Event Reporting System (FAERS) per 21 CFR 314.80 (post-marketing) or 21 CFR 312.32 (clinical trials).

Quality Assurance

QA processes should include:

  • Real-time QC: Review of a defined percentage of cases before submission (typically 100% for expedited, sample-based for non-expedited)
  • Retrospective QC: Periodic review of submitted cases to identify systemic quality issues
  • KPI tracking: Monitor key metrics — Day 0 accuracy, processing time, submission timeliness, QC error rates
  • Audit readiness: Maintain complete documentation trails for every case, from source document through processing to submission

Optimizing ICSR Management

Process Efficiency

  • Standardized workflows: Documented SOPs for each step of the ICSR lifecycle ensure consistency across case processors
  • Automation: AI-powered tools can assist with case intake, triage, duplicate detection, and data entry (see our article on AI in PV)
  • Surge capacity: ICSR volumes can spike (e.g., post-launch, media attention, safety signal). Having access to trained backup resources prevents backlogs and missed deadlines

Data Quality

  • Training: Regular training for case processors on MedDRA coding, causality assessment, and narrative writing
  • Coding dictionaries: Keep MedDRA version current (EMA specifies the required version for EudraVigilance submissions)
  • Duplicate management: Implement systematic duplicate detection to prevent artificial inflation of adverse event counts

Regulatory Compliance Monitoring

  • Timeline tracking: Automated monitoring of Day 0 to submission date for every case
  • Late report analysis: Root cause analysis for any late submissions, with CAPA implementation
  • Regulatory intelligence: Monitor changes in reporting requirements (e.g., new EURD list entries, changes in NCA-specific requirements)

Conclusion

ICSR management is the most operationally intensive pharmacovigilance activity and the most frequently scrutinized during inspections. Compliance with GVP Module VI, ICH E2B(R3), and applicable reporting timelines is non-negotiable. For biotech companies with growing ICSR volumes, outsourcing case management to a specialized PV partner ensures that every case is processed accurately and submitted on time — protecting both patient safety and regulatory standing.