Data Readiness
Knowledge BaseLife-sciences R&D
54 profiles ·
source-checked 13 Jul 2026

Standard · ISO 11615:2017 + suite; revision and EU rollout in progress

ISO IDMP Suite

Maintained by ISO / jurisdictional implementers including EMA

What it helps you do

Use ISO IDMP when you need identification of medicinal products, pharmaceutical products, substances, dose forms, routes, units, and packages across the product lifecycle.

  • Clinical
  • Regulatory
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
Regulated medicinal-product master data, cross-system product identity, and jurisdictional submissions such as EMA SPOR/PMS.
Do not use it as
Do not treat ISO IDMP as a complete solution on its own. The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.
Best for
Teams working with Clinical and Regulatory data across Plan → Harmonize → Exchange.
Maturity
ScalingUsable today, with adoption or tooling still scaling; pilot the exact stack you plan to run.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

  1. InputWhat starts

    Clinical and Regulatory data, metadata, and the local decisions around them

  2. ISO IDMPWhat changes

    ISO IDMP applies a shared standard across Plan → Harmonize → Exchange

  3. OutputWhat becomes possible

    A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.

03

A concrete example

A sponsor aligns product, substance, organization, and referential master data to the current EU IDMP implementation guide before PMS exchange.

Why it matters: Provides stable regulated product identity for joins and reasoning, but not study observations, outcomes, or ML dataset governance.

04

What it fits with

The ISO suite is implemented through jurisdictional guides and services; EMA is moving to an IDMP-compatible FHIR submission format.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Name an accountable owner and the decision ISO IDMP must support.

  2. Pin the exact version and companion artifacts: ISO 11615:2017 + suite; revision and EU rollout in progress.

  3. Map one representative input to the required standard artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Limitation to test first—and the tests that catch it

Risk

The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.

Test

Run one representative end-to-end pilot and record exactly where ISO IDMP loses context, needs an extension, or depends on another standard.

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Provides stable regulated product identity for joins and reasoning, but not study observations, outcomes, or ML dataset governance.

07

Why we believe this

Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.

Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.

Formal status
Published ISO suite; revision and rollout underway
Confidence
High
Review state
Source-checked · watch
Reviewed by
Medicinal-product data reviewer
Last verified
13 July 2026
Review again when
ISO revision or jurisdictional implementation-guide update
How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

  • Primary sourceISO 11615:2017 + suite; revision and EU rollout in progress

    EMA IDMP / SPOR implementation

    The canonical publisher or steward source used to verify this standard profile.

    Publisher
    ISO / jurisdictional implementers including EMA
    Rights
    Rights remain with the publisher; this knowledge base links to the source rather than copying it.
    Access
    Opens the publisher's source in a new tab; no external media loads on this page.
    Verified
    2026-07-13
    Open at source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.