> 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/opening-a-sample.md).

# Opening a sample

The Variant Interpreter is organized around **samples**. You reach a sample's variants through the Data Page, then open the analysis you want to review.

## The path to the interpreter

1. To open the **Variant Interpreter**, navigate to the **Data Page** from the left hand navigation.
2. Select the **instrument** whose samples you want to review. The Data Page then loads the sample list for that instrument. See [The Data Page](/products/workbench/variant-interpreter/getting-started/the-data-page.md).
3. Locate your sample, for example the proband, using the sample name, and select it to open its **sample details** page.
4. On the sample details page, find the workflow run you want to interpret. NOTE: Only a run that **succeeded** can be opened for review.
5. Click the succeeded run, then click **Review analysis** to open the sample in the Variant Interpreter where you will land on the [Summary tab](/products/workbench/variant-interpreter/getting-started/the-summary-tab.md).

{% hint style="info" %}
A sample can have more than one workflow run. Confirm you're opening the run you intend to interpret, the workflow and caller versions that produced it are recorded in the sample drawer, and the report's Methods section records the workflow and run ID. See [Pipeline & caller versions](/products/workbench/variant-interpreter/pipeline-and-caller-versions.md).
{% endhint %}

{% hint style="warning" %}
If a sample shows no succeeded run, there is nothing to interpret yet, the upstream analysis either hasn't finished or failed. The Data Page shows each sample's workflow status so you can tell at a glance.
{% 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/variant-interpreter/getting-started/opening-a-sample.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.