How ICH E2A to E2F Guidelines Shape Pharmacovigilance in 2026

The ICH guidelines for pharmacovigilance are the E2 series, six harmonised guidelines that give companies and regulators a common language for drug safety: E2A covers expedited reporting in clinical trials, E2B(R3) the electronic case format, E2C(R2) the periodic benefit-risk evaluation report (PBRER), E2D(R1) post-approval case management, E2E pharmacovigilance planning and E2F the development safety update report (DSUR).

Indeed, EudraVigilance alone collected and managed around 1.77 million individual case safety reports (ICSRs) in 2025. ICH E2 provides the harmonised recommendations behind that exchange; however, each regulator’s implementation documents decide which version and regional requirements apply. This guide therefore maps each E2 document to the safety question it answers and notes where EU and FDA rules differ. For a stronger foundation, you can study the core concepts of pharmacovigilance with Pharmuni.

Table of Contents

The Organisation Behind ICH Guidelines for Pharmacovigilance

The International Council for Harmonisation (ICH) created these guidelines. ICH brings together regulators and industry experts from the EU, US, Japan, and other regions. Together, they design global standards that simplify drug development and safety reporting.
The E2 recommendations focus on how companies collect, evaluate, and report safety data.

They help teams manage patient risks and ensure consistent formats across regulatory regions. Additionally, the guidelines protect public health because they support transparent communication about safety events and product risks.

Who Applies the ICH Pharmacovigilance Guidelines?

Companies apply these guidelines during clinical trials and post-marketing phases. They cover any activity that involves monitoring, detecting, assessing, and reporting adverse events. Therefore, they apply to:

  • Sponsors running clinical studies

  • MAHs (Marketing Authorisation Holders)

  • Contract Research Organisations (CROs)

  • Global safety teams that manage ICSRs

  • Regulators that adopt ICH guidelines, such as those in the EU, the US and Japan

Before applying a guideline, check that regulator’s implementation documents for the version in force.

The ICH E2 Guidelines at a Glance

Guideline Focus Adoption / version note
E2A
Clinical safety data management: definitions and expedited reporting
Step 4, October 1994
E2B(R3)
Data elements and message format for electronic ICSRs (replaced E2B(R2))
Initial Step 4, November 2012; technical implementation package version 1.11, January 2026
E2C(R2)
Periodic Benefit-Risk Evaluation Report (PBRER)
Step 4, November 15, 2012; corrected version, December 17, 2012
E2D(R1)
Post-approval ICSR definitions, management and reporting
Step 4, September 2025
E2E
Pharmacovigilance planning: Safety Specification and Pharmacovigilance Plan
Step 4, November 2004
E2F
Development Safety Update Report (DSUR)
Step 4, August 2010
Follow the ICH E2 roadmap from first adverse event to long-term safety review.
One timeline, six guidelines – your quick guide to ICH E2 for pharmacovigilance

E2A – Clinical Safety Data Management: Definitions and Standards for Expedited Reporting

E2A defines core terms such as adverse event, adverse drug reaction, unexpected adverse drug reaction and serious adverse event. It also sets expedited timelines for clinical trials: fatal or life-threatening unexpected ADRs should reach regulators no later than 7 calendar days after the sponsor first learns of them, followed by as complete a report as possible within 8 additional days. Other serious, unexpected ADRs must be reported no later than 15 calendar days.

At minimum, an initial report needs an identifiable patient, a suspect medicinal product, an identifiable reporting source and a serious, unexpected event with a reasonable suspected causal relationship to the product.

Download E2A PDF Here

E2B(R2) and E2B(R3) – Electronic Transmission of Individual Case Safety Reports (ICSRs)

These guidelines define the electronic structure of ICSRs: the data fields, the message format and how reports are transmitted to regulators. E2B(R3) is the current version, while E2B(R2) is now mainly of historical interest. Its technical implementation package is updated separately, so check the current version, 1.11 since January 2026, before configuring a safety database.

Download E2B(R2) PDF here (2001, historical)

Download View the official E2B(R3) guideline and implementation documents Here

E2C(R2) – Periodic Benefit-Risk Evaluation Report (PBRER)

E2C(R2) reached Step 4 on November 15, 2012, with corrections dated December 17, 2012. It recommends the PBRER format for the periodic, cumulative evaluation of an authorised product’s benefit-risk profile. However, regional requirements still determine what must be submitted and when, and the term periodic safety update report (PSUR) remains in use in regional frameworks such as the EU.

Download E2C(R2) PDF here

E2D(R1) – Post-Approval Safety Data: Definitions and Standards for ICSR Management and Reporting

E2D, finalised in November 2003, applied the E2A definitions to post-approval safety reporting. Its revision, E2D(R1), reached Step 4 on 15 September 2025 and sets definitions and standards for managing and reporting post-approval ICSRs, including good case management practices. Regional timelines still differ, so marketing authorisation holders must also follow local requirements.

Download the final ICH E2D(R1) guideline (2025) here

E2E and E2F Pharmacovigilance Planning and Development Safety Update Reports

The E2 series does not stop at individual case reporting. Two further guidelines shape how sponsors plan safety work and summarise it during development.

E2E – Pharmacovigilance Planning

E2E reached Step 4 in November 2004. It helps companies plan pharmacovigilance activities, especially for the early post-marketing period of a new drug. Its two building blocks are the Safety Specification and the Pharmacovigilance Plan, which a sponsor may submit at the time of the licence application. The Safety Specification summarises the important identified risks, important potential risks and important missing information, including populations that were not studied before approval. The Pharmacovigilance Plan then describes the activities proposed to address those risks and gaps.

E2F – Development Safety Update Report (DSUR)

E2F reached Step 4 in August 2010. It sets a common standard for periodic safety reporting on drugs under development, including marketed drugs that are still being studied. The DSUR is an annual review, and its reporting period starts from the Development International Birth Date (DIBD), which is the sponsor’s first authorisation to conduct a clinical trial in any country. Its main focus is data from interventional clinical trials.

Together, these two guidelines complete the lifecycle view: E2A covers urgent case reports during trials, E2F adds a yearly review of the same development programme, and E2E prepares the risk plan that carries the product into the market.

Choose the Right ICH E2 Guideline for Each Safety Question

Start with the decision you need to make rather than the abbreviation; the table below matches common safety questions to the E2 document that addresses them.

Safety question Start with
Does a serious, unexpected reaction in a clinical trial need expedited reporting?
E2A, plus regional rules
How should the development programme’s safety be reviewed each year?
E2F (DSUR)
How should a post-approval case be managed and reported?
E2D(R1)
How should the case be structured for electronic transmission?
E2B(R3)
Has the authorised product’s overall benefit-risk balance changed?
E2C(R2) (PBRER)
What safety information is missing, and how will it be obtained?
E2E

From ICH E2 to Regional Pharmacovigilance Rules

Global teams use ICH as the base, but each regulator turns it into binding regional rules. In the EU, GVP Module VI requires marketing authorisation holders to submit valid serious ICSRs, whether they occur inside or outside the EU, to EudraVigilance within 15 days of receipt; valid non-serious ICSRs occurring in the EU are due within 90 days.

In the US, 21 CFR Parts 312 and 314 set the timelines for IND and postmarketing safety reports. Other ICH members, such as Japan’s MHLW/PMDA and Health Canada, implement the E2 guidelines through their own national requirements.

See how ICH E2 connects with EMA GVP and FDA safety rules at a glance.
Global base, regional detail – mapping ICH pharmacovigilance to EU and US requirements

Link Between ICH E2 and FDA Safety Requirements

FDA aligns closely with ICH E2, but US regulations set the binding timelines and formats:

  • IND safety reports: under 21 CFR 312.32(c)(1), sponsors notify FDA and all participating investigators of potential serious risks within 15 calendar days of determining that the information qualifies. Unexpected fatal or life-threatening suspected adverse reactions must reach FDA within 7 calendar days of the sponsor’s initial receipt of the information.
  • Postmarketing 15-day Alert reports: applicants must report each serious and unexpected adverse drug experience, foreign or domestic, within 15 calendar days (21 CFR 314.80).
  • Electronic format: FDA’s former FAERS database is now the FDA Adverse Event Monitoring System (AEMS). Since 1 October 2026, postmarketing ICSRs sent through ESG NextGen must use E2B(R3). Since 1 April 2026, commercial IND sponsors must also submit IND safety reports under 21 CFR 312.32(c)(1)(i) in E2B(R3); noncommercial sponsors are exempt.

How the EU and FDA Are Implementing ICH E2D(R1)

In the EU, E2D(R1) became effective on March 18, 2026. EMA’s implementation information, however, separates the guideline’s application from the later introduction of new E2B(R3) code-list values in EudraVigilance, so updates to submissions should follow the published EU instructions.

FDA issued its own E2D(R1) guidance on March 6, 2026, and its AEMS data standards page confirms that FDA now accepts new study-type values for patient support programmes, market research programmes and organised data collection systems using digital platforms. That said, acceptance by FDA does not mean EudraVigilance accepts the same values.

Keep a Separate Record of Regional E2 Implementation

A simple implementation record keeps four things apart: the ICH revision, the regulator’s implementation date, the current technical package and the approved internal procedure, each with its source. Otherwise, an old adoption date can be mistaken for proof that a database is current.

For example, an intake procedure for patient support programme cases may need both E2D(R1) terminology and the authority’s current E2B(R3) instructions. Name who tracks regulatory changes and who approves updates, and date the decision even when nothing changes.

Final Words

The ICH guidelines for pharmacovigilance give safety teams a shared standard, yet 2026 has shown how much still depends on regional implementation: E2D(R1) took effect in the EU in March, and FDA moved postmarketing ICSRs to E2B(R3) in October. The volume behind these standards keeps growing, too, as WHO’s VigiBase now holds more than 40 million case reports from over 160 countries. Treat each E2 document as the starting point, then confirm the regional version before acting on it. To plan your own next steps, explore the pharmacovigilance career path.

FAQs

1️⃣ Which ICH E2 guidelines matter most for drug safety work?

The key E2 guidelines are E2A, E2B(R3), E2C(R2), E2D(R1), E2E and E2F. E2A and E2D(R1) cover expedited and post-approval case reporting, E2B(R3) defines the electronic ICSR format, E2C(R2) covers the PBRER, E2E covers pharmacovigilance planning, and E2F covers the DSUR.

ICH E2 sets the global base, while EMA GVP and FDA regulations add regional details such as timelines, formats, and system requirements.

3️⃣ Does every regulator apply the ICH E2 guidelines in the same way?

No two regulators apply them in exactly the same way. ICH E2 provides harmonised recommendations, so check the relevant regulator’s implementation documents to establish which version and regional requirements apply to the activity.

 

4️⃣What is the difference between ICH E2A and E2D(R1)?

E2A covers clinical safety data management and expedited reporting during clinical development, including 7- and 15-calendar-day timelines for serious, unexpected adverse drug reactions. E2D(R1) applies the same type of definitions to the post-approval phase and sets standards for managing and reporting individual case safety reports from post-marketing sources.

References
Picture of Ershad Moradi
Ershad Moradi

Ershad Moradi, a Content Marketing Specialist at Zamann Pharma Support, brings 6 years of experience in the pharmaceutical industry. Specializing in pharmaceutical and medical technologies, Ershad is currently focused on expanding his knowledge in marketing and improving communication in the field. Outside of work, Ershad enjoys reading and attending industry related networks to stay up-to-date on the latest advancements. With a passion for continuous learning and growth, Ershad is always looking for new opportunities to enhance his skills and contribute to pharmaceutical industry. Connect with Ershad on Facebook for more information.

Share