> 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/model-systems-evidence.md).

# Model Systems Evidence

Model systems evidence shows that a non-human model organism or a cell culture model with a disrupted copy of the gene has a phenotype consistent with the human disease state.&#x20;

Curation of model systems evidence is based on whether the experiments were conducted with a <mark style="color:green;">**non-human model organism**</mark> or a <mark style="color:green;">**cell culture model**</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%2FFlnX5IEPpx6rehq7TNZj%2FScreen%20Shot%202022-06-03%20at%209.26.46%20AM.png?alt=media\&token=5b7dcf30-c4f7-46fa-a811-c4225af88968)

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.
* **Description of gene alteration** is a free-text field that enables you to describe how the endogenous gene was altered in the experiment.
* **Phenotype(s) observed in model system** requires an entry in either the Human Phenotype Ontology (HPO)/Mammalian Phenotype Ontology (MP) ID or the free text field.&#x20;
* **Human phenotype(s)** requires an entry in the Human Phenotype Ontology (HPO) ID or the free text field.&#x20;
* **Explanation of how model system phenotype is similar to phenotype observed in humans** is a free-text field.

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

* **Non-human model organism** presents a dropdown menu of non-human model organism options. New organisms can be added upon request; please email us at <clingen-helpdesk@lists.stanford.edu>.

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

* **Cell culture model type/line** requires an entry in either the Experimental Factor Ontology (EFO)/Cell Ontology (CL) ID or the free text field.

Links to the Human Phenotype Ontology (HPO), Cell Ontology (CL) and the Experimental Factor Ontology (EFO) are provided to aid in searching for the correct ID. A link to the Mammalian Phenotype Ontology (MP) is [here](http://www.informatics.jax.org/vocab/mp_ontology).

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 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/model-systems-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.
