> 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/pharmaceutical-and-biologic-product/medicinal-product/medicinal-product-groupers/groupers-based-on-structure.md). # Groupers Based on Structure ## Overview A high-level grouper concept supports the organization of the hierarchy based on structure: 763760008 |Medicinal product categorized by structure (product)| All substances have spatial arrangement of the atoms and molecules and bonds that they are constituted from and which therefore govern the final shape that the substance takes; this arrangement is their "structure". Substance structures often follow patterns so that similar structures are grouped together and often share particular name patterns. Medicinal products can be collected together into groups based on the structural pattern(s) of their active ingredient substance(s). Structure-based grouping is a characteristic of the active ingredient substance(s) present in the medicinal product, therefore structure-based grouping concepts are assigned (inferred) by the classifier to medicinal products and include all their child concepts (medicinal product form and clinical drug concepts) although in a browser such as the DailyBuild, the inferred grouping concepts will be shown on the proximal concept only (the "medicinal product containing" concept).

Inferred view of Medicinal product showing membership of a structural grouping (sulfonamide)

{% hint style="info" %} This section applies to grouper concepts representing a **single** structure; groupers comprised of multiple structures are described in [Groupers Based on Multiple Dispositions, Structures](https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/pharmaceutical-and-biologic-product/174691077.html). {% endhint %} ## Naming ### FSN Product containing \ (product) Align naming and case sensitivity with the Preferred Term for the concept that is selected as the attribute value for the 127489000 |Has active ingredient (attribute)|. For example, * Product containing prostaglandin (product) * Product containing A series prostaglandin (product) ### Preferred Term \-containing product Align naming and case significance with the Preferred Term for the concept that is selected as the attribute value. For example, * Prostaglandin-containing product * A series prostaglandin-containing product ### Synonym Synonyms matching the FSN are not required. ## Modeling
Stated parent concept763158003 |Medicinal product (product)
Semantic tag(product)
Definition statusDefined

Attribute:

Has active ingredient

Range: << 105590001
## Exemplars

Stated view for 350067007 |Product containing prostaglandin (product)|

Inferred view for 350067007 |Product containing prostaglandin (product)|

Stated view for 350068002 |Product containing A series prostaglandin (product)|

Inferred view for 350068002 |Product containing A series prostaglandin (product)|

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/pharmaceutical-and-biologic-product/medicinal-product/medicinal-product-groupers/groupers-based-on-structure.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.