> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/library-preparation/amplicon-library-prep/library-preparation-amplicon-library-prep-faq-list/000007433.md).

# Viral Surveillance Panel (VSP) probes and panel design frequently asked questions (FAQs)

**Which viruses are targeted**? The list of viruses detected can be found on the [product page](https://www.illumina.com/products/by-type/sequencing-kits/library-prep-kits/viral-surveillance-panel.html#tabs-090604f93b-item-ddcfc55931-figures), in the "FAQ" section, under "show more", in "What viruses are included in VSPv2?" or, selecting the link [here](https://1177916873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4OEB7VheHjRG5hBZXuPi%2Fuploads%2Fgit-blob-062620746dd1db19d3b21c46dc3c4c949f3df6e7%2FVSPV2_2-7-0_Panel_Summary.xlsx?alt=media) will directly download the targeted virus list (.xlsx file).

**Does VSP detect DNA or RNA pathogens**?Both v1 and v2 target both DNA and RNA viruses. dsRNA, ssRNA, dsDNA, and ssDNA viruses are detected using the library prep workflow (note: ds = double stranded, ss = single stranded).

**What are the probe sequences**?v1 and v2 probe sequences and probe design are the intellectual property of Illumina and are proprietary.

**Are there any probes targeting human control genes in the design**?No probes target human control genes in either v1 or v2.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7433), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007433%20-%20Library%20Preparation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/library-preparation/amplicon-library-prep/library-preparation-amplicon-library-prep-faq-list/000007433.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.