> 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/getting-started/reviewing-analysis.md).

# Reviewing Analysis

Once a workflow has produced results, a clinical geneticist reviews and interprets them in the **Variant Interpreter**. This is the tertiary-analysis step that follows [locating your outputs](/products/workbench/getting-started/locating-workflow-outputs.md).

## Opening the Variant Interpreter

To review a completed analysis:

1. From the **Data Page**, select the instrument and locate your sample.
2. Open the sample to reach its details page.
3. Select the workflow run you want to interpret. Only a run that **succeeded** can be reviewed.
4. Click **Review analysis** to open the sample in the Variant Interpreter.

You land on the **Summary tab**, which surfaces the priority findings for the case.

## What you can do in the Variant Interpreter

* Triage the **priority findings** and step through the strongest candidates.
* Review each variant class on its own tab: small variants, structural variants, copy number, tandem repeats, and paralogs.
* Classify variants and add them to the report.
* Submit the report for **Admin** review and sign-off.

For the full walkthrough, see the [Variant Interpreter](/products/workbench/variant-interpreter.md) documentation.

{% hint style="info" %}
The Variant Interpreter is the interpretation surface for long-read tertiary analysis. It presents the output of a completed workflow rather than calling variants itself.
{% 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://docs.omics.ai/products/workbench/getting-started/reviewing-analysis.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.