> 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-curate-manual/curate_variants/curate_variant_page/variant-information-card.md).
# Variant information card
## Card contents
The **Variant information card** on the [**Curate Variant page**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page.md) shows key variant details.
### Small variants
Variant information card for a small variant.
For small variants, including those in mtDNA, the **Variant information card** displays:
* Variant type: `SNV`, `small ins`, or `small del`
* [Main variant effect](/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/how_does_emedgene_calculate_variant_effect_and_severity.md)
* Affected gene
* HGVS variant description
### CNVs
Variant information card for a copy number variant.
For copy number variants, the **Variant information card** displays:
* Variant type: `DEL` or `DUP`
* Variant length
* List of affected genes
***
## How to update a reference transcript for a small variant
Updating the reference transcript for a small variant.
You can select or change a reference transcript for a small variant from the dropdown menu.
{% stepper %}
{% step %}
Open the reference transcript dropdown in the **Variant information card**.
{% endstep %}
{% step %}
Select the reference transcript you want to apply.
{% endstep %}
{% endstepper %}
**Result:** The affected gene, main variant effect, and HGVS variant description are updated in the **Variant information card** and in the page header.
---
# 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-curate-manual/curate_variants/curate_variant_page/variant-information-card.md?ask=&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.
%20(2).png?alt=media)
.png?alt=media)
