> 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/completing-case-interpretation.md).

# Completing case interpretation

Once you have reviewed the case, updated variant details and interpretations where needed, and assigned relevant tags, complete the case interpretation.

## How to complete case interpretation

{% stepper %}
{% step %}

### Open the **Case interpretation widget**

On the **Individual Case page**, click the **Case interpretation** button in the top bar.

{% hint style="info" %}
**Tip:** Click **Save** at any time to save your progress.
{% endhint %}
{% endstep %}

{% step %}

### Indicate the case result

In the left panel, select the final analysis result.

<table><thead><tr><th width="373">Case result</th><th>Case result category</th></tr></thead><tbody><tr><td><strong>Case is confidently solved (Positive)</strong></td><td><mark style="background-color:green;">Resolved</mark></td></tr><tr><td><strong>Case is likely to be solved (Positive)</strong></td><td><mark style="background-color:green;">Resolved</mark></td></tr><tr><td><strong>Further investigation (Uncertain)</strong></td><td><mark style="background-color:green;">Resolved</mark></td></tr><tr><td><strong>Case is not solved (Negative)</strong></td><td><mark style="background-color:red;">Not resolved</mark></td></tr></tbody></table>

Case results are grouped into **Resolved** and **Not resolved** categories and you can [filter cases](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/how-to-filter-cases.md) in the **Cases table** by them.
{% endstep %}

{% step %}

### Select variants to include in the report

1. In the **left panel**, open the **variant tag** dropdown to view all tags used in the case.
2. Select a **tag** to view variants assigned to that tag.
   * **Single‑tag mode**
     * Each variant appears under the last tag assigned to it.
     * Variants tagged by the [**AI Shortlist**](/emedgene/emedgene-analyze-manual/reviewing_a_case/candidates-tab/most_likely_candidates_and_candidates.md) appear in a **Most Likely**, **Candidate**, **Most Likely** [**GUS**](#user-content-fn-1)[^1], or **Candidate** [**GUS**](#user-content-fn-1)[^1] list. If a user applies a different tag, the variant appears in that tag’s list.
   * **Multi‑tag mode**
     * Each variant appears under all tags it has been assigned, not just the last one.
     * If a variant is selected under Tag A, it also appears selected when you filter by Tag B.
3. Select variants to report by selecting the checkbox next to each variant.
4. Switch to another tag if needed and repeat the selection process.
5. Adjust variant order if needed.\
   Variant order in the final list is preserved in the report within each tag group and variant type. You can reorder variants by drag-and-drop.

{% hint style="info" %}
**Note:** Each variant in the **Case interpretation widget** is specified at the coding DNA and protein level when applicable; otherwise, it is described at the genomic DNA level.
{% endhint %}
{% endstep %}

{% step %}

### Enter your case-level notes

Add supporting information that applies to the case:

* **Interpretation notes**
* **Gene interpretation**\
  You can [import](/emedgene/emedgene-curate-manual/curate_variant_annotations_in_the_case/import_curate_gene_annotations_to_the_case_-300+.md) gene interpretations from **Curate** for any gene affected by a reported variant in the case.
* **Recommendations**

These notes are saved with the case and automatically populate the report.
{% endstep %}

{% step %}

### Save the case interpretation

Select **Save** to save the case interpretation.
{% endstep %}
{% endstepper %}

### Result

The saved case interpretation includes the selected case result, details of reported variants and their interpretations, and case-level notes. This information becomes available for the report.

[^1]: Gene of unknown significance


---

# 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/completing-case-interpretation.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.