> 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/evidence-collection-experimental-evidence/functional-alteration-evidence.md).

# Functional Alteration Evidence

Functional alteration evidence shows that cultured cells in which the function of the gene has been disrupted have a phenotype that is consistent with the human disease process.&#x20;

Curation of functional alteration evidence is based on whether the experiments were conducted with <mark style="color:green;">**Patient cells**</mark> or <mark style="color:green;">**Non-patient cells**</mark>; select the appropriate option from the pull-down menu:

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FeXBTxKF3uFYRDHpZJe9D%2FScreen%20Shot%202022-06-02%20at%204.55.27%20PM.png?alt=media\&token=614717a4-122d-4c18-81e8-f616909ed2f0)

The curation interface for both options has a number of required fields, shown with an asterisk next to the field. For both, the required fields are:

* **Experiment name** is a free-text field; please choose a descriptive name for the experiment.
* **Normal function of gene/gene product** requires an entry in either the Gene Ontology (GO) ID or the free text field.
* **Description of gene alteration** is a free-text field that enables you to describe how the function of the gene was altered in the experiment.
* **Evidence for altered function** is a free-text field that enables you to describe the evidence presented in the publication.

For the "<mark style="color:green;">**Patient cells**</mark>" option, the additional required field is:

* **Patient cell type** requires an entry in either the Cell Ontology (CL) ID or the free text field.

For the "<mark style="color:green;">**Non-patient cells**</mark>" option, the additional required field is:

* **Non-patient cell type** requires an entry in either the Experimental Factor Ontology (EFO)/Cell Ontology (CL) ID or the free text field.

Links to the Cell Ontology (CL) and the Experimental Factor Ontology (EFO) are provided to aid in searching for the correct ID.

Finally, select whether the experimental evidence should be scored, brought up for review by the GCEP, or contradicts the gene-disease association.

{% hint style="warning" %}
Remember to click the "Save" button at the bottom of the page. If you click "Cancel" or navigate away from the page without saving, all entered data will be lost.
{% endhint %}


---

# 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/evidence-collection-experimental-evidence/functional-alteration-evidence.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.
