> 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.md).

# Search by Active ingredient

Active ingredients are used to group reports across products that contain the same active pharmaceutical substance, regardless of product name or manufacturer.

For example, a search for ibuprofen includes reports associated with products that contain ibuprofen as the only active ingredient.

To search by active ingredient:

1. Click in the search bar.
2. Start typing the name of the active ingredient.
3. Select the active ingredient from the list of suggestions.
4. Press **Enter** or click to select.

**When should I search by active ingredient?**

Searching by active ingredient is a useful starting point when reviewing reports related to a specific active ingredient, regardless of product name.


---

# 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.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.