IDMP / SPOR — The EMA Data Standard Every CMC Team Needs to Know
If your company submits marketing authorization applications to EMA, the Identification of Medicinal Products data standard is not a future regulatory requirement — it is a current obligation that is…
On this pageArticle overview
If your company submits marketing authorization applications to EMA, the Identification of Medicinal Products data standard is not a future regulatory requirement — it is a current obligation that is already affecting variation submissions and product lifecycle management across the EU.
I have spent the better part of two decades watching the pharmaceutical industry treat data standards as IT projects — something to be delegated below the CMC and regulatory affairs leadership level and addressed when a submission deadline forces the issue. IDMP and EMA’s SPOR platform are different. They are not metadata housekeeping. They are load-bearing infrastructure for every EU marketing authorization submission your organization makes, and the teams that have not yet built IDMP-compliant data systems are discovering that gap in the worst possible way: inside an active variation dossier, days before a submission window closes.
This article is a practitioner-level orientation to the ISO IDMP standards, the SPOR architecture, and the operational consequences for CMC and regulatory teams managing EU product portfolios today.
What IDMP and SPOR Are: The EMA Data Architecture Behind Substance and Product Identification
IDMP is a suite of five ISO standards published between 2012 and 2017 that collectively define how medicinal products, their substances, packaging, units of measurement, and organizations involved in their manufacture and authorization are identified and described in a structured, machine-readable format. The five standards are ISO 11615 (Identification of Medicinal Products, 2017), ISO 11238 (Substances, 2012), ISO 11239 (Pharmaceutical dose forms, routes of administration, and packaging, 2012), ISO 11240 (Units of measurement, 2012), and ISO 11616 (Regulated medicinal product information, 2017). Taken together, they define a data model that enables regulators, manufacturers, and health authorities to exchange and reconcile product information across borders using a shared ontology rather than free-text fields.
EMA implemented IDMP through its SPOR platform — Substance, Product, Organisation, and Referential data management services — which serves as the authoritative European registry for the data elements these standards govern. SPOR is composed of four distinct services, each with a defined governance scope. The Substance Management Service, or SMS, implements ISO 11238 and maintains the EU master list of regulated substances with assigned SPOR substance identifiers. The Product Management Service, or PMS, maintains structured product data for EU-authorized medicinal products and assigns the EU product identifier that is required in electronic product information submissions. The Organisation Management Service, or OMS, maintains the registry of organizations — MAHs, manufacturers, API suppliers — referenced in regulatory submissions. The Referential Management Service, or RMS, maintains the controlled vocabularies — dose forms, routes of administration, units of measure, administration devices — that give the other three services semantic consistency.
The EMA Guideline on the Use of ISO IDMP Standards (EMA/361611/2016) sets out the phased implementation framework under which EMA adopted SPOR as the mandatory data backbone for EU product information. That guideline, combined with subsequent ePI implementation guidance, establishes that structured IDMP data is not advisory — it is a prerequisite for compliant submissions.
How SPOR Affects Your EU Variation and Lifecycle Management Submissions Today
The operational impact of SPOR on day-to-day regulatory work is more immediate than most CMC teams realize until they encounter it firsthand.
The first point of friction is substance registration. Before submitting a new EU marketing authorization application, the active substance — and any excipients subject to IDMP data requirements — must have a registered SPOR SMS substance identifier. This identifier is derived from the ISO 11238 substance data model and must be requested through the SPOR SMS portal if it does not already exist for the substance in question. For established active pharmaceutical ingredients with long regulatory histories in other regions, it is entirely common for the substance to lack a SPOR SMS ID because no prior EU MAA required one at the time of original authorization. When a regulatory affairs team discovers this gap during eAF population, the result is a submission delay that cannot be resolved by data entry alone — it requires a formal substance registration request through the SPOR SMS workflow, which carries its own processing timeline.
The second friction point is eAF integration. The Electronic Application Form for EU submissions has SPOR ID fields for substances and organizations that are validated at the time of eAF completion. Teams that have not mapped their product portfolio to SPOR IDs before beginning an eAF encounter validation failures that are not self-explanatory — the eAF does not simply warn you that a SPOR ID is missing; it rejects the field value because the identifier format does not match the SPOR registry. CMC teams that have not been briefed on SPOR ID requirements frequently attribute this to a technical error and escalate to IT rather than to their regulatory data team, which compounds the delay.
The third impact area is variation submissions — specifically Article 61(3) notifications and Type IA and IB variations that touch product information. Under the ePI framework, product information submitted to EMA must be structured using PMS product identifiers and RMS controlled vocabulary terms. A variation to Section 6.1 (list of excipients) or Section 4.2 (posology) that would have been a straightforward text change in the legacy environment now requires that the affected data elements be mapped to valid SPOR identifiers before the variation document can be assembled. Companies without active SPOR data governance find these mappings deferred to the regulatory affairs coordinator at the moment of submission, where they become a critical path item rather than a routine data maintenance task.
The fourth and most systemic impact is product lifecycle management coherence. As EMA expands SPOR scope and ePI requirements across product types and member states, companies with ad hoc IDMP compliance will accumulate inconsistencies between their internal product master data and their SPOR-registered data. These inconsistencies surface as reconciliation failures during periodic renewals, post-approval change management, and parallel distribution notifications. The longer the gap persists, the larger the remediation effort becomes.
The UNII-to-SPOR Gap: Managing Dual-Region CMC Data in a Harmonizing World
For companies operating in both the US and EU regulatory environments, a structural data challenge exists that is not resolved by compliance with either region’s standards in isolation. The FDA uses the Unique Ingredient Identifier, or UNII, administered through the FDA Substance Registration System and maintained by the USP/NLM, as its substance identification framework. EMA uses the SPOR SMS substance identifier under ISO 11238. These two identifiers do not automatically cross-reference each other, and the substance data models underlying them — while conceptually aligned — are not identical. A substance with a registered UNII may require a separate SPOR SMS registration with different data field requirements, naming conventions that differ from INN usage in the US, and reference to EU-specific controlled vocabularies for substance class and molecular structure representation.
For CMC teams managing dual-region product portfolios, the practical consequence is that US regulatory data — SPL-formatted ingredient listings, UNII-linked substance records — cannot be directly transposed into EU SPOR submissions without a mapping and translation step. Organizations that have built their product data infrastructure around US submission requirements and then extended to the EU without a deliberate dual-region data architecture find that their substance master data, excipient records, and manufacturer organizational data each require separate reconciliation against SPOR before a first EU submission can proceed.
The path forward is not to wait for full international harmonization of UNII and SPOR — that convergence is a long-term objective of ICH M5, which addresses electronic standards for transfer of regulatory information, but it will not resolve the near-term operational gap. The practical answer is a maintained UNII-to-SPOR cross-reference table that maps each substance in your portfolio to both its US and EU identifiers, with version tracking as SPOR SMS records are updated and FDA UNII assignments are revised.
Building an IDMP Compliance Roadmap Before the EMA Enforcement Window Closes
XGene IDMP/SPOR Compliance Architecture — Six-Step Implementation Framework
1. Portfolio SPOR Registration Status Audit Map every EU-authorized product and active substance in your portfolio against the SPOR SMS and PMS registries. Identify which substances have confirmed SPOR SMS IDs, which are pending, and which have never been submitted to SMS. This audit generates the gap inventory that drives all subsequent steps.
2. Substance Registration Gap Assessment and SMS Submission Plan For each substance without a confirmed SPOR SMS ID, prepare the ISO 11238 data package required for SMS registration — including substance name, molecular structure data, substance class, and any moiety or relationship data required by the SPOR SMS data model. Sequence submissions to prioritize products with near-term variation or renewal timelines.
3. PMS Product Data Reconciliation Cross-reference your internal product master data against PMS records for each EU-authorized product. Resolve discrepancies in product name, pharmaceutical dose form coding, route of administration, pack size, and manufacturer linkages. Assign EU product identifiers to all products requiring ePI submissions.
4. eAF and Variation Workflow Integration Update your eAF preparation SOPs to include SPOR ID verification as a pre-submission checklist item. Embed SPOR SMS, PMS, and OMS ID validation into the variation dossier assembly workflow so that data gaps are identified at the planning stage rather than at the eAF population stage.
5. UNII-to-SPOR Cross-Reference Table Build and maintain a dual-region substance identifier table linking each FDA UNII to its corresponding SPOR SMS ID for every substance in your portfolio. Include version control, the date of last SPOR record verification, and the name of the data steward responsible for each entry.
6. Governance Model for Ongoing IDMP Data Stewardship Designate an IDMP data steward — a role that sits at the intersection of CMC, regulatory affairs, and information management — responsible for SPOR record maintenance, new submission registrations, and cross-functional communication of SPOR requirements to project teams. Establish a periodic SPOR data review cadence aligned with your portfolio’s variation and renewal schedule.
The enforcement window for IDMP compliance is not a future date on a regulatory calendar — it is the next variation submission your team makes to EMA that touches a product information element. Pull your EU marketing authorization portfolio and identify the SPOR SMS substance IDs for your top five active substances — if any are missing or unregistered, that gap is already affecting your ability to submit variations and ePI in the EU. The remediation is straightforward if you begin it before you need it. It is not straightforward when you discover it inside an active submission.
If your team needs support with SPOR registration, IDMP data architecture, or UNII-to-SPOR cross-reference development, I am glad to talk through where to begin.