> 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/curation-status-v100.41+.md).

# Curation status (v100.41+)

A *curation status* records the review state of a variant, gene, or article in your organization's **Curate** database. Each curated variant, gene, and article has one of these statuses:

* **Draft**
* **Pending review**
* **Approved**
* **Reclassification needed**
* **Artifact**

{% hint style="info" %}
Network-only[^1] variants do not have a curation status. Their status shows as **NA** and cannot be changed.
{% endhint %}

Curation status appears in these places:

* The header of the [**Curate Variant page**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page/top-bar.md), [**Curate Gene page**](/emedgene/emedgene-curate-manual/curate_genes_2_28/curate_gene_page/top-bar.md), and [**Curate Article page**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/header.md). You can view and change the status here.
* The **Status** column of the [**Curate Variant table**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_table.md#variant-table-columns), [**Curate Gene table**](/emedgene/emedgene-curate-manual/curate_genes_2_28/curate_gene_table.md#gene-table-columns), and [**Curate Article table**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-table.md#article-table-columns). You can sort and move this column like any other column.
* The variant popup of the [**Curate** track](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool/visualization-tracks/curated-data-tracks.md) in the **Variant visualization tool**, as the **Curation status** field.

## Default curation status

New variants, genes, and articles receive the **Draft** status. The exception is a variant batch upload, where you can set each variant's status in the CSV file:

* If the **Status** column has a value, the variant receives that status.
* If the column or the value is missing, the variant receives the **Draft** status.

Variants and genes curated before your organization upgraded to v100.41 have the **Approved** status.

## Variant curation status and automatic annotation

From pipeline version v100.41, your organization selects which curation statuses allow a variant's Curate data to automatically annotate the same variant in cases.

The setting applies only to new and reanalyzed cases. Existing cases keep their original annotations.

Select the statuses in the **Curate Annotation** card of the **Workbench & Pipeline** organization settings. By default, **Draft** and **Approved** are selected.

On earlier pipeline versions, all curated variants are used for annotation, regardless of their status.

[^1]: Shared by collaborators but not stored in your organization’s **Curate** database.


---

# 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/curation-status-v100.41+.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.