> 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.md).

# Getting Started

This section covers what you need before you start, how to log in, how to open a case, and how to read the Data Page.

## Prerequisites

Before interpreting a case, the following must already be in place, typically handled by your lab's administrator or bioinformatics team:

* A completed analysis run for the sample or family, produced by a supported long-read WGS workflow.
* Access to the workspace that contains the sample, with a **Contributor** or **Admin** role. See [Workspaces & roles](/products/workbench/variant-interpreter/workspaces-and-roles.md).
* For family-based interpretation, a pedigree describing the relationships between samples. See [Family Based Analysis with Pedigree Information](/products/workbench/instruments/adding-pedigrees.md).

{% hint style="warning" %}
If a sample isn't appearing, check that you've selected the right instrument and workspace, and that the upstream run has finished. The Data Page shows each sample's workflow status.
{% endhint %}

## The interpretation session at a glance

A typical case review follows the same path. The target is a focused, end-to-end session, from opening the case through submitting the report, measured from login to report submission.

1. [Log into Workbench](/products/workbench/getting-started/log-into-workbench.md) and select your workspace.
2. On the [Data Page](/products/workbench/variant-interpreter/getting-started/the-data-page.md), select an instrument, find your sample, and open its succeeded run with **Review analysis**.
3. Orient on the [Summary tab](/products/workbench/variant-interpreter/getting-started/the-summary-tab.md) and triage the priority findings.
4. Work through the remaining variant tabs, capturing evidence as you go.
5. [Apply filters](/products/workbench/variant-interpreter/filtering-and-prioritization.md) where you need to narrow a list.
6. [Generate and submit the report](/products/workbench/variant-interpreter/generating-a-report.md).


---

# 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.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.