Page History

This section provides some guidance on how to use or implement the EDQM to SNOMED CT pharmaceutical dose form map.

Capsule dose forms

Situations where it would appear that EDQM is "defining by exclusion"

Statements like "xxx are excluded" are not part of the definition of the concept, they are guidance to manufacturers when selecting a dose form for a product to be explicit rather than select what is in effect a grouper concept.

For example: "Oromucosal" is a grouper site in EDQM, just as it is in SNOMED CT, even though it might appear that the child concepts (like sublingual) are excluded.  Therefore, a 1..1 exact match between an oromucosal concept in EDQM and an oromucosal concept in SNOMED CT is acceptable.

Translations

Need to be mindful of translation of PDF concepts and supporting concepts - e.g. oromucosal = buccale (Fr); buccal = buccogingival (Fr) an Spanish uses buccale for both

No match concepts

Thread, wound stick - try to find a more appropriate dose form for any individual RCD/CD that is authorised with these dose forms which are not well enough defined for addition to SNOMED CT.  See also below about medical devices

The device/physical object boundary

Some dose forms and the products that use them cross the boundary into physical objects/medical devices - this includes "medicated thread" used in dental impressions

Medicated sponge has a 1..* map as SNOMED CT is explicit about where the sponge is located.  These will need to be mapped on a case by case basis per product

Especially for ears, nose etc.  “Wash” is about “in and out” rather than (for example, a simple solution) being left in situ to have a (local) therapeutic effect 

Drops and Sprays

Use of the grouper concepts for CDs in International Edition

The map is released as a standard RF2 component. A derivative product that can be used in an implementation along with the corresponding version of the International edition and any relevant national extensions. 

Loading the map and its dependencies in a terminology server will support the conversion between EDQM and SNOMED codes using a REST API, supporting integration in health information systems and simple adaptation to new versions of the maps. In simpler use cases, the human readable version released as a spreadsheet in the package Release Notes may be sufficient for single-time conversions.

...