ICH E2D(R1): What the Updated ICSR Guidance Means for Medical Device and Drug Sponsors

FDA finalized its adoption of the revised ICH E2D(R1) guidance in March 2026, updating the global standard for postapproval individual case safety reporting. Here's what regulatory and clinical affairs teams need to know.

Background

The original ICH E2D guidance established the international framework for collecting and reporting Individual Case Safety Reports (ICSRs) after product approval. This revision — finalized at ICH Step 4 in September 2025 and adopted by FDA in March 2026 — modernizes that framework to reflect how safety information actually flows today: through digital platforms, patient support programs, social media, and real-world data sources that simply didn't exist when the original guidance was written.

While E2D is primarily a drug and biologic framework, the underlying definitions and case management principles have direct relevance for medical device sponsors navigating postmarket safety obligations, particularly those managing combination products or running postmarket clinical studies.

Key Updates Worth Your Attention

Digital platforms are now formally addressed. The guidance draws a clear line between platforms the MAH controls (your product website, branded app) and those it doesn't (social media, public forums). For platforms you own or operate, you are expected to screen regularly and the reporting clock starts the moment minimum ICSR criteria appear in a post — not when you find it. For third-party platforms, you're not required to actively monitor, but if you do so in a planned, systematic way, that activity becomes an Organized Data Collection System (ODCS) with its own documentation requirements.

The ODCS concept is central to the revision. Whether you're running a patient support program, a market research study, a noninterventional study, or a social listening program, if it's planned and systematic, it's an ODCS. That triggers specific documentation requirements: objectives, data sources, dataset scope, review methodology, and an AE/ADR collection process. This is important for sponsors who conduct post-approval registries or patient engagement programs — FDA now expects a defined process, not ad hoc review.

Patient Support Programs (PSPs) get their own section. PSPs are defined as MAH-initiated programs involving two-way communication with patients or HCPs. If any component of a combined program meets PSP criteria (e.g., a nurse hotline paired with home delivery), the entire program's AEs are managed as solicited reports requiring causality assessment. Sponsors using third-party vendors to run PSPs must have contractual agreements specifying AE reporting obligations and timelines.

Pregnancy and breastfeeding exposure reports have clearer follow-up expectations. MAHs are expected to follow up all pregnancy reports where embryo or fetal exposure is possible, collecting outcomes including newborn health and child development — unless the product is specifically indicated for use during pregnancy and no AE is present.

The minimum criteria for ICSR submission remain the same — identifiable patient, identifiable reporter, at least one suspect product, at least one AE/ADR or qualifying other observation — but the guidance tightens how identifiability is assessed for digital platform reports. A username or social media handle alone is not sufficient. You need at least one qualifying characteristic (age, sex, initials, etc.) to confirm a real person exists.

Reporting timelines are unchanged at 15 calendar days for expedited reports, but the guidance clarifies when Day Zero begins across different source types, including literature, digital platforms, and follow-up scenarios. Importantly, when you receive follow-up that reclassifies a case from nonserious to serious, the 15-day clock restarts from the date of that follow-up.

What This Means Practically

For sponsors running postmarket clinical studies or registries, the solicited report pathway applies — causality assessment is required, and AEs go into E2B format as "report from study." This is not new, but the guidance reinforces that secondary use of data (e.g., pulling from a claims database) does not generate ICSRs unless regional requirements say otherwise.

For sponsors with patient engagement programs, vendor contracts need to explicitly address AE reporting — timelines, hand-off processes, and who holds ultimate regulatory responsibility (always the MAH).

For regulatory affairs teams, the narrative requirements in Section 6.2 deserve attention. The guidance calls for a comprehensive, stand-alone medical story presented in the chronology of the patient's experience — not the chronology of when your team received the information. This is a meaningful quality standard for case documentation.

BSC's Perspective

The E2D(R1) revision reflects a broader FDA trend: standardizing expectations around real-world data sources while preserving the core principle that the MAH is ultimately accountable. The expansion to cover digital platforms and PSPs is practical and overdue, but it places new documentation burdens on sponsors who may not have formalized these activities as ODCSs.

If your organization runs any structured patient engagement, digital monitoring, or post-approval study activity, now is a good time to audit whether your SOPs and vendor agreements align with what E2D(R1) requires. BSC regularly supports clients in structuring postmarket study SAPs and safety reporting frameworks to meet these evolving standards.

Questions about how E2D(R1) applies to your postmarket program? Contact BSC to discuss your specific situation.