> 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/variant-visualization.md).

# Variant visualization

Variant visualization in **Emedgene** lets you review alignment, annotation, and population data in genomic context to support variant validation and interpretation.

Open the built-in viewer from the [**Visualization tab**](/emedgene/emedgene-analyze-manual/variant_page/visualization_section.md) on the **Variant page** or from the [**Analysis tools tab**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+.md) for RUO cases when **New mode** is enabled (v100.39 and later).

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Variant visualization tool</strong></td><td>IGV-based genome viewer for inspecting variants, tracks, and supporting evidence during case review.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool.md">Learn more</a></td></tr><tr><td><strong>Variant visualization setup</strong></td><td>Configure visualization for VCF cases and connect <strong>Emedgene</strong> to desktop IGV.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/variant-visualization/variant_visualization_setup.md">Learn more</a></td></tr></tbody></table>


---

# 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/variant-visualization.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.