EudraVigilance Reporting: A Practical Guide to ICSR Submission

Introduction

EudraVigilance reporting is one of the most visible and heavily regulated pharmacovigilance activities performed by Marketing Authorisation Holders (MAHs).

Every day, thousands of Individual Case Safety Reports (ICSRs) are transmitted to EudraVigilance by pharmaceutical companies, regulators and other stakeholders.

While the technical process of transmitting a report may appear straightforward, maintaining compliance requires much more than simply pressing a submit button.

Organisations must ensure:

• Accurate case processing
• Appropriate coding
• Timely submissions
• Successful transmission
• Successful acceptance
• Ongoing reconciliation
• Effective oversight

Failures at any stage can result in regulatory non-compliance and inspection findings.

What is an ICSR?

An Individual Case Safety Report (ICSR) documents a suspected adverse reaction associated with a medicinal product.

A valid case generally requires:

• An identifiable patient
• An identifiable reporter
• A suspect medicinal product
• A suspected adverse reaction

Without these minimum criteria a report may not be considered valid for regulatory reporting purposes.

For an overview of EudraVigilance itself see:

[[what-is-eudravigilance]]

Regulatory Reporting Requirements

Within the European Union, MAHs are required to submit suspected adverse reactions to EudraVigilance in accordance with applicable legislation.

Reporting obligations may apply to:

• Serious adverse reactions
• Non-serious adverse reactions
• Follow-up information
• Literature cases
• Solicited reports

Requirements vary depending on the nature of the report and applicable regulations.

E2B(R3): The Foundation of Electronic Reporting

Modern EudraVigilance reporting relies on the ICH E2B(R3) standard.

E2B(R3) defines:

• Data structures
• Message formats
• Validation rules
• Mandatory fields

The standard allows safety information to be exchanged consistently between companies and regulators.

Without E2B(R3), large-scale electronic pharmacovigilance reporting would not be feasible.

EVWEB

EVWEB is the EMA web-based reporting platform.

It enables authorised users to:

• Create reports manually
• Submit reports
• Review acknowledgements
• Manage reporting activities

EVWEB is commonly used by:

• Smaller MAHs
• Organisations with lower reporting volumes
• Users requiring manual submission capability

Because EVWEB is browser-based, it generally requires less technical infrastructure than gateway reporting.

Gateway Reporting

Many larger organisations use automated gateway connections.

Gateway reporting allows:

• Direct system-to-system communication
• Automated report submission
• High-volume processing
• Reduced manual intervention

The process typically involves:

1. Case processing
2. E2B(R3) generation
3. Gateway transmission
4. Validation
5. Acknowledgement receipt

Gateway reporting improves efficiency but introduces additional technical governance requirements.

EVWEB Versus Gateway Reporting

Neither method is inherently superior.

The appropriate approach depends on organisational requirements and reporting volume.

Understanding Acknowledgements

One of the most common misunderstandings in pharmacovigilance reporting is the assumption that successful submission automatically means successful reporting.

In reality, submission is only one stage of the process.

After transmission, EudraVigilance validates the report and returns acknowledgement messages.

These acknowledgements indicate whether:

• The report was accepted
• The report was rejected
• Warnings were generated
• Further action is required

Why Acknowledgements Matter

A rejected report may never enter the regulatory database.

Failure to monitor acknowledgements can therefore result in:

• Missed reporting timelines
• Incomplete submissions
• Compliance failures
• Inspection findings

Organisations should maintain procedures describing how acknowledgements are reviewed and escalated.

Common Reasons for Rejection

Common validation issues include:

• Missing mandatory fields
• Invalid coding
• Product information errors
• Structural E2B(R3) issues
• Duplicate submissions

Trend analysis of validation failures can help identify underlying process weaknesses.

Follow-Up Reporting

Case information frequently evolves after initial submission.

Additional information may include:

• Outcome information
• Laboratory results
• Diagnostic confirmation
• Medical assessments

Follow-up reports ensure that regulators receive the most complete safety information available.

Nullifications and Amendments

Occasionally reports require correction.

Situations may include:

• Duplicate reports
• Administrative errors
• Invalid submissions

EudraVigilance provides mechanisms for:

• Amendments
• Corrections
• Nullifications

These processes help maintain data quality and regulatory accuracy.

Reporting Compliance Monitoring

Effective organisations monitor reporting performance continuously.

Typical metrics include:

• On-time reporting
• Late submissions
• Rejected reports
• Resubmission rates
• Acknowledgement review completion

Metrics help identify trends before they become regulatory issues.

Reconciliation Activities

Reconciliation verifies that submitted reports have been successfully transmitted, accepted and appropriately processed.

Reconciliation may compare:

• Internal databases
• Submission records
• EudraVigilance data
• Acknowledgement records

The objective is to identify discrepancies and ensure data integrity.

QPPV Oversight

The QPPV is not expected to submit individual reports personally.

However, regulators generally expect the QPPV to maintain oversight of reporting compliance.

This includes visibility of:

• Timeliness performance
• Significant deviations
• Reporting failures
• Escalations
• Compliance metrics

The QPPV should be informed of material issues that may affect regulatory compliance.

Inspection Perspective

Reporting activities are routinely reviewed during pharmacovigilance inspections.

Inspectors commonly examine:

• Reporting procedures
• Timeliness metrics
• Acknowledgement management
• Reconciliation activities
• Deviation handling
• Governance arrangements

Evidence demonstrating that the reporting process operates effectively is often as important as the process itself.

Common Inspection Findings

Frequently observed deficiencies include:

• Late reporting
• Failure to review acknowledgements
• Missing reconciliation activities
• Inadequate deviation management
• Poor oversight of outsourced reporting activities
• Insufficient compliance monitoring

Many findings arise because organisations focus on transmission while overlooking governance controls.

Key Takeaways

• EudraVigilance reporting is a core pharmacovigilance activity.
• E2B(R3) provides the foundation for electronic reporting.
• EVWEB and Gateway reporting are the primary submission methods.
• Successful submission does not necessarily mean successful acceptance.
• Acknowledgement management is essential.
• Reconciliation activities help ensure data integrity.
• QPPVs are expected to maintain oversight of reporting compliance.
• Reporting processes are routinely reviewed during inspections.

References

1. Regulation (EC) No 726/2004.
2. Directive 2001/83/EC.
3. Commission Implementing Regulation (EU) No 520/2012.
4. EMA Good Pharmacovigilance Practices (GVP) Module VI.
5. EMA EudraVigilance Electronic Reporting Guidance.
6. EMA EVWEB User Documentation.
7. ICH E2B(R3) Implementation Guide.
8. ICH E2D Post-Approval Safety Data Management.