> 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/samples-runs-and-analyses.md).

# Samples, runs & analyses

This page defines the objects you work with in the Variant Interpreter and how they relate. Read it once before your first session — the rest of the guide assumes these terms.

## The hierarchy at a glance

```
Workspace
  └─ Instrument                 (the storage account where data resides: AWS / Azure / GCP)
       └─ Sample                (one individual's sequenced data)
            └─ Workflow run      (a secondary/tertiary analysis of that sample)
                 └─ Analysis     (what you open in the interpreter: variants + report)
```

* A **workspace** is the tenant you select after logging in. It scopes everything below it — you only see the storage, samples, and analyses that belong to the workspace you're in. See [Workspaces & roles](/products/workbench/variant-interpreter/workspaces-and-roles.md).
* An **instrument** is the cloud storage account (AWS S3, Azure Blob, or GCP) a workspace is connected to, surfaced on the Data Page. You select an instrument to list its samples. Connecting storage is normally an administrator task.
* A **sample** is one individual's sequenced data — the unit you open to interpret. A sample carries metadata used throughout interpretation: biological sex, phenotype (HPO) terms, and family relationships.
* A **workflow run** is a single execution of an analysis pipeline against a sample. A sample can have more than one run (for example, a re-analysis on a newer pipeline).
* An **analysis** is what opens in the Variant Interpreter when you choose **Review analysis** on a *succeeded* run. It holds that run's variant sets and its report.

## Opening a sample for interpretation

You always enter interpretation through a **succeeded** workflow run:

1. On the **Data Page**, select an instrument and find your sample.
2. Open the sample to reach its details, then open the succeeded run.
3. Choose **Review analysis** to open the analysis in the interpreter.

Only succeeded runs can be opened. If a run failed or is still in progress, the sample's Analysis section shows its status and, for failures, which step failed. See [Opening a sample](/products/workbench/variant-interpreter/getting-started/opening-a-sample.md) for the step-by-step path.

## The interpretation workspace

Once open, an analysis has three areas, reachable from the tabs at the top:

| Tab              | What it's for                                                                                                                                                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Summary**      | Orientation and QC for the analysis, plus the priority findings to triage first.                                                                                               |
| **Variant sets** | The filterable variant tables — one per set — where you review and classify variants. See [Reviewing variants](/products/workbench/variant-interpreter/reviewing-variants.md). |
| **Report**       | The single clinical report for this analysis. See [Generating a report](/products/workbench/variant-interpreter/generating-a-report.md).                                       |

A **sample drawer** is available on every screen. It slides out to show the sample's details, its pedigree (for family-based analyses), and its workflow history, so you can check provenance without leaving the variant you're looking at.

## Interpretation status

Each analysis tracks an outcome so your team can track what's still open:

* **Active** — interpretation is in progress.
* **Solved** — a causative finding was reached.
* **Unsolved** — interpretation completed without a causative finding.

## Provenance

Every analysis records the **reference genome**, the **pipeline version**, and the **caller versions** used to produce its variants. These are shown in the interpreter and printed on the released report so any finding can be traced back to exactly how it was produced. See [Pipeline & caller versions](/products/workbench/variant-interpreter/pipeline-and-caller-versions.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 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/samples-runs-and-analyses.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.