XEVMPD Data Quality: Common Errors, Validation and Maintenance

Article 57 data quality is a lifecycle responsibility. A technically accepted submission can still contain incorrect content, and an initially correct record can become stale after a variation, transfer or pharmacovigilance-system change.

Regulatory and System Context

Article 57(2) of Regulation (EC) No 726/2004 requires marketing authorisation holders (MAHs) to electronically submit information on medicinal products authorised in the Union and to inform EMA of new or varied marketing authorisations using the published format. Commission Implementing Regulation (EU) No 520/2012 provides for use of XEVPRM or another agreed format for this electronic exchange.

EMA's Article 57 database is implemented through the Extended EudraVigilance Medicinal Product Dictionary (XEVMPD). As of 2026, XEVMPD remains operational while the Product Management Service (PMS) and ISO IDMP implementation proceeds in stages. External users have used the upgraded XEVMPDweb interface since legacy EVWEB access ended on 11 May 2026. This is an interface change, not evidence that the Article 57 maintenance obligation has disappeared.

EMA's current guidance states that information on new marketing authorisations is submitted within 15 calendar days from the relevant notification, and that changes to the terms of marketing authorisation are maintained within the applicable 30-calendar-day timeframe described by EMA guidance. These operational timelines should be applied using the current EMA legal notice and Q&A because the triggering date varies with the regulatory event.

What Data Quality Means

Good XEVMPD data have several dimensions:

• accuracy — the value represents the authorised product correctly;
• completeness — the required product population and applicable fields are represented;
• currency — the record reflects the current regulatory state;
• consistency — related information is coherent within the record and with authoritative sources;
• standardisation — controlled terms and structured elements are used correctly;
• traceability — the origin and history of important data can be reconstructed.

These dimensions are independent. A record can be complete but wrong, technically valid but stale, or internally consistent but based on an incorrect source.

Technical Validation and Content Quality

XEVPRM messages are subject to structural and business-rule validation. Passing those controls demonstrates that the message can be processed under the applicable rules. It does not prove that every value is substantively correct.

For example, a valid pharmaceutical-form term may be selected even though it is not the form authorised for that product. The submission can therefore be structurally acceptable while the content is wrong.

A mature control model separates:

1. transmission and acknowledgement;
2. schema/business-rule validation;
3. content verification against authoritative regulatory sources;
4. post-submission verification of the resulting record.

Common Error Categories

Product identity and presentation

Errors may involve product name, strength, pharmaceutical form, route or presentation structure. Free-text copying from an SmPC title is not a substitute for understanding how the XEVMPD data model represents those elements.

Substance and controlled terminology

Substance names and other controlled terms require use of the appropriate EMA-managed terminology. An internal preferred name, development code or local abbreviation is not automatically the correct regulatory representation.

Marketing-authorisation information

Authorisation number, status, legal entity and country-specific data can become incorrect after lifecycle events. Errors here often indicate an interface problem between regulatory operations and Article 57 maintenance rather than a simple data-entry mistake.

QPPV and PSMF-related information

Article 57 also supports information linked to the pharmacovigilance system. Changes to relevant QPPV or PSMF-location information must therefore be assessed for downstream Article 57 impact rather than being confined to PV documentation.

Building a Validation Process

A reliable validation process begins with the regulatory source rather than with the XEVMPD screen. For each material field, the organisation should know which source is authoritative and how that source is translated into the required structured representation.

Source verification

Potential sources include the marketing-authorisation decision, current approved product information, regulatory information-management system, controlled organisation data and approved pharmacovigilance-system information. Different fields may legitimately have different authoritative sources.

Structural review

The reviewer then determines whether the source has been represented using the correct XEVMPD structure and controlled terminology. This prevents the common error of treating structured product data as a collection of free-text fields.

Submission and acknowledgement

A submission should not be considered complete merely because it was sent. The resulting acknowledgement and submission status should be reviewed, and rejected or unsuccessful transactions should be investigated and resubmitted as necessary.

Post-submission verification

For higher-risk changes, verification of the resulting product record provides an additional control against situations in which the message was technically successful but the intended regulatory state was not achieved.

Maintenance Through Change Control

The strongest Article 57 control is an upstream trigger. Every relevant regulatory or PV change should create the question: does this event alter information maintained in XEVMPD?

Potential triggers include:

• a new marketing authorisation;
• product-information or other variation affecting Article 57 fields;
• marketing-authorisation transfer;
• renewal or change of authorisation status;
• suspension, revocation or withdrawal;
• legal-entity changes;
• changes to relevant pharmacovigilance contact or PSMF information.

The process should identify the affected records, applicable deadline, source documentation, responsible submitter and verification step. This is recommended operating practice; EU legislation does not prescribe a particular internal workflow or software tool.

Data Quality Controls

Maker-checker review

Independent review can be useful where manual interpretation or mapping creates material error risk. The reviewer should verify meaning, not merely repeat the entry process.

Controlled mapping tables

Where source values are routinely transformed into XEVMPD terminology, governed mapping tables reduce inconsistent manual choices. Ownership, versioning and change control matter because a defective mapping can propagate an error across many products.

Portfolio reconciliation

Periodic or event-driven reconciliation can identify records missing from the expected population, stale lifecycle states and inconsistencies across systems. Reconciliation is particularly valuable after acquisitions, divestments, migrations and large product transfers.

Exception management

Not every difference is an error. Systems can represent the same concept differently. A useful exception process distinguishes expected structural differences from discrepancies requiring investigation and records the rationale for accepted differences.

Risk-Based Quality Management

All fields should be correct, but review effort can be prioritised according to impact. A data issue affecting product identity, authorisation status, active substance or pharmacovigilance-system linkage can have broader consequences than a purely cosmetic local formatting difference.

Risk-based review should therefore consider:

• potential effect on product identification;
• pharmacovigilance and regulatory use of the field;
• number of records potentially affected by a common mapping or process;
• likelihood that the problem is systematic;
• time sensitivity of the regulatory change.

Risk prioritisation does not make low-priority errors acceptable. It determines the order and depth of investigation.

Working During the PMS/IDMP Transition

The progressive implementation of PMS and ISO IDMP increases, rather than reduces, the need for reliable source data. EMA's 2026 roadmap includes staged enrichment of product data and continued use of XEVMPD for specified activities during transition.

Organisations should therefore avoid two opposite errors: treating XEVMPD as a legacy system that no longer needs maintenance, or assuming that every PMS data element should already be maintained through the old XEVMPD process. Current EMA implementation guidance should determine which service and data flow applies at a given point in the transition.

Failure Modes and Investigation

Illustrative failure modes include a technically accepted record containing the wrong controlled term, an approved transfer not reaching the Article 57 process, a bulk mapping defect affecting many records, or a rejected XEVPRM that is not followed to successful correction.

The investigation should move beyond the individual incorrect value. It should ask how the value was generated, whether the same mechanism affected other records, whether the required lifecycle trigger occurred, and whether the organisation verified the final state.

A single wrong field can therefore be either an isolated error or a marker of a systemic data-governance weakness.

Inspection Perspective

An inspector assessing Article 57 controls could reasonably examine evidence such as:

• how the organisation identifies products within scope;
• how regulatory changes trigger Article 57 maintenance;
• how deadlines are calculated and tracked;
• how source data and controlled terminology are verified;
• how acknowledgements, errors and corrections are managed;
• how the organisation detects stale or inconsistent records;
• how vendor-submitted data are overseen when submission is outsourced.

These are illustrative inspection questions rather than published inspection findings.

Practical Checklist

For a selected product, an experienced reviewer should be able to establish:

1. why the product is represented in XEVMPD;
2. which regulatory sources support the material fields;
3. the latest lifecycle event affecting those fields;
4. whether the Article 57 update was submitted within the applicable timeframe;
5. whether a successful acknowledgement was obtained;
6. whether the resulting record was verified where appropriate;
7. whether any discrepancy has been investigated to population level where a systemic cause is plausible.

Key Takeaways

Article 57 compliance is not demonstrated by submission alone. High-quality XEVMPD data are accurate, complete, current, standardised and traceable.

Technical validation establishes processability; it does not establish regulatory truth. Effective control therefore connects authoritative source data, structured representation, successful submission, lifecycle maintenance and verification.

In 2026, XEVMPD remains an active Article 57 mechanism. XEVMPDweb has replaced the legacy external EVWEB interface, while PMS/IDMP implementation is proceeding progressively. Organisations need controlled data governance across that transition rather than assuming one system has simply replaced the other.

References

1. Regulation (EC) No 726/2004, consolidated text, Article 57(2). EUR-Lex.
2. Commission Implementing Regulation (EU) No 520/2012, consolidated text, Article 26. EUR-Lex.
3. European Medicines Agency. How to submit information on authorised and investigational medicines. Current EMA Article 57/XEVMPD reporting page.
4. European Medicines Agency. Electronic submission of Article 57(2) data: questions and answers. EMA/159776/2013, current version.
5. European Medicines Agency. Quality Control of medicinal product data submitted as per Article 57(2). EMA/661709/2014 Rev. 7, 2025.
6. European Medicines Agency. Measures for Article 57 Data Quality Assurance. EMA/465609/2015.
7. European Medicines Agency. Guidance documents related to data submission for authorised medicines, including current controlled-terminology and data-quality guidance.
8. European Medicines Agency. XEVMPDweb user interface and training information, current 2026 material.
9. European Medicines Agency. Substance and product data management services / PMS roadmap, current 2026 implementation information.

Regulatory Note

Article 57(2) establishes the legal submission framework; EMA legal notices, Q&A, user guidance and data-quality documents provide procedural detail. Internal reconciliation, maker-checker review, mapping governance and other controls described here are recommended operational practices unless made mandatory by a specific procedure or company commitment. Current EMA guidance should be checked for applicable timelines and PMS/XEVMPD transition arrangements.