> 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.md).

# Case completion and reporting

After you review and interpret the variants in a case, move on to case completion and reporting:

1. **Complete case interpretation.** Set the case result, select variants for the report, and add notes.
2. **Preview the draft report.** Check the content, layout, and formatting before finalizing.
3. **Finalize the case and generate the final report.** Finalization makes the case read-only. Final reports remain available for review and download.

Learn more about each stage below.

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Completing case interpretation</strong></td><td>Step‑by‑step guidance on completing case interpretation in the <strong>Case Interpretation</strong> widget.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/case-completion-and-reporting/completing-case-interpretation.md">Learn more</a></td></tr><tr><td><strong>Finalizing a case</strong></td><td>How to lock the case once interpretation is confirmed to prevent further edits.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/case-completion-and-reporting/finalizing_a_case.md">Learn more</a></td></tr><tr><td><strong>Reporting</strong></td><td>Overview of the reporting solution with instructions on generating a draft or final report.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/case-completion-and-reporting/report.md">Learn more</a></td></tr></tbody></table>


---

# 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.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.