XEVMPD Guide for Pharmacovigilance Professionals
The eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD), also known as the Article 57 database, is EMA's structured repository of medicinal-product information used to support identification, coding and pharmacovigilance activities in Europe. It is related to EudraVigilance but serves a different purpose: EudraVigilance stores and processes safety reports, while XEVMPD provides structured information about the medicinal products to which those reports may relate.
- XEVMPD Guide for Pharmacovigilance Professionals
- Purpose and Legal Context
- What XEVMPD Contains
- XEVMPD and EudraVigilance
- Why Product-Data Quality Matters
- The 2026 XEVMPDweb Transition
- Submission Routes and Acknowledgements
- Product Lifecycle Maintenance
- Source of Truth and Data Ownership
- Reconciliation
- Controlled Vocabularies and Data Standards
- XEVMPD, SPOR, PMS and IDMP
- Relationship With the PSMF
- QPPV Oversight
- Outsourcing
- Illustrative Lifecycle Example
- Potential Failure Modes
- Inspection and Governance Considerations
- Practical Review Checklist
- Relationship With Other QPPV.com Articles
- Key Takeaways
- References
- Regulatory Note
Purpose and Legal Context
The Article 57 framework requires marketing authorisation holders to submit information on medicinal products authorised in the European Union in the electronic format specified by EMA and to keep that information up to date. EMA uses XEVMPD to support standardised identification of medicines and wider pharmacovigilance activities.
The database also contains information on investigational medicinal products used in clinical trials in the European Economic Area. The precise responsibilities and submission routes differ according to stakeholder type and regulatory context.
XEVMPD should therefore be understood as regulated medicinal-product master data, not merely as an administrative directory.
What XEVMPD Contains
The XEVMPD data model represents structured information and relationships concerning medicinal products. Depending on the applicable record and submission requirements, this can include information about:
- medicinal-product name;
- active substance;
- pharmaceutical form;
- strength;
- route of administration;
- marketing-authorisation holder;
- marketing-authorisation number and status;
- country and authorisation information;
- presentations and related product attributes; and
- controlled terminology used by the Article 57 data model.
The exact fields, controlled vocabularies and business rules should always be taken from current EMA specifications rather than copied permanently from an old implementation guide.
XEVMPD and EudraVigilance
XEVMPD and EudraVigilance interact conceptually but should not be conflated.
| System | Primary function |
|---|---|
| XEVMPD / Article 57 database | structured medicinal-product information |
| EudraVigilance | individual case safety report collection and management |
| EVDAS | analysis of EudraVigilance data for authorised users |
Accurate product master data helps regulators identify products consistently in pharmacovigilance datasets. However, maintaining an XEVMPD record is not the same activity as submitting an ICSR.
Why Product-Data Quality Matters
A medicinal-product record is a set of relationships, not just a product name. If the authorised product, active substance, strength, route or authorisation status is represented incorrectly, downstream identification and regulatory use can become unreliable.
Product-data quality therefore depends on:
- authoritative source information;
- consistent terminology;
- correct relationships between entities;
- timely lifecycle maintenance;
- controlled correction of errors; and
- evidence showing what was submitted and how discrepancies were resolved.
The pharmacovigilance significance is indirect but important: reliable product identification supports reliable safety-data interpretation.
The 2026 XEVMPDweb Transition
EMA introduced the upgraded browser-based XEVMPDweb interface for external users in February 2026. Following a transition period, external users from MAHs, sponsors and national competent authorities could no longer use the former EVWEB Article 57/XEVMPD interface from 11 May 2026 and must access the Article 57 database through XEVMPDweb.
This is an interface transition, not a replacement of the underlying Article 57/XEVMPD regulatory concept. Procedures should therefore distinguish stable regulatory obligations from user-interface instructions that may change.
Submission Routes and Acknowledgements
EMA provides mechanisms for organisations to submit and maintain Article 57 information, including the user interface and applicable electronic message-based routes. The appropriate route depends on organisational needs and current EMA technical arrangements.
Whatever route is used, the organisation should be able to determine whether a submission was processed successfully and whether corrective action is needed. Evidence should be sufficient to reconstruct important submissions and changes without treating every screenshot as a regulatory deliverable.
Product Lifecycle Maintenance
Article 57 data changes as the authorised product changes. Relevant lifecycle events may include:
- new marketing authorisation;
- variation affecting submitted product attributes;
- change of marketing-authorisation holder;
- product-name or presentation changes;
- suspension, revocation or withdrawal;
- corrections to previously submitted data; and
- other regulatory events that change information required in XEVMPD.
The operational challenge is not simply submitting a new record. It is maintaining consistency between the regulatory decision, the organisation's master data and the Article 57 record over time.
Source of Truth and Data Ownership
Organisations should define which controlled sources establish each submitted data element. Regulatory information management systems, approved authorisation documents and controlled substance/product master data may all contribute.
A practical governance model should answer:
- Who identifies a change requiring Article 57 action?
- Which source document establishes the authoritative value?
- Who prepares and submits the change?
- How is technical acceptance monitored?
- How are discrepancies investigated?
- Which issues require escalation because they could affect pharmacovigilance?
The roles can be assigned to Regulatory Affairs, product-data teams, pharmacovigilance or shared service functions. EMA does not prescribe one company organisation chart.
Reconciliation
Reconciliation is useful where the organisation has multiple systems holding product information. It should be designed around plausible failure modes rather than performed merely because a fixed periodic frequency appears in an SOP.
Relevant comparisons can include:
- current marketing-authorisation records versus XEVMPD;
- internal product master data versus submitted Article 57 data;
- changes recorded in regulatory systems versus changes processed by EMA; and
- known lifecycle events versus outstanding corrections.
The frequency and method should reflect portfolio size, rate of change, system automation and risk.
Controlled Vocabularies and Data Standards
Structured product data rely on standard terminology and defined relationships. Free-text approximations can create inconsistent records even when the underlying product is correctly understood.
Staff responsible for submissions therefore need access to current EMA data specifications and controlled terminology. Procedures should avoid embedding technical codes that can become obsolete unless there is a controlled mechanism for maintaining them.
XEVMPD, SPOR, PMS and IDMP
The EU medicinal-product data environment is evolving toward ISO Identification of Medicinal Products (IDMP) standards and EMA's Substance, Product, Organisation and Referential (SPOR) services.
This evolution does not mean that current Article 57 obligations can be ignored in anticipation of a future state. Organisations should distinguish:
- current XEVMPD/Article 57 obligations;
- current SPOR services used in regulatory data management; and
- future or phased IDMP/PMS implementation requirements according to EMA's actual deployment roadmap.
A migration programme or internal IDMP project is not itself a substitute for maintaining required Article 57 data today.
Relationship With the PSMF
The PSMF describes the pharmacovigilance system and relevant computerised systems and data flows. Depending on the organisation's system, Article 57/XEVMPD responsibilities may be relevant to that description, particularly where product master data support safety-reporting or pharmacovigilance processes.
The PSMF need not reproduce the entire XEVMPD operating procedure. It should describe the system sufficiently for the reader to understand important pharmacovigilance interfaces and responsibilities.
QPPV Oversight
The QPPV is not required to enter every XEVMPD record or personally approve every Article 57 submission. The more relevant question is whether significant product-data deficiencies that could affect the pharmacovigilance system become visible and are controlled.
Depending on the organisation, QPPV oversight may include awareness of:
- significant or systemic Article 57 compliance problems;
- product-data defects affecting safety reporting or analysis;
- major changes to systems supporting medicinal-product data;
- important unresolved discrepancies; and
- governance arrangements for outsourced Article 57 activities.
Routine operational ownership can remain with specialised regulatory-data teams.
Outsourcing
Article 57 submission activities may be delegated to a service provider, but the MAH retains its regulatory responsibilities. Effective oversight should therefore establish:
- what the provider is responsible for;
- how regulatory changes reach the provider;
- how submission outcomes and errors are communicated;
- how source data are controlled;
- how changes are evidenced; and
- what happens if the provider or technical route fails.
A service-level metric alone cannot demonstrate that the submitted product data are scientifically and regulatorily correct.
Illustrative Lifecycle Example
Consider a product whose marketing-authorisation holder changes following a corporate transfer. The regulatory decision becomes effective on a defined date, but the organisation's internal product master and Article 57 data are maintained by different teams.
A weak process would rely on informal notification and assume that the XEVMPD record will eventually be corrected.
A stronger process would identify the transfer as a controlled lifecycle event, use the authorised decision as the source record, update affected master data, submit the required Article 57 change through the current route, review the processing result and reconcile the final record. If the discrepancy could affect safety-reporting identification, it would also be escalated through the pharmacovigilance quality system.
Potential Failure Modes
The following are illustrative failure modes, not published inspection findings.
| Failure mode | Why it matters |
|---|---|
| obsolete EVWEB instructions remain hard-coded after May 2026 | staff are directed to a retired external interface |
| XEVMPD is treated as an ICSR reporting database | responsibilities and controls become confused |
| product changes rely on informal email notification | lifecycle updates can be missed |
| internal master data and Article 57 records diverge | product identification becomes unreliable |
| fixed quarterly reconciliation is treated as an EMA requirement | company practice is misrepresented as law |
| every record requires QPPV signature | operational ownership is confused with QPPV oversight |
| future IDMP plans are used to defer current XEVMPD maintenance | existing obligations remain unmet |
| provider acknowledgement is accepted without investigating recurring errors | outsourced process effectiveness is not understood |
Inspection and Governance Considerations
An inspector may examine Article 57/XEVMPD controls when product-data quality is relevant to the pharmacovigilance system. Useful questions may include:
- How are new authorisations and relevant variations identified for Article 57 maintenance?
- Which records are the authoritative source?
- How does the organisation know that a submission was processed?
- How are discrepancies corrected?
- How are outsourced activities controlled?
- How did procedures change when XEVMPDweb became the required external interface?
- How are current Article 57 obligations distinguished from future IDMP/PMS work?
The evidence should show an effective lifecycle process, not merely the presence of a particular template or committee.
Practical Review Checklist
- Are current Article 57 responsibilities defined?
- Is XEVMPD distinguished clearly from EudraVigilance ICSR reporting?
- Are authoritative source records identified?
- Are relevant lifecycle events translated into timely data maintenance?
- Are current controlled vocabularies and technical specifications used?
- Is processing/acknowledgement evidence reviewed?
- Are important discrepancies investigated and corrected?
- Are internal systems reconciled where risk justifies it?
- Are vendor responsibilities and evidence accessible to the MAH?
- Do procedures reflect mandatory use of XEVMPDweb for external users from 11 May 2026?
- Are current XEVMPD requirements distinguished from IDMP/PMS transition planning?
- Are significant pharmacovigilance-impacting issues visible to appropriate management and the QPPV?
Relationship With Other QPPV.com Articles
For the safety-reporting infrastructure see [[what-is-eudravigilance]], [[eudravigilance-reporting]] and [[eudravigilance-registration-and-access]]. Computerised-system controls are discussed in [[computerised-system-validation-in-pharmacovigilance]] and [[user-requirements-specifications-in-pharmacovigilance]].
Key Takeaways
XEVMPD is the Article 57 medicinal-product database supporting standardised medicine identification and EU pharmacovigilance; it is not the ICSR repository itself.
MAHs need controlled lifecycle processes that keep required Article 57 information aligned with authoritative regulatory data.
From 11 May 2026, external users access XEVMPD through XEVMPDweb rather than the former EVWEB Article 57 interface.
XEVMPD remains a current obligation while EMA's broader product-data environment evolves toward SPOR, PMS and IDMP-based structures.
QPPV oversight should focus on significant pharmacovigilance implications rather than routine data entry or universal sign-off.
References
- European Medicines Agency. How to submit information on authorised and investigational medicines. Current Article 57/XEVMPD procedural guidance.
- European Medicines Agency. EudraVigilance system overview — Extended EudraVigilance Medicinal Product Dictionary (XEVMPD).
- European Medicines Agency. XEVMPDweb user manual, EMA/389113/2025, current 2026 revision.
- European Medicines Agency / PLM Portal. Reminder: XEVMPD access from 11 May 2026, published 7 May 2026.
- Regulation (EC) No 726/2004, Article 57, as amended.
- European Medicines Agency. Data on medicines (ISO IDMP standards): SPOR/PMS information and implementation guidance. Current applicable material.
Regulatory Note
This article describes Article 57/XEVMPD operations as of 9 September 2026. EMA made XEVMPDweb available to external users in February 2026 and ended external access through the former EVWEB Article 57/XEVMPD interface after 10 May 2026; from 11 May 2026 external users must use XEVMPDweb. Current EMA specifications, controlled vocabularies and implementation notices should be checked for live submissions.