XEVMPD, SPOR, and the EU’s Product Data Infrastructure

The EU has built out the most concrete, operational implementation of the product identification discipline this module has covered, and it’s worth knowing the specific pieces by name, because this is genuinely current, actively-taught, legally mandatory infrastructure — not an abstract standard sitting in a document somewhere. The eXtended EudraVigilance Medicinal Product Dictionary (XEVMPD), commonly called the "Article 57 database" after the specific regulation provision requiring it, is where marketing authorisation holders operating in the EU/EEA are legally required to submit medicinal product data, under Regulation (EC) No. 726/2004 as amended.

Getting data into XEVMPD happens through a specific technical message format, the eXtended EudraVigilance Product Report Message (XEVPRM), submitted via EVWEB, the actual data entry tool companies use day to day. And critically, this isn’t simply a system organisations are free to use however they see fit — EMA requires at least one person from every marketing authorisation holder organisation to successfully complete a specific XEVMPD training course and pass its knowledge evaluation before the organisation can even register with EudraVigilance for data submission at all. This is precisely the kind of concrete, specific, legally-mandated detail that separates genuine EU regulatory fluency from a general familiarity with "the EU has rules about this."

SPOR — Substance, Product, Organisation, Referential data management services — is EMA’s longer-term, more structurally ambitious programme, implementing the full IDMP standards Lesson 16.3 covered across EMA’s entire referential data management infrastructure, gradually superseding XEVMPD’s narrower, EudraVigilance-specific scope with a fuller, IDMP-aligned system covering substance data, product data, organisation data, and the broader reference data all of it depends on. This is an active, ongoing implementation programme rather than a completed rollout, which is exactly why this lesson’s earlier callout flagged IDMP as a maturing standard rather than a fixed, finished system.

This entire infrastructure sits inside the same EU regulatory architecture Module 2 built the general framework for, and it connects directly to Module 7’s EudraVigilance signal-management content — accurate, structurally sound product data in XEVMPD/SPOR is precisely what makes the signal detection and case linkage this course has built throughout actually work correctly at the product-identification level, the same way MedDRA coding quality (Module 4) makes it work at the event level.