EudraVigilance is the EU's centralized system for collecting, managing, and analyzing reports of suspected adverse reactions to medicines authorized in the European Economic Area (EEA). Every marketing authorization holder (MAH) with a product authorized in the EU is legally required to submit Individual Case Safety Reports (ICSRs) through EudraVigilance and maintain product data in the eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD).
These obligations are established by Regulation (EU) No 520/2012, Articles 24-27 and enforced through EMA's EudraVigilance access policy.
EudraVigilance Registration, Setup, and Maintenance
Understanding EudraVigilance
EudraVigilance was designed by the European Medicines Agency (EMA) to enable electronic exchange of ICSRs between MAHs, national competent authorities, and EMA. The system supports:
- Electronic ICSR submission — MAHs submit suspected adverse reaction reports in the ICH E2B(R3) format, either through EVWEB (the web-based interface) or via a secure gateway connection
- Signal detection — The EudraVigilance Data Analysis System (EVDAS) provides access to aggregated safety data for signal detection per EMA GVP Module IX (EMA/827661/2011 Rev 1)
- Transparency — Anonymized adverse reaction data is publicly available through the adrreports.eu portal
- Data sharing — Facilitates safety data exchange between regulatory authorities across the EEA
Registration Process
Before an MAH can submit ICSRs or access EVDAS, they must complete the EudraVigilance registration process:
Step 1: EMA Account Management Portal
The MAH (or their authorized representative) creates an organizational account through EMA's Account Management portal. This requires:
- Valid organization identification (legal entity details)
- Designated EudraVigilance super user (typically the QPPV or a delegated person)
- Organization's pharmacovigilance contact details
Step 2: QPPV Registration
The EU QPPV must be registered in the EudraVigilance system. The QPPV's details must be consistent with those notified to national competent authorities under EU Directive 2001/83/EC, Article 104.
Step 3: Mandatory Training
EMA requires that all users who will access EudraVigilance (EVWEB or gateway) and EVDAS complete mandatory EMA training modules. Training certificates must be obtained before system access is granted.
Step 4: Access Approval
Once registration and training are complete, EMA grants access to the relevant EudraVigilance components (EVWEB, gateway, EVDAS) based on the organization's role and products.
System Setup
EVWEB vs. Gateway
- EVWEB: Web-based interface for ICSR submission. Suitable for MAHs with low ICSR volumes (typically <50 cases/year). No IT infrastructure required beyond a web browser.
- Gateway: Automated, system-to-system ICSR transmission. Suitable for MAHs with higher ICSR volumes or those using safety databases (e.g., Argus, ArisGlobal) that support direct gateway integration. Requires IT setup and validation.
NextPV has configured both EVWEB and gateway-based EudraVigilance setups for 60+ organizations and can advise on the best approach based on your ICSR volume and safety database.
Integration with Safety Database
For MAHs using a safety database, the EudraVigilance gateway must be configured to transmit ICSRs in the ICH E2B(R3) format. This requires:
- Gateway configuration and testing
- Mapping of database fields to E2B(R3) data elements
- Test submissions to the EudraVigilance test environment
- Validation of successful submission and acknowledgment handling
User Role Configuration
Define user roles and permissions within EudraVigilance based on job responsibilities (ICSR submission, EVDAS access, XEVMPD management). Follow the principle of least privilege — users should only have access to the functions they need.
Ongoing Maintenance
- User management: Add/remove users as personnel change; ensure training certificates remain current
- System updates: Monitor EMA communications for EudraVigilance system updates and implement changes to maintain compatibility
- Performance monitoring: Track ICSR submission success rates, acknowledgment status, and address any submission failures promptly
- Compliance monitoring: Verify that all ICSRs are submitted within regulatory timelines (15 days for expedited, 90 days for non-expedited per GVP Module VI)
XEVMPD: Medicinal Product Dictionary Management
What is XEVMPD?
The eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD) is the database within EudraVigilance that contains structured information about all medicinal products authorized in the EEA. MAHs are required to enter and maintain their product data in XEVMPD, which is used for:
- Matching ICSRs to specific medicinal products
- Supporting signal detection by linking adverse reactions to specific products
- Facilitating regulatory reporting and safety analysis
MAH Obligations
Under Regulation (EU) No 520/2012, MAHs must:
- Enter product data into XEVMPD before or at the time of marketing authorization
- Maintain product data to reflect any changes (new formulations, name changes, withdrawal of products)
- Ensure data consistency between XEVMPD entries and the authorized product information (SmPC)
XEVMPD Data Elements
Key data elements include:
- Product name and marketing authorization number
- Active substance(s) and strength
- Pharmaceutical form and route of administration
- Marketing authorization holder details
- Authorization country and procedure type
- Product classification (ATC code)
Common XEVMPD Errors
- Duplicate entries for the same product
- Incorrect active substance spelling or coding
- Missing or outdated marketing authorization details
- Failure to update entries after product variation approvals
ISO IDMP: The Future of Product Identification
What is ISO IDMP?
The ISO Identification of Medicinal Products (IDMP) standards are a set of five ISO standards that will replace the current XEVMPD system with a more comprehensive, globally interoperable framework for identifying medicinal products. The key standards are:
- ISO 11615: Medicinal product identification
- ISO 11616: Pharmaceutical product identification
- ISO 11238: Substance identification
- ISO 11239: Pharmaceutical dose forms, routes of administration, and packaging
- ISO 11240: Units of measurement
Current Status and Timeline
EMA has been working on IDMP implementation through its SPOR (Substances, Products, Organizations, Referentials) data management services. The transition from XEVMPD to IDMP-based data management is ongoing, and MAHs should:
- Monitor SPOR portal and communications for implementation timelines
- Assess their current product data against IDMP requirements
- Plan for data migration from XEVMPD to IDMP-compliant formats
- Ensure their safety databases and IT systems can support IDMP data structures
Practical Advice for Biotech Companies
For most biotech companies with 1–3 products, the IDMP transition does not require immediate action. However, companies should:
- Keep current XEVMPD data clean and accurate (this facilitates future migration)
- Select safety database vendors that are preparing for IDMP compatibility
- Allocate future budget for IDMP implementation when EMA finalizes timelines
Conclusion
EudraVigilance compliance is a foundational requirement for any MAH operating in the EU. From initial registration through ongoing ICSR submission, EVDAS signal screening, and XEVMPD maintenance, the system demands consistent attention and expertise. The regulatory basis is clear: Regulation (EU) No 520/2012 and EMA GVP Module VI define the requirements, and EMA inspectors verify compliance.
For biotech companies entering the EU market for the first time, outsourcing EudraVigilance setup and management to an experienced PV partner eliminates the learning curve and ensures compliance from Day 1 of marketing authorization.