> 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/index-1/index/medicinal-product-form-containing.md).

# Medicinal Product Form containing

## Overview

The `|Product containing x in y dose form (medicinal product form)|` concept is an abstract representation of active ingredient(s) and dose form intended site for a medicinal product. The medicinal product must contain the active ingredient(s) specified in the FSN but may also contain a modification of the active ingredient(s) specified in the FSN or may contain additional active ingredient(s) as well.

For example,

* Product containing axitinib in oral dose form (medicinal product form)
* Product containing abacavir and lamivudine in oral dose form (medicinal product form)

In other words, "MPF containing" represents a medicinal product based on description of active ingredient substances it contains and on the (generalized) intended site of use for the product.

For example,

* "Product containing amoxicillin in oral dosage form" represents the group of products that must contain some amoxicillin (be it amoxicillin sodium or amoxicillin trihydrate or amoxicillin base), but *may also* contain other active ingredients, such as clavulanic acid, in manufactured dose forms such as oral suspension, oral capsule (any type), oral tablet (any type).

#### Use case(s) supported by |Product containing x in y dose form (medicinal product form)|

The main use case for the *MPF (containing)* is for analysis, as an aggregation concept for use in research.

#### IDMP Compatibility

A concept at this level with the open world view does not correspond to any concept currently in the IDMP suite of standards.

## Naming

Use the following pattern for the FSN and PT. Align naming and case sensitivity with the FSN for the concepts that are selected as the attribute value.

For multiple ingredient drug products, active ingredients must be in alphabetical order and separated by the word “and”.

### FSN

Product containing \<Active ingredient FSN> in \<Manufactured dose form FSN> (medicinal product form)

Product containing \<Active ingredient FSN> and \<Active ingredient FSN> in \<Manufactured dose form FSN> (medicinal product form)

Product containing \<Active ingredient FSN> and \<Active ingredient FSN> and \<Active ingredient FSN> in \<Manufactured dose form FSN> (medicinal product form)

For example,

* Product containing axitinib in oral dose form (medicinal product form)
* Product containing abacavir and lamivudine in oral dose form (medicinal product form)
* Product containing abacavir and lamivudine and zidovudine in oral dose form (medicinal product form)

*Creation of MPF-containing concepts for all possible combinations of active ingredients contained in multiple ingredient products is not recommended at this time (no specific use case has been identified). For example, a product containing three active ingredients would only require creation of one MPF-containing concept. If any of the active ingredients is available as a single ingredient product, or as part of another multiple ingredient concept, then appropriate concepts would be created for those products.*

### Preferred Term

\<Active ingredient PT>-containing product in \<Manufactured dose form PT>

\<Active ingredient PT>- and \<Active ingredient PT>-containing product in \<Manufactured dose form PT>

\<Active ingredient PT>- and \<Active ingredient PT>- and \<Active ingredient PT>-containing product in \<Manufactured dose form PT>

For example,

* Axitinib-containing product in oral dose form
* Abacavir- and lamivudine-containing product in oral dose form
* Abacavir- and lamivudine- and zidovudine-containing product in oral dose form

### Synonym

Synonyms matching the FSN are not required.

## Modeling

| **Stated parent**                                                   | `763158003 \|Medicinal product (product)` |
| ------------------------------------------------------------------- | ----------------------------------------- |
| **Semantic tag**                                                    | (medicinal product form)                  |
| ***Definition status***                                             | Defined                                   |
| <p><strong>Attribute:</strong></p><p>Has active ingredient</p>      | **Range:** `<105590001`                   |
| <p><strong>Attribute:</strong></p><p>Has manufactured dose form</p> | **Range:** `<736542009`                   |

## Exemplars

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FbkjCymyW1BoW45iPxbKD%2Fimage.png?alt=media&amp;token=e2bf6ecc-5c67-44b3-8f9e-f99b3dda5dba" alt=""><figcaption><p>Stated Template View</p></figcaption></figure>

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FgpLmXlCWQPamscfL2M5k%2Fimage.png?alt=media&amp;token=140c35be-4542-4962-a1f0-a938f0ba491d" alt=""><figcaption><p><strong>Stated</strong> view for 773391004 |Product containing axitinib in oral dose form (medicinal product form)|</p></figcaption></figure>

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FLjFyWsObj7zccKiAEW6w%2Fimage.png?alt=media&amp;token=4926c367-644c-4f61-ace3-eab672b308f0" alt=""><figcaption><p><strong>Inferred</strong> view for 773391004 |Product containing axitinib in oral dose form (medicinal product form)|</p></figcaption></figure>

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FoPmK5YZY1qUuHDrAdJGN%2Fimage.png?alt=media&amp;token=87c5b739-ea73-4075-b446-0a2aea181b0f" alt=""><figcaption><p><strong>Stated</strong> view for 767783007 |Product containing codeine and paracetamol in oral dose form (medicinal product form)|</p></figcaption></figure>

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FFLiEGw27dItoMZ3odLv7%2Fimage.png?alt=media&amp;token=0dd3b0ba-1831-47d0-bd6f-e3fec00aca63" alt=""><figcaption><p><strong>Inferred</strong> view for 767783007 |Product containing codeine and paracetamol in oral dose form (medicinal product form)|</p></figcaption></figure>

<figure><img src="https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/pharmaceutical-and-biologic-product/images/174690705.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=Medicinal%20Product%20Form%20containing" 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 dynamically 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/index-1/index/medicinal-product-form-containing.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 `build a script that syncs our docs to a CMS` 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.