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

# Saving an Evaluation Summary

#### When to Save a Summary

You will need to Save the Evaluation Summary:

1. If you want to Save any any edits made to the "Modify Classification", "Explain reason(s) for change", and/or "Evidence Summary" fields, OR
2. If you want the option of making a Provisional Interpretation based on the current evidence/evaluations.

{% hint style="warning" %}
While the system allows you to save the summary and make a provisional interpretation without an Evidence Summary, a summary statement is a required part of the curation process. 
{% endhint %}

#### In Progress Status

The first time an Evaluation Summary is saved the status of the Interpretation will change to "In Progress". The Interpretation will remain "In Progress" until a summary is saved as Provisional.

#### Saving New Summaries

Every time the Save button is clicked in the Evaluation Summary, any previous summary is overwritten and the ‘Interpretation Last Edited’ is appended with a "New Saved Summary" label.


---

# 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-evaluation-summary/saving-an-evaluation-summary.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.