01
Where it fits and where it does not
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.
- Limits
- The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.
- Best for
- Clinical and Regulatory teams working across Plan → Harmonize → Exchange.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical and Regulatory source data, metadata, and local mappings
- ISO IDMPWhat changes
Use ISO IDMP as a pinned standard across Plan → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
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.
- Governance frameworkICH E6(R3)
Both support Clinical and Regulatory work and meet around Plan, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileTMF Reference Model
Both support Clinical and Regulatory work and meet around Plan, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - StandardCDISC
Both support Clinical work and meet around Plan, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Clinical work and meet around Plan, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision ISO IDMP must support.
Pin the exact version and companion artifacts: ISO 11615:2017 + suite; revision and EU rollout in progress.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.
Run one representative end-to-end pilot and record exactly where ISO IDMP loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
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
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
EMA IDMP / SPOR implementation
Official publisher or steward guidance for this standard profile.
- Publisher
- ISO / jurisdictional implementers including EMA