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

# Curate Variants

The **Curate Variants** tab is where you review and manage variants in your organization’s **Curate** database and variants shared by collaborators from your **Network**.

Use **Curate Variants** to:

* Add or delete curated variant annotations.
* Review curated variants.

The **Curate Variants** **tab** includes:

* [**Curate Variant table**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_table.md): Lists the variants in your **Curate** database.
* [**Curate Variant page**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page.md): Shows detailed information for the selected variant.

The [**Curate navigation panel**](/emedgene/emedgene-curate-manual/curate_navigation_panel.md) provides access to other **Curate** tabs and the flow for adding new entries.

![Curate Variants tab interface.](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-075cd1df64cdd962afd6266fc94e0202b972b55f%2Fcurate_variants_overview_1_curate_variants_overvie.gif?alt=media)

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Variants supported in Curate</strong></td><td>Review the variant types that <strong>Curate</strong> supports and does not support.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variants/variants-supported-in-curate.md">Learn more</a></td></tr><tr><td><strong>Curate Variant table</strong></td><td>Search, sort, and review variants stored in your organization’s <strong>Curate</strong> database.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variants/curate_variant_table.md">Learn more</a></td></tr><tr><td><strong>Curate Variant page</strong></td><td>Review interpretation details, pathogenicity, related cases, and network data for a variant.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page.md">Learn more</a></td></tr><tr><td><strong>Adding variants to Curate</strong></td><td>Add one variant, upload many variants, or export a variant from <strong>Analyze</strong>.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate.md">Learn more</a></td></tr><tr><td><strong>Curate Variant annotations in the case</strong></td><td>See how <strong>Curate</strong> data appears in <strong>Analyze</strong> during case and variant review.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variant_annotations_in_the_case.md">Learn more</a></td></tr><tr><td><strong>Deleting a variant from Curate (v100.39+)</strong></td><td>Permanently remove a variant from your organization’s <strong>Curate</strong> database.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate_variants/how-to-delete-a-variant-in-curate-v100.39.0+.md">Learn more</a></td></tr></tbody></table>


---

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