0%
Print report
Variant interpretation report

PTEN c.975del, p.Asp326ThrfsTer18

NM_000314.8:c.975del NP_000305.3:p.(Asp326ThrfsTer18) Frameshift · exon 8 View identifiers
Classification
Likely pathogenic

Variant description:

The PTEN NM_000314.8:c.975del (NP_000305.3:p.(Asp326ThrfsTer18)) frameshift variant has not previously been reported in somatic cancers (COSMIC), and lies in a statistically significant hotspot (cancerhotspots.org). This variant is predicted to result in an absent or disrupted protein product. Based on available guidelines, this variant is considered to be Likely Pathogenic.

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

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

In plain language

Gene-level background from the recorded interpretation.

About 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 8 frameshift p.D326 is 49 amino-acid positions 5' of the p.D375 NMD threshold in NM_000314.8.

PM2Supporting
PM2 · supporting

Met at supporting strength: the variant is absent from gnomAD v2.1 and v4.1, below the VCEP PM2 threshold of <0.00001 (0.001%).

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

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

No listed criterion applied SpliceAI ↗
ClinVar submissions
1 reported laboratory submissions

1 Uncertain significance.

Context only ClinVar ↗
Functional evidence
Statement recorded

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

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

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

Cancer Hotspots

This variant lies in a statistically significant hotspot.

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 · 3 not met · 10 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

No segregation or de novo criterion can be assessed from the available case-level evidence because proband, parental-testing, phenotype, family-history, relative-testing, and meiosis data are not documented.

PS4 is not assessed because the VCEP's affected-versus-control prevalence pathway and specificity-score pathway cannot be evaluated with the available variant-specific evidence.

PP4, PP5, and BP6 are not applicable under the PTEN VCEP's explicit criterion entries.

BP5 is not assessed because the required alternate highly penetrant molecular diagnosis and non-overlapping personal/family history are not documented.

Met · 2

PVS1 Very strongVCEPMet, very strong: exon 8 frameshift p.D326 is 49 amino-acid positions 5' of the p.D375 NMD threshold in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.975del is a frameshift, NP_000305.3:p.(Asp326ThrfsTer18) / p.(D326Tfs*18), in exon 8 of the biologically relevant NM_000314.8 transcript. The frameshift occurs at p.D326, which is 5' to the VCEP decision tree threshold p.D375 (c.1121), and the exon is present in the biologically relevant transcript. This follows the PTEN-specific frameshift path for a disruption at or 5' to p.D375 predicted to undergo NMD, assigning full PVS1. No named downgrade rule applies.

VCEP rule
Nonsense or frameshift | 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_variant_assessment: NM_000314.8:c.975del; frameshift; NP_000305.3:p.(Asp326ThrfsTer18) / p.(D326Tfs*18); exon 8.
  • PVS1_DecisionTree_PTEN.pdf, page 1, row 'Nonsense or frameshift': predicted NMD with stop codon or disruption at or 5' to p.D375 (c.1121), followed by presence of the exon in biologically relevant transcript NM_000314.8, assigns PVS1.
  • The variant's frameshift position p.D326 is 49 residues 5' of p.D375, satisfying the named positional branch; no downgrade branch is applicable.
Still missing
  • No variant-specific row for c.975del, p.Asp326ThrfsTer18, or p.D326Tfs*18 was found in PVS1_DecisionTree_PTEN.pdf.txt; the pre-assigned result is determined from the governing decision-tree path.
Sources
PM2 SupportingVCEPMet at supporting strength: the variant is absent from gnomAD v2.1 and v4.1, below the VCEP PM2 threshold of <0.00001 (0.001%). Details ▾Hide ▴
Reasoning

The governing PTEN VCEP PM2 rule allows PM2 at supporting strength when the variant is 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%). NM_000314.8:c.975del is absent from gnomAD v2.1 and v4.1, satisfying the stated 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 specification v3.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, that subpopulation must be <0.00002 (0.002%).
  • gnomAD v2.1: NM_000314.8:c.975del absent, consistent with allele frequency 0 in the queried dataset.
  • gnomAD v4.1: NM_000314.8:c.975del absent, consistent with allele frequency 0 in the queried dataset.
  • The available non-cancer gnomAD v2.1 and v3.1 queries also report the variant as absent; the VCEP rule does not require a non-cancer-only or exome-only source, so the all-comers gnomAD records are the governing default.
Sources

Not met · 3 · evaluated, threshold not reached

PM1 VCEPNot met: Residue 326 is outside the PTEN PM1 catalytic motifs 90–94, 123–130, and 166–168, and the VCEP names no usable somatic-hotspot source or route. Details ▾Hide ▴
Reasoning

The PTEN VCEP defines PM1 to include residues in catalytic motifs 90-94, 123-130, and 166-168 of NP_000305.3. The variant affects residue 326, outside all three specified regions. Although the collected Cancer Hotspots result reports a D326 hotspot, the PTEN VCEP rule does not name cancerhotspots.org, COSMIC, or another somatic-hotspot source or route, so that external hotspot observation cannot establish PM1 under the governing VCEP text.

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
  • PTEN VCEP PM1 rule defines the approved catalytic-motif regions as residues 90-94, 123-130, and 166-168 (NP_000305.3); the variant consequence is p.(Asp326ThrfsTer18) at residue 326.
  • Cancer Hotspots result for query PTEN D326 reports a statistically significant hotspot, but its extracted record is partial and the PTEN VCEP PM1 rule does not name Cancer Hotspots, COSMIC, or a somatic-hotspot route.
Sources
BA1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, below the VCEP BA1 threshold of >0.00056 (0.056%). Details ▾Hide ▴
Reasoning

The governing PTEN VCEP BA1 threshold is a gnomAD filtering allele frequency greater than 0.00056 (0.056%). NM_000314.8:c.975del is absent from gnomAD v2.1 and gnomAD v4.1, so its observed allele frequency is below the BA1 threshold and BA1 is not met.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP specification v3.2, BA1 rule: gnomAD filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1: NM_000314.8:c.975del absent; no allele count or frequency reported.
  • gnomAD v4.1: NM_000314.8:c.975del absent; no allele count or frequency reported.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, rather than within the VCEP BS1 range of 0.0000043–0.00056. Details ▾Hide ▴
Reasoning

The governing PTEN VCEP BS1 strong range is a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%), with a supporting range from 0.0000043 (0.00043%) up to 0.000043 (0.0043%). NM_000314.8:c.975del is absent from gnomAD v2.1 and v4.1, so no observed frequency falls within either BS1 range; BS1 is not 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 specification v3.2, BS1 strong rule: gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • ClinGen PTEN VCEP specification v3.2, BS1 supporting rule: allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • gnomAD v2.1: NM_000314.8:c.975del absent; no allele count or frequency reported.
  • gnomAD v4.1: NM_000314.8:c.975del absent; no allele count or frequency reported.
Sources

Not assessed · 10 · no assessment recorded

PS2 VCEPNot assessed: no documented proband, parental maternity/paternity confirmation, family-history status, or proven/assumed de novo observation is available. Details ▾Hide ▴
Reasoning

PS2 cannot be assessed because the available case evidence does not document a disease-affected proband with this variant, confirmed maternity and paternity, absence of family history, or multiple proven/assumed de novo observations.

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. ... De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • No case-level proband, parental-testing, family-history, or de novo-observation data are documented in the available evidence.
Still missing
  • Documented affected proband with NM_000314.8:c.975del
  • Parental testing and confirmation of maternity and paternity
  • Family-history status
  • Number and classification of proven or assumed de novo observations
Sources
PS3 VCEPNot assessed: mmc2 Table S2 has no c.975del or p.D326Tfs*18 functional-assay row meeting the VCEP's required High_conf and Cum_score evidence. Details ▾Hide ▴
Reasoning

The PTEN VCEP's PS3_Moderate path is restricted to the Mighell et al. 2018 phosphatase assay and requires a Table S2 variant entry with High_conf TRUE and Cum_score <= -1.11. The exact notations c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18 were searched throughout mmc2.xlsx.txt; none occurs in the functional Table S2 data. The broader p.D326Tfs*18 occurrence is only in Table S5's curated somatic-cancer phenotype list, without phosphatase measurements or assay controls, and therefore cannot establish PS3 at any strength. No other variant-specific functional assay evidence was available in the consulted case materials.

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 specification v3.2 PS3 rule: PS3_Moderate uses the Mighell et al. 2018 phosphatase assay when the Table S2 variant is high confidence and its cumulative score is <= -1.11.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S2: exact searches for c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18 returned no functional-assay row.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S5, row p.D326Tfs*18: Somatic cancer / Somatic Cancer / TCGA / In_gnomAD=False / In_ClinVar_pathogenic=False; no functional measurement is reported.
Still missing
  • No variant-specific phosphatase, splicing, cellular, or transgenic functional assay result with the VCEP-required controls and replicates was available.
  • mmc2.xlsx was searched for c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18; the exact notations were not found in the Table S2 functional-assay data.
Sources
PS4 VCEPNot assessed: no variant-specific affected-versus-control counts, frequency comparison, odds ratio, confidence interval, or PTEN VCEP specificity score is available. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP permits PS4 Strong when the prevalence of the variant in affected individuals is significantly increased compared with controls. The available case evidence contains no variant-specific affected-versus-control counts, case frequency, matched-ancestry gnomAD frequency, odds ratio, confidence interval, or specificity score. The literature packet's PS4 candidates were not variant-specific in the available evidence; the extracted full text for PMID:35924163 states that PTEN, c.975del, and p.(D326Tfs*18) were not reported. Therefore, PS4 cannot be evaluated from the available evidence, and no case-control comparison or numeric inequality can be made.

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 PS4 Strong rule: affected-individual prevalence must be significantly increased compared with controls; the bundle provides no variant-specific case-control counts, frequencies, odds ratio, 95% confidence interval, or specificity score.
  • PMID:35924163 paper extract: the consensus paper does not report PTEN, c.975del, or NP_000305.3:p.(D326Tfs*18), and provides no variant-specific clinical or population-frequency information.
Still missing
  • Variant-specific affected and control counts or frequencies, including matched-ancestry population controls, are needed to calculate an odds ratio and 95% confidence interval.
  • A PTEN VCEP specificity score is not available for this case.
Sources
PM6 VCEPNot assessed: no assumed de novo observation with disease status, family-history status, and parental maternity/paternity information is documented. Details ▾Hide ▴
Reasoning

PM6 cannot be assessed because the available case evidence does not document an assumed de novo observation in a disease-affected proband, the absence of family history, or the status of maternity and paternity confirmation.

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
  • No case-level de novo, parental-testing, proband phenotype, or family-history data are documented in the available evidence.
Still missing
  • Documented affected proband with NM_000314.8:c.975del
  • Evidence that the occurrence is assumed de novo
  • Family-history status
  • Confirmation status for maternity and paternity
  • Number of presumed de novo probands if applying the stronger VCEP paths
Sources
PP1 VCEPNot assessed: no affected relatives, segregation results, or countable meioses are documented for this variant. Details ▾Hide ▴
Reasoning

PP1 cannot be assessed because the available case evidence contains no affected family members, segregation results, or countable meioses across one or more families.

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-based segregation observations or meiosis count are documented in the available evidence.
Still missing
  • Affected family members carrying the variant
  • Unaffected or non-carrier relatives where relevant
  • Segregation results and phase for each relative
  • Countable number of meioses
  • Number of families represented
Sources
BS2 Not assessed: gnomAD reports no variant observations, so no confirmed homozygous healthy or PHTS-unaffected individual can be evaluated. Details ▾Hide ▴
Reasoning

The governing PTEN VCEP BS2 rule requires observation of the variant in the homozygous state in a healthy or PHTS-unaffected individual. The available gnomAD records report the variant as absent and provide no homozygous observations or individual-level clinical information, so the homozygous-observation requirement cannot be evaluated.

Evidence considered
  • ClinGen PTEN VCEP specification v3.2, BS2 rule requires a homozygous observation in a healthy or PHTS-unaffected individual, with one observation if confirmed or two if not confirmed.
  • gnomAD v2.1 and gnomAD v4.1 report NM_000314.8:c.975del as absent and provide no homozygous observation or clinical-status record.
Still missing
  • No individual-level homozygous observation with healthy or PHTS-unaffected clinical status is available.
Sources
BS3 VCEPNot assessed: mmc2 Table S2 has no p.D326Tfs*18 functional result showing high-confidence phosphatase activity >0 for the VCEP's BS3 path. Details ▾Hide ▴
Reasoning

The PTEN VCEP's BS3_Supporting path requires a variant-specific in vitro or in vivo study showing no damaging effect, including the Mighell et al. 2018 Table S2 requirement that the variant be High_conf TRUE and have phosphatase activity >0. The exact notations c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18 were searched throughout mmc2.xlsx.txt; none occurs in the functional Table S2 data. The broader p.D326Tfs*18 occurrence is only in Table S5's curated somatic-cancer phenotype list and provides no benign functional result, so BS3 cannot be applied.

VCEP rule
_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 specification v3.2 BS3 rule: BS3_Supporting uses the Mighell et al. 2018 phosphatase assay when phosphatase activity is >0 and the assay result is otherwise eligible under the VCEP specification.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S2: exact searches for c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18 returned no functional-assay row.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S5, row p.D326Tfs*18: curated somatic-cancer phenotype entry, not a benign functional assay result.
Still missing
  • No variant-specific benign functional assay result demonstrating no damaging effect on PTEN protein function was available.
  • mmc2.xlsx was searched for c.975del, p.Asp326ThrfsTer18, and p.D326Tfs*18; the exact notations were not found in the Table S2 functional-assay data.
Sources
BS4 VCEPNot assessed: no affected relatives lacking the variant and no family count for lack of segregation are documented. Details ▾Hide ▴
Reasoning

BS4 cannot be assessed because the available case evidence does not document affected family members who lack the variant, nor the number of families in which lack of segregation was observed.

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 non-segregation observations in affected relatives or family-level count are documented in the available evidence.
Still missing
  • Affected relatives tested for the variant
  • Variant-negative results in affected relatives
  • Family identifiers and number of families with lack of segregation
Sources
BP2 VCEPNot assessed: no documented trans, cis, or phase-unknown observation with a different pathogenic or likely pathogenic PTEN variant was available. Details ▾Hide ▴
Reasoning

The PTEN VCEP specifies BP2 at Supporting strength when the variant is observed in trans with a pathogenic or likely pathogenic PTEN variant, or when there are at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants. The available case evidence does not document a qualifying trans observation, cis observation, phase-unknown observation, or a different pathogenic/likely pathogenic PTEN variant, 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
  • ClinGen PTEN Expert Panel Specification v3.2, BP2 Supporting 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."
  • The available case evidence contains no documented qualifying trans observation, cis observation, phase-unknown observation, or different pathogenic/likely pathogenic PTEN variant for NM_000314.8:c.975del.
Still missing
  • Documented phase and an identified different pathogenic or likely pathogenic PTEN variant are needed to assess BP2; alternatively, at least three qualifying cis or phase-unknown observations are needed.
Sources
BP5 VCEPNot assessed: no highly penetrant alternate molecular diagnosis and no documented personal or family history excluding overlap with PTEN are available. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires a variant to be found in a case with an alternate molecular basis for disease, with the other gene/disorder highly penetrant and the patient's personal or family history showing no overlap between that disorder and PTEN. The available case evidence does not document an alternate molecular diagnosis, its penetrance, or the required non-overlapping history. BP5 is therefore not assessed rather than inferred from the absence of a reported alternate basis.

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
  • ClinGen PTEN VCEP BP5 rule requires an alternate molecular basis, a highly penetrant other gene/disorder, and personal/family history demonstrating no overlap with PTEN; those facts are not documented in the available case evidence.
Still missing
  • An alternate molecular diagnosis and evidence that the associated disorder is highly penetrant are needed.
  • The patient's personal and family history must be documented as showing no overlap between the alternate disorder and PTEN.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: NM_000314.8:c.975del is a frameshift, p.(Asp326ThrfsTer18), rather than the missense or splicing change required by the PTEN PS1 rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP PS1 rule requires the interrogated variant to be the same amino acid change as an established pathogenic variant, or a different variant at the same nucleotide position as a pathogenic splicing variant with equivalent or greater predicted impact. NM_000314.8:c.975del is a frameshift, p.(Asp326ThrfsTer18), not a missense amino-acid substitution and not a splicing variant at the same nucleotide position; therefore PS1 does not apply.

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
  • Case normalization identifies NM_000314.8:c.975del as NP_000305.3:p.(Asp326ThrfsTer18), a frameshift; no same-amino-acid missense comparison is applicable.
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly excludes PM3 for PTEN. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification v3.2 explicitly states that PM3 is not applicable to PTEN. Therefore, phase, affected-proband observations, and inheritance evidence cannot make PM3 applicable for this gene.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN Expert Panel Specification v3.2, PM3 applicability: "This rule is not applicable to PTEN."
Sources
PM4 N/ANot applicable: c.975del is a frameshift, while the PTEN PM4 rule names only in-frame length changes and stop-loss variants. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule is limited to protein length changes caused by in-frame deletions or insertions in a non-repeat region, in-frame changes affecting a catalytic motif, or stop-loss variants. NM_000314.8:c.975del is a frameshift, not an in-frame deletion or insertion and not a stop-loss variant, so PM4 is not applicable.

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
  • vcep_materials.json cspec PM4 entry: the applicable variant classes are in-frame deletions/insertions and stop-loss variants, including in-frame catalytic-motif changes and protein extensions.
  • pvs1_variant_assessment: NM_000314.8:c.975del is classified as a frameshift.
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: The variant is a frameshift, whereas PTEN PM5 requires a missense change at a residue with a previously observed pathogenic or likely pathogenic missense change. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule is restricted to a missense change at an amino-acid residue where a different pathogenic or likely pathogenic missense change has been observed, with the interrogated variant also meeting the specified BLOSUM62 comparison. NM_000314.8:c.975del is a frameshift, so the missense PM5 rule is not applicable.

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
  • Case normalization identifies p.(Asp326ThrfsTer18), a frameshift; the PM5 candidate file records no eligible same-residue missense search because the variant is not missense.
Sources
cspec ↗pm5_candidates
PP2 N/ANot applicable: NM_000314.8:c.975del is a frameshift, not the missense variant required by the PTEN PP2 rule. 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. NM_000314.8:c.975del is a frameshift, not a missense variant, so PP2 is not applicable.

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
  • Case normalization identifies NM_000314.8:c.975del as NP_000305.3:p.(Asp326ThrfsTer18), a frameshift rather than a missense variant.
Sources
PP3 N/ANot applicable: c.975del is a coding frameshift, while the PTEN PP3 rule covers only splicing and missense variants. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP PP3 rule names only splicing variants and missense variants. NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), not a splicing or missense variant; therefore PP3 is outside its governing scope and is not applicable. The available SpliceAI result is not used because the rule does not name a frameshift path for PP3.

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 v3.2 PP3 entry: the rule specifies separate paths for splicing variants and missense variants; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources
PP4 VCEPNot applicable: the ClinGen PTEN VCEP explicitly marks PP4 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks PP4 as Not Applicable. No PP4 evidence is therefore evaluated.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP CSPEC criterion entry for PP4: Applicability = Not Applicable.
Sources
PP5 VCEPNot applicable: the ClinGen PTEN VCEP explicitly marks PP5 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks PP5 as Not Applicable. The literature packet contains no variant-specific assertion that could alter this VCEP applicability determination.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP CSPEC criterion entry for PP5: Applicability = Not Applicable.
Sources
BP1 VCEPNot applicable: The PTEN VCEP explicitly designates BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP1 as Not Applicable. No BP1 evidence is therefore evaluated or applied.

VCEP rule
Not Applicable
Evidence considered
  • The PTEN Version 3.2 CSPEC entry for BP1 states applicability: Not Applicable.
Sources
BP3 VCEPNot applicable: the PTEN VCEP CSPEC entry explicitly designates BP3 as Not Applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP CSPEC entry explicitly marks BP3 as Not Applicable. Therefore BP3 cannot be applied to this variant under the governing PTEN VCEP framework, regardless of the variant's repeat-region context.

VCEP rule
Not Applicable
Evidence considered
  • vcep_materials.json cspec BP3 entry: applicability is explicitly 'Not Applicable'.
Sources
BP4 N/ANot applicable: c.975del is a truncating frameshift, and BP4 does not apply to frameshift variants under the PTEN VCEP rule. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP4 rule names splicing variants and missense variants, but NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), outside those paths. BP4 is therefore not applicable; a no-impact splice prediction cannot negate the truncating protein consequence and is not evidence for BP4 in this situation.

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 v3.2 BP4 entry: the rule specifies separate paths for splicing variants and missense variants; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources
BP6 VCEPNot applicable: the ClinGen PTEN VCEP explicitly marks BP6 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks BP6 as Not Applicable. No BP6 evidence is therefore evaluated.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP CSPEC criterion entry for BP6: Applicability = Not Applicable.
Sources
BP7 N/ANot applicable: c.975del is a coding frameshift, whereas PTEN BP7 is limited to synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP7 rule is limited to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), so it lies outside BP7 scope and no splice-prediction evidence is evaluated for this criterion.

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 v3.2 BP7 entry: the rule is limited to synonymous or intronic variants at or beyond +7/-21; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.975del
Protein (HGVS p.)
NP_000305.3:p.(Asp326ThrfsTer18)
GRCh38
chr10:87961065 CT>C
GRCh37
chr10:89720822 CT>C
Location and type
Exon 8 · frameshift
ClinVar
2687602

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 -128 bp
0.008
SpliceAI acceptor gainat -171 bp
0.000
SpliceAI donor lossat -151 bp
0.005
SpliceAI donor gainat +298 bp
0.001
Pangolin splice lossmagnitude shown
-0.052
Pangolin splice gain
0.004

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: c.975del is a coding frameshift, while the PTEN PP3 rule covers only splicing and missense variants. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP PP3 rule names only splicing variants and missense variants. NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), not a splicing or missense variant; therefore PP3 is outside its governing scope and is not applicable. The available SpliceAI result is not used because the rule does not name a frameshift path for PP3.

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 v3.2 PP3 entry: the rule specifies separate paths for splicing variants and missense variants; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources
BP4 N/ANot applicable: c.975del is a truncating frameshift, and BP4 does not apply to frameshift variants under the PTEN VCEP rule. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP4 rule names splicing variants and missense variants, but NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), outside those paths. BP4 is therefore not applicable; a no-impact splice prediction cannot negate the truncating protein consequence and is not evidence for BP4 in this situation.

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 v3.2 BP4 entry: the rule specifies separate paths for splicing variants and missense variants; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources
BP7 N/ANot applicable: c.975del is a coding frameshift, whereas PTEN BP7 is limited to synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP7 rule is limited to synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.975del is a coding frameshift, p.(Asp326ThrfsTer18), so it lies outside BP7 scope and no splice-prediction evidence is evaluated for this criterion.

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 v3.2 BP7 entry: the rule is limited to synonymous or intronic variants at or beyond +7/-21; this variant is a coding frameshift, p.(Asp326ThrfsTer18).
Sources

Statement

In silico

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

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.

Recorded publications

  • PTEN: life as a tumor suppressor.
    No paper-specific finding is recorded.
    PMID 11237521 ↗
  • Essential role for nuclear PTEN in maintaining chromosomal integrity.
    No paper-specific finding is recorded.
    PMID 17218262 ↗
  • A practice guideline from the American College of Medical Genetics and Genomics and the National Society of Genetic Counselors: referral indications for cancer predisposition assessment.
    Hampel H et al. · 2015
    No paper-specific finding is recorded.
    PMID 25394175 ↗
  • Molecular Biomarkers in Localized Prostate Cancer: ASCO Guideline.
    Eggener SE et al. · 2020
    No paper-specific finding is recorded.
    PMID 31829902 ↗
  • Genetic Testing and Its Clinical Application in Prostate Cancer Management: Consensus Statements from the Hong Kong Urological Association and Hong Kong Society of Uro-Oncology.
    Chiu PKF et al. · 2022
    This consensus paper addresses genetic testing in prostate cancer but does not report PTEN, the coding variant c.975del, or NP_000305.3:p.(D326Tfs*18); it provides no variant-specific case-control, phenotype-specific, segregation, or population-frequency evidence for this case.
    Does not name this variant
    PMID 35924163 ↗

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

Error retrieving ClinVar entry.

In silico

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

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 lies in a statistically significant hotspot. This variant has not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant lies in a statistically significant hotspot.