> 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/quantitative-view/filter-for-important-medical-events.md).

# Filter for important medical events

The Drug-Event Combinations table can be configured to show specific groups of events.

For example, the table can be limited to Important Medical Events as defined by the EMA. It can also be limited to specific MedDRA groupings, such as SOCs, HLGTs, HLTs, or to a Custom reaction group.

#### To display only Important Medical Events:

1. Select **Filter** → **Reaction**.
2. Select **Important Medical Event (EMA)**.

The table updates to include only events classified as Important Medical Events. Read more in the EMA document “[*Inclusion/exclusion criteria for the “Important Medical Events” list*](https://www.ema.europa.eu/en/documents/other/inclusion-exclusion-criteria-important-medical-events-ime-list_en.pdf)*"*

#### Selecting specific types of events with MedDRA

The MedDRA hierarchy can be used to restrict results to a specific group of events.

1\.       Select **Filter** → **Reaction** → **SOC view**.

2\.       Select a MedDRA SOC or another MedDRA level.

#### Custom reaction groups

Each organisation can define its own list of event terms using custom groups.
\
Selecting a Custom reaction group limits the table to events included in that group.


---

# 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/quantitative-view/filter-for-important-medical-events.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.