> 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/sample-quality-section/dragen-qc-report/prerequisites-for-accessing-the-dragen-qc-report.md).

# Requirements by case type

This page explains the requirements for viewing the DRAGEN QC report for each case type.

## NGS FASTQ cases

Run a FASTQ case in Emedgene.

**Result:** Because DRAGEN analysis is integrated into Emedgene secondary analysis pipeline, QC reports are automatically generated in the system.

## NGS VCF cases

**Prerequisite:** [Batch case upload via UI or CLI](/emedgene/emedgene-analyze-manual/launching-analysis/creating_multiple_cases.md) or [API-based case creation](/emedgene/integrations/api-beginner-guide.md)

{% stepper %}
{% step %}
Run DRAGEN analysis externally. This approach is referred to as "Bring your own DRAGEN (BYOD)".
{% endstep %}

{% step %}
Prepare the DRAGEN QC data. Use one of these options:

**DRAGEN report HTML file (v100.40.0+):** Download the DRAGEN report as a `.report.html` file per sample.

or

**DRAGEN metrics TAR file:** Download DRAGEN QC metrics files and prepare a TAR archive as described [here](/emedgene/emedgene-analyze-manual/reviewing_a_case/lab_tab/sample-quality-section/dragen-qc-report/prerequisites-for-accessing-the-dragen-qc-report/how-to-i-prepare-metrics-files-generated-by-dragen-to-be-used-as-input-for-emedgene.md).
{% endstep %}

{% step %}
Upload the HTML file or TAR archive together with the sample VCF file.
{% endstep %}

{% step %}
Run the case.
{% endstep %}
{% endstepper %}

**Result:**

* **If you uploaded an HTML file:** The system directly visualizes the uploaded HTML file instead of generating the report from metrics files.
* **If you uploaded a TAR file:** The system generates an interactive HTML report from metrics files.

## Array **VCF cases**

Array cases start from VCF input files.

**Prerequisites:**

* [DRAGEN Array v1.3.0](https://help.dragenarray.illumina.com/reference/release-notes/dragen-array-v1.3.0-release-notes) and later
* Emedgene v100.39.0 and later
* [Batch case upload via UI or CLI](/emedgene/emedgene-analyze-manual/launching-analysis/creating_multiple_cases.md) or [API-based case creation](/emedgene/integrations/api-beginner-guide.md)

{% stepper %}
{% step %}
Run DRAGEN analysis externally. This approach is referred to as "Bring your own DRAGEN (BYOD)".
{% endstep %}

{% step %}
Prepare the DRAGEN QC data. Use one of these options:

**DRAGEN report HTML file** (v100.40.0+)**:** Download DRAGEN report as a `.report.html` file per sample.

or

**DRAGEN metrics files:** Download the `.annotated_cyto.json` DRAGEN QC metrics file, the sample VCF file, and the `.gt_sample_summary.json` file.
{% endstep %}

{% step %}
Upload the HTML file or metrics files together with the sample VCF file.
{% endstep %}

{% step %}
Run the case.
{% endstep %}
{% endstepper %}

**Result:**

* **If you uploaded an HTML file:** The system directly visualizes the uploaded HTML file instead of generating the report from metrics files.
* **If you uploaded metrics files:** The system generates an interactive HTML report from metrics files.


---

# 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/sample-quality-section/dragen-qc-report/prerequisites-for-accessing-the-dragen-qc-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.