> 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/generating-a-report/the-printed-report.md).

# The printed report

The released report is an A4 document assembled from the report's template, your organization's [report branding](/products/workbench/variant-interpreter/generating-a-report/report-branding.md) and the case data. **Preview** on the Report tab shows the same document at any phase; the PDF and HTML downloads are the version frozen at release.

## Layout

The report prints in this order:

1. **Letterhead**: your logo and organization name, the address, and the report title. Beneath them, the **Case ID**, **Analysis Type**, **Report Date**, **CLIA ID**, and **Accreditation**. A missing value prints as a dash.
2. **The template's sections**, in the template's order, each under a ruled heading. For the standard template:
   * **Patient, Specimen & Provider Information**: a **Patient** column (proband ID, sex, affected status) and, where recorded, a **Family** column (family ID, paternal ID, maternal ID).
   * **Clinical Phenotypes**: the sample's HPO terms, each with its ID and label.
   * **Findings tables**: one table per findings section, with the columns **Gene(s)**, **Variant**, **Type**, **Classification**, and **Interpretation**. Rows classified as Pathogenic (not Likely pathogenic) are highlighted.
   * **Clinical Interpretation**, **Recommendations**, **Methods** (including the workflow, run ID, and number of variants reported), **Limitations**, **References**, and any statements your lab added.
3. **Report Sign-Off**: the signer's role and name, the date signed, any amendment reason, the disclaimer, and the version (**Version 1**, or **Amendment 2** and later).

Every page has a footer with "Confidential", your footer text and, if enabled, the page number. From page 2 onward, the report title and case ID repeat at the top of the page.

Sections you've turned off in the template aren't printed. The Clinical Phenotypes section is left out when the case has no phenotype terms, and a findings section you added is left out when nothing is filed under it.

## Download formats

| Format   | Use it for                                                                                             |
| -------- | ------------------------------------------------------------------------------------------------------ |
| **PDF**  | The signed report to share or file.                                                                    |
| **HTML** | Viewing the report in a browser or embedding it in another system.                                     |
| **JSON** | Machine-readable report content (sections, findings, and branding) for integration with other systems. |

All three are produced at release from the same frozen document, so their content matches.

{% hint style="info" %}
The report's **Methods** section records the workflow and run ID of the analysis that produced it. The reference genome and caller versions aren't printed on the report; find them in the sample drawer. See [Pipeline & caller versions](/products/workbench/variant-interpreter/pipeline-and-caller-versions.md).
{% 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/generating-a-report/the-printed-report.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.