> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/case-completion-and-reporting/finalizing_a_case.md).

# Finalizing a case

Finalizing a case prevents users from making further changes after work is completed.

## How to finalize a case

{% stepper %}
{% step %}

### Update the **case status** to **Finalized**

{% hint style="info" %}
The case status can be [updated](/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status/how-to-update-a-case-status.md) to **Finalized** only from the **Individual Case page**, not the **Cases table**.
{% endhint %}

1. In the top bar of the **Individual Case page**, select the dropdown next to the current case status.
2. From the dropdown menu, select **Finalized**. Selecting this status automatically opens the **Case interpretation widget**.
   {% endstep %}

{% step %}

### Review or complete case interpretation

In the **Case interpretation widget**, review and update the following if needed:

* Case result
* Selected variants
* **Interpretation notes**, **Gene interpretation**, and **Recommendations**

If [case interpretation](/emedgene/emedgene-analyze-manual/case-completion-and-reporting/completing-case-interpretation.md) was already completed earlier, this step serves as a final confirmation.
{% endstep %}

{% step %}

### Select **Finalize**

{% hint style="warning" %}
**Finalize** locks the case and makes it read-only. Organization managers can reopen it by [changing its status](/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status.md).
{% endhint %}

Select **Finalize** in the widget to lock the case.
{% endstep %}
{% endstepper %}

### Result

After the case is finalized, it becomes read‑only. No edits can be made to:

* **Variant information**:
  * Variant tags
  * Selected gene-related disease
  * **Variant Interpretation**
  * HGVS nomenclature
  * **Pathogenicity**
  * **ACMG classification**
* **Case information:**
  * Case result
  * Variants selected for reporting
  * **Interpretation notes**
  * **Gene interpretation**
  * **Recommendations**
  * **Case details**

***

## How to review finalized cases

{% hint style="warning" %}
**Gene interpretation** and **Recommendations** are unavailable for review after finalization, except in report.
{% endhint %}

### How to review the case

Review a finalized case as you would any other case. Editing is disabled.

### How to review finalized details

#### Variants selected for reporting

* **To inspect reported variants in full detail:** Open the [**Candidates tab**](/emedgene/emedgene-analyze-manual/reviewing_a_case/candidates-tab.md) and select **Finalized** in the dropdown.
* **To confirm the reported variant list:** Open the [**Case details panel**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/case_details.md) and select the **Finalize** tab. Each entry is shown in **`chromosome`**`:`**`location`** **`ref`**`>`**`alt`** format.

#### Case result and Interpretation notes

To review the case result and **Interpretation notes**, open the [**Case details panel**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/case_details.md) and select the **Finalize** tab.


---

# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/case-completion-and-reporting/finalizing_a_case.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.