Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
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 quality, alongside log R deviation.
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 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 value is shown as is. The system does not validate or flag abnormal ploidy values. Interpret ploidy in context.
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.
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.
The case status reflects the current stage of case processing, either by the Emedgene platform or a genomic analyst.
Case statuses help teams:
Monitor case progress
Track ownership
Maintain workflow consistency across the organization
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 log
There are out-of-the-box statuses provided by the platform and the option to create custom statuses to suit your case review workflow. Go to Settings > Management > to create, remove, or reorder case statuses for your organization.
In the top bar of the individual case page, click the dropdown icon next to the current case status
From the dropdown menu, select the new status you want to apply
In the Cases table, click the current case status of the relevant case
From the dropdown menu, select the new status you want to apply
The Top bar in the Individual case page indicates the Case ID and current Case status.
Change the Case status
Reanalyze the case
and write interpretation notes
Preview the
Summary dashboard provides a quick overview of key quality indicators at both the case and sample levels.
Case quality 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
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
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
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
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
Sample-level 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.
The Emedgene Workbench offers a wide array of dynamic filters to help reveal or limit variants that are the most relevant to your clinical case. Each filter contains multiple options to customize the case review process according to your organization's best practices.
: Quickly locate specific variants within a case by applying customized filters. Located on top of the Filters/Presets panel.
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
Phenomatch Filters are used to highlight variants in genes linked to diseases whose symptoms closely align with the patient's clinical presentation. These genes have high phenotypic match scores, calculated through .
There is a corresponding filter for each model:
Phenomeld
The Zygosity Filters enable manual selection of for each sequenced sample in the pedigree.
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.
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.
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
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
If the sex was marked as unknown during case creation, the system will display the predicted sex instead of a validation status.
N/A QC file not available; validation could not be performed.
If the sex was marked as unknown during case creation, the system will display the predicted sex instead of a validation status.
Filters tab: Manually adjust variant specifications using a range of filter options
Presets tab: Apply predefined filter combinations tailored to your team's case analysis SOPs



Phenomatch – Powered by AI
Phenomatch – High Specificity
Phenomatch with Unknown



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 overall sample quality indicator provides a quick assessment of sequencing reliability for each sample.
Sample quality is evaluated using the following metrics:
Average depth of coverage Mean coverage across the target regions
% bases covered >20x Percentage of bases in the target regions covered at a depth greater than 20×, indicating reliable coverage
Error rate Sequencing error rate. Reflects general sequencing accuracy
% mapped reads Proportion of reads successfully mapped to the reference genome
Contamination check Detects mixed or low-quality samples that may affect interpretation
These metrics give an overall confidence level for whether the sequencing data can support accurate variant interpretation.
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 quality, alongside call rate.
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.
You can expand to a broader genetic testing option if the results of more targeted testing are inconclusive. You may reflex from Custom Panel to Exome or Genome, or from Exome to Genome.
To do this, you should change the Case type in Edit case info flow, thereby rerunning using the broader analysis.


The user can enter a specific case from the Cases tab by clicking Full details in the corresponding row of the case table.
Top bar—displays a Case ID and Case status and includes Case interpretation, Edit case info, and Report preview buttons
—highlights a shortlist of variants, suggested to be reviewed first - Most Likely Candidates and Candidates
—illustrates quality metrics for the sequenced samples
—provides an interactive overview of genomic structure, ideal for analyzing CNV and ROH/LOH events
—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
—documents versions of all the resources used during case analysis
The Contamination column reports whether a sample shows signs of DNA contamination, helping ensure data reliability before interpretation.
Be mindful that when contamination is suspected in sequencing data, it could stem from various sources, including true contamination, sample mix-up, library preparation issues, or technical artifacts.
Always confirm the issue with other quality checks.
Contamination is detected using Peddy calculations, which estimate the proportion of reads that do not match the expected genotype. This estimate is based on the idr_baf score.
idr_baf stands for the interdecile range of the B-allele frequency—calculated as the difference between the 90th and 10th percentiles of the distribution of alt / (ref + alt) ratios across all variant sites.
A larger idr_baf value indicates greater variability in allele balance, which may suggest sample contamination, particularly from another human DNA sample.
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
Hover over the value to display a tooltip showing the HET ratio (proportion of sites that are heterozygous) and the HET count (number of heterozygote calls in sampled sites).
Tips:
Always review contamination results before starting interpretation to rule out technical issues that could explain unexpected variant calls.
Warnings:
Panels may be less reliable: For targeted panels, contamination estimates may be inaccurate due to the limited number of variants available for calculation. Use caution and cross-check with other QC metrics when interpreting these results.
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.
The Lab tab shows sample and case-level quality metrics so you can check data reliability before starting interpretation.
Summary dashboard—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 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.
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 and support in-depth review and documentation.
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.
Several dozen highly scored variants worth considering.
The ranking of variants by AI Shortlist considers:
SNVs
CNVs
SNV + CNV compound heterozygotes
SVs
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.
New mode introduces a dual-view interface that combines the variant table with an IGV-based visualization component.
Users can enable the New Analysis tools viewing mode using the toggle in the upper-right corner of the screen. When the New mode is activated, a new window appears on top of the variant table in the lower half of the screen. The window includes the Variant visualization tool, same as available in the Visualization tab of the Variant page.
Visualization window features
The window can be resized by dragging its upper border
Use the Show visualizations and Hide visualizations on top of the variant table to toggle the visualization component on or off.
Table and visualization window interaction
Single-click on a variant row zooms the visualization to that region (Note: In Legacy mode, single-click opens variant page)
Double-click or click the Open link (visible in the leftmost column on hover) to open variant page
Once a variant is open in visualization window, use the up/down arrow keys to move through the variant table
All filter and preset activity is automatically preserved when switching between Legacy and New modes.
Legacy mode does not include access to the IGV-based variant viewer.
You can filter for the following inheritance patterns:
Autosomal Recessive - Homozygotes: Autosomal variants that are homozygous (Hom) in the proband and other affected family members (if any), and heterozygous (Het), reference (Ref), or have no coverage (No Cov) in the unaffected members.
Autosomal Recessive - Compound Heterozygotes: Two or more autosomal het variants in the same gene inherited from different parents. This filter excludes haplotype variant types.
X-Linked Recessive: X-chromosome variants in a male proband where zygosity is Het, Hom, or Hemi in the proband, Het, Ref, or No Cov in the unaffected mother, and Ref or No Cov in the unaffected father.
X-Linked Dominant: X-chromosome variants where zygosity is Het, Hom, or Hemi in the proband, Het in the affected mother, and Ref or No Cov in the unaffected father.
De Novo Dominant: Variants where zygosity is Het in the proband and Ref in both unaffected parents.
Autosomal Dominant: Autosomal variants where zygosity is Het in the proband and affected family members and Ref in unaffected family members.
The Gene Filters allow filtering variants by specific genes or regions based on clinical relevance, functional significance, or targeted sequencing design. These filters help prioritize variants in genes associated with disease, dosage sensitivity, or coding regions.
All Disease Associated Genes: Variants in genes with a published disease association.
All Unknown Genes: Variants in genes of unknown clinical significance.
Candidate Genes: Variants in a gene list defined during case creation.
When are reset to default, Gene Filters remain disabled, except for cases launched in Virtual Panel mode. In such cases, the Candidate Genes filter is activated by default.
The Variant Type Filters allow filtering variant list by variant type:
Small variants: SNV, Indel, MNV (100.39.0+)
SV & CNV: DEL, DUP, INS
mtDNA SNV/Indel
Other: STR, Haplotype, LOH/ROH
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).
The Pedigree section displays relatedness metrics and the results of relationship validation for each pair of samples in the family tree.
Relatedness coefficient (observed)
Shows the observed coefficient of relatedness between sample pairs. The expected coefficient is available via hover tooltip for quick comparison.
The Genome view tab is a powerful feature designed to give users a clear, visual overview of the genome and chromosomes in their cases. This feature is especially useful for analyzing large Copy Number Variation (CNV) events and regions of homozygosity/loss of heterozygosity (ROH/LOH) across the genome, providing intuitive filtering and interactive insights for researchers and clinicians.
The Genome View tab is a dedicated section within the Case Page for Whole Genome Sequencing (WGS), Whole Exome Sequencing (WES), and Array data. This tab offers a graphical visualization of genomic data, focusing on CNV and LOH/ROH analysis for proband cases. Users can access this tab directly from the Case Page.
Hom = Homozygous for alternative allele;
Het = Heterozygous;
Hemi = Hemizygous (X-chromosome variants in males except for heterozygous variants in pseudoautosomal regions);
Ref = Homozygous for reference allele;
Each phenotype observed in the proband is compared to the phenotypic profile of the selected disease. Based on how closely each proband phenotype matches the disease phenotype profile, a similarity level is assigned.
On the and in the Variant page , each HPO term listed for the proband is marked with an icon that shows how similar it is to the phenotypes reported for the disease.
Exact match
The Emedgene Workbench offers a wide array of dynamic filters to help reveal or limit variants that are the most relevant to your clinical case. Each filter contains multiple options to customize the case review process according to your organization's best practices.
: Quickly locate specific variants within a case by applying customized filters. Located on top of the Filters/Presets panel.
Likely
Contamination suspected (0.241 ≤ idr_baf < 0.300).
Yes
Contamination confirmed (idr_baf ≥ 0.300).
For family cases, check that no contamination is flagged before relying on inheritance-based filters.
mtDNA variants
STRs
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)
During review in the Candidates tab, additional tags can be applied to a variant alongside the original automatic tag.
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
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.
A variant is automatically tagged as an incidental (secondary) finding if it meets all of the following criteria:
Classification: Previously classified as pathogenic or likely pathogenic in ClinVar or Curate variant databases
Zygosity: Heterozygous or homozygous (only homozygous for the HFE gene)
Allele frequency: Less than 5%
Read depth: 10× or higher
Variant quality: Any value but LOW
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)
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.
*In Emedgene, the terms "incidental findings" and "secondary findings" both refer to secondary findings as defined by the ACMG, due to historical usage.
When Emedgene was first released, the term “incidental findings” was adopted in alignment with the clinical genomics standard at the time. The 2013 ACMG recommendations defined incidental findings as “the results of a deliberate search for pathogenic or likely pathogenic alterations in genes that are not apparently relevant to a diagnostic indication for which the sequencing test was ordered” (PMID: 23788249).
As the field evolved, the ACMG and broader clinical community began to distinguish between “incidental findings” (unexpected, not actively sought) and “secondary findings” (intentionally analyzed and reportable). This shift was reflected in the updated 2016 ACMG guidance (PMID: 27854360).
To reflect this change, Emedgene introduced the term “secondary findings” into the platform. However, “incidental findings” remains in use throughout the platform for technical consistency.
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.
Variants that were manually selected to be reported.
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.
Tips:
Use ploidy checks early in case review to spot potential large-scale chromosomal abnormalities.
Always confirm whether the sex karyotype inferred from ploidy matches the sex validation results to rule out sample swaps.
Failed results do not confirm clinical abnormalities. They only indicate a deviation in copy number estimation and should be reviewed in context of other QC metrics and visualization.
Run a FASTQ case in Emedgene.
Since DRAGEN analysis is integrated into Emedgene secondary analysis pipeline, QC reports are automatically generated in the system.
Run DRAGEN analysis externally.
Prepare a TAR archive containing DRAGEN QC metrics files.
Upload the TAR archive and the sample VCF file to Emedgene.
This workflow is supported for batch case upload via UI and CLI and API-based case creation.
Array cases start from VCF input files. DRAGEN QC for array cases is supported on Emedgene v100.39.0 and later.
Run DRAGEN analysis externally using DRAGEN Array v1.3.0.
Upload the .annotated_cyto.json DRAGEN QC metrics file, the sample VCF file, and the .gt_sample_summary.json file to Emedgene.
This workflow is supported for batch case upload via UI and CLI and API-based case creation.
On-demand variant visualization tool: Provides visual review of alignment and annotation data for selected variant. Available for RUO cases in New Analysis Tools mode when Show visualization is selected.
Filters tab: Manually adjust variant specifications using a range of filter options
Presets tab: Apply predefined filter combinations tailored to your team's case analysis SOPs




v100.39.0+: 84 genes (Lee et al. 2025)
≤v38.0: 81 genes (Miller et al. 2023)
Cancer Associated Genes: Variants in genes with published association with oncological disease.
LoF Genes (Emedgene Knowledgebase 26+): Variants in extremely LoF-intolerant genes (gnomAD pLI ≥ 0.9).
If a variant is a CNV that overlaps more than one gene, it will appear in the filtering results if at least one of the genes has gnomAD pLI ≥ 0.9).
Variants of type mtDNA are excluded because they are not included in ClinGen dosage sensitivity dataset.
Established HI/TS Genes (Emedgene Knowledgebase 26+): Variants in genes with sufficient evidence of dosage sensitivity (defined by having ClinGen's Haploinsufficiency and/or Triplosensitivity scores of 3).
Variants of type mtDNA are excluded because they are not included in ClinGen dosage sensitivity dataset.
Coding regions: Variants restricted to the protein-coding sequences.
In Targeted Regions: Variants in regions defined by the Enrichment Kit selected during case creation. RefSeq coding regions are used as a reference if no kit is provided.


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 is done by Peddy 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).
Unrelated
Relatively high
0
< 0.2 Pass 0.2–4 Shared ancestry 4–15 Consanguinity
> 15 Consanguinity + Failed validation
Parent–child
0 or close to 0. Any IBS0 sites—due to genotyping errors
50
< 40 Failed validation 40–60 Pass > 60 Failed validation
Full siblings
Small but detectable number
Chromosome ideogram
The chromosome ideogram offers a visual representation of all 23 human chromosomes, with CNV and LOH/ROH events highlighted for intuitive analysis. Here's what you can expect:
Variant types:
Deletions (DEL): Marked in red, displayed to the left of the chromosome.
Duplications (DUP): Marked in blue, displayed to the right of the chromosome.
LOH/ROH (Regions of Homozygosity/Loss of Heterozygosity): Marked in gold, displayed over the chromosome.
Note: Variants with no coverage or reference (Ref) are excluded.
Filtering Options:
Users can filter segments by size, using a range selector with the following options: 50 bp,1 KB, 10 KB, 50 KB, 100 KB, 1 MB, 10 MB, Max (no filter).
The default filter is set from 50 KB to Max.
Note: Only the 500 largest variants are displayed in this tab.
Hover and Click Interactions:
Hovering over a variant displays
Chromosome number, start and end positions, and size (e.g., chr1:100000-200000 (100 KB))
Cytoband range (e.g., p12.3 - q11.2) based on ISCN nomenclature
Variant type (DEL/DUP/LOH/ROH)
Number of genes affected
Clicking on a chromosome refines the genome view below to that chromosome.
Clicking on a variant opens a detailed Variant Page where many actions and further review can be made.
Legend: A clear legend explains color coding and icons for DEL, DUP, and LOH/ROH variants for quick reference.
The genome viewer provides a deeper dive into the genomic data through three interactive tracks:
Log R / TNS Track:
Displays copy number intensity data using values from the TNS BigWig file or LogR bedgraph.
Y-axis ranges from -3 to 3, with increments of 0.4.
X-axis displays the genome (whole genome view) or chromosome segments (whole chromosome view).
BAF Track:
Displays B Allele Frequency (BAF) data using values from the BAF BigWig file or BAFbedgraph.
Y-axis ranges from 0 to 1, with increments of 0.1.
ROH Track:
Indicates regions of homozygosity for further analysis.
Zoom and navigation
Default View: Displays the entire genome.
Zoom-In Options: Users can zoom in to view individual chromosomes by clicking on them.
Interactive Navigation: Clickable chromosomes on the ideogram allow seamless switching between views.

Match by ascendance/descendance
The proband phenotype is a direct ancestor or descendant of a disease phenotype in the Human Phenotype Ontology (HPO) hierarchical tree, up to 7 steps apart.
Indirect match
The proband phenotype lies within a 4-step range in the HPO graph from the disease phenotype but is not its direct ancestor or descendant. While indirect match may highlight potential connections, we advise users to interpret it carefully because it may include phenotypes from different branches of the HPO ontology that are not biologically related.
No match
The proband phenotype does not appear in the disease’s phenotype list and is not connected to it within the range of match by ascendance/descendance and indirect match.
Proprietary phenotypic match models assess how closely a gene’s associated disease phenotype matches the patient’s phenotype profile. A degree of similarity is resembled by the phenotypic match score. The phenotypic match score indicates the degree of similarity between the patient’s phenotype set and the phenotype set of the best-matching gene-related disease.
If a gene is linked to multiple diseases, the model compares the patient’s phenotypes with each disease profile individually. The highest score determines the best match, and this disease is automatically displayed in the Evidence graph. The Phenomatch and Phenomeld scores shown in the variant table correspond to this best-matching disease, even if the associated disease is manually updated.
Note: Case reanalysis causes Phenomatch/Phenomeld scores to be recalculated.
The Versions tab provides a snapshot of all tools, data sources, and knowledge bases used during the analysis of a case. This feature supports traceability and reproducibility by documenting the exact versions of each resource involved in variant interpretation.
This section lists automated tools used for variant-level annotation. Using computational models and predictive algorithms, they generate scores or classifications that help assess the potential impact of each variant.
This section includes Emedgene proprietary models and components that support variant prioritization and interpretation:
ACMG tags algorithm
AI Shortlist model "Tier v0" indicates focused mode, and "Tier v2" indicates discovery mode of the AI Shortlist model for rare diseases.
Emedgene knowledge base
An Emedgenizer is a logic-based tool designed to normalize quality parameters in the VCF output from a specific , ensuring alignment with Emedgene internal format. An Emedgenizer is specific to the variant caller, its version, and the calling methodology used.
All Emedgenizers are grouped and versioned within an Emedgenizer Plugin.
Typically, the Emedgenizer Plugin version used for a case aligns with the pipeline version that processed it. However, updates to existing normalization logic, bug fixes, or the addition of support for new callers or methodologies may require updating or creating new Emedgenizers, which in turn necessitates a new plugin version. These changes are generally reflected in a minor version update of the Emedgenizer Plugin.
Phenocompare model
This section documents the input files used in the tertiary analysis pipeline. These include:
Quality BED file—Defines regions used to evaluate sample quality
Region of interest BED file—Specifies genomic intervals included in tertiary analysis
Sample VCF files—Contain the variant calls generated during upstream analysis; associated individual
This section documents the curated databases used to provide gene-level and disease-related information.
This section includes organization-specific datasets integrated into the analysis.
This section documents the variant frequency databases used to assess variant rarity and support pathogenicity classification.
This section documents the reference genome assembly name and reference genome GenBank assembly accession number.
This section includes databases that support classification by providing information on previously observed variants.
Note: These versions remain static from the time a case is run. They are not updated unless a case is reanalyzed.
Current limitation: Reports generated within the system do not dynamically reflect the versions of the tools, data sources, and knowledge bases used.
The Polymorphism Filters enable filtering variants by alternative allele frequencies and genotype counts in public and internal databases.
The Polymorphism Filters can operate in a or mode.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
Exporting annotated variant data facilitates collaboration and record-keeping. To start the download, click the Export icon at the top of the Analysis Tools tab.
The XLSX export file contains only the variants visible after applying filters. If your filtered list has more than 1,500 variants, the export file will include only the first 1,500.
The Evidence & Tags filters focus variant review by surfacing variants with relevant supporting evidence, annotations, tags, and review status, making decision‑making faster and more consistent.
The Evidence & Tags filters can operate in a or mode.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
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.
Note: Multi-selection and bulk actions are only available in non-finalized cases to maintain data integrity.
The Presets feature in the Analysis Tools tab lets you save and reuse filter combinations that match your lab’s workflows and Standard Operational Procedures (SOPs). Instead of setting filters from scratch each time, you can apply a Preset to instantly narrow down variants according to predefined rules. Presets can be created from active filters or gene lists, and managed at the organization level for consistency across all users.
To save Presets from active filters:
Case ID
Chromosome
Position
REF
ALT
END
Vartype
Gene
Transcript
Effect
Quality
Depth
Alternate Read
Proband Zygosity
Allele Bias
GnomAD AF
GnomAD AC
GnomAD SV AF
GnomAD SV AC
Max AF
Pathogenicity
Coding Change
Protein Change
Hom
Hemi
Tag
Prediction
SpliceAI DS AG, AL, DG, DL
SIFT Pred
LRT Pred
MutationTaster Pred
PolyPhen2_HVAR Pred
PolyPhen2_HDIV Pred
DANN Score
REVEL Score
CADD Phred Score
PrimateAI3D Score
PrimateAI3D Prediction
ExAC pLI
gnomAD pLI
Missense z-score
pRec
Known Variants
Other Family Members
Reference
Evidence Text
Diseases
Disease Inheritance Mode
Phenomeld Score
AI Rank
Individual Genotype
Variant length (kbp)
ISCN
Cytoband
Bin Count
Variant Inheritance
Phenomeld represents the cutting edge of phenotypic matching models from Emedgene. As an advanced iteration of Phenomatch – Powered by AI, it delivers superior gene prioritization.
The score ranges from 0 to 2:
A score of 0 indicates no phenotypic match,
A score above 0.15 suggests a moderate match,
A score above 0.7 indicates a strong phenotypic match.
Phenomatch – Powered by AI identifies genes with disease phenotypes that loosely match the patient’s HPO terms.
The score ranges between 0 and 1 where 1 is the strongest match.
Phenomatch – High Specificity identifies genes with disease phenotypes that exactly match the patient’s HPO terms.
The score ranges between 0 and 1 where 1 is the strongest match.
Phenomatch with Unknown identifies genes of unknown significance based on indirect links to patient phenotypes. These links may include mouse models, gene families, pathways, and other functional associations.
The score ranges between 0 and 1 where 1 is the strongest match.
Emedgenizer plugin (v100.39.0+)
50
< 40 Failed validation 40–60 Pass > 60 Failed validation

Use the Display Polymorphism toggle to enable or disable filtering:
On: No filtering is applied
Off: Variants with maximum allele frequency >0.05 in public databases are excluded
Select the source for population statistics:
A specific database
All databases
By default, "All databases" is selected.
Available databases:
SNV, STR:
gnomAD
ExAC
Apply the filters to the selected source.
Maximum allele frequency in the selected source.
Range: 0–0.05 using the slider
Custom value: Enter a number in the input field (value can exceed 0.05 but cannot be greater than 1)
Hom/Hemi count—the number of individuals who are homozygous/hemizygous for the variant in the selected source.
Range: 0–100 using the slider
Custom value: Enter a number in the input field (value can exceed 100)
Max: Disables filtering for this parameter
Maximum allele count in the selected source.
Range: 0–500 using the slider
Custom value: Enter a number in the input field (value can exceed 500)
Max: Disables filtering for this parameter
Maximum allele frequency in a sample of 806 healthy individuals, designed to eliminate artifacts introduced by the FASTQ processing pipeline.
Range: 0–0.05 using the slider
Custom value: Enter a number in the input field (value can exceed 0.05 but cannot be greater than 1)
Maximum allele frequency within the internal databases of an organization (Historic or Noise).
Range: 0–0.05 using the slider
Custom value: Enter a number in the input field (value can exceed 0.05 but cannot be greater than 1)
When Filters are reset to default, The Polymorphism filters are not applied.
Variant interpretation: Variants with automatically or user‑created Variant Interpretation notes, unless the notes were removed by a user.
Submitted for Sanger confirmation: Variants marked as requiring additional validation by Sanger sequencing
Manually added variants: Variants on top of the automated case results by a user
Pathogenicity: Variants with an assigned
Filter by tagging status.
My tags: Variants tagged by you
AI Shortlist: Variants tagged by the AI Shortlist
Filter by viewing status.
Viewing status is tracked per user and reflects only your own variant review activity, specifically opening the Variant page.
Viewed: Variants you have already viewed
Unviewed: Variants you have not yet viewed
Filter by pathogenicity classification.
Pathogenic
Likely Pathogenic
Uncertain significance
Likely Benign
Benign
Filter by user-applied tags:
Specific tags: Variants with selected user-assigned tags
My tags: Variants tagged by you
User tags: Variants originally tagged by users and not tagged by the AI Shortlist
Filter by AI shortlist tags.
Most Likely
Most Likely GUS
Candidate
Candidate GUS
When are reset to default, The Evidence & Tags filters are not applied.
Hover over a variant to reveal a checkbox at the start of the line;
Selecting a checkbox activates the Multi-select actions bar, replacing the Search bar.
Checkboxes appear for all variants in the current view.
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.
Change the review status for multiple variants at once:
Select the variants of interest.
In the Multi-select actions bar, click the Viewed icon.
Choose Viewed or Un-viewed.
Note: Variants already tagged by a user cannot be marked as Un-viewed.
Assign or manage tags across multiple variants at once:
Assign tags
Select the variants of interest.
Click the Tag icon in the Multi-select actions bar.
Choose a tag from the dropdown menu.
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.
When multiple tags per variant are enabled, tags are always added in addition to existing tags. no confirmation window will appear.
All tags assigned to a variant are displayed in the Tag column.
If both user tags and AI tags exist, only user tags appear in the column.
Remove tags
Select the variants of interest.
Click the Tag icon.
Choose one of the following:
Clear – removes user-assigned tags.
Not relevant – removes tags assigned by Emedgene.
Set or remove pathogenicity classifications for multiple variants:
Assign pathogenicity
Select the variants of interest.
In the Multi-select actions bar, click the Pathogenicity icon.
Choose a classification (Pathogenic, Likely Pathogenic, VUS, Likely Benign, Benign).
Note: Only tagged variants can have pathogenicity assigned.
Clear pathogenicity
Select the variants of interest.
In the Multi-select actions bar, click the Pathogenicity icon.
Select Clear to remove the existing classification.
Tips:
Use bulk tagging to ensure consistency across variants that share biological or interpretive context.
Combine tags and pathogenicity assignments in bulk to streamline reporting prep.
For large variant sets, apply filters first to narrow down your view before using multi-selection.
Warnings:
Bulk edits apply immediately to all selected variants. Double-check your selections before applying.
Removing tags or pathogenicity affects all team members working on the case—coordinate with your team to avoid conflicts.
Once a case is finalized, bulk actions are disabled to protect case integrity.
Open the Filters panel and navigate to the Filters tab
Apply the filters you want
Click on the three-dot icon
Select Save as preset
Enter a name for the Preset (Note: Avoid using non-Latin symbols that don't follow the ISO-5589-1 standard)
Click Save
In Presets, scroll to Gene Lists
Select the gene lists you want to utilize as filter presets by marking the relevant checkboxes. You can also search by list name.
Click Save
Presets originating from gene lists will appear in Presets under Gene Lists.
Click the arrow next to a Preset name to review its logic directly in your analysis flow
When you apply a Preset, you can refine it further by running a search on top of the filtered results. This creates a real-time sub-filter without changing the original Preset.
Example: If your Preset is based on a gene list with multiple genes and returns many variants, you can search for a single gene within that list. The results will then display only variants from that specific gene.
If this refined view is useful for future cases, you can save it as a Custom Preset.
When you have completed reviewing all variants within a Preset, you can mark it as Reviewed. This feature makes it clear which Presets have already been addressed in a case, helping teams avoid re-checking the same variants.
Once marked, the Preset will display a visual indicator in the Presets panel. You can still reopen and apply the Preset at any time if you need to revisit it.
Tips:
Use Viewed/Unviewed filters in Presets to avoid re-checking the same variants.
Use marking a preset as reviewed feature in collaborative workflows so team members know which Presets have already been covered. If your SOP requires multiple reviewers, the Preset can be revisited even after being marked as reviewed.
Combine search and filters: A search applied within a Preset intersects results in real time (e.g., narrow a multi-gene preset to a single gene).
Use Search Intersect to quickly narrow large gene lists without editing the original Preset.
Save refined results as Custom Presets to reuse them in similar cases.
Combine multiple searches for stepwise filtering when reviewing complex datasets.
In Emedgene, case status indicates the current stage of a case—from data upload through analysis, review, and results finalization. Statuses are assigned either automatically by the system or by authorized users, depending on the workflow stage and user permissions.
Different statuses require different IAM scopes/Emedgene roles for assignment and reassignment.
Case statuses are grouped into three categories based on control type:
System-controlled: Assigned automatically by the system; cannot be reassigned by users.
User-controlled: Assigned and reassigned by authorized users.
System-assigned, user-reassignable: Assigned automatically by the system but can be reassigned by authorized users.
Case statuses by origin:
Out-of-the-box: Default options provided by the platform.
Custom: to align with specific workflows.
Each status represents a distinct stage in the case lifecycle. Figure 1 shows the possible transitions between statuses and the control type for each assignment, indicated by solid and dashed arrows. Table 1 provides an overview of case statuses.
Table 1. Case status reference
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.
Note: SV support is planned for future releases.
Open the Analysis Tools tab.
Click the plus (+) button in the top-right corner.
Note: If you do not see the option, please contact support to verify your user role permissions.
In the Manually Add Variant window, select the variant type: SNV, CNV, UPD, ROH, or STR.
Fill in the details based on the selected type:
Chromosome,
Position,
REF,
Click on Create Variant to add it to the case.
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.
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.
Tip: When reviewing manually added STRs, rely on the repeat numbers and unit provided, since length formatting is not included.
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.
Use the Filters tab in the Filters/Presets panel to narrow numerous variants down to those most relevant to your case.
Applying multiple filters at once may exclude important variants if thresholds are too strict. Start broad, then refine.
, , , , and can operate in either a simple or advanced mode.
Use simple mode for quick, high-level filtering. For more detailed filtering with expanded options, choose advanced mode to gain deeper control over filter parameters.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
For example, setting Severity to "High" in simple mode might yield slightly different results than selecting all high severity Main effect options in advanced mode of Variant effect filters.
When the Filters tab of the Filters/Presets panel is selected, click the vertical ellipsis (⋮) in the top-left corner to access the following actions:
Clear: Clears all filters and displays all variants in the case
Reset to default: Clears all filters and applies the :
Quality: Moderate/High
If you need to update your case details, adjust phenotypes, change the gene list, or customize disease information for reporting, Emedgene allows you to edit an existing case directly from the interface. Depending on what you modify, some edits may prompt reanalysis, while others will simply be saved without triggering a new run.
Important: Not all changes are supported. Certain modifications must be handled by creating a new case.
GME
SV, CNV:
gnomAD SV
DGV Gold
Decipher Healthy Population


















Custom status
Indicates a custom case processing stage between "Delivered" and "Finalized".
User-controlled
Custom
"Finalized"
The analysis and review of the case by the analyst group have been .
Typically assignment and reassignment of the "Finalized" status is configured to be restricted to organization managers and/or lab directors.
User-controlled
Out-of-the-box
"Trash bin" (v38.0+) or
"Move to trash" (≤v37.0)
Case marked for ; access restricted.
Typically assignment and reassignment of the "Trash bin"/"Move to trash" status is configured to be restricted to organization managers and/or lab directors.
User-controlled
Out-of-the-box
"Pending sequencing"
Case created; awaiting sequencing data.
System-controlled.
Exception: user-reassignable to "Trash bin"
Out-of-the-box
"Issue reported"
The case failed to run.
Please check the integrity of the uploaded files and ensure that the variant caller used is on Emedgene list of accepted .
System-controlled.
Exception: user-reassignable to "Trash bin"
Out-of-the-box
"Reanalysis"
The system is re-running the AI Shortlist algorithm.
System-controlled
Out-of-the-box
"Uploading"
Data upload in progress.
System-controlled
Out-of-the-box
"In progress"
Analysis currently running.
System-controlled
Out-of-the-box
"Delivered"
Analysis completed; case ready for review.
System-assigned, user-reassignable
Out-of-the-box
Zygosity
Chromosome,
Position Start,
Position End,
REF,
ALT,
Type:
CNV: DEL, DUP,
UPD: IUPDMAT (maternal isodisomy), IUPDPAT (paternal isodisomy), HUPDPAT (paternal heterodisomy), HUPDMAT (maternal heterodisomy),
Zygosity
Chromosome,
Position,
REF Repeats Number,
ALT Repeats Number,
Repeats Unit,
Zygosity
Population Statistics are not shown.
Automatic ACMG scoring is not applied, but you can still manually add ACMG tags, interpretation notes, and classifications.




Variant Severity: Low/Moderate/High
Proband Zygosity: Het/Hom
Save as preset: Saves the current filter configuration as a new preset
Narrow variants by sequencing quality metrics such as depth, mapping quality, and confidence grade
Filter by allele frequency and genotype counts from public databases (e.g., gnomAD, ExAC) or your lab’s internal controls
Focus on specific variant categories (SNVs, indels, CNVs, SVs, STRs, mtDNA)
Select by predicted consequences on genes or proteins, ACMG classes, or database classifications
Apply computational prediction scores for pathogenicity, conservation, splicing, or missense effects
Restrict results to genes of interest, such as disease–associated, candidate, ACMG actionable, or cancer–related genes
Highlight variants in genes with known disease associations matching the proband’s phenotypes
Filter variants according to inheritance patterns consistent with family genotypes and phenotypes
Select by genotype status (Het, Hom, Hemi) in specific samples
Show variants tagged by users, AI shortlist, or flagged at the organization level
Filter by allele frequency and genotype counts from public databases (e.g., gnomAD, ExAC) or your lab’s internal controls
Focus on specific variant categories (SNVs, indels, CNVs, SVs, STRs, mtDNA)
Select by predicted consequences on genes or proteins, ACMG classes, or database classifications
Apply computational prediction scores for pathogenicity, conservation, splicing, or missense effects
Restrict results to genes of interest, such as disease–associated, candidate, ACMG actionable, or cancer–related genes
Highlight variants in genes with known disease associations matching the proband’s phenotypes
Filter variants according to inheritance patterns consistent with family genotypes and phenotypes
Select by genotype status (Het, Hom, Hemi) in specific samples
Show variants tagged by users, AI shortlist, or flagged at the organization level
Applying multiple filters at once may exclude important variants if thresholds are too strict. Start broad, then refine.
Quality, Polymorphism, Variant effect, In silico prediction, and Evidence & Tags filters can operate in either a simple or advanced mode.
Use simple mode for quick, high-level filtering. For more detailed filtering with expanded options, choose advanced mode to gain deeper control over filter parameters.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
For example, setting Severity to "High" in simple mode might yield slightly different results than selecting all high severity Main effect options in advanced mode of Variant effect filters.
When the Filters tab of the Filters/Presets panel is selected, click the vertical ellipsis (⋮) in the top-left corner to access the following actions:
Clear: Clears all filters and displays all variants in the case
Quality: Moderate/High
Variant Severity: Low/Moderate/High
Proband Zygosity: Het/Hom
Save as preset: Saves the current filter configuration as a new preset
Narrow variants by sequencing quality metrics such as depth, mapping quality, and confidence grade
Open a case you wish to edit,
Click the Edit Case Info button in the top right corner.
This will open the Add new case flow where you can modify fields across the following sections:
Family Tree
Select Gene List
Select Preset
Additional Case Info (in the Case Info Screen)
Note: When dealing with delivered cases, only specific data can be modified before initiating reanalysis:
Edits that won't affect the the AI Shortlist analysis, thus won't prompt reanalysis:
Family tree screen:
Clinical Notes,
Patient Ethnicities,
Suspected Disease Severity,
Proband Suspected Disease Condition,
Case info screen:
Indication for testing,
Preset.
Edits that will affect the the AI Shortlist analysis, thus will trigger reanalysis:
Family tree screen:
Proband Phenotypes,
Medical Condition.
⚠️ Prohibited or unsupported changes
Any modifications outside the above lists may lead to reanalysis failure. In such cases, it’s safer to create a new case.
The system does not currently block unsupported edits in the interface — please follow this documentation carefully.
After you've finished editing the case and pressed Next in the Case info screen, a window will pop up:
When you confirm reanalysis:
Case status changes to Reanalysis.
AI Shortlist is recalculated with updated data.
Variant-level evidence from the first run is cleared, except for user-tagged variants.
Preserved for user-tagged variants:
Tag value
Variant interpretation notes
Pathogenicity
Selected transcript
ACMG tags and notes
Sanger and Sanger notes
At the case level, any selected Presets remain saved.
Tip: Reanalysis has been made more robust for older cases and for carrier analyses, so these case types now reprocess more reliably.
If you choose Save instead of Reanalyze:
Your edits are stored without rerunning the analysis.
Note: Changing proband phenotypes may affect the results of Phenomatch filters.
The right-hand Case Details panel will remind you that reanalysis is recommended.
When updating HPO terms, older terms may not map automatically in reanalysis. Review carefully before finalizing.
After reanalysis, some input files may not appear immediately in the Versions tab.
Editing interpretation notes may create an activity entry labeled as reanalysis. This does not affect case results but may appear in the audit trail.
If you replace the gene list, the original list is not displayed in the Activity log.
Always check whether your edit will trigger reanalysis before proceeding.
Keep edits to delivered cases within the supported fields to avoid errors.
For sensitive inputs (like phenotypes or gene lists), plan to rerun the case to ensure results reflect the most up-to-date information.
If uncertain, use the Save option first, then decide if reanalysis is needed.






The Genes coverage section helps you quickly identify parts of genes that may not have been adequately sequenced in your case. This insight is particularly important when assessing sequencing quality, interpreting uncertain findings, or deciding if further validation is needed.
While variant callers provide base-by-base coverage, Emedgene simplifies the view by showing average coverage per region. This makes it easier for you to spot undercovered genes at a glance, even when individual positions may appear sufficiently covered. By smoothing out local fluctuations, average coverage helps you prioritize regions that might require further review and complements DRAGEN's fine-grained metrics with a broader, more interpretable view.
Coverage metrics are generated differently depending on the type of input data used for your case:
1. FASTQ / BAM or gVCF-based cases
If your case was started from FastQ/BAM or gVCF, coverage is inferred from gVCF reference blocks (also called GVCFBlocks).
These blocks are segments of the genome where genotype quality (GQ) is consistent.
A new block is created whenever there's a significant change in GQ, which results in a highly segmented and detailed representation of local sequencing quality.
2. VCF + BAM or VCF + BED-based Cases
If your case includes VCF and BAM or VCF and BED, coverage is calculated directly from the aligned reads or from predefined BED intervals.
Coverage is calculated as the true base-by-base average across the entire region.
This method avoids the variability of gVCF segmentation and gives a precise coverage profile for each region.
Tip: Before comparing coverage values across cases, check whether the case was processed from FASTQ/gVCF or VCF with alignment files (BAM/CRAM). The calculation method differs, so values may not be directly comparable.
Limitation: Coverage estimation is not supported for VCF + CRAM cases. If a CRAM file is used with a VCF file, as opposed to a BAM or a BED file, the Genes Coverage table will remain empty for virtual panel cases.
Coverage is compared against expected regions defined in:
Emedgene's reference BED file, or
Your test’s custom KIT BED file
Each region is defined by:
Chromosome
Start & end positions
Name and strand (Optional)
Emedgene uses the tool bedtools intersect to compare each expected region from the regions used for coverage assessment against actual read coverage. The system captures:
How much of the region overlaps with sequenced data
Depth of coverage per segment
Each region includes these metrics:
Note:
Genes with insufficient coverage is available only for FASTQ-based cases.
Warning:
Minimum depth for FASTQ / BAM / gVCF-based cases does not represent minimum depth but Minimum average depth within the GVCF block.
You can interactively explore gene-level coverage details using the Genes with Insufficient Coverage tab. This tool is currently available only for FASTQ-based cases.
Here’s what you can do:
Search for a specific gene or a list of genes.
Filter results based on coverage thresholds:
≤0x
To check coverage for a gene:
Enter the gene symbol in the search box and select it.
Choose your desired coverage filter from the dropdown.
Review the results in the table or download the data.
Click the Add Gene List button and select any of your pre-loaded gene lists.
By maximum depth of coverage
Select Coverage, then choose the highest allowable coverage value from the dropdown list,
By percentage of bases covered >20×
Select % of Bases Gt20, then choose the highest allowable percentage from the dropdown list.
Visual review in allows manual variant confirmation by inspecting aligned reads at specific genomic regions.
Click on More details in the row corresponding to the gene of interest. This opens a pop-up with coverage details for the selected gene.
In the pop-up, select View on IGV to open the region in the IGV desktop application.
Click the Download button to export the full list of low-coverage regions as a *_insufficient_regions.tsv file. Each row includes region coordinates and all metrics.
Each row corresponds to one region and includes:
Region coordinates
Calculated coverage metrics
Region length
Use this file to:
Compare multiple cases
Track sequencing gaps
Plan confirmatory testing
Share results with collaborators
Use Quality filters to refine variant reviews by setting quality thresholds and filtering based on calling methodology. This prioritizes variants that meet specific confidence metrics for interpretation.
The Quality filters can operate in a Simple or Advanced mode.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
Tips:
Start with Simple Mode for quick triaging, then refine using Advanced Mode
Quickly filter variants by minimum overall sequencing quality:
Low: No quality filtering applied
Moderate: Includes moderate or high quality variants with read depth >10
Provides fine-grained control over multiple quality metrics depending on the variant type.
Aggregated quality specific to variant type and caller. Determines overall confidence score thresholds for all variant types.
Low
Moderate
FILTER column value in VCF.
Pass: Variants with PASS value
Other values: Variants with any value except PASS
Calling methodology filter allows filtering by type.
Small Variant
CNV Read-Depth
Minimum mapping quality.
Range: 0–60 using the slider
Custom value: Enter a number in the input field (value can exceed 60)
Minimum read depth.
Range: 0–500 using the slider
Custom value: Enter a number in the input field (value can exceed 500)
Minimum number of reads supporting the alternate allele.
Range: 0–500 using the slider
Custom value: Enter a number in the input field (value can exceed 500)
Minimum and maximum allowable allele bias. For mtDNA, this represents heteroplasmy level.
Range: 0–100 using two sliders (minimum and maximum)
Sets the minimum and maximum variant size using two sliders.
Supported values: 50 bp, 1 kbp, 10 kbp, 100 kbp, 1 Mbp, 10 Mbp, Max.
Minimum bin count.
Range: 0–500 using the slider
Custom value: Enter a number in the input field (value can exceed 500)
When analyzing a VCF file that includes CNV variants with AD values, be aware that these variants—along with SNVs—may also be impacted by the Allele bias filter.
When are reset to default, The Quality filters are set to:
Quality: Moderate and High
Mapping Quality: ≥45
Depth: ≥10
Finalizing a case locks it to preserve interpretation decisions and ensures reporting consistency. Once finalized, no changes can be made to variant tags, pathogenicity, interpretation notes, or case-level classifications unless the case status is reverted.
Open the Case Interpretation widget
On the Individual Case page, click on the Case Interpretation button in the top bar.
Indicate the case result
In the Case Interpretation widget, select the final result of the analysis:
Confidently Solved (Positive)
Likely Solved (Positive)
Confidently Solved, Likely Solved, and Further Investigation end-result categories correspond to the Resolved case status supercategory.
Unsolved falls into the Not resolved status supercategory together with all the non-finalized cases.
Select variants to include in the Clinical Report
Use the tag filter dropdown to choose which tagged variants to include.
You can reorder variants by drag-and-drop. The order is preserved in the Clinical Report within each tag group and variant type.
Tip: This makes it easier to manage multi-user and multi-tag workflows while ensuring no variant is missed when preparing the report.
Note: each variant in the Case interpretation widget is denoted at the coding DNA and protein level where applicable, otherwise, it's described at the genomic DNA level.
Within the Case Interpretation widget, you may add:
Interpretation notes
Gene interpretation (import gene annotation from Curate)
Recommendations
These free-text fields are saved per case and will automatically populate in the Clinical Report if your lab uses Emedgene’s reporting solution.
Click Save at any time to ensure all changes are recorded.
Click the eye icon in the top bar of the Individual Case page.
Select a template and click Preview.
Reports can be downloaded in .pdf or .odt format.
Change the Case Status to Finalized.
Once finalized:
The case is locked from further edits.
Note: Finalizing a case will prevent users from making further changes to the case. To change information within the case (including and , Interpretation notes, Gene interpretation, and Recommendations, finalized variants, case analysis outcome, and , the case status must be changed from Finalized to another status.
Warning: Finalizing prevents further edits to variant tags, interpretations, and outcomes. Only finalize once you are confident the case is complete.
Click the printer icon in the top bar of the Individual Case page.
Choose Create New or select a previously generated report.
Select a template and click Generate.
For finalized cases, you can review the Case Result, Interpretation Notes, and Finalized Variants in the Finalize tab (right-hand panel).
You can also see finalized variants by selecting Finalized in the dropdown menu on the Candidates tab.
Tip: Use the tag counts in the dropdown to quickly identify how many variants are associated with each tag. This is especially useful for distinguishing between primary findings and secondary/incidental findings before signing off.
Warning: Multi-tag variants may appear in multiple filtered views — always double-check before finalizing to avoid accidental duplication or omission in reports.
With reporting solution provided by Emedgene, creating comprehensive Clinical Reports is a piece of cake.✨ All the relevant case- and variant-level information is automatically populated to the corresponding sections of the report.
Note: Emedgene offers the capability of customizing Clinical Reports upon request. We tailor Report templates for any use case according to your SOPs and aesthetic sense.
Includes (numbers indicate ):
Patient details: Patient's name [1], date of birth [2], sex [2] and MRN [1];
Technical sample details: Specimen's type [1] and quality [3], dates collected [1] and received [1];
Provider details: Lab number [1], ordering physician's name [1];
Results summary gives a general overview of the test result:
Test result summary [4];
Secondary ACMG findings summary [4];
Interpretation summary [4];
Recommendations [4].
Detailed results highlight the genetic testing findings:
Basic sequence variant details:
Gene [3],
Genomic location [3],
Test details:
Test methodology [5];
Test limitations [5].
The References [9] section lists all the PubMed citations mentioned in the report. References will be auto-formatted if the PMID is supplied in the report.
The Signatures section documents who and when generated the report [3].
After you completed the , you may want to have a look at the Report Preview before finalizing a case. To do this, click on the eye button located rightmost on the , select a template and click Preview.
You can download the report preview in a .pdf or .odt format.
After you changed to Finalized, you can Generate Report. All the generated reports are saved per case. Click on the printer button on the , select Create New or choose a previously generated report (if any), then select a template and click Generate.
You can download the report in a .pdf or .odt format.
[1] - API;
[2] - filled in while ; displayed in ; for non-finalized cases;
[3] - automatically inferred by Emedgene,
[4] - filled in in the Case Interpretation widget while ,
[5] - fixed text,
[6] - manually assigned in the Pathogenicity box of the of the Variant Page,
[7] - depends on the evidence generated on the ,
[8] - automatically or manually filled in in the Variant Interpretation notes of the of the Variant Page,
[9] - in any of the free text fields you can add PMIDs in one of the following formats: PMID1234, PMID 1234, PMID:1234.
The Evidence page presents the most relevant evidence supporting the automatic variant classification generated by the AI Shortlist. This includes ACMG classification tags, variant details, gene-disease relationships, phenotype matches, and supporting literature. You can also manually review and edit evidence to tailor it to your case.
The Evidence page is available for:
Variants in the AI Shortlist (automatically)
Any manually tagged variant in the analysis
You can view teh Evidence Page from:
Click on the variant bar to open its dedicated Evidence page.
In the Evidence section, click the See evidence button under the Evidence box.
You can switch between two display modes:
Graph view: Offers an interactive visual of gene-disease-phenotype relationships, inheritance modes, and ACMG tags.
Text view: Displays structured evidence and citations for use in clinical reports or further notes.
AI Shortlist collects data from credible studies and public databases in an internal knowledge base that maps complex connections between variants, genes, mechanisms, diseases, and phenotypes.
Displays the main effect, HGVS nomenclature, zygosity (HET, HOM, HEMI, or REF), and de novo status if applicable.
Gene symbol, if the gene is tolerant to variation, and assumed inheritance mode in the case under review. This is suggested based on the observed level of genotype-phenotype co-segregation and inheritance mode of the genetic condition (reported or suspected).
In addition to the conventional inheritance modes (Autosomal Dominant, Autosomal Recessive, Compound Heterozygote Autosomal Recessive, X-Linked Dominant, X-Linked Recessive), the platform also employs Autosomal Dominant Partial Penetrance and Partial Autosomal Recessive designations.
Autosomal Dominant Partial Penetrance is used when the gene-associated condition is AD, and the variant is Het in the test subject and at least one of their parents. This suggests that the phenotypes may be due to incomplete penetrance of the genetic condition.
Partial Autosomal Recessive is used when the gene-associated condition is AR and the variant in the test subject is Het. This helps to account for the possibility that another causative variant is undetected - in the same (compound heterozygosity) or another (digenic inheritance) gene.
Name of the condition as sourced from OMIM, literature, or other databases. When multiple diseases are associated with a gene, users can manually select the one most relevant to the case or choose to add a custom disease.
Proband's phenotypes that match phenotypes reported for the suspected disease. Exact, indirect, and matches by ascendance are considered.
Phenotypes reported for the suspected disease but not observed in the proband.
Phenotypes observed in the proband but not known to be manifested as part of the suspected disease.
Follow the links to the primary sources to explore the evidence further. The links are in the References section (text view) and are accessible by hovering over the arrows (graph view).
Click the pencil icon in the top-left corner of the graph to:
Edit disease associations
Add or remove evidence boxes
Tailor interpretation to case-specific insights
Important Notes When Editing the Evidence Graph
After modifying the evidence graph on the variant page or within the candidates section, the phenotypic match strength indicators may no longer appear in the side panel or on the variant page.
This visual module links genes, diseases, and inheritance modes, providing an at-a-glance overview of your variant’s clinical context.
Easily switch the associated disease for reporting or interpretation.
The graph influences ACMG tags like PP4, PM5, and PVS1, depending on gene-disease pairings.
Connects with literature via LitVar2 integration.
Important Warning:
Changing the disease in the Evidence Graph does not automatically update inheritance mode. You must edit this manually to ensure consistency.
Add your own insights or justifications related to the variant, interpretation, or evidence decisions.
Notes are tag-specific and can support audit trails and future reviews.
Note changes are not logged in the Activity Panel—consider logging important insights as Comments instead.
All meaningful updates—including ACMG tag edits, classification changes, and disease graph modifications—are logged in the Activity Panel, ensuring full transparency for collaborative curation and audits.
Use Phenomeld scores (available as a filter and sortable column in Analysis Tools) to prioritize variants with high phenotype concordance.
When editing any ACMG tag, always click Save before editing notes to ensure no data is lost (especially for finalized cases).
Double-check that inheritance mode matches disease after editing the Evidence Graph.
The Evidence Page brings together automation, clinical reasoning, and interpretative flexibility, enabling users to make transparent, reproducible decisions in line with the latest guidelines—while giving you full control to adjust when needed.
Sequencing lab information section reports sequencing run technicalities as indicated during case creation:
Lab
Instrument
Reagents
Kit type
Expected coverage
Protocol
Coverage for a region is based on the median coverage of each gVCF block. If a region spans multiple blocks, the reported value is the average of those medians.
Within a region (like an exon), you’ll often see multiple blocks. Emedgene aggregates them to show you:
Average depth
Minimum depth
Depth range
Occasionally, some blocks may be unusually large and may miss internal variation—for example, in genes like XIAP, one block could span an entire region despite having uneven coverage inside.
≤10x
≤20x
or All
Download tables or genomic coordinates for regions with poor coverage.
Click More details to open a pop-up with exact genomic coordinates of low-coverage blocks.
Min Depth
Lowest depth in the region (for gVCF-based cases: lowest avg depth in a block)
Max Depth
Highest depth observed
Average Coverage
Mean read depth across the region
% ≥3×
Percent of base pairs with at least 3x coverage
% ≥20×
Percent of base pairs with at least 20x coverage
Length
Region length in base pairs





High: Includes only high quality variants with read depth >10
High
Forced Genotyping
Star Allele
STR Repeat Expansion
SV Split-End
Targeted
MRJD
Array
Unknown
Note: This is especially useful for filtering CNVs from different callers (e.g., DRAGEN Read-Depth vs. SV Caller) to apply separate noise databases or QC settings.










Further Investigation (Uncertain)
Unsolved (Negative)
The outcomes are grouped into two supercategories:
Resolved → Confidently Solved, Likely Solved, Further Investigation
Not Resolved → Unsolved
These outcomes contribute to your lab’s diagnostic yield calculations.
Variants now appear under all tags they have been assigned, not just the last one.
If a variant is already selected under Tag A, it will also appear as selected when filtering by Tag B.
The tag dropdown shows only tags used in the case, with the number of variants per tag displayed (e.g., Most Likely (10)).








Case type [2];
Clinical information: Indication for testing [2] or, if it's not available, Proband's phenotypes [2]; Secondary findings requested [2]: Yes/No.
Zygosity/Inheritance [3] (Zygosity in Proband and their relatives),
Classification [6] (Pathogenicity),
Condition [7] (Disease and Inheritance mode if available).
Basic copy number variant details:
Chromosome region [3],
Type: DEL/DUP [3],
Genes [3],
Zygosity/Inheritance [3] (Zygosity in Proband and their relatives),
Minimum length [3],
Classification [6] (Pathogenicity).
Individual sequence variant interpretations:
Basic variant details [3]: gene, genomic location, coding sequence and protein sequence change HGVS notations, exon involved, variant's main effect, Prediction, Conservation and Splice Prediction scores, gnomAD population statistics,
Associated diseases [3] - all the diseases known to be associated with the gene,
Quality [3]: Zygosity, base quality, depth in Proband and their relatives,
Summary [8].
Individual copy number variant interpretations:
Chromosome region [3],
Type: DEL/DUP [3],
Minimum length [3],
Zygosity in Proband [3],
Classification [6] (Pathogenicity),
Summary [8].
Gene interpretation [4]








Changing the disease in the evidence graph does not automatically update the inheritance mode. If the inheritance pattern differs for the new disease, you must manually adjust the inheritance setting to ensure accurate interpretation.
For CNVs >20MB, perform manual evaluation, as automation and tagging will not apply.









Suspected Disease Penetrance.
Case info screen:
Genes list;
Case Type.


(overall)
:
Average coverage
% Bases with coverage >10x
% Bases with coverage >20x
(overall)
For eligible cases, users can review the results of DRAGEN QC: interactive DRAGEN QC report and DRAGEN QC metric files.
DRAGEN QC for array samples is available from version 100.39.0 onwards.
Emedgene uses ExpansionHunter by DRAGEN to call short tandem repeats (STR), also known as repeats expansions.
Thirty clinical genes associated with diseases caused by repeat expansion are called in DRAGEN version 3.9 and presented in the platform. Those genes are: AFF2, AR, ATN1, ATXN1, ATXN10, ATXN2, ATXN3, ATXN7, ATXN8OS, C9ORF72, CACNA1A, CBL, CNBP, CSTB, DIP2B, DMPK, FMR1, FXN, GIPC1, GLS, HTT, JPH3, NIPA1, NOP56, PABPN1, PHOX2B, PPP2R2B, RFC1, TBP, TCF4.
Exact sizes of short repeats are identified from spanning reads that completely contain the repeat sequence.
When the repeat length is close to the read length, the size of the repeat is approximated from the flanking reads that partially overlap the repeat and one of the repeat flanks.
If the repeat is longer than the read length, its size is estimated from reads completely contained inside the repeat (in-repeat reads). In-repeat reads anchored by their mate to the repeat region are used to estimate the size of the repeat up to the fragment length. When there is no evidence of long repeats with the same repeat motif elsewhere in the genome, pairs of in-repeat reads can also be used to estimate the size of long (greater-than-fragment-length) repeats.
Note: ExpansionHunter for STR calling is designed for use in PCR-free WGS only. While STR variants might be called in exome cases, the limitations are currently unknown and it is therefore not recommended for use.
In light of our recent experience and an internal investigation by the Illumina’s scientific team, we believe it is appropriate to enable prioritization for a subset of STR loci, but not all loci typed by DRAGEN. This is due to technical genotyping challenges and/or lack of scientific evidence of pathogenicity for the remaining loci. Current list of genes where STR may be tagged when appropriate is provided below:
The In silico predictions filters allow filtering variants based on scores from computational prediction tools. These filters help prioritize variants with potential functional or regulatory impact inferred from predictive models.
The filters can operate in a Simple or Advanced mode.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
Refine the variant list by setting minimum thresholds for aggregated in silico prediction scores:
Missense prediction (All, Neutral, Damaging)
Conservation
Fine-tune the variant list by setting minimum thresholds for particular in silico prediction tools:
Minimum threshold for REVEL missense variant pathogenicity score.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
PrimateAI-3D missense variant pathogenicity prediction category:
None
Benign
Minimum threshold for CADD Phred deleteriousness score. Applicable for SNVs, MNVs, and indels, both coding and non-coding.
Range: 0-99 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for missense Z-score indicating a gene's intolerance to missense variants.
Range: -8 to 8 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for PLI score indicating a gene's probability of being intolerant to loss-of-function variants.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for GERP RS conservation score.
Range: -12.36 to 6.18 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for SpliceAI delta scores for splice acceptor site gain.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for SpliceAI delta scores for splice acceptor site loss.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for SpliceAI delta scores for splice donor site gain.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
Minimum threshold for SpliceAI delta scores for splice donor site loss.
Range: 0-1 using the slider
Custom value: Enter a number within the range in the input field
When are reset to default, The In silico predictions filters are not applied.
Splicing (Low, Moderate, High)
Damaging











ATXN1
Spinocerebellar ataxia 1 (SCA1)
Autosomal Dominant
CAG
ATXN2
Spinocerebellar ataxia 2 (SCA2)
Semi-dominant
CAG
ATXN3
Spinocerebellar ataxia 3 (SCA3)
Autosomal Dominant
CAG
ATXN7
Spinocerebellar ataxia 7 (SCA7)
Autosomal Dominant
CAG
CACNA1A
Spinocerebellar ataxia 6 (SCA6)
Autosomal Dominant
CAG
DMPK
Myotonic dystrophy 1 (DM1)
Autosomal Dominant
CTG
DMPK
Myotonic dystrophy 1, mild
Autosomal Dominant
CTG
FMR1
Fragile X tremor/ataxia syndrome (FXTAS) or Premature Ovarian Failure (POF)
X-linked
CGG
FMR1
Fragile X Syndrome (FXS)
X-linked
CGG
HTT
Huntington's disease (HD)
Autosomal Dominant
CAG
PPP2R2B
Spinocerebellar ataxia 12 (SCA12)
Autosomal Dominant
CAG
TBP
Spinocerebellar ataxia 17 (SCA17)
Autosomal Dominant
CAG
C9orf72
Amyotrophic lateral sclerosis and/or frontotemporal dementia (FTDALS1)
Autosomal Dominant
GGGGCC
AR
Spinal and bulbar muscular atrophy (SBMA)
X-linked
CAG
FXN
Friedreich ataxia (FRDA)
Autosomal Recessive
GAA
CNBP
Myotonic dystrophy 2 (DM2)
Autosomal Dominant
CCTG
JPH3
Huntington disease-like 2 (HDL2)
Autosomal Dominant
CTG
NOP56
Spinocerebellar ataxia 36 (SCA36)
Autosomal Dominant
GGCCTG
ATXN10
Spinocerebellar ataxia 10 (SCA10)
Autosomal Dominant
ATTCT
ATXN8OS
Spinocerebellar ataxia 8 (SCA8)
Autosomal Dominant
CTG
ATN1
Dentatorubral-pallidoluysian atrophy (DRPLA)
Autosomal Dominant

CAG
Viewed: Displayed in regular font weight. A variant is marked as viewed if the user opened the variant page before the case was finalized
Not viewed: Displayed in bold font weight
Note: After a case reanalysis, all variants appear as not viewed.
no
no
no
by the AI Shortlist
no
by a user
yes
The variant search box on top of the Filters/Presets panel allows you to quickly find specific variants within a case by applying customized filters.
Variant search uses AND logic with any active filters or filter presets.
This means that only variants matching all selected criteria—from both the search and the filters/presets—will be displayed.
You can apply multiple filters in variant search box, one at a time, from the same or different categories.
Individual search queries are combined under either:
AND logic
A variant must meet all selected criteria to appear in the results. This narrows your search.
Example
Search query:
Phenotype = Hyporeflexia AND Phenotype = Dilated cardiomyopathy AND
Phenotype = Calf muscle pseudohypertrophy
Combined gene search query: "FBN1" , "TGFBR1, TGFBR2, SMAD3, TGFB2, TGFB3" , "Ehlers-Danlos syndrome panel"
The query returns:
Combined phenotype search query: "Brainstem dysplasia", "Generalized-onset seizure", "Clinodactyly"
The query will return:
Combined disease search query: "Genitopatellar syndrome" , "Arthrogryposis, distal, type 3" , "Dysosteosclerosis"
The query returns:
Due to a current limitation, the dropdown may display duplicate entries for the same disease. To ensure complete results, please select all matching entries, not just one.
Combined variant notation search query: "chr1:27089776G>T" , "chr1:100AT>GC"
The query returns:
Combined genomic position search query: "chr1:27089776" , "chr11:2686616-2886620"
The query returns:
Use gene symbol searches when exploring CNVs; this can often give more reliable results than coordinate-based CNV queries.
Free text search is performed within variant characteristics using substring matching, meaning the query can match any part of a word. See the table below for example use cases.
Variants in gene(s) that are associated with all three specified phenotypes
OR logic
A variant will appear in the results if it meets any of the selected criteria. This broadens your search.
Example
Search query:
Gene = BRCA1
OR Disease = Breast-ovarian cancer, familial, 2
Search result will include:
Variants in the BRCA1 gene
Variants in gene(s) associated with Breast-ovarian cancer, familial, 2
Variants in the TGFBR1, TGFBR2, SMAD3, TGFB2, TGFB3 genes
Variants in the Ehlers-Danlos syndrome gene list
Variants in genes where at least one associated disease is Arthrogryposis, distal, type 3
Variants in genes where at least one associated disease is Dysosteosclerosis
chr1:100AT>GC variant
CNVs whose starting position either match chr1:27089776 or fall within chr11:2686616-2886620, inclusive of both start and end coordinates
Free text
Search by dbSNP ID
"rs2488992"
Variant with dbSNP ID "rs2488992"
Free text
Search by cytoband
"1p36.33"
Variants located within the 1p36.33 cytoband
Gene symbol
Search by a single gene name
"BRCA1"
Variants in the BRCA1 gene
Multiple gene symbols (batch)
Search multiple genes in one query
"BRCA1, BRCA2, UBE3A"
Variants in the BRCA1, BRCA2, UBE3A genes
Gene list
Search by a predefined gene list name
"Cardiomyopathy panel"
Phenotype
Search by a phenotype name
"Mandibular prognathia"
Variants in genes where at least one associated disease includes Mandibular prognathia as one of it's phenotypes
Disease
Search by a disease name
"Kabuki syndrome 1"
Variants in genes where at least one associated disease has a name that exactly matches the query disease
Disease inheritance mode
Search by a disease inheritance mode
"Autosomal dominant"
Variants in genes where at least one associated disease has an inheritance mode that matches the query
Specific SNV/Indel
Search by exact variant notation
"chr1:27089776G>T"
Variant that exactly matches the specified genomic position, reference allele, and alternate allele
Specific MNV (v100.39.0+)
Search by exact variant notation
"chr1:100AT>GC"
Variant that exactly matches the specified genomic position, reference allele, and alternate allele
Genomic position
Search by a single coordinate
"chr11:2686616"
SNVs/indels that match the specified genomic position
CNVs whose starting position matches the specified genomic position
Genomic range
Search by a range of positions
"chr11:2686616-2886620"
SNVs/indels whose positions fall within the specified genomic range, including both start and end coordinates
CNVs whose starting position falls within the specified genomic range, including both start and end coordinates
Free text
Search by variant main effect full name
"Stop lost"
Variants where the main effect is "Stop lost"
Free text
Search by variant main effect partial name
"Stop"
Variants where the main effect is "Stop lost", "Stop gained", "Stop retained variant"
Free text
Search by partial gene symbol
"CYP"

Variants in the genes included in the Cardiomyopathy panel gene list
Variants in genes whose symbols include "CYP" (cytochrome P450 genes)
no
yes
by the AI Shortlist
yes
by a user
When creating NGS 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.
Navigate to local directory containing metrics files for a specific sample.
Define sample name as a variable samplename="NA12878".
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:
Upload the metrics.tar.gz file to the storage location used for creating cases.
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.
DRAGEN report link is then available once your case has been delivered.
{
"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
}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 "*.correlation.txt.gz" -o -name "*.correlation.txt" -o -name "*.repeats.vcf" -o -name "*.ploidy.vcf.gz" -o -name "*.repeats.vcf.gz" -o -name "*.annotated_cyto.json" \) | xargs tar -czf "${samplename}.metrics.tar.gz"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.
Gene
Gene identifier.
SNV/Indel/single-gene CNV: An HGNC-approved gene symbol
Multi-gene CNVs: A list of HGNC-approved gene symbols and the number of genes included if only part of the list is shown.
Tip: If only the beginning of the list is displayed in the table, you can see the full gene list in the pop-up tooltip.
Variant type
Specifies whether the variant is SNV, Indel, CNV, SV, STR, or other.
Allows alphabetical sorting.
Main effect
Predicted effect(s) of the variant on protein structure and function (transcript-specific). By default the most severe effect is presented.
Allows alphabetical sorting
Disease
Lists the count of disease associations, mode(s) of inheritance, and the name of one of the diseases.
Tip: Hover over the line to see the full disease list in a pop-up window.
Allows alphabetical sorting.
Tag
Variant tag assigned by Emedgene or by a user.
Allows alphabetical sorting.
Known variants
Classification(s) of the variant in ClinVar and your curated variant database.
Allows alphabetical sorting.
Variant notes
Indicates if Variant interpretation notes are available.
Allows alphabetical sorting.
AI rank
Indicates potential causative variants: Most Likely Candidates and Candidates.
Variants with identical scores share the same rank. Ranges from 1 to 220; lower numbers indicate higher rank.
Case reanalysis causes Al ranks to be recalculated.
Allows numerical sorting.
Phenomatch score
Proprietary phenotypic match score ranging from 0 to 1.
Case reanalysis causes Phenomatch score to be recalculated.
Allows numerical sorting.
PhenomeId score
Proprietary phenotypic match score outperforming previous Phenomatch models. Ranges from 0 to 2. A score of 0 means no match, a score above 0.15 suggests a moderate match, and scores above 0.7 indicate a high phenotypic match.
Case reanalysis causes Phenomeld score to be recalculated.
Allows numerical sorting.
Proband quality
Overall score in proband.
SNV/Indel: Based on base quality, depth, mapping quality, and genotype quality
CNV: Based on CNV quality, size, and bin count
Allows alphabetical sorting.
Depth
Variant depth in proband.
SNV/Indel: Sequencing depth of coverage at the variant position
CNV: Depth of coverage across the CNV region
Allows numerical sorting.
Alternate read
Number of alternate reads.
Available only for SNVs.
Allows numerical sorting.
Allele bias
Percentage of reads that include an alternate allele out of all reads.
Available only for SNVs.
Allows numerical sorting.
Bin count
Number of bins supporting CNV detection.
Allows numerical sorting.
Allele freq
Indicates variant frequency category according to the highest allele frequency in public population frequency databases:
Private: 0
Rare: <0.01
Low Frequency: 0.01-0.05
Emedgene DB frequency (%)
Variant frequency in the Emedgene internal control database.
Allows numerical sorting.
Emedgene DB frequency (#)
Variant allele count in the Emedgene internal control database.
Allows numerical sorting.
gnomAD All AF
Overall alternative allele frequency across gnomAD populations (also called Total AF in the ).
Allows numerical sorting.
gnomaAD allele count
Number of observed alternate alleles in gnomAD dataset.
Allows numerical sorting.
gnomAD Hom/Hemi
Number of gnomAD subjects who are homozygous (autosomal or X-linked variant in a female) or hemizygous (X-linked variant in a male) for this variant.
Max AF (%)
The highest alternative allele frequency among all public population databases.
Note: Not to be confused with Max AF in that only considers gnomAD statistics.
Allows numerical sorting.
Prediction
Summarized in silico pathogenicity prediction score.
Tip: You can glance at the underlying scores in a pop-up tooltip.
Allows alphabetical sorting.
Conservation
Summarized nucleotide conservation score.
Tip: You can glance at the underlying scores in a pop-up tooltip.
Allows alphabetical sorting.
Splice prediction
Summarized splicing impact prediction score.
Tip: You can glance at the underlying scores in a pop-up tooltip.
Allows alphabetical sorting.
Coding change
HGVS-compliant coding sequence change notation.
Allows alphabetical sorting.
Protein change
HGVS-compliant protein change notation.
Allows alphabetical sorting.
Variant length
Variant size in kilobases (relevant for CNVs/SVs).
Allows numerical sorting.
Cytoband
Chromosomal cytogenetic band where variant is located.
Allows alphanumeric sorting.
ISCN
Cytogenetic description of a chromosomal abnormality, using the International System for Human Cytogenomic Nomenclature (ISCN).
Allows alphanumeric sorting.
Pathogenicity
Pathogenicity classification assigned in the .
Allows alphabetical sorting.
Manual classification
Displays pathogenicity classifications previously assigned by members of the organization to the same variant in earlier cases. Badge color indicates pathogenicity class while badge number indicates count.
Tip: hover over the badge to see pathogenicity.
Allows alphabetical sorting.
Networks classification
Displays pathogenicity classifications assigned by partnering organizations. Badge color indicates pathogenicity class while badge number indicates count.
Tip: hover over the badge to see pathogenicity.
Allows alphabetical sorting.
Proband zygosity
Variant zygosity status in the proband. Allows alphabetical sorting
Mother zygosity
Variant zygosity status in mother.
Allows alphabetical sorting
Father zygosity
Variant zygosity status in father.
Allows alphabetical sorting.
Mother quality
Overall score in mother.
SNV/Indel: Based on base quality, depth, mapping quality, and genotype quality
CNV: Based on CNV quality, size, and bin count
Allows alphabetical sorting
Father quality
Overall score in father.
SNV/Indel: Based on base quality, depth, mapping quality, and genotype quality
CNV: Based on CNV quality, size, and bin count
Allows alphabetical sorting.
Mother depth
Variant depth in mother.
SNV/Indel: Sequencing depth of coverage at the variant position
CNV: Depth of coverage across the CNV region
Allows numerical sorting
Father depth
Variant depth in father.
SNV/Indel: Sequencing depth of coverage at the variant position
CNV: Depth of coverage across the CNV region
Allows numerical sorting
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
Allows sorting by genomic start location.
Variant effect filters allow you to filter variants by consequence, ACMG pathogenicity class, and prior classifications in both internal and external clinical variation databases.
The filters can operate in a Simple or Advanced mode.
Simple and advanced filtering modes operate independently.
Even with similar settings, results may differ due to variations in filtering logic and options available.
Filter variants by the of their effect:
High
Moderate
Known variants: Variants that have been curated in public or private variant databases.
Filter variants by their specific .
Results include variants matching any selected effect.
Filter SNV variants by :
Pathogenic
Likely Pathogenic
Filter variants by pathogenicity class in ClinVar:
Pathogenic
Likely Pathogenic
Filter variants by pathogenicity class in your variant database:
Pathogenic
Likely Pathogenic
Filter variants by pathogenicity class in a maintained by your organization:
Pathogenic
Likely Pathogenic
Filter STR variants by gnomAD STR pathogenicity category:
Pathogenic
Intermediate
Limit results to variants with established pathogenicity in prior cases.
When are reset to default, the Variant effect filters are not applied.
Low
Modifier
Unknown
Drug response: Variants classified in ClinVar as impacting drug response.
Known pathogenic: Variants classified as pathogenic or likely pathogenic in public or private variant databases.
Uncertain Significance
Likely Benign
Benign
Note: Only tagged variants have an ACMG classification.
VUS
Likely Benign
Benign
Other
VUS
Likely Benign
Benign
Other
VUS
Likely Benign
Benign
Other
If your institution maintains multiple curated databases, each database will have its own filter.
Normal
Unknown









Polymorphism: >0.05
Allows alphabetical sorting.
Max AF (#)
The highest alternative allele count among all public population databases.
Note: Not to be confused with Max AF in Summary section that only considers gnomAD statistics.
Allows numerical sorting.
[Organization DB] AF (%)
Variant frequency in a specific historic or noise organization database.
SNV/Indel: Percentage of database samples carrying the variant
CNV/SV: Percentage of database samples containing overlapping CNV/SV events
Allows numerical sorting.
[Organization DB] AF (#)
Variant allele count in a specific historic or noise organization database.
SNV/Indel: Number of database samples carrying the variant
CNV/SV: Number of database samples containing overlapping CNV/SV events
Allows numerical sorting.