> 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/top-bar.md).

# Header

## Header contents

The header of the [**Curate Variant page**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page.md) shows the key identifying details of the variant, pathogenicity classification, and curation status (v100.41+).

### Small variants

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-bc72ffbe228597d286a967833b32e41632904470%2Fimage%20(167).png?alt=media" alt=""><figcaption><p><strong>Header of the Curate Variant page</strong> for a small variant.</p></figcaption></figure>

For small variants, including mtDNA variants, the header highlights:

* Clickable gene symbol linked to the gene page in [**Curate Genes**](/emedgene/emedgene-curate-manual/curate_genes_2_28.md)
* Variant type: `SNV`, `small ins`, or `small del`
* Genomic position and nucleotide change
* HGVS variant description
* [Main variant effect](/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/how_does_emedgene_calculate_variant_effect_and_severity.md)
* Pathogenicity classification
* Curation status (v100.41+)

### CNVs

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-b1327b8c3476b0695d06e79354d37775cccad3c4%2Fimage%20(166).png?alt=media" alt=""><figcaption><p><strong>Header of the Curate Variant page</strong> for a copy number variant.</p></figcaption></figure>

For copy number variants, the header highlights:

* For each involved gene, a clickable gene symbol linked to the gene page in [**Curate Genes**](/emedgene/emedgene-curate-manual/curate_genes_2_28.md)
* Variant type: `DEL` or `DUP`
* Genomic range and variant length
* Pathogenicity classification
* Curation status (v100.41+)

***

## How to update curated variant pathogenicity

{% stepper %}
{% step %}
In the header of the **Curate Variant page**, select **Pathogenicity**.
{% endstep %}

{% step %}
From the dropdown, select the classification you want to assign to the variant.
{% endstep %}
{% endstepper %}

**Result:** The pathogenicity classification is updated for the variant and used in future case annotations.

***

## How to update the variant curation status (v100.41+)

Use the curation status dropdown in the header to set the review state of the variant's curated data.

{% hint style="info" %}
For a network-only variant, the curation status shows **NA** and cannot be changed.
{% endhint %}

**Prerequisite:** You need [permissions](/emedgene/emedgene-analyze-manual/settings/user_roles/iam-scopes-emedgene-roles.md) to change the curation status.

{% stepper %}
{% step %}
In the header of the **Curate Variant page**, select the curation status dropdown.
{% endstep %}

{% step %}
From the dropdown, select **Draft**, **Pending review**, **Approved**, **Reclassification needed**, or **Artifact**.
{% endstep %}
{% endstepper %}

**Result:**

* The curation status is updated for the variant.
* The change is recorded in the [**Activities panel**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page/activities-panel.md).


---

# 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/top-bar.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.
