> 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/combined-quality-status.md).

# Combined quality status

The combined quality status summarizes the main quality results of a case in one icon. It appears in two places:

* Next to the **Lab** **tab** label when you open a case
* In the **Quality** column of the [**Cases table**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/cases_table.md#cases-table-fields)

The combined quality status is based on:

* [**Overall case quality status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/case-quality-section.md#overall-case-quality-status)
* [**Overall sample quality status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/sample-quality-section.md#overall-sample-quality-status) of every sample in the case
* [**Custom gene coverage status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/genes-coverage-section.md#overall-coverage-status), in cases with a gene list applied
* [**Overall pedigree status**](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/pedigree-section.md#overall-pedigree-status), in family cases

Statuses that do not apply to the case are not counted, for example, overall pedigree status in a single sample case.

## Combined quality status values

<table><thead><tr><th width="117">Status</th><th width="361">How it is defined</th><th>Lab tab warning</th><th>Quality column</th></tr></thead><tbody><tr><td><strong>Pass</strong></td><td>Every applicable status is <strong>Pass</strong>.</td><td><p><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2FJqtpOHtXPTs4ZBoxXdD7%2Fimage.png?alt=media&#x26;token=e9763450-4315-467d-a693-c87a7a365eeb" alt="" data-size="original"></p><p>(no icon)</p></td><td><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2F9Snnlxkvy2A3qtlIbJTM%2Fimage.png?alt=media&#x26;token=52fa3ada-f944-4c9e-a96b-286eb5eaec12" alt="" data-size="line"></td></tr><tr><td><strong>Pass with exceptions (v100.41+)</strong></td><td><p><strong>v100.41 and later</strong>: The overall case quality status is <strong>Pass with exceptions</strong>, and every other applicable status is <strong>Pass</strong>.</p><hr><p><strong>v100.40 and earlier</strong>: Not available. A failed case quality check (for example, sex validation) sets the overall case quality status to <strong>Fail</strong>, so the combined quality status is also <strong>Fail</strong>.</p></td><td><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2FdaBVERjBxSzAEyuej5zY%2Fimage.png?alt=media&#x26;token=c0213eef-c52c-45a0-9fb4-8ec6822bd39e" alt="" data-size="line"></td><td><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2F04vFlHU1tZkF727EupxS%2Fimage.png?alt=media&#x26;token=e6131f33-a382-4faf-8004-c65960688320" alt="" data-size="line"></td></tr><tr><td><strong>Fail</strong></td><td><p><strong>v100.41 and later</strong>: At least one applicable status, other than the overall case quality status, is <strong>Fail</strong>.</p><p>A failed case quality check alone results in <strong>Pass with exceptions</strong>, not <strong>Fail</strong>.</p><hr><p><strong>v100.40 and earlier</strong>: At least one applicable status, including the overall case quality status, is <strong>Fail</strong>.</p></td><td><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2FdKpmAXA0cOL65ligi1Eo%2Fimage.png?alt=media&#x26;token=d0928c51-5192-4efc-a5d8-1a9d47a01d70" alt="" data-size="line"></td><td><img src="https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2FIHqQsyMFGWOmXuiZ9rWO%2Fimage.png?alt=media&#x26;token=9a89a01b-d5cf-49e8-ac36-ad56848fe2a3" alt="" data-size="line"></td></tr><tr><td><strong>No data</strong></td><td>The case has the <strong>Issue reported</strong> status.</td><td>N/A. Cases with this status cannot be opened.</td><td><i class="fa-minus">:minus:</i><br>(dash)</td></tr></tbody></table>


---

# 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/combined-quality-status.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.