Article 57(2) of Regulation (EC) No 726/2004 establishes an ongoing obligation for marketing authorisation holders (MAHs) to submit and maintain accurate information on authorised human medicinal products in the European Union and European Economic Area (EU/EEA). This information is maintained in the European Medicines Agency’s (EMA) Extended EudraVigilance Medicinal Product Dictionary (XEVMPD), also known as the Article 57 database.
For MAHs, compliance involves more than submitting product information once. Relevant data must remain accurate, complete and up to date as marketing authorisations and product details change. Effective Article 57(2) data updates therefore depend on defined responsibilities, reliable source information, appropriate validation and documented submission follow-up.
With the introduction of the upgraded XEVMPD web interface in 2026, organisations must also ensure their operational processes reflect the current submission environment. Understanding the reporting requirements, identifying update triggers and maintaining robust data controls are essential to sustainable XEVMPD compliance.
Article 57(2) Is a Continuous Data Obligation, not a One-Time Submission
Article 57(2) compliance is an ongoing regulatory responsibility. MAHs must submit the required information for applicable authorised medicinal products and maintain that information when reportable details change. An initial submission establishes the product record, but it does not eliminate the need for subsequent maintenance. Changes arising from authorisation procedures, approved variations, transfers or other relevant regulatory events may require the corresponding Article 57 data to be reviewed and updated.
EMA guidance specifies reporting timelines for new marketing authorisations and amendments to marketing authorisation terms. Organisations should incorporate these timelines into their regulatory change-management procedures rather than relying on periodic reviews alone.
Key reporting timelines:
- New marketing authorisations: Submit the required information as soon as possible and no later than 15 calendar days from the relevant notification of the granting of the marketing authorisation.
- Amendments to marketing authorisation terms: Submit the required information no later than 30 calendar days from the date the amendments are authorised, following applicable events such as variations, transfers, renewals, suspensions, revocations or withdrawals.
The applicable trigger date and reporting requirement should be verified against the current EMA guidance for the specific event. Internal procedures should also assign responsibility for monitoring deadlines, preparing updates, submitting the required information and confirming the outcome.
What Regulatory Data Must MAHs Keep Accurate?
Reliable pharmaceutical regulatory data supports product identification, regulatory oversight and pharmacovigilance activities across the EU/EEA. In XEVMPD, the information must be structured and submitted according to the applicable EMA requirements, data elements, business rules and controlled vocabularies. Depending on the product and applicable reporting requirements, relevant data may include:
- Product identification: Information used to identify the medicinal product and distinguish its record from other products.
- Substance information: Relevant substance details represented using the applicable terminology and controlled vocabularies.
- Pharmaceutical characteristics: Required information describing the product’s pharmaceutical form and other applicable product attributes.
- Marketing authorisation details: Relevant authorisation information, including the applicable procedure and status.
- Marketing authorisation holder information: Required organisation and related contact details.
- Pharmacovigilance-related information: Applicable information required by the Article 57 data specifications.
The precise data elements depend on the applicable requirements and the product record. MAHs should therefore avoid relying solely on legacy records, manually maintained spreadsheets or assumptions about which fields need to change. A robust regulatory data management process connects the approved regulatory source, the relevant product record, the update decision and the final submission outcome. This helps ensure that data changes are both justified and traceable.
Which Regulatory Changes Should Trigger an Article 57 Data Review?
A defined review process helps organisations identify when a regulatory event may require an Article 57 update. The review should be linked to established regulatory activities so that reportable changes are not overlooked between submission milestones.
Common review triggers include:
- New marketing authorisations: Establish whether the required initial product information has been submitted within the applicable timeline.
- Approved variations: Assess whether the authorised change affects information maintained in XEVMPD.
- Marketing authorisation transfers: Review the relevant authorisation-holder information and other affected data elements.
- Renewals and changes in authorisation status: Determine whether the event requires a corresponding update under the applicable requirements.
- Suspensions, revocations or withdrawals: Assess the impact on the product record and the information that must be reported.
- Data discrepancies: Investigate differences identified through reconciliation, quality checks or regulatory review.
For example: When a variation is authorised, the regulatory team records the event and assesses its impact. The responsible data owner compares the relevant approved information with the existing XEVMPD record, identifies the required changes and validates the proposed data. The submission is then made through an authorised route, and the resulting acknowledgement or validation outcome is reviewed. Any errors are investigated and corrected, and completion is documented.
Why Article 57 Data Becomes Difficult Across Global Regulatory Systems
Maintaining Article 57 data can become challenging when product information is managed across multiple markets, systems, teams and regulatory procedures.
A change may be documented in one system while the corresponding product record remains unchanged elsewhere. Different teams may also interpret the same event differently, use inconsistent source information or operate separate tracking processes.
Common operational challenges include:
- Fragmented ownership: Responsibilities for regulatory assessment, data preparation, submission and verification are not clearly assigned.
- Inconsistent source information: Product records, approved documents and internal databases do not reflect the same information.
- Manual tracking: Update deadlines depend on spreadsheets, emails or individual follow-ups.
- Limited traceability: The rationale for a change, its approval and the final submission outcome are not consistently documented.
- Unresolved validation issues: Errors are identified but not tracked through to resolution and closure.
- Disconnected lifecycle processes: Article 57 data maintenance is not adequately integrated with variation management, regulatory intelligence or product lifecycle activities.
These issues can undermine data quality even when an organisation has a defined submission procedure. Sustainable compliance requires an end-to-end process that connects regulatory events with data ownership, validation, submission and verification.
XEVMPDweb and the 2026 Operational Change
The transition to XEVMPDweb is an important operational development for organisations responsible for Article 57 data maintenance. EMA made the upgraded XEVMPDweb interface available to external users in February 2026. From 11 May 2026, external users can no longer access the Article 57 database through the legacy EVWEB interface and must use XEVMPDweb, with their existing credentials.
The upgraded interface is browser-based and does not require the additional ActiveX or IE Tab components needed for the legacy interface. Specific tools, including Bulk Export and Bulk Update in the EudraVigilance Restricted area, may have separate technical requirements; users should consult the relevant EMA instructions for those functions.
For MAHs, the transition makes it important to confirm that users can access the correct environment, responsibilities remain clear and internal work instructions reflect the current interface. However, a change in the user interface does not remove the underlying Article 57(2) reporting obligations. Organisations still need to assess regulatory events, maintain accurate data, meet applicable deadlines and verify submission outcomes. The technical submission route must also be distinguished from the data-quality process itself. EMA supports submission using the Extended EudraVigilance Product Report Message (XEVPRM) schema through the EudraVigilance Gateway or its user interface, subject to the applicable requirements.
Article 57, PMS and IDMP: Why Data Governance Matters
Article 57, the EMA Product Management Service (PMS) and Identification of Medicinal Products (IDMP) are related parts of the broader regulatory data environment, but they should not be treated as interchangeable obligations.
XEVMPD supports the collection and maintenance of medicinal product information under Article 57(2). PMS and IDMP developments form part of the wider evolution towards structured, standardised medicinal product data and associated regulatory processes. For MAHs, this makes data governance increasingly important. Organisations need to understand which system and reporting requirement applies to a given activity, which data elements are involved, and how information should be maintained across connected processes.
Effective governance should include:
- Defined data ownership: Assign clear responsibility for product information and maintenance activities.
- Controlled source information: Identify the authoritative source for each relevant data element.
- Consistent data standards: Apply the current applicable specifications, business rules and controlled vocabularies.
- Documented change assessment: Record why an update is required, what information is affected and how the decision was reached.
- Traceable submission outcomes: Retain relevant evidence of submission, acknowledgement, validation and resolution.
- Lifecycle coordination: Align regulatory data maintenance with relevant product lifecycle and data-governance activities.
A well-designed regulatory data management framework can support these controls while helping teams prepare for changes in the wider regulatory data environment. It should not, however, assume that an emerging PMS or IDMP requirement automatically changes an existing Article 57 deadline.
A Practical Article 57 Data-Update Control Framework
A consistent framework can help MAHs manage Article 57(2) data updates more reliably across products and regulatory events.
- Capture and assess the regulatory event
Record the event, identify the affected product and determine whether it changes information required in XEVMPD. Establish the applicable reporting requirement and deadline. - Validate the source and proposed data
Compare the existing product record with the relevant approved or authoritative information. Check applicable data elements, terminology, completeness and consistency with current EMA requirements. - Prepare and submit the update
Prepare the required submission using the applicable XEVPRM specifications and an authorised submission route. Ensure that responsibilities and review steps are defined. - Review the submission outcome
Check the relevant acknowledgement and validation results. Investigate errors or rejected information, arrange corrections where necessary and retain evidence of the outcome. - Verify completion and maintain the record
Confirm that the intended update has been processed successfully, document closure and preserve an audit trail. Maintain the record through subsequent regulatory events and scheduled data-quality reviews.
This framework should be supported by clear standard operating procedures, appropriate staff training, deadline monitoring and escalation arrangements. Periodic reconciliation can complement event-driven updates by helping identify discrepancies that were not captured through routine workflows.
How DDReg Can Support Article 57 Data Maintenance
Managing Article 57 data effectively requires coordination between regulatory knowledge, data quality and operational execution. DDReg can support organisations in assessing their existing processes and identifying opportunities to strengthen regulatory data controls.
Support may include:
- Process and governance assessment: Reviewing responsibilities, workflows, change triggers and controls relevant to Article 57 data maintenance.
- Data-quality and reconciliation support: Helping assess data consistency, identify discrepancies and define appropriate resolution workflows.
- Lifecycle coordination: Supporting alignment between regulatory changes, product information maintenance and broader regulatory data activities.
- Process improvement: Identifying opportunities to strengthen traceability, deadline monitoring, submission follow-up and documentation.
Conclusion
Article 57(2) compliance is an ongoing responsibility that requires accurate product information, timely updates and effective data governance. For MAHs, the challenge is to ensure that relevant regulatory events consistently translate into the required XEVMPD maintenance activities.
By integrating change assessment, data validation, submission follow-up and verification into a defined framework, organisations can strengthen XEVMPD compliance and improve the reliability of their regulatory records.
As the wider regulatory data environment continues to evolve through PMS and IDMP initiatives, a disciplined approach to Article 57(2) data updates can help organisations maintain control over their data while preparing for broader data-standardisation developments.
Frequently Asked Questions
Article 57(2) compliance refers to meeting the applicable obligation to submit and maintain required information on authorised human medicinal products in the EU/EEA. MAHs must ensure that the information reported to EMA remains accurate and up to date.
New marketing authorisations must be reported as soon as possible and no later than 15 calendar days from the relevant notification of authorisation. Amendments to marketing authorisation terms following specified events, including variations, transfers, renewals, suspensions, revocations or withdrawals, must generally be reported no later than 30 calendar days from the date the amendments are authorised. MAHs should consult current EMA guidance to confirm the applicable trigger and requirements for each event.
EMA introduced the upgraded XEVMPDweb interface in February 2026. From 11 May 2026, external users must access the Article 57 database through XEVMPDweb rather than the legacy EVWEB interface. The transition changes the access interface, not the underlying Article 57(2) reporting obligations.
MAHs can improve data accuracy through defined data ownership, controlled source information, event-driven reviews, validation against applicable EMA specifications, reconciliation, submission-outcome monitoring and documented issue resolution. Integrating these controls into regulatory data management processes helps maintain reliable records over time.