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

# Variant tagging widget

Variant tags are shown in the Variant tagging widget of the [Variant page header](/emedgene/emedgene-analyze-manual/variant_page/variant_page_top_bar.md).

When a variant is tagged by a user, the user's tag is displayed in the tag field. If the variant is only tagged by AI Shortlist and not by a user, the tag AI Shortlist is displayed. If a variant has not been tagged, the tag is shown as N/A.

{% hint style="info" %}
**Note:** After a case [reanalysis](/emedgene/emedgene-analyze-manual/reviewing_a_case/editing_an_existing_case.md), all variants appear as not viewed.
{% endhint %}

A variant can be tagged by the AI Shortlist or a user as:

* Most Likely Candidate - most promising for solving the case
* Candidate - worth considering
* [Incidental](/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/2.-family-tree/secondary_findings.md) - meets the ACMG criteria for reporting secondary findings
* Carrier - identified by the Carrier analysis pipeline
* In Report - manually selected to be reported
* Not relevant - automatically tagged variant that has been disregarded after manual review
* Any custom tag used in your organization (e.g., Submitted for Sanger confirmation)

## Variant tagging widget how-to

### Add or change a tag

Click on the dropdown icon in the Variant tag field and select a suitable tag. The Variant tag field showcases the most recently assigned tag.

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-a84a66515b756c1ae600c65ee2bc7748fbeeb5a0%2Fvariant_tagging_widget_1_image.png?alt=media)

### Review the tagging history

Click on the Variant tag field and scroll to the Assigned tags section.

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-9e8e6a3e3705d720ac3876edcfa3ec1ad05a9026%2Fvariant_tagging_widget_2_image.png?alt=media)

### Remove an automatic tag

Click on the dropdown array in the Variant tag field and select Not relevant.

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-7df79240487a96400dec0c934dbec87c2b4c8199%2Fvariant_tagging_widget_4_image.png?alt=media)

### Clear your manual tag:

Click on the dropdown array in the Variant tag field and select Clear.

{% hint style="warning" %}
**Note:** you can't clear a tag added by another user.
{% endhint %}

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-d03dd1f53514d20ecb902d997e66791eaaef65a2%2Fvariant_tagging_widget_5_image.png?alt=media)


---

# 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/variant_tagging_widget.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.