0%
Print report
Variant interpretation report

DICER1 c.2367_2369delinsCTGATATCCTCCT, p.Arg789SerfsTer2

NM_177438.3:c.2367_2369delinsCTGATATCCTCCT NP_803187.1:p.(Arg789SerfsTer2) Frameshift · exon 15 View identifiers
Classification
Likely pathogenic

Variant description:

The DICER1 NM_177438.3:c.2367_2369delinsCTGATATCCTCCT (NP_803187.1:p.(Arg789SerfsTer2)) frameshift variant has not previously been reported in somatic cancers (COSMIC). This variant is predicted to result in an absent or disrupted protein product. Based on available guidelines, this variant is considered to be Likely Pathogenic.

Five-step scale from benign to pathogenic. This variant is likely pathogenic. Select a step to read what it means.

Likely pathogenic.A likely pathogenic classification under the recorded framework.

In plain language

Gene-level background from the recorded interpretation.

About DICER1

DICER1 encodes an enzyme that processes RNA into small silencing RNAs and microRNAs, which regulate gene expression after transcription. Germline mutations in DICER1 cause DICER1-related disorders, a familial tumor susceptibility syndrome that increases the risk of pleuropulmonary blastoma, cystic nephroma, rhabdomyosarcoma, multinodular goiter, and ovarian Sertoli-Leydig cell tumors. DICER1 acts as a tumor suppressor, and loss or reduced activity of the protein is linked to cancer development and poorer outcomes in several cancer types, including lung, breast, and ovarian cancers.

LYFE Sciences is an AI system, and it can make mistakes. Criteria may be applied incorrectly, sources may be misread, and a confident-looking classification can still be wrong. Double-check every criterion and its underlying evidence before relying on any call.
01The reasoning

How it was classified

The recorded framework is ClinGen DICER1 VCEP v1.4. The criteria and strengths shown below come from the saved assessment; this page does not recalculate the classification.

Recorded applied criteria

The applied criteria and their strengths are shown as assessed under the stated framework.

Pathogenic evidence criteria: 1 Benign evidence criteria: 0
Pathogenic criteria applied · 1
PVS1Very strong
PVS1 · very strong

Met, very strong: frameshift p.Arg789SerfsTer2 creates a stop at p.790, 5' of the DICER1 NMD cutoff at p.Pro1850.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Likely pathogenic

Likely Pathogenic: PVS1 (very strong) contributes 8 points, which meets the DICER1 VCEP point-based range for Likely Pathogenic.

02The sources

Evidence at a glance

Evidence summaries and captured source records, where available. Missing entries should not be interpreted as negative findings.

gnomAD v4.1
gnomAD v2.1
Population frequency
Not recorded

gnomAD v4.1 allele counts were not recorded for this variant.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI score
0.046 maximum delta

Recorded SpliceAI maximum delta score: 0.046. Refer to the recorded PP3/BP4 rationale for interpretation.

No listed criterion applied SpliceAI ↗
No screenshot for this evidence
ClinVar submissions
Not recorded

A ClinVar laboratory submission summary was not recorded.

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB identified variant-specific curated literature and context relevant to functional review; biological-effect context: Likely Loss-of-function; curated oncogenicity label: Likely Oncogenic.

No listed criterion applied OncoKB ↗
COSMIC
Cancer Hotspots
Somatic evidence
No matching record reported

This variant has not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.

For specialists

Technical detail

ACMG/AMP criteria under ClinGen DICER1 VCEP v1.4, with the data and sources behind each one.

28 criteria with recorded statuses: 1 met · 0 not met · 12 not assessed · 15 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

PS3 and BS3 are both not_assessed because no variant-specific RNA or pre-miRNA cleavage assay result with the VCEP-specified controls was available.

The reviewed papers provide general DICER1 loss-of-function or disease-mechanism context but do not report a functional result for this exact variant.

All three requested criteria are not_applicable because the variant is an exonic frameshift and falls outside each VCEP criterion's named variant scope.

The available splice prediction is not used to assign PP3, BP4, or BP7 because scope is determined before predictor evidence and BP4 is not applicable to frameshift variants.

Met · 1

PVS1 Very strongVCEPMet, very strong: frameshift p.Arg789SerfsTer2 creates a stop at p.790, 5' of the DICER1 NMD cutoff at p.Pro1850. Details ▾Hide ▴
Reasoning

The variant is a frameshift in exon 15 of the biologically relevant DICER1 transcript, NM_177438.3, producing NP_803187.1:p.(Arg789SerfsTer2), with a premature stop at p.790. This stop is 5' of the VCEP NMD cutoff at p.Pro1850, so the variant is predicted to undergo NMD; exon 15 is present in the governing transcript. The VCEP decision-tree path for a nonsense or frameshift variant predicted to undergo NMD assigns full PVS1. The VCEP file contained no exact pre-assigned row for c.2367_2369delinsCTGATATCCTCCT, p.Arg789SerfsTer2, or p.R789Sfs*2, so the governing frameshift/NMD path was applied.

VCEP rule
Nonsense or frameshift | Predicted to undergo NMD: stop codon 5' of p.Pro1850 -> exon is present in biologically-relevant transcript NM_177438.2 | PVS1
Evidence considered
  • Variant-level assessment: NM_177438.3:c.2367_2369delinsCTGATATCCTCCT is a frameshift in exon 15 and is predicted as NP_803187.1:p.(Arg789SerfsTer2) / p.(R789Sfs*2), with the predicted truncating stop at p.790.
  • PVS1_DecisionTree.pdf, frameshift/NMD row: 'Nonsense or frameshift | Predicted to undergo NMD: stop codon 5' of p.Pro1850 -> exon is present in biologically-relevant transcript NM_177438.2 | PVS1'.
  • The case's NM_177438.3 transcript is the corresponding current transcript representation; the VCEP decision tree names NM_177438.2 as the biologically relevant transcript, and the variant is confirmed exonic in exon 15.
Still missing
  • No exact entry for c.2367_2369delinsCTGATATCCTCCT, p.Arg789SerfsTer2, or p.R789Sfs*2 was found in PVS1_DecisionTree.pdf.txt.
Sources

Not assessed · 12 · no assessment recorded

PS2 VCEPNot assessed: no documented parental testing, de novo observation, or de novo point total is available to apply the VCEP PS2 thresholds. Details ▾Hide ▴
Reasoning

The available case evidence contains no proband-level parental testing, maternity or paternity confirmation, de novo assertion, de novo point assignment, or family-history documentation. Therefore, the VCEP PS2 point-based rule cannot be evaluated. The criterion remains applicable, but no PS2 strength can be assigned without documented de novo evidence and the required parental context.

VCEP rule
De novo points should be tallied using the simplified table for tallying proband points and used to determine the applied strength of PS2, consistent with SVI guidance. To avoid redundancy and increase consistency, the EP has opted to drop PM6 and exclusively use PS2 for de novo evidence. ... ≥4 de novo points ... ≥2 but less than 4 de novo points ... ≥1 but less than 2 de novo points ... ≥0.5 but less than 1 de novo points
Evidence considered
  • The case evidence materials provide variant and population/functional records but no proband-specific parental testing, maternity or paternity confirmation, de novo observation, or de novo point tally.
  • The VCEP specifies that de novo points determine PS2 strength, with thresholds ranging from 0.5 to at least 4 points.
Still missing
  • Documented parental testing with maternity and paternity confirmation
  • Evidence that the variant is absent in both parents and present in the affected proband
  • De novo point assignment and relevant family-history information
Sources
PS3 Not assessed: No variant-specific RNA or pre-miRNA cleavage assay with the VCEP-required controls was reported for c.2367_2369delinsCTGATATCCTCCT. Details ▾Hide ▴
Reasoning

The DICER1 VCEP specification permits PS3 for functional evidence of splicing impact or reduced DICER1 pre-miRNA cleavage, with strength calibrated by the specified RNA-assay and in vitro cleavage-assay results. The available evidence contains no variant-specific RNA assay showing an out-of-frame or qualifying in-frame splicing effect, and no in vitro cleavage assay showing failure or severe reduction of production of either 5p or 3p microRNAs with the required positive and negative controls. The reviewed papers study general Dicer1 loss or unrelated DICER1 variants and do not report NM_177438.3:c.2367_2369delinsCTGATATCCTCCT or NP_803187.1:p.(Arg789SerfsTer2). Therefore, PS3 cannot be assessed.

Evidence considered
  • The DICER1 VCEP PS3 rule states: RNA assay shows splicing impact that is out-of-frame, in-frame ≥193 residues, or in-frame with RNase IIIb disruption; PS3_Moderate applies for an in-frame change in protein length <193 residues when the RNase IIIb domain is not disrupted.
  • The DICER1 VCEP PS3 rule also states: In vitro cleavage assay shows failure or severely reduced capacity to produce either 5p or 3p microRNAs from a premiRNA, with positive and negative controls also performed.
  • PMID:20305640 reports conditional mouse Dicer1 deletion in osteoprogenitor cells and does not mention the exact queried human variant.
  • PMID:22353998 reports conditional mouse Dicer1 deletion in myeloid-committed progenitors and does not mention the exact queried human variant.
  • PMID:21266384 reports constitutional DICER1 truncating mutations and haploinsufficiency but does not report the exact queried human variant or a variant-specific functional assay.
  • PMID:21501861 reports germline DICER1 loss-of-function mutations in ovarian sex cord-stromal tumor cases but does not report the exact queried human variant or a variant-specific functional assay.
Still missing
  • No variant-specific RNA assay result was identified for NM_177438.3:c.2367_2369delinsCTGATATCCTCCT.
  • No variant-specific in vitro pre-miRNA cleavage assay demonstrated failure or severely reduced production of either 5p or 3p microRNAs with positive and negative controls.
Sources
PS4 VCEPNot assessed: no exact-variant phenotype points, case-control counts, odds ratio, confidence interval, or qualifying rare-variant case series were available. Details ▾Hide ▴
Reasoning

The VCEP permits PS4 for unrelated probands contributing phenotype points, with Supporting at 1–1.5 points, Moderate at 2–3.5 points, and Strong at ≥4 points. No case-level phenotype-point data for this exact variant are available. The four papers in the literature packet were checked through their extracted full-text findings: none mentions NM_177438.3:c.2367_2369delinsCTGATATCCTCCT or p.(R789Sfs*2), and none provides a case-control comparison for this variant. Therefore, no phenotype points, odds ratio, confidence interval, or qualifying rare-variant case series can be established.

VCEP rule
Unrelated probands may contribute up to 1 point each based on phenotype (see Tables 2 & 3 in ruleset) ... ≥4 phenotype points ... 2 – 3.5 phenotype points ... 1 – 1.5 phenotype points
Evidence considered
  • ClinGen DICER1 VCEP PS4 rule: unrelated probands may contribute up to 1 point each based on phenotype; the PS4 strength thresholds are Supporting 1–1.5 phenotype points, Moderate 2–3.5 phenotype points, and Strong ≥4 phenotype points.
  • PMID:20305640 full-text extraction: conditional mouse Dicer1 deletion study; the exact queried human variant was not mentioned, so it supplies no variant-specific phenotype or case-control evidence.
  • PMID:21266384 full-text extraction: constitutional DICER1 mutation cohort of 823 individuals with various tumors; the exact queried variant was not reported, and no variant-specific affected-versus-control comparison was provided.
  • PMID:21501861 full-text extraction: germline DICER1 mutations in patients with ovarian sex cord-stromal tumors; the exact queried variant was not mentioned, and no variant-specific control comparison was provided.
  • PMID:22353998 full-text extraction: conditional mouse Dicer1 deletion study; the exact queried human variant was not mentioned, so it supplies no variant-specific phenotype or case-control evidence.
  • No case-control odds ratio or 95% confidence interval was computed because no exact-variant case and control counts or matched-ancestry control frequency were available.
Still missing
  • Variant-specific affected-proband phenotype data sufficient to assign VCEP phenotype points are unavailable.
  • Variant-specific unaffected/control counts or matched-ancestry control frequency needed for a case-control comparison are unavailable.
Sources
PM2 VCEPNot assessed: gnomAD reports absence, but the required ≤1 allele per subpopulation and ≥20x coverage data are unavailable. Details ▾Hide ▴
Reasoning

The VCEP permits PM2 at supporting strength only when allele frequency is <0.000005 across gnomAD, no subpopulation contains more than one allele, and coverage is at least 20x. The variant is reported absent from gnomAD v2.1 and v4.1, including the available non-cancer searches, but allele-level subpopulation data and coverage are not provided; therefore the complete rule cannot be evaluated.

VCEP rule
Allele frequency <0.000005 across gnomAD with no more than one allele in any subpopulation and at least 20x coverage.
Evidence considered
  • ClinGen DICER1 VCEP v1.4 PM2 supporting rule: allele frequency <0.000005 across gnomAD with no more than one allele in any subpopulation and at least 20x coverage.
  • gnomAD v2.1 and v4.1 report the variant absent; the source records contain no allele frequency, subpopulation allele counts, or coverage metrics.
  • The available non-cancer searches also report absence, but do not supply the allele-level or coverage fields required by the VCEP rule.
Still missing
  • Subpopulation allele counts and coverage metrics, including confirmation of at least 20x coverage, are needed to apply PM2.
Sources
PP1 VCEPNot assessed: no affected relatives, genotype segregation results, or meiosis count are documented for comparison with the VCEP PP1 thresholds. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected relatives, genotype results for relatives, documented family segregation, or meiosis count. Consequently, the VCEP PP1 requirements for phenotype-positive individuals and its 3–4, 5–6, or at least 7 meiosis thresholds cannot be evaluated.

VCEP rule
Phenotype-positive individuals should have high, moderate, or low-specificity phenotypes (see phenotype table). (Caveat: segregation with a single low-specificity phenotype across multiple individuals (e.g. familial Wilms tumor) does not fulfill PP1.) Do not apply PP1 if variant meets BA1/BS1 criteria. ... ≥7 meioses across ≥2 families ... 5 – 6 meioses across ≥1 family ... 3 – 4 meioses across ≥1 family
Evidence considered
  • No family pedigree, affected-relative phenotype data, relative genotypes, cosegregation observations, or meiosis count appears in the available case evidence.
  • The VCEP requires phenotype-positive individuals and assigns PP1 strength according to 3–4, 5–6, or at least 7 meioses.
Still missing
  • Affected relatives with documented DICER1-related phenotypes
  • Genotype results for proband and relatives
  • Pedigree-based meiosis count and number of families
Sources
PP4 VCEPNot assessed: no tumor sequencing evidence showed a qualifying RNase IIIb hotspot second hit, germline retention, and absence of additional somatic loss-of-function variants. Details ▾Hide ▴
Reasoning

The VCEP PP4 rule requires tumor testing in a proband carrying the germline variant to identify a previously reported somatic second hit in an RNase IIIb hotspot codon and demonstrate retention of the germline variant, with no additional somatic DICER1 loss-of-function variants. The available case evidence contains no tumor sequencing result establishing these findings for the queried variant, so PP4 cannot be evaluated.

VCEP rule
Somatic tumor testing identifies somatic hotspot second hit and no additional somatic LOF variants. Tumor testing[<sup>6</sup>](#pmid_30311369) of a neoplasm with known DICER1 association in a proband who carries the germline variant under evaluation reveals the following: ... A previously reported somatic second hit of DICER1 in an RNase IIIb-disrupting “hotspot” codon (p.S1344, p.E1705, p.D1709, p.D1713, p.G1809, p.D1810, or p.E1813) AND ... Retention of the germline DICER1 variant under evaluation.
Evidence considered
  • The VCEP PP4 rule requires a somatic second hit at one of p.S1344, p.E1705, p.D1709, p.D1713, p.G1809, p.D1810, or p.E1813, retention of the germline variant under evaluation, and no additional somatic DICER1 non-hotspot variants.
  • The case evidence provides no qualifying tumor sequencing result for NM_177438.3:c.2367_2369delinsCTGATATCCTCCT.
Still missing
  • Tumor sequencing data from a proband carrying the queried germline variant are unavailable.
  • Retention of the germline variant and exclusion of additional somatic DICER1 loss-of-function variants are unestablished.
Sources
BA1 VCEPNot assessed: gnomAD reports absence, but required subpopulation denominators (>2,000 alleles) and allele counts are unavailable. Details ▾Hide ▴
Reasoning

The VCEP requires frequency >0.003 in a gnomAD subpopulation, with >2,000 alleles tested and at least 5 alleles present. The variant is reported absent from gnomAD v2.1 and v4.1, but the available records provide no subpopulation allele counts or tested-allele denominators, so the VCEP rule cannot be fully evaluated.

VCEP rule
Frequency >0.003 (0.3%) in gnomAD subpopulations. Subpopulations must have >2,000 alleles tested and a minimum of 5 alleles present.
Evidence considered
  • ClinGen DICER1 VCEP v1.4 BA1 rule: frequency >0.003 (0.3%) in gnomAD subpopulations; subpopulations must have >2,000 alleles tested and a minimum of 5 alleles present.
  • gnomAD v2.1 reports the variant absent; the source record contains no allele count, allele number, subpopulation, or denominator data.
  • gnomAD v4.1 reports the variant absent; the source record contains no allele count, allele number, subpopulation, or denominator data.
Still missing
  • Subpopulation-specific allele counts and tested-allele denominators are needed to evaluate the VCEP BA1 threshold and data-quality requirements.
Sources
BS1 VCEPNot assessed: gnomAD reports absence, but required subpopulation denominators (>2,000 alleles) and allele counts are unavailable. Details ▾Hide ▴
Reasoning

The VCEP requires frequency >0.0003 in a gnomAD subpopulation, with >2,000 alleles tested and at least 5 alleles present. The variant is reported absent from gnomAD v2.1 and v4.1, but the available records provide no subpopulation allele counts or tested-allele denominators, so the VCEP rule cannot be fully evaluated.

VCEP rule
Frequency >0.0003 (0.03%) in gnomAD subpopulations. Subpopulations must have >2,000 alleles tested and a minimum of 5 alleles present.
Evidence considered
  • ClinGen DICER1 VCEP v1.4 BS1 rule: frequency >0.0003 (0.03%) in gnomAD subpopulations; subpopulations must have >2,000 alleles tested and a minimum of 5 alleles present.
  • gnomAD v2.1 reports the variant absent; the source record contains no allele count, allele number, subpopulation, or denominator data.
  • gnomAD v4.1 reports the variant absent; the source record contains no allele count, allele number, subpopulation, or denominator data.
Still missing
  • Subpopulation-specific allele counts and tested-allele denominators are needed to evaluate the VCEP BS1 threshold and data-quality requirements.
Sources
BS2 VCEPNot assessed: gnomAD reports absence, but no qualifying healthy individuals, homozygotes, parental confirmation, or tumor-free female cohort is documented. Details ▾Hide ▴
Reasoning

The VCEP requires either tumor-free unrelated females meeting the stated age and ratio thresholds or specified observations of homozygosity in healthy or clinically uninformative individuals. The gnomAD records report the variant absent and provide no homozygote observations, individual health status, sex, age, parental confirmation, or proband ratio, so BS2 cannot be evaluated.

VCEP rule
40+ unrelated females from a single source are tumor-free through age 50 (caveat: ratio of BS2-eligible females to PS4-eligible probands must be ≥ 40:1) OR 2+ observations of homozygosity in healthy individuals OR 1+ observation(s) of homozygosity in a healthy individual with status confirmed by parental testing. ... 10+ unrelated females from a single source are tumor-free through age 50 (caveat: ratio of BS2-eligible females to PS4-eligible probands must be ≥ 10:1) OR 2+ observations of homozygosity in individuals lacking clinical information
Evidence considered
  • ClinGen DICER1 VCEP v1.4 BS2 rule requires either 40+ unrelated females from one source tumor-free through age 50 with a ratio of at least 40:1, or the specified homozygosity observations; supporting strength requires 10+ such females with a ratio of at least 10:1 or 2+ homozygous observations lacking clinical information.
  • gnomAD v2.1 and v4.1 report the variant absent, but absence records do not provide the individual-level health, sex, age, homozygote, parental-testing, or ratio data required by BS2.
Still missing
  • Qualifying healthy-individual homozygote observations or the VCEP-specified tumor-free female cohort and proband ratio are needed.
Sources
BS3 Not assessed: No controlled assay demonstrated normal splicing or production of both 5p and 3p microRNAs for this variant. Details ▾Hide ▴
Reasoning

The DICER1 VCEP specification permits BS3 for functional evidence of no splicing impact or no reduced DICER1 ability to cleave pre-miRNA. For this variant, no RNA assay demonstrated absence of splicing impact, and no in vitro cleavage assay demonstrated production of both 5p and 3p microRNAs from a pre-miRNA with the required positive and negative controls. The reviewed papers do not report a normal functional result for NM_177438.3:c.2367_2369delinsCTGATATCCTCCT or NP_803187.1:p.(Arg789SerfsTer2). Therefore, BS3 cannot be assessed.

Evidence considered
  • The DICER1 VCEP BS3 rule states: For intronic or synonymous variants, no splicing impact observed via RNA assay, and the observation should occur more than once.
  • The DICER1 VCEP BS3 rule also states: An in vitro cleavage assay must demonstrate the variant produces both 5p and 3p microRNAs from a pre-miRNA, with positive and negative controls also performed.
  • The reviewed functional-context papers PMID:20305640, PMID:21266384, PMID:21501861, and PMID:22353998 do not report a normal assay result for the exact queried variant.
Still missing
  • No variant-specific RNA assay demonstrated no splicing impact for NM_177438.3:c.2367_2369delinsCTGATATCCTCCT.
  • No variant-specific in vitro cleavage assay demonstrated production of both 5p and 3p microRNAs from a pre-miRNA with positive and negative controls.
Sources
BS4 VCEPNot assessed: no phenotype-positive, genotype-negative first-, second-, or third-degree relatives are documented for the VCEP BS4 rule. Details ▾Hide ▴
Reasoning

The available case evidence contains no phenotype-positive first-, second-, or third-degree relatives who were tested and found genotype-negative. Thus, the VCEP BS4 requirement for high- or moderate-specificity phenotype-positive, genotype-negative relatives cannot be evaluated.

VCEP rule
Family members should be phenotype-positive (must be high- or moderatespecificity phenotype; see phenotype table), genotype-negative 1st, 2nd, or 3rd degree relatives of the proband.
Evidence considered
  • No affected-relative phenotype records, relationship information, or genotype-negative relative testing results are present in the available case evidence.
  • The VCEP BS4 rule requires phenotype-positive, high- or moderate-specificity relatives who are genotype-negative and within the first, second, or third degree.
Still missing
  • Documented phenotype-positive relatives with high- or moderate-specificity phenotypes
  • Negative genotype testing for each relevant first-, second-, or third-degree relative
  • Relationship degree and family context
Sources
BP2 VCEPNot assessed: no proband observation, P/LP DICER1 partner variant, or trans/cis/phase-unknown evidence is available to evaluate the VCEP threshold. Details ▾Hide ▴
Reasoning

BP2 is applicable, but the available case evidence contains no affected-proband observation of this variant with a P/LP DICER1 variant, no confirmed trans or cis phase, and no series of phase-unknown observations with two or more different P/LP DICER1 variants. The VCEP threshold therefore cannot be evaluated.

VCEP rule
≥1 observation in trans with P/LP DICER1 variant or ≥3 observations in cis or phase unknown with 2+ different P/LP DICER1 variants.
Evidence considered
  • ClinGen DICER1 and miRNA-Processing Gene Expert Panel Specification v1.4, BP2 rule: "≥1 observation in trans with P/LP DICER1 variant or ≥3 observations in cis or phase unknown with 2+ different P/LP DICER1 variants."
  • The case evidence provides no affected-proband allelic observation, partner P/LP DICER1 variant, or phase information for NM_177438.3:c.2367_2369delinsCTGATATCCTCCT.
Still missing
  • Affected-proband observation(s) containing the evaluated variant and one or more P/LP DICER1 variants.
  • Classification of each partner DICER1 variant as pathogenic or likely pathogenic.
  • Confirmed trans or cis phase, or enough phase-unknown observations to establish at least three observations with at least two different P/LP DICER1 variants.
Sources
Not applicable · 15· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: the variant is a frameshift, whereas PS1 requires comparison of the same amino-acid change. Details ▾Hide ▴
Reasoning

The variant is a frameshift, NP_803187.1:p.(Arg789SerfsTer2), and does not produce a same-amino-acid substitution for comparison under the VCEP's PS1 rule. The available evidence contains no same-amino-acid pathogenic DICER1 comparator asserted by the ClinGen DICER1 VCEP. Therefore, the VCEP's same-amino-acid PS1 criterion is not applicable to this frameshift variant.

VCEP rule
For same AA change, must confirm there is no difference in splicing using RNA data or in-silico modeling data (concordance of MaxEntScan and SpliceAI). For non-canonical intronic splicing variants at same nucleotide should have equal or worse splicing impact. This rule code can only be used to compare variants asserted as pathogenic by the ClinGen DICER1 VCEP. Likely pathogenic changes do not apply.
Evidence considered
  • Variant consequence: NM_177438.3:c.2367_2369delinsCTGATATCCTCCT; NP_803187.1:p.(Arg789SerfsTer2), a frameshift.
  • The VCEP PS1 rule is restricted to a same-amino-acid comparison and requires the comparator to be asserted pathogenic by the ClinGen DICER1 VCEP; no such comparison is applicable to this frameshift.
Sources
PM1 N/ANot applicable: the variant is p.Arg789SerfsTer2, not a putative missense variant in the VCEP-defined metal-binding residues or RNase IIIb domain. Details ▾Hide ▴
Reasoning

The VCEP limits PM1 to putative missense variants at the seven metal ion-binding residues or to putative missense variants in the RNase IIIb domain p.Tyr1682-p.Ser1846 outside those residues. This variant is a frameshift, p.Arg789SerfsTer2, and is not a putative missense variant; the PM1 routes therefore do not apply.

VCEP rule
Putative missense variants at residues affecting metal ion-binding: codons p.S1344, p.E1705, p.D1709, p.D1713, p.G1809, p.D1810, p.E1813 ... Putative missense variants at residues in the RNase IIIb domain (p.Y1682 – p.S1846), besides the metal ion-binding residues (see PM1).
Evidence considered
  • The VCEP PM1 moderate route lists metal ion-binding codons p.S1344, p.E1705, p.D1709, p.D1713, p.G1809, p.D1810, and p.E1813; the supporting route covers putative missense variants in RNase IIIb p.Y1682-p.S1846 besides those residues.
  • The case variant is a frameshift, NP_803187.1:p.(Arg789SerfsTer2), so neither VCEP-defined PM1 route applies.
Sources
PM3 VCEPNot applicable: the DICER1 VCEP specifies autosomal dominant inheritance, so PM3's recessive in-trans criterion does not apply. Details ▾Hide ▴
Reasoning

PM3 is not applicable under the ClinGen DICER1 VCEP specification because DICER1-related tumor predisposition has autosomal dominant inheritance; no recessive in-trans phase assessment is permitted for this criterion.

VCEP rule
Autosomal dominant.
Evidence considered
  • ClinGen DICER1 and miRNA-Processing Gene Expert Panel Specification v1.4, PM3 instructions to use: "Autosomal dominant."
  • The governing CSPEC marks PM3 applicability as "Not applicable" and the DICER1 disease context as autosomal dominant inheritance.
Sources
PM4 N/ANot applicable: the variant is a frameshift, whereas DICER1 PM4 is restricted to in-frame indels. Details ▾Hide ▴
Reasoning

The variant is a frameshift, not an in-frame indel. The DICER1 VCEP PM4 specification applies only to in-frame indels within or outside the RNase IIIb domain and repeat regions; therefore PM4 is not applicable.

VCEP rule
In-frame indels with a residue within the RNase IIIb domain (p.Y1682 – p.S1846). ... In-frame indels outside of the RNase IIIb domain (p.Y1682 – p.S1846) and repeat regions (p.D606-p.D609; p.E1418-p.E1420; p.E1422-p.E1425).
Evidence considered
  • Variant-level assessment classifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as a frameshift producing p.(Arg789SerfsTer2), not an in-frame indel.
  • The VCEP PM4 table contains only in-frame-indel paths: one for indels with a residue within p.Y1682-p.S1846 and one for indels outside that domain and the specified repeat regions.
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: PM5 requires a missense variant under evaluation, but this variant is a frameshift ending two residues after Arg789. Details ▾Hide ▴
Reasoning

The VCEP PM5 rule requires a missense variant under evaluation and a different pathogenic variant at the same amino-acid residue, with at least an equal or worse Grantham score and splicing ruled out. The case variant is a frameshift, NP_803187.1:p.(Arg789SerfsTer2), so the missense PM5 rule is not applicable.

VCEP rule
Missense variant under evaluation should have equal or worse Grantham score. Splicing should be ruled out with either RNA data or agreement in splicing predictors (MaxEntScan and SpliceAI) that show no splicing effects. The other variant must be interpreted as pathogenic by the ClinGen DICER1 VCEP. Likely pathogenic changes do not apply. This rule cannot be applied in combination with PM1 or PS1.
Evidence considered
  • The VCEP PM5 rule begins with the requirement 'Missense variant under evaluation' and requires a pathogenic comparator interpreted by the ClinGen DICER1 VCEP.
  • The case variant is NP_803187.1:p.(Arg789SerfsTer2), a frameshift; pm5_candidates.json contains no eligible same-residue missense candidates.
Sources
PM6 VCEPNot applicable: the VCEP explicitly directs users to combine de novo evidence with PS2 and use PS2 instead of PM6. Details ▾Hide ▴
Reasoning

PM6 is not applicable under the DICER1 VCEP specification because the Expert Panel explicitly dropped PM6 and requires de novo evidence to be evaluated exclusively through PS2.

VCEP rule
Combined with PS2. Use PS2 instead of PM6.
Evidence considered
  • The VCEP marks PM6 as not applicable and instructs that de novo evidence be handled through PS2 rather than PM6.
Sources
PP2 VCEPNot applicable: the DICER1 VCEP explicitly recommends not using PP2 because benign and likely benign missense variants occur throughout the gene. Details ▾Hide ▴
Reasoning

PP2 is explicitly marked not applicable by the DICER1 VCEP. The VCEP states that, despite DICER1 meeting the cited missense-constraint cutoff, PP2 should not be used because benign and likely benign missense variants occur throughout the gene.

VCEP rule
While DICER1 does meet recommended cutoff for missense constraint z score of ≥3.09 established by the SVI (4.23 on gnomAD) the VCEP recommends this rule not be used for DICER1 due to the presence of various missense variants throughout the gene that are clinically interpreted as benign (9) or likely benign (30) in ClinVar.
Evidence considered
  • The DICER1 VCEP marks PP2 'Not applicable' and states that it recommends not using PP2 because various missense variants throughout DICER1 are clinically interpreted as benign (9) or likely benign (30) in ClinVar.
Sources
PP3 N/ANot applicable: the variant is an exon 15 frameshift, whereas PP3 names only missense or splicing variants for computational prediction evidence. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP PP3 rule names missense variants and splicing variants, with concordant MaxEntScan and SpliceAI predictions for the splicing-variant path. This variant is an exonic frameshift, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), in exon 15, and is outside the PP3 variant types named by the rule; therefore the available SpliceAI score is not evaluated for PP3.

VCEP rule
For missense variants, REVEL score ≥ 0.750 OR agreement in splicing predictors predict splicing effects. For splicing variants, concordance of MaxEntScan and SpliceAI.
Evidence considered
  • The VCEP specification defines PP3 as applying to missense variants or splicing variants, with the splicing path requiring concordance of MaxEntScan and SpliceAI.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment
PP5 VCEPNot applicable: the DICER1 VCEP explicitly prohibits use of PP5. Details ▾Hide ▴
Reasoning

The DICER1 VCEP marks PP5 as not applicable for this VCEP and explicitly states that the criterion is not for use.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The VCEP lists PP5 as “Not Applicable for this VCEP” and instructs that it is not for use.
Sources
BP1 VCEPNot applicable: the VCEP explicitly excludes BP1 for DICER1 because truncating variants account for only a portion of disease-causing variants. Details ▾Hide ▴
Reasoning

BP1 is explicitly marked not applicable by the DICER1 VCEP. Its instruction states that BP1 does not apply to this gene because truncating variants account for only a portion of disease-causing variants.

VCEP rule
This rule code does not apply to this gene, as truncating variants account for only a portion of disease-causing variants.
Evidence considered
  • The DICER1 VCEP marks BP1 'Not applicable' and states: 'This rule code does not apply to this gene, as truncating variants account for only a portion of disease-causing variants.'
Sources
BP3 VCEPNot applicable: the DICER1 VCEP explicitly designates BP3 as not applicable, and this variant is a coding frameshift. Details ▾Hide ▴
Reasoning

The DICER1 VCEP explicitly marks BP3 as not applicable for this VCEP. Independently, this variant is a coding frameshift rather than an in-frame deletion or insertion in a repetitive region, so no BP3 path applies.

VCEP rule
Not Applicable
Evidence considered
  • The DICER1 VCEP CSPEC entry for BP3 states 'Not Applicable'.
  • Variant-level assessment classifies the variant as a coding frameshift, not an in-frame indel or deletion/insertion evaluated under BP3.
Sources
cspec ↗pvs1_variant_assessment
BP4 N/ANot applicable: BP4 names missense, synonymous, intronic, and non-coding variants, but this variant is an exonic frameshift in exon 15. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP BP4 rule covers missense variants and synonymous, intronic, or non-coding variants. This variant is an exonic frameshift, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), in exon 15. Under the governing scope, BP4 cannot be applied to a frameshift; a no-splice-impact prediction would not negate its truncating protein consequence.

VCEP rule
For missense variants, REVEL score < 0.500 and agreement in splicing predictors that no splicing effects are predicted. For synonymous/intronic/non-coding variants concordance of MaxEntScan and SpliceAI.
Evidence considered
  • The VCEP specification defines BP4 for missense variants or synonymous, intronic, and non-coding variants, with concordant splicing predictors on the latter path.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment
BP5 VCEPNot applicable: the DICER1 VCEP explicitly says BP5 should not be used for this gene. Details ▾Hide ▴
Reasoning

The DICER1 VCEP marks BP5 as not applicable and states that, because of the broad spectrum of DICER1-related neoplasms and insufficient evidence for other high-penetrance germline explanations, this rule should not be used.

VCEP rule
Given the broad spectrum of DICER1-related neoplasms and the General recommendation lack of evidence of other high-penetrance germline variants that could account for such neoplasms (except perhaps for some already low-specificity phenotypes such as Wilms tumor), this rule should not be used at this time.
Evidence considered
  • The VCEP marks BP5 as not applicable and states that this rule should not be used at this time because DICER1-related neoplasms have a broad spectrum and evidence for alternate high-penetrance germline causes is lacking.
Sources
BP6 VCEPNot applicable: the DICER1 VCEP explicitly prohibits use of BP6. Details ▾Hide ▴
Reasoning

The DICER1 VCEP marks BP6 as not applicable for this VCEP and explicitly states that the criterion is not for use.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The VCEP lists BP6 as “Not Applicable for this VCEP” and instructs that it is not for use.
Sources
BP7 N/ANot applicable: BP7 covers silent, intronic, or other non-coding variants, whereas this variant is an exonic frameshift in exon 15. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP BP7 rule is limited to silent, intronic, or other intronic/non-coding variants and additionally requires BP4. This variant is an exonic frameshift in exon 15, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), so it is outside BP7's stated scope.

VCEP rule
Silent variant OR Intronic variant at or beyond +7 to -21 positions OR Other intronic or non-coding variant if the variant is the reference nucleotide in ≥1 primate and/or ≥4 mammalian species. Caveat: Variant must meet BP4 to apply BP7
Evidence considered
  • The VCEP specification limits BP7 to silent, intronic, or other intronic/non-coding variants and states that the variant must meet BP4.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment

Identifiers

Gene
DICER1
Transcript
NM_177438.3
Coding (HGVS c.)
NM_177438.3:c.2367_2369delinsCTGATATCCTCCT
Protein (HGVS p.)
NP_803187.1:p.(Arg789SerfsTer2)
GRCh38
chr14:95108391 CGC>AGGAGGATATCAG
GRCh37
chr14:95574728 CGC>AGGAGGATATCAG
Location and type
Exon 15 · frameshift

Gene diagram

Every interpreted variant in DICER1, mapped onto the exon structure of NM_177438.3. Select a row to find it on the plot.

DICER1NM_177438.3
Fetching transcript structure from UCSC…
gnomAD v4.1 Allele count data not recorded
gnomAD v2.1 Allele count data not recorded
gnomAD-Canada v1.0 Allele count data not recorded

Statements

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat +2 bp
0.015
SpliceAI acceptor gainat +5 bp
0.046
SpliceAI donor lossat -67 bp
0.001
SpliceAI donor gainat -139 bp
0.000
Pangolin splice lossmagnitude shown
-0.100
Pangolin splice gain
0.153

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: the variant is an exon 15 frameshift, whereas PP3 names only missense or splicing variants for computational prediction evidence. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP PP3 rule names missense variants and splicing variants, with concordant MaxEntScan and SpliceAI predictions for the splicing-variant path. This variant is an exonic frameshift, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), in exon 15, and is outside the PP3 variant types named by the rule; therefore the available SpliceAI score is not evaluated for PP3.

VCEP rule
For missense variants, REVEL score ≥ 0.750 OR agreement in splicing predictors predict splicing effects. For splicing variants, concordance of MaxEntScan and SpliceAI.
Evidence considered
  • The VCEP specification defines PP3 as applying to missense variants or splicing variants, with the splicing path requiring concordance of MaxEntScan and SpliceAI.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment
BP4 N/ANot applicable: BP4 names missense, synonymous, intronic, and non-coding variants, but this variant is an exonic frameshift in exon 15. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP BP4 rule covers missense variants and synonymous, intronic, or non-coding variants. This variant is an exonic frameshift, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), in exon 15. Under the governing scope, BP4 cannot be applied to a frameshift; a no-splice-impact prediction would not negate its truncating protein consequence.

VCEP rule
For missense variants, REVEL score < 0.500 and agreement in splicing predictors that no splicing effects are predicted. For synonymous/intronic/non-coding variants concordance of MaxEntScan and SpliceAI.
Evidence considered
  • The VCEP specification defines BP4 for missense variants or synonymous, intronic, and non-coding variants, with concordant splicing predictors on the latter path.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment
BP7 N/ANot applicable: BP7 covers silent, intronic, or other non-coding variants, whereas this variant is an exonic frameshift in exon 15. Details ▾Hide ▴
Reasoning

Not applicable: the DICER1 VCEP BP7 rule is limited to silent, intronic, or other intronic/non-coding variants and additionally requires BP4. This variant is an exonic frameshift in exon 15, NM_177438.3:c.2367_2369delinsCTGATATCCTCCT, p.(Arg789SerfsTer2), so it is outside BP7's stated scope.

VCEP rule
Silent variant OR Intronic variant at or beyond +7 to -21 positions OR Other intronic or non-coding variant if the variant is the reference nucleotide in ≥1 primate and/or ≥4 mammalian species. Caveat: Variant must meet BP4 to apply BP7
Evidence considered
  • The VCEP specification limits BP7 to silent, intronic, or other intronic/non-coding variants and states that the variant must meet BP4.
  • Variant assessment identifies NM_177438.3:c.2367_2369delinsCTGATATCCTCCT as an exonic frameshift in exon 15, predicted p.(Arg789SerfsTer2).
Sources
cspec ↗pvs1_variant_assessment

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.05).

4 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata. None of the listed paper records explicitly indicates that the variant is named.

Recorded publications

  • Bone progenitor dysfunction induces myelodysplasia and secondary leukaemia.
    This paper does not mention the exact human DICER1 variant c.2367_2369delinsCTGATATCCTCCT or NP_803187.1:p.(R789Sfs*2). Instead, it studies conditional deletion of Dicer1 in mouse osterix-positive osteoprogenitor cells and reports impaired osteoblastic differentiation and a microenvironment-dependent myelodysplastic phenotype.
    Does not name this variant
    PMID 20305640 ↗
    Quoted passage
    Taken together, these data demonstrate that disruption of Dicer1 from cells of the osteoblastic lineage causes myelodysplasia in mice recapitulating key characteristics of human MDS, including the propensity to develop AML.

    Results, sections "Myelodysplasia in OCDfl/fl mice" and "Emergence of leukemia"; Discussion

  • DICER1 syndrome: clarifying the diagnosis, clinical features and management implications of a pleiotropic tumour predisposition syndrome.
    This paper does not report the exact DICER1 variant c.2367_2369delinsCTGATATCCTCCT or p.(R789Sfs*2). It reports constitutional DICER1 frameshift, nonsense, and consensus splice-site mutations causing premature protein truncation in patients with DICER1-associated tumors and discusses haploinsufficiency.
    Does not name this variant
    PMID 21266384 ↗
    Quoted passage
    Seventeen mutations led to premature protein truncation as a result of frameshift, nonsense or consensus splice-site mutations.

    Results, Germline DICER1 mutation analysis; Discussion, mechanism of DICER1 tumour predisposition

  • Ovarian sex cord-stromal tumors, pleuropulmonary blastoma and DICER1 mutations: a report from the International Pleuropulmonary Blastoma Registry.
    This paper does not mention DICER1 c.2367_2369delinsCTGATATCCTCCT or NP_803187.1:p.(R789Sfs*2). It reports heterozygous germline loss-of-function DICER1 mutations in patients with pleuropulmonary-blastoma-associated ovarian sex cord-stromal tumors and describes DICER1 as required for mature microRNA production, without providing a variant-specific functional assay.
    Does not name this variant
    PMID 21501861 ↗
    Quoted passage
    Our sequence analysis identified heterozygous germline loss of function DICER1 mutations in 4 of 6 patients with PPB-associated OSCST. We also identified a DICER1 mutation in two young sisters with OSCST and no known family or personal history of PPB.

    Discussion, paragraph beginning "Our sequence analysis identified heterozygous germline loss of function DICER1 mutations"

  • Dicer1 deletion in myeloid-committed progenitors causes neutrophil dysplasia and blocks macrophage/dendritic cell development in mice.
    This paper does not mention the exact human DICER1 variant c.2367_2369delinsCTGATATCCTCCT or NP_803187.1:p.(R789Sfs*2). It studies conditional deletion of Dicer1 in mouse Cebpa-expressing myeloid-committed progenitors and reports impaired myeloid differentiation and depletion of more than 95% of miRNAs in Dicer1-null cells.
    Does not name this variant
    PMID 22353998 ↗
    Quoted passage
    Dicer1 deletion did not affect the numbers of myeloid progenitors in mice.

    Results, "Cebpa-Cre–driven deletion of Dicer1 does not affect the number of HSPCs"; Results, "Cebpa-Cre–driven deletion of Dicer1 affects GM-CFU outgrowth, cellular replating capacity, and myeloid differentiation"; Discussion and Conclusion

Screenshots represent source records captured during evidence collection. Select one to view the recorded source content.

All source links

Statements for reports

The evidence statements recorded by the interpretation pipeline. They have not been reinterpreted by the page.

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant is absent from ClinVar.

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.05).

Functional

OncoKB identified variant-specific curated literature and context relevant to functional review; biological-effect context: Likely Loss-of-function; curated oncogenicity label: Likely Oncogenic.

Somatic

This variant does not lie in a statistically significant hotspot. This variant has not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.