> 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/vci-help/the-evidence-view.md).

# The Evidence View

SOP Section 4

### Evidence tab organization 

The Evidence View is accessible to any logged in curator.  It includes both aggregated external evidence and evidence curated manually by individual curators. Please note: you cannot curate from the evidence view . 

{% hint style="info" %}
Using the evidence view alone will not create a variant curation record on your dashboard. To create a record on the dashboard you must start an interpretation. 
{% endhint %}

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2Fje78GGrI2hhubDtgvT3m%2FVCI%20Evidence%20view.png?alt=media\&token=95242ae1-7d47-42cd-9e4d-defde60ccffb)

Once you are in the “Evidence View,” you will see the information and evidence for the selected variant organized into six tabs: Basic Information, Population, Variant Type, Experimental, Case/Segregation, and Gene-centric.

The Variant Type tab is further divided into four subtabs: Missense, Loss of Function, Silent & Intron, and In-frame Indel.

**Variant Titles**

{% hint style="info" %}
HGVS variant titles are assigned to variants as follows: 

1. The HGVS is based on the MANE Select transcript if there is one.
2. If there is no MANE Select transcript, then the HGVS is based on the ClinVar variant title.
3. If 1 and 2 do not exist, then the HGVS is based on the RefSeq canonical transcript. 
4. If 1-3 do not exist, the HGVS is based on the GRCh38 genomic coordinates.
   {% endhint %}

### Evidence types

The Evidence View displays two main types of evidence.

#### 1. External Evidence

The curation interface aggregates dozens of types of evidence from external resources such as [gnomAD](http://gnomad.broadinstitute.org/), [PAGE](https://www.pagestudy.org/), [REVEL](https://sites.google.com/site/revelgenomics/about), [ESP](http://evs.gs.washington.edu/EVS/), [ClinVar](https://www.ncbi.nlm.nih.gov/clinvar/), [dbNSFP](https://sites.google.com/site/jpopgen/dbNSFP), etc.

#### 2. Manually curated evidence

* **Evidence** a curator enters for a [PubMed](https://www.ncbi.nlm.nih.gov/pubmed/) ID (PMID) or clinical/research sources when in Interpretation mode (see next section) will be viewable by all curators in the Evidence View. 

**Note: Evaluations** (e.g. PS4 “Met”) and **Interpretations** are specific to the curator who makes them and are not viewable in the Evidence View. 

See information on manually adding [Case Segregation Data](/vci-gci-docs/vci-help/evaluating-criteria/case-segregation-data.md) and [Functional Data](/vci-gci-docs/vci-help/evaluating-criteria/functional-data.md) evidence types.


---

# 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/vci-help/the-evidence-view.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.