> 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/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns.md).

# Appendix A: Product Patterns

To correctly interpret "*one countable instance of a whole of medicinal product* ", it is important that this is seen in the context of the overall description of a medicinal product, which is always presented from the manufacturer as a "packaged medicinal product". Note that description of packaged medicinal products is outside the scope of the international release but may be included within a national extension. The IDMP Medicinal Product model describes this, showing how the Manufactured Item is related to the Packaged Medicinal Product via the Package Item (Container). This is a recursive class that represents both the package as supplied by the manufacturer (and, for example, labelled with the GTIN, the batch number and the expiry), and through a recursive relationship, with any sub-packages inside the outer pack.

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FDRmCxT8nlA4EVz3d4f5U%2FScreenshot%202025-09-26%20at%202.47.45%E2%80%AFPM.png?alt=media&amp;token=f8c1fa75-b4ad-4df3-ac4f-27d3e9e3720d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://confluence.ihtsdotools.org/download/attachments/123904118/App%20A.png?version=1&#x26;modificationDate=1615996337000&#x26;api=v2" alt=""><figcaption></figcaption></figure>

By describing the various standard patterns of products with their basic dose forms and intimate containers, consistent representation of strength based on unit of presentation can be maintained.

{% hint style="info" %}
In all the patterns described below, pack size is mentioned to show how information is sourced from "what is". Description of pack size is out of scope for the international release, although it is in scope for the national extension model, as some nations may require medicinal products that include description of pack size for their national terminology. Therefore, it is useful to have it shown here for informational purposes only.
{% endhint %}

* [Discrete manufactured dose form; similar unit of presentation](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/discrete-manufactured-dose-form-similar-unit-of-presentation.md)
* [Continuous presentation: Metered dose unit of presentation](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-metered-dose-unit-of-presentation.md)
* [Continuous presentation: Oral liquids designed for administration by "metered" medicine spoon](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-oral-liquids-designed-for-administration-by-metered-medicine-spoon.md)
* [Continuous presentation: bounded by unit of presentation; solid dose forms](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-bounded-by-unit-of-presentation-solid-dose-forms.md)
* [Continuous presentation: bounded by container; liquid dose forms](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-bounded-by-container-liquid-dose-forms.md)
* [Continuous presentation: bounded by container; liquid/semi-solid dose forms; concentration strength required](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-bounded-by-container-liquidsemi-solid-dose-forms-concentration-strength-requ.md)
* [Continuous presentation: unbounded by container](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns/continuous-presentation-unbounded-by-container.md)

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Appendix%20A%3A%20Product%20Patterns" 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/pharmaceutical-and-biologic-product-and-dose-form-attributes-summary/appendix-a-product-patterns.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.