> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/case_details/case-info.md).

# Case info

The Case info tab includes the following information:

{% tabs %}
{% tab title="Technical" %}

* Case ID—a unique identifier assigned to each case by Emedgene, formatted as EMGXXXXXXXXX
* Case type—the type of analysis performed:
  * Whole Genome
  * Exome
  * Custom Panel
  * Array
* Sample type—the format of the sample files used in the case:
  * FASTQ: \*.fastq.gz, \*.fq.gz, \*.bam, \*.cram.
  * Project VCF: \*.pvcf, \*.vcf, \*.vcf.gz, \*.pvcf.gz
  * VCF: \*.vcf, \*.vcf.gz, \*.targeted.json, \*.gt\_sample\_summary.json
* Gene list—defines whether gene list was used during analysis and how it was applied:
  * All genes—AI Shortlist was neither confined to nor prioritized a specific gene list
  * Virtual panel (In silico panel)—AI Shortlist was limited to only the genes in the gene list
  * Boosted gene list—AI Shortlist analyzed variants in all genes, but variants in the gene list were given higher priority
* Analysis type:
  * If field is not present—carrier analysis was not performed
  * Carrier—carrier analysis was performed for the selected gene list
* Human reference—the genome reference used during case analysis
  {% endtab %}

{% tab title="Operational" %}

* Ordered by—the user who created the case and the case creation date
* Signed by—the user who finalized the case
* Related cases—the Case IDs of other cases that share one or more samples with the selected case
* Due Date—the user-defined deadline for finalizing the case. To enter or edit the Due Date, click the calendar icon in the Due Date section
* Participants—Users involved in the case, whether in submission, analysis, finalization, or those subscribed to updates. To receive email notifications, click the Subscribe icon. To unsubscribe, hover over your avatar and click the X icon
  {% endtab %}

{% tab title="Clinical" %}

* Patient Information—basic demographic details:
  * Sex. Specified by the user
  * Age. Automatically calculated in years based on the provided date of birth
* Clinical Information:
  * Proband phenotypes—HPO terms used to describe clinical findings in the proband
  * Suspected disease—if provided, includes the suspected condition, penetrance (%), and severity (mild, moderate, severe, or profound)
  * Maternal and Paternal [ethnicity](/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/2.-family-tree/supported_parental_ethnicities.md)—ethnic background of the proband’s parents
  * Parental consanguinity—indicates whether the parents are related by blood
  * Report secondary findings—specifies whether secondary findings analysis was requested
* Clinical note—free-text notes provided at the time of launching the analysis
  {% endtab %}

{% tab title="Additional" %}
Additional case information can be added using custom fields, either via the API or by including extra columns in your CSV during batch case creation.\
This allows you to extend the case details panel with project-specific data.\
To enable this feature or learn more, please contact <techsupport@illumina.com>.
{% endtab %}
{% endtabs %}


---

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

```
GET https://help.connected.illumina.com/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/case_details/case-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.