Archived Revision: You are viewing historical Version 2 of this article. View current active version →

What Is EudraVigilance?

Explains what EudraVigilance is, how it supports electronic ICSR exchange and regulatory surveillance, how MAHs interact with it, and how its signal-management role changed following the 2025 amendment to the EU pharmacovigilance framework.

What Is EudraVigilance?

EudraVigilance (EV) is the European Union system for managing and analysing information on suspected adverse reactions to medicinal products authorised or studied in the European Economic Area. It provides shared regulatory infrastructure for electronic ICSR exchange, case access and safety surveillance.

Purpose and Regulatory Framework

EudraVigilance operates within the EU pharmacovigilance framework established by Regulation (EC) No 726/2004, Directive 2001/83/EC and Commission Implementing Regulation (EU) No 520/2012 as amended. Detailed ICSR collection and reporting expectations are described in GVP Module VI — Collection, management and submission of reports of suspected adverse reactions (Rev. 2) and EMA EudraVigilance guidance.

The system should be understood as infrastructure rather than as a pharmacovigilance process by itself. It supports processes performed by MAHs, national competent authorities, EMA and clinical-trial sponsors.

What EudraVigilance Contains

The principal data objects are Individual Case Safety Reports (ICSRs). These can include initial and follow-up information on suspected adverse reactions, together with administrative and clinical data needed for regulatory processing and scientific evaluation.

The system also manages report amendments, nullifications and acknowledgements. The data are structured using the ISO/ICH E2B(R3) standard for electronic transmission.

E2B(R3)

ICH E2B(R3) defines the structured data elements and messaging model used to exchange ICSRs electronically. Mandatory use of the ISO/ICH E2B(R3) ICSR standard in the EU became effective on 30 June 2022.

E2B(R3) allows different safety databases and regulators to exchange information consistently. It does not, however, guarantee that a case is clinically complete or scientifically correct. Technical conformance and pharmacovigilance quality remain separate questions.

EVWEB and Gateway Reporting

Organisations can interact with EudraVigilance through different technical routes.

EVWEB is EMA's web application for authorised users. It supports activities such as ICSR creation, submission, review of acknowledgements, search and case access.

Higher-volume organisations commonly use gateway-based electronic exchange from a local safety database. The technical architecture may differ, but the regulatory control objective remains the same: valid reports should be transmitted through the applicable route and successful receipt should be demonstrable.

Submission Is Not the Same as Acceptance

A case transmitted to EudraVigilance generates an acknowledgement. A positive acknowledgement provides evidence that the message passed the applicable technical checks and was accepted; a negative acknowledgement or missing acknowledgement requires investigation.

This distinction is operationally important. A sending system can record a message as “sent” even when the regulatory destination has rejected it or no acknowledgement has been received.

Effective reporting control therefore considers the full chain:

case due → message generated → transmitted → acknowledgement received → rejection resolved where applicable.

Simplified Reporting and MAH Case Download

Since the simplified reporting model introduced in November 2017, MAHs submit applicable ICSRs to EudraVigilance rather than separately exchanging them with each EEA national competent authority. EudraVigilance applies rerouting rules to forward relevant reports to NCAs.

MAHs can also access and download ICSRs submitted by NCAs for active substances in medicinal products for which they hold EEA marketing authorisations. This enables the MAH to incorporate regulatory-source reports into its own pharmacovigilance processes in accordance with the EudraVigilance access policy.

Case Access and Reconciliation

Downloaded EudraVigilance cases may need to be compared with the MAH's internal safety database to identify reports that were not otherwise received, duplicates, follow-up information or discrepancies. The appropriate reconciliation model depends on the reporting route, product portfolio, system architecture and applicable procedure.

Reconciliation is a control, not an end in itself. The purpose is to determine whether the MAH's case collection and reporting process is complete enough to support regulatory obligations and scientific evaluation.

EudraVigilance and Signal Management

EudraVigilance contains a large body of spontaneous-reporting information that can support signal evaluation. Historically, EVDAS and electronic Reaction Monitoring Reports were also used within a pilot in which certain MAHs performed routine signal detection in EudraVigilance.

That framework changed materially in 2025. Commission Implementing Regulation (EU) 2025/1466 amended Regulation 520/2012, and EMA states that the MAH EudraVigilance signal-detection pilot ended when the amended Regulation entered into force. EMA published dedicated Q&A, updated in January 2026, and plans corresponding revisions to GVP Module IX.

This means current articles should not teach routine MAH EVDAS signal screening as a universal continuing obligation. EudraVigilance data remain relevant to safety evaluation and regulatory interaction, but the applicable current signal-management responsibilities should be taken from the amended legal framework and current EMA procedural guidance.

EVDAS

The EudraVigilance Data Analysis System (EVDAS) provides analytical access to EudraVigilance data for authorised users. Its outputs can support regulatory and scientific analysis, but a statistical output is not equivalent to a confirmed safety signal.

The companion articles [[eudravigilance-signal-detection]] and [[evdas-and-signal-detection]] explain the historical and current signal context in more detail.

Medical Literature Monitoring

EMA's Medical Literature Monitoring service identifies reportable suspected adverse reactions in defined literature sources for covered active substances and creates ICSRs for entry into EudraVigilance.

The service reduces duplicate MAH literature case processing only within its defined scope. It does not eliminate the MAH's broader obligation to monitor literature relevant to its medicinal products. See [[medical-literature-monitoring]].

Product Data and XEVMPD

Article 57/XEVMPD product data historically sat closely within the wider EudraVigilance environment. In 2026, EMA changed the external user interface: from 11 May 2026, external users access the XEVMPD/Article 57 database through the upgraded XEVMPDweb interface rather than the former EVWEB Article 57/XEVMPD interface.

This operational change is a useful reminder that EudraVigilance-related procedures should distinguish stable regulatory obligations from interface-specific instructions that can change.

See [[xevmpd-guide]] for product-data obligations and implementation.

Registration, Training and Access

EudraVigilance access is controlled. Organisations and users must follow EMA registration and training requirements applicable to their intended role and reporting route.

Access governance should ensure that users have roles appropriate to their responsibilities and that leavers, transfers and privilege changes are managed. The precise internal access-review cadence is an organisational control rather than a universal EMA schedule.

EMA continues to provide EudraVigilance training for MAHs and sponsors. Its 2026 training material confirms that organisations registering their first QPPV/RP user or starting EVWEB reporting must satisfy the applicable training/registration prerequisites.

Quality Assurance Testing for Electronic Reporting

Organisations establishing or materially changing an electronic reporting connection may need to perform EMA quality-assurance testing according to the applicable EudraVigilance process. EMA's electronic-reporting page and support guide were updated in February 2026, including additional information on ICH E2B(R3) test cases and ICSR compliance/quality.

For vendor-developed software, EMA guidance allows organisations to consider vendor testing for the version and configuration in use, provided applicability is understood. This does not remove the organisation's responsibility for its configured reporting process.

QPPV Oversight

The QPPV does not need to operate EVWEB or personally review every acknowledgement. The oversight requirement is that significant EudraVigilance-related risks become visible within the pharmacovigilance system.

The QPPV should be able to understand, at an appropriate level:

Potential Failure Modes

The following are illustrative failure modes, not published inspection findings.

Failure mode Why it matters
“sent” status is treated as evidence of accepted submission regulatory rejection may remain unnoticed
acknowledgement failures are not reconciled reporting compliance may be overstated
downloaded NCA cases are not integrated into controlled processing relevant safety information may be missed or duplicated
old EVDAS pilot procedures remain active as if legally required resources are spent on an obsolete regulatory model
EVWEB interface instructions are embedded permanently in SOPs procedures become outdated when EMA changes the interface
product-data responsibilities are confused with ICSR reporting different regulatory processes become operationally entangled
vendor gateway evidence is accepted without MAH visibility outsourced technical failure may undermine reporting obligations
access rights remain after role changes confidentiality and data-integrity risk increases

Inspection Considerations

An inspector may ask the organisation to demonstrate:

The most persuasive evidence is a controlled end-to-end process rather than a large set of EV-specific screenshots.

Practical EudraVigilance Review Checklist

  1. Is the organisation's applicable ICSR reporting route defined?
  2. Are E2B(R3) requirements implemented correctly for that route?
  3. Is successful acceptance distinguished from transmission alone?
  4. Are missing and negative acknowledgements investigated?
  5. Are downloaded NCA cases integrated appropriately?
  6. Are duplicate and follow-up relationships controlled?
  7. Are registration, training and user access current?
  8. Are gateway or vendor changes assessed and tested appropriately?
  9. Do procedures reflect the end of the former MAH EV signal-detection pilot?
  10. Are XEVMPD/Article 57 instructions current for the 2026 interface transition?
  11. Are material EudraVigilance compliance issues visible to the QPPV?
  12. Can critical reporting evidence be retrieved during inspection?

Relationship With Other QPPV.com Articles

For detailed reporting practice see [[eudravigilance-reporting]]. Registration and roles are covered in [[eudravigilance-registration-and-access]]. Signal-analysis history and current context are covered in [[eudravigilance-signal-detection]] and [[evdas-and-signal-detection]]. Literature integration is covered in [[medical-literature-monitoring]], and medicinal-product data in [[xevmpd-guide]].

Key Takeaways

EudraVigilance is shared EU infrastructure for managing and analysing suspected adverse-reaction information; it is more than a case-submission portal.

E2B(R3) provides the electronic ICSR messaging standard, while EVWEB and gateway connections provide practical reporting routes.

Successful reporting requires evidence of acceptance, not merely evidence that a message was sent.

MAHs can download relevant ICSRs submitted by NCAs and must integrate them appropriately into their pharmacovigilance processes.

The EudraVigilance signal-management context changed materially after Implementing Regulation (EU) 2025/1466: the former MAH EV signal-detection pilot has ended.

EudraVigilance procedures should be written so that stable regulatory obligations are separated from interface details that EMA may update.

References

  1. European Medicines Agency. EudraVigilance system overview. Current EMA information.
  2. European Medicines Agency. EudraVigilance: electronic reporting. Updated 24 February 2026.
  3. European Medicines Agency. EudraVigilance training and support. Current 2026 training information.
  4. European Medicines Agency. GVP Module VI — Collection, management and submission of reports of suspected adverse reactions to medicinal products (Rev. 2). EMA/873138/2011 Rev. 2.
  5. European Medicines Agency. Questions and answers on Implementing Regulation (EU) 2025/1466 and conclusion of the Signal Detection in EudraVigilance Pilot by MAHs. EMA/243145/2025 Rev. 2, updated 28 January 2026.
  6. International Council for Harmonisation. ICH E2B(R3): Electronic Transmission of Individual Case Safety Reports.
  7. European Union. Commission Implementing Regulation (EU) No 520/2012, as amended by Commission Implementing Regulation (EU) 2025/1466.
  8. European Union. Directive 2001/83/EC, as amended.
  9. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article describes EudraVigilance as of 9 September 2026. EMA updated its electronic-reporting guidance on 24 February 2026. External XEVMPD users moved to XEVMPDweb from 11 May 2026. The former MAH EudraVigilance signal-detection pilot has ended following Implementing Regulation (EU) 2025/1466; current EMA procedural guidance should be used for live signal-management obligations.

Revision History

Last reviewed: 2026-09-09

QPPV.com