> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigilyze/searching-and-filtering/search-by-active-ingredient-variant.md).

# Search by Active ingredient variant

Active ingredient variants allow you to distinguish between different variants of the same active ingredient.

Active ingredient variations represent different forms or alterations of an active substance, for instance:

* Different salts or esters of a conventional medicinal product
* Different levels of vaccine specificity (such as Polio vaccine live oral type 1 and inactivated Polio vaccine)
* Different plant parts used in herbal medicinal products
* Different insulin derivatives (such as isophane and crystalline insulins).

**To search by active ingredient variant:**

1. Click **Filter** → **Drug** → **ATC view**.
2. Search for the required active ingredient variant, for example omeprazole sodium.
3. Select the variant from the list.
4. Click **Save**.

The search results will only include reports matching the selected variant.


---

# 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://support.who-umc.org/vigilyze/searching-and-filtering/search-by-active-ingredient-variant.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.