> 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/disproportionality-analysis/disproportionality-tab-overview.md).

# “Disproportionality” tab overview

The “Disproportionality” tab provides statistical information about the reporting frequency of a selected drug-reaction combination.

The information shown in this tab is based on the current drug and reaction search and helps identify combinations that are reported more frequently than expected within the selected dataset.

The exact disproportionality measure displayed depends on the settings selected for your account.

The tab can include:

* Disproportionality values
* Report counts
* Expected counts
* Stratified analyses
* Trend visualisations

The information is presented in both tabular and graphical format.

#### How can I use the disproportionality view?

The “Disproportionality” tab can help you:

* Understand how frequently a combination is reported relative to the database background
* Compare reporting across patient groups
* Explore reporting trends over time
* Identify combinations that may warrant further review

Disproportionality results should be considered alongside qualitative review of the underlying reports.


---

# 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/disproportionality-analysis/disproportionality-tab-overview.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.