> 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/settings-and-customisation/custom-groups/create-a-custom-drug-group.md).

# Create a Custom drug group

Custom drug groups enable organisations to organise selected medicines into predefined group for easier case retrieval .

Custom drug groups can be used in searches, filters and analyses.

 

To create a Custom drug group:

1. Open the User menu.
2. Open **Custom groups**.
3. Locate **Drug group**.
4. Click **Create new**.
5. Enter a group **Name**.
6. Add the medicines or vaccines of interest.
7. Click Save.

The new group becomes available to all users in the organisation.

Custom drug groups can include any number of active ingredients and active ingredient variants. Trade name products cannot be included in a custom group.

#### When should I use a Custom drug group?

Custom drug groups are useful when:

* Frequently analysing the same group  of medicines
* Reviewing specific therapeutic areas. Example, medicines used in specific disease-programmes
* Supporting recurring workflows
* Monitoring medicines under additional monitoring
* Standardising searches across a team


---

# 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/settings-and-customisation/custom-groups/create-a-custom-drug-group.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.