> 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/getting-started/the-qualitative-view.md).
# The Qualitative view
The Qualitative view is the main workspace for reviewing and assessing individual reports and case series.
It allows you to:
* Search for drugs and reactions
* Apply filters to refine your results
* Export data
* Review summary information
* Examine individual reports
* Perform disproportionality analyses
* Create and manage investigations
### Main areas of the Qualitative view
#### **Search bar**
The search bar is located at the top of the page.
You can use it to search for:
* Drugs
* Reactions
* Patient characteristics such as age and sex
#### Filter menu
The Filter menu allows you to refine search results.
\
Available filters include:
* Drug filters
* Reaction filters
* Patient filters
* Administrative filters
Filters remain active when you move between tabs.
#### Tabs
Information is organised into tabs that present the current dataset in different ways.
**Overview**
Provides graphical summaries of the current search results.
**Cases**
Displays individual reports and line listings.
**Disproportionality**
Displays disproportionality measures for selected drug-reaction combinations.
**Related investigations**
Displays investigations related to the current search and helps identify whether a topic has already been assessed.
**Working across tabs**
The current search and filters remain active when moving between tabs. This allows the same dataset to be reviewed from different perspectives without repeating the search.
---
# 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/getting-started/the-qualitative-view.md?ask=&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.
