> 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/use-graphs-to-refine-a-search.md).
# Use graphs to refine a search
Most graphs in the “Overview” tab are interactive.
Selecting an item in a graph automatically applies a corresponding filter and updates the results.
For example:
* Selecting an age group further narrows the results by age.
* Selecting a country filters the results to country-specific data.
* Selecting a reaction further narrows the results based on the MedDRA hierarchy.
This allows you to move from a broad dataset to a more focused subset without opening the Filter menu. To return to the previous search, simply click the **Undo** icon in the top-right corner of the tab.
The Undo icon reverses the most recent search action performed in the graph.
#### Table view and Chart view
Many overview panels can be displayed either as charts or tables.
* Charts provide a visual overview of the data.
* Tables make it easier to review exact values and compare categories.
---
# 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/use-graphs-to-refine-a-search.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.
