EVWEB
What is EVWEB?
EVWEB is the web-based interface provided by the European Medicines Agency for interaction with EudraVigilance.
The platform allows authorised users to create, submit, review and manage Individual Case Safety Reports without requiring a direct gateway connection.
For smaller Marketing Authorisation Holders and organisations with relatively low reporting volumes, EVWEB may provide a practical alternative to maintaining a fully integrated E2B(R3) gateway infrastructure.
EVWEB supports:
- Manual case creation
- Case submission
- Follow-up reporting
- Acknowledgement review
- Case searching
- User administration activities
Many organisations initially begin reporting through EVWEB before transitioning to automated gateway reporting as reporting volumes increase.
Who Uses EVWEB?
Common users include:
- Small and medium pharmaceutical companies
- Virtual pharmaceutical companies
- Generic manufacturers
- Local affiliates
- Academic organisations
- Clinical trial sponsors
The platform remains widely used throughout Europe despite increasing adoption of automated gateway solutions.
Advantages of EVWEB
Advantages include:
- No gateway infrastructure required
- Direct access to EudraVigilance
- Lower implementation costs
- Suitable for low case volumes
- Regulatory acceptance
Limitations of EVWEB
Limitations include:
- Manual processing effort
- Reduced scalability
- Increased risk of human error
- Less efficient handling of large reporting volumes
For organisations processing substantial numbers of ICSRs, gateway reporting is generally more efficient.
Downloading Cases from EudraVigilance
Many pharmacovigilance professionals focus primarily on case submission. However, receiving information from EudraVigilance is equally important.
Marketing Authorisation Holders may download cases relating to their authorised products to support safety monitoring and signal management activities.
Why Download Cases?
Downloaded cases support:
- Signal detection
- Aggregate reporting
- Case reconciliation
- Medical review
- Benefit-risk evaluation
The downloaded information often contains reports received directly by regulators or originating from sources not available through internal company reporting channels.
Level 2A Cases
Level 2A access provides information relating to cases associated with products for which an organisation holds regulatory responsibility.
These reports support routine pharmacovigilance activities and help ensure a complete understanding of product safety profiles.
QPPVs should understand the role of Level 2A access because signal detection activities frequently depend upon these data.
Level 2B Cases
Level 2B access provides broader access to data sets used primarily for signal detection and pharmacovigilance evaluation activities.
These data are frequently used by:
- Signal management teams
- Safety scientists
- Epidemiologists
- Regulatory authorities
Level 2B data support population-level analysis rather than individual case processing activities.
Case Reconciliation
Downloaded EudraVigilance cases should be reconciled against internal safety databases where appropriate.
Reconciliation activities help identify:
- Missing cases
- Duplicate reports
- Transmission failures
- Processing delays
Failure to perform effective reconciliation is a common inspection concern.
Inspection
Inspectors frequently review reconciliation procedures and evidence that downloaded EudraVigilance cases are appropriately managed within the pharmacovigilance system.
Medical Literature Monitoring (MLM)
What is Medical Literature Monitoring?
Medical Literature Monitoring (MLM) is an EMA initiative whereby selected scientific literature is monitored centrally for adverse reaction reports relating to specified active substances.
This programme reduces duplication of effort across the pharmaceutical industry while improving consistency of literature surveillance activities.
Why MLM Exists
Historically, every Marketing Authorisation Holder was responsible for independently screening scientific literature.
This resulted in:
- Duplicate effort
- Inconsistent identification of cases
- Increased resource requirements
The MLM programme was introduced to improve efficiency while maintaining pharmacovigilance oversight.
EMA Responsibilities
For substances included within the MLM programme, EMA:
- Screens designated literature sources
- Identifies reportable adverse reactions
- Creates ICSRs
- Transmits reports through EudraVigilance
Downloading MLM Cases
Marketing Authorisation Holders may download MLM-generated cases from EudraVigilance.
These cases should be incorporated into routine pharmacovigilance activities in accordance with organisational procedures.
MAH Responsibilities
The existence of the MLM programme does not eliminate all literature monitoring obligations.
Organisations remain responsible for:
- Understanding MLM scope
- Monitoring literature outside MLM coverage
- Processing MLM cases appropriately
- Maintaining oversight of compliance activities
Inspection Expectations
Inspectors frequently assess whether organisations:
- Understand MLM responsibilities
- Process MLM cases appropriately
- Maintain documented procedures
- Demonstrate effective oversight
EudraVigilance Data Analysis System (EVDAS)
What is EVDAS?
The EudraVigilance Data Analysis System (EVDAS) is the analytical environment built upon EudraVigilance data.
Where EudraVigilance functions as the repository for safety reports, EVDAS provides tools for analysing those reports.
EVDAS plays a central role in modern signal management activities.
Why EVDAS Matters
Signal detection increasingly relies on large-scale data analysis.
EVDAS allows organisations to:
- Review reporting trends
- Evaluate potential signals
- Monitor disproportionality metrics
- Support benefit-risk assessments
Many routine signal detection processes depend heavily upon EVDAS outputs.
eRMR Reports
One of the most widely used EVDAS outputs is the electronic Reaction Monitoring Report (eRMR).
These reports provide structured summaries of adverse event reporting patterns and support signal detection activities.
Signal management teams frequently review eRMR outputs as part of routine surveillance processes.
EVDAS and Signal Management
EVDAS supports multiple stages of signal management including:
- Signal detection
- Signal validation
- Signal prioritisation
- Signal assessment
Gvp
GVP Module IX describes signal management activities and expectations relating to the evaluation of potential safety signals.
QPPV Oversight of EVDAS
The QPPV may not personally review EVDAS outputs but should maintain oversight of:
- Signal management processes
- Governance arrangements
- Escalation pathways
- Compliance monitoring
Effective oversight helps ensure that potential safety concerns are identified and evaluated appropriately.
XEVMPD
What is XEVMPD?
The eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD) is the European database containing structured medicinal product information.
Although often discussed separately from EudraVigilance case reporting, XEVMPD is a critical component of the wider European pharmacovigilance ecosystem.
Why XEVMPD Matters
Accurate product information supports:
- Regulatory reporting
- Product identification
- Signal detection
- Safety analysis
Errors within product data may create downstream pharmacovigilance compliance risks.
Information Stored Within XEVMPD
Typical data include:
- Product names
- Active substances
- Authorisation information
- Pharmaceutical forms
- Strengths
- Marketing status
Registration Obligations
Marketing Authorisation Holders are responsible for maintaining accurate product information within XEVMPD in accordance with applicable requirements.
Common Compliance Issues
Common issues include:
- Delayed updates
- Incomplete product records
- Incorrect product coding
- Poor change management controls
Inspection Perspective
Inspectors may review XEVMPD governance as part of broader assessments of pharmacovigilance system effectiveness.
Deficiencies within product data management processes may indicate wider governance weaknesses.
Qppv
The QPPV should understand how XEVMPD governance, EudraVigilance reporting and signal detection activities interact within the wider pharmacovigilance system.
EudraVigilance Registration and Access Management
EudraVigilance is a regulated system and access is controlled by the European Medicines Agency.
Organisations cannot simply create user accounts and begin reporting. Registration, training, access management and governance controls must be established before production access is granted.
From an inspection perspective, access management is often viewed as part of the wider pharmacovigilance quality system because inappropriate access controls can affect data integrity, reporting compliance and patient safety.
Organisation Registration
Before an organisation can access EudraVigilance it must complete the EMA registration process.
Registration typically involves:
- Organisation identification
- Designation of responsible contacts
- System documentation
- User administration arrangements
- Compliance declarations
The registration process helps ensure that organisations interacting with EudraVigilance are appropriately governed and accountable.
Responsible Person for EudraVigilance
Organisations must designate individuals responsible for managing EudraVigilance access and user administration activities.
Responsibilities commonly include:
- User account management
- Access approvals
- Training verification
- User deactivation
- Governance oversight
The role may be performed by pharmacovigilance personnel, regulatory personnel or dedicated system administrators depending on organisational structure.
User Registration
Individual users require authorised access.
Registration generally involves:
- User identification
- Role assignment
- Training completion
- Access approval
Access should be granted according to business need and maintained through documented procedures.
User Roles
Different users may require different levels of access.
Examples include:
| User Type | Typical Activities |
|---|---|
| Case Processor | ICSR submission and review |
| Safety Scientist | Signal management activities |
| QPPV | Oversight and compliance review |
| Administrator | User management |
| Regulatory Affairs | Reporting review |
Access permissions should be aligned with responsibilities.
Training Requirements
Training is an important component of EudraVigilance compliance.
Users should understand:
- Reporting obligations
- System functionality
- Submission processes
- Acknowledgement review
- Compliance expectations
Training records should be maintained as part of the pharmacovigilance quality system.
User Lifecycle Management
User management should include:
- Account creation
- Role changes
- Periodic review
- Account deactivation
Former employees and contractors should have access removed promptly.
Inspection
Inspectors frequently review access governance and may request evidence demonstrating that inactive users have been removed from the system.
QPPV Responsibilities Relating to EudraVigilance
Many operational activities within EudraVigilance are delegated to specialist teams.
However, the QPPV remains responsible for maintaining oversight of the pharmacovigilance system and understanding whether EudraVigilance-related activities are functioning effectively.
The QPPV is not expected to perform routine case processing activities personally.
The QPPV is expected to understand:
- Reporting performance
- Compliance risks
- Governance controls
- Signal management activities
- Escalation mechanisms
Oversight of Reporting Compliance
One of the most important QPPV responsibilities is oversight of reporting compliance.
This includes awareness of:
- Reporting timelines
- Submission success rates
- Late submissions
- Significant compliance deviations
The QPPV should be informed of material reporting issues that may affect regulatory compliance.
Oversight of Case Quality
Poor case quality can affect signal detection and regulatory decision making.
Oversight activities may include review of:
- Case completeness
- Coding quality
- Follow-up effectiveness
- Quality metrics
Quality governance should be proportionate to organisational risk.
Oversight of EVDAS Activities
Signal management activities supported by EVDAS should operate within a defined governance framework.
The QPPV should understand:
- Signal detection methodology
- Review frequency
- Escalation processes
- Decision-making structures
Oversight of Vendor Activities
Many organisations outsource portions of EudraVigilance-related work.
Examples include:
- Case processing
- Literature monitoring
- EVDAS review
- Regulatory submissions
Outsourcing does not remove accountability.
The QPPV should understand how outsourced activities are monitored and controlled.
Oversight of Access Management
Access governance is often overlooked despite its importance.
The QPPV should have confidence that:
- Access is controlled
- Training is maintained
- Inactive users are removed
- Critical activities are appropriately supervised
Governance Reporting
Periodic reporting to the QPPV commonly includes:
- Compliance metrics
- Submission performance
- Inspection findings
- Significant deviations
- Emerging risks
Effective governance reporting supports informed oversight.
Inspection Perspective
EudraVigilance activities are routinely reviewed during pharmacovigilance inspections.
Inspectors are typically less interested in theoretical procedures and more interested in evidence that processes operate effectively in practice.
Reporting Timeliness
Inspectors commonly review:
- Serious case submissions
- Non-serious case submissions
- Follow-up reporting
- Compliance metrics
Late reporting is among the most common pharmacovigilance inspection findings.
Reporting Accuracy
Reporting accuracy may be assessed through:
- Case reviews
- Data verification
- Coding assessments
- Validation review
Inspectors may compare submitted reports against source documentation.
Reconciliation Activities
Inspectors frequently evaluate:
- EudraVigilance reconciliation procedures
- Downloaded case management
- Duplicate handling
- Missing case investigations
Reconciliation failures may indicate weaknesses in process control.
Signal Detection Activities
Inspection review may include:
- EVDAS review procedures
- Signal detection documentation
- Escalation records
- Governance meeting minutes
Inspectors generally expect evidence demonstrating that signals are actively monitored and assessed.
User Access Controls
Inspectors may review:
- User lists
- Training records
- Access approvals
- Account deactivation activities
Weak access governance may generate broader concerns regarding data integrity.
Common Inspection Findings
Observed findings frequently include:
Late Reporting
- Missed regulatory timelines
- Delayed submissions
- Failure to monitor acknowledgements
Poor Reconciliation
- Missing downloaded cases
- Inadequate reconciliation documentation
- Unresolved discrepancies
Weak Oversight
- Inadequate QPPV visibility
- Poor governance reporting
- Limited management review
User Management Deficiencies
- Inactive accounts remaining active
- Missing training records
- Unclear access ownership
Signal Management Weaknesses
- Delayed reviews
- Poor documentation
- Inadequate escalation
Metrics Every QPPV Should Monitor
The QPPV does not need to review every operational detail.
However, certain metrics provide valuable insight into EudraVigilance performance.
Reporting Compliance Metrics
Examples include:
| Metric | Purpose |
|---|---|
| Serious case compliance | Timeliness monitoring |
| Non-serious case compliance | Regulatory compliance |
| Follow-up compliance | Case management effectiveness |
| Submission success rate | Technical performance |
Quality Metrics
Examples include:
- Case completeness
- Coding quality
- Follow-up success rates
- Quality review outcomes
EVDAS Metrics
Examples include:
- Signal reviews completed
- Signals escalated
- Assessment timeliness
- Governance review outcomes
Access Governance Metrics
Examples include:
- Active users
- Overdue training
- Access reviews completed
- Deactivated accounts
Qppv
Effective QPPV oversight relies upon meaningful metrics rather than detailed operational involvement in every EudraVigilance activity.
Frequently Asked Questions
Is EudraVigilance mandatory?
Yes. EudraVigilance reporting requirements apply to organisations subject to European pharmacovigilance legislation.
What is the difference between EVWEB and gateway reporting?
EVWEB is a web-based reporting interface while gateway reporting uses automated electronic transmission of E2B(R3) messages.
What is EVDAS used for?
EVDAS supports signal detection, signal validation and pharmacovigilance data analysis activities.
Are MLM cases required to be processed?
Yes. MLM cases downloaded from EudraVigilance form part of routine pharmacovigilance activities and should be managed appropriately.
Is XEVMPD still relevant?
Yes. Product data quality remains important because accurate medicinal product information supports reporting, signal detection and regulatory analysis.
Final Thoughts
EudraVigilance is far more than a reporting database.
It is the central information infrastructure supporting European pharmacovigilance.
Reporting compliance, signal detection, Medical Literature Monitoring, EVDAS review activities, XEVMPD governance and regulatory oversight all depend on effective operation of the system.
For QPPVs, understanding EudraVigilance is not optional. It is a fundamental component of maintaining oversight of the pharmacovigilance system and ensuring that medicinal product safety information is collected, evaluated and communicated effectively.
References
- Regulation (EC) No 726/2004.
- Directive 2001/83/EC.
- Commission Implementing Regulation (EU) No 520/2012.
- GVP Module I – Pharmacovigilance Systems and Their Quality Systems.
- GVP Module VI – Collection, Management and Submission of Reports of Suspected Adverse Reactions.
- GVP Module IX – Signal Management.
- EMA EudraVigilance Electronic Reporting Guidance.
- EMA EudraVigilance Registration Manual.
- EMA EVDAS User Manual.
- EMA Medical Literature Monitoring Guidance.
- EMA XEVMPD Guidance.