> 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/annotation/v3.27/core-functionality/variant-ids.md).

# Variant IDs

### Overview

Many downstream tools use a variant identifier to store annotation results. We've standardized on using variant identifiers (VIDs) that originated from the notation used by the Broad Institute.

The Broad VID scheme is not only simple, but it has the advantage that a user could create a bare bones VCF entry from the information captured in the identifier. One of the limitations of the Broad VID scheme is that it does not define how to handle structural variants. Our VID scheme attempts to fill that gap.

{% hint style="info" %}
**Conventions**

* all chromosomes use Ensembl style notation (i.e. 22 instead of chr22)
* for a reference variant (i.e. no alt allele), replace the period (.) with the reference base
* padding bases are used, neither the reference nor alternate allele can be empty
* some large variant callers lazily output N for the reference allele. If this is the case, replace it with the true reference base
  {% endhint %}

### Small Variants

#### VCF Examples

```scss
chr1	66507	.	T	A	184.45	PASS	.
chr1	66521	.	T	TATATA	144.53	PASS	.
chr1	66572	.	GTA	G,GTACTATATATTATA	45.45	PASS	.
```

#### Format

`chromosome`—`position`—`reference allele`—`alternate allele`

#### VID Examples

* 1-66507-T-A
* 1-66521-T-TATATA
* 1-66572-GTA-G
* 1-66572-G-GTACTATATATTA

### Translocation Breakends

#### VCF Example

```scss
chr1	2617277	.	A	AAAAAAAAAAAAAAAAAATTAGTCAGGCAC[chr3:153444911[	.	PASS	SVTYPE=BND
```

#### Format

`chromosome`—`position`—`reference allele`—`alternate allele`

#### VID Example

* 1-2617277-A-AAAAAAAAAAAAAAAAAATTAGTCAGGCAC\[chr3:153444911\[

### All Other Structural Variants

#### VCF Examples

```scss
chr1	1000	.	G	<ROH>	.	PASS	END=3001000;SVTYPE=ROH
chr1	1350082	.	G	<DEL>	.	PASS	END=1351320;SVTYPE=DEL
chr1	1477854	.	C	<DUP:TANDEM>	.	PASS	END=1477984;SVTYPE=DUP
chr1	1477968	.	T	<INS>	.	PASS	END=1477968;SVTYPE=INS
chr1	1715898	.	N	<DUP>	.	PASS	SVTYPE=CNV;END=1750149
chr1	2650426	.	N	<DEL>	.	PASS	SVTYPE=CNV;END=2653074
chr2	321682	.	T	<INV>	.	PASS	SVTYPE=INV;END=421681
chr20	2633403	.	G	<STR2>	.	PASS	END=2633421
```

#### Format

`chromosome`—`position`—`end position`—`reference allele`—`alternate allele`—`SVTYPE`

#### VID Examples

* 1-1000-3001000-G-\<ROH>-ROH
* 1-1350082-1351320-G-\<DEL>-DEL
* 1-1477854-1477984-C-\<DUP:TANDEM>-DUP
* 1-1477968-1477968-T-\<INS>-INS
* 1-1715898-1750149-A-\<DUP>-CNV **(replace the N with A)**
* 1-2650426-2653074-N-\<DEL>-CNV **(keep the N)**
* 2-321682-421681-T-\<INV>-INV
* 20-2633403-2633421-G-\<STR2>-STR


---

# 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/annotation/v3.27/core-functionality/variant-ids.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.