> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/summary-dashboard.md).

# Summary dashboard

The **Summary dashboard** provides a quick overview of key quality indicators at the case and sample levels.

## Included metrics

* [**Case quality**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/case-quality-section.md) — displays the overall case quality status.
* [**Sample quality**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/sample-quality-section.md) — reflects the sample quality status.
* **Evaluation kit** — 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.
* **Custom gene coverage** — indicates whether coverage of genes in the selected panel meets the expected threshold defined by the QC BED.
* [**Pedigree status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/pedigree-section.md) — displays relationship-validation results and confirms whether the submitted pedigree matches the genetic data.

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