Siedlerstraße 7 | 68623 Lampertheim, Germany

info@zamann-pharma.com

ICSR in Pharmacovigilance in 2026: Case Processing, E2B(R3), Reporting Timelines, and Compliance Guide

EudraVigilance now holds more than 31.2 million individual case safety reports, which shows the scale of safety data that regulators must review and compare. Therefore, inspectors no longer accept timely submission alone as proof of compliance; they trace each case from day zero and validity checks through seriousness assessment, MedDRA coding, medical review, duplicate detection, follow-up, and E2B(R3) transmission. In 2026, ICSR in pharmacovigilance requires both speed and documented control. Companies must show who made each decision, why they made it, and how their systems protected reporting timelines and data integrity. However, one weak intake record, coding error, missed follow-up, or duplicate case can reveal wider failures across the pharmacovigilance system.

Table of Contents

What Is an ICSR in Pharmacovigilance?

An individual case safety report (ICSR) records a suspected adverse event in a specific patient. However, safety information becomes a valid ICSR only when it includes an identifiable patient, reporter, suspected drug, and adverse event. Once these four elements exist, the pharmacovigilance team confirms day zero and evaluates reporting requirements.

The infographic below shows the four minimum criteria required to validate an ICSR in pharmacovigilance.

Infographic showing the four ICSR validity criteria: identifiable patient, identifiable reporter, suspected medicinal product, and suspected adverse event.
ICSR Validity Map: Four Minimum Criteria for a Valid Individual Case Safety Report.

Why Do Case Processing Controls Matter During an Inspection?

Inspectors review ICSR case processing to confirm that the pharmacovigilance system makes consistent, timely, and traceable decisions. However, incomplete assessments, inconsistent MedDRA coding, delayed follow-up, and missed submission clocks can expose weak procedures or poor oversight. Therefore, companies must document each case decision, track reporting timelines, and resolve data gaps quickly. Otherwise, inspectors may classify individual errors as wider pharmacovigilance quality-system failures.

Four ICSR Controls Inspectors Examine Across the Case Lifecycle

Inspectors follow each safety case from initial receipt to regulatory submission and closure. Therefore, they focus on the controls that protect case validity, data consistency, reporting timelines, and traceability.

The following four control areas often determine whether an ICSR process can withstand regulatory inspection:

  • Validity Assessment and Day Zero Control (PDF)
  • MedDRA Coding and Medical Review (PDF)
  • E2B(R3) Data Mapping and Acknowledgement Control (PDF)
  • Follow-Up and Duplicate Case Management (PDF)

Validity Assessment and Day Zero Control (PDF)

A valid ICSR needs four minimum criteria. Once available, they establish day zero and start the reporting clock.

Download ICH E2D: Post-Approval Safety Data Management—Definitions and Standards for Expedited Reporting Here

MedDRA Coding and Medical Review (PDF)

Accurate MedDRA coding preserves the clinical meaning. Medical review then confirms consistency and case quality.

Download Coding with MedDRA Here

E2B(R3) Data Mapping and Acknowledgement Control (PDF)

E2B(R3) standardizes electronic ICSR transmission. Acknowledgements confirm acceptance or identify transmission errors.

Download ICH E2B(R3): Implementation Guide for Electronic Transmission of Individual Case Safety Reports Here

Follow-Up and Duplicate Case Management (PDF)

Follow-up completes missing case information. Duplicate checks prevent repeated reports from affecting safety analysis.

Download ICH E2D(R1): Post-Approval Safety Data—Management and Reporting of Individual Case Safety Reports Here

How Do Reporting Timelines Change by Case Type and Region?

The reporting clock starts when the company receives enough information to validate an ICSR. However, regional rules determine the final deadline. Therefore, pharmacovigilance teams must document day zero, classify the case correctly, track new follow-up information, and retain proof of successful submission.

The table below connects each reporting deadline with the evidence inspectors may review.

Case Type and Region Reporting Timeline Evidence Inspectors Expect
Day Zero – General Principle
Starts when the minimum ICSR criteria become available
Original source, receipt timestamp, validity assessment, and audit trail
Serious Post-Marketing ICSR – EU
As soon as possible, within 15 calendar days
Seriousness assessment, due-date calculation, E2B transmission record, and acknowledgement
Non-Serious Post-Marketing ICSR – EU
Within 90 calendar days
Case classification, reporting clock, submission record, and acknowledgement
Serious and Unexpected Post-Marketing Case – US
Within 15 calendar days
Seriousness and expectedness rationale, FDA submission record, and confirmation
Follow-Up to a US 15-Day Alert Report
Within 15 calendar days after receiving new information
Follow-up receipt date, contact attempts, updated case data, and submission evidence
Significant Follow-Up – EU
Apply the 15-day or 90-day clock according to the updated seriousness status
Follow-up assessment, version history, revised due date, E2B update, and acknowledgement

The infographic below explains how day zero, case type, and follow-up information determine ICSR reporting timelines.

Infographic showing ICSR reporting timelines from day zero through 15-day, 90-day, and follow-up reporting decisions.
ICSR Reporting Clock: Day Zero, 15-Day, 90-Day, and Follow-Up Decisions.

How Do Inspectors Reconcile ICSR Data with Source Evidence?

Inspectors trace each ICSR from the original source to the final database status. They compare source records with case validity, MedDRA coding, medical assessment, E2B(R3) transmission, acknowledgements, and follow-up history. Therefore, companies must maintain a clear audit trail and explain every case decision. Any mismatch between the source, safety database, or submission record can reveal weak data integrity and case-processing controls.

Final Words

EMA inspectors recorded 87 pharmacovigilance deficiencies in 2024, including 29 major findings. Therefore, companies must treat ICSR in pharmacovigilance as a controlled lifecycle rather than a simple reporting task. Strong teams document every decision from day zero to follow-up, transmission, acknowledgement, and final case closure. As inspections become more data-driven, clear audit trails and consistent case processing will define inspection readiness.

Pharmaceutical team managing GMP Quality Management System (QMS) activities, reviewing change control records, CAPA documentation, deviation reports, and audit readiness data in a regulated manufacturing environment.
Services

Quality Management System

We work with pharmaceutical teams to design, implement, and run effective Quality Management Systems, covering change control, CAPA, deviations, and audits to support consistent GMP compliance.

FAQ

1. What makes an ICSR valid for regulatory reporting?

An ICSR becomes valid when it includes an identifiable patient, an identifiable reporter, a suspected medicinal product, and a suspected adverse event.

2. When does day zero start in pharmacovigilance?

Day zero starts when any company employee or contracted partner first receives all four minimum ICSR validity criteria.

3. What ICSR evidence do inspectors usually request?

Inspectors commonly review source records, validity decisions, MedDRA coding, medical assessments, submission timestamps, E2B(R3) acknowledgements, follow-up attempts, duplicate checks, and audit trails.

References

Picture of Marco Klinger
Marco Klinger

Marco Klinger is Head of Quality Services at Zamann Pharma Support, where he leads consulting teams through complex regulatory and quality-driven projects. He brings more than 15 years of hands-on compliance experience across regulated industries. His work includes close collaboration with companies such as Reckitt, Sanofi, Biotech, Biotest, and others. Marco has deep expertise in medical device development, aseptic manufacturing, and the design, implementation, and management of complete quality management systems within GMP-regulated environments.