> 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-evaluation-summary/viewing-an-evaluation-summary.md).

# Viewing an Evaluation Summary

### Evaluation Summary

The first section provides a summary of the variant classification (auto-calculated and modified), disease association, mode of inheritance, and any associated specification document. 

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2F5ZSECoY2WlR3YhCbK3vk%2Feval%20summary%20view.png?alt=media\&token=306911fb-00e5-4558-8ef8-4e684d39f56a)

Following the summary information, there are three fields available to edit:

**A. Modify Classification**: pull-down which allows curator to select the pathogenicity 

**B. Reason(s) for change**: free text box for curators to explain why they selected an alternative pathogenicity to the one calculated

**C. Evidence Summary**: free text box for curators to summarize their evidence and provide a rationale for the clinical significance

{% hint style="info" %}
See [Standardized Text for ClinGen Variant Curation Expert Panels](https://clinicalgenome.org/docs/standardized-text-for-clingen-variant-curation-expert-panels/) 
{% endhint %}

### Criteria Tables

At the bottom of the Summary page, all of the ACMG criteria are split into three separate tables according their evaluation status. These tables are not editable in Summary View. To make changes, you must return to Interpretation Mode.

**Criteria meeting an evaluation strength**

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2F690370iM43nws72awiLJ%2Fcriteria%20met%20table.png?alt=media\&token=8dc78126-2e8f-442c-9c40-792b6fdf4c59)

**Criteria evaluated as 'Not met'**

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FXvpCYx5S3hEVMoI2Krin%2Fcritera%20not%20table.png?alt=media\&token=13c1286a-dd75-4da3-a0bf-ad56692f558e)

**Criteria 'Not yet evaluated'** 

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2Fe2fewjQEeOf294HT2KLr%2Fcritera%20nye%20table.png?alt=media\&token=7aa5bbdb-181a-4e60-9f15-d811a9edbc02)

Each table summarizes the evaluations made for each criterion into the following fields:

* **B/P**: Red icon indicates pathogenic; purple icon indicates benign. “Met” criteria have ticks in a circle, “Not met” have crosses in a circle, and “Not evaluated” criteria have an empty circle.
* **Criteria**: Listed using their ACMG criteria codes; color indicates pathogenicity on a scale from ‘purple’ benign to ‘red’ pathogenic.
* **Criteria Descriptions**: Brief descriptions of the ACMG criteria.
* **Modified**: For "met" criteria, ‘yes’ or ‘no’ indicates whether the criterion has a modification. "Not met" and "Not evaluated" criteria will display N/A.
* **Status**: Criteria are shown as “Met”, “Not Met” and “Not evaluated”. Additionally, “Met” indicates any modifications: \_Strong, \_Moderate, \_Supporting, \_Very strong, \_Stand-alone.
* **Explanation**: Displays criterion-level explanation provided by the curator.


---

# 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/vci-help/the-evaluation-summary/viewing-an-evaluation-summary.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.