> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/candidates-tab/reviewing-the-candidates-tab.md).
# Reviewing the Candidates tab
To select variants with a particular tag, use the Filter candidates dropdown menu in the top right corner. You can select from Most Likely, Candidate, Incidental, Carrier, Not Reviewed, or any custom tags used in your organization.
For each variant on the Candidates tab, you can explore the gene-related disease, gene symbol, main variant details, and variant tag.
When a variant is found in a gene with no known disease association, the gene-related disease cannot be displayed. Such variants appear under the Gene of Unknown Significance heading.
All the relevant [Most Likelies and Candidates](/emedgene/emedgene-analyze-manual/reviewing_a_case/candidates-tab/most_likely_candidates_and_candidates.md) fitting a сompound heterozygous mode of inheritance are presented together. This refers to both confirmed and assumed compound heterozygosity (cases with at least one parent and singleton cases, respectively).
If you want to inspect the complete variant information, click on the variant bar to continue to the [Evidence page](/emedgene/emedgene-analyze-manual/reviewing_a_case/evidence_page.md). You can visualize evidence in text or graphical format (Click on the interactive text in the top left corner: Show evidence as text or Show evidence graph to toggle between the two).
---
# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/candidates-tab/reviewing-the-candidates-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.
.png?alt=media)