> 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/cases-tab-overview.md).
# “Cases” tab overview
The “Cases” tab provides access to individual reports that match the current search criteria.
Each row in the line listing represents a single report.
The “Cases” tab is typically used when:
* Reviewing individual reports
* Exploring a case series
* Assessing report quality
* Preparing exports
* Investigating specific reports
The information shown depends on the columns currently displayed.
\
Users with narrative access can view the narrative by clicking the document icon.
\
You can sort the list in ascending or descending order by any column by clicking the arrow icon in each heading.
#### Sort and review reports
The “Cases” tab supports sorting of information.
To sort the reports:
1. Locate the column of interest.
2. Click the column heading.
3. Click again to reverse the sort order.
{% hint style="info" %}
Sorting reports by criteria such as completeness score, report date, country, or patient age can help prioritise which reports to review first.
{% 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/cases-tab-overview.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.
