> 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-and-quantitative-view.md).

# Disproportionality tab and  Quantitative view

#### How is the “Disproportionality” tab different from the Quantitative view?

Both the “Disproportionality” tab and the Quantitative view contain disproportionality information, but they are designed for different purposes. Below is a comparison betwee the two.

|                       Quantitative View                       |                              Disproportionality tab                             |
| :-----------------------------------------------------------: | :-----------------------------------------------------------------------------: |
|    Analysis begins with a drug-reaction combinations table.   |                     Analysis begins with an existing search.                    |
|    Focuses on large numbers of drug-reaction combinations.    | Focuses on a specific drug-reaction combination that has already been selected. |
|           Used to identify combinations of interest.          |            Used to explore a selected combination in greater detail.            |
| Supports sorting, prioritisation, and quantitative filtering. |       Supports trend review, subgroup comparison, and detailed assessment.      |

#### A common workflow is:

1. Use the Quantitative view to identify a drug-reaction combination of interest.
2. Move to the Qualitative view.
3. Review the associated reports.
4. Use the “Disproportionality” tab to explore the combination in greater detail.
5. Create an investigation if further assessment is required.

The two views support different stages of the assessment process.


---

# 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-and-quantitative-view.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.