> 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/dragen-somatic-for-idt-custom-panels/readme.md).

# Introduction

Welcome to the user documentation for **DRAGEN somatic for IDT custom panels**, a cloud-based bioinformatics solution that enables verified analysis of solid sample somatic sequencing data generated with **IDT xGen cfDNA and FFPE library preparation kits** using IDT custom panels on any Illumina sequencer.

## What You Will Learn

* How to set up prerequisites and connect BSSH to BioInsight Platform Core (Platform Core)
* How to generate a systematic noise baseline file (Stage 1)
* How to launch variant calling from Run Planner, BSSH, or Platform Core (Stage 2)
* How to locate and review pipeline outputs
* How to evaluate quality control metrics and connect to Illumina Connected Insights
* How to troubleshoot common issues

## Software Version

This documentation covers **DRAGEN somatic for IDT custom panels Software v4.5.4**.

{% hint style="info" %}
**For Research Use Only. Not for use in diagnostic procedures.**
{% 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://help.connected.illumina.com/dragen-somatic-for-idt-custom-panels/readme.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.