> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/summary-dashboard.md).

# Summary dashboard

<div data-with-frame="true"><figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-df20becf556c2cd7b944b1a4a71c6e00d564ac77%2Fimage%20(211).png?alt=media" alt=""><figcaption><p>The <strong>Summary dashboard</strong> of the <strong>Lab tab.</strong></p></figcaption></figure></div>

The **Summary dashboard** provides a quick overview of key quality indicators at the case and sample levels. Each card summarizes its corresponding section of the **Lab tab**.

* **Case quality** card displays the overall case quality status. See [Case quality section](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/case-quality-section.md).
* **Sample quality** card displays the overall sample quality status. See [Sample quality section](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/sample-quality-section.md).
* **Evaluation kit** card specifies the QC BED kit used to evaluate coverage depth and breadth. If no kit is specified when analysis launches, NCBI RefSeqGene is used as the default reference. See [Sequencing lab information section](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/sequencing-lab-information-section.md).
* **Custom gene coverage** card indicates whether coverage of genes in the selected panel meets the expected threshold defined by the QC BED. Shown only in cases with a gene list applied. See [Genes coverage section](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/genes-coverage-section.md).
* **Pedigree** card displays relationship-validation results and confirms whether the submitted pedigree matches the genetic data. Shown only in family cases. See [Pedigree section](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/pedigree-section.md).

If the **Case quality**, **Sample quality**, **Custom gene coverage**, or **Pedigree** card reports a problem, the [**combined quality status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/combined-quality-status.md) next to the **Lab tab** label shows a warning.

{% hint style="info" %}
In v100.41 and later, the pedigree status is displayed only for family cases where the [joined VCF file](#user-content-fn-1)[^1] contains at least 10000 variants.

When the variant count is below this threshold, there are too few variants to validate relationships reliably, so relationship validation is not performed.
{% endhint %}

[^1]: A Variant Call Format file that merges the proband's variants with family members' variants.


---

# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/summary-dashboard.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.
