> 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/emedgene/emedgene-analyze-manual/variant_page/clinical_significance_section/variant-info/resources.md).

# Resources

The Resources field provides links to external databases with pre-filled search queries, helping users efficiently gather supporting evidence for variant interpretation.

## Available resources

* **UCSC Genome Browser**
* **GeneCards** (retired in v100.39.0)
* **PubMed**
* **WikiGenes** (retired in v100.39.0)
* **Google Scholar** (v100.39.0+)
* **LitVar2** (v100.39.0+)
* **Genomenon**

## How search queries are built

### v100.39.0+ and above

Search queries are built using **detailed variant information** whenever possible.

The smart query builder:

* Supports variant aliases
* Takes variant type into account for more precise and context-aware results

The query logic varies by variant type:

* **SNV/indel (including mtDNA):** Includes gene symbol, dbSNP identifier, HGVS coding change, and HGVS protein change across affected transcripts
* **DEL, DUP:** Includes gene symbol, ISCN notation, cytoband, genomic location, and standard terms like «CNV», «deletion» and similar
* **INS:** Includes gene symbol, cytoband, genomic location, and standard SV descriptors, and standard terms like «SV», «rearrangement» and similar
* **TRA (v100.41+), INV (v100.41+):** Includes gene symbols, genomic locations, and standard terms like «translocation», «rearrangement», «breakpoint», «BND» and similar
* **BND (v100.41+):** Includes gene symbol, genomic location, and standard terms like «rearrangement», «breakpoint», «BND» and similar

### Versions prior to v100.39.0

Search queries are based on **gene information** only.


---

# 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/emedgene/emedgene-analyze-manual/variant_page/clinical_significance_section/variant-info/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.