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

# The Data Page

The Data Page is where you find the sample to interpret. It is the entry point to the Variant Interpreter, reached by selecting an instrument, and lists every sample for that instrument.

## Selecting an instrument

The Data Page is scoped to an instrument. Choose the instrument whose samples you want to work with; the sample list then loads for that instrument.

## The sample list

Each row is a sample. The list shows:

* **Sample name**: the identifier you use to locate the proband or a family member.
* **Movies**: the number of PacBio CCS files available for the sample.
* **Date Added**: when the sample was added to Workbench.
* **Family**: the family the sample is connected to (for trio / family analysis).
* **Sex**: biological sex of the sample, if known.
* **HPO terms**: how many phenotype terms are logged for the sample.
* **Run Date**: the date the tertiary analysis workflow was run.
* **Workflows**: which workflows have been run against the sample, and whether each **succeeded or failed**.
* **Status**: the status of the most recent workflow run.

## How to use it

1. Select the instrument.
2. Find your sample by name and check that a workflow has **succeeded**.
3. Open the sample to reach its details page, then open the succeeded run for review. See [Opening a sample](/products/workbench/variant-interpreter/getting-started/opening-a-sample.md).

{% hint style="info" %}
The sample drawer, available throughout the interpreter, carries the sample's details, pedigree, and workflow history with you, so you don't have to return to the Data Page to check provenance.
{% 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 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-data-page.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.