> 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/dragen-clinical-research-apps/readme/common.md).

# Common Product Features

## Run Planning

<table><thead><tr><th width="162.6796875">Application</th><th width="192.80859375">Supported in BSSH Run Planner</th><th>Note</th></tr></thead><tbody><tr><td><a href="/dragen-clinical-research-apps/readme/dragen-heme-wgs-to-pipeline.md">Heme WGS TO</a></td><td>Yes</td><td>Mixed flow cell, auto-launch</td></tr><tr><td><a href="/dragen-clinical-research-apps/readme/dragen-solid-wgs-tn-pipeline.md">Solid WGS TN</a></td><td>No</td><td>Only Header and TN_Data sections required in SampleSheet.csv</td></tr></tbody></table>

## Sample Sheets

All the clinical research workflow pipelines support only [v2 sample sheet](/dragen-clinical-research-apps/readme/common/run-planning.md) and requires index2 to be in forward orientation, with bcl-convert SoftwareVersion >= 4.4. The pipelines are stil compatible with legacy sample sheets where the BCLConvert\_Settings section has SoftwareVersion < 4.4. Sample sheet v1 is no longer supported.

## Cloud Pipelines

The clinical research pipelines in the BioInSight Platform Core support [post-processing scripts](/dragen-clinical-research-apps/readme/common/advanced/post-processing.md) to be executed after the completion of the pipeline analysis.

## ICI Variant Interpretation

The clinical research workflow pipelines support [automatic data ingestion or manual upload into ICI for variant interpretation](broken://pages/9F8145tsQQtI1bk7x2sR) after the analysis is completed in ICA, or using a [DRAGEN on-premises server locally](broken://pages/E3cTPAlHcdOl8uTfooiT).


---

# 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/dragen-clinical-research-apps/readme/common.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.