> 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/report.md). # Reporting ## Reporting solution overview The reporting feature generates case reports using template-defined logic to compile case-level and variant-level information from two primary sources: * **User‑entered data**, such as user‑selected disease, case metadata, sample information, interpretation notes, variant tags, pathogenicity assignments, disclaimers, and methodology statements. * **Automatically extracted annotations**, such as automatically selected disease, variant details, quality metrics, and population frequencies. The reporting engine extracts case and variant data, then automatically populates template sections. Template conditions determine which content appears for each case. **Benefits of the reporting solution:** * **Reduced manual work:** Automatic data population eliminates repetitive text entry. * **Consistency and reproducibility:** Reports follow standardized logic across cases. * **Traceability:** Reports generated in finalized cases are saved and can be reviewed or downloaded at any time. * **Customizability:** Templates can be tailored to your laboratory’s clinical, regulatory, and branding requirements. ### Template types Emedgene uses two types of templates: * **Case report templates**, used to automatically create complete case reports that include proband and sample details, a summary of findings, the final case outcome, and interpretation and recommendations. * **Variant interpretation templates**, used to automatically create variant‑level interpretation notes that may be incorporated into case reports. ### Customization **Emedgene** provides out‑of‑the‑box templates for case‑level and variant‑level reports. These standard templates include essential components such as case metadata, variant summaries, interpretation notes, and test details. If your organization requires alignment with specific SOPs or branding guidelines, templates can be customized to include: * Conditional sections based on variant type * Dynamic paragraphs triggered by tags or pathogenicity * Organization‑specific disclaimers or formatting rules * Multiple electronic signatures To request custom template development beyond the standard offering, contact your Illumina representative. ## Next steps To learn more, continue with:


Previewing and generating report	Previewing and generating report	Step‑by‑step explanation of how reports are prepared, finalized, and generated.
Downloading reports in a finalized case	Downloading reports in a finalized case	Access previously generated reports.
Troubleshooting	Troubleshooting	Common causes of report rendering issues and how to resolve them.

--- # 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/report.md?ask=&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.