0%
Print report
Variant interpretation report

PTEN c.-326_-324delinsCCC, p.?

NM_000314.8:c.-326_-324delinsCCC NP_000305.3:p.? Unknown · exon 1 View identifiers
Classification
Uncertain significance

Variant description:

The PTEN NM_000314.8:c.-326_-324delinsCCC (NP_000305.3:p.?) 5' UTR variant has not previously been reported in somatic cancers (COSMIC). Based on available guidelines, this variant is considered to be a Variant of Uncertain Significance (VUS).

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

Uncertain.The recorded classification is uncertain significance.

In plain language

Gene-level background from the recorded interpretation.

About PTEN

PTEN is a tumor suppressor gene that encodes a phosphatase converting the lipid messenger PIP3 back to PIP2 at the cell membrane, thereby restraining the AKT/mTOR signaling pathway that drives cell growth, proliferation, and survival. It is one of the most frequently mutated genes across many types of human cancer, and its loss promotes unchecked cell growth, survival, and genomic instability, partly through impaired DNA repair. Germline loss-of-function variants in PTEN cause Cowden syndrome, an inherited cancer predisposition disorder associated with elevated risk of breast and thyroid cancer.

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 PTEN VCEP v3.2. 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
PM2Supporting
PM2 · supporting

Met at Supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP requirement for <0.00001 (0.001%) allele frequency.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: PM2 (supporting) is met, but no PTEN Expert Panel combination rule is satisfied by the adjudicated criteria.

02The sources

Evidence at a glance

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

SpliceAI score
0.015 maximum delta

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

No listed criterion applied SpliceAI ↗
ClinVar submissions
Not recorded

A ClinVar laboratory submission summary was not recorded.

Context only ClinVar ↗
No screenshot for this evidence
Functional evidence
Not recorded

No standalone functional evidence summary is recorded in evidence_summary.functional.

No listed criterion applied OncoKB ↗
Somatic evidence
No matching record reported

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

Context only COSMIC ↗
For specialists

Technical detail

ACMG/AMP criteria under ClinGen PTEN VCEP v3.2, with the data and sources behind each one.

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

Met Not met Not assessed Not applicable

Population evidence supports PM2 at Supporting strength because the variant is absent from both queried all-comers gnomAD datasets.

BA1 and BS1 are not met because no population allele frequency was observed, and BS2 is not assessed because no homozygous healthy-individual observation was available.

Met · 1

PM2 SupportingVCEPMet at Supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP requirement for <0.00001 (0.001%) allele frequency. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PM2 at Supporting strength when the variant is absent or present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles occur in a subpopulation, that subpopulation frequency must be <0.00002 (0.002%). The variant was absent from gnomAD v2.1 and v4.1, satisfying the applicable absence/frequency requirement.

VCEP rule
Absent in population ... Databases present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population. If multiple alleles are present within any subpopulation, allele frequency in that subpopulation must be <0.00002 (0.002%).
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, PM2 Supporting rule: databases present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present within any subpopulation, allele frequency in that subpopulation must be <0.00002 (0.002%).
  • gnomAD v2.1 result for NC_000010.10:g.89623901_89623903delinsCCC: absent.
  • gnomAD v4.1 result for NC_000010.11:g.87864144_87864146delinsCCC: absent.
Sources

Not met · 2 · evaluated, threshold not reached

BA1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, rather than exceeding the >0.00056 (0.056%) BA1 threshold. Details ▾Hide ▴
Reasoning

The PTEN VCEP specifies BA1 only when the gnomAD filtering allele frequency is >0.00056 (0.056%). The variant was absent from gnomAD v2.1 and gnomAD v4.1, so no frequency exceeding the BA1 threshold is observed.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BA1 rule: gnomAD Filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1 result for NC_000010.10:g.89623901_89623903delinsCCC: absent; no allele frequency reported.
  • gnomAD v4.1 result for NC_000010.11:g.87864144_87864146delinsCCC: absent; no allele frequency reported.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, so its frequency does not fall within either 0.0000043–0.00056 BS1 interval. Details ▾Hide ▴
Reasoning

The PTEN VCEP specifies BS1 Strong for a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%), and BS1 Supporting from 0.0000043 (0.00043%) up to 0.000043 (0.0043%). The variant was absent from gnomAD v2.1 and v4.1, so neither frequency interval is met.

VCEP rule
gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) ... Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BS1 Strong rule: gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • ClinGen PTEN VCEP Version 3.2, BS1 Supporting rule: Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • gnomAD v2.1 result for NC_000010.10:g.89623901_89623903delinsCCC: absent; no allele frequency reported.
  • gnomAD v4.1 result for NC_000010.11:g.87864144_87864146delinsCCC: absent; no allele frequency reported.
Sources

Not assessed · 12 · no assessment recorded

PS2 VCEPNot assessed: no proband de novo observation, parental testing, maternity/paternity confirmation, disease phenotype, or family-history information is available. Details ▾Hide ▴
Reasoning

The available case evidence contains no proband-level de novo observation, parental testing, maternity or paternity confirmation, disease phenotype, or family-history information. Therefore, the PTEN VCEP PS2 rule cannot be evaluated.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • The case evidence bundle reports no pedigree, proband de novo, parental testing, maternity, paternity, phenotype, or family-history data for this variant.
  • The governing PTEN VCEP rule requires a de novo observation in a patient with the disease and no family history, with both maternity and paternity confirmed for PS2 Strong.
Still missing
  • Proband disease phenotype and confirmation of PTEN-related disease
  • Variant testing results for both biological parents
  • Maternity and paternity confirmation
  • Family history and absence of disease in relatives
Sources
PS3 VCEPNot assessed: the governing mmc2.xlsx search found no c.-326_-324delinsCCC or p.? entry and no case-specific damaging functional result is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS3 for a damaging splicing assay, for phosphatase activity <= -1.11 per Mighell et al. 2018, or for a damaging functional study below that moderate threshold. The case variant is NM_000314.8:c.-326_-324delinsCCC, normalized as NP_000305.3:p.? with unknown consequence class; the governing mmc2.xlsx file is indexed for missense variants, and searches of its full text for c.-326_-324delinsCCC and p.? found no matching entry. No case-specific RNA, mini-gene, phosphatase, or other functional result establishes a PS3 finding, so PS3 cannot be assessed.

VCEP rule
Well-established _in vitro_ or _in vivo_ functional studies supportive of a damaging effect on the gene or gene product. * Phosphatase activity ≤ -1.11 per Mighell et al. 2018, PMID: 29706350.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 PS3 rule: damaging RNA, mini-gene, or other splicing assay may support PS3 Strong; phosphatase activity <= -1.11 per Mighell et al. 2018 may support PS3 Moderate; a damaging functional study below that moderate threshold may support PS3 Supporting.
  • Case normalization: NM_000314.8:c.-326_-324delinsCCC; NP_000305.3:p.?; consequence class unknown.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, README and indexed Tables S2-S5: the file is specified for PTEN missense functional data; full-text searches for c.-326_-324delinsCCC and p.? returned no matching row.
Still missing
  • No matching c.-326_-324delinsCCC entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No matching p.? entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • A variant-specific RNA, mini-gene, phosphatase, or other validated functional assay result is unavailable.
Sources
PS4 VCEPNot assessed: no case-control statistics or qualifying proband phenotype-specificity scores are available to compare with the PTEN VCEP PS4 thresholds. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from a sufficiently powered case-control study or phenotype-specificity scores across independent probands. The available evidence contains no case-control odds ratio, p-value, confidence interval, Cleveland Clinic scores, pediatric phenotype scores, proband count, or qualifying phenotype/family-history data for this variant. Therefore PS4 cannot be evaluated. The VCEP also states that PS4 may not be applied with PP4 and may not be applied if BS1 applies; neither interaction changes the present evidence gap.

VCEP rule
This criterion may not be applied if BS1 applies. Phenotype specificity scores are added across independent probands and calculated as follows: Adults: 1 point per proband with Cleveland Clinic (CC) score ≥ 30 (Tan 2011); 0.5 points per proband with CC score of 25-29. Children: 1 point per proband with pediatric phenotype score ≥ 5 (please see supplementary information in manuscript for scoring rubric). 0.5 points per proband with pediatric phenotype score of 4, but autism/developmental delay/intellectual disability may not contribute to the score. PS4_Very Strong: Probands with specificity score ≥16. PS4: Probands with specificity score of 4-15.5. PS4_Moderate: Probands with specificity score of 2-3.5. PS4_Supporting: Proband(s) with specificity score of 1-1.5.
Evidence considered
  • No case-control study result, odds ratio, p-value, confidence interval, proband specificity score, Cleveland Clinic score, or pediatric phenotype score was present in the available case evidence.
  • Variant facts identify NM_000314.8:c.-326_-324delinsCCC as an upstream noncoding variant with predicted protein consequence p.(=), but provide no patient phenotype or family-history observations usable for PS4.
Still missing
  • Case-control odds ratio, p-value, and 95% confidence interval for a PHTS component phenotype are unavailable.
  • Independent proband phenotype data and Cleveland Clinic or pediatric phenotype scores are unavailable.
  • BS1 status is not relevantly documented for this criterion, and the VCEP's PS4-BS1 restriction cannot be independently assessed from phenotype evidence alone.
Sources
PM6 VCEPNot assessed: no de novo observations, proband disease phenotype, family history, or parental testing information is available to evaluate PM6 thresholds. Details ▾Hide ▴
Reasoning

The available case evidence contains no presumed or assumed de novo observations, proband disease phenotype, family history, or parental testing information. Consequently, none of the PTEN VCEP PM6 de novo observation thresholds can be evaluated.

VCEP rule
Two proven OR four assumed OR one proven + two assumed de novo observations in a patient with the disease and no family history. ... Two probands with presumed _de novo_ occurrence (maternity/ paternity not confirmed) with the disease and no family history. ... May also be used for a proband with presumed de novo occurrence for an individual with a highly specific phenotype (meets criteria to count towards PS4) ... Assumed _de novo,_ but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • The case evidence bundle reports no de novo observations, parental testing, proband phenotype, or family-history data for this variant.
  • The PTEN VCEP PM6 rule specifies separate thresholds for proven and assumed de novo observations in patients with disease and no family history.
Still missing
  • Number of de novo observations
  • Whether each de novo observation is proven or assumed
  • Proband disease phenotype
  • Family history
  • Maternity and paternity confirmation
Sources
PP1 VCEPNot assessed: no affected relatives, segregation observations, family structure, or meiosis count is available for evaluating PP1. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected relatives, segregation observations, family structure, or meiosis count. Therefore, the PTEN VCEP PP1 co-segregation thresholds cannot be evaluated.

VCEP rule
Co-segregation with disease in multiple affected family members, with ≥7 meioses observed across at least two families. ... Co-segregation with disease in multiple affected family members, with 5 or 6 meioses observed. ... Co-segregation with disease in multiple affected family members, with 3 or 4 meioses observed.
Evidence considered
  • The case evidence bundle reports no affected family members, segregation results, family structure, or meiosis count for this variant.
  • The PTEN VCEP PP1 rule assigns strength according to the number of observed co-segregating meioses across affected family members and families.
Still missing
  • Affected family members with the variant
  • Unaffected or non-carrier relatives where informative
  • Family structure and phase information
  • Observed meiosis count across families
Sources
PP3 VCEPNot assessed: the PTEN rule requires concordance of SpliceAl and VarSeak for splicing variants, but only SpliceAI (maximum delta 0.015) is available. Details ▾Hide ▴
Reasoning

The variant is a noncoding 5'-UTR change with no missense consequence, so the PTEN VCEP's splicing-variant computational path is the relevant path. That path requires concordance of SpliceAl and VarSeak to support a deleterious effect. SpliceAI is available and reports a maximum delta score of 0.015, but no VarSeak result is present; therefore concordance cannot be evaluated and PP3 cannot be assigned.

VCEP rule
Multiple lines of computational evidence support a deleterious effect on the gene or gene product. * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL score > 0.7
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 PP3 rule: the splicing-variant path requires concordance of SpliceAl and VarSeak.
  • SpliceAI Lookup for NM_000314.8:c.-326_-324delinsCCC reports DS_AG 0.014, DS_AL 0.015, DS_DG 0.001, and DS_DL 0.004; maximum delta score is 0.015.
  • No VarSeak result is present for this variant, so the required predictor concordance cannot be determined.
Still missing
  • VarSeak prediction for NM_000314.8:c.-326_-324delinsCCC is unavailable, so the VCEP-required SpliceAl/VarSeak concordance cannot be assessed.
Sources
BS2 VCEPNot assessed: gnomAD reports absence and provides no confirmed or unconfirmed homozygous observations in healthy or PHTS-unaffected individuals. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires observation of the variant in the homozygous state in a healthy or PHTS-unaffected individual; one observation is sufficient if homozygous status is confirmed and two are required if it is not confirmed. The available gnomAD results report absence and provide no homozygote observations or clinical status, so BS2 cannot be evaluated.

VCEP rule
Observed in the homozygous state in a healthy or PHTS-unaffected individual. One observation if homozygous status confirmed, two if not confirmed. To be applied at supporting evidence level if BS1 is also applied.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BS2 rule: observed in the homozygous state in a healthy or PHTS-unaffected individual; one observation if homozygous status confirmed, two if not confirmed.
  • gnomAD v2.1 and gnomAD v4.1 report the variant as absent and contain no homozygote or clinical-status observation for this variant.
Still missing
  • No documented homozygous observations with confirmation status and healthy or PHTS-unaffected clinical status were available.
Sources
BS3 VCEPNot assessed: mmc2.xlsx contains no matching c.-326_-324delinsCCC or p.? entry and provides no variant-specific phosphatase activity >0 value. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits BS3 for a well-established functional study showing no damaging effect, including phosphatase activity >0 per Mighell et al. 2018 for BS3 Supporting. The case variant is normalized as NP_000305.3:p.? with unknown consequence class; searches of the governing mmc2.xlsx full text for c.-326_-324delinsCCC and p.? found no matching entry, and no variant-specific benign functional assay result is available. Therefore BS3 cannot be assessed.

VCEP rule
Well-established _in vitro_ or _in vivo_ functional studies shows no damaging effect on protein function. To be applied to intronic or synonymous variants, RNA, mini-gene or other splicing assay demonstrating no splicing impact. ... _In vitro_ or _in vivo_ functional study or studies showing no damaging effect on protein function. * Phosphatase activity >0 per Mighell et al. 2018, PMID: 29706350.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BS3 rule: a well-established functional study showing no damaging effect may support BS3 Strong; an in vitro or in vivo study showing no damaging effect, including phosphatase activity >0 per Mighell et al. 2018, may support BS3 Supporting.
  • Case normalization: NM_000314.8:c.-326_-324delinsCCC; NP_000305.3:p.?; consequence class unknown.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, README and indexed Tables S2-S5: the file is specified for PTEN missense functional data; full-text searches for c.-326_-324delinsCCC and p.? returned no matching row.
Still missing
  • No matching c.-326_-324delinsCCC entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No matching p.? entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • A variant-specific functional study demonstrating no damaging effect or phosphatase activity >0 is unavailable.
Sources
BS4 VCEPNot assessed: no affected-family-member genotypes or segregation results are available to evaluate lack of segregation in one or more families. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected-family-member genotypes or segregation results, so there is no evidence of lack of segregation in one or more families. The PTEN VCEP BS4 rule therefore cannot be evaluated.

VCEP rule
Lack of segregation in affected members of two or more families. ... Lack of segregation in affected members of one family.
Evidence considered
  • The case evidence bundle reports no affected-family-member genotypes, phenotypes, or segregation results for this variant.
  • The PTEN VCEP BS4 rule requires lack of segregation in affected members of one or more families, with strength determined by the number of families.
Still missing
  • Genotypes and phenotypes of affected family members
  • Segregation results within each family
  • Number of families with informative non-segregation
Sources
BP2 VCEPNot assessed: no affected-proband, phase, or cis/trans observations pairing this variant with a pathogenic or likely pathogenic PTEN variant are available. Details ▾Hide ▴
Reasoning

The PTEN VCEP Version 3.2 BP2 rule requires either observation in trans with a pathogenic or likely pathogenic PTEN variant, or at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants. The available case evidence contains no affected-proband observations, phase information, or documented cis/trans pairing with another pathogenic or likely pathogenic PTEN variant, so BP2 cannot be assessed.

VCEP rule
Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
  • ClinGen PTEN Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for PTEN Version 3.2, criteria entry BP2: "Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants."
  • The case evidence records no affected-proband, inheritance, phase, cis, trans, or qualifying second-variant observations for NM_000314.8:c.-326_-324delinsCCC.
Still missing
  • Affected-proband observations with a second PTEN pathogenic or likely pathogenic variant are not documented.
  • Phase is not established as trans, cis, or phase unknown for any qualifying PTEN variant pair.
  • No qualifying count of at least three cis and/or phase-unknown observations with different pathogenic/likely pathogenic PTEN variants is documented.
Sources
BP4 VCEPNot assessed: the PTEN rule requires concordance of SpliceAl and VarSeak for splicing variants, but only SpliceAI (maximum delta 0.015) is available. Details ▾Hide ▴
Reasoning

The variant is a noncoding 5'-UTR change with no missense consequence, so the PTEN VCEP's splicing-variant computational path is the relevant path. That path requires concordance of SpliceAl and VarSeak to support no impact on the gene or gene product. SpliceAI is available and reports a maximum delta score of 0.015, but no VarSeak result is present; therefore concordance cannot be evaluated and BP4 cannot be assigned.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores < 0.5
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP4 rule: the splicing-variant path requires concordance of SpliceAl and VarSeak.
  • SpliceAI Lookup for NM_000314.8:c.-326_-324delinsCCC reports DS_AG 0.014, DS_AL 0.015, DS_DG 0.001, and DS_DL 0.004; maximum delta score is 0.015.
  • No VarSeak result is present for this variant, so the required predictor concordance cannot be determined.
Still missing
  • VarSeak prediction for NM_000314.8:c.-326_-324delinsCCC is unavailable, so the VCEP-required SpliceAl/VarSeak concordance cannot be assessed.
Sources
BP5 VCEPNot assessed: no two qualifying cases with a highly penetrant alternate disorder and non-overlapping PTEN history are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires at least two cases with an alternate molecular basis, a highly penetrant other gene/disorder, and personal or family history showing no overlap between that disorder and PTEN. No qualifying alternate molecular diagnosis, case count, penetrance evidence, or non-overlapping personal/family history is available for this variant. Therefore BP5 cannot be evaluated.

VCEP rule
Variant found in a case with an alternate molecular basis for disease. Other gene/disorder must be considered highly penetrant AND patient’s personal/family history must demonstrate no overlap between other gene and PTEN.
Evidence considered
  • The available case evidence contains no qualifying alternate molecular diagnosis, case series, penetrance assessment, or personal/family history for BP5.
Still missing
  • At least two qualifying cases with an alternate molecular basis are unavailable.
  • Evidence that the alternate gene/disorder is highly penetrant is unavailable.
  • Personal and family histories demonstrating no overlap between the alternate disorder and PTEN are unavailable.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: the exon 1 5' UTR substitutions have predicted protein consequence p.(=) and are not a VCEP-defined null, splice-site, deletion, duplication, or initiation-codon variant. Details ▾Hide ▴
Reasoning

The PTEN VCEP PVS1 rule applies to nonsense, frameshift, specified canonical splice-site, exon-deletion, duplication, or initiation-codon variants evaluated with the PTEN PVS1 decision tree. NM_000314.8:c.-326_-324delinsCCC is a pair of 5' UTR substitutions in exon 1, normalized by Variant Validator as c.[-326G>C;-324G>C], with predicted protein consequence NP_000305.3:p.(=); it is not a null variant, canonical +/-1/2 splice disruption, exon deletion, duplication, or initiation-codon variant. The PVS1_DecisionTree_PTEN.pdf file was searched for c.-326_-324delinsCCC and p.? and contained no entry for this variant.

VCEP rule
Use PTEN PVS1 decision tree.
Evidence considered
  • ClinGen PTEN VCEP PVS1 specification: PVS1 is evaluated using the PTEN PVS1 decision tree for the specified null-variant classes; the case variant is NM_000314.8:c.-326_-324delinsCCC.
  • Variant Validator normalization: NM_000314.8:c.[-326G>C;-324G>C], both positions upstream of the coding sequence in exon 1; predicted protein consequence NP_000305.3:p.(=).
  • Complete-text search of PVS1_DecisionTree_PTEN.pdf for c.-326_-324delinsCCC and p.? found no matching row or pre-assigned code.
Still missing
  • No entry for c.-326_-324delinsCCC or p.? was found in PVS1_DecisionTree_PTEN.pdf after searching the complete text.
Sources
PS1 N/ANot applicable: the upstream-of-CDS variant has protein consequence p.? and is neither a same-amino-acid nor pathogenic splice-position change. Details ▾Hide ▴
Reasoning

The queried variant is NM_000314.8:c.-326_-324delinsCCC, an upstream-of-CDS noncoding variant with protein consequence NP_000305.3:p.?; it is neither a same-amino-acid change nor a different variant at the same nucleotide position as a pathogenic splicing variant.

VCEP rule
Same amino acid change as a previously established pathogenic variant regardless of nucleotide change OR different variant at same nucleotide position as a pathogenic splicing variant, where in silico models predict impact equal to or greater than the known pathogenic variant.
Evidence considered
  • Prefetch normalization: NM_000314.8:c.-326_-324delinsCCC is upstream of the coding sequence at c.-326 to c.-324; normalized protein consequence is NP_000305.3:p.?.
  • ClinGen PTEN VCEP CSPEC PS1 rule: the criterion is limited to a same amino acid change as a previously established pathogenic variant or a different variant at the same nucleotide position as a pathogenic splicing variant.
Sources
PM1 N/ANot applicable: the upstream-of-CDS variant has no translated residue and cannot occupy PTEN catalytic-motif residues 90-94, 123-130, or 166-168. Details ▾Hide ▴
Reasoning

The variant is upstream of the coding sequence and has no translated residue (NP_000305.3:p.?); therefore it cannot lie in the VCEP-defined PTEN catalytic-motif residues 90-94, 123-130, or 166-168, and vcep_materials.json contains no additional PTEN domain-table entries.

VCEP rule
Located in a mutational hot spot and/or critical and well-established functional domain. Defined to include residues in catalytic motifs: 90-94, 123-130, 166-168 (NP_ 000305.3)
Evidence considered
  • Prefetch normalization: c.-326_-324 is upstream of the coding sequence and the protein consequence is NP_000305.3:p.?.
  • vcep_materials.json domain_tables is an empty object, so there are no additional authoritative PTEN domain-table entries to inspect.
  • ClinGen PTEN VCEP CSPEC PM1 rule defines the critical functional-domain path to include catalytic-motif residues 90-94, 123-130, and 166-168 of NP_000305.3.
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly marks PM3 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP Version 3.2 criteria entry explicitly marks PM3 as "Not Applicable". Therefore PM3 is not evaluated for this PTEN variant under the governing framework, regardless of available allelic evidence.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for PTEN Version 3.2, criteria entry PM3: applicability = "Not Applicable".
Sources
PM4 N/ANot applicable: the exon 1 5' UTR substitutions have predicted protein consequence p.(=) and produce no protein length change required by the PM4 rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule is limited to protein length changes from in-frame deletions or insertions in a non-repeat region, specified catalytic-motif in-frame indels, stop-loss variants, or protein extensions. NM_000314.8:c.-326_-324delinsCCC is a 5' UTR exon 1 substitution event with predicted protein consequence NP_000305.3:p.(=), so it does not change protein length and does not meet any PM4 variant class.

VCEP rule
Protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants. Applies to in-frame insertions or deletions impacting at least one residue in a catalytic motif (see PM1), and variants causing protein extension.
Evidence considered
  • ClinGen PTEN VCEP PM4 rule: protein length changes are due to in-frame deletions/insertions in a non-repeat region, specified catalytic-motif indels, stop-loss variants, or protein extension.
  • Variant Validator normalization and consequence: NM_000314.8:c.[-326G>C;-324G>C] in exon 1 upstream of the CDS, with NP_000305.3:p.(=).
Sources
PM5 N/ANot applicable: the upstream-of-CDS variant is noncoding with protein consequence p.? and is not a missense change at an amino-acid residue. Details ▾Hide ▴
Reasoning

The VCEP PM5 rule applies to a missense change at an amino acid residue. This variant is an upstream-of-CDS noncoding change with protein consequence NP_000305.3:p.? and no amino-acid residue to compare.

VCEP rule
Missense change at an amino acid residue where a different missense change determined to be pathogenic or likely pathogenic has been seen before. In addition, variant being interrogated must have BLOSUM62 score equal to or less than the known variant.
Evidence considered
  • Prefetch normalization: NM_000314.8:c.-326_-324delinsCCC is upstream of the coding sequence, with NP_000305.3:p.? and no residue position.
  • pm5_candidates.json reports no residue context and states that classic PM5 is not applicable because the consequence class is not missense.
Sources
PP2 N/ANot applicable: PP2 requires a missense variant, whereas this upstream-of-CDS variant has protein consequence p.?. Details ▾Hide ▴
Reasoning

The VCEP PP2 rule requires a missense variant. NM_000314.8:c.-326_-324delinsCCC is upstream of the coding sequence and has protein consequence NP_000305.3:p.?, so the missense-specific criterion does not apply.

VCEP rule
Missense variant in a gene that has a low rate of benign missense variation and where missense variants are a common mechanism of disease.
Evidence considered
  • Prefetch normalization: the variant is upstream of the coding sequence and has protein consequence NP_000305.3:p.?.
  • ClinGen PTEN VCEP CSPEC PP2 rule begins with the applicability requirement 'Missense variant'.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 rather than allowing independent PP4 use. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks PP4 as not applicable and states that phenotype specificity has been incorporated into PS4 Use 2. PP4 is therefore not assessed independently.

VCEP rule
PTEN EP Commentary: Phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Evidence considered
  • The PTEN VCEP CSPEC entry marks PP4 as Not applicable and directs that phenotype specificity is incorporated into PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP prohibits use of PP5 under the ClinGen Sequence Variant Interpretation VCEP Review Committee recommendation. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks PP5 as not applicable for this VCEP and states that the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP CSPEC entry marks PP5 as Not Applicable for this VCEP.
Sources
BP1 VCEPNot applicable: the ClinGen PTEN VCEP explicitly marks BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP CSPEC explicitly marks BP1 as Not Applicable; no BP1 evidence is therefore assigned.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP CSPEC BP1 entry: applicability is 'Not Applicable'.
Sources
BP3 VCEPNot applicable: the PTEN VCEP explicitly excludes BP3 for PTEN, regardless of repeat-region or protein-consequence context. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP3 as not applicable to PTEN. Therefore, repeat-region context cannot activate BP3 in this gene, regardless of the variant's 5' UTR location or its lack of protein consequence.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN VCEP BP3 entry: instructions state, "This rule is not applicable to PTEN."
Sources
BP6 VCEPNot applicable: the PTEN VCEP prohibits use of BP6 under the ClinGen Sequence Variant Interpretation VCEP Review Committee recommendation. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP6 as not applicable for this VCEP and states that the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP CSPEC entry marks BP6 as Not Applicable for this VCEP.
Sources
BP7 N/ANot applicable: c.-326_-324delinsCCC is a 5'-UTR variant, not a synonymous or intronic variant at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP7 to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.-326_-324delinsCCC is a 5'-UTR variant, not a synonymous or intronic variant in the stated BP7 scope, so BP7 is not applicable regardless of the available splice prediction.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP7 applies only to a synonymous or intronic variant at or beyond +7/-21; this variant is located in the 5'-UTR at c.-326_-324.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.-326_-324delinsCCC
Protein (HGVS p.)
NP_000305.3:p.?
GRCh38
chr10:87864144 GCG>CCC
GRCh37
chr10:89623901 GCG>CCC
Location and type
Exon 1 · unknown

Gene diagram

Every interpreted variant in PTEN, mapped onto the exon structure of NM_000314.8. Select a row to find it on the plot.

PTENNM_000314.8
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

Not available in gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -105 bp
0.015
SpliceAI acceptor gainat +106 bp
0.014
SpliceAI donor lossat +404 bp
0.004
SpliceAI donor gainat -260 bp
0.001
Pangolin splice lossmagnitude shown
-0.015
Pangolin splice gain
0.021

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 VCEPNot assessed: the PTEN rule requires concordance of SpliceAl and VarSeak for splicing variants, but only SpliceAI (maximum delta 0.015) is available. Details ▾Hide ▴
Reasoning

The variant is a noncoding 5'-UTR change with no missense consequence, so the PTEN VCEP's splicing-variant computational path is the relevant path. That path requires concordance of SpliceAl and VarSeak to support a deleterious effect. SpliceAI is available and reports a maximum delta score of 0.015, but no VarSeak result is present; therefore concordance cannot be evaluated and PP3 cannot be assigned.

VCEP rule
Multiple lines of computational evidence support a deleterious effect on the gene or gene product. * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL score > 0.7
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 PP3 rule: the splicing-variant path requires concordance of SpliceAl and VarSeak.
  • SpliceAI Lookup for NM_000314.8:c.-326_-324delinsCCC reports DS_AG 0.014, DS_AL 0.015, DS_DG 0.001, and DS_DL 0.004; maximum delta score is 0.015.
  • No VarSeak result is present for this variant, so the required predictor concordance cannot be determined.
Still missing
  • VarSeak prediction for NM_000314.8:c.-326_-324delinsCCC is unavailable, so the VCEP-required SpliceAl/VarSeak concordance cannot be assessed.
Sources
BP4 VCEPNot assessed: the PTEN rule requires concordance of SpliceAl and VarSeak for splicing variants, but only SpliceAI (maximum delta 0.015) is available. Details ▾Hide ▴
Reasoning

The variant is a noncoding 5'-UTR change with no missense consequence, so the PTEN VCEP's splicing-variant computational path is the relevant path. That path requires concordance of SpliceAl and VarSeak to support no impact on the gene or gene product. SpliceAI is available and reports a maximum delta score of 0.015, but no VarSeak result is present; therefore concordance cannot be evaluated and BP4 cannot be assigned.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores < 0.5
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP4 rule: the splicing-variant path requires concordance of SpliceAl and VarSeak.
  • SpliceAI Lookup for NM_000314.8:c.-326_-324delinsCCC reports DS_AG 0.014, DS_AL 0.015, DS_DG 0.001, and DS_DL 0.004; maximum delta score is 0.015.
  • No VarSeak result is present for this variant, so the required predictor concordance cannot be determined.
Still missing
  • VarSeak prediction for NM_000314.8:c.-326_-324delinsCCC is unavailable, so the VCEP-required SpliceAl/VarSeak concordance cannot be assessed.
Sources
BP7 N/ANot applicable: c.-326_-324delinsCCC is a 5'-UTR variant, not a synonymous or intronic variant at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP7 to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.-326_-324delinsCCC is a 5'-UTR variant, not a synonymous or intronic variant in the stated BP7 scope, so BP7 is not applicable regardless of the available splice prediction.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP7 applies only to a synonymous or intronic variant at or beyond +7/-21; this variant is located in the 5'-UTR at c.-326_-324.
Sources

Statement

In silico

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

0 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata.

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

Not available in 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.01).

Somatic

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