ISO Identification of Medicinal Products standards
The ISO IDMP family standardizes the identification and description of substances, dose forms and routes, units of measurement, regulated pharmaceutical products, and regulated medicinal products. EMA is implementing these concepts through substance, product, organization, and referential master-data services.
What the authority record establishes
The ISO IDMP family standardizes the identification and description of substances, dose forms and routes, units of measurement, regulated pharmaceutical products, and regulated medicinal products. EMA is implementing these concepts through substance, product, organization, and referential master-data services.
Use in the EU is required through applicable implementing regulation and phased regulatory processes; technical requirements depend on the relevant activity and implementation phase
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
IDMP readiness is a data-governance and operating-model question, not just a product feature. Buyers need to examine source ownership, data quality, terminology services, submission interfaces, stewardship, and change propagation.
Affected operating stages
- Data-Model Definition
- Source-System Mapping
- Product And Substance Data Stewardship
- Registration And Submission Use
- Labeling And Safety Reuse
- Authority Data Submission
- Ongoing Change And Reconciliation
Capabilities to examine
Change Control
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for change control.
Regulatory Product And Registration Data
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for regulatory product and registration data.
Regulatory Activity And Commitment Tracking
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for regulatory activity and commitment tracking.
Submission Planning And Dossier Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for submission planning and dossier management.
Labeling And Structured Product Data
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for labeling and structured product data.
Health-Authority Correspondence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for health-authority correspondence.
Analytics And Management Review
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for analytics and management review.
Affected buyer audiences
- pharmaceutical regulatory affairs and operations
- regulatory data governance
- master-data management
- labeling and pharmacovigilance teams
- RIM and enterprise architecture owners
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
The ISO standards, EU legal requirement, and EMA technical implementation are distinct layers. A provider's IDMP-ready claim does not prove data completeness, governance, successful submission, or support for every implementation phase.