Emedgene
Illumina Connected Software
  • Get Started with Emedgene
    • Get started with Emedgene
    • How can Emedgene help you solve a case?
  • Emedgene analyze manual
    • Getting around the platform
      • Top navigation panel
      • Emedgene Applications menu
      • Dashboard
      • Settings
      • User roles
      • Help
      • Okta identity management
    • Managing data storage
      • Manage data storages
      • Manage Azure Blob data storage
      • Manage S3 credentials
      • Manage BaseSpace storage
      • Manage GCS storage (V37.0+)
      • Bring Your Own Bucket
      • Bring Your Own Key
    • Cases tab
      • Cases tab
      • Cases table
      • Case status
      • Browse and select cases
      • Case details
    • Creating a single case
      • Add a new case
      • Select sample type
      • Create a family tree
      • Family tree legend
      • Add a sample
      • Supported Variant callers
      • Adding patient info for the proband
      • Adding patient info for the non-proband samples
      • Secondary findings
      • Labeling a case
      • Gene list
      • Supported parental ethnicities
    • Creating multiple cases
      • Batch case upload from platform
      • CSV format requirements
      • Batch case upload via CLI
    • Reviewing a case
      • Individual case page
      • Individual case page: Top bar
      • Individual case page: Top bar
      • Candidates tab
      • Most Likely Candidates and Candidates
      • Genome Overview
      • Analysis tools tab
      • Variant table columns
      • Variant table
      • Variant search
      • Multiselection of variants and bulk actions (34.0+)
      • Download variants
      • Manually add variants to a delivered case
      • Filters/Presets panel
      • Filters
      • Presets
      • Preset groups
      • Variant Type Filters
      • Variant Effect Filters
      • Quality Filters
      • Polymorphism Filters
      • Gene Filters
      • Phenomatch Filters
      • Inheritance Filters
      • Zygosity Filters
      • User Filters
      • Evidence page
      • Phenotypic match strength
      • Lab tab
      • Versions tab
      • Editing an existing case
      • Finalizing a case
      • Clinical Report
      • Reflex genetic testing
      • Variant zygosity notations
      • STR calling and interpretation
    • Variant page
      • Variant page
      • Variant page top bar
      • Variant tagging widget
      • Variant activity panel
      • Desktop apps panel
      • Clinical Significance section
      • Summary section
      • Quality section
      • Visualization section
      • Population Statistics section
      • Related Cases section
      • CNV overlap percentage
      • Evidence section
      • ACMG SNV Classification wizard
      • Logic behind ACMG classification of SNVs
      • ACMG CNV Classification wizard
      • Variant page sidebar (2.29+)
    • Variant visualization setup
      • Enabling visualization for a VCF case
      • Integration between emedgene and desktop IGV
      • Loading alignment files to your desktop IGV (32.0+)
    • Analyze Network
      • Analyze Network Setup
      • Network sharing configuration
      • Case subject consent for extended sharing
      • Public vs Private network
      • Create a network
      • Set network data sharing policy
      • Leave a network
      • Delete a network
    • Settings
      • My settings
      • Management
      • User Management
      • Network
      • Organization Settings (33.0+)
    • Integrations
      • API Beginner Guide
      • Advanced API Implementations
      • API Key Generation
      • BSSH Integration
      • ICA Integration
      • Webhook Integration
  • Emedgene Curate Manual
    • Curate overview
      • Curate overview
      • Emedgene Applications menu
      • Curate navigation panel
      • Genome assemblies supported by Curate
    • Curate Variants
      • Curate Variants overview
      • Curate Variant table
      • Curate Variant page
      • How to add a variant to Curate
      • Curate Variant annotations in the case
    • Curate Genes (2.28+)
      • Curate Genes overview
      • Curate Gene table
      • Curate Gene page
      • How to add a gene to Curate
    • Import Curate annotations to the case (30.0+)
      • Import Curate Variant annotations to the case (30.0+)
      • Import Curate Gene annotations to the case (30.0+)
  • Frequently Asked Questions
    • All FAQ
      • Which browser should I use with Emedgene?
      • Emedgene annotations and update frequency
      • How do I use developer tools to collect logs?
      • Can I analyze Illumina Complete Long Reads in Emedgene?
      • How do I prepare VCF files generated by DRAGEN MANTA to be used as input for Emedgene?
      • Source of gnomAD data for small variants on GRCh38
      • How are MNVs handled on the platform?
      • Support for gene lists with up to 10,000 genes
      • Genomic Regions by Case Type
      • How do I analyze mtDNA variants?
      • Can I use exome data for CNV detection?
      • How does joint calling work on Emedgene?
      • What is the required format for a BED file defining a kit?
      • Which reference genomes can I use?
      • How do I move between organizations?
      • How do I check the version of my environment?
      • "Failed to generate report". What should I do?
      • How do I prepare VCF files generated by Dragen STR (ExpansionHunter) to be used as input?
      • How does Emedgene Analyze prioritize transcripts?
      • How does Emedgene Analyze merge variants from different sources?
      • Performance issue troubleshooting
      • How does Emedgene calculate variant effect and severity ?
      • How to I prepare metrics files generated by DRAGEN to be used as input for Emedgene
      • How are timekeeping and log timestamps kept accurate and consistent?
  • Release Notes
    • Workbench & Pipeline Updates
      • New in Emedgene V37.0 (February 20, 2025)
        • V37 Patches
      • New in Emedgene V36.0 (October 8 2024)
        • V36 Patches
      • New in Emedgene V35.0 (May 22nd 2024)
        • V35 Patches
      • New in Emedgene V34.0 (January 28th 2024)
        • V34 Patches
      • New in Emedgene V33.0 (September 6th 2023)
        • V33 Patches
      • New in Emedgene V32.0 (June 8th 2023)
        • New pipeline 32 (June 8th 2023)
        • V32 Patches
      • More release notes
        • New in emedgene 31 (March 1st 2023)
        • New in emedgene 30 (January 8th 2023)
        • New in emedgene 2.29 (August 25 2022)
        • New pipeline 5.29 (May 1st 2022)
        • New in emedgene 2.28 (May 1 2022)
        • New in emedgene 2.27 (March 7, 2022)
        • New in emedgene 2.26 (Dec 14, 2021)
        • New in emedgene 2.24-2.25 (Aug 11, 2021)
        • New in emedgene 2.23 (Jun 15, 2021)
        • New in emedgene 2.19-2.22 (Apr 8, 2021)
        • New in emedgene 2.16-2.19 (Dec 7, 2020)
        • New in emedgene 2.12-2.16 (Oct 18, 2020)
    • Knowledgebase Updates
      • 2025
        • Variant Databases (March 30th 2025)
        • Zoidberg 77 (March 17th 2025)
        • Zoidberg 76 (February 3rd 2025)
        • Zoidberg 75 (January 6th 2025)
      • 2024
        • Variant Databases (December 8th 2024)
        • Zoidberg 74 (December 2nd 2024)
        • Zoidberg 73 (October 21th 2024)
        • Variant Databases (September 22nd 2024)
        • Zoidberg 72 (September 10th 2024)
        • Variant Databases (July 21st 2024)
        • Zoidberg 71 (July 24th 2024)
        • Zoidberg 70 (June 3rd 2024)
        • Zoidberg 69 (April 19th 2024)
        • Variant Databases (April 9th 2024)
        • Zoidberg 68 (March 18th 2024)
        • Variant Databases (February 5th 2024)
        • Zoidberg 67 (January 28th 2024)
        • Variant Databases (January 5th 2024)
      • 2023
        • Zoidberg 66 (December 24th 2023)
        • Variant Databases (December 3rd 2023)
        • Zoidberg 65 (November 21th 2023)
        • Variant Databases (November 5th 2023)
        • Zoidberg 64 (October 24th 2023)
        • Variant Databases (October 8th 2023)
        • Zoidberg 63 (September 18th 2023)
        • Variant Databases (September 5th 2023)
        • Zoidberg 62 (August 23th 2023)
        • Zoidberg 61 (August 16th 2023)
        • Variant Databases (August 6th 2023)
        • Zoidberg 60 (July 30th 2023)
        • Variant Databases (July 2nd 2023)
        • Zoidberg 59 (June 18th 2023)
        • Variant Databases (June 4th 2023)
          • Variant Databases (May 7th 2023)
        • Zoidberg 58 (May 21th 2023)
        • Zoidberg 57 (April 16th 2023)
        • Variant Databases (April 2nd 2023)
        • Zoidberg 56 (March 19th 2023)
        • Variant Databases (March 11th 2023)
        • Zoidberg 55 (February 19th 2023)
        • Zoidberg 54 (January 16th 2023)
    • Change log
      • Change log pipeline v34
      • Change log pipeline 31
      • Change log workbench 31
      • Change log pipeline 30
      • Change log workbench 30
      • Change log workbench 2.29
      • Change log pipeline 5.29
      • Change log workbench 2.28
  • Legal
    • Privacy, Security & Compliance
    • Release Policy
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Frequently Asked Questions
  2. All FAQ

How does Emedgene calculate variant effect and severity ?

PreviousPerformance issue troubleshootingNextHow to I prepare metrics files generated by DRAGEN to be used as input for Emedgene

Last updated 2 months ago

Was this helpful?

Variant effect

For each variant that is mapped to the reference genome, Emedgene uses Ensembl’s Variant Effect Predictor (VEP) and the RefSeq (NCBI) library of transcripts to calculate variant effect. VEP uses a set of consequence terms defined by the , including immediately recognizable terms like “missense_variant” and “frame_shift_variant” as well as some more esoteric ones like “non_coding_transcript_exon_variant”.

The full list of terms, along with detailed descriptions and severity impact categories can be found in the below.

Importantly, each variant has a "main_effect" and "main_gene" chosen based on the most prioritized transcript for this variant. Transcript prioritization depends on many different parameters and on different Emedgene pipeline versions as described .

Variant severity

Variant severity, also known as variant impact, is a subjective assessment of the severity of a variant consequence.

Severity is usually categorized as modifier, low, moderate or high:

  • Modifier severity is used for non-coding variants or variants affecting non-coding genes, where predictions are difficult or there is no evidence of impact. Inter-genic and non-coding variants are classic examples.

  • Low severity is used for variants that are assumed to be mostly harmless or unlikely to change protein function. This includes synonymous variants.

  • Moderate severity is used for non-disruptive variants that might change protein effectiveness, such as missense variants and in-frame insertions/deletions.

  • High severity is used for variants that are assumed to have a disruptive impact on abundance protein, such as by causing protein truncation, loss of open reading-frame, and/or triggering nonsense mediated decay.

Most of the time, variant effect and variant severity on Emedgene are consistent with VEP. However, genomics is a field defined by exceptions. There are key factors, outlined below, the Emedgene genetic team believes are critical to account for when assigning severity.

For small variants (SNV):

  1. Splice prediction: Small variants will be upgraded to HIGH severity if its splicing prediction is high (dbscSNV > 0.6 or max spliceAI > 0.8) or MODERATE if its splicing prediction is moderate (max spliceAI > 0.2 or dbscSNV > 0.5).

  2. Conservation: Synonymous variants and splice region variants that are highly conserved (GERP score > 0.9 or PhastCons100 > 0.2) will be upgraded to MODERATE.

  3. Non-coding RNA disease genes: The severity of a small variant will be upgraded to MODERATE if the variant is within a list of RNA genes known to be associated with disease. The current list of RNA genes is:

ATXN8OS, GNAS-AS1, H19, HELLPAR, KCNQ1OT1, LINC00237, LINC00299, MEG3, MIAT, MIR137, MIR140, MIR184, MIR19B1, MIR204, MIR2861, MIR4718, MIR605, MIR96, MIR99A, RMRP, RNU12, RNU4ATAC, SNORD116-1, SNORD118, TERC, MT-TF, MT-RNR1, MT-TV, MT-RNR2, MT-TL1, MT-TI, MT-TQ, MT-TM, MT-TW, MT-TA, MT-TN, MT-TC, MT-TY, MT-TS1, MT-TD, MT-TK, MT-TG, MT-TR, MT-TH, MT-TS2, MT-TL2, MT-TE, MT-TT, MT-TP, RNU7-1*, RNU4-2*. &#xNAN;*Added in V35.2

For CNV/SV:

VEP annotates CNVs with overlapping genomic features and designates them with the following effects: transcript amplification (DUP), feature elongation (DUP, INS), feature truncation (DEL), and transcript ablation (DEL). However, the severity assigned by VEP for CNVs does not reflect the complexity of CNV effects on protein function and in our experience is not suitable for genome analysis and filtering.

The region annotation is then used to assess severity for CNV and SV as follow:

High
Moderate
Low
Modifier

Deletion (DEL)

Coding regions

Clinical Regions and not in Coding regions

Full gene and not in Clinical Regions

No overlap with any BED

Gain (DUP)

Intragenic (coding regions but not entire gene region)

Coding Regions / Clinical Regions not intragenic

Full gene and not in Clinical Regions

No overlap with any BED

Insertion (INS)

Coding regions

Clinical Regions and not in Coding regions

Full gene and not in Clinical regions

None

Table 1: CNV/SV severity table. For each category of CNV/SV, the types of regions that overlap a given variant required to trigger the severity classification are shown.

For STR variants:

Emedgene is using an internal annotation for STR variants. More details can be provided by request to techsupport@illumina.com.

Known limitations

  • List of RNA genes known to be associated with disease is updated overtime as part of pipeline update.

  • Emedgene does not provide VEP annotation for non-coding regulatory data.

  • The “main effect” filter under the advanced “variant effect filters” in Emedgene UI represents the effects categorized by the relevant severity. It should be noted that the following effects in the advanced filter are missing. They will be added in V34.6 and V35.3.

Effect name
Severity

splice_donor_5th_base_variant

LOW

splice_donor_region_variant

LOW

splice_polypyrimidine_tract_variant

LOW

coding_sequence_variant

MODIFIER

mature_miRNA_variant

MODIFIER

NMD_transcript_variant

MODIFIER

coding_transcript_variant

MODIFIER

regulatory_region_ablation

MODIFIER

regulatory_region_variant

MODIFIER

intergenic_variant

MODIFIER

sequence_variant

MODIFIER

On Emedgene, variants are annotated in regards to its overlap with three different types of regions: ‘coding regions’, ‘clinical regions’, and ‘full gene’ region (see for a more detailed description about the BED files used in the system).

Sequence Ontology (SO)
link
here
here