ICH's individual case safety report guideline had not moved since it reached Step 4 in November 2003. E2D(R1) changes that: the European Medicines Agency adopted the revision at Step 5 on September 18, 2025, applicable in the EU from March 18, 2026, and FDA followed with its own final guidance in early March 2026, replacing the 2003 original it had relied on for more than two decades. The headline change is not a new definition of "serious" or "unexpected" — it is guidance on data sources the 2003 guideline never had to classify: patient support programs, market research programs, and digital-platform monitoring.

What E2D(R1) actually revises

The original E2D set the baseline still in use across every region: the minimum criteria for a reportable case — an identifiable patient, an identifiable reporter, a suspect product, and an adverse event — and the definitions of adverse drug reaction, serious, and unexpected that every downstream report depends on. E2D(R1) keeps that architecture and updates it for how safety data actually arrives at a company today. The draft went out for public consultation in February 2024, reached Step 4 on September 15, 2025, and has now cleared implementation in the two regions that move first. For a new drug application or an approved product generating real-world safety signals, the practical question is no longer just what counts as a case — it is which of your existing data streams your SOPs were never built to classify.

Nov 2003
The original E2D's Step 4 date — unrevised for more than two decades until now.
Mar 18, 2026
E2D(R1) applicable in the EU, per EMA's Step 5 adoption.
FDA-2024-D-0803
FDA's final guidance docket, replacing the September 2003 guidance it supersedes.

The data-source problem the 2003 guideline never addressed

The substantive addition in E2D(R1) is guidance on two sources of case data that barely existed as formal categories in 2003. First, non-interventional studies — both studies that collect safety data directly and those that make secondary use of data collected for another purpose — now have explicit guidance on when a case arising from them meets the threshold for an individual case safety report. Second, ICH Code List 8 gains new values under data element C.5.4 specifically to classify solicited reports coming from patient support programs, market research programs, and digital-platform data collection. Companies that run patient support programs or monitor social and digital channels for safety signals have been making ad hoc classification calls for years; E2D(R1) gives those calls a standard structure for the first time.

  • Non-interventional study data. New guidance distinguishes primary data collection from secondary use of existing data when deciding whether a case is reportable — a distinction the 2003 guideline left to regional interpretation.
  • Patient support programs. Now explicitly addressed under the revised Code List 8 values, rather than treated as a market-access or global regulatory strategy activity adjacent to pharmacovigilance.
  • Market research and digital-platform data. The same new data-element values extend to solicited reports surfaced through market research and digital or social-platform monitoring — sources most 2003-era SOPs route inconsistently, if at all.
  • EU rollout is staged. The new Code List 8 values take effect in the EU through EudraVigilance change management on its own timeline, separate from E2D(R1)'s own March 2026 applicability date — confirm both dates rather than assuming they match.
The 2003 guideline told you how to recognize a case. E2D(R1) tells you what to do with a case that arrived from a source the 2003 guideline never had to name. Why the data-source guidance is the real change

What E2D(R1) does not change

FDA's 15-calendar-day expedited reporting requirement for serious, unexpected adverse drug experiences is set in regulation — 21 CFR 314.80 for drugs, 21 CFR 600.80 for biologics — not in ICH guidance. E2D(R1) informs how FDA expects sponsors to define and classify cases under those existing regulations; it is guidance, and guidance does not amend the underlying reporting deadline. The same separation holds for a biologics license application program running parallel EU and US safety streams: the classification standard moved, but the submission clocks it feeds did not.

A readiness sequence for the E2D(R1) transition
  1. Map your case sources. Identify every stream — patient support programs, market research, digital monitoring, non-interventional studies — against the new Code List 8 values.
  2. Confirm regional adoption. Live in the EU since March 2026; FDA guidance finalized; verify any other region before changing processing logic there.
  3. Revise intake SOPs. Build explicit classification criteria for non-interventional study data and solicited reports from the newly named sources.
  4. Trace it downstream. Confirm the revised case data still reconciles cleanly into your DSUR and PBRER outputs.

None of this requires rebuilding a safety system. It requires recognizing that the individual case safety report standard underneath the PBRER's integrated benefit-risk analysis and the DSUR's annual safety reporting has changed for the first time in over twenty years, and that the change is aimed squarely at data sources most pharmacovigilance groups already have and have never formally classified. Programs that treat the pharmacovigilance plan as the only document E2D(R1) touches will miss where the actual case-intake work now sits.

Frequently asked questions

What actually changed in E2D(R1) versus the original 2003 guideline?

E2D(R1) updates the definitions and standards for managing and reporting individual case safety reports and, more substantively, adds guidance on when cases from non-interventional studies — both primary data collection and secondary use of existing data — qualify as reportable ICSRs. It also introduces new values under ICH Code List 8's data element C.5.4 to classify solicited reports coming from patient support programs, market research programs, and digital-platform data collection: sources the 2003 original did not contemplate as a formal category.

Is E2D(R1) already in effect?

In the EU, yes. The European Medicines Agency adopted E2D(R1) at Step 5 on September 18, 2025, with application in the EU framework from March 18, 2026. FDA published its own final guidance adopting E2D(R1), replacing the September 2003 guidance it supersedes, in early March 2026. Confirm the implementation status in any other region where you submit before assuming the revised standard applies there yet.

Does E2D(R1) change FDA's 15-calendar-day expedited reporting deadline?

No. The 15-calendar-day expedited reporting timeline for serious, unexpected adverse drug experiences comes from FDA's own regulations at 21 CFR 314.80 and 600.80, not from the ICH guideline. E2D(R1) is FDA guidance that informs how the agency expects sponsors to define and classify cases under those existing regulations — it does not itself amend the regulatory deadline.

Sources & further reading

  1. FDA. E2D(R1) Postapproval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports — Guidance for Industry. fda.gov
  2. EMA. ICH E2D(R1) — Post-approval safety data management: scientific guideline. ema.europa.eu
  3. ICH. E2D(R1) guideline and work plan. ich.org

This article is provided for general informational purposes and reflects the regulatory landscape as of October 2026. It is not legal or regulatory advice. Confirm current ICH E2D(R1) implementation status in your submission regions with FDA, EMA, or qualified counsel before acting.