Five-step scale from benign to pathogenic. This variant is likely pathogenic. Select a step to read what it means.
This variantScenario
BenignPathogenic
Likely pathogenic.A likely pathogenic classification under the recorded framework.
In plain language
Gene-level background from the recorded interpretation.
Words with a dotted underline have a short definition. Hover or tap them.
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.
Met (Very Strong): frameshift duplication creates a premature stop (p.Ser226IlefsTer31) upstream of p.D375 and the last exon-exon junction, predicting nonsense-mediated decay.
PM2Supporting
PM2 · supporting
Met (Supporting): absent from gnomAD v2.1, v4.1, and gnomAD-Canada v1.0, meeting the panel's population-absence requirement.
Benign criteria applied · 0
No benign criterion marked as applied in the recorded assessment.
Recorded classification: Likely pathogenic
PVS1 at Very Strong plus PM2 at Supporting maps to Likely Pathogenic under the PTEN VCEP combination rule.
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.
ACMG/AMP criteria under ClinGen PTEN VCEP v3.2, with the data and sources behind each one.
28 criteria with recorded statuses: 2 met · 2 not met · 10 not assessed · 14 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.
c.674_675dupAT is a frameshift duplication (p.(Ser226IlefsTer31)) in exon 7 of 9 of PTEN, predicted to be NMD-competent with a premature stop well upstream (5') of the PTEN VCEP's p.D375/c.1121 threshold, meeting PVS1 at Very Strong strength per the PTEN VCEP PVS1 decision tree.
PM4 and BP3 do not apply because both criteria in the PTEN VCEP framework are scoped to in-frame protein-length-change variants (or stop-loss for PM4); this variant is an out-of-frame frameshift, already fully captured by PVS1.
Variant NM_000314.6:c.674_675dupAT / NP_000305.3:p.(Ser226IlefsTer31) is a frameshift duplication, not a missense substitution.
All five criteria in this group (PS1, PM1, PM5, PP2, BP1) are defined by the PTEN VCEP (cspec v3.2) and/or generic ACMG as missense- or residue-substitution-specific evidence types; none of their applicability conditions are met by a frameshift variant.
PM1's PTEN-specific catalytic motif residue ranges (90-94, 123-130, 166-168) do not include residue 226, and the case's own hotspot lookup found no statistically significant hotspot overlap.
The case's pm5_candidates.json artifact independently confirms PM5 ineligibility due to non-missense consequence class.
BP1 is marked Not Applicable directly in the PTEN VCEP specification for this gene.
PTEN Expert Panel specifications version 3.2 govern PS2, PM6, PP1, and BS4 for PTEN hamartoma tumor syndrome.
No case-specific de novo, parental, pedigree, segregation, or non-segregation evidence was supplied; all four criteria remain not_assessed.
Variant is a frameshift duplication (p.Ser226IlefsTer31), functionally assessed via PVS1 (loss-of-function/NMD pathway), not via the PTEN VCEP's missense-specific PS3/BS3 functional assay framework (Mighell et al. 2018, PMID: 29706350).
No published in vitro or in vivo functional characterization of this specific variant (phosphatase activity, splicing, or otherwise) was located in the case evidence bundle or reviewed literature; PS3 and BS3 are therefore both not_assessed rather than not_applicable, since a functional study of this variant could in principle exist but was not found.
NM_000314.6:c.674_675dupAT is a frameshift duplication variant, not synonymous, intronic, or missense.
The PTEN VCEP restricts its calibrated PP3/BP4 splicing pathway to synonymous or intronic variants (via SpliceAI+VarSeak concordance) and its PP3/BP4 missense pathway to REVEL score thresholds; neither applies to a frameshift variant.
BP7 is restricted to synonymous (or deep intronic +7/-21) variants under both the PTEN VCEP and generic ACMG framework; a frameshift variant does not qualify.
SpliceAI was computed (max delta = 0.103) and REVEL/BayesDel were queried (both null) but none of these apply to this variant's consequence class under the governing VCEP specification, so PP3, BP4, and BP7 are all not_applicable rather than met/not_met.
No criteria match.
Met · 2
PVS1Very strongMet (Very Strong): frameshift duplication creates a premature stop (p.Ser226IlefsTer31) upstream of p.D375 and the last exon-exon junction, predicting nonsense-mediated decay.
Details ▾Hide ▴
Reasoning
NM_000314.6:c.674_675dupAT (normalized c.674_675dup) is a 2bp duplication in exon 7 of 9 causing a frameshift, NP_000305.3:p.(Ser226IlefsTer31). The premature termination codon falls in exon 7, well upstream of the last exon-exon junction (exon 9), so the transcript is predicted to be a substrate for nonsense-mediated decay (NMD) under standard NMD rules. Applying the PTEN VCEP PVS1 decision tree (PVS1_DecisionTree_PTEN.pdf, using biologically-relevant transcript NM_000314.8): for variants predicted to undergo NMD, the tree asks whether the stop codon/disruption occurs at or 5' to p.D375 (c.1121). The new stop here occurs at predicted residue 256 (well 5' of D375/c.1121), so the decision tree assigns PVS1 at Very Strong strength.
Rule
PTEN VCEP PVS1 (cspec v3.2): 'Use PTEN PVS1 decision tree' -> NMD-predicted frameshift with stop at or 5' to p.D375 (c.1121) = PVS1 Very Strong.
Evidence considered
PTEN VCEP PVS1 decision tree (PVS1_DecisionTree_PTEN.pdf) markdown extract: 'Predicted to undergo NMD: Stop codon or disruption at or 5' to Exon is present in biologically-relevant transcript NM_000314.8 PVS1 p.D375 (c.1121)... Not predicted to undergo NMD: Stop codon 3' to p.D375 (c.1121) PVS1_Moderate'.
Mutalyzer/VariantValidator normalization: NM_000314.6:c.674_675dup gives protein consequence NP_000305.3:p.(Ser226IlefsTer31); variant_exonic_positions places the variant in exon 7 of the 9-exon transcript (NC_000010.10/NC_000010.11 start_exon=end_exon=7).
Predicted protein sequence from prefetch shows the frameshifted ORF terminates at predicted residue position 256 (position_last_predicted=256), which is 5' to the p.D375/c.1121 threshold defined by the PTEN VCEP.
Because the new stop is in exon 7 of 9 and far upstream of the last exon-exon junction, the transcript meets standard NMD-competent criteria (PTC >50-55 nt upstream of the final exon-exon junction), matching the VCEP tree's 'Predicted to undergo NMD' branch.
PM2SupportingMet (Supporting): absent from gnomAD v2.1, v4.1, and gnomAD-Canada v1.0, meeting the panel's population-absence requirement.
Details ▾Hide ▴
Reasoning
PM2_Supporting is met. This variant is absent from the queried gnomAD v2.1 and v4.1 datasets and is also absent from gnomAD-Canada v1.0, satisfying the PTEN Expert Panel population-absence requirement.
Rule
PTEN EP v3.2 PM2_Supporting: absent from population databases or gnomAD AF <0.00001; if multiple alleles are present in a subpopulation, subpopulation AF <0.00002.
Evidence considered
ClinGen PTEN Expert Panel Specifications version 3.2 apply PM2 at Supporting strength for absence from population databases, or allele frequency <0.00001 (0.001%) in gnomAD or another large sequenced population; where multiple alleles occur in a subpopulation, subpopulation allele frequency must be <0.00002 (0.002%).
The normalized variant 10-89717644-G-GAT is absent from gnomAD v2.1; 10-87957887-G-GAT is absent from gnomAD v4.1 and gnomAD-Canada v1.0.
BA1Not met: absent from gnomAD v2.1 and v4.1, so the allele frequency does not exceed the BA1 threshold.
Details ▾Hide ▴
Reasoning
BA1 is not met. The variant is absent from the queried gnomAD v2.1 and v4.1 datasets, therefore it does not exceed the PTEN Expert Panel BA1 filtering allele-frequency threshold.
Rule
PTEN EP v3.2 BA1: gnomAD filtering allele frequency >0.00056 (0.056%).
Evidence considered
ClinGen PTEN Expert Panel Specifications version 3.2 define BA1 as gnomAD filtering allele frequency >0.00056 (0.056%).
The normalized variant 10-89717644-G-GAT is absent from gnomAD v2.1, and 10-87957887-G-GAT is absent from gnomAD v4.1.
BS1Not met: absent from gnomAD v2.1 and v4.1, so no allele frequency reaches the BS1 threshold.
Details ▾Hide ▴
Reasoning
BS1 is not met. The variant is absent from the queried gnomAD v2.1 and v4.1 datasets, so no filtering allele frequency reaches either PTEN Expert Panel BS1 range.
Rule
PTEN EP v3.2 BS1: Strong at filtering AF 0.000043 to 0.00056; Supporting at AF 0.0000043 to 0.000043.
Evidence considered
ClinGen PTEN Expert Panel Specifications version 3.2 define BS1_Strong as gnomAD filtering allele frequency 0.000043 to 0.00056 and BS1_Supporting as 0.0000043 to 0.000043.
The normalized variant is absent from gnomAD v2.1 and gnomAD v4.1.
PS2Not assessed: no case documents an affected proband with both parents tested negative and confirmed parentage.
Details ▾Hide ▴
Reasoning
No case-specific observation documents the variant in an affected proband with both parents tested negative, parentage confirmed, and no relevant family history; PS2 cannot be assigned.
Rule
PTEN EP PS2: Strong requires confirmed maternity and paternity for a de novo observation in an affected patient without family history; Very Strong requires two PS2 observations or two PM6 plus one PS2 observation.
Evidence considered
The PTEN Expert Panel requires a de novo observation in a patient with disease, no family history, and confirmation of both maternity and paternity for PS2 at Strong; PS2_Very Strong requires two PS2 observations or two PM6 plus one PS2 observation.
The consolidated case-evidence bundle supplies no case-level proband, parental-testing, parentage, family-history, or de novo observation data for this variant.
Still missing
Obtain the proband phenotype and PTEN testing result.
Obtain parental PTEN results and maternity/paternity confirmation.
Document family history and additional independent proven de novo observations, if present.
PS3Not assessed: no functional study of this frameshift variant exists; the VCEP's functional criteria cover only missense and splicing variants.
Details ▾Hide ▴
Reasoning
NM_000314.6:c.674_675dupAT (p.Ser226IlefsTer31) is a frameshift duplication, not a missense or splicing variant. The PTEN VCEP (cspec v3.2) PS3 rule ties Moderate/Supporting strength to phosphatase activity scores from Mighell et al. 2018 (PMID: 29706350), whose saturation mutagenesis dataset (mmc2.xlsx Table S2) covers only missense substitutions, and ties Strong strength to RNA/mini-gene splicing assay evidence, which does not apply here since this variant is not a splice-region change (SpliceAI predicts no significant splice impact, max delta 0.10). No in vitro or in vivo functional study of this specific frameshift variant or its truncated protein product was identified anywhere in the case bundle, source registry, or reviewed literature.
Rule
PTEN VCEP (ClinGen cspec v3.2) PS3: Strong for RNA/mini-gene splicing assay showing splicing impact; Moderate for phosphatase activity <=-1.11 per Mighell et al. 2018 (PMID: 29706350); Supporting for phosphatase activity <50% of wild-type or other abnormal in vitro/transgenic model. Mighell dataset (mmc2.xlsx) is restricted to missense variants and is not applicable to this frameshift duplication.
Still missing
No functional (phosphatase activity, splicing, or other in vitro/in vivo) assay data available for this specific frameshift duplication variant; the VCEP Mighell et al. 2018 dataset used for PTEN PS3/BS3 applies only to missense variants.
PS4Not assessed: no case-control enrichment statistics or qualifying phenotype-specific probands are available for this variant.
Details ▾Hide ▴
Reasoning
The PTEN Expert Panel requires either a sufficiently powered case-control result for a PHTS component phenotype or qualifying, independent phenotype-specific probands. No case-control enrichment statistics or qualifying proband phenotype-specificity score is available for this exact variant.
Rule
PTEN EP PS4: phenotype-specificity scores across independent probands determine strength; alternatively, a sufficiently powered PHTS component-phenotype case-control study may support strong evidence. PS4 cannot be combined with PP4.
Evidence considered
PTEN EP PS4 permits phenotype-specificity scoring across independent probands: adult CC score >=30 contributes 1 point and 25-29 contributes 0.5 points; pediatric score >=5 contributes 1 point and score 4 contributes 0.5 points under the stated restrictions. Strength requires a total score of 1-1.5 (supporting), 2-3.5 (moderate), 4-15.5 (strong), or >=16 (very strong).
The PTEN EP also permits strong PS4 from a sufficiently powered case-control study with odds ratio >2, p<0.05, and 95% CI lower limit >1.5 for a PHTS component phenotype.
PMID:21194675 was searched for NM_000314.6:c.674_675dup, c.674_675dup, p.Ser226IlefsTer31, and p.S226Ifs*31; the publication reports aggregate PTEN mutation cohorts and does not report this exact variant.
Still missing
Independent proband-level phenotypes and adult Cleveland Clinic or pediatric phenotype scores for this exact variant are not available.
No sufficiently powered case-control study reporting an odds ratio, p value, and confidence interval for this exact variant is available.
PM6Not assessed: no presumed de novo observation is documented for this variant.
Details ▾Hide ▴
Reasoning
No case-specific presumed de novo observation is documented; therefore PM6 cannot be assigned.
Rule
PTEN EP PM6: Moderate requires an assumed de novo occurrence in an affected proband without family history and without confirmed maternity/paternity; Strong and Very Strong require the specified additional observations or phenotype specificity.
Evidence considered
The PTEN Expert Panel permits PM6 for assumed de novo occurrence without confirmation of maternity and paternity in an affected proband without family history; higher strengths require the specified number of independent presumed/proven de novo observations or a highly specific phenotype.
The consolidated case-evidence bundle supplies no case-level proband, parental-testing, parentage, family-history, or presumed de novo observation data for this variant.
Still missing
Obtain the proband phenotype and PTEN testing result.
Obtain parental PTEN testing showing the variant absent in both parents, with parentage status recorded.
Document family history and any additional independent presumed de novo observations.
PP1Not assessed: no affected relatives or segregation data are documented.
Details ▾Hide ▴
Reasoning
No informative affected relatives, genotypes, phenotypes, pedigrees, or meiosis count are documented; PP1 cannot be assigned.
Rule
PTEN EP PP1: Supporting for 3-4 meioses, Moderate for 5-6 meioses, and Strong for at least 7 meioses across at least two families.
Evidence considered
The PTEN Expert Panel requires co-segregation in affected relatives across 3-4 meioses for PP1 Supporting, 5-6 meioses for PP1 Moderate, and at least 7 meioses across at least two families for PP1 Strong.
The consolidated case-evidence bundle contains no family segregation data or meiosis count for this variant.
Still missing
Obtain pedigrees with affected relative phenotypes and PTEN genotypes.
Establish the number of informative meioses and number of independent families.
Evaluate potential phenocopies and age-dependent penetrance before segregation counting.
BS2Not assessed: no homozygous unaffected or PHTS-negative individual carrying this variant has been observed.
Details ▾Hide ▴
Reasoning
BS2 cannot be assessed because no observation of this variant in a homozygous healthy or PHTS-unaffected individual is provided. The variant's absence from the population datasets supplies no homozygote observation.
Rule
PTEN EP v3.2 BS2: homozygous observation(s) in healthy or PHTS-unaffected individual(s), with specified confirmation requirements.
Evidence considered
ClinGen PTEN Expert Panel Specifications version 3.2 permit BS2_Strong for a homozygous healthy or PHTS-unaffected individual (one observation if homozygosity is confirmed, two if not confirmed); if BS1 is also applied, BS2 is Supporting.
The variant is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0; no homozygote record or phenotype information is available.
Still missing
Confirmed homozygous observation(s) with health or PHTS-unaffected status are required for BS2 assessment.
BS3Not assessed: no functional study shows normal function for this variant; the panel's functional evidence covers only missense and splicing variants.
Details ▾Hide ▴
Reasoning
Same rationale as PS3: NM_000314.6:c.674_675dupAT is a frameshift duplication outside the scope of the PTEN VCEP functional-evidence data source. The VCEP BS3 rule requires either a splicing assay showing no impact (applicable to intronic/synonymous variants) or phosphatase activity >0 per Mighell et al. 2018 (PMID: 29706350), whose missense-only saturation mutagenesis dataset does not cover this variant. No functional study of this variant or its truncated protein product showing normal/wild-type-like function was found in the case bundle or reviewed literature.
Rule
PTEN VCEP (ClinGen cspec v3.2) BS3: Strong for well-established in vitro/in vivo functional study (or splicing assay for intronic/synonymous variants) showing no damaging effect; Supporting for phosphatase activity >0 per Mighell et al. 2018 (PMID: 29706350). Mighell dataset (mmc2.xlsx) is restricted to missense variants and is not applicable to this frameshift duplication.
Still missing
No functional assay data available for this specific frameshift duplication variant; the applicable VCEP functional dataset (Mighell et al. 2018) is restricted to missense variants.
BS4Not assessed: no affected relative lacking the variant is documented, so non-segregation evidence is unavailable.
Details ▾Hide ▴
Reasoning
No affected relative who lacks the variant is documented, so non-segregation evidence is unavailable and BS4 cannot be assigned.
Rule
PTEN EP BS4: Supporting requires lack of segregation in affected members of one family; Strong requires lack of segregation in affected members of two or more families.
Evidence considered
The PTEN Expert Panel specifies BS4 Supporting for lack of segregation in affected members of one family and BS4 Strong for lack of segregation in affected members of two or more families.
The consolidated case-evidence bundle contains no affected-relative genotype/phenotype data demonstrating non-segregation.
Still missing
Obtain pedigrees with affected relative phenotypes and PTEN genotypes.
Document informative non-segregation in one or more families and assess phenocopies or other molecular diagnoses.
BP2Not assessed: no observation places this variant in trans with a pathogenic PTEN variant.
Details ▾Hide ▴
Reasoning
No case-level observation establishes this variant in trans with a pathogenic/likely pathogenic PTEN variant, nor are three qualifying cis or phase-unknown observations with different pathogenic/likely pathogenic PTEN variants documented.
Rule
PTEN Expert Panel BP2 Supporting: observed in trans with a pathogenic/likely pathogenic PTEN variant, or at least three cis/phase-unknown observations with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
The PTEN Expert Panel permits BP2 for an observation in trans with a pathogenic or likely pathogenic PTEN variant, or for at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants.
The consolidated case-evidence bundle contains no qualifying co-occurring PTEN variant, phase determination, or affected-proband observation for this criterion.
Still missing
Phase-resolved case observations with a pathogenic/likely pathogenic PTEN variant, or at least three distinct qualifying cis/phase-unknown observations, are needed.
BP5Not assessed: no reports link this variant to an alternate molecular diagnosis in two or more cases.
Details ▾Hide ▴
Reasoning
No reports identify this variant in at least two cases with a highly penetrant alternate molecular diagnosis and a personal/family history lacking overlap with PTEN-associated disease.
Rule
PTEN EP BP5 supporting: at least two cases with a highly penetrant alternate molecular diagnosis and documented absence of phenotype overlap with PTEN.
Evidence considered
PTEN EP requires at least two such cases; the alternate gene/disorder must be highly penetrant, and the patient's personal/family history must show no overlap between that disorder and PTEN. No such cases are present in the supplied evidence.
Still missing
At least two independent cases with the exact variant, a highly penetrant alternate molecular diagnosis, and documented non-overlapping PTEN and alternate-disorder phenotypes are required.
Not applicable · 14· recorded as not applicableShow reasons ▾Hide reasons ▴PS1N/ANot applicable: this frameshift duplication produces no defined amino acid substitution, so the missense-equivalence PS1 criterion does not apply.
Details ▾Hide ▴
Reasoning
PS1 per PTEN VCEP requires 'same amino acid change as a previously established pathogenic variant' — a missense-equivalence criterion. This variant, NM_000314.6:c.674_675dupAT, is a frameshift duplication (NP_000305.3:p.(Ser226IlefsTer31)) that produces a premature termination codon, not a defined amino acid substitution. PS1 mechanism is inapplicable to frameshift variants.
Evidence considered
PTEN VCEP cspec v3.2 defines PS1 as: '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.' This applies to missense substitutions or splicing-position comparisons, neither of which describes this frameshift duplication.
Normalized protein consequence is NP_000305.3:p.(Ser226IlefsTer31), a frameshift with downstream premature stop, not a single amino-acid substitution.
PM1N/ANot applicable: the frameshift starts at residue Ser226, outside the PTEN catalytic motifs (residues 90-94, 123-130, 166-168).
Details ▾Hide ▴
Reasoning
PTEN VCEP defines PM1 as location in a mutational hotspot/critical functional domain restricted to catalytic motif residues 90-94, 123-130, and 166-168 (NP_000305.3). The frameshift start residue Ser226 lies outside all three defined catalytic motif ranges, and the frameshift/PTC mechanism differs from the missense positional reasoning the criterion targets.
Evidence considered
PTEN VCEP cspec v3.2 PM1: '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).' Residue 226 (variant start) is not within any of these ranges.
prefetch/hotspots data notes: 'This variant does not lie in a statistically significant hotspot.'
PM4N/ANot applicable: this out-of-frame 2-bp duplication is not an in-frame insertion/deletion or stop-loss variant; its loss-of-function effect is captured by PVS1.
Details ▾Hide ▴
Reasoning
The PTEN VCEP restricts PM4 to protein length changes from in-frame insertions/deletions in a non-repeat region, or stop-loss variants (and in-frame indels affecting a catalytic motif residue per PM1). c.674_675dupAT is a 2-nucleotide (out-of-frame) duplication producing a frameshift with a premature termination codon, not an in-frame insertion/deletion and not a stop-loss variant. PM4 therefore does not apply to this variant; its loss-of-function consequence is already captured under PVS1.
Rule
PTEN VCEP PM4 (cspec v3.2) applies only to in-frame indels or stop-loss variants; frameshift/out-of-frame duplications are excluded.
Evidence considered
PTEN VCEP cspec v3.2 PM4 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.'
Normalization confirms c.674_675dup is a 2bp duplication causing a frameshift (p.(Ser226IlefsTer31)), i.e. out-of-frame, not an in-frame indel or stop-loss event, so it falls outside the VCEP PM4 scope.
PM5N/ANot applicable: PM5 requires a missense change at a residue with a known pathogenic missense; this is a frameshift.
Details ▾Hide ▴
Reasoning
PTEN VCEP PM5 requires a missense change at a residue where a different missense change is known pathogenic/likely pathogenic, with BLOSUM62 comparison. This variant is a frameshift, not a missense substitution, so no residue-level amino-acid comparison is possible. The case's own pm5_candidates artifact explicitly flags this variant as ineligible for classic same-residue missense PM5 search because the consequence class is frameshift, not missense.
Evidence considered
pm5_candidates.json: eligible_for_classic_pm5_search=false; reason='Framework is classic same-residue missense PM5, but the variant consequence class (frameshift) is not missense.'
PTEN VCEP cspec v3.2 PM5: 'Missense change at an amino acid residue where a different missense change determined to be pathogenic or likely pathogenic has been seen before... variant being interrogated must have BLOSUM62 score equal to or less than the known variant.' Requires a missense query variant, which this is not.
PP2N/ANot applicable: PP2 is restricted to missense variants; this is a frameshift duplication.
Details ▾Hide ▴
Reasoning
PTEN VCEP PP2 applies to 'missense variant in a gene that has a low rate of benign missense variation and where missense variants are a common mechanism of disease.' This variant is a frameshift duplication, not a missense substitution, so PP2's missense-specific applicability gate is not met regardless of PTEN's known missense-intolerance.
Evidence considered
PTEN VCEP cspec v3.2 PP2: 'Missense variant in a gene that has a low rate of benign missense variation and where missense variants are a common mechanism of disease.' Variant consequence here is frameshift (p.(Ser226IlefsTer31)), not missense.
PP3N/ANot applicable: PP3 applies only to synonymous, intronic, or missense variants; this frameshift falls outside all three pathways.
Details ▾Hide ▴
Reasoning
Variant NM_000314.6:c.674_675dupAT is a coding frameshift duplication, not a synonymous, intronic, or missense variant. Per the PTEN VCEP (ClinGen) specification, PP3 applies only to (a) synonymous or intronic variants assessed via SpliceAI/VarSeak concordance, or (b) missense variants via REVEL score > 0.7. This frameshift variant falls into neither category, so the VCEP's calibrated PP3 pathway is not applicable. REVEL/BayesDel scores are not available (null) and would not apply to a frameshift variant regardless. SpliceAI max delta score of 0.103 was computed but is not evidentiary here since the VCEP restricts splice-based PP3/BP4 to synonymous/intronic variants only.
Rule
PTEN VCEP: PP3 supporting - splicing variants (synonymous/intronic) with SpliceAI+VarSeak concordance for pathogenic impact, or missense variants with REVEL > 0.7.
Evidence considered
PTEN VCEP PP3 specification (cspec materials): 'To be applied to synonymous or intronic variants where SpliceAI and VarSeak in silico models predict a splicing impact... May also be applied to missense variants with REVEL score > 0.7.' The variant here is a frameshift duplication, outside both scopes.
SpliceAI lookup for NM_000314.6:c.674_675dup shows max delta score = 0.103 (DS_AG=0.103, DS_AL=0.011, DS_DG=0.014, DS_DL=0.001), but this is not applied toward PP3/BP4 because the variant type (frameshift) is excluded from the VCEP's splice-impact pathway scope.
REVEL and BayesDel scores were both null/not found in prefetch data; not applicable to a frameshift variant in any case.
PP5VCEPNot applicable: the ClinVar record has only a single one-star laboratory submission, insufficient for PP5.
Details ▾Hide ▴
Reasoning
PP5 is not applicable under the PTEN Expert Panel specification. Independently, the exact-variant ClinVar record has only one laboratory submission with a one-star 'criteria provided, single submitter' review status and no expert-panel assertion, so it cannot support PP5.
VCEP rule
PTEN EP: PP5 not applicable. Under the requested restriction, only an exact-variant ClinVar expert-panel Pathogenic/Likely pathogenic assertion could otherwise be considered.
Evidence considered
The PTEN EP specification designates PP5 as not applicable.
ClinVar variation 1456603 is Pathogenic from Labcorp Genetics with review status 'criteria provided, single submitter'; the ClinVar data contain no expert-panel assertion.
Still missing
No exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic assertion is available.
BP1VCEPNot applicable: BP1 addresses missense variants in genes where truncation causes disease; the panel marks it not applicable for PTEN.
Details ▾Hide ▴
Reasoning
The PTEN VCEP cspec v3.2 explicitly marks BP1 as 'Not Applicable' at the gene-specification level for PTEN, independent of variant type. Additionally BP1 (missense variant in a gene where truncating variants cause disease) would not apply mechanistically to this frameshift/truncating variant even under a generic framework, since BP1 is designed to argue against missense variants in genes with a truncating disease mechanism.
Evidence considered
PTEN VCEP cspec v3.2 lists BP1 with applicability: 'Not Applicable' for this gene specification.
Even under generic ACMG, BP1 targets missense variants in genes where truncating variants are the known mechanism; this variant is itself a frameshift/truncating variant, not a missense variant, so BP1's applicability logic does not fit.
BP3VCEPNot applicable: BP3 addresses in-frame indels in repetitive regions; this is a frameshift duplication, and the panel marks BP3 not applicable for PTEN.
Details ▾Hide ▴
Reasoning
The PTEN VCEP (cspec v3.2) explicitly marks BP3 as Not Applicable for this gene. Independently, BP3 (in-frame indel in a repetitive region with no known functional significance) would not apply on generic grounds either, since c.674_675dupAT is a frameshift-producing duplication rather than an in-frame insertion/deletion.
VCEP rule
PTEN VCEP: BP3 applicability = Not Applicable.
Evidence considered
PTEN VCEP cspec v3.2 lists BP3 with applicability 'Not Applicable' for this gene/framework.
The variant is an out-of-frame duplication causing a frameshift, not an in-frame insertion/deletion, so BP3's underlying rationale (protein length unchanged by in-frame repeat-region indel) does not fit the variant type regardless of gene-level applicability.
BP4N/ANot applicable: BP4 is restricted to synonymous, intronic, or missense variants; this frameshift is outside its scope.
Details ▾Hide ▴
Reasoning
Variant NM_000314.6:c.674_675dupAT is a coding frameshift duplication, not a synonymous, intronic, or missense variant. Per the PTEN VCEP specification, BP4 applies only to (a) synonymous or intronic variants where SpliceAI (0-0.2) and VarSeak (Class 1-2) concordantly predict no splicing impact, or (b) missense variants with REVEL score < 0.5. This frameshift variant falls outside both defined scopes, so BP4 is not applicable regardless of the SpliceAI score (max delta = 0.103, which would fall in the benign range 0-0.2 if this pathway applied to this variant type, but the VCEP restricts this pathway to synonymous/intronic variants only). REVEL and BayesDel scores are not available and are not relevant to a frameshift consequence.
Rule
PTEN VCEP: BP4 supporting - splicing variants (synonymous/intronic) with SpliceAI (0-0.2) + VarSeak (Class 1-2) concordance for no impact, or missense variants with REVEL < 0.5.
Evidence considered
PTEN VCEP BP4 specification (cspec materials): 'To be applied to synonymous or intronic variants where SpliceAI and VarSeak in silico models predict no splicing impact (SpliceAI: scores 0-0.2 are considered evidence of benign)... May also be applied to missense variants with REVEL score < 0.5.' Variant is frameshift, outside both scopes.
SpliceAI lookup for NM_000314.6:c.674_675dup: max delta score = 0.103, which is numerically within the 0-0.2 benign-supportive range specified by the VCEP, but this pathway is not invoked because the variant is a frameshift duplication, not a synonymous or intronic variant.
REVEL and BayesDel scores were both null/not found in prefetch data; BayesDel is also not treated as calibrated for PP3/BP4 in this pipeline absent a named, cited publication threshold.
BP6VCEPNot applicable: the ClinVar record is a single one-star Pathogenic submission, not a benign expert-panel assertion.
Details ▾Hide ▴
Reasoning
BP6 is not applicable under the PTEN Expert Panel specification. The exact-variant ClinVar record is a one-star Pathogenic laboratory submission, not a Benign/Likely benign expert-panel assertion, and therefore cannot support BP6.
VCEP rule
PTEN EP: BP6 not applicable. Under the requested restriction, only an exact-variant ClinVar expert-panel Benign/Likely benign assertion could otherwise be considered.
Evidence considered
The PTEN EP specification designates BP6 as not applicable.
ClinVar variation 1456603 has one Pathogenic laboratory submission with review status 'criteria provided, single submitter' and no expert-panel assertion.
Still missing
No exact-variant ClinVar expert-panel Benign or Likely benign assertion is available.
BP7N/ANot applicable: BP7 applies only to synonymous or deep intronic variants; this is a frameshift duplication.
Details ▾Hide ▴
Reasoning
BP7 per both the generic ACMG/AMP rule and the PTEN VCEP specification applies only to synonymous variants (or intronic variants at or beyond +7/-21) for which splicing prediction algorithms predict no impact. NM_000314.6:c.674_675dupAT is a frameshift duplication (coding, protein-altering), not a synonymous or intronic variant, so BP7 does not apply.
Rule
PTEN VCEP / generic ACMG: BP7 supporting - synonymous or deep intronic (+7/-21) variant predicted not to impact splicing.
Evidence considered
PTEN VCEP BP7 specification (cspec materials): 'A synonymous variant for which splicing prediction algorithms predict no impact to the splice consensus sequence... Intronic variants must be positioned at or beyond +7/-21.' Variant is a frameshift duplication, not synonymous or intronic, so this criterion's scope is not met.
Every interpreted variant in PTEN, mapped onto the exon structure of NM_000314.6. Select a row to find it on the plot.
PTENNM_000314.6
Fetching transcript structure from UCSC…
Exons
—
Transcript span
—
Strand
—
Variants mapped
—
Source
UCSC ncbiRefSeqCurated
All variants in PTEN—Select a row to find it on the plot; use the link to open its page.
Protein
Location
Classification
Link
gnomAD v4.1Allele count data not recorded
gnomAD v2.1Allele count data not recorded
gnomAD-Canada v1.0Allele 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 -178 bp
0.011
SpliceAI acceptor gainat +20 bp
0.103
SpliceAI donor lossat -132 bp
0.001
SpliceAI donor gainat -55 bp
0.014
Pangolin splice lossmagnitude shown
-0.038
Pangolin splice gain
0.132
Other predictors
REVEL
Not available
BayesDel
Not available
How the predictions were used
PP3N/ANot applicable: PP3 applies only to synonymous, intronic, or missense variants; this frameshift falls outside all three pathways.
Details ▾Hide ▴
Reasoning
Variant NM_000314.6:c.674_675dupAT is a coding frameshift duplication, not a synonymous, intronic, or missense variant. Per the PTEN VCEP (ClinGen) specification, PP3 applies only to (a) synonymous or intronic variants assessed via SpliceAI/VarSeak concordance, or (b) missense variants via REVEL score > 0.7. This frameshift variant falls into neither category, so the VCEP's calibrated PP3 pathway is not applicable. REVEL/BayesDel scores are not available (null) and would not apply to a frameshift variant regardless. SpliceAI max delta score of 0.103 was computed but is not evidentiary here since the VCEP restricts splice-based PP3/BP4 to synonymous/intronic variants only.
Rule
PTEN VCEP: PP3 supporting - splicing variants (synonymous/intronic) with SpliceAI+VarSeak concordance for pathogenic impact, or missense variants with REVEL > 0.7.
Evidence considered
PTEN VCEP PP3 specification (cspec materials): 'To be applied to synonymous or intronic variants where SpliceAI and VarSeak in silico models predict a splicing impact... May also be applied to missense variants with REVEL score > 0.7.' The variant here is a frameshift duplication, outside both scopes.
SpliceAI lookup for NM_000314.6:c.674_675dup shows max delta score = 0.103 (DS_AG=0.103, DS_AL=0.011, DS_DG=0.014, DS_DL=0.001), but this is not applied toward PP3/BP4 because the variant type (frameshift) is excluded from the VCEP's splice-impact pathway scope.
REVEL and BayesDel scores were both null/not found in prefetch data; not applicable to a frameshift variant in any case.
BP4N/ANot applicable: BP4 is restricted to synonymous, intronic, or missense variants; this frameshift is outside its scope.
Details ▾Hide ▴
Reasoning
Variant NM_000314.6:c.674_675dupAT is a coding frameshift duplication, not a synonymous, intronic, or missense variant. Per the PTEN VCEP specification, BP4 applies only to (a) synonymous or intronic variants where SpliceAI (0-0.2) and VarSeak (Class 1-2) concordantly predict no splicing impact, or (b) missense variants with REVEL score < 0.5. This frameshift variant falls outside both defined scopes, so BP4 is not applicable regardless of the SpliceAI score (max delta = 0.103, which would fall in the benign range 0-0.2 if this pathway applied to this variant type, but the VCEP restricts this pathway to synonymous/intronic variants only). REVEL and BayesDel scores are not available and are not relevant to a frameshift consequence.
Rule
PTEN VCEP: BP4 supporting - splicing variants (synonymous/intronic) with SpliceAI (0-0.2) + VarSeak (Class 1-2) concordance for no impact, or missense variants with REVEL < 0.5.
Evidence considered
PTEN VCEP BP4 specification (cspec materials): 'To be applied to synonymous or intronic variants where SpliceAI and VarSeak in silico models predict no splicing impact (SpliceAI: scores 0-0.2 are considered evidence of benign)... May also be applied to missense variants with REVEL score < 0.5.' Variant is frameshift, outside both scopes.
SpliceAI lookup for NM_000314.6:c.674_675dup: max delta score = 0.103, which is numerically within the 0-0.2 benign-supportive range specified by the VCEP, but this pathway is not invoked because the variant is a frameshift duplication, not a synonymous or intronic variant.
REVEL and BayesDel scores were both null/not found in prefetch data; BayesDel is also not treated as calibrated for PP3/BP4 in this pipeline absent a named, cited publication threshold.
BP7N/ANot applicable: BP7 applies only to synonymous or deep intronic variants; this is a frameshift duplication.
Details ▾Hide ▴
Reasoning
BP7 per both the generic ACMG/AMP rule and the PTEN VCEP specification applies only to synonymous variants (or intronic variants at or beyond +7/-21) for which splicing prediction algorithms predict no impact. NM_000314.6:c.674_675dupAT is a frameshift duplication (coding, protein-altering), not a synonymous or intronic variant, so BP7 does not apply.
Rule
PTEN VCEP / generic ACMG: BP7 supporting - synonymous or deep intronic (+7/-21) variant predicted not to impact splicing.
Evidence considered
PTEN VCEP BP7 specification (cspec materials): 'A synonymous variant for which splicing prediction algorithms predict no impact to the splice consensus sequence... Intronic variants must be positioned at or beyond +7/-21.' Variant is a frameshift duplication, not synonymous or intronic, so this criterion's scope is not met.
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.10).
5 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.
A clinical scoring system for selection of patients for PTEN mutation testing is proposed on the basis of a prospective study of 3042 probands.
This prospective study of 3,042 probands developed PTEN phenotype scoring for mutation-testing referral and reports aggregate mutation-spectrum and phenotype data. It does not mention NM_000314.6:c.674_675dup or p.(Ser226IlefsTer31), so it supplies no exact-variant proband observations for PS4.
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 has been reported in ClinVar as Pathogenic (1 clinical laboratory). (ClinVarID = 1456603)
In silico
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.10).
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 previously been reported in somatic cancers (COSMIC; COSV99058014, n = 1 times).
Cancer Hotspots
This variant does not lie in a statistically significant hotspot.
This variant was interpreted by pipeline 7.1.5.
The current version is 11.0.07.
Re-running queues a fresh interpretation; the result replaces this page when complete.
Re-runs are not free. Blank draws on today's public interpretation allowance; with a code, it uses one of that code's uses.