ISO IDMP
- Stage boundary
- No direct role is recorded for Acquire, Learn + reuse.
- Known limitation
- The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving.
Decision support
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
1 of 3 selected
Decision lens
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
01 · Lifecycle reach
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| ISO IDMPStandard | ISO IDMP Suite has a direct role in Plan. | ISO IDMP Suite has no direct role recorded in Acquire. | ISO IDMP Suite has a direct role in Harmonize. | ISO IDMP Suite has a direct role in Exchange. | ISO IDMP Suite has no direct role recorded in Learn + reuse. |
02 · Boundaries
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | ISO IDMPISO IDMP Suite |
|---|---|
| Purpose & coverage | Identification of medicinal products, pharmaceutical products, substances, dose forms, routes, units, and packages across the product lifecycle. Best fitRegulated medicinal-product master data, cross-system product identity, and jurisdictional submissions such as EMA SPOR/PMS. |
| Readiness stages | PlanHarmonizeExchange |
| AI-ready contribution | Provides stable regulated product identity for joins and reasoning, but not study observations, outcomes, or ML dataset governance. |
| First limitation to test | The suite spans multiple ISO standards and amendments; implementation scope, identifiers, and timelines vary by jurisdiction and are still evolving. |
| Evidence | E1 + E2 High confidence Formal statusPublished ISO suite; revision and rollout underway ReviewSource-checked · watch |
| Maturity | Scaling International standards; jurisdictional implementation is staged |
| Sources & links | EMA IDMP / SPOR implementation (opens in a new tab)Read full profile |