The Cases tab provides an overview of genomic sequencing cases submitted by the organization, as well as individual case details.

The Cases tab includes:

1. Cases table—displays a list of cases along with key details

2. Cases table navigation panel—enables customization of the table view, including grouping and filtering of cases

3. Case details panel—opens when a case is selected, providing additional information

The top navigation panel serves as a guide to the platform. It includes:

1. Case search bar

2. Dashboard tab

3. Cases tab

4. Add new case button

5. Emedgene applications dropdown menu to switch between Analyze and Curate

6. Help dropdown menu under a question mark icon

7. Settings dropdown menu activated by clicking the username or profile picture

The Cases table navigation panel provides several tools to help you customize your table view and manage cases. It includes the following components:

• menu Use this to narrow down the list of cases.

• menu Organize your cases by case status

• menu Choose which columns are visible in the table and define their order

• button

  Permanently delete cases currently in the trash. Use with caution, as this action cannot be undone

Welcome to Emedgene, where we unlock genomic insights for hereditary disease and streamline your tertiary analysis workflows.

So you've signed in and can't wait to get started? Here we will guide you through the platform architecture, case creation, and results review. You can dive a bit deeper by following the links and exploring manuals for the platform's applications:

• —Genomic analysis workbench, where you can accession, interpret, curate and report on your cases, while also efficiently managing the lab workflow

• —A repository for all of your organizational curated knowledge

Look around

The platform is operated from the .

By clicking on the corresponding buttons, you can enter:

• tab

• page

• menu

• dropdown menu

• dropdown menu

Create a case

To enter the flow, click on the namesake button on the . Here:

Examine the analysis results

The Case details panel provides comprehensive information about a particular case.

The Case details panel is organized into three tabs:

• Case info—displays technical, operational, and clinical information about the case

• Family tree—shows a graphical pedigree and sample details for each family member

• Activity—provides a timeline of all actions taken within the case for audit and collaboration

How to access the Case details panel

From the

Click on the row of the case you want to view. A pop-up side Case details panel will appear on the right. To close the panel, click the X icon in the top right corner.

From an

To expand the Case details panel, click the left-pointing arrow icon on the right edge of the screen. To collapse it, click the right-pointing arrow icon at the top left of the panel.

The AI-powered Emedgene platform utilizes machine learning throughout the analysis and interpretation workflow to deliver the fastest time from genomic data to decisions. We apply machine learning models that retrieve evidence-backed answers and provide exceptional decision support.

• Using automated interpretation algorithms, Emedgene generates an accurate shortlist of up to 10 potential causative variants. In a joint study of 180 solved cases with Baylor Genetics, 96% of cases were successfully solved by the algorithm. See Meng et al, , 2023 publication for more details.

• The platform is not a black box, and overlays a layer of explainable AI (XAI), presenting supporting evidence from the literature and databases which significantly reduces the time to interpret a case.

• The algorithms use a proprietary Emedgene knowledge graph which incorporates information extracted from literature with Natural Language Processing, as well as from public databases and is updated on a monthly basis.

• Dozens of additional algorithms are incorporated throughout the workflow.

Overall, the system combines AI in a highly optimized and customizable workbench, in order to automate the most time-intensive aspects of genomic analysis and research.

You can sort cases by Creation date, Due date, or Quality.

To sort cases:

A. Hover over the column header and click the up or down arrow to sort in ascending or descending order

B. Alternatively, click the column name and select Sort ascending or Sort descending from the dropdown menu

The current sort direction is indicated by a single arrow icon next to the column name.

Click on the question mark icon of the top navigation panel to open the Help dropdown menu.

From there, you can access:

• Help Center. Feeling curious? Dive right in.

• Feature requests. Submit your ideas.

• What's New. Stay updated with the latest release notes.

The Emedgene platform utilizes the Okta Identity Management solution to control user access. This improves user management, enhances access and authentication security, and allows organizations to implement single sign-on for their users.

​

Select a coverage BED file to be used in order to calculate and determine QC data for your case. This is relevant for exomes and panel cases only. Once selecting a coverage BED, an indication of availability per reference sequence will appear.

You can define a region name as an additional column within your BED. This region name will appear when reviewing regions of insufficiency in the Lab page.

Include lab level information such as lab name, machine used, reagents and expected coverage.

The Autosomal call rate field displays percentage of loci on the array for which a genotype call was successfully made, that only includes autosomes.

A high call rate indicates a high-quality sample and successful genotyping. Low call rates can signify problems with the DNA sample (poor quality or quantity) or issues during the array processing.

Displayed to three decimal places.

To open a case:

A. Hover over the corresponding row in the Cases table and click on the Open case link next to the Case ID in the first column

B. Alternatively, double-click the row

Sequencing error rate refers to the frequency at which incorrect base calls are made during sequencing process.

Blue bars represent each of these parameters per sample, while a vertical line represents a general metric across all the samples of the same case type in the account.

To streamline case review, the AI Shortlist pre-selects the list of variants likely to be causative for each case:

Most Likely Candidates

Variants that are most promising for solving the case. This list is limited to 10 top-scored variants but may include more if more than one variant is tagged per gene (suggesting compound heterozygosity). We can change the Most Likely Candidates number limit upon request.

Candidates

Several dozen highly scored variants worth considering.

The ranking of variants by AI Shortlist considers:

• SNVs

• CNVs

• SNV + CNV compound heterozygotes

• SVs

• mtDNA variants

• STRs

The AI Shortlist rates variants based on predicted variant effects, alternative allele frequency, familial segregation pattern, phenotypic match, in silico predictions, and other relevant information from scientific papers and databases.

During the case review, you can untag variants selected by the AI Shortlist or manually tag ones not selected by the AI Shortlist.

Coverage metrics for a target region defined by a QC BED file (or RefSeq coding regions if no kit is provided) included in the Sample quality section:

• Average coverage Average depth of coverage for a target region

• % Bases with coverage >10x percentage of a target region that is covered at a minimum depth of 10x

• % Bases with coverage >20x percentage of a target region that is covered at a minimum depth of 20x

Blue bars represent each of these parameters per sample, while a vertical line represents a general metric across all the samples of the same case type in the account.

The CNV overall ploidy field displays the ploidy value extracted from the CNV VCF header. If no CNV VCF file is provided, "N/A" is displayed.

Displayed to three decimal places.

The Quality status provides a quick assessment of array data reliability for each sample:

• High

  Call rate ≥ 0.99 and Log R dev ≤ 0.2

• Low If either condition is not met

• N/A

  If the QC file not available

Use the Quality status to quickly screen whether a sample meets minimal QC thresholds before starting detailed interpretation.

The Sex validation column indicates whether the biological sex inferred from genomic data matches the sex information provided during case creation. This helps identify potential sample mix-ups or metadata errors before interpretation begins.

Sex validation results:

• Pass

  Reported sex matches the estimated sex

• Fail A mismatch was detected between reported and estimated sex.

• N/A QC file not available; validation could not be performed.

Sex validation is performed by comparing the observed homozygous/heterozygous genotype ratio on the X chromosome with the expected ratios:

• <2 for females

• >2 for males

Prerequisites:

• Only high-quality SNVs from targeted regions—either kit-specific or RefSeq coding regions—are used for sex validation

• A minimum of 50 variants is required to generate a reliable result. If this threshold is not met, sex validation cannot be performed, and no result is displayed

The Sex validation column indicates whether the biological sex inferred from genomic data matches the sex information provided during case creation. This helps identify potential sample mix-ups or metadata errors before interpretation begins.

Sex validation results:

• Pass

  Reported sex matches the estimated sex

• Fail A mismatch was detected between reported and estimated sex.

• N/A QC file not available; validation could not be performed.

Percentage of reads mapped to the reference sequence.

Blue bars represent each of these parameters per sample, while a vertical line represents a general metric across all the samples of the same case type in the account.

Cases table lists key details of all genomic sequencing cases submitted by the organization.

You can customize the table by hiding, showing, rearranging fields, or adjusting column widths, except for Case ID, which is fixed as the first column and always visible.

Cases table fields

To organize cases by status, navigate to the Cases table, click on Group on the navigation panel, and select Status. To remove the grouping, select None.

Add new case page > Family tree screen > Create family tree panel

Build a pedigree via the visual tool.

It is ideal that a proband selected for case analysis is affected and has disease phenotype(s).

You can add a Father, a Mother, a Sibling, or a Child to any family member, starting with the Proband. To do this, choose their icon, then click on the Add family member button in the bottom right corner of the pedigree builder to select a family member.

More information about the pedigree symbols can be found here.

To delete a family member, choose their icon, then click on the Delete Subject button in the top right corner of the Add patient information panel.

To select variants with a particular tag, use the Filter candidates dropdown menu in the top right corner. You can select from Most Likely, Candidate, Incidental, Carrier, Not Reviewed, or any custom tags used in your organization.

For each variant on the Candidates tab, you can explore the suggested diagnosis, gene symbol, main variant details, and variant tag.

When a variant is found in a gene with no known association with a disease, the possible diagnosis cannot be indicated. Such variants are displayed under the Gene of Unknown Significance title.

All the relevant fitting a сompound heterozygous mode of inheritance are presented together. This refers to both confirmed and assumed compound heterozygosity (cases with at least one parent and singleton cases, respectively).

If you want to inspect the complete variant information, click on the variant bar to continue to the . You can visualize evidence in text or graphical format (Click on the interactive text in the top left corner: Show evidence as text or Show evidence graph to toggle between the two).

Whenever an organization is created, we automatically allocate bucket folders in AWS S3 cloud storage to it:

• Path for upload

Folder intended to store input case files.

Authorized user has view and upload privileges.

• Path for download

This folder contains a partially annotated (excluding results of proprietary algorithms) VCF file per case.

Authorized user has view and download privileges.

• Path for DRAGEN output

This folder contains DRAGEN output files.

Authorized user has view and download privileges.

To get access to your upload, download and DRAGEN output folders, you need to get a key pair consisting of an access key ID and a secret access key. , , and credentials is available for users with Manager and Manage S3 Credentials .

You can create and use up to two dynamic access keys at the same time.

When you require technical support, you have the option to generate a new key pair specifically for the troubleshooting process. After the issue has been resolved, you can delete the credentials to ensure security of your system.

The newly generated credentials will only be saved in AWS Identity and Access Management (IAM) and not in our database.

How to create a key pair

1. In Settings > Management > S3 Credentials, click on Create Access Key.

2. You can retrieve the secret access key only when you initially create the key pair. If you lose it, you have to create a new key pair. To immediately copy the secret access key to a secure location, use the Copy to clipboard button.

How to deactivate a key pair

In Settings > Management > S3 Credentials, click on Deactivate in the corresponding key pair card.

How to activate an inactive key pair

In Settings > Management > S3 Credentials, click on Activate in the corresponding key pair card.

How to delete a key pair

In Settings > Management > S3 Credentials, click on Delete in the corresponding key pair card. Only inactive key pairs can be deleted.

The Top bar in the Individual case page indicates the Case ID and current .

Options available through the Top bar:

• Change the

• Reanalyze the case

• and write interpretation notes

• Preview the

The case status reflects the current stage of case processing, either by the Emedgene platform or a genomic analyst.

You can view the current status of a case in the following locations:

• Status column in the – for a quick overview across multiple cases

• of the individual case page – for immediate visibility while reviewing a case

• panel, under Case-related activities – to track status updates and history

There are both provided by the platform and the option to create to suit your workflow.

The Lab tab shows sample and case-level quality metrics so you can check data reliability before starting interpretation.

The Lab tab includes:

• —highlights the key quality indicators, with more details provided in the subsequent sections

• —reports sequencing run technicalities

• —summarizes the data quality of the case

• —highlights quality metrics for each sample

• —displays the results of the relationship validation for each pair of samples in a family tree

• —highlights regions that may not have been adequately sequenced

The Log R Deviation (or Log R Ratio standard deviation) quantifies the variability of the the signal intensity for each SNP marker on an array, ie, noise level.

Log R deviation is one of the key metrics used to determine array sample , alongside .

Lower values indicate more consistent signal intensities. A high Log R Deviation can indicate a poor-quality sample or potential issues with CNV calling.

Displayed to three decimal places.

When available, a link appears below the sample name in the Sample quality section of the Lab tab. Clicking the link opens the detailed quality control metrics report in a new browser tab. This integration allows users to quickly assess sequencing quality and confidently interpret results—without leaving the Emedgene interface.

The Call rate field displays the percentage of loci on the array for which a genotype call was successfully made.

Call rate is one of the key metrics used to determine array sample , alongside .

A high call rate indicates a high-quality sample and successful genotyping. Low call rates can signify problems with the DNA sample (poor quality or quantity) or issues during the array processing.

Displayed to three decimal places.

The Case info tab includes the following information:

Available filters

You can filter cases using the following fields:

• Case ID

• Sample ID (Proband ID)

• Status

• Type

• Label

• Resolved: Resolved or Not resolved

• Participants

How to apply filters

How to remove a filter

How to clear all filters

In the Cases table navigation panel, click the X icon next to the Filters menu

The Ploidy column provides results from the DRAGEN Ploidy Estimator, which is designed to detect aneuploidies and determine the sex karyotype in whole genome cases.

Ploidy estimation results:

• Pass All autosomes fall within the expected ploidy range.

• Fail

  At least one autosome shows a median score outside the expected thresholds (below 0.9 or above 1.1).

  • When you hover over a failed result, the system displays which chromosomes are problematic.

• N/A

  Case type is not Whole genome or QC file not available; validation could not be performed.

The ploidy calculation uses values from the *.ploidy_estimation_metrics.csv file.

The DRAGEN sample-level quality control (QC) report is generated by the Illumina DRAGEN Bio-IT Platform and covers the entire analysis workflow—from raw sequencing reads to variant calls.

DRAGEN QC report formats

Interactive HTML summary A visual summary that includes interactive plots of key quality metrics. This report can be accessed from the Sample quality section of the Lab tab.

CSV metric files A set of detailed CSV files containing sample-level quality metrics. These files are downloadable and support in-depth review and documentation.

Prerequisites for accessing the DRAGEN QC report

To view the DRAGEN QC report within an Emedgene case, one of the following workflows must be used:

A. FASTQ case

Run a FASTQ case in Emedgene. Since the DRAGEN analysis is integrated into Emedgene secondary analysis pipeline, QC reports are automatically generated.

B. Bring your own DRAGEN (BYOD)

Run the DRAGEN analysis externally. Then upload a VCF case to Emedgene, along with the QC report metrics files. This workflow is supported for batch case upload via UI and CLI and API-based case creation. Files must be prepared as described here.

The Dashboard tab depicts an overview of the user activity on the Emedgene platform and provides a glance at key performance indicators for an organization.

Lefthand panel

• Diagnostic Yield card presents the proportion of "solved" cases out of the total number of the organization's cases of the same type.

• Status Diagram card displays the total number of the organization's submitted cases as well as the numbers of cases under each status.

• Stale Cases card highlights the cases that are stuck at one of the intermediate stages of the analysis, and are not finalized.

Righthand panel

• Network Activities panel displays a timeline of activities performed by multiple users within the organization. This log includes activity like creating a case, verifying a filter preset, changing a Case status, generating a report, and more.

Prerequisites

• Download and install node js platform via https://nodejs.org/en/download Minimum version required: 16 Upgrade existing installation: nvm install --lts

Batch upload via CLI (Command Line Interface)

1. Download the batch case create script. Replace my-domain with your Emedgene domain. Illumina cloud: my-domain.emg.illumina.com Legacy Emedgene cloud: my-domain.emedgene.com

curl https://my-domain.emg.illumina.com/v2/js/batchCasesCreator.js --output batchCasesCreator.js

1. Download the CSV template file.

node batchCasesCreator.js saveTemplateFile

1. Edit the downloaded batchCases.csv file. See CSV format requirements for more details.

2. Execute the batch cases creator as java script using the command below. Replace my-domain with your Emedgene domain and my-email with your user email. A prompt for your Emedgene password will appear, enter the password and press Enter.

node batchCasesCreator.js create -h https://my-domain.emg.illumina.com -c batchCases.csv -u my-email -l

1. In case of validation errors in the input CSV, an output CSV called batchCases_results.csv will be created in the same location with detailed error results.

2. -l will create a log file in the same location.

More information can be found by running

node batchCasesCreator.js --help

node batchCasesCreator.js create --help

The Contamination column reports whether a sample shows signs of DNA contamination, helping ensure data reliability before interpretation.

Contamination is detected using Peddy calculations, which estimate the proportion of reads that do not match the expected genotype and is based on the idr_baf score.

Contamination check results:

• N/A No data is available (older cases or when idr_baf = 0.000).

• No No contamination detected (idr_baf < 0.200).

• Unlikely Possible contamination, but evidence is weak (0.200 ≤ idr_baf < 0.241).

• Likely Contamination suspected (0.241 ≤ idr_baf < 0.300).

• Yes

  Contamination confirmed (idr_baf ≥ 0.300).

The Case quality section summarizes the data quality of the case and highlights the results of validation checks:

• Chromosome validation

  Confirms that each chromosome with at least 100 SNVs in defined enrichment kit or coding regions includes at least one high-quality variant

• gnomAD validation

  Verifies that each chromosome with at least 100 SNVs in defined enrichment kit or coding regions includes at least one variant annotated with gnomAD

• ClinVar validation

  Ensures that each chromosome with at least 100 SNV variants in defined enrichment kit or coding regions includes at least one variant annotated with ClinVar

• AI Shortlist validation

  Checks that at least one variant is tagged by the AI Shortlist.

  • This validation is not applicable if the gene list contains fewer than 50 genes

  • If your workgroup uses a higher threshold, it is reflected in the Gene list threshold field

• mtDNA reference validation Confirms that the rCRS reference is used for mitochondrial DNA

While adding a new case, you will build a pedigree and annotate each of the samples with data required for analysis (Add new case page > Family tree screen).

After the case has been created, the family tree is available in the Case details panel (righthand panel of the Cases page).

Family tree legend:

1. Icon fill color in other pedigree members indicates the presence or absence of the proband's phenotypes in a present sample (regardless of the potential presence of additional unrelated phenotypes):

* Filled - the individual is affected by all of the proband's phenotypes;
* Half-filled - the individual is affected by some of the proband's phenotypes;
* Empty - the individual is not affected by any of the proband's phenotypes.

2. Icon color intensity denotes whether sample files have been uploaded for the particular individual:

* Full color - the sample has files loaded in the case;
* Faded color - no sample files are available.

3. Icon line type indicates whether the sample is considered or excluded during analysis (relevant to samples with uploaded files only):

* Solid - the sample is included in the analysis;
* Dashed - the sample is ignored by Inheritance filters and the AI Shortlist algorithm, but you still can explore its genotypes.\
  ​

​

Add new case page > Case info screen > Select genes list

Select gene list

You can limit analysis to a gene list in the platform while creating a case. Choose between:

1. All genes

No limitation of the analysis.

2. Existing gene list

Select one of the previously added gene lists from a dropdown list.

3. Create a new gene list

Generate a new virtual panel: add a List title and then add all the gene symbols one by one (Selection mode) or in a batch (Batch mode).

A new gene list can be comprised from a combination of configured gene lists and/or individual genes.

A gene list can by configured to hold up to 10,000 genes.

A new gene list can be created by combining configured gene lists and/or individual genes. Each gene list can be configured to contain up to 10,000 genes.

Selection mode

For each gene please follow the steps described below: Enter a gene symbol in the search box in the right panel (Candidate Genes) and select a matching symbol from a dropdown menu.

Batch mode

After selecting batch mode, paste a list of comma-separated gene symbols in the search box in the right panel (Candidate Genes).

Gene list modes

You can choose between two different modes of a gene list feature:

1. In silico panel

Selected by default.

AI Shortlist is limited to the selected gene panel, no variants in other genes are considered in the results. If this in silico panel is used for analysis of exome or genome data, the gene restriction may be lifted during manual analysis to "open-up" the entire exome or genome for analysis.

2. Boosted genes

Analysis is performed for variants in all the genes. Variants in the targeted genes get upgraded scores during prioritization by the AI Shortlist algorithm.

If you're comfortable with scripting and API usage, you can upload multiple cases at once using those methods. But if you're not a technical expert, don't worry. There is a user-friendly alternative available—importing a CSV file directly through the user interface.

Please follow the steps as described below.

1. Prepare a CSV file

CSV (Comma-Separated Values) is a simple file format used to store data in tabular form. A row represents a sample, and a column represents a data field.

Start by downloading a CSV template with an example line and mandatory and non-mandatory fields from the Add new case page set to Batch mode (see step 2). Fill the file with your data according to CSV format requirements.

2. Upload a CSV file

1. Click on the + New case button on the top navigation panel.

2. Click on the Switch to batch button in the top right corner. You'll be directed to the Select file page of the Batch upload flow. Note: Here you can download a CSV template in the valid format.

3. Drag and drop a CSV file into the box or upload it from the file explorer. Wait for file upload and validation to finish.

3. Review file validation results

After validation is complete, you will be directed to the Batch validation page. It features validation results details for you to review:

• File name,

• Number of rows in the file,

• Number of cases to be created

• Number of errors found,

• Status message

  • If no errors were detected, a success message will be displayed

  • If any errors were detected, an error message will be displayed.

    You will be given the option to download a file with error details to help you diagnose and correct any issues with the data. Once you've corrected the CSV file, reupload it.

4. Create cases

1. Click on Create. A progress bar will appear on the right as the cases are created (Cases creation page).

2. If the cases have been created successfully, the Cases summary page will display the total number of cases that were created.

3. If there were any errors during the batch case creation process, the Cases summary page will display a table indicating the number of cases that were successfully created and the number of cases that failed.

You will have the option to download a CSV file containing two additional columns: Errors and Case ID. The Errors column will contain error messages for samples where case creation failed, while the Case ID column will contain the Case ID of a successfully created case for the lines where case creation was successful.

Add new case page > Family tree screen > Add patient information panel > Patient info section

1. Fill in the boxes:

1. Sex (*)

Options: Male, Female, Unknown.

2. Relationship

Indicates the family relationship of a subject to the Proband automatically inferred from the pedigree. Options: Father, Mother, Sibling, Child, Other.

3. Date of Birth

Expected format: mm/dd/yyyy.

4. Ignore Sample

Mark the checkbox if you want to exclude the sample from the AI Shortlist analysis and Inheritance filters while preserving genotype data.

5. Add Proband's phenotypes

If a sample shares some phenotypes with the Proband, you can copy them by checking this box. Proband's phenotypes will appear in a newly created Related Phenotypes section. To remove any of the proband's phenotypes not observed in a current individual, click the ☒ button next to the HPO term in the Related Phenotypes section.

6. Unrelated Phenotypes

Phenotypes not shared with a Proband. They can be added one by one (Selection mode) or in batch (Batch mode).

Selection mode

Please follow the steps described below for each phenotype:

• Enter an HPO term (e.g., Hypoplasia of the ulna), an HPO ID (e.g., HP:0003022), or a descriptive phenotype name (e.g., Underdeveloped ulna) in the search box;

• Select a matching term from a dropdown menu and press Complete after you've added all the terms.

Batch mode

Paste a list of comma-separated HPO terms or HPO IDs in the search box and press Complete.

2. Click on Complete once all the information is added.

You can implement different combinations of Presets to be used for different case types (i.e. Presets for exome may be different from Presets for genome) as defined by your SOPs to further streamline case review.

The combination of Presets is referred to as a Preset group.

Select a Preset group to display in the case

Preset group selection is available in the Case info screen of the Add new case flow while creating or editing a case.

Where can I manage Preset groups?

To manage filter Preset groups, navigate to Settings > Organization Settings > Lab Workflow:

Preset groups

From here, you can create (from Presets/from a JSON file, edit, hide/unhide and download Preset groups as needed.

Default Preset group

Here, you can set a Preset group as default, so it will be used unless another Preset group is selected during case creation.

The user can enter a specific case from the Cases tab by clicking Full details in the corresponding row of the case table.

The Individual case page includes:

1. Top bar—displays a Case ID and Case status and includes Case interpretation, Edit case info, and Report preview buttons

2. Candidates tab—highlights a shortlist of variants, suggested to be reviewed first - Most Likely Candidates and Candidates

3. Lab tab—illustrates quality metrics for the sequenced samples

4. Genome view—provides an interactive overview of genomic structure, ideal for analyzing CNV and ROH/LOH events

5. Analysis tools tab—provides numerous customizable filters to help you explore the total list of genetic variants in compliance with your organization's standard case review process. You can export shortlisted variants in .xlsx format

6. Versions tab—documents versions of all the resources used during case analysis

Add new case page > Family tree screen > Add patient information panel > Add sample section

You can choose one of the following options:

1. Existing sample - pick one of the samples already loaded on the platform

2. Upload New Sample - upload files from your PC and enter sample name

3. Choose from storage - choose files from your cloud storage and enter sample name

4. No sample - postpone uploading files but proceed with case creation or skip uploading files for family members other than Proband

The table view is customizable:

• Columns can be reordered by drag-and-drop

• Any column can be shown or hidden by selecting the columns in the Show/Hide columns menu in the top right corner of the page

• You can choose between comfort and compact view by clicking the corresponding button

All modifications are automatically saved for each individual user and retained until new changes are made.

Sample-level DRAGEN QC metric files for all samples in a case can be downloaded by clicking the download icon next to the Sample quality section title.

For NGS cases, the report includes coverage and mapping statistics.

For array cases, metrics include array QC values such as call rate, autosomal call rate, and Log R dev.

How to select columns to be displayed

A. Show or hide columns via the Fields menu

B. Hide a column directly from the Cases table

How to change column order

You can reorder columns in three ways.

A. Drag and drop the column

B. Reorder columns via the Fields menu

C. Move a column using a dropdown menu

How to adjust column width

> Case info screen > Select case type

Select the case type in order to define the proper analysis of your case.

Select the region of interest in order to filter-in only variants located within the proper regions.

Regional information is used to process genomic data in a variety of ways. Regional information influences the variants presented in gene panels, exomes, and genomes, variant quality and variant annotations.

Regardless of the case type, you can select any region of interest.

When selecting a Custom BED as you region of interest, you must select a specific BED file that is configured in your organization.

Case type table:

Case type + regions of interest BEDs are applied as follows:

1. Research Genome + No Region of interest: There is no intersection and all variants are viewable (Note: data pipeline time will increase, and intergenic variants have very limited annotations).

2. Whole Genome + Full genes: A wide range of genomic regions BED file. It contains:

   • "RefSeq ALL" transcripts and "GENCODE" full genes regions with 5Kbp upstream and 5Kbp downstream

   • Within this range, all “Clinical Regions” are included

   • All dosage regions (HI/TS sig level 1, 2 or 3)

3. Exome + Clinical regions: A comprehensive bed file that includes every clinically relevant region. The following are included:

   • “RefSeq Curated” and “GENCODE” regions with flanking areas of 50bp from each side 5UTR and 3UTR region for protein coding genes (based on RefSeq)

   • OMIM disease-related RNA genes (50bp flanking)

   • All Clinvar Pathogenic variants regions (flanking 50bp)

   • Promoters region (EPDnew human version 006, flanking 50bp)

   • Known STR regions (Dragen 4.0 specification file)

   • All microRNA genes (flanking 50bp based on HGNC)

   • Full mtDNA region

4. Custom Panel+ Custom BED: You can select any existing BED file configured in your organization to restrict according to it's regions.

BED files

While creating a new case, you can choose whether to include secondary findings for the proband. This option is available on the Family Tree screen → Create family tree panel → Show Secondary Findings.

Secondary findings are genetic variants that are not related to the primary indication for testing but may have important medical implications. These variants are automatically assigned the Incidental tag when they meet American College of Medical Genetics and Genomics (ACMG)-defined criteria for reportable secondary findings.

Tagging criteria

A variant is automatically tagged as a secondary finding if it meets all of the following criteria:

1. Classification: Previously classified as pathogenic or likely pathogenic in ClinVar or Curate variant databases

2. Zygosity: Heterozygous or homozygous (only homozygous for the HFE gene)

3. Allele frequency: Less than 5%

4. Read depth: 10× or higher

5. Variant quality: Any value except LOW

6. Affected gene: Listed in the ACMG SF v3.2 or 3.3 medically actionable gene list for reporting secondary findings in clinical exome and genome sequencing (PMID: 37347242, 40568962)

ACMG SF v3.2 gene list

ACTA2, ACTC1, ACVRL1, APC, APOB, ATP7B, BAG3, BMPR1A, BRCA1, BRCA2, BTD, CACNA1S, CALM1, CALM2, CALM3, CASQ2, COL3A1, DES, DSC2, DSG2, DSP, ENG, FBN1, FLNC, GAA, GLA, HFE, HNF1A, KCNH2, KCNQ1, LDLR, LMNA, MAX, MEN1, MLH1, MSH2, MSH6, MUTYH, MYBPC3, MYH11, MYH7, MYL2, MYL3, NF2, OTC, PALB2, PCSK9, PKP2, PMS2, PRKAG2, PTEN, RB1, RBM20, RET, RPE65, RYR1, RYR2, SCN5A, SDHAF2, SDHB, SDHC, SDHD, SMAD3, SMAD4, STK11, TGFBR1, TGFBR2, TMEM127, TMEM43, TNNC1, TNNI3, TNNT2, TP53, TPM1, TRDN, TSC1, TSC2, TTN, TTR, VHL, WT1.

ACMG SF v3.3 (2025 release; requires pipeline v100.39.0+)

Includes all v3.2 genes plus newly added genes:

• PLN

• ABCD1

• CYP27A1

This brings the total to 84 reportable genes.

You have the flexibility to manage Case labels at any time: create, add, or remove them directly in the .

Adding labels to a case provides the ability to quickly mark cases for specific use cases and an easy filtering of cases sub set in the cases page.

The Sample quality section in the Lab tab gives you a quick view of the reliability of sequencing or array data used in your case.

For eligible cases, users can review the results of : interactive DRAGEN report and DRAGEN QC metric files.

The metrics displayed in the Sample quality section and their underlying calculation vary depending on the case type:

When creating a new case, the first step is to select the sample input type. This determines how your data will be processed and which quality metrics will be available later in the analysis.

You can choose from the following supported formats:

• FASTQ Accepted file types: .fastq.gz, .fq.gz, .bam, .cram Use this option if you want the platform to perform secondary analysis and variant calling.

• Project VCF Accepted file types: .pvcf, .vcf, .vcf.gz, .pvcf.gz Use when working with a joint VCF file containing multiple samples.

• VCF Accepted file types: .vcf, .vcf.gz, .targeted.json, .gt_sample_summary.json Use for cases where variants have already been called externally, or for array inputs with accompanying JSON files.

• Array Supported with DRAGEN Array v1.2 VCF and quality files. Use this option for cytogenetic array cases. Array results can be visualized in Genome View and the IGV tab, and sample-level quality metrics are available under the Lab tab.

The formatting of variant table rows provides visual cues about the variant status for the current user within a specific case.

The Pedigree section displays relatedness metrics and the results of relationship validation for each pair of samples in the family tree.

Included metrics

Relatedness coefficient (observed)

Shows the observed coefficient of relatedness between sample pairs. The expected coefficient is available via hover tooltip for quick comparison.

IBS0

Identity by state 0—a number of genomic loci where two individuals share zero alleles. This occurs when the two individuals are opposite homozygotes for a biallelic SNP.

This metric is calculated across a set of biallelic SNPs and is inversely related to the degree of genetic similarity between the individuals. A low IBS0 count suggests a higher degree of overall genetic similarity, but it is an indirect and limited measure of genetic relatedness that requires interpretation alongside other metrics.

Relationship validation result

Summarizes the outcome of the relationship validation, confirming whether the observed data aligns with the expected pedigree structure.

Relationship validation calculation

Relationship validation is done by based on:

• Relatedness coefficient (𝑟)—a measure of how much two individuals share alleles from a common ancestor, indicating the probability that alleles at the same genome location are identical by descent

• IBS0 (Identity by state 0)—a number of genomic loci where two individuals share zero alleles, ie, they are opposite homozygotes

• IBS2 (Identity by state 2)—a number of genomic loci where two individuals share two alleles, meaning they have the exact same genotype

Peddy takes the inferred relationships from the genetic data and cross-references them against the declared relationships. For every pair of individuals in a cohort, Peddy calculates a coefficient of relatedness from the genotypes observed at the sampled sites.

For each possible pair of samples in a pedigree, the expected relatedness coefficient based on declared family relation is compared with the observed relatedness coefficient (𝑟). IBS0 value helps to differentiate between sibling and parent–child relationships, both expected to have ~50% relatedness coefficient (see table).

To directly import files from your own storage, link it to an organization's storage in Emedgene.

How to link your storage to Emedgene:

How to edit storage information:

Click Manage on the right to the storage details.

How to remove a link to storage:

Click Delete on the right to the storage details.

How to get your ICA credentials:

To connect ICA:

The Candidates tab displays all tagged variants, whether tagged by the AI Shortlist or manually by a user.

Variant tagging by the AI Shortlist

Variants are automatically tagged as:

• Most Likely Candidates and Candidates

  Variants prioritized by the AI Shortlist

• Secondary findings

  Variants that meet ACMG-defined criteria for secondary findings and automatically tagged with an Incidental tag (if enabled)

• Carrier variants

  Variants identified by the carrier analysis pipeline (if enabled)

Assigning variant tags during review

During review in the Candidates tab, additional tags can be applied to a variant alongside the original automatic tag.

The Candidates tab presents:

Most Likely Candidates and Candidates

A set of the most promising variants based on scores calculated by the AI Shortlist. These variants are initially tagged by the system.

Variant types assessed:

• SNVs and indels

• CNVs

• SVs

• mtDNA variants

• STRs

Incidental (Secondary)*

Secondary findings are variants that are automatically assigned the Incidental tag when they meet the criteria for secondary findings as defined by the American College of Medical Genetics and Genomics (ACMG).

Tagging is applied only when the Secondary findings checkbox is selected during case creation.

Tagging criteria

A variant is automatically tagged as an incidental (secondary) finding if it meets all of the following criteria:

1. Classification: Previously classified as pathogenic or likely pathogenic in ClinVar or Curate variant databases

2. Zygosity: Heterozygous or homozygous (only homozygous for the HFE gene)

3. Allele frequency: Less than 5%

4. Read depth: 10× or higher

5. Variant quality: Any value but LOW

6. Affected gene: Listed in the ACMG SF v3.2 medically actionable gene list for reporting secondary findings in clinical exome and genome sequencing (PMID: 37347242)

ACMG SF v3.2 gene list

ACTA2, ACTC1, ACVRL1, APC, APOB, ATP7B, BAG3, BMPR1A, BRCA1, BRCA2, BTD, CACNA1S, CALM1, CALM2, CALM3, CASQ2, COL3A1, DES, DSC2, DSG2, DSP, ENG, FBN1, FLNC, GAA, GLA, HFE, HNF1A, KCNH2, KCNQ1, LDLR, LMNA, MAX, MEN1, MLH1, MSH2, MSH6, MUTYH, MYBPC3, MYH11, MYH7, MYL2, MYL3, NF2, OTC, PALB2, PCSK9, PKP2, PMS2, PRKAG2, PTEN, RB1, RBM20, RET, RPE65, RYR1, RYR2, SCN5A, SDHAF2, SDHB, SDHC, SDHD, SMAD3, SMAD4, STK11, TGFBR1, TGFBR2, TMEM127, TMEM43, TNNC1, TNNI3, TNNT2, TP53, TPM1, TRDN, TSC1, TSC2, TTN, TTR, VHL, WT1.

Carrier

Variants identified by the Carrier analysis pipeline. Carrier variants are automatically tagged only if you've selected the Carrier Analysis checkbox while creating a case. Analysis requirements and a list of targeted regions are specified by the organization's manager. This Carrier analysis flow is implemented by request.

In Report and other custom variant tags

Variants that were manually selected to be reported.

The ethnicities of the proband's mother and father can be specified during the process of UI or API case creation. Please refer to the following list of supported ethnicities.

The Family tree tab includes the following information:

• Pedigree diagram. Pedigree legend can be found here.

• Sample details for each family member:

  • Phenotypes. For family members other than the test subject, phenotypes are categorized as:

    • Related—directly match one of the proband’s phenotypes

    • Unrelated—do not match any of the proband’s phenotypes

  • Medical Condition – Indicates whether the individual is considered Healthy or Affected in the case

  • Sex. Specified by the user

  • Age. Automatically calculated in years based on the provided date of birth

  • Maternal and Paternal ethnicity—ethnic background of the proband’s parents

  • BAM file location. Shown where relevant

Before you proceed to this article, make sure you understand data storage management basics.

Update Azure Blob Storage Credentials

In Settings > Management Tab, add or edit the required credentials: CLIENT_ID, CLIENT_SECRET, TENANT_ID, and ACCOUNT_URL.

See the table below to learn where to look for them in your Azure account.

Blob Integration Setup

Create an App registration

1. In Microsoft Entra ID, click on App registrations.

1. Select New registration.

2. Fill the name of the application & press "register."

3. You got to the registered app page: (CLIENT_ID / TENANT_ID) From this you can retrieve: Application ID and Tenant ID. Both are marked in the screenshot.

1. Press "Certificates & secrets"

2. Press on "New Client secret"

1. Fill the "Description" and change expires to 12 months. (or according to your organization policy), than press "Add"

8. Get the CLIENT_SECRET from this page.

1. Give this App registration roles and read access to the relevant Blob.

Azure Blob configuration

1. Go to Azure Storage accounts

1. Get into the relevant Storage account

1. Press on "containers"

1. Press on the relevant container

2. Press on "Properties"

3. Copy the ACCOUNT_URL

For Internal support:

Errors for bad connections can be found in CloudWatch on particular FRY log stream

Search for: BlobApi, BlobFs, azure.

Google Cloud Storage Credentials update procedure

How to get the client credentials?

1. Go to the google cloud Console.

2. Navigate to IAM & Admin - In the left sidebar, go to IAM & Admin > Service Accounts.

1. Create a New Service Account: Click on the "Create Service Account" button at the top.

1. Fill in the Service Account Details:

   • Service account name: Give your service account a name.

   • Service account ID: This will be automatically generated based on the name.

   • Description: Optionally, provide a description for the service account.

   Click "Create and Continue".

   example:

1. Assign Roles to the Service Account:

   • In the Grant this service account access to project step, you’ll assign the necessary roles.

   • Grant these role:

     • "storage object viewer" (read-only access)

2. Create the Service Account:

   • After assigning the roles, click "Done".

3. Generate and Download a Key:

   • Find your newly created service account, click the three dots on the right, and select "Manage Keys".

   • Click Add Key > Create New Key and choose the JSON format.

   • Download the key and store it securely, as it is used for authentication in your code or applications.

4. Encode the key in base 64:

   • use python function: put this function and your json (here named json_file.json) in the same directory and run.\

   • save the output printed.

Add the storage provider to Emedgene platform:

• Add the above 3 values into the appropriate fields:

  • Client_credentials_base64: pasting the output of 8.

  • Bucket: the bucket name.

  • Path: for default, fill with / else, put your path in the bucket. Seperate directories with /

CORS - Visualisation

1. Download and install the Google Cloud SDK from the Google Cloud SDK Install page.

2. Select Your Platform (Windows, macOS, or Linux), download and run.

3. Initialize and Authenticate with Google Cloud: In the Cloud SDK Shell/terminal, run: gcloud init This will open a browser window to authenticate your Google account. Follow the instructions to log in and select your project.

4. Set CORS Configuration via gcloud: Create a JSON file (cors.json) on your machine with the CORS rules. Example\ it should look like:

notice:

• origin: if using Illumina cloud:

  https://host_name.emg.illumina.com

  else, Emedgene cloud:

  https://host_name.emedgene.com

1. Apply CORS Configuration to Your Bucket: run the next command. gcloud storage buckets update gs://your-bucket-name --cors-file=cors.json

2. Verify the CORS Configuration: gcloud storage buckets describe gs://your-bucket-name

Log in to Emedgene and navigate to Settings in the upper right-hand corner of the page.

Click on the Management tab and then on Add Storage.

Choose Illumina BaseSpace storage type.

Fill Client Key, Client Secret and App Token as provided from BaseSpace (a description on how to get this information is provided below) and click Add storage to complete the setup.

Via Command Line

Prerequisite

Install BaseSpace CLI (Command Line Interface)

Follow the instructions on the if needed. Be aware of the Basespace Regional Instance you are working on (us, euc1, aps2, euw2)

Authenticate

On BSSH, login to the workgroup you want to connect as the storage.

Once the BaseSpace CLI is installed, run the authentication command in the terminal.

The command will direct you to a link which requires to login.

After the authentication was completed successfully, find the access token in the config file.

The result should look like -

Populate the App_token with the accessToken value, and Server with the apiServer URL from the BSSH config file.

Client_key will be displayed in subsequent menus, so a descriptive name such as the workgroup name can be used.

Client_secret is unused when the App_token is available and can be set to "x".

Via BaseSpace Developer Portal

Go to the BaseSpace and login. Be aware of the Basespace Regional Instance you are working on (us, , , )

Go to My Apps and click Create a new Application.

Fill details for the application and click on create an application.

Fill details and press save.

You will need to fill all the fields that it requested, please add “NA” to them.

Go to My Apps and click on your new app. Then go to the credentials tab.

You will find the Client ID (Client Key), Client Secret and App Token to enter to Emedgene platform.

Adding BSSH account to your Emedgene account

1. Log in into the desired Emedgene organization.

2. Go to Settings

3. Go to Management tab

4. Click on Add Storage

5. Select BaseSpace:

1. Add the information from your “Credentials” of the App previously created in BSSH.

If you have an Enterprise account and you would like Emedgene-managed DRAGEN solution to save the DRAGEN output files in your own bucket, reach out to .

Emedgene directly from your AWS S3 bucket. In order to do it, you should enable for the Emedgene application URLs.

This feature is only related to saving Dragen output files in your own bucket when using Dragen through Emedgene (without ICA).

If you are looking to:

• Import data from AWS S3 to Emedgene go to

• Integrating any data storage to Emedgene go to

• Download any data from Emedgene go to

Bring Your Own Bucket

Bring Your Own Bucket, also known as BYOK, enables you to control your DRAGEN file outputs.

Emedgene-managed DRAGEN solution saves the DRAGEN output files in a detected AWS S3 bucket that you have access to using your .

However, if you have an Enterprise account and you would like Emedgene-managed DRAGEN solution to save the DRAGEN output files in your own bucket, reach out to [email protected] and follow this steps:

1. Create an AWS bucket

Emedgene requires access to the root folder, which means a dedicated bucket might be appropriated.

2. Edit Bucket policy

Bucket policy should allow Emedgene user access to the bucket.

Example bucket policy:

3. Allow illumina.com and emedgene.com for CORS

Emedgene directly from your AWS S3 bucket. In order to do it, you should enable for the Emedgene application URLs.

Example CORS policy:

4. Test and validate the configuration with Illumina support

We will require to run a case and validate the managed DRAGEN pipeline finish successfully and all features are available in the platform.

Managing AWS S3 Lifecycle policy

If a customer enables an AWS S3 Lifecycle policy in order to archive or change the S3 tiers for different files, they might create an adverse effect on the platform.

In some cases, you may need to record variants that were not included in the uploaded VCF or not called from FASTQ data. This is particularly useful when:

• You are complementing NGS results with findings from other genetic tests (e.g., long-read sequencing, optical mapping, CGH, SNP array, karyotyping/FISH, repeat-primed PCR, MLPA, Southern blot, etc.)

• You wish to report on adjacent CNV calls as a single CNV event.

• You wish to report a set of adjacent variants together as a single multi-nucleotide variant (MNV).

Manually adding variants ensures that all relevant findings are visible in the case review and can be considered during interpretation.

Currently supported variant types: SNV, CNV, UPD, ROH, and STR.

To manually add a variant:

1. Open the Analysis Tools tab.

2. Click the plus (+) button in the top-right corner.

1. In the Manually Add Variant window, select the variant type: SNV, CNV, UPD, ROH, or STR.

2. Fill in the details based on the selected type:

1. Click on Create Variant to add it to the case.

Viewing manually added variants

• Manually added variants have a blue frame and are clearly marked with the label “Manually added variant” on the Variant page.

• These variants differ from pipeline-called variants:

  • Quality and Visualization sections are not available.

  • Population Statistics are not shown.

  • Automatic ACMG scoring is not applied, but you can still manually add ACMG tags, interpretation notes, and classifications.

Sorting and formatting notes

• STR variants that are added manually do not fully align with the pipeline-called STR format. For example, variant length is not displayed.

• Manually added variants cannot be sorted by columns that do not apply, such as AI Rank.

Filtering manually added variants

To view only the variants you have added manually:

• In the Evidence & Tags Filters section, select Manually added variants.

This helps you focus specifically on variants that were entered outside of the automated pipeline.

In the tab under Settings, you can tailor how case statuses appear and function to better align with your workflow:

• Create custom case statuses to reflect your team's specific processes

• Remove unused statuses to keep the list clean and relevant. Only statuses that are not currently assigned to any case can be removed.

• Rearrange the order of statuses by drag-and-drop to match your preferred case interpretation flow. The updated order is refelected in:

  • The Status field dropdown in the Cases table

  • The top bar of the individual case page

Summary dashboard provides a quick overview of key quality indicators at both the case and sample levels.

Included metrics:

• Displays the overall case quality status

• Reflects sample quality status

• Evaluation kit

  Specifies the QC BED kit used to evaluate coverage depth and breadth. If no kit is specified at analysis launch, NCBI RefSeqGene is used as the default reference

• Custom gene coverage Indicates whether the coverage of genes in the selected panel meets the expected threshold, as defined by the QC BED

• Displays the results of relationship validation, confirming whether the submitted pedigree aligns with genetic data

When creating Emedgene cases that start from VCF, you can create a browsable DRAGEN QC report from the DRAGEN metrics files. Due to security restrictions, CSV files are not directly ingested, but they can be included when packaged in a TAR file.

1. Navigate to local directory containing metrics files for a specific sample.

2. Define sample name as a variable samplename="NA12878".

3. Combine the find and tar commands to package the files into a tar.gz file with the following extension *.metrics.tar.gz. Command to find files matching the required patterns:

find . \( -name "*.csv" -o -name "*.tsv" -o -name "*.counts" -o -name "*.counts.gz" -o -name "*.counts.gc-corrected" -o -name "*.counts.gc-corrected.gz" -o -name "*.ploidy.vcf" -o -name "*.repeats.vcf" -o -name "*.ploidy.vcf.gz" -o -name "*.repeats.vcf.gz" \) | xargs tar -czf "${samplename}.metrics.tar.gz"

1. Upload the metrics.tar.gz file to the storage location used for creating cases.

2. Add metrics.tar.gz to case creation API JSON payload using the corresponding storage ID. Ensure that if the extension is not contained in the filename (e.g. files from BaseSpace) that "sample_type": "dragen-metrics" is set within the JSON payload.

{
    "test_data":
    {
        "consanguinity": false,
        "inheritance_modes":
        [],
        "sequence_info":
        {},
        "type": "Whole Genome",
        "notes": "",
        "samples":
        [
            {
                "bam_location": "",
                "fastq": "NA12878-PCRF450-1",
                "status": "uploaded",
                "directoryPath": "",
                "sampleFiles":
                [
                    {
                        "filename": "NA12878-PCRF450-1.metrics.tar.gz",
                        "sample_type": "dragen-metrics",
                        "path": "/analysis_output/demo_data_germline_v4_3_6_v2-DRAGEN_Germline_Whole_Genome_4-3-6-v2-75b081e8-a8aa-433e-862b-a20d2d65e492/NA12878-PCRF450-1/NA12878-PCRF450-1.metrics.tar.gz",
                        "size": 0,
                        "storage_id": 420,
                        "status": "uploaded",
                        "vcf_column_name": "NA12878-PCRF450-1",
                        "vcf_column_names":
                        [
                            "NA12878-PCRF450-1"
                        ],
                        "loadingSample": false
                    },
                    {
                        "filename": "NA12878-PCRF450-1.hard-filtered.vcf.gz",
                        "sample_type": "vcf",
                        "path": "/analysis_output/demo_data_germline_v4_3_6_v2-DRAGEN_Germline_Whole_Genome_4-3-6-v2-75b081e8-a8aa-433e-862b-a20d2d65e492/NA12878-PCRF450-1/NA12878-PCRF450-1.hard-filtered.vcf.gz",
                        "size": 0,
                        "storage_id": 420,
                        "status": "uploaded",
                        "vcf_column_name": "NA12878-PCRF450-1",
                        "vcf_column_names":
                        [
                            "NA12878-PCRF450-1"
                        ],
                        "loadingSample": false
                    }
                ],
                "storage_id": 420,
                "sampleType": "vcf"
            }
        ],
        "sample_type": "vcf",
        "patients":
        {
            "proband":
            {
                "fastq_sample": "NA12878-PCRF450-1",
                "gender": "Male",
                "healthy": false,
                "relationship": "Test Subject",
                "notes": "",
                "phenotypes":
                [
                    {
                        "id": "phenotypes/EMG_PHENOTYPE_0001324",
                        "name": "Muscle weakness"
                    }
                ],
                "detailed_ethnicity":
                {
                    "maternal":
                    [],
                    "paternal":
                    []
                },
                "zygosity": "",
                "quality": "",
                "dead": false,
                "ignore": false,
                "id": "proband"
            },
            "other":
            []
        },
        "diseases":
        [],
        "disease_penetrance": 100,
        "disease_severity": "",
        "boostGenes": false,
        "selected_preset_set": "",
        "incidental_findings": null,
        "labels":
        [],
        "gene_list":
        {
            "type": "all",
            "id": 1,
            "visible": false
        }
    },
    "should_upload": false,
    "sharing_level": 0
}

1. DRAGEN report link is then available once your case has been delivered.

The Activity tab offers a timeline of case actions and enables users to leave comments. It supports key functions that enhance case management and review:

• Traceability—Maintains a complete, time-stamped history of case actions

• Error recovery—Allows users to identify and trace changes, such as variant edits or disease associations, made in error

• Real-time collaboration – Enables teams to monitor each other’s updates as they happen, ensuring transparency

• Training & quality control – Helps identify patterns in variant interpretation and supports consistent application of evidence criteria

• Audit compliance – Supports clinical and laboratory documentation standards (e.g., CAP/CLIA) by providing a verifiable action history

Each activity entry includes:

• Timestamp (date + time)

• User name of the person who performed the action

• Action description

Activity logs are kept for at least six years for full traceability.

The Activity tab logs the following actions:

Viewing activity logs

In the Cases table, the Activity tab within the Case details panel displays only comments and case-related activities. To view the full list of all activities, open the Case details panel directly from the individual case page.

The Emedgene platform is divided into two applications:

• Analyze—genomic analysis workbench

• Curate—the knowledge management system

To switch from Analyze to Curate:

Go to the nine-dot app launcher icon located on the top navigation panel and select Curate from the dropdown menu.

To switch from Curate to Analyze:

Go to the nine-dot app launcher icon located on the Curate navigation panel and select Analyze from the dropdown menu.

Sequencing lab information section reports sequencing run technicalities as indicated during case creation:

• Lab

• Instrument

• Reagents

• Kit type

• Expected coverage

• Protocol

The Add New Case flow guides you step by step through creating and submitting a case for analysis on the Emedgene platform. Here you can define your family structure, input patient details, select case type, apply gene lists and presets, and confirm case information before analysis begins.

Step 1: Start a new case

1. Click on the Add New Case button on the top navigation panel.

2. At the Select sample type page, choose the file type for your case analysis (FASTQ, gVCF, VCF, or Array).

3. Click Next to proceed.

1. In the Create family tree panel (left):

   • Build a pedigree using the visual tool;

   • Add Clinical Notes (optional) in a free text panel. In this section, you can record additional clinical information that does not fall under the other categories or provide further details that can give context and help solve the case.

   • You have an option to upload a file that includes description of the clinical presentation (.pdf, .xls, .txt, .doc, .jpeg, .jpg formats are supported). HPO terms for Phenotypes and Diseases are extracted from the files and can be added to Proband's Phenotypes in Patient info section.

   • You may select suspected Inheritance mode(s). This is for the case record and won't be used during analysis.

   • Select whether you want Secondary findings in Proband to appear in the AI Shortlist analysis results.

Step 2: Build the family tree and add patient information

The page is divided into two panels: Create family tree (left) and Add patient information (right).

Create family tree (left)

1. Use the visual tool to build the pedigree.

2. Add Clinical Notes (optional) in free text, or upload a clinical presentation file (.pdf, .xls, .txt, .doc, .jpeg, .jpg).

   1. HPO terms for phenotypes and diseases will be extracted and can be linked to the proband.

3. Select suspected Inheritance mode(s) (for record only; not used in the analysis).

4. Decide whether to include Secondary findings in the proband for the AI Shortlist (checkbox).

Add patient information (right)

For each family member:

1. Add a sample (use a unique file path unless reusing samples).

2. Fill in a sample name (for VCF input, this must match the header in the file).

3. Complete the required patient details.

Click Next to proceed to the Case info screen.

Step 3: Case info screen

Here you define how the analysis will run:

1. Case type: Choose Array, Custom Panel, Exome, Whole Genome, or Other.

   • For Exome cases, variants outside exons ±50 bp are automatically filtered.

2. Carrier Analysis: Optional checkbox. Requires a targeted gene list.

3. Sequencing Information:

   1. Select an enrichment kit (if applicable) or "No kit".

   2. If provided, kit details (Lab, Machine, Reagents, Expected coverage) will be used to compare coverage depth and breadth.

   3. If no kit is provided, RefSeq coding regions will be used as reference.

4. Gene list options:

   1. All genes

   2. Phenotype-based genes

   3. Existing gene list

   4. Create a new gene list

      • You may now combine multiple gene lists into one, or add specific genes to an existing list during case creation. The merged list behaves like any other list in the platform.

5. Preset group: Select the Preset group appropriate for this case type.

   • If none is selected, the default Preset group is applied automatically (marked as default).

6. Consent: Confirm subject consent for extended sharing.

Additional case info (optional):

• Indication for testing (free text).

• Labels (choose from predefined organization labels; these cannot be changed later).

At the Summary stage, confirm case type, gene list, and other selections.

Step 4: Done screen

After creation:

• A Case ID is displayed.

• Add participants to the case so colleagues receive notifications on case status changes.

You can use the Case search tab in the top bar to search for cases by the Case ID or Proband ID.

By using the multi-selection mode, you can speed up review by applying actions to multiple variants at once. This makes it easier to apply tags, assign pathogenicity, and review status without handling each variant individually.

Multi-selection of variants

1. Hover over a variant to reveal a checkbox at the start of the line;

2. Selecting a checkbox activates the Multi-select actions bar, replacing the Search bar.

3. Checkboxes appear for all variants in the current view.

4. Select variants individually or use the Select all checkbox.

   Important: Select all applies only to variants currently displayed on the page, not all variants matching your filters.

Bulk actions:

1. View/ Un-view variants

Change the review status for multiple variants at once:

1. Select the variants of interest.

2. In the Multi-select actions bar, click the Viewed icon.

3. Choose Viewed or Un-viewed.

2. Assign/ Remove tags

Assign or manage tags across multiple variants at once:

Assign tags

1. Select the variants of interest.

2. Click the Tag icon in the Multi-select actions bar.

3. Choose a tag from the dropdown menu.

   1. If a tag is already assign to at least one variant within the selected variants of interest, a confirmation window will appear showing the current assigned tag and the new tag per variants.

   2. When multiple tags per variant are enabled, tags are always added in addition to existing tags. no confirmation window will appear.

   3. All tags assigned to a variant are displayed in the Tag column.

   4. If both user tags and AI tags exist, only user tags appear in the column.

Remove tags

1. Select the variants of interest.

2. Click the Tag icon.

3. Choose one of the following:

   1. Clear – removes user-assigned tags.

   2. Not relevant – removes tags assigned by Emedgene.

3. Assign/ Clear pathogenicity

Set or remove pathogenicity classifications for multiple variants:

Assign pathogenicity

1. Select the variants of interest.

2. In the Multi-select actions bar, click the Pathogenicity icon.

3. Choose a classification (Pathogenic, Likely Pathogenic, VUS, Likely Benign, Benign).

Clear pathogenicity

1. Select the variants of interest.

2. In the Multi-select actions bar, click the Pathogenicity icon.

3. Select Clear to remove the existing classification.

How to update a case status:

A. On the

B. In the

1. In the Cases table, click the current case status of the relevant case

2. From the dropdown menu, select the new status you want to apply

The variant table displays all variants identified in your case, along with key annotations, quality metrics, pathogenicity data, and interpretation details. Each column provides specific information to help you review and prioritize variants effectively.

This guide explains the meaning of each column for proband analysis and trio analysis, with sorting features and scoring details.

1. Core variant information

Variant Details

• Displays genomic coordinates and basic variant identifiers.

  • SNV/Indel: Genomic position, nucleotide change, and dbSNP ID.

  • CNV/SV: Genomic coordinates and variant size.

• Sorting: Allows sorting by genomic start location.

Gene

• HGNC-approved gene symbol(s) where the variant occurs.

  • Single-gene CNVs: One gene symbol.

  • Multi-gene CNVs: Multiple gene symbols (hover to see full list).

• Sorting: Alphabetical.

Variant Type

• Specifies whether the variant is SNV, Indel, CNV, SV, STR, or other.

• Sorting: Alphabetical.

2. Clinical and phenotypic data

Disease

• Displays the number of disease associations, disease name and inheritance modes derived from OMIM, CGD and ORPHANET. Shows complete list of disease names and inheritance on hovering.

• Sorting: Alphabetical.

Tag

• Indicates variant tags assigned by Emedgene or manually by users (e.g., "Candidate," "Reviewed").

• Sorting: Alphabetical.

Known Variants

• Shows existing classifications from ClinVar and your Curate database.

• Sorting: Alphabetical.

Variant Notes

• Indicates if Variant Interpretation notes are available.

• Sorting: Alphabetical.

3. AI and Phenotype scoring

AI Rank

• AI-based ranking of potential causative variants. Lower numbers indicate higher rank. Variants with identical scores share the same rank (1–220).

• Sorting: Numerical.

Phenomatch Score

• Proprietary phenotype-matching score ranging from 0–1.

• Sorting: Numerical.

Phenomeld Score

• Enhanced phenotype-matching score (range 0–2).

  • 0 = No match

  • 0.15 = Moderate match

  • 0.7 = High match

• Sorting: Numerical.