> 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-articles/curate-article-page.md).

# Curate Article page

The **Curate Article page** presents curated article information. Use it to review and manage article curations.

**Curate Article page** includes:

* [**Header**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/header.md): Shows the PMID, article title, and curation status.
* **Cards**:
  * [**Article Information card**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/article-information-card.md): Presents bibliographic details imported from PubMed and provides the article file upload workflow.
  * [**Interpretation card**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/interpretation-card.md): Displays and allows editing of curated interpretation text and notes.
  * [**Relevance Tags card**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/relevance-tags-card.md): Displays and allows editing of relevance tags.
  * [**Gene-Disease Connections card**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/gene-disease-connections-card.md): Lists the gene-disease connections and phenotypes reported in the article.
  * [**Variant card**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/linked-variants.md): Lists variants associated with the article and provides actions for adding them to **Curate**.
* [**Activities panel**](/emedgene/emedgene-curate-manual/curate-articles/curate-article-page/activities-panel.md): Records changes to the article entry.

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Curate Articles</strong></td><td>Overview of the <strong>Articles</strong> section in <strong>Curate</strong>.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate-articles.md">Learn more</a></td></tr><tr><td><strong>Curate Article table</strong></td><td>Find and open an article from the article list.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate-articles/curate-article-table.md">Learn more</a></td></tr><tr><td><strong>Adding articles to Curate</strong></td><td>Import an article from PubMed by PMID.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-curate-manual/curate-articles/adding-an-article-to-curate.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-articles/curate-article-page.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.