0%
Print report
Variant interpretation report

PTEN c.634+1_634+3del, p.?

NM_000314.8:c.634+1_634+3del NP_000305.3:p.? Canonical splice · intron 6 View identifiers
Classification
Likely pathogenic

Variant description:

The PTEN NM_000314.8:c.634+1_634+3del (NP_000305.3:p.?) splicing variant has not previously been reported in somatic cancers (COSMIC). This variant is predicted to disrupt normal RNA processing, resulting in either an aberrant protein product or nonsense-mediated RNA decay. 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 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: 2 Benign evidence criteria: 0
Pathogenic criteria applied · 2
PVS1Very strong
PVS1 · very strong

Met, very strong: exon 6 donor disruption causes a 142-nucleotide frameshifting skip 5' of p.D375 in NM_000314.8, matching the VCEP's full PVS1 path.

PM2Supporting
PM2 · supporting

Met, supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP PM2 requirement of less than 0.00001 (0.001%) allele frequency.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Likely pathogenic

Likely Pathogenic: PVS1 (very strong) plus PM2 (supporting) satisfy the PTEN Expert Panel's Rule20.

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.990 maximum delta

Recorded SpliceAI maximum delta score: 0.990. 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 ↗
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: 2 met · 4 not met · 11 not assessed · 11 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

Only PS4, PP4, PP5, BP5, and BP6 were adjudicated.

PS4 and BP5 remain not_assessed because the VCEP-required case, phenotype, alternate-diagnosis, or history data are unavailable; PP4, PP5, and BP6 are explicitly not applicable under the PTEN VCEP.

No numeric threshold was evaluated because no qualifying numeric PS4 or BP5 evidence was available; therefore no substituted inequality was warranted.

Met · 2

PVS1 Very strongVCEPMet, very strong: exon 6 donor disruption causes a 142-nucleotide frameshifting skip 5' of p.D375 in NM_000314.8, matching the VCEP's full PVS1 path. Details ▾Hide ▴
Reasoning

NM_000314.8:c.634+1_634+3del is a canonical GT-AG donor splice-site disruption at exon 6. The case evidence identifies exon 6 skipping as removing 142 coding nucleotides, shifting the reading frame, and producing NP_000305.3:p.?. The affected exon is present in the biologically relevant NM_000314.8 transcript, and the disruption is 5' of p.D375 (c.1121). Under the PTEN VCEP decision-tree row for GT-AG splice sites, a frameshifting exon-skipping consequence predicted to undergo NMD at or 5' of p.D375 receives full PVS1. The full-strength tier is therefore very strong.

VCEP rule
GT-AG 1,2 splice sites [footnote a] | Exon skipping or use of a cryptic splice site disrupts reading frame and is predicted to undergo NMD; stop codon or disruption at or 5' to p.D375 (c.1121) -> exon is present in biologically-relevant transcript NM_000314.8 | PVS1
Evidence considered
  • PVS1_DecisionTree_PTEN.pdf, GT-AG splice-site row: "Exon skipping or use of a cryptic splice site disrupts reading frame and is predicted to undergo NMD; stop codon or disruption at or 5' to p.D375 (c.1121) -> exon is present in biologically-relevant transcript NM_000314.8 | PVS1".
  • Variant assessment for NM_000314.8:c.634+1_634+3del: canonical donor (+1) splice-site variant in exon 6; exon range c.493_634; exon 6 skipping removes 142 coding nucleotides (142 % 3 = 1) and shifts the reading frame; exon 6 is neither first nor last and is present in the 9-exon transcript.
  • The exact variant was not mentioned in PMID:28677221, but its Results/Table 1 report that the nearby exon-6 donor variant c.634+1G>C causes exon 6 skipping and a frameshift at glycine 165; this is contextual support for the splice consequence, not an exact-variant observation.
  • The exact variant was not mentioned in PMID:16014636, but its Results and Figures 3, 5 and 6 report that an analogous exon-6 splice-donor defect produces an unstable exon-6-skipped transcript subject to nonsense-mediated decay; this is contextual support for the NMD path, not an exact-variant observation.
Still missing
  • No exact c.634+1_634+3del or p.? entry was found in PVS1_DecisionTree_PTEN.pdf.txt; the matching canonical splice-site row was applied to the documented exon-6 frameshift and transcript facts.
Sources
PM2 SupportingVCEPMet, supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP PM2 requirement of less than 0.00001 (0.001%) allele frequency. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP permits PM2 at supporting strength when a variant is absent from population databases or present at less than 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 less than 0.00002 (0.002%). The variant is absent from gnomAD v2.1 and gnomAD v4.1, satisfying the rule.

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 PM2 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, that subpopulation allele frequency must be <0.00002 (0.002%).
  • gnomAD v2.1: variant absent; absence is below the VCEP PM2 allele-frequency threshold.
  • gnomAD v4.1: variant absent; absence is below the VCEP PM2 allele-frequency threshold.
Sources

Not met · 4 · evaluated, threshold not reached

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

The ClinGen PTEN VCEP requires a gnomAD filtering allele frequency greater than 0.00056 (0.056%) for BA1. The variant is absent from gnomAD v2.1 and gnomAD v4.1, so no qualifying population frequency is present.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP BA1 rule: gnomAD Filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1: variant absent; no allele frequency reported.
  • gnomAD v4.1: variant absent; no allele frequency reported.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, with no allele frequency in either VCEP BS1 interval of 0.0000043 to 0.00056. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP applies BS1 at strong strength for a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%), and at supporting strength from 0.0000043 (0.00043%) up to 0.000043 (0.0043%). The variant is absent from gnomAD v2.1 and gnomAD v4.1, so it falls in neither frequency interval.

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 BS1 strong rule: gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • ClinGen PTEN VCEP BS1 supporting rule: Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • gnomAD v2.1: variant absent; no allele frequency reported.
  • gnomAD v4.1: variant absent; no allele frequency reported.
Sources
BS2 VCEPNot met: gnomAD v2.1 and v4.1 report no variant observations, so there is no qualifying homozygous observation in a healthy or PHTS-unaffected individual. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires observation in the homozygous state in a healthy or PHTS-unaffected individual; one observation is sufficient when homozygous status is confirmed, and two are required when it is not confirmed. The available population records report the variant as absent from gnomAD v2.1 and v4.1, with no homozygous observations, so BS2 is not met.

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 BS2 strong rule requires observation in the homozygous state in a healthy or PHTS-unaffected individual, with one confirmed observation or two if confirmation is unavailable.
  • gnomAD v2.1: variant absent; no homozygous observation reported.
  • gnomAD v4.1: variant absent; no homozygous observation reported.
Sources
BP4 VCEPNot met: SpliceAI max delta 0.99 exceeds the VCEP BP4 benign range of 0-0.2, and VarSeak concordance is unavailable. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 splice path applies to synonymous or intronic variants when SpliceAl and VarSeak concordantly predict no splicing impact; SpliceAl scores 0-0.2 are benign evidence and VarSeak classes 1 or 2 are benign evidence. This intronic canonical splice-donor variant has a SpliceAI maximum delta score of 0.99, outside the VCEP benign range and directly inconsistent with no predicted splice impact. VarSeak is also unavailable, so the required benign concordance is not present. BP4 is not met.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score \< 0.5.
Evidence considered
  • NM_000314.8:c.634+1_634+3del is an intronic canonical splice-donor variant.
  • SpliceAI reports max delta score 0.99, with DS_DL 0.99 and DS_AL 0.904; the VCEP BP4 benign range is 0-0.2.
  • No VarSeak result is available, and the available SpliceAI result independently contradicts the required no-impact prediction.
Sources

Not assessed · 11 · no assessment recorded

PS1 VCEPNot assessed: a nearby c.634+1G>C splice variant causes exon 6 skipping, but pathogenic status and a comparable in-silico result are unavailable. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS1 Strong for either the same amino-acid change as an established pathogenic variant or a different variant at the same nucleotide position as a pathogenic splicing variant when in-silico impact is equal to or greater than the known pathogenic variant. The case variant is canonical splice NM_000314.8:c.634+1_634+3del with protein consequence p.?. PMID:28677221 reports the nearby same-position splice variant c.634+1G>C causing exon 6 skipping and a frameshift, but the available extraction does not establish that comparator as pathogenic or provide a directly comparable in-silico result. Therefore PS1 cannot be evaluated from the available evidence.

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
  • ClinGen PTEN VCEP v3.2 PS1 rule: same amino-acid change as an established pathogenic variant, or a different variant at the same nucleotide position as a pathogenic splicing variant with equal or greater predicted impact.
  • PMID:28677221, Results/Table 1: c.634+1G>C is reported to cause exon 6 skipping and a frameshift at glycine 165, but the extraction does not classify it as pathogenic or provide a comparable prediction score.
  • Case normalization: NM_000314.8:c.634+1_634+3del; NP_000305.3:p.?; consequence class canonical_splice.
Still missing
  • A VCEP-established pathogenic comparator at the same nucleotide position and a comparable in-silico impact result are needed.
Sources
PS2 VCEPNot assessed: no documented proband, confirmed maternity and paternity, or family-history information establishes a de novo observation. Details ▾Hide ▴
Reasoning

The available case evidence does not document a disease-affected proband with confirmed de novo occurrence, confirmed maternity and paternity, or absence of family history. Therefore the 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
  • No case-specific proband, parental-testing, family-history, or de novo-observation data are documented in the available evidence.
Still missing
  • Disease-affected proband documentation is unavailable.
  • Parental testing confirming both maternity and paternity is unavailable.
  • Family-history information is unavailable.
  • The number of proven and assumed de novo observations is unavailable.
Sources
PS3 VCEPNot assessed: no damaging RNA, mini-gene, or other splicing-assay result is available for this canonical splice-site deletion. Details ▾Hide ▴
Reasoning

The variant is a canonical splice-site deletion with predicted protein consequence p.?, so the VCEP missense phosphatase-assay table is not applicable as a direct assay result. The governing PS3 rule permits damaging RNA, mini-gene, or other splicing-assay evidence, but no such result is present in the case evidence. The designated VCEP file mmc2.xlsx was searched for c.634+1_634+3del and p.?; no matching entry was found. Therefore PS3 cannot be assigned from the available functional evidence.

VCEP rule
Well-established _in vitro_ or _in vivo_ functional studies supportive of a damaging effect on the gene or gene product. * RNA, mini-gene, or other assay shows impact on splicing...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
  • The case normalization identifies NM_000314.8:c.634+1_634+3del with NP_000305.3:p.? and consequence class canonical_splice.
  • The PTEN VCEP index declares mmc2.xlsx for PS3/BS3 missense saturation-mutagenesis phosphatase data and states that PS3_Moderate is based on Cum_score <= -1.11.
  • The full converted mmc2.xlsx text was searched for c.634+1_634+3del and p.?; no matching variant row was found.
  • The available case evidence contains no variant-specific damaging RNA, mini-gene, or other functional splicing-assay result.
Still missing
  • No matching c.634+1_634+3del or p.? entry was found in the designated VCEP file /Users/gs_agent/LYFESCI_HERMES_v12/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No variant-specific damaging RNA, mini-gene, or other functional splicing assay result is available.
Sources
PS4 VCEPNot assessed: no affected-case counts, matched controls, or proband phenotype-specificity scores are available to evaluate the PTEN PS4 rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from a sufficiently powered case-control study with odds ratio >2, p<0.05, and a 95% confidence-interval lower limit >1.5, or from phenotype-specificity scores accumulated across probands. No case-control counts, matched-ancestry control frequency, affected-proband count, Cleveland Clinic scores, pediatric scores, or variant-specific phenotype series are available. Therefore an odds ratio and 95% confidence interval cannot be computed, and no PS4 specificity score can be assigned. The literature packet contains no AI-classified papers; the extracted papers do not report this exact variant. Absence from gnomAD is population evidence but does not by itself establish the required affected-versus-control comparison.

VCEP rule
Probands with specificity score 4-15.5 (see text) OR The prevalence of the variant in affected individuals is significantly increased compared with the prevalence in controls.
Evidence considered
  • ClinGen PTEN VCEP specification: PS4 may use a sufficiently powered case-control study with odds ratio >2, p<0.05, and 95% confidence-interval lower limit >1.5; no qualifying counts or frequencies are present, so OR and 95% CI were not computable.
  • ClinGen PTEN VCEP specification: phenotype specificity is scored as 1 point per adult proband with Cleveland Clinic score >=30, 0.5 points for 25-29, 1 point per child with pediatric phenotype score >=5, and 0.5 points for score 4; no such scores are available.
  • PMID:28677221 reports 34 germline PTEN intronic variants in 61 patients and family members but explicitly does not mention c.634+1_634+3del.
  • PMID:23470840 reports a 25-person PTEN hamartoma tumor syndrome neuropsychological cohort but no variant-specific observation for c.634+1_634+3del.
  • PMID:39316756 and PMID:16014636 do not explicitly mention c.634+1_634+3del and do not provide qualifying case-control or variant-specific phenotype data.
  • gnomAD v2.1 and v4.1 report the variant absent; this supplies no affected-case numerator or matched-control denominator for PS4.
Still missing
  • Variant-specific affected-proband count and phenotype details
  • Unaffected or matched-ancestry population-control count/frequency
  • Cleveland Clinic or pediatric phenotype scores for independent probands
Sources
PM6 VCEPNot assessed: no assumed de novo proband observation with parental-confirmation status and no-family-history evidence is documented. Details ▾Hide ▴
Reasoning

The available case evidence does not document an assumed de novo observation in a disease-affected proband, the parental-confirmation status, or absence of family history. The VCEP PM6 rule therefore cannot be evaluated at any specified strength.

VCEP rule
Assumed _de novo,_ but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • No case-specific de novo, parental-testing, proband-phenotype, or family-history data are documented in the available evidence.
Still missing
  • Disease-affected proband documentation is unavailable.
  • Evidence for an assumed de novo occurrence is unavailable.
  • Maternity and paternity confirmation status is unavailable.
  • Family-history information is unavailable.
  • The number of proven and assumed de novo observations is unavailable.
Sources
PP1 VCEPNot assessed: no affected-family co-segregation observations or meioses are documented against the VCEP minimum of 3 meioses. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected family members with documented co-segregation and no meiosis count. The VCEP PP1 thresholds of 3 or 4, 5 or 6, or at least 7 meioses across at least two families 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
  • No family segregation data, informative relatives, or meiosis count are documented in the available evidence.
Still missing
  • Affected family members and their phenotypes are unavailable.
  • Variant genotypes in informative relatives are unavailable.
  • The number of informative meioses is unavailable.
  • Family count is unavailable.
Sources
PP3 VCEPNot assessed: SpliceAI max delta 0.99 supports impact, but the VCEP requires concordant VarSeak class 4 or 5 and no VarSeak result is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 splice path applies to synonymous or intronic variants only when SpliceAl and VarSeak concordantly predict splicing impact, with SpliceAl scores 0.5-1 and VarSeak class 4 or 5. This is an intronic canonical splice-donor variant and SpliceAI predicts impact (max delta score 0.99; DS_DL 0.99 and DS_AL 0.904), but no VarSeak result is available. Because the required two-predictor concordance cannot be evaluated, PP3 is not_assessed rather than met; the SpliceAI result is not reused for BP4 or BP7.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic).
Evidence considered
  • NM_000314.8:c.634+1_634+3del is an intronic canonical splice-donor variant at +1.
  • SpliceAI reports max delta score 0.99, with DS_DL 0.99 and DS_AL 0.904, which falls within the VCEP's pathogenic splice-prediction range of 0.5-1.
  • No VarSeak prediction or class is present; therefore the VCEP-required concordance of SpliceAl and VarSeak cannot be established.
Still missing
  • VarSeak prediction class for NM_000314.8:c.634+1_634+3del is unavailable, so required SpliceAl-VarSeak concordance cannot be determined.
Sources
BS3 VCEPNot assessed: no RNA, mini-gene, or other splicing assay demonstrates that this canonical splice-site deletion has no splicing impact. Details ▾Hide ▴
Reasoning

The variant is a canonical splice-site deletion with predicted protein consequence p.?, and no benign functional result is available. The governing VCEP BS3 rule requires a functional study showing no damaging effect, with the intronic pathway specifically requiring RNA, mini-gene, or another splicing assay demonstrating no splicing impact. The designated VCEP file mmc2.xlsx was searched for c.634+1_634+3del and p.?; no matching entry was found, and no variant-specific benign splicing assay is present. Therefore BS3 cannot be assigned.

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
  • The case normalization identifies NM_000314.8:c.634+1_634+3del with NP_000305.3:p.? and consequence class canonical_splice.
  • The governing PTEN VCEP BS3 rule requires a study showing no damaging effect; for intronic or synonymous variants it requires RNA, mini-gene, or another splicing assay demonstrating no splicing impact.
  • The full converted mmc2.xlsx text was searched for c.634+1_634+3del and p.?; no matching variant row was found.
  • No variant-specific benign RNA, mini-gene, other splicing-assay result, or phosphatase result is available in the case evidence.
Still missing
  • No matching c.634+1_634+3del or p.? entry was found in the designated VCEP file /Users/gs_agent/LYFESCI_HERMES_v12/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No variant-specific RNA, mini-gene, or other splicing assay demonstrating no splicing impact is available.
Sources
BS4 VCEPNot assessed: no affected relatives lacking the variant or family-level non-segregation observations are documented. Details ▾Hide ▴
Reasoning

The available case evidence does not document affected relatives who lack the variant, nor does it establish one or more families with lack of segregation. The VCEP BS4 rule 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
  • No affected-relative genotype/phenotype comparisons or family-level lack-of-segregation data are documented in the available evidence.
Still missing
  • Affected relatives are unavailable.
  • Relative genotypes are unavailable.
  • Non-segregation observations are unavailable.
  • Family count is unavailable.
Sources
BP2 VCEPNot assessed: no qualifying trans observation or at least three cis/phase-unknown observations with different pathogenic PTEN variants are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP2 rule requires either observation of the variant in trans with a pathogenic or likely pathogenic PTEN variant, or at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants. The available case evidence contains no affected-proband observation, second PTEN variant, phase assignment, cis/trans result, or qualifying multi-observation series, so BP2 cannot be evaluated.

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
  • No case-level evidence documents a second pathogenic or likely pathogenic PTEN variant, affected-proband observation, cis/trans phase, or three qualifying cis/phase-unknown observations for NM_000314.8:c.634+1_634+3del.
Still missing
  • A documented affected-proband observation with a second pathogenic or likely pathogenic PTEN variant and confirmed trans phase, or at least three qualifying cis/phase-unknown observations, is missing.
Sources
BP5 VCEPNot assessed: no two qualifying cases with an alternate highly penetrant molecular diagnosis and non-overlapping PTEN history are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires at least two cases in which the variant is found with an alternate molecular basis for disease, with the other gene/disorder highly penetrant and the patient's personal/family history showing no overlap between that disorder and PTEN. The available evidence contains no alternate molecular diagnosis, qualifying cases, or personal/family-history assessment. BP5 therefore cannot be evaluated.

VCEP rule
**PTEN EP Specifications:** At least two such cases are required for criteria to apply.  In addition, the other gene/disorder must be considered highly penetrant AND the patient’s personal/family history must demonstrate no overlap between the other gene and _PTEN_. ... 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 PTEN VCEP instructions require at least two such cases and require the alternate gene/disorder to be highly penetrant with no overlap between the patient's personal/family history and PTEN.
  • No qualifying alternate molecular diagnosis, case count, penetrance evidence, or personal/family-history documentation is present in the available case evidence.
Still missing
  • At least two cases carrying the variant with an alternate molecular diagnosis
  • Evidence that the alternate disorder is highly penetrant
  • Personal and family histories demonstrating no overlap with PTEN
Sources
Not applicable · 11· recorded as not applicable Show reasons ▾Hide reasons ▴
PM1 N/ANot applicable: the canonical splice-site deletion has protein consequence p.? and no amino-acid residue to compare with the PM1 intervals 90-94, 123-130, and 166-168. Details ▾Hide ▴
Reasoning

The VCEP limits PM1 to variants located in the specified PTEN catalytic-motif residue intervals 90-94, 123-130, or 166-168. This variant is a canonical splice-site deletion with protein consequence p.? and has no assignable amino-acid residue, so it cannot lie within one of those residue-defined regions.

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
  • ClinGen PTEN VCEP v3.2 defines PM1 as catalytic-motif residues 90-94, 123-130, and 166-168 on NP_000305.3.
  • Case normalization reports NM_000314.8:c.634+1_634+3del with NP_000305.3:p.? and consequence class canonical_splice; no residue is available for interval comparison.
Sources
PM3 VCEPNot applicable: the PTEN VCEP specification explicitly designates PM3 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP specification explicitly marks PM3 as Not Applicable; therefore PM3 is not evaluated for this PTEN variant, regardless of the absence of reported phase or affected-proband observations.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN Expert Panel Specifications, Version 3.2, CSPEC criterion entry PM3: applicability is "Not Applicable".
Sources
PM4 N/ANot applicable: the variant is a frameshifting canonical splice disruption, not an in-frame indel affecting a catalytic motif or a stop-loss extension. Details ▾Hide ▴
Reasoning

PM4 is not applicable under the PTEN VCEP rule because this is a canonical splice-site variant with a frameshifting loss-of-function consequence, not an in-frame insertion/deletion affecting a catalytic motif or a stop-loss protein extension. The VCEP PM4 rule is limited to protein-length changes from in-frame indels in non-repeat regions or stop-loss variants.

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
  • PTEN VCEP CSPEC PM4 entry: the rule covers protein length changes due to in-frame deletions/insertions in non-repeat regions or stop-loss variants, including in-frame indels impacting a catalytic motif and protein extensions; this variant is canonical splice-site with a frameshifted exon-skipping consequence.
Sources
PM5 N/ANot applicable: PM5 requires a missense change at an amino-acid residue, whereas this variant is a canonical splice-site deletion with protein consequence p.?. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule requires a missense change at an amino-acid residue where a different pathogenic or likely pathogenic missense change has been seen, plus a BLOSUM62 comparison. This variant is a canonical splice-site deletion with protein consequence p.?, not a missense change.

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
  • ClinGen PTEN VCEP v3.2 PM5 rule requires a missense change at an amino-acid residue and a BLOSUM62 comparison.
  • Case normalization reports consequence class canonical_splice and NP_000305.3:p.?.
Sources
PP2 N/ANot applicable: PP2 is restricted to missense variants, while this variant is a canonical splice-site deletion with protein consequence p.?. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP2 rule applies to a missense variant in a gene with a low rate of benign missense variation where missense variants are a common disease mechanism. This variant is a canonical splice-site deletion, not a missense variant.

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
  • ClinGen PTEN VCEP v3.2 PP2 rule explicitly begins with missense variant.
  • Case normalization reports consequence class canonical_splice and NP_000305.3:p.?.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 Use 2 and explicitly excludes separate PP4 application. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks PP4 not applicable and states that phenotype specificity has been incorporated into PS4 Use 2. PP4 is therefore not evaluated separately, regardless of the absence of case-specific phenotype data.

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 explicitly prohibits PP5 use under its governing specification. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly designates 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 PP5 entry states: This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP1 VCEPNot applicable: the ClinGen PTEN VCEP marks BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks BP1 as Not Applicable.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP v3.2 CSPEC entry for BP1: Not Applicable.
Sources
BP3 VCEPNot applicable: the PTEN VCEP explicitly marks BP3 as Not Applicable, and this splice-site loss-of-function variant is outside that criterion. Details ▾Hide ▴
Reasoning

BP3 is explicitly marked Not Applicable in the PTEN VCEP CSPEC criteria. No BP3 benign in-frame repeat-region rule is available for this variant under the governing VCEP framework.

VCEP rule
Not Applicable
Evidence considered
  • PTEN VCEP CSPEC BP3 entry lists applicability as Not Applicable.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly prohibits BP6 use under its governing specification. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly designates 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 BP6 entry states: This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP7 N/ANot applicable: the intronic deletion is at the canonical +1 splice donor, not at or beyond the VCEP BP7 boundary of +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule is limited to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.634+1_634+3del affects the canonical splice donor at +1, which is inside the excluded canonical splice-site interval and is not at or beyond +7/-21; BP7 is therefore not_applicable before evaluating prediction evidence.

VCEP rule
**PTEN EP Specification:** Intronic variants must be positioned at or beyond +7/-21.
Evidence considered
  • The variant is NM_000314.8:c.634+1_634+3del, an intronic canonical splice-donor deletion at +1.
  • The VCEP applicability instruction requires intronic variants to be positioned at or beyond +7/-21.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.634+1_634+3del
Protein (HGVS p.)
NP_000305.3:p.?
GRCh38
chr10:87952258 CAGT>C
GRCh37
chr10:89712015 CAGT>C
Location and type
Intron 6 · canonical splice

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

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -140 bp
0.904
SpliceAI acceptor gainat +30 bp
0.000
SpliceAI donor lossat +1 bp
0.990
SpliceAI donor gainat +30 bp
0.010
Pangolin splice lossmagnitude shown
-0.912
Pangolin splice gain
0.104

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

BP4 VCEPNot met: SpliceAI max delta 0.99 exceeds the VCEP BP4 benign range of 0-0.2, and VarSeak concordance is unavailable. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 splice path applies to synonymous or intronic variants when SpliceAl and VarSeak concordantly predict no splicing impact; SpliceAl scores 0-0.2 are benign evidence and VarSeak classes 1 or 2 are benign evidence. This intronic canonical splice-donor variant has a SpliceAI maximum delta score of 0.99, outside the VCEP benign range and directly inconsistent with no predicted splice impact. VarSeak is also unavailable, so the required benign concordance is not present. BP4 is not met.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score \< 0.5.
Evidence considered
  • NM_000314.8:c.634+1_634+3del is an intronic canonical splice-donor variant.
  • SpliceAI reports max delta score 0.99, with DS_DL 0.99 and DS_AL 0.904; the VCEP BP4 benign range is 0-0.2.
  • No VarSeak result is available, and the available SpliceAI result independently contradicts the required no-impact prediction.
Sources
PP3 VCEPNot assessed: SpliceAI max delta 0.99 supports impact, but the VCEP requires concordant VarSeak class 4 or 5 and no VarSeak result is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 splice path applies to synonymous or intronic variants only when SpliceAl and VarSeak concordantly predict splicing impact, with SpliceAl scores 0.5-1 and VarSeak class 4 or 5. This is an intronic canonical splice-donor variant and SpliceAI predicts impact (max delta score 0.99; DS_DL 0.99 and DS_AL 0.904), but no VarSeak result is available. Because the required two-predictor concordance cannot be evaluated, PP3 is not_assessed rather than met; the SpliceAI result is not reused for BP4 or BP7.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic).
Evidence considered
  • NM_000314.8:c.634+1_634+3del is an intronic canonical splice-donor variant at +1.
  • SpliceAI reports max delta score 0.99, with DS_DL 0.99 and DS_AL 0.904, which falls within the VCEP's pathogenic splice-prediction range of 0.5-1.
  • No VarSeak prediction or class is present; therefore the VCEP-required concordance of SpliceAl and VarSeak cannot be established.
Still missing
  • VarSeak prediction class for NM_000314.8:c.634+1_634+3del is unavailable, so required SpliceAl-VarSeak concordance cannot be determined.
Sources
BP7 N/ANot applicable: the intronic deletion is at the canonical +1 splice donor, not at or beyond the VCEP BP7 boundary of +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule is limited to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.634+1_634+3del affects the canonical splice donor at +1, which is inside the excluded canonical splice-site interval and is not at or beyond +7/-21; BP7 is therefore not_applicable before evaluating prediction evidence.

VCEP rule
**PTEN EP Specification:** Intronic variants must be positioned at or beyond +7/-21.
Evidence considered
  • The variant is NM_000314.8:c.634+1_634+3del, an intronic canonical splice-donor deletion at +1.
  • The VCEP applicability instruction requires intronic variants to be positioned at or beyond +7/-21.
Sources

Statement

In silico

SpliceAI predicts possible splice impact for this variant (max delta score = 0.99).

0 paper records listed. 2 cited in the classification.

Cited in the classification

  • Different splicing defects lead to differential effects downstream of the lipid
    The exact variant c.634+1_634+3del is not explicitly mentioned. An analogous PTEN exon 6 splice-donor mutation caused exon 6 skipping, with an unstable transcript subject to nonsense-mediated decay and undetectable exon-6-deleted PTEN protein.
    → PVS1 · very strong Does not name this variant
    PMID 16014636 ↗
    Source detail
    Similarly, puromycin treatment reduced the ratio of wild-type to exon 6 spliced out transcript in the patient sample with the IVS6+1G>T mutation to half than when not treated, suggesting the instability of exon 6 deleted mRNA transcript as well.

    Location Results: Table 1; Figures 3, 5 and 6; sections on exon 6 transcript NMD and PTEN protein stability

    Context PTEN cDNA sequencing and RT-PCR in lymphoblastoid cell lines, puromycin treatment for NMD assessment, western blotting, and transient expression of exon-deleted PTEN constructs in MCF-7 cells.

  • Characterization of cryptic splicing in germline PTEN intronic variants in Cowde
    The exact variant c.634+1_634+3del is not explicitly mentioned. The paper reports that the nearby intron 6 splice-site variant c.634+1G>C causes exon 6 skipping and a frameshift at glycine 165 that terminates after eight codons.
    → PVS1 · very strong Does not name this variant
    PMID 28677221 ↗
    Source detail
    Five mutations around exon 6 (c.493−2A>G, c.634+1G>C, c.634+2T>C, c.634+4A>T, and c.634+5G>C) cause exon 6 skipping and result in a frameshift at glycine 165 that terminates after eight codons.

    Location Results, paragraph discussing exon skipping; Table 1

    Context Cohort of 61 patients and family members with 34 germline PTEN intronic variants; lymphoblast-derived cell RNA, cDNA sequencing, and related splicing analyses.

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 possible splice impact for this variant (max delta score = 0.99).

Somatic

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