> 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/settings/organization_settings_-330+/workbench-and-pipeline/curate-annotation-v100.41+.md).

# Curate Annotation (v100.41+)

Use the **Curate Annotation** card to select which curation statuses allow a variant's **Curate** data to automatically annotate that variant in new and reanalyzed cases.

By default, **Draft** and **Approved** are selected.

{% hint style="info" %}
The card is available from v100.41. On earlier versions, the card is inactive, and all curated variants are used for annotation regardless of their status.
{% endhint %}

## Select the curation statuses used for annotation

**Prerequisite:** You have the required [permissions](/emedgene/emedgene-analyze-manual/settings/user_roles/iam-scopes-emedgene-roles.md).

{% stepper %}
{% step %}
In the **Curate Annotation** card:

* Select each status to use for annotation.
* Clear each status to exclude.

Select at least one status. When you clear every status, **Save** is unavailable.
{% endstep %}

{% step %}
Select **Save** to confirm your selection.
{% endstep %}
{% endstepper %}

**Result:**

* Cases that you create or reanalyze after the change are annotated only with curated data from variants with a selected status.
* Existing cases keep their original annotations unless reanalyzed.
* The organization activity log records the change.


---

# 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/settings/organization_settings_-330+/workbench-and-pipeline/curate-annotation-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.