> 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-infusion-and-or-injection.md).

# Groupers Based on Infusion and or Injection

Pharmaceutical dose form grouper concepts specifying "infusion *and/or* injection" are modeled using General Concept Inclusions (GCIs).

* For example,
  * 1208958005 |Conventional release solution for infusion and/or injection (dose form)|
  * 1236769008 |Gas for conventional release dispersion for infusion and/or injection (dose form)|
  * 1237269000 |Concentrate for conventional release solution for infusion and/or injection (dose form)|

The following are out of scope for the international release but can be added to national extensions, concepts that specify:

* "infusion or injection"
* "infusion and injection"

## Clinical drugs with *infusion and/or injection*

Clinical drugs modeled using pharmaceutical dose form groupers for “infusion *and/or* injection” are in scope for the International Release.

For example,

1252729004 |Product containing precisely ofloxacin 2 milligram/1 milliliter conventional release solution for infusion and/or injection (clinical drug)| is modeled with |Has manufactured dose form (attribute)| of |Conventional release solution for infusion and/or injection (dose form)|.

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FT7Y4CrjwyWAK553CBhPs%2Fimage.png?alt=media&amp;token=b4d5ce0b-4eed-4085-9189-eaca4efcc8c7" alt=""><figcaption><p>Stated view of 1252729004 |Product containing precisely ofloxacin 2 milligram/1 milliliter conventional release solution for infusion and/or injection (clinical drug)|</p></figcaption></figure>

In cases where corresponding clinical drugs for both injection and infusion exist, the grouper for “infusion and/or injection” should be created. In other words, when creating a new clinical drug for infusion and an existing injection concept exists with the same substance and strength, then the grouper "for infusion and/or injection" should be created.

For example,

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FseaCOZC1EUhpFc7ZIAA8%2Fimage.png?alt=media&amp;token=f24c07a6-b7be-4349-9bab-00f21273144a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/pharmaceutical-and-biologic-product/images/232391040.png" alt=""><figcaption></figcaption></figure>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Groupers%20Based%20on%20Infusion%20and%20or%20Injection" class="button primary">Provide Feedback</a>


---

# 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-infusion-and-or-injection.md?ask=<question>&goal=<user_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.