> 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_genes_2_28/curate_gene_page/top-bar.md).

# Header

## Header contents

The header of the [**Curate Gene page**](/emedgene/emedgene-curate-manual/curate_genes_2_28/curate_gene_page.md) shows the key identifying details of the gene and its curation status. The header highlights:

* Gene symbol
* DNA strand orientation
* Gene type
* Clickable HGNC ID (links to HGNC)
* Clickable NCBI ID (links to NCBI Gene)
* Curation status (v100.41+)

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-c81407da1bd27b1b3fca4697206f87a1a7a06c6a%2Fapp.png?alt=media" alt="Header of the Curate Gene page in v100.41."><figcaption><p><strong>Header of the Curate Gene page</strong> in v100.41.</p></figcaption></figure>

***

## How to update the gene curation status (v100.41+)

Use the curation status dropdown in the header to set the review state of gene's curated data.

**Prerequisite:** You need [permissions](/emedgene/emedgene-analyze-manual/settings/user_roles/iam-scopes-emedgene-roles.md) to change the curation status.

{% stepper %}
{% step %}
In the header of the **Curate Gene page**, select the curation status dropdown.
{% endstep %}

{% step %}
From the dropdown, select **Draft**, **Pending review**, **Approved**, **Reclassification needed**, or **Artifact**.
{% endstep %}
{% endstepper %}

**Result:**

* The curation status is updated for the gene.
* The change is recorded in the [**Activities panel**](/emedgene/emedgene-curate-manual/curate_genes_2_28/curate_gene_page/activities-panel.md).


---

# 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_genes_2_28/curate_gene_page/top-bar.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.