> 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/analysis-tools-tab-beta-v100.39.0+.md).

# Analysis tools tab

The **Analysis tools tab** is the primary workspace for reviewing and interpreting variants within a case.

## The Analysis tools tab includes:

* [**Variant table**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/variant_table.md): Displays variants with key annotations, quality metrics, and interpretation details in a table.
* [**Filtering panel**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel.md): Allows you to narrow results using filters and presets.
* [**Variant visualization tool**](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool.md) (v100.39.0+): Enables visual inspection of a variant's genomic context in a genome viewer built into the **Analysis tools tab**. The **Variant visualization tool** is available for RUO[^1] cases when the **New** [**viewing mode**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/viewing-modes.md) of the **Analysis tools tab** is enabled.

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Variant table</strong></td><td>Explanation of <strong>Variant table</strong> functionality, including column definitions, row formatting, customization, bulk actions, and data export.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/variant_table.md">Learn more</a></td></tr><tr><td><strong>Filtering panel</strong></td><td>Overview of the filtering infrastructure used during case review, including filters, presets, preset groups, and variant search.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel.md">Learn more</a></td></tr><tr><td><strong>Viewing modes (v100.39.0+)</strong></td><td>Switch between <strong>New</strong> and <strong>Legacy</strong> viewing modes for <strong>Analysis tools tab</strong>. <strong>New mode</strong> includes an integrated variant visualization window above the variant table.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/viewing-modes.md">Learn more</a></td></tr></tbody></table>

[^1]: Research use only


---

# 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/analysis-tools-tab-beta-v100.39.0+.md?ask=<question>&goal=<user_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.