> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/getting-started/the-summary-tab.md).

# The Summary tab & priority findings

When you open a sample for review, the Variant Interpreter lands on the **Summary tab**. This is the orientation surface for the sample's results: it presents the **priority findings**, the variants the system has identified as most likely to be pathogenic, so you can start interpreting immediately instead of working through every tab.

## Priority findings

Priority findings are drawn from across the variant classes (for example a structural variant together with tandem-repeat variants) and gathered into one list. From a priority finding you can:

1. Open the variant to see its details.
2. Explore the affected **gene**.
3. Open the variant in the [**genome browser (IGV)**](/products/workbench/variant-interpreter/reviewing-variants/genome-browser.md) tab to inspect the underlying reads.
4. [**Classify**](/products/workbench/variant-interpreter/classifying-variants.md) the variant so it becomes eligible for the report.

{% hint style="info" %}
Note, that a navigation control within the details panel lets you step through the priority findings in turn, so you can triage the whole list without leaving the Summary tab.
{% endhint %}

## Where to go next

The Summary tab is the fastest path through the strongest candidates. To review a variant class in full, switch to its tab, see [Reviewing variants](/products/workbench/variant-interpreter/reviewing-variants.md). The [sample drawer](/products/workbench/variant-interpreter/getting-started/the-data-page.md) is available here and on every other screen for sample context.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/getting-started/the-summary-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.