> 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/understand-the-results/what-information-is-shown-in-the-overview-tab.md).
# What information is shown in the “Overview” tab?
The “Overview” tab provides a high-level summary of the current search results. It helps you understand the characteristics of the reports responsive to your search before moving on to more detailed review.
Information is presented as graphs and tables and updates automatically when search criteria or filters are changed.
The "Overview" tab includes graphs and tables that summarise the results. It provides patient and report characteristics, including the number of medicines and reactions recorded in the reports, as well as a timeline showing when the reports occurred or were reported to the database.
Each visualisation presents a different perspective of the current dataset.
{% hint style="info" %}
The “Overview” tab is often used as the starting point for exploring a case series and identifying patterns before reviewing individual reports.
{% endhint %}
---
# 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/understand-the-results/what-information-is-shown-in-the-overview-tab.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.
