Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Add new case page > Case info screen > Select genes list
You can limit analysis to a gene list in the platform while creating a case. Choose between:
No limitation of the analysis.
The list is automatically built from genes related to the HPO terms you entered for the case (per Emedgene knowledge base).
Select one of the previously added gene lists from a dropdown list.
Generate a new virtual panel: add a List title and then add all the gene symbols one by one (Selection mode) or in a batch (Batch mode).
Note: Please use the up-to-date gene symbols approved by the Hugo Gene Nomenclature Committee. When adding gene symbols in a Batch mode, those genes that do not comply with HGNC standards will be automatically excluded from the gene list. These genes will appear for 3 seconds in a black error box at the bottom of the screen.
For each gene please follow the steps described below: Enter a gene symbol in the search box in the right panel (Candidate Genes) and select a matching symbol from a dropdown menu.
After selecting batch mode, paste a list of comma-separated gene symbols in the search box in the right panel (Candidate Genes).
You can choose between two different modes of a gene list feature:
The default option.
Analysis is limited to the selected gene panel, no variants in other genes are considered in the results. If this in silico panel is used for analysis of exome or genome data, the gene restriction may be lifted during manual analysis to "open-up" the entire exome or genome for analysis.
Enabled through checkbox.
Analysis is performed for variants in all the genes. Variants in the targeted genes get upgraded scores during prioritization by the AI Shortlist algorithm.
To filter variants by the gene list, or remove the gene list restriction after the case has been delivered, go to the Analysis tools > Filters > Gene Filters > Candidate Genes filter.
If you have run a case in All genes mode, you still can filter variants by a gene list. Go to Analysis tools > Presets > Gene Lists and select a list of interest. The Gene Lists filter presets can be defined by organization's manager.
Alternatively to creating a gene list filter in Presets, create and manage gene lists in Settings > Management > Gene lists.
First, fill in the List title and click Add button. Then add the gene symbols one by one (Selection mode) or in a batch (Batch mode).
Selection mode - for each gene please follow the steps described below: Enter a gene symbol in the search box (Candidate Genes) and select a matching symbol from a dropdown menu.
Batch mode: Paste a list of comma-separated gene symbols in the search box (Candidate Genes).
When you finished, press Save.
To view the Gene list in read-only mode, click on its name. By pressing the corresponding icons next to the Gene list's name, you can duplicate, edit or delete it. If a gene list has already been used by a case in the platform, you will only have the possibility to duplicate it.
Add new case page > Family tree screen > Create family tree panel
Build a pedigree via the visual tool.
It is ideal that a proband selected for case analysis is affected and has disease phenotype(s).
You can add a Father, a Mother, a Sibling, or a Child to any family member, starting with the Proband. To do this, choose their icon, then click on the Add family member button in the bottom right corner of the pedigree builder to select a family member.
More information about the pedigree symbols can be found here.
To delete a family member, choose their icon, then click on the Delete Subject button in the top right corner of the Add patient information panel.
Note: There is no technical limit on the size or number of generations for a family tree.
Emedgene provides the tightest integration with DRAGEN for germline variation analysis, providing accuracy, comprehensiveness, and efficiency, spanning variant calling through interpretation and report generation.
DRAGEN | Emedgene | Available Callers |
---|---|---|
The Emedgene platform supports a variety of variant callers and applies specific quality parameters for each. The quality assessment is an essential step in the Emedgene pipeline because variants with low quality will not be considered by the AI components.
If the variant caller is not supported or not recognized, a default quality function will be applied. The default parameters are built on GT (genotype), depth (DP) and allele bias (AB). These fields are mandatory, and their absence will induce “Low quality” for all variants.
The following variant callers are currently supported on the Emedgene pipeline, providing a header with the variant caller command line should be present within the VCF headers.
Additional callers can be supported on demand.
Var caller / VCF | Supported versions | Notes | Calling Methodology |
---|---|---|---|
Internally the list is also called a list of Emedgenizer / Emedgenizers. Emedgenizer means to normalize a VCF to an expected format for the system.
Add new case page > Family tree screen > Add patient information panel > Patient info section
Note: The fields marked with (*) are mandatory.
Note: Please omit the Patient ethnicities field for non-proband samples.
Options: Male, Female, Unknown.
Indicates the family relationship of a subject to the Proband automatically inferred from the pedigree. Options: Father, Mother, Sibling, Child, Other.
Expected format: mm/dd/yyyy.
Mark the checkbox if you want to exclude the sample from the AI Shortlist analysis and Inheritance filters while preserving genotype data.
If a sample shares some phenotypes with the Proband, you can copy them by checking this box. Proband's phenotypes will appear in a newly created Related Phenotypes section. To remove any of the proband's phenotypes not observed in a current individual, click the ☒ button next to the HPO term in the Related Phenotypes section.
Note: A popup notification will appear at the bottom of the page if any input HPO term or HPO ID is unknown.
Phenotypes not shared with a Proband. They can be added one by one (Selection mode) or in batch (Batch mode).
Please follow the steps described below for each phenotype:
Enter an HPO term (e.g., Hypoplasia of the ulna), an HPO ID (e.g., HP:0003022), or a descriptive phenotype name (e.g., Underdeveloped ulna) in the search box;
Select a matching term from a dropdown menu and press Complete after you've added all the terms.
Paste a list of comma-separated HPO terms or HPO IDs (🆕 32.0+) in the search box and press Complete.
With version 33.0 and later, you have the flexibility to manage Case labels at any time: create, add, or remove them directly in the Cases table.
The organization's custom Case labels must be assigned while creating a case, in the Case info screen of the Add new case flow.
The desired Case labels should be created prior to case creation by the organization's manager in the Organization settings.
Once a case is created, Case labels cannot be removed or added.
Add new case page > Family tree screen > Add patient information panel > Patient info section
Note: The fields marked with (*) are mandatory.
Options: Male, Female, Unknown.
The default fixed value for Proband is Test Subject.
Expected format: mm/dd/yyyy.
Options: Affected, Healthy.
The default value for Proband is Affected, but you may change it to Healthy.
To add all relevant phenotypes for the Proband, use one of the following methods:
Automatically infer disease-associated phenotypes (see Proband Suspected Disease Condition below).
Note: the maximum permissible number of Proband Phenotypes is 100.
Please follow the steps described below for each phenotype:
Enter an HPO term (e.g., Hypoplasia of the ulna), an HPO ID (e.g., HP:0003022), or a descriptive phenotype name (e.g., Underdeveloped ulna) in the search box.
Select a matching term from a dropdown menu and press Complete after you've added all the terms and additional patient information below.
Paste a list of comma-separated HPO terms or HPO IDs (🆕32.0+) in the search box and press Complete.
Notes:
A popup notification will appear at the bottom of the page if any input HPO term or HPO ID is unknown.
Only phenotypes from the 'Phenotypic abnormality' HPO branch are currently supported.
In the Clinical Notes section upload a description of the clinical presentation in .pdf, .xls, .txt, .doc, .jpeg, or .jpg format. Among the extracted HPO terms for Phenotypes and Diseases select the ones you want to add to Proband's Phenotypes.
Enter the disease name in the search box, select a matching term from a dropdown menu and press Complete. All the associated phenotypes will be automatically added to the Proband Phenotypes. To remove any phenotype described for the disease but not observed in your patient, click the ☒ button next to the HPO term in the Proband Phenotypes list.
Enter the suspected disease penetrance as a percentage.
Select the appropriate category to indicate the severity of the disease symptoms observed in the patient: Mild, Moderate, Severe, Profound.
Mark the checkbox if applicable.
Note: If consanguinity is identified in the Proband's parents, but this box is not selected in case creation, this will result in a discrepancy alert in the Lab tab.
Paternal and Maternal. Enter the ethnicity name in the search box and select a matching term from a dropdown menu.
Add new case page > Family tree screen > Create family tree panel > Show Secondary Findings
While creating a case, you can choose if you want Secondary (Incidental) findings in the Proband to appear in the results.
These are known or expected pathogenic variants in the genes that are unrelated to the primary purpose of the testing. The secondary finding genes list includes:
81 genes (Miller et al. 2023) on versions 33.0+;
78 genes (Miller et al. 2022) on versions <33.0.
Ethnicities of the proband's mother and father can be specified during the UI case creation. Starting from version 32.0.0, this can also be accomplished via API case creation. Please refer to the following list of supported ethnicities.
While adding a new case, you will build a pedigree and annotate each of the samples with data required for analysis ( > Family tree screen).
After the case has been created, the family tree is available in the panel (righthand panel of the Cases page).
Icon fill color in other pedigree members indicates the presence or absence of the proband's phenotypes in a present sample (regardless of the potential presence of additional unrelated phenotypes):
Filled - the individual is affected by all of the proband's phenotypes;
Half-filled - the individual is affected by some of the proband's phenotypes;
Empty - the individual is not affected by any of the proband's phenotypes.
Icon color intensity denotes whether sample files have been uploaded for the particular individual:
Full color - the sample has files loaded in the case;
Faded color - no sample files are available.
Icon line type indicates whether the sample is considered or excluded during analysis (relevant to samples with uploaded files only):
Solid - the sample is included in the analysis;
Dashed - the sample is ignored by Inheritance filters and the AI Shortlist algorithm, but you still can explore its genotypes.
> Family tree screen > Add patient information panel > Add sample section
You can choose one of the following options:
Existing sample - pick one of the samples already loaded on the platform
Upload New Sample - upload files from your PC and enter sample name
Choose from storage - choose files from your cloud storage and enter sample name
No sample - postpone uploading files but proceed with case creation or skip uploading files for family members other than Proband
Note: A case won't run if Proband sample files are missing. However, sample files are not mandatory for the rest of the family members (although highly recommended).
Note: When you are loading sample files from your PC or choosing them from the storage, and there is more than one file per sample, please ensure that all the necessary files are simultaneously selected in the upload pop-up. You may only select one file type per case (i.e. you may not select both a .vcf and a .bam at the same time).
This section will guide you through adding new cases to the Emedgene platform.
Caution: Please note that refreshing or leaving the page, exiting the Add new case tab, or power failure of your computer before you've completed adding a new case will result in loss of the case creation progress.
Click on the Add new case button on the .
At the page, select the file type for your case analysis. Click Next to proceed to the Family tree panel.
The page is divided into two panels: Create family tree (left) and Add patient information (right).
In the Create family tree panel (left):
Add Clinical Notes (optional) in a free text panel. In this section, you can record additional clinical information that does not fall under the other categories or provide further details that can give context and help solve the case.
You have an option to upload a file that includes description of the clinical presentation (.pdf, .xls, .txt, .doc, .jpeg, .jpg formats are supported). HPO terms for Phenotypes and Diseases are extracted from the files and can be added to Proband's Phenotypes in Patient info section.
You may select suspected Inheritance mode(s). This is for the case record and won't be used during analysis.
In the Add patient information panel (right) for each of the family members:
Fill in a sample name (for cases starting from VCF, this must correspond to the corresponding proband or family member header within the file);
Click Next to proceed to the Case info screen.
In the Case info screen:
Select case type (Custom Panel, Exome, Whole Genome, or other). When running cases as Exome, variants outside exons ±50 bp are filtered out and won't appear in the results.
Pick whether you want Carrier Analysis to be carried out (checkbox). Carrier analysis requires you to provide us with a targeted genes list.
Sequencing Information (Choose from existing kit, No kit). You can indicate if there was an Enrichment Kit used if you wish to compare the breadth and depth of coverage to that expected for the kit used. RefSeq coding regions will be used as a reference if no kit is provided. This option is relevant for Custom Panel and Exome case types. In the Kit info section, fill in the Enrichment Kit and optionally Lab, Machine, Sequencing reagents, and Expected coverage.
Optional: Additional case info:
Indication for testing. Add free-text notes.
Label. Add labels to your case. You can choose among the labels created beforehand by your organization's manager. Labels cannot be added after case creation.
Summary: confirm the selected case type and genes list before completing case creation.
Click Next to complete case creation.
Caution: Pressing Next at this stage will create a case, so please ensure that you've carefully checked all the information. After the case is delivered, you will only be able to edit the Proband phenotypes.
In the Done screen:
The Case ID is displayed;
> Select sample type screen.
You can select the sample's file type from the given options:
FASTQ: .fastq.gz, .fq.gz, .bam, .cram.
Project VCF: .pvcf, .vcf, .vcf.gz, .pvcf.gz
VCF: .vcf, .vcf.gz.
Build a using the visual tool;
Select whether you want in Proband to appear in the AI Shortlist analysis results (checkbox).
;
;
Select (All genes, Phenotype based genes, Existing gene list, Create a new gene list) - indicate if you want the analysis to be limited to a specified list of genes.
Select : We can implement different combinations of to be used for different case types (i.e. Presets for exome may be different from Presets for genome) as defined by your SOPs to further streamline case review.
🆕 34.0+: If the user does not select a Preset group, the system automatically assigns the to the case. The default Preset group is indicated by the word "default" in parentheses after its name.
Confirm (32.0+).
Add participants to your case - subscribe your colleagues to notifications on change.
V36.0
SNV, CNV, STR, SV, Targeted, MRJD, JSON PGx*
V35.0
SNV, CNV, STR, SV, SMN, JSON PGx*
4.2
Recommended: V34.0
SNV, CNV, STR, SV, SMN
4.0
Recommended: V34.0
SNV, CNV, STR, SV
3.10
Recommended: V34.0
SNV, CNV, STR, SV
3.6-3.9
Recommended: V34.0
SNV
AED CNV
N/A
Affymetrix Extensible Data. converted to VCF
CNVReadDepth
5.12, 5.20
SmallVariant
N/A
SmallVariant
1.38
CNVReadDepth
N/A
SmallVariant
N/A
CNVReadDepth
CNVReporter
0.01
CNVReadDepth
1.0
CNVReadDepth
N/A
CNVReadDepth
Multi-Sample Viewer:1.0.0.71
Unknown
1.0.0
SmallVariant
1.2.0, 1.1.0, 1.0.0
V37.0 and up
Array
N/A
SVSplitEnd
0.1
CNVReadDepth
ExomeDepthAM
0.1
Private fork of ExomeDepth
CNVReadDepth
N/A
SmallVariant
3, 3.4, 3.5, 2014, 4, 4.1
SmallVariant
GATK Mutect
N/A
SmallVariant
Scramble
Running: scramble2vcf.pl
SmallVariant
1.4
SmallVariant
4.x, 5.x and not: 5.12, 5.20
SmallVariant
2.2.0
SVSplitEnd
N/A
SmallVariant
2.X
SmallVariant
2.1.1
SVSplitEnd
2.2.4
SmallVariant
2.2.4
SVSplitEnd
2.X
SVSplitEnd
5.2.9
SmallVariant
201808, 201911, 202010
SmallVariant
201808.03
SmallVariant
2.0.6
SVSplitEnd
0.0.2
SmallVariant
2.0.1
CNVReadDepth
2.4.5
SmallVariant
N/A
SmallVariant
N/A
SVSplitEnd
A "Afghan Jews" "Afghani" "African" "African American" "Afro-Brazilian" Alaska Native" "Algerian" "Algerian Jews" "Amish" "Anatolian" "Arab" "Argentinian/Paraguayan" "Armenian" "Ashkenazi Jews" "Asian" "Asian Brazilian" "Australian Native" "Azerbaijan Jews" | B "Bedouin" "Bengali/Northeast Indian" "British/Irish" "Bulgarian Jews" | C "Caribbean Australian" 32.0.0+: "Caucasus Jews" "Central African" "Central Asian" "Chilean" "Chinese" "Chinese Dai" "Christian Arab" "Circassian" "Colombia" | D "Druze" "Dutch" |
E "East African" "East Asian" "East European" "Egyptian" "Egyptian Jews" "Emirates" "Ethiopia" "Ethiopian / Eritrean" "Ethiopian Jews" "Ethiopian Jews - Beta Israel" "European" "European American" | F "Fijian Australian" "Filipino" "Filipino Austronesian" "Finnish" "French" "French Canadian" | G "Georgian Jews" "Germans" "Ghanaian / Liberian / Sierra Leonean" "Greece Jews" "Greek Americans" "Greek / Balkan" "Guam/Chamorro" | H "Hawaiian" |
I "Iberian" "India - Bene Israel Jews" "India - Cochin Jews" "Indian" "Indigenous Amazonian" "Indigenous peoples in Canada" "Indonesian" "Inuit" "Iranian" "Iranian Persian Jews" "Iraq" "Iraqi Jews" "Irish" "Italian" "Italian Americans" "Italian Jews" | J "Japanese" "Japanese Brazilian" "Jordan" | K "Kenyan" "Korean" "Kurdish" "Kurdish Jews" | L "Latino/Hispanic Americans" "Lebanese Jews" "Levantine" "Libyan" "Libyan Jews" |
M "Maasai" "Malayali Indian" "Melanesian" "Mesoamerican and Andean" "Mexican American" "Middle Eastern" "Mongolian / Manchurian" "Mormon" "Moroccan" "Moroccan Jews" "Muslim Arab" | N "Native American" "Nepali" "Nigerian" "North African" "North and West European" "Northern Asian" "Northern Indian" | O "Other Pacific Islander" | P "Pakistani" "Papuan" "Polynesian" "Portuguese in Northern Brazil" "Portuguese in Southern Brazil" |
R "Russian Jews" "Russians" | S "Samaritan" "Samoan" "Sardinian" "Saudi" "Scandinavian" "Senegambian / Guinean" "Siberian" "Somali" "South African" "South Asian" "Southern East African / Congolese" "Southern European" "Southern Indian" "Southern Indian / Sri Lankan" "Southern South Asian" "Spaniards" "Spanish Jews" "Sub-Saharan African" "Sudanese" "Swedes" "Syrian Jews" "Syrian-Lebanese" | T "Tajikistan Jews" "Thai / Cambodian / Vietnamese" "Tunisian" "Tunisian Jews" "Turkish" "Turkish / Anatolian" "Turkish Jews" | U "Ukraine" "Ukraine Jews" " zbekistan/ Bukharan Jews" |
V "Venezuela" | W "West African" | Y "Yemenite" "Yemenite Jews" |