ISO IDMP standardizes medicinal-product identity—not regulatory approval

Product identity and regulatory approval answer different questions

The direct answer in EMA's overview is that ISO IDMP standardizes how medicinal products are identified and described so information can be exchanged reliably. EMA separately says the scope spans products in development, investigational products, products under evaluation, and authorized products. A product can therefore have structured identity data while occupying a materially different regulatory state from another product represented with the same family of standards.

A regulatory-quality system should keep medicinal-product identity, application or procedure, jurisdiction, authorization status, approved particulars, submission status, authority correspondence, and lifecycle dates as linked but distinct records. A populated identifier or accepted master-data transaction cannot by itself establish that an application was approved, that a variation was accepted, that product information is current in every market, or that a dossier is complete.

Five standards create a shared data structure

EMA identifies five ISO IDMP standards covering substances; pharmaceutical dose forms, units of presentation, routes of administration, and packaging; units of measurement; regulated pharmaceutical product information; and regulated medicinal product information. The overview also lists medicinal-product name, ingredient substances, route and strength, marketing authorization, clinical particulars, packaging, and manufacturing among the aspects used to describe a human medicinal product.

That structure supports a more exact product record, but the relationships matter as much as the fields. Buyers should test whether a platform preserves the source and version for a substance or referential term, connects packaging and manufacturing context to the correct product representation, handles translations and market-specific values, and retains the history when an authority or accountable data steward changes a value.

A standard identifier does not collapse lifecycle states

EMA describes benefits across pharmacovigilance, regulatory submissions, clinical trials, and good manufacturing practice. Reuse across those settings depends on consistent identity, but each setting still has its own purpose, evidence, decision owner, confidentiality limits, and status. A safety case, trial record, submission package, inspection record, and authorized product record should not become interchangeable merely because they refer to the same medicinal product.

A useful demonstration should follow one product from development through an application, authority questions, authorization, a later variation, and post-authorization safety use. The system should show which identifiers and master-data values persist, which records are jurisdiction-specific, who approves changes, how downstream uses are notified, and how an earlier representation can be reconstructed without rewriting the regulatory decision history.

Implementation status needs its own evidence

EMA says it is implementing ISO IDMP in phases through substance, product, organization, and referential master data. The same page notes that data on authorized human medicines has been mandatory in an earlier format since July 2012 and describes replacement by an ISO IDMP-compatible format. Teams therefore need the current EMA implementation material, procedure scope, applicable data requirement, format, transition state, and effective date rather than assuming the existence of the standards means every workflow has already moved to one final operating model.

This overview establishes the purpose, scope, and phased regulatory context of ISO IDMP; it does not decide whether a particular medicine is authorized, whether submitted data are complete or accepted, or whether a software implementation is conformant. Regulatory, data-governance, safety, quality, and legal owners should apply current authority instructions and product facts. Buyers should require source-linked data lineage and status-specific evidence instead of an undifferentiated 'IDMP ready' label.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.