From October 1, 2026, postmarketing Individual Case Safety Reports (ICSRs) for human drug products, biological products, and drug or biologic led combination products submitted to FDA via the Electronic Submissions Gateway Next Generation (ESG NextGen) must use the ICH E2B(R3) data standard. FDA will continue to accept E2B(R2) submissions through September 30, 2026, after which only E2B(R3) will be processed. The mandate was announced by FDA on April 6, 2026 (91 FR 17284) and extends the previously recommended transition by six months.
What is ICH E2B(R3)?
ICH E2B(R3) is the international data standard for electronic transmission of ICSRs between pharmaceutical companies and regulators. It defines the data elements, message structure, and XML schema that describe a single adverse event case: patient, product, reaction, narrative, seriousness, outcome, reporter, and regulatory processing metadata.
The guideline is built on the ISO/HL7 27953-2 ICSR standard, which makes E2B(R3) interoperable with clinical terminologies (MedDRA for reactions, ICH M5 for substance, UCUM for units). The current ICH implementation package (Implementation Guide, Q&As, and Appendix I(G) technical information) reached Step 4 of the ICH Process on July 18, 2025.
E2B(R3) replaces E2B(R2), the XML-based 2001 standard still used by most FDA submitters today. EMA already switched to E2B(R3) as mandatory for EudraVigilance on June 30, 2022. October 1, 2026 closes the transatlantic gap.
The October 1, 2026 deadline: what it covers
The FDA mandate, published as 91 FR 17284 on April 6, 2026, applies to:
- Postmarketing ICSRs for human drug products, biological products (including vaccines), and combination products where a drug or biologic is the primary mode of action
- Submissions sent through ESG NextGen (database to database gateway submissions)
E2B(R3) has been optional at FDA since January 16, 2024 for postmarketing reports and since April 1, 2024 for premarketing (IND study and IND exempt BA/BE study) reports (FDA E2B(R3) announcement, January 2023). After October 1, 2026, E2B(R2) will no longer be accepted through ESG NextGen.
Note that non-ICSR safety data (PSURs, DSURs, 15-day alert reports via paper MedWatch 3500A) are out of scope for the E2B transition. Those follow separate submission pathways.
Who must comply and what products are in scope
The mandate applies to every entity that submits postmarketing ICSRs to FDA's Adverse Event Monitoring System (AEMS, successor to FAERS) via ESG NextGen:
| Product type | In scope | Regulatory basis |
|---|---|---|
| Human drugs (NDA, ANDA) | Yes | 21 CFR 314.80, 314.98 |
| Biologics (BLA) | Yes | 21 CFR 600.80 |
| Vaccines | Yes (via VAERS interface) | 21 CFR 600.80 |
| Drug or biologic led combination products | Yes | 21 CFR Part 4 |
| Device led combination products | No (follow MDR and 21 CFR 803) | 21 CFR 803 |
| Nonprescription (OTC monograph) | Yes | 21 CFR 314.80 |
Marketing authorization holders, applicants, licensed manufacturers, and their authorized agents are all affected. Contract safety and CRO partners that submit ICSRs on behalf of sponsors must also transition their systems.
E2B(R2) vs E2B(R3): key differences
| Area | E2B(R2) (2001) | E2B(R3) (current) |
|---|---|---|
| Underlying standard | ICH-specific XML | ISO/HL7 27953-2 ICSR |
| Data elements | Approximately 200 | Approximately 470 |
| Narrative structure | Single free-text block | Structured narrative with case summary, reaction episodes, drug history |
| Terminology | MedDRA only | MedDRA, EDQM, UCUM, ISO 3166, IDMP substance identifiers |
| Acknowledgment | MSH segment | Full ICSR ACK message with validation results |
| Duplicate detection | Limited fields | Expanded worldwide unique case identifier logic |
| Backwards compatibility | N/A | Documented in Appendix to the Implementation Guide (Step 4) |
The additional data elements are not decorative. E2B(R3) captures parent-child cases for maternal exposure, detailed device-drug combination data, structured dose regimens, and richer reporter hierarchies. Converting legacy E2B(R2) cases into E2B(R3) requires mapping rules documented in FDA's Regional Implementation Guide.
Submission paths and technical requirements
FDA offers two submission paths for E2B(R3) ICSRs:
ESG NextGen (database to database)
The primary pathway for sponsors with a safety database. Submitters transmit XML messages over AS2 or the SOAP-based NextGen API. This path requires:
- An active ESG NextGen account with a production certificate
- A safety database (Argus, ArisG, Veeva Vault Safety, or equivalent) configured to output E2B(R3) XML per the FDA Regional Implementation Guide
- Validation of outbound files against FDA E2B(R3) Core and Regional Data Elements and Business Rules
- Processing of inbound ICSR ACK messages to confirm receipt and validation status
Safety Reporting Portal (SRP)
For submitters without database-to-database capability, FDA continues to offer the web-based Safety Reporting Portal. SRP generates E2B(R3) compliant XML from manually entered case data. This path remains available after October 1, 2026 and is the practical option for small manufacturers, investigator-initiated submissions, and one-off reports.
Try this in RegAid: What ICSR data elements are mandatory under FDA E2B(R3)?
How to prepare before October 1, 2026
-
Confirm your scope. Identify every product, license, and agent submission stream currently sending E2B(R2) ICSRs to FDA. Include postmarketing, IND, and BA/BE premarketing streams.
-
Upgrade or reconfigure your safety database. Vendors have released E2B(R3) capable versions, but reconfiguration is non-trivial. Budget time for field mapping, narrative restructuring, and MedDRA version alignment.
-
Validate against FDA's test environment. Use the FDA E2B(R3) Validator and the ESG NextGen pre-production environment to validate outbound XML before go-live. Common validation failures: incorrect country codes, missing worldwide unique case identifiers, invalid MedDRA versions, truncated narratives.
-
Train your case processors and vendors. Structured narrative fields are the biggest workflow change. Processors must learn to decompose a single free-text narrative into case summary, reaction episodes, and drug history fields.
-
Run parallel submissions. Between now and October 1, 2026, submit a sample of cases in both E2B(R2) and E2B(R3) to confirm end-to-end processing and identify discrepancies before the hard cutoff.
-
Document the transition in your PSMF. Update your Pharmacovigilance System Master File (Module III, Sources of Safety Data, and Module IV, Computerized Systems) to reflect the new data flow, validation controls, and retention of legacy E2B(R2) archives.
-
Review contracts with CRO and safety outsourcing partners. Confirm they are E2B(R3) ready on the same timeline, and that service level agreements cover validation failures and resubmission responsibilities.
Common pitfalls
Underestimating MedDRA version management: E2B(R3) requires that the MedDRA version used for coding is transmitted with each case. Safety databases that auto-upgrade MedDRA without maintaining per-case version history will produce non-conforming files.
Ignoring the ACK message: E2B(R3) introduces a richer acknowledgment with validation results. Submitters who do not parse and act on ACKs risk undetected processing failures after the deadline.
Skipping combination product analysis: Drug-led combination products fall under the E2B(R3) mandate, but device-led combinations do not. Map each product against 21 CFR Part 4 to route ICSRs correctly.
Assuming EMA parity is enough: If your organization already submits E2B(R3) to EudraVigilance, you are not automatically FDA compliant. FDA regional data elements and business rules differ from EU. Validate against FDA's rule set specifically.
Key takeaways
- FDA requires ICH E2B(R3) for postmarketing ICSRs via ESG NextGen from October 1, 2026, per 91 FR 17284
- E2B(R2) is accepted through September 30, 2026, then retired from the gateway
- In scope: human drugs, biologics, vaccines, and drug or biologic led combination products
- E2B(R3) adds structured narrative, richer combination product data, and ISO/HL7 based interoperability
- Two submission paths remain: ESG NextGen for database submitters, Safety Reporting Portal for manual submitters
- Start validation against the FDA pre-production environment now, and run parallel E2B(R2)/E2B(R3) submissions before the cutoff
How RegAid helps
RegAid covers the full FDA guidance package for E2B(R3), the ICH Implementation Guide, FDA Regional Implementation Guide, and the underlying 21 CFR 314.80 and 600.80 postmarketing reporting rules. Ask "Which ICSR data elements are mandatory for FDA E2B(R3)?" or "How do I map an E2B(R2) case into E2B(R3)?" and get a cited answer with links to the FDA guidance and ICH source documents.