> 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/connected-insights/interpret-and-report/viewdetails-introduction/viewdetails-cancer-data-sets.md).

# Cancer Datasets

This section provides details on the variant’s presence in different datasets.

## Lab Frequency

Displays the number of samples with the variant in the given workgroup presented per disease. To be accounted for, the variant:

* Need to be present in any uploaded VCF or variant file
* Need to have a flag PASS in the VCF variant filters
* Doesn’t need to be interpreted or included in the report
* Can have any variant origin (predicted germline or suspected somatic)

❗ Cases processed prior to version 4.0 of Connected Insights will not appear in the lab frequency.

## Cancer Hotspots

The section displays:

* Number of samples in the [Cancer Hotspots database](https://www.cancerhotspots.org) with the variant for the selected transcript
* Highest number of samples in the [Cancer Hotspots database](https://www.cancerhotspots.org) for the variant across transcripts

## COSMIC

The section displays:

* Genomic Mutation ID in the COSMIC database
* Number of samples with the variant in the COSMIC database displayed per cancer site, for example, breast
* Number of samples with the variant in the COSMIC database displayed per histology, for example, carcinoma


---

# 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/connected-insights/interpret-and-report/viewdetails-introduction/viewdetails-cancer-data-sets.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.