> 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.md).
# Medicinal Product Form (MPF)
Medicinal Product Form - An abstract representation of a medicinal product described by its active ingredient substances and a grouping dose form concept (based on the intended site of administration for the dose form group) but without reference to any product strength.
The grouping dose form concepts are the immediate children of `736542009 |Pharmaceutical dose form (dose form)|` and are described in detail in the section [Pharmaceutical Dose Form Grouper Based on Intended Site](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/index/index/pharmaceutical-dose-form-grouper-based-on-intended-site.md). These grouper concepts gather all the formulations (solid, semi-solid, liquid, or gaseous manufactured dose forms) that have the same intended site of administration. The intended site of administration of a dose form concept is a description of the general body site (i.e., not exactly anatomically explicit - no laterality etc.) where the dose form will be administered.
For example,
* Products formulated with a dose form of *eye drops* are required to meet various pharmacopoeial standards of sterility, particulate contamination, and pH, as they are intended to be administered to an *ocular* site.
For further information, see section 5.3.2.7 of ISO 11239:2012 *Health informatics - Identification of medicinal products — Data elements and structures for the unique identification and exchange of regulated information on pharmaceutical dose forms, units of presentation, routes of administration and packaging*.
## Subpages
{% content-ref url="/pages/FsSLgGSI9dD0hfLj8qfv" %}
[Medicinal Product Form containing only](/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-only.md)
{% endcontent-ref %}
{% content-ref url="/pages/iTh7wW1Ypel2VvMTgCsZ" %}
[Medicinal Product Form containing](/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)
{% endcontent-ref %}
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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.