> 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/biochemical-function-evidence.md).

# Biochemical Function Evidence

Curation of biochemical function evidence is based on two options that are selected from a pull-down menu:

* <mark style="color:green;">**A. The gene product performs a biochemical function shared with other known genes in the disease of interest.**</mark> The biochemical function of both gene products must have been proven experimentally, and not just predicted. When awarding points in this evidence category, the other known gene(s) should have compelling evidence to support the gene-disease relationship.&#x20;
* <mark style="color:green;">**B. The gene product is consistent with the observed phenotype(s).**</mark>

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FXOHdsLWrOG1PFJVo6a1I%2FScreen%20Shot%202022-06-02%20at%2010.43.12%20AM.png?alt=media\&token=0dd5f66f-44f6-41ca-8485-3c8d62428742)

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.
* **Identified function of gene in this record** requires an entry in either the Gene Ontology (GO) ID or the free text field. To aid in searching for the correct GO ID, there are three links provided; one to view existing GO annotations for the gene product, one that links to the OLS GO search, and one that links to QuickGO. Only choose terms from the Molecular Function (MF) or Biological Process (BP) domains and terms that have manual experimental evidence codes associated with them, e.g. IDA, IMP, IGI, IPI or IEP.
* **Evidence for above function** is a free text field where you should describe the evidence supporting the function(s) you chose.

For <mark style="color:green;">**option A**</mark>, the additional required fields are:

* **Other gene(s) with same function as gene in record** requires entry of a valid HGNC gene name.
* **Evidence that above gene(s) share same function with gene in record** is a free text field where you should describe the evidence for shared function.

For <mark style="color:green;">**option B**</mark>, the additional required fields are:

* **Phenotype(s) consistent with function** requires an entry in either the HPO or free text fields.
* **Explanation of how phenotype is consistent with disease**

Finally, select whether the biochemical 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 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/evidence-collection-experimental-evidence/biochemical-function-evidence.md?ask=<question>&goal=<endgoal>
```

`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.
