> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/substance/substance-naming-and-modeling-conventions/guidelines-for-substance-hierarchy-grouper-concepts.md). # Substance Groupers In the SNOMED CT substance hierarchy, there are a large number of grouper concepts. Currently, groupers within the substances can be considered to be structural groupers, disposition groupers, or role based. The intent is to build the SNOMED CT substance hierarchy along structural or disposition groupers and use a |Has disposition (attribute)| relationship to define grouper concepts in the substance hierarchy. Grouper concepts that do not reference structural or disposition properties of a substance should not be included within the substance hierarchy and existing role concepts are considered for relocation outside of the substance hierarchy. ### Structure based Groupers Groupers that organize substances by their chemical structure are used as the main hierarchy for substances. Where substances are heterogeneous and do not have a single identifiable chemical structure, such as those of biological origin, it may be more appropriate to organize them by source. ### Dispositions Groupers In the context of substances, a disposition is a behavior that a substance will exhibit or participate in, given the appropriate context. This context-based definition of disposition would allow us to assign |Has disposition (attribute)| values that are necessarily true, even though the substance does not exhibit the disposition in all contexts. ### Role based Groupers Role based groupers are associated with a particular purpose or outcome. Roles are a function of the way the substance is formulated or presented and so may not be applicable to all products containing that substance, which may lead to incorrect classification of concepts using role groupers as attribute values. At this time, the existing Substance role groupers will remain in situ with no change. However, additional concepts of this type will not be created, and requests for new instances will be rejected. {% hint style="danger" %} Known issues with use of Substance role groupers, including potential incorrect classification, will remain and should be considered by stakeholders at their discretion. {% endhint %} * [Substance Groupers Based on Structure](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/substance/substance-naming-and-modeling-conventions/guidelines-for-substance-hierarchy-grouper-concepts/substance-groupers-based-on-structure.md) * [Substance Groupers Based on Disposition](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/substance/substance-naming-and-modeling-conventions/guidelines-for-substance-hierarchy-grouper-concepts/substance-groupers-based-on-disposition.md) * [Substance Groupers Based on Both Structure and Disposition](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/substance/substance-naming-and-modeling-conventions/guidelines-for-substance-hierarchy-grouper-concepts/substance-groupers-based-on-both-structure-and-disposition.md) ### Restructure of the Substance hierarchy Previously, the substances hierarchy in SNOMED CT was organized using a number of different axes, some of which did not comply with the terminological principle of being always true. This resulted in incorrect inferences both within the substance hierarchy and in other hierarchies where substances were used to define concepts. To avoid this, the substances hierarchy has been organized by characteristics that are always true (e.g., chemical structure). For substances where the structure is unknown or the substance is heterogeneous, other characteristics that are always true should be used as parent concepts within the substances hierarchy. The current substances top level hierarchy includes a number of grouper concepts that are role- or use case-based. The proposal is to create a substances top level hierarchy as below.
The grouper concepts that are retained as top level substance concepts will need review of their descendants, but ultimately, it should provide a consistent hierarchy. There are similarities in the scope of *ISO 11238 Health informatics – Identification of medicinal products – Data Elements and Structures for the Unique Identification and Exchange of Regulated Information on Substances* and the SNOMED CT substances revision, since both consider a substance to be defined by properties such as molecular structure, and not by how it is formulated or used. IDMP groups substances as being one of five types of single substances: * (simple) chemical * protein/peptide * nucleic acid * polymer * structurally-diverse or they are classified as a mixture. In IDMP, the definition of a mixture is much broader that would be perceived by clinical users. IDMP defines starches as mixtures, and also compounds, such as isophane insulin and gentamicin sulfate, as mixtures. This broad definition for mixtures would mean that many of the SNOMED CT substances would be classified as mixtures. These IDMP types are not represented in SNOMED CT, since they are not mutually exclusive and are open to some interpretation. The IDMP documentation does provide guidance on the selection of the correct type for a substance but also acknowledges that a single substance may have two separate type definitions. In addition, the use of the word “mixture” in the substances hierarchy is to be discouraged, since as a general scope statement, SNOMED CT does not include combination substances that are a mixture of more than one individual chemical even when the two exhibit a synergistic effect, e.g., tazobactam and piperacillin. *Changes to SNOMED CT concept model in the future to permit the use of concepts within the products hierarchy to model disorder and findings concepts means that these combined substances concepts will no longer be required, and so, will be inactivated at that time.* ### Differences between SNOMED CT substances and IDMP substances The scope of substances in SNOMED CT is broader than that of IDMP, since the definition of regulated products is not the only use case supported by the SNOMED CT substances hierarchy. IDMP classes are used to identify which features could/should be identified as defining. This is different from the SNOMED CT requirement to identify top level concepts to support a hierarchy that provides a logical structure for substance concepts. IDMP makes a distinction between Substance and the more closely defined Specified Substance. Substances are “any matter of defined composition that has discrete existence, whose origin may be biological, mineral or chemical". 1. Specified Substances are "defined by groups of elements that describe multi-substance materials or specifies further information on substances relevant to the description of Medicinal Products". 2. Specified substances include mixture substances, substances defined by pharmacopoeial specification or substances where a particular manufacturing process is specified. In order for SNOMED CT to support the IDMP work, whose primary goal is to define unambiguously all substances present in regulated products, it is necessary for both the concepts that are IDMP Substances and those that are IDMP Specified Substances to be present in the SNOMED CT Substance hierarchy. Stereoisomers, hydrates, and solvates are included in the SNOMED CT substances hierarchy as concepts, as well as concepts to represent their base chemical in the SNOMED CT substance hierarchy. Since both IDMP Substances and IDMP Specified Substances are candidate concepts to be used in the ingredient role attributes, it does not add value in the definition of these concepts to separately identify IDMP Substances and IDMP Specified Substances in SNOMED CT and would likely cause confusion where substance concepts are used to define concepts outside the scope of IDMP and the medicinal product hierarchy. Provide Feedback --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/substance/substance-naming-and-modeling-conventions/guidelines-for-substance-hierarchy-grouper-concepts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.