> 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/creating-a-gene-disease-record/creating-a-free-text-disease-identifier.md).

# Creating a Free-Text Disease Identifier

{% hint style="warning" %}
It is **strongly recommended** that you select a MONDO ontology term for your disease. Gene-disease records with free-text disease identifiers can not be published to the ClinGen website. MONDO disease identifiers are very important for linking and transferring information on the database end. If you cannot find an appropriate MONDO term, please feel free to contact us at <clingen-helpdesk@lists.stanford.edu> and we will be happy to assist. However, as a **last resort**, if you cannot find an appropriate term, you may create a disease term using free text.
{% endhint %}

To enter a free text term, click on the "Add free text term" link in the "Select Disease" selection screen.&#x20;

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2F9DFS2TzqRzWOQ7mRsn2N%2FScreen%20Shot%202022-04-12%20at%202.31.02%20PM.png?alt=media\&token=1fe86391-d4c4-4459-b8a1-d0d171bf6dbb)

In the new selection screen, you can enter a disease name in free text (up to 100 characters in length). Please remember that if someone else enters a different name for the same disease, the interface will not be able to determine that they are equivalent. You must also provide either a set of Human Phenotype Ontology (HPO) terms (preferred -- a link to the [HPO Browser](https://hpo.jax.org/app/browse/term/HP:0000118) is provided; see also [HPO Search Help](/vci-gci-docs/external-tools/hpo-search-help.md)) or a free-text definition for the term you are entering. You may also provide both. Click "Save" to save the new disease record.&#x20;

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FuVSXVtwYZhUWREiDbCJP%2FScreen%20Shot%202022-04-11%20at%206.09.09%20PM.png?alt=media\&token=167ced43-5ff6-4434-a666-3b6c577a7fa8)


---

# 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://vci-gci-docs.clinicalgenome.org/vci-gci-docs/gci-help/creating-a-gene-disease-record/creating-a-free-text-disease-identifier.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.