> For the complete documentation index, see [llms.txt](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/gci-help/publishing-an-approved-gene-disease-record/editing-the-disease-term-of-a-published-gene-disease-record.md).
# Editing the Disease Term of a Published Gene-Disease Record
Disease terms cannot be changed on published gene-disease records so it must be unpublished first. Select the "Unpublish Summary" link in the "Saved Provisional and Approved Classification(s)" panel.
A new panel will appear **above** the "Saved Provisional and Approved Classification(s)" panel
An label will now appear in the "Saved Provisional and Approved Classification(s)" panel.
You can now return to Curation Central for the gene-disease record, and the "Disease" edit button in the header will be active and allow you to select a new disease term.
After you've selected a new disease term and are ready to republish the classification, select "Administrative Update: Disease Name Update."
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/gci-help/publishing-an-approved-gene-disease-record/editing-the-disease-term-of-a-published-gene-disease-record.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
