> 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-array/dragen-array-v1.0/reference/support-and-additional-resources.md).

# Support and Additional Resources

## Technical Support <a href="#toc150786157" id="toc150786157"></a>

For support, questions, and feedback on DRAGEN Array, please contact Illumina Tech Support at <techsupport@illumina.com>.

## Additional Resources

| Resource                                                                                                                      | Description                                                                        |
| ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| [DRAGEN Array Webpage](https://www.illumina.com/products/by-type/informatics-products/dragen-array-secondary-analysis.html)   | Product features and benefits and allows product ordering.                         |
| [DRAGEN Array Support Site](https://support.illumina.com/array/array_software/dragen-array-secondary-analysis.html)           | Support site for DRAGEN Array which includes installers and product documentation. |
| [Infinium Lab Setup and Best Practices](http://support-docs.illumina.com/ARR/infinium-labsetup.htm)                           | Lab setup and maintenance information for Infinium assays.                         |
| [Infinium Assay Consumables & Equipment List](http://support-docs.illumina.com/ARR/infinium-consumables.htm)                  | List of consumables and equipment used in Infinium assays.                         |
| [iScan System Product Documentation](http://support-docs.illumina.com/ARR/iscan.htm)                                          | Instructions for operating and maintaining the iScan System.                       |
| [Polygenic Risk Score – Predict](https://support-docs.illumina.com/ARR/PRS/Content/ARR/PRS/PRS.htm)                           | Instructions for using the Polygenic Risk Score – Predict Module.                  |
| [Illumina Connected Analytics](https://support.illumina.com/sequencing/sequencing_software/illumina-connected-analytics.html) | Instructions for using the hosted environment Illumina Connected Analytics.        |
| [BaseSpace Sequence Hub](https://help.basespace.illumina.com/)                                                                | Instructions for using the hosted environment BaseSpace Sequence Hub.              |

### &#x20;<a href="#toc150786158" id="toc150786158"></a>


---

# 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-array/dragen-array-v1.0/reference/support-and-additional-resources.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.
