VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Science? | ICH M5, IDMP and Medicinal Product Identification Data

Three students sit around open books and worksheets at a classroom table, reading, writing and discussing the work together.

eduKateSG · Why Science?

Identify a medicine consistently across names, strengths, formulations, markets and information systems so safety records refer to the same product

Follow ICH M5 from its 2005 draft through the five ISO Identification of Medicinal Products standards, the 2013 closure of the working group and careful product-data exchange.

Full chapter index · Science Learning Hub

A medicine can have a brand name, an ingredient name, several strengths, different packs and different names in different countries. Safety data become unreliable if two systems cannot tell whether those records describe the same substance, pharmaceutical product or regulated product.

ICH M5 began as work on data elements and standards for drug dictionaries. The 2005 document remained a draft, while the work moved into collaboration with standards-development organisations and helped produce five ISO standards for Identification of Medicinal Products, known as IDMP.

Did you know? The M5 Expert Working Group was closed in June 2013 after the five ISO IDMP standards had been finalised in 2012. That history matters: M5 should not be described as a final ICH implementation guideline when its lasting outcome is the international standards and later implementation work.

For students, M5 is a joyful data lesson: naming is part of measurement. A reliable product record keeps the substance, dose form, route, strength, units, manufacturer, market authorisation and identifiers connected without pretending that one name is enough.

CHAPTER 1 OF 17 · See why product identity is hard

1. Medicinal-product identity is a relationship, not one label

Back to contents

A brand name can be reused or translated, while the same active substance can appear in different strengths, dose forms, manufacturers and markets. Reliable identification therefore needs structured attributes and relationships rather than text matching alone.

The detective work in medicinal-product identity is a relationship, not one label begins by asking what kind of thing a code identifies. A brand name can be reused or translated, while the same active substance can appear in different strengths, dose forms, manufacturers and markets. Reliable identification therefore needs structured attributes and relationships rather than text matching alone. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Try this

Build an identity receipt for medicinal-product identity is a relationship, not one label. Trace medicinal-product identity is a relationship, not one label from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep the original label beside every mapped value. Respect this limit: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

A strong science note separates observation from interpretation. Trace medicinal-product identity is a relationship, not one label from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Trace medicinal-product identity is a relationship, not one label from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Contents · Next chapter

CHAPTER 2 OF 17 · See why product identity is hard

2. ICH adopted the M5 topic in 2003

Back to contents

The official history records a November 2003 concept paper and creation of an Expert Working Group to standardise medicinal-product identifiers and related terminology, especially for electronic exchange of individual case safety reports across regions.

For ich adopted the m5 topic in 2003, sameness is a claim supported by attributes and governance. The official history records a November 2003 concept paper and creation of an Expert Working Group to standardise medicinal-product identifiers and related terminology, especially for electronic exchange of individual case safety reports across regions. Preserve this guardrail: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Try this

Run a false-match challenge for ich adopted the m5 topic in 2003. Challenge whether ich adopted the m5 topic in 2003 distinguishes a substance, pharmaceutical product, regulated product and package. Find two records that look similar but describe different entities. Preserve this boundary: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

A strong science note separates observation from interpretation. Challenge whether ich adopted the m5 topic in 2003 distinguishes a substance, pharmaceutical product, regulated product and package. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Challenge whether ich adopted the m5 topic in 2003 distinguishes a substance, pharmaceutical product, regulated product and package. Keep this boundary visible: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 17 · See why product identity is hard

3. The 2005 M5 document was a consultation draft

Back to contents

FDA lists the September 2005 M5 guidance as draft and not for implementation. It proposed business requirements for medicinal-product identifiers plus controlled vocabularies for routes of administration and units of measurement.

A trustworthy account of the 2005 m5 document was a consultation draft keeps names, entities, identifiers and versions in one inspectable chain. FDA lists the September 2005 M5 guidance as draft and not for implementation. It proposed business requirements for medicinal-product identifiers plus controlled vocabularies for routes of administration and units of measurement. Remember: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Try this

Audit the mapping route for the 2005 m5 document was a consultation draft. Reconstruct the 2005 m5 document was a consultation draft with issuing authority, standard, version, mapping rule and exception log. Record every version, transformation and human decision. Keep this limit: Standard product identity does not prove product quality, safety or therapeutic equivalence.

A strong science note separates observation from interpretation. Reconstruct the 2005 m5 document was a consultation draft with issuing authority, standard, version, mapping rule and exception log. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Reconstruct the 2005 m5 document was a consultation draft with issuing authority, standard, version, mapping rule and exception log. Keep this boundary visible: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 17 · See why product identity is hard

4. Standards-development organisations extended the work

Back to contents

In 2006 ICH decided to collaborate with standards-development organisations so technical specifications could support wider interoperability across regulatory and healthcare communities. The revised draft was submitted to ISO in 2007.

The detective work in standards-development organisations extended the work begins by asking what kind of thing a code identifies. In 2006 ICH decided to collaborate with standards-development organisations so technical specifications could support wider interoperability across regulatory and healthcare communities. The revised draft was submitted to ISO in 2007. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Try this

Build an identity receipt for standards-development organisations extended the work. Test standards-development organisations extended the work against translated names, changed packs, combination products and legacy local codes. Keep the original label beside every mapped value. Respect this limit: A clean mapping must preserve uncertainty and the original source value.

A strong science note separates observation from interpretation. Test standards-development organisations extended the work against translated names, changed packs, combination products and legacy local codes. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Test standards-development organisations extended the work against translated names, changed packs, combination products and legacy local codes. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 17 · Understand the five IDMP standards

5. ISO 11238 addresses substances

Back to contents

The IDMP family includes ISO 11238 for the identification and exchange of regulated information on substances. A substance identity needs defined composition and relationships, not only a common chemical or biological name.

For iso 11238 addresses substances, sameness is a claim supported by attributes and governance. The IDMP family includes ISO 11238 for the identification and exchange of regulated information on substances. A substance identity needs defined composition and relationships, not only a common chemical or biological name. Preserve this guardrail: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Try this

Run a false-match challenge for iso 11238 addresses substances. Trace iso 11238 addresses substances from the source label through substances, strength, dose form, route, pack and the relevant identifier. Find two records that look similar but describe different entities. Preserve this boundary: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

A strong science note separates observation from interpretation. Trace iso 11238 addresses substances from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Trace iso 11238 addresses substances from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 17 · Understand the five IDMP standards

6. ISO 11239 addresses dose forms, units of presentation, routes and packaging

Back to contents

Standard terms for the pharmaceutical dose form, route of administration, unit of presentation and packaging help distinguish products that contain similar ingredients but are prepared, administered or counted differently.

A trustworthy account of iso 11239 addresses dose forms, units of presentation, routes and packaging keeps names, entities, identifiers and versions in one inspectable chain. Standard terms for the pharmaceutical dose form, route of administration, unit of presentation and packaging help distinguish products that contain similar ingredients but are prepared, administered or counted differently. Remember: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Try this

Audit the mapping route for iso 11239 addresses dose forms, units of presentation, routes and packaging. Challenge whether iso 11239 addresses dose forms, units of presentation, routes and packaging distinguishes a substance, pharmaceutical product, regulated product and package. Record every version, transformation and human decision. Keep this limit: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

A strong science note separates observation from interpretation. Challenge whether iso 11239 addresses dose forms, units of presentation, routes and packaging distinguishes a substance, pharmaceutical product, regulated product and package. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Challenge whether iso 11239 addresses dose forms, units of presentation, routes and packaging distinguishes a substance, pharmaceutical product, regulated product and package. Keep this boundary visible: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 17 · Understand the five IDMP standards

7. ISO 11240 addresses units of measurement

Back to contents

A numerical strength is incomplete without a unit and representation rule. Standardised units, prefixes and expression support consistent comparisons and reduce dangerous errors created by incompatible or ambiguous quantities.

The detective work in iso 11240 addresses units of measurement begins by asking what kind of thing a code identifies. A numerical strength is incomplete without a unit and representation rule. Standardised units, prefixes and expression support consistent comparisons and reduce dangerous errors created by incompatible or ambiguous quantities. Keep this boundary visible: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Try this

Build an identity receipt for iso 11240 addresses units of measurement. Reconstruct iso 11240 addresses units of measurement with issuing authority, standard, version, mapping rule and exception log. Keep the original label beside every mapped value. Respect this limit: Standard product identity does not prove product quality, safety or therapeutic equivalence.

A strong science note separates observation from interpretation. Reconstruct iso 11240 addresses units of measurement with issuing authority, standard, version, mapping rule and exception log. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Reconstruct iso 11240 addresses units of measurement with issuing authority, standard, version, mapping rule and exception log. Keep this boundary visible: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 17 · Understand the five IDMP standards

8. ISO 11615 addresses regulated medicinal products

Back to contents

This standard provides data elements and structures for identifying medicinal products as regulated in a jurisdiction, including authorisation and product-level relationships. The regulated product is not identical to a substance or generic clinical description.

For iso 11615 addresses regulated medicinal products, sameness is a claim supported by attributes and governance. This standard provides data elements and structures for identifying medicinal products as regulated in a jurisdiction, including authorisation and product-level relationships. The regulated product is not identical to a substance or generic clinical description. Preserve this guardrail: A clean mapping must preserve uncertainty and the original source value.

Try this

Run a false-match challenge for iso 11615 addresses regulated medicinal products. Test iso 11615 addresses regulated medicinal products against translated names, changed packs, combination products and legacy local codes. Find two records that look similar but describe different entities. Preserve this boundary: A clean mapping must preserve uncertainty and the original source value.

A strong science note separates observation from interpretation. Test iso 11615 addresses regulated medicinal products against translated names, changed packs, combination products and legacy local codes. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Test iso 11615 addresses regulated medicinal products against translated names, changed packs, combination products and legacy local codes. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 17 · Connect identity to safety exchange

9. ISO 11616 addresses pharmaceutical products

Back to contents

The pharmaceutical-product view connects active ingredients, strength and dose form in a way that can support comparison across regulated products. Its identity serves a different purpose from a pack, trade name or regional authorisation identifier.

A trustworthy account of iso 11616 addresses pharmaceutical products keeps names, entities, identifiers and versions in one inspectable chain. The pharmaceutical-product view connects active ingredients, strength and dose form in a way that can support comparison across regulated products. Its identity serves a different purpose from a pack, trade name or regional authorisation identifier. Remember: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Try this

Audit the mapping route for iso 11616 addresses pharmaceutical products. Trace iso 11616 addresses pharmaceutical products from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record every version, transformation and human decision. Keep this limit: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

A strong science note separates observation from interpretation. Trace iso 11616 addresses pharmaceutical products from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Trace iso 11616 addresses pharmaceutical products from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 17 · Connect identity to safety exchange

10. The five standards form one connected information model

Back to contents

Substance, pharmaceutical product, medicinal product, dose form, route, packaging and unit data must link coherently. Implementing one identifier without its supporting attributes can create false matches that look precise but describe different products.

The detective work in the five standards form one connected information model begins by asking what kind of thing a code identifies. Substance, pharmaceutical product, medicinal product, dose form, route, packaging and unit data must link coherently. Implementing one identifier without its supporting attributes can create false matches that look precise but describe different products. Keep this boundary visible: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Try this

Build an identity receipt for the five standards form one connected information model. Challenge whether the five standards form one connected information model distinguishes a substance, pharmaceutical product, regulated product and package. Keep the original label beside every mapped value. Respect this limit: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

A strong science note separates observation from interpretation. Challenge whether the five standards form one connected information model distinguishes a substance, pharmaceutical product, regulated product and package. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Challenge whether the five standards form one connected information model distinguishes a substance, pharmaceutical product, regulated product and package. Keep this boundary visible: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 17 · Connect identity to safety exchange

11. M5 was motivated by pharmacovigilance exchange

Back to contents

The original need included identifying medicines consistently in ICH E2B individual case safety reports. Product identity supports case aggregation, duplicate detection, signal analysis and communication while the safety report keeps its separate clinical and causality fields.

For m5 was motivated by pharmacovigilance exchange, sameness is a claim supported by attributes and governance. The original need included identifying medicines consistently in ICH E2B individual case safety reports. Product identity supports case aggregation, duplicate detection, signal analysis and communication while the safety report keeps its separate clinical and causality fields. Preserve this guardrail: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Try this

Run a false-match challenge for m5 was motivated by pharmacovigilance exchange. Reconstruct m5 was motivated by pharmacovigilance exchange with issuing authority, standard, version, mapping rule and exception log. Find two records that look similar but describe different entities. Preserve this boundary: Standard product identity does not prove product quality, safety or therapeutic equivalence.

A strong science note separates observation from interpretation. Reconstruct m5 was motivated by pharmacovigilance exchange with issuing authority, standard, version, mapping rule and exception log. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Reconstruct m5 was motivated by pharmacovigilance exchange with issuing authority, standard, version, mapping rule and exception log. Keep this boundary visible: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 17 · Connect identity to safety exchange

12. Names and identifiers answer different questions

Back to contents

A name helps people recognise a product; an identifier lets systems refer to a defined entity. Neither is meaningful without the issuing system, version, jurisdiction and type of entity being identified.

A trustworthy account of names and identifiers answer different questions keeps names, entities, identifiers and versions in one inspectable chain. A name helps people recognise a product; an identifier lets systems refer to a defined entity. Neither is meaningful without the issuing system, version, jurisdiction and type of entity being identified. Remember: A clean mapping must preserve uncertainty and the original source value.

Try this

Audit the mapping route for names and identifiers answer different questions. Test names and identifiers answer different questions against translated names, changed packs, combination products and legacy local codes. Record every version, transformation and human decision. Keep this limit: A clean mapping must preserve uncertainty and the original source value.

A strong science note separates observation from interpretation. Test names and identifiers answer different questions against translated names, changed packs, combination products and legacy local codes. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Test names and identifiers answer different questions against translated names, changed packs, combination products and legacy local codes. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 17 · Keep implementation status visible

13. Controlled vocabularies need active stewardship

Back to contents

Routes, dose forms, units and other reference data evolve. Implementers need governance for additions, retirements, translations, synonyms, effective dates and mappings so an update does not silently change a historical record.

The detective work in controlled vocabularies need active stewardship begins by asking what kind of thing a code identifies. Routes, dose forms, units and other reference data evolve. Implementers need governance for additions, retirements, translations, synonyms, effective dates and mappings so an update does not silently change a historical record. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Try this

Build an identity receipt for controlled vocabularies need active stewardship. Trace controlled vocabularies need active stewardship from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep the original label beside every mapped value. Respect this limit: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

A strong science note separates observation from interpretation. Trace controlled vocabularies need active stewardship from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Trace controlled vocabularies need active stewardship from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 17 · Keep implementation status visible

14. Mapping legacy dictionaries requires evidence

Back to contents

Older databases may combine substance, product and pack information in one local code. Migration should preserve the original value, mapping rule, confidence, exceptions and reviewer decision rather than overwrite uncertainty with a neat new identifier.

For mapping legacy dictionaries requires evidence, sameness is a claim supported by attributes and governance. Older databases may combine substance, product and pack information in one local code. Migration should preserve the original value, mapping rule, confidence, exceptions and reviewer decision rather than overwrite uncertainty with a neat new identifier. Preserve this guardrail: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Try this

Run a false-match challenge for mapping legacy dictionaries requires evidence. Challenge whether mapping legacy dictionaries requires evidence distinguishes a substance, pharmaceutical product, regulated product and package. Find two records that look similar but describe different entities. Preserve this boundary: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

A strong science note separates observation from interpretation. Challenge whether mapping legacy dictionaries requires evidence distinguishes a substance, pharmaceutical product, regulated product and package. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Challenge whether mapping legacy dictionaries requires evidence distinguishes a substance, pharmaceutical product, regulated product and package. Keep this boundary visible: An identifier is meaningful only with its entity type, issuer, version and jurisdiction.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 17 · Keep implementation status visible

15. The M5 working group closed after IDMP finalisation

Back to contents

EMA records that five ISO IDMP standards were finalised in November 2012 and that ICH agreed to sunset the M5 EWG in June 2013. Later maintenance and broader implementation sit outside the old M5 working group.

A trustworthy account of the m5 working group closed after idmp finalisation keeps names, entities, identifiers and versions in one inspectable chain. EMA records that five ISO IDMP standards were finalised in November 2012 and that ICH agreed to sunset the M5 EWG in June 2013. Later maintenance and broader implementation sit outside the old M5 working group. Remember: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Try this

Audit the mapping route for the m5 working group closed after idmp finalisation. Reconstruct the m5 working group closed after idmp finalisation with issuing authority, standard, version, mapping rule and exception log. Record every version, transformation and human decision. Keep this limit: Standard product identity does not prove product quality, safety or therapeutic equivalence.

A strong science note separates observation from interpretation. Reconstruct the m5 working group closed after idmp finalisation with issuing authority, standard, version, mapping rule and exception log. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Reconstruct the m5 working group closed after idmp finalisation with issuing authority, standard, version, mapping rule and exception log. Keep this boundary visible: Standard product identity does not prove product quality, safety or therapeutic equivalence.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 17 · Keep implementation status visible

16. E2B use is a bounded part of the wider IDMP landscape

Back to contents

The E2B implementation group incorporated use of the five ISO standards for electronic ICSR exchange, while broader IDMP maintenance and publication requirements were outside that group’s remit. A project must identify which implementation authority and use case it follows.

The detective work in e2b use is a bounded part of the wider idmp landscape begins by asking what kind of thing a code identifies. The E2B implementation group incorporated use of the five ISO standards for electronic ICSR exchange, while broader IDMP maintenance and publication requirements were outside that group’s remit. A project must identify which implementation authority and use case it follows. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Try this

Build an identity receipt for e2b use is a bounded part of the wider idmp landscape. Test e2b use is a bounded part of the wider idmp landscape against translated names, changed packs, combination products and legacy local codes. Keep the original label beside every mapped value. Respect this limit: A clean mapping must preserve uncertainty and the original source value.

A strong science note separates observation from interpretation. Test e2b use is a bounded part of the wider idmp landscape against translated names, changed packs, combination products and legacy local codes. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Test e2b use is a bounded part of the wider idmp landscape against translated names, changed packs, combination products and legacy local codes. Keep this boundary visible: A clean mapping must preserve uncertainty and the original source value.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 17 · Keep implementation status visible

17. A complete M5-IDMP receipt reconstructs product identity

Back to contents

The record includes source product name, language and market, authorisation and organisation, substance identifiers, pharmaceutical and medicinal-product identifiers, dose form, route, strength, units, pack, reference-data versions, mapping method, confidence, exceptions and exchange purpose.

For a complete m5-idmp receipt reconstructs product identity, sameness is a claim supported by attributes and governance. The record includes source product name, language and market, authorisation and organisation, substance identifiers, pharmaceutical and medicinal-product identifiers, dose form, route, strength, units, pack, reference-data versions, mapping method, confidence, exceptions and exchange purpose. Preserve this guardrail: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Try this

Run a false-match challenge for a complete m5-idmp receipt reconstructs product identity. Trace a complete m5-idmp receipt reconstructs product identity from the source label through substances, strength, dose form, route, pack and the relevant identifier. Find two records that look similar but describe different entities. Preserve this boundary: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

A strong science note separates observation from interpretation. Trace a complete m5-idmp receipt reconstructs product identity from the source label through substances, strength, dose form, route, pack and the relevant identifier. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.

Evidence checkpoint

Trace a complete m5-idmp receipt reconstructs product identity from the source label through substances, strength, dose form, route, pack and the relevant identifier. Keep this boundary visible: The 2005 M5 document remained draft and should not be presented as a final ICH guideline.

Contents · Previous chapter

M5 and IDMP identity map

QuestionEvidence to captureBoundary to retain
What is being identified?Substance, pharmaceutical product, medicinal product or packDo not collapse entity types
Which attributes define it?Strength, dose form, route, units and authorisationA name alone is insufficient
Which rule applies?ISO standard, regional implementation and versionM5 itself remained draft
Can the match be audited?Source value, mapping, confidence and exceptionPreserve uncertainty

Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect these habits to career pathways built from subject capabilities.

M5 shows that good medicine data begin with careful identity. The working group may have closed, yet its scientific lesson remains fresh: when systems describe the same product in the same structured way, safety evidence can travel farther without losing its subject.

Primary sources and verification date

Source status checked 27 October 2026. FDA guidance describes the agency’s current thinking and does not replace applicable statutes, regulations or product-specific communication with FDA.

Continue the evidence journey