In the ever-evolving world of pharmacovigilance (PV), the accuracy and timeliness of Individual Case Safety Report (ICSR) submissions are critical to maintaining compliance and protecting patient safety. But not all submissions are created equal—E2B and non-E2B formats represent two distinct approaches with very different operational implications.
Whether you’re a PV specialist, quality lead, or regulatory affairs professional, understanding the difference between E2B and non-E2B submissions—and why it matters—is key to maintaining inspection readiness and global compliance.
What is an ICSR?
An Individual Case Safety Report (ICSR) is a structured report of an adverse event (AE) related to the use of a pharmaceutical product. It typically includes information about the patient, the drug, the adverse reaction, and the reporter.
ICSRs are submitted to health authorities (e.g., EMA, FDA, MHRA) to monitor drug safety in real-world use.
E2B Submissions: The Digital Standard
What is E2B?
E2B is an ICH (International Council for Harmonisation) guideline that defines the electronic format for exchanging ICSRs between stakeholders using standardised fields in XML format. It enables automated, efficient, and compliant electronic transmission of safety data.
Who Uses It?
- Regulatory agencies like EMA, FDA, PMDA, HC, TGA
- Marketing Authorisation Holders (MAHs)
- Contract Research Organisations (CROs)
- PV service providers
Key Features:
- Uses structured XML files
- Transmitted via gateway systems like EVWEB (Europe) and FDA ESG (US)
- Enables automation and validation before submission
- Facilitates large-scale data exchange across borders
Advantages:
- Faster and more secure data transfer
- Improved data quality through validation checks
- Supports regulatory harmonization (especially with E2B(R3))
Non-E2B Submissions: Still Relevant
What is a Non-E2B Submission?
Non-E2B ICSRs are those submitted manually, often via email, fax, or paper. They do not conform to the structured XML format and are usually in CIOMS or MedWatch form.
When Is It Used?
- When health authorities do not support E2B
- In early-phase clinical trials
- For literature cases where manual review is needed
- In post-marketing programs without E2B integration
- By smaller affiliates or partners without E2B capabilities
Examples:
- CIOMS I form for spontaneous AE reporting
- FDA Form 3500A for US paper submissions
Why It Matters: Compliance, Speed, and Scalability
Regulatory Expectations:
Health authorities increasingly expect E2B submissions—particularly E2B(R3)—as the standard. Non-compliance or delays in submission can result in audit findings, inspection citations, or product safety risks.
Operational Efficiency:
- E2B allows for automation, reducing manual errors and resource strain.
- Non-E2B processes often involve more human intervention, leading to inconsistencies.
Global Variability:
- EMA and FDA require E2B formats for post-marketing cases.
- Some local agencies still accept or prefer non-E2B formats.
- Global PV systems must support hybrid workflows to remain compliant.
Q&V Insight: Building an ICSR Submission Strategy That Works
At Q&V, we guide clients through building robust, scalable ICSR submission systems that meet evolving global requirements:
E2B and non-E2B submissions are not interchangeable—they serve different roles in the ICSR ecosystem. Understanding when and how to use each format ensures not just compliance but also faster, more effective pharmacovigilance.
Automating E2B workflows for high-volume case submissions
Managing non-E2B processes for local regulatory needs
Training teams on format-specific compliance standards
Auditing vendors for E2B/non-E2B submission capabilities
Upgrading systems to support E2B(R3) and XML validation
Contact Q&V to review your ICSR submission processes, evaluate E2B readiness, or streamline your global safety reporting today.