QPPV.COM

What is EudraVigilance?

A comprehensive introduction to EudraVigilance, electronic safety reporting, EVWEB, E2B(R3), case downloads and the role of EudraVigilance within the European pharmacovigilance system.

Audio Lesson 12 min

What is EudraVigilance?

Introduction

EudraVigilance is the European Union system for managing and analysing information relating to suspected adverse reactions associated with medicinal products.

Operated by the European Medicines Agency (EMA), EudraVigilance serves as the central repository for Individual Case Safety Reports (ICSRs) submitted by marketing authorisation holders, sponsors, national competent authorities and other authorised stakeholders throughout the European Economic Area (EEA).

Although many pharmacovigilance professionals associate EudraVigilance primarily with adverse event reporting, its role extends far beyond the submission of individual cases.

EudraVigilance supports:

Virtually every major pharmacovigilance process performed by a Marketing Authorisation Holder ultimately interacts with EudraVigilance either directly or indirectly.

For Qualified Persons Responsible for Pharmacovigilance (QPPVs), understanding EudraVigilance is essential because reporting compliance, signal management, governance oversight and inspection readiness all depend on effective operation of the system.

Why EudraVigilance Exists

Before EudraVigilance was established, adverse reaction reporting across Europe was fragmented.

Individual Member States maintained separate reporting systems and regulators often had limited visibility of safety information originating outside their own jurisdictions.

This created several challenges:

As medicinal products became increasingly global and regulatory cooperation expanded, a centralised European pharmacovigilance database became necessary.

EudraVigilance was developed to provide:

Today it functions as one of the largest medicinal product safety databases in the world and forms a cornerstone of the European pharmacovigilance framework.

EudraVigilance operates under European pharmacovigilance legislation.

The principal legal foundations include:

Operational expectations are further described within:

Together these requirements establish obligations relating to electronic reporting, pharmacovigilance system governance, signal management and regulatory compliance.

EudraVigilance Within the European Pharmacovigilance System

EudraVigilance is not an isolated database.

It functions as a central component of the wider European pharmacovigilance ecosystem.

Key stakeholders interacting with EudraVigilance include:

Information submitted by one stakeholder may subsequently support signal detection, regulatory assessment, benefit-risk evaluation or safety actions undertaken by another.

The database therefore acts as shared regulatory infrastructure rather than merely a reporting destination.

What Information is Stored in EudraVigilance?

Individual Case Safety Reports

The primary content of EudraVigilance consists of Individual Case Safety Reports.

An ICSR documents a suspected adverse reaction associated with the use of a medicinal product.

A valid case generally requires:

Without these minimum elements, a report may not qualify as a valid case for pharmacovigilance reporting purposes.

Serious Adverse Reactions

Serious adverse reactions include events that result in:

These reports are subject to expedited reporting requirements and frequently receive increased regulatory attention.

Non-Serious Adverse Reactions

European pharmacovigilance legislation also requires reporting of non-serious adverse reactions.

Although individually less significant than serious cases, non-serious reports contribute substantially to signal detection and population-level safety surveillance.

Follow-Up Information

Additional information frequently becomes available after the initial report has been received.

Examples include:

Follow-up reporting improves case quality and supports more accurate safety evaluation.

Amendments and Nullifications

Occasionally reports require correction.

EudraVigilance supports:

These functions help maintain data quality and regulatory accuracy.

EudraVigilance Architecture

Understanding how EudraVigilance operates helps explain how safety information moves through the European pharmacovigilance system.

Marketing Authorisation Holders

Marketing Authorisation Holders are responsible for collecting and reporting suspected adverse reactions associated with their products.

Most MAHs interact with EudraVigilance through either:

The approach adopted depends largely on organisational size, technical capability and reporting volume.

National Competent Authorities

National Competent Authorities contribute reports, review safety information and participate in signal management activities supported by EudraVigilance.

European Medicines Agency

The EMA operates and maintains EudraVigilance.

Responsibilities include:

Clinical Trial Sponsors

Sponsors may also interact with EudraVigilance depending on applicable reporting requirements and study activities.

Signal Management Users

Safety scientists, epidemiologists and signal detection teams use EudraVigilance-derived information to identify and evaluate potential safety concerns.

E2B(R3) and Electronic Reporting

What is E2B(R3)?

E2B(R3) is the internationally recognised standard used for electronic transmission of Individual Case Safety Reports.

Developed through the International Council for Harmonisation (ICH), E2B(R3) defines:

The standard enables consistent exchange of safety information between companies and regulators.

Why E2B(R3) Matters

Without a common reporting standard, electronic pharmacovigilance reporting would be difficult to validate, analyse and exchange.

E2B(R3) supports:

It forms the technical foundation of modern pharmacovigilance reporting.

EVWEB

EVWEB is the web-based reporting interface provided by the EMA.

It allows authorised users to:

EVWEB is particularly useful for organisations with relatively low reporting volumes.

Gateway Reporting

Larger pharmaceutical companies commonly use automated gateway connections to exchange E2B(R3) messages with EudraVigilance.

Advantages include:

Gateway reporting is generally preferred when reporting volumes become substantial.

Gateway Risks

Despite its advantages, gateway reporting introduces technical risks.

Examples include:

These risks require ongoing monitoring and governance.

Understanding EudraVigilance Acknowledgements

Submitting a report does not automatically mean it has been successfully accepted.

After submission, EudraVigilance performs validation checks and generates acknowledgement messages.

These acknowledgements indicate whether a report has:

Failure to review acknowledgements can result in unnoticed submission failures and subsequent compliance issues.

Typical Reporting Lifecycle

A simplified reporting lifecycle includes:

Stage Description
Submission Report transmitted
Validation Technical checks performed
Acknowledgement System response generated
Acceptance or Rejection Outcome determined
Follow-Up Actions Corrections performed if required

Common Validation Errors

Frequently observed issues include:

Monitoring validation failures helps organisations identify weaknesses within reporting processes and implement corrective actions.

!!! note

Successful pharmacovigilance reporting requires both successful transmission and successful acceptance. Submission statistics alone do not necessarily demonstrate compliance.

Downloading Cases from EudraVigilance

Many pharmacovigilance professionals focus primarily on submitting reports. However, receiving information from EudraVigilance is equally important.

Marketing Authorisation Holders may access reports relating to their products to support ongoing safety surveillance activities.

Downloaded reports support:

These reports may include information not otherwise available through internal reporting channels.

Level 2A Access

Level 2A access supports product-specific pharmacovigilance activities.

Typical uses include:

Users commonly include:

Level 2B Access

Level 2B access provides broader data access for signal management and analytical activities.

Typical users include:

Common uses include:

Reconciliation Activities

Downloaded cases should be reconciled appropriately against internal safety systems where applicable.

Reconciliation activities help identify:

Failure to perform effective reconciliation remains a common inspection concern.

!!! inspection

Inspectors frequently assess whether organisations maintain documented reconciliation procedures and whether discrepancies are investigated and resolved appropriately.

For additional information see:

Medical Literature Monitoring (MLM)

Medical Literature Monitoring (MLM) is an EMA programme under which selected scientific literature is centrally monitored for specific active substances.

Historically, every Marketing Authorisation Holder was responsible for independently screening scientific literature for potential adverse reactions. This often resulted in duplication of effort, inconsistent case identification and increased resource requirements across the pharmaceutical industry.

To improve efficiency and consistency, the EMA introduced the MLM programme.

For substances included within the programme, the EMA:

Marketing Authorisation Holders may subsequently download these cases and incorporate them into their routine pharmacovigilance activities.

The MLM programme does not remove all literature surveillance obligations. Organisations remain responsible for understanding the scope of EMA monitoring and ensuring that literature outside programme coverage is appropriately monitored.

For a detailed discussion see:

[[medical-literature-monitoring]]

EudraVigilance Data Analysis System (EVDAS)

The EudraVigilance Data Analysis System (EVDAS) is the analytical environment built upon EudraVigilance data.

Where EudraVigilance functions as the repository for adverse reaction reports, EVDAS provides tools that allow regulators and Marketing Authorisation Holders to analyse those reports and identify potential safety concerns.

EVDAS supports:

Many routine signal management activities rely heavily on EVDAS outputs.

One of the most widely used outputs is the electronic Reaction Monitoring Report (eRMR), which provides structured summaries of reporting patterns and potential safety signals.

EVDAS has become an important component of modern signal management and plays a significant role in supporting compliance with GVP Module IX.

For a detailed discussion see:

[[evdas-and-signal-detection]]

XEVMPD

The eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD) is the European database containing structured medicinal product information.

Although less visible than adverse event reporting activities, XEVMPD plays an important role within the wider EudraVigilance ecosystem.

Accurate product information supports:

Typical information stored within XEVMPD includes:

Maintaining accurate product information is an important compliance responsibility because errors in product data may affect downstream pharmacovigilance activities.

For a detailed discussion see:

[[xevmpd-guide]]

Registration and Access Management

Access to EudraVigilance is controlled by the European Medicines Agency.

Organisations must complete registration activities before production access is granted.

Typical activities include:

User access should be governed through documented procedures and maintained throughout the user lifecycle.

Good access management typically includes:

Weak access governance may create compliance, security and data integrity risks.

For a detailed discussion see:

[[eudravigilance-registration-and-access]]

QPPV Responsibilities Relating to EudraVigilance

The QPPV is not expected to personally process every case or operate EudraVigilance on a day-to-day basis.

However, regulators generally expect the QPPV to maintain oversight of how EudraVigilance-related activities are performed within the pharmacovigilance system.

The QPPV should understand:

Oversight of Reporting Compliance

Reporting compliance remains one of the most important areas of QPPV oversight.

This includes visibility of:

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

Oversight of Signal Management

Signal detection and evaluation activities frequently rely on EudraVigilance and EVDAS data.

The QPPV should understand:

Although the QPPV may not personally review every signal, effective oversight remains essential.

Oversight of Outsourced Activities

Many organisations outsource activities associated with EudraVigilance.

Examples include:

Outsourcing does not transfer accountability.

The QPPV should understand how outsourced activities are monitored and controlled.

Oversight of Access Governance

The QPPV should have confidence that:

These controls support data integrity and regulatory compliance.

Inspection Perspective

EudraVigilance-related activities are routinely reviewed during pharmacovigilance inspections.

Inspectors are generally interested not only in procedures but also in evidence that those procedures operate effectively in practice.

Common inspection focus areas include:

Inspectors may review documentation, system records, metrics and examples of completed activities.

Reporting Timeliness

Inspectors frequently assess whether reports are submitted within required regulatory timelines.

This may include review of:

Reporting Accuracy

Inspectors may compare submitted reports against source documentation to verify:

Reconciliation Activities

Reconciliation procedures are often reviewed to ensure that downloaded reports are appropriately identified, processed and tracked.

Signal Management Activities

Inspection review may include:

Inspectors generally expect evidence demonstrating that signal management processes are active and effective.

Key Takeaways

References

  1. Regulation (EC) No 726/2004 of the European Parliament and of the Council.
  2. Directive 2001/83/EC on the Community Code Relating to Medicinal Products for Human Use.
  3. Commission Implementing Regulation (EU) No 520/2012.
  4. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
  5. EMA Good Pharmacovigilance Practices (GVP) Module II – Pharmacovigilance System Master File.
  6. EMA Good Pharmacovigilance Practices (GVP) Module VI – Collection, Management and Submission of Reports of Suspected Adverse Reactions to Medicinal Products.
  7. EMA Good Pharmacovigilance Practices (GVP) Module IX – Signal Management.
  8. EMA EudraVigilance Registration Manual.
  9. EMA EudraVigilance Electronic Reporting Guidance.
  10. EMA EudraVigilance Data Analysis System (EVDAS) User Guide.
  11. EMA Medical Literature Monitoring Guidance.
  12. EMA XEVMPD Guidance Documents.
  13. ICH E2B(R3) Electronic Transmission of Individual Case Safety Reports Implementation Guide.
  14. ICH E2D Post-Approval Safety Data Management.
  15. EMA EudraVigilance System Overview Documentation.

Related Articles

EudraVigilance Reporting: A Practical Guide to ICSR Submission

Understanding EudraVigilance reporting requirements, reporting pathways, acknowledgements and compliance expectations from a pharmacovigilance perspective.

Medical Literature Monitoring in Pharmacovigilance

Understanding Medical Literature Monitoring, EMA responsibilities, MAH obligations, literature surveillance and pharmacovigilance compliance requirements.

XEVMPD Guide for Pharmacovigilance Professionals

Understanding XEVMPD, medicinal product data management, regulatory requirements, inspection readiness and QPPV oversight responsibilities.

Last reviewed: 2026-06-11