0%
Print report
Variant interpretation report

PTEN c.127dup, p.Glu43GlyfsTer9

NM_000314.8:c.127dup NP_000305.3:p.(Glu43GlyfsTer9) Frameshift · exon 2 View identifiers
Classification
Likely pathogenic

Variant description:

The PTEN NM_000314.8:c.127dup (NP_000305.3:p.(Glu43GlyfsTer9)) frameshift variant has previously been reported in somatic cancers (COSMIC; COSV99057940, n = 1 time). 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: Frameshift p.Glu43GlyfsTer9 creates a premature stop before p.D375 in transcript NM_000314.8, meeting the VCEP's full PVS1 path.

PM2Supporting
PM2 · supporting

Met, Supporting: the variant is absent from gnomAD v2.1, v4.1, and non-cancer subsets, below the VCEP's <0.00001 (0.001%) PM2 threshold.

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

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

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

2 Pathogenic. ClinVar API review status: criteria provided, multiple submitters, no conflicts.

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
1 recorded samples

This variant has previously been reported in somatic cancers (COSMIC; COSV99057940, n = 1 times).

Cancer Hotspots

This variant does not lie 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 · 8 not assessed · 15 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

PVS1 is met at very strong strength under the PTEN VCEP frameshift/NMD decision-tree path; PM4 and BP3 are not applicable under their PTEN-specific rules.

For the requested codon, residue, domain, and missense-mechanism criteria, the variant is a frameshift beginning at residue 43; only PM1 is evaluable as a location-based rule and residue 43 is outside all VCEP-specified catalytic motifs.

PS1, PM5, and PP2 are not applicable because the VCEP rules require a missense or amino-acid substitution context, and BP1 is explicitly not applicable to PTEN.

Only PS4 and BP5 are evaluable in principle under this PTEN VCEP; the available evidence does not satisfy or permit assessment of either criterion.

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

All three requested computational criteria are not applicable because NM_000314.8:c.127dup is an exonic coding frameshift, outside the variant types named by PP3/BP4 and BP7.

The available SpliceAI result was not used to assign PP3 or BP4 because the governing PTEN rules do not provide an applicable frameshift path, and BP7 excludes coding frameshifts.

Met · 2

PVS1 Very strongVCEPMet: Frameshift p.Glu43GlyfsTer9 creates a premature stop before p.D375 in transcript NM_000314.8, meeting the VCEP's full PVS1 path. Details ▾Hide ▴
Reasoning

NM_000314.8:c.127dup is a frameshift, NP_000305.3:p.(Glu43GlyfsTer9), in exon 2. The resulting premature stop is at codon 51, well 5' of p.D375 (c.1121), and exon 2 is present in the biologically relevant transcript NM_000314.8; therefore the PTEN VCEP decision tree assigns full PVS1 for a frameshift predicted to undergo NMD. The exact variant notations c.127dup, p.Glu43GlyfsTer9, and p.E43Gfs*9 were not present as individual rows in PVS1_DecisionTree_PTEN.pdf.txt, so the governing frameshift path was applied to the documented consequence and transcript facts.

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
  • Case variant facts: NM_000314.8:c.127dup; NP_000305.3:p.(Glu43GlyfsTer9)/p.(E43Gfs*9); frameshift; exon 2.
  • PVS1_DecisionTree_PTEN.pdf, page 1, row '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': c.127dup produces a premature stop at p.51, 5' of p.D375, and exon 2 is present in NM_000314.8.
  • The required searches for c.127dup, p.Glu43GlyfsTer9, and p.E43Gfs*9 returned no exact variant row in the PTEN fulltext directory.
Still missing
  • No exact c.127dup, p.Glu43GlyfsTer9, or p.E43Gfs*9 entry was found in PVS1_DecisionTree_PTEN.pdf.txt; the applicable frameshift decision-tree row was present and used.
Sources
PM2 SupportingVCEPMet, Supporting: the variant is absent from gnomAD v2.1, v4.1, and non-cancer subsets, below the VCEP's <0.00001 (0.001%) PM2 threshold. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits 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.127dup is absent from gnomAD v2.1, gnomAD v4.1, gnomAD v2.1 non-cancer, and gnomAD v3.1 non-cancer, satisfying the stated population-frequency requirement.

VCEP rule
Absent in population ... Databases present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population. If multiple alleles are present within any subpopulation, allele frequency in that subpopulation must be <0.00002 (0.002%).
Evidence considered
  • ClinGen PTEN VCEP Version 3.2: PM2 Supporting applies when databases show <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: NM_000314.8:c.127dup absent.
  • gnomAD v4.1: NM_000314.8:c.127dup absent.
  • GNOMAD_V2_1_NON_CANCER, exomes-only figures: NM_000314.8:c.127dup absent.
  • GNOMAD_V3_1_NON_CANCER, genomes-only figures: NM_000314.8:c.127dup absent.
Sources

Not met · 3 · evaluated, threshold not reached

PM1 VCEPNot met: the frameshift begins at residue 43, outside all VCEP-approved catalytic motifs 90-94, 123-130, and 166-168. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PM1 to residues in catalytic motifs 90-94, 123-130, and 166-168 of NP_000305.3. This variant alters residue 43 and is outside all three specified regions. The case's authoritative PTEN domain_tables entry is empty, and no VCEP-approved hotspot route is specified in the governing PM1 rule.

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 specification: catalytic motifs are residues 90-94, 123-130, and 166-168 in NP_000305.3; the variant protein consequence begins at Glu43.
  • vcep_materials.json domain_tables for PTEN is an empty object; no additional authoritative domain entry is available.
  • Hotspot evidence reports that the variant does not lie in a statistically significant hotspot, and the VCEP PM1 rule does not name a somatic hotspot source or route.
Sources
BA1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, rather than exceeding the 0.00056 (0.056%) BA1 threshold. Details ▾Hide ▴
Reasoning

The PTEN VCEP defines BA1 as a gnomAD filtering allele frequency greater than 0.00056 (0.056%). NM_000314.8:c.127dup is absent from gnomAD v2.1 and gnomAD v4.1, so no allele frequency exceeding the BA1 threshold is present.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP Version 3.2: BA1 requires gnomAD filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1: NM_000314.8:c.127dup absent; no allele frequency or homozygote count reported.
  • gnomAD v4.1: NM_000314.8:c.127dup absent; no allele frequency or homozygote count reported.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, below the 0.0000043 (0.00043%) lower BS1 Supporting boundary. Details ▾Hide ▴
Reasoning

The PTEN VCEP defines BS1 Strong as a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) and BS1 Supporting as 0.0000043 (0.00043%) up to 0.000043 (0.0043%). NM_000314.8:c.127dup is absent from gnomAD v2.1 and gnomAD v4.1, so neither BS1 frequency interval is met.

VCEP rule
gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) ... Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
Evidence considered
  • ClinGen PTEN VCEP Version 3.2: BS1 Strong requires gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • ClinGen PTEN VCEP Version 3.2: BS1 Supporting requires allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • gnomAD v2.1: NM_000314.8:c.127dup absent; no allele frequency reported.
  • gnomAD v4.1: NM_000314.8:c.127dup absent; no allele frequency reported.
Sources

Not assessed · 8 · no assessment recorded

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

The available case evidence does not document a de novo observation for NM_000314.8:c.127dup, parental testing, confirmation of both maternity and paternity, or absence of family history. Therefore, the PTEN VCEP PS2 rule cannot be evaluated.

VCEP rule
Two proven OR four assumed OR one proven + two assumed de novo observations in a patient with the disease and no family history. ... De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • No proband-level de novo, parental-testing, or family-history result for NM_000314.8:c.127dup is present in the available case evidence.
Still missing
  • Documented proband-level de novo observation is missing.
  • Parental testing with confirmation of both maternity and paternity is missing.
  • Family-history information is missing.
Sources
PS4 VCEPNot assessed: no study reports PTEN c.127dup in affected and control groups, and no proband specificity scores are available for the VCEP PS4 thresholds. 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 independent probands meeting its phenotype-specificity score thresholds; it also states PS4 may not be applied if BS1 applies. The available literature does not report this exact variant, c.127dup/p.(Glu43GlyfsTer9), in affected patients with an unaffected/control comparison or patient-level Cleveland Clinic/pediatric specificity scores. Tan et al. (PMID:21194675) reports 290/3042 probands with pathogenic PTEN mutations but does not identify c.127dup and is not an exact-variant case-control comparison. The other reviewed papers likewise do not report this variant. Therefore the VCEP PS4 rule cannot be evaluated from the available evidence; no odds ratio or 95% CI was computable.

VCEP rule
**PTEN EP Commentary:** This criterion is unlikely to be used in this manner for a condition as rare as PHTS. However, if sufficiently powered, a case-control study finding an odds ratio >2 for a PHTS component phenotype with p\<0.05 and 95% confidence interval with lower limit >1.5, this criteria may be applied. However, this criterion may _not_ be applied in combination with PP4. ... **PTEN EP Specifications:** This criterion may not be applied if BS1 applies.  Phenotype specificity scores are added across independent probands and calculated as follows: ... PS4\_Very Strong: Probands with specificity score ≥16. PS4: Probands with specificity score of 4-15.5. PS4\_Moderate: Probands with specificity score of 2-3.5. PS4\_Supporting: Proband(s) with specificity score of 1-1.5.
Evidence considered
  • ClinGen PTEN VCEP PS4 rule: the case-control route requires an odds ratio >2, p<0.05, and a 95% confidence-interval lower limit >1.5; the specificity-score route uses independent probands and the listed adult/child score thresholds.
  • Tan et al. 2011 (PMID:21194675), Results, PTEN Mutation Spectrum in Patients: 290 of 3,042 probands had germline pathogenic PTEN mutations, but the paper does not identify c.127dup or p.(Glu43GlyfsTer9) and supplies no exact-variant control comparison.
  • Zelcer et al. 2013 (PMID:23519317), Page 4, Single-gene disorders: reports 3/18 and 15/318 PTEN-positive ASD cases, but does not mention c.127dup or provide exact-variant data.
  • ACMG incidental-findings recommendations (PMID:23788249) do not mention PTEN c.127dup or p.(Glu43GlyfsTer9).
  • NCCN/ACMG/NSGC referral guideline (PMID:25394175) discusses PTEN hamartoma tumor syndrome generally but does not mention the exact variant or provide variant-level case-control or specificity-score evidence.
  • Marsh et al. 1998 (PMID:9467011), Results/Table 1: reports PTEN mutation distributions in Cowden/Bannayan-Zonana families, including insertions, but does not report c.127dup or an exact-variant control comparison.
Still missing
  • An exact-variant case-control dataset with affected and unaffected/control counts, or an exact-variant case frequency with an appropriate matched-ancestry control frequency, is needed to compute the odds ratio and 95% CI.
  • Patient-level Cleveland Clinic scores or pediatric phenotype scores for independent probands carrying this exact variant are needed to evaluate the VCEP specificity-score route.
Sources
PM6 VCEPNot assessed: no presumed or assumed de novo observation, parental-confirmation status, observation count, or family-history result is documented. Details ▾Hide ▴
Reasoning

The available case evidence does not document a presumed or assumed de novo observation of NM_000314.8:c.127dup in a proband with PTEN hamartoma tumor syndrome, the number of de novo observations, parental confirmation status, or family history. Therefore, the PTEN VCEP PM6 rule cannot be evaluated.

VCEP rule
Two proven OR four assumed OR one proven + two assumed de novo observations in a patient with the disease and no family history. ... Two probands with presumed _de novo_ occurrence (maternity/ paternity not confirmed) with the disease and no family history. * May also be used for a proband with presumed de novo occurrence for an individual with a highly specific phenotype (meets criteria to count towards PS4) ... Assumed _de novo,_ but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • No proband-level presumed or assumed de novo observation, observation count, parental-confirmation status, or family-history result for NM_000314.8:c.127dup is present in the available case evidence.
Still missing
  • Proband-level presumed or assumed de novo observation is missing.
  • The number of independent de novo observations is missing.
  • Maternity and paternity confirmation status is missing.
  • Family-history information is missing.
Sources
PP1 VCEPNot assessed: no affected relatives, informative meioses, or family-level co-segregation data are documented. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected relatives carrying NM_000314.8:c.127dup, no informative meioses, and no family-level segregation data. Therefore, the PTEN VCEP PP1 rule cannot be evaluated at supporting, moderate, or strong strength.

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 members, genotype-phenotype pairs, informative meioses, or co-segregation results for NM_000314.8:c.127dup are present in the available case evidence.
Still missing
  • Affected relatives with genotype and phenotype data are missing.
  • Informative meiosis count is missing.
  • Segregation results across families are missing.
Sources
BS2 Not assessed: gnomAD reports no variant observations, so no confirmed homozygous healthy or PHTS-unaffected individual is available for BS2. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires an observation in the homozygous state in a healthy or PHTS-unaffected individual for BS2. The available gnomAD records report the variant as absent and provide no homozygote observations; absence from gnomAD cannot establish the required homozygous observation or its clinical status.

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. ... Two homozygous observations with no clinical data provided, or meets criteria for BS2 but BS1 is also applied.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2: BS2 Strong requires one confirmed homozygous observation in a healthy or PHTS-unaffected individual, or two observations if homozygous status is not confirmed; BS2 is Supporting when there are two homozygous observations with no clinical data or when BS1 is also applied.
  • gnomAD v2.1 and gnomAD v4.1 both report NM_000314.8:c.127dup as absent, with no homozygote observations or clinical-status data.
Still missing
  • A confirmed homozygous observation in a healthy or PHTS-unaffected individual, or two unconfirmed homozygous observations, is not available.
Sources
BS4 VCEPNot assessed: no affected relative without the variant and no documented non-segregation in one or more families are available. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected family members who lack NM_000314.8:c.127dup and no documented non-segregation in one or more families. Therefore, the PTEN 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 tested negative for NM_000314.8:c.127dup and no family-level non-segregation result is present in the available case evidence.
Still missing
  • Affected relatives tested negative for the variant are missing.
  • Family-level non-segregation data are missing.
Sources
BP2 VCEPNot assessed: no documented trans observation or three qualifying cis/phase-unknown observations with different pathogenic PTEN variants are available. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP2 rule requires either observation of this 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 documented affected-proband observation, paired pathogenic/likely pathogenic PTEN variant, phase result, cis/trans relationship, or qualifying count of observations. Therefore BP2 cannot be assessed.

VCEP rule
Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP2 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."
  • Case evidence documents NM_000314.8:c.127dup (NP_000305.3:p.(Glu43GlyfsTer9)) but provides no qualifying second PTEN variant, cis/trans phase, or three qualifying observations.
Still missing
  • Documented affected-proband observations involving this variant and another pathogenic or likely pathogenic PTEN variant are unavailable.
  • Cis/trans or phase information and a qualifying observation count are unavailable.
Sources
BP5 VCEPNot assessed: no two cases document an alternate highly penetrant molecular diagnosis with personal or family histories excluding overlap with PTEN. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires at least two cases with an alternate molecular basis for disease, with the other gene/disorder considered highly penetrant and the patient's personal/family history demonstrating no overlap between that disorder and PTEN. The available case, ClinVar, population, and literature materials do not document two such cases for PTEN c.127dup, an alternate pathogenic molecular diagnosis, or the required non-overlapping histories. 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
  • ClinGen PTEN VCEP BP5 instructions require at least two such cases, a highly penetrant other gene/disorder, and no overlap between the patient's personal/family history and PTEN.
  • No available exact-variant case record documents the alternate molecular basis and the required personal/family-history exclusions.
Still missing
  • Two independent exact-variant cases with the alternate molecular diagnosis, evidence that the alternate disorder is highly penetrant, and documented non-overlapping personal/family histories are required.
Sources
Not applicable · 15· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: c.127dup causes p.(Glu43GlyfsTer9), a frameshift rather than a same-amino-acid substitution or qualifying splice-site variant. Details ▾Hide ▴
Reasoning

The variant is NM_000314.8:c.127dup, predicted to cause the frameshift p.(Glu43GlyfsTer9), not an amino-acid substitution. No same-amino-acid change or different variant at the same nucleotide position as a pathogenic splicing variant can therefore be evaluated under the PTEN VCEP PS1 rule.

VCEP rule
Same amino acid change as a previously established pathogenic variant regardless of nucleotide change OR different variant at same nucleotide position as a pathogenic splicing variant, where in silico models predict impact equal to or greater than the known pathogenic variant.
Evidence considered
  • Prefetch normalization: NM_000314.8:c.127dup is predicted to cause NP_000305.3:p.(Glu43GlyfsTer9), classified as a frameshift.
Sources
PS3 N/ANot applicable: the governing PTEN functional table is restricted to missense variants, whereas c.127dup is a frameshift with no matching assay row. Details ▾Hide ▴
Reasoning

PS3 is not applicable under the PTEN VCEP evidence scope for this variant. The governing mmc2.xlsx entry is declared for missense variants and Table S2 contains missense protein-level variants with phosphatase-assay scores; NM_000314.8:c.127dup is a frameshift, NP_000305.3:p.(Glu43GlyfsTer9)/p.(E43Gfs*9). Searches of mmc2.xlsx.txt for c.127dup, p.Glu43GlyfsTer9, and p.E43Gfs*9 found no matching entry, so no VCEP-assigned phosphatase activity value or pre-assigned PS3 code applies.

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
  • VCEP index entry for mmc2.xlsx: criteria PS3 and BS3; types: missense; Table S2 is the PTEN saturation-mutagenesis phosphatase assay table and the stated PS3_Moderate threshold is phosphatase activity ≤ -1.11.
  • mmc2.xlsx.txt, README and Table S2: the assay data are protein-level missense variants with columns Variant (one letter), Variant (three letter), Type, Cum_score, and High_conf; no row matched c.127dup, p.Glu43GlyfsTer9, or p.E43Gfs*9.
  • Case normalization: NM_000314.8:c.127dup is a frameshift producing NP_000305.3:p.(Glu43GlyfsTer9)/p.(E43Gfs*9).
Still missing
  • mmc2.xlsx searched for c.127dup: no entry found.
  • mmc2.xlsx searched for p.Glu43GlyfsTer9: no entry found.
  • mmc2.xlsx searched for p.E43Gfs*9: no entry found.
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly marks PM3 as Not Applicable. Details ▾Hide ▴
Reasoning

PM3 is not applicable under the ClinGen PTEN VCEP specification, which explicitly marks this criterion as Not Applicable. No PM3 assessment is therefore performed, regardless of the variant's frameshift consequence or the PTEN autosomal-dominant inheritance context.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 criteria entry for PM3: applicability is "Not Applicable".
Sources
PM4 N/ANot applicable: The variant is a frameshift, whereas PTEN PM4 covers only in-frame indels or stop-loss protein-length changes. Details ▾Hide ▴
Reasoning

The variant is a frameshift, not an in-frame insertion, in-frame deletion, or stop-loss variant. The PTEN VCEP PM4 rule is limited to protein length changes from in-frame indels in non-repeat regions or stop-loss variants, including in-frame indels affecting a catalytic motif or causing protein extension; this variant does not meet any named PM4 variant type.

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
  • Case variant facts classify NM_000314.8:c.127dup as a frameshift producing p.(Glu43GlyfsTer9), not an in-frame indel or stop-loss variant.
  • PTEN CSPEC PM4 entry: protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants; the stated extensions concern in-frame catalytic-motif indels and protein extension.
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: p.(Glu43GlyfsTer9) is a frameshift, while PM5 requires a missense change at the same amino-acid residue. Details ▾Hide ▴
Reasoning

The variant is a frameshift, p.(Glu43GlyfsTer9), rather than a missense change. The PTEN VCEP PM5 rule is restricted to a missense change at an amino acid residue and requires comparison with a different pathogenic or likely pathogenic missense change and its BLOSUM62 score.

VCEP rule
Missense change at an amino acid residue where a different missense change determined to be pathogenic or likely pathogenic has been seen before. In addition, variant being interrogated must have BLOSUM62 score equal to or less than the known variant.
Evidence considered
  • Prefetch normalization: NM_000314.8:c.127dup is predicted to cause NP_000305.3:p.(Glu43GlyfsTer9), classified as a frameshift.
Sources
PP2 N/ANot applicable: PP2 requires a missense variant, whereas c.127dup produces the frameshift p.(Glu43GlyfsTer9). Details ▾Hide ▴
Reasoning

The PTEN VCEP PP2 rule applies to a missense variant. NM_000314.8:c.127dup is a frameshift predicted to produce p.(Glu43GlyfsTer9), so the criterion does not apply regardless of PTEN's missense disease mechanism or benign missense variation rate.

VCEP rule
Missense variant in a gene that has a low rate of benign missense variation and where missense variants are a common mechanism of disease.
Evidence considered
  • Prefetch normalization: NM_000314.8:c.127dup is predicted to cause NP_000305.3:p.(Glu43GlyfsTer9), classified as a frameshift.
Sources
PP3 N/ANot applicable: c.127dup is a coding frameshift, whereas PTEN PP3 names only splicing variants and missense variants. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 rule specifies a splicing-variant path requiring concordance of SpliceAI and VarSeak, and a separate missense path requiring REVEL > 0.7. NM_000314.8:c.127dup is a coding frameshift, p.(Glu43GlyfsTer9), not a splicing or missense variant; therefore PP3 is outside the governing rule's stated scope. The available SpliceAI result is not used because a predictor outside the applicable variant-type path cannot establish 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 Version 3.2 PP3 rule: the named computational paths are splicing variants (concordance of SpliceAI and VarSeak) and missense variants (REVEL score > 0.7).
  • Case variant consequence: NM_000314.8:c.127dup produces NP_000305.3:p.(Glu43GlyfsTer9), a coding frameshift; no PP3 predictor path is applicable.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 Use 2 rather than permitting independent PP4 application. Details ▾Hide ▴
Reasoning

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

VCEP rule
PTEN EP Commentary: Phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Evidence considered
  • ClinGen PTEN VCEP PP4 entry: applicability is Not applicable; its commentary states that phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP explicitly prohibits PP5 use, regardless of available pathogenic reports or ClinVar classifications. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks PP5 as not applicable and states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. ClinVar and literature reports therefore cannot be used to apply PP5 under this governing framework.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP PP5 entry: applicability is Not Applicable for this VCEP and the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BS3 N/ANot applicable: the governing PTEN functional table is restricted to missense variants, and this frameshift has no matching row or benign phosphatase result. Details ▾Hide ▴
Reasoning

BS3 is not applicable under the PTEN VCEP evidence scope for this variant. The governing mmc2.xlsx entry is declared for missense variants and provides phosphatase-assay results for missense protein substitutions; NM_000314.8:c.127dup is a frameshift. Searches of mmc2.xlsx.txt for c.127dup, p.Glu43GlyfsTer9, and p.E43Gfs*9 found no matching entry, so there is no VCEP-assigned phosphatase activity value above zero or pre-assigned BS3 code for this variant.

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
  • VCEP index entry for mmc2.xlsx: criteria PS3 and BS3; types: missense; Table S2 is the PTEN saturation-mutagenesis phosphatase assay table and the stated BS3_Supporting threshold is phosphatase activity > 0.
  • mmc2.xlsx.txt, README and Table S2: the assay data are protein-level missense variants with columns Variant (one letter), Variant (three letter), Type, Cum_score, and High_conf; no row matched c.127dup, p.Glu43GlyfsTer9, or p.E43Gfs*9.
  • Case normalization: NM_000314.8:c.127dup is a frameshift producing NP_000305.3:p.(Glu43GlyfsTer9)/p.(E43Gfs*9).
Still missing
  • mmc2.xlsx searched for c.127dup: no entry found.
  • mmc2.xlsx searched for p.Glu43GlyfsTer9: no entry found.
  • mmc2.xlsx searched for p.E43Gfs*9: no entry found.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly states that BP1 is not applicable to PTEN. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP1 as not applicable to PTEN. No BP1 evidence can be assigned to this variant.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • PTEN VCEP BP1 instructions: 'This rule is not applicable to PTEN.'
Sources
BP3 VCEPNot applicable: The PTEN VCEP explicitly marks BP3 Not Applicable, and this variant is a coding frameshift rather than an in-frame deletion. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP3 as Not Applicable. The variant is also a coding frameshift rather than an in-frame deletion in a repetitive region, so BP3 cannot be applied under the governing PTEN framework.

VCEP rule
Not Applicable
Evidence considered
  • PTEN CSPEC BP3 entry explicitly states 'Not Applicable'.
  • Case variant facts classify NM_000314.8:c.127dup as a frameshift.
Sources
cspec ↗pvs1_variant_assessment
BP4 N/ANot applicable: the coding frameshift is outside PTEN BP4's named splicing-variant and missense predictor paths. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 rule specifies a splicing-variant path requiring concordance of SpliceAI and VarSeak and a missense path requiring REVEL < 0.5. NM_000314.8:c.127dup is a coding frameshift, p.(Glu43GlyfsTer9), outside both named paths. BP4 is therefore not applicable; a no-impact splice prediction cannot negate the truncating protein consequence.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores \< 0.5
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP4 rule: the named computational paths are splicing variants (concordance of SpliceAI and VarSeak) and missense variants (REVEL scores < 0.5).
  • Case variant consequence: NM_000314.8:c.127dup produces NP_000305.3:p.(Glu43GlyfsTer9), a coding frameshift; BP4 is not applicable to this truncating protein consequence.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly prohibits BP6 use, regardless of any reputable benign classification source. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks BP6 as not applicable and states that this 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
  • ClinGen PTEN VCEP BP6 entry: applicability is Not Applicable for this VCEP and the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP7 N/ANot applicable: c.127dup is an exonic coding frameshift, not a synonymous or intronic variant at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous variants or intronic variants at or beyond +7/-21 with splice-prediction results showing no impact to the splice consensus sequence or creation of a new splice. NM_000314.8:c.127dup is a coding frameshift in exon 2, not a synonymous or intronic variant; BP7 is outside scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP7 rule limits the criterion to synonymous or intronic variants at or beyond +7/-21 with no predicted splice impact.
  • Case variant consequence and location: NM_000314.8:c.127dup is a coding frameshift in exon 2, p.(Glu43GlyfsTer9), not a synonymous or intronic variant.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.127dup
Protein (HGVS p.)
NP_000305.3:p.(Glu43GlyfsTer9)
GRCh38
chr10:87894071 T>TG
GRCh37
chr10:89653828 T>TG
Location and type
Exon 2 · frameshift
ClinVar
482077
COSMIC
COSV99057940

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 -75 bp
0.007
SpliceAI acceptor gainat -7 bp
0.079
SpliceAI donor lossat +253 bp
0.001
SpliceAI donor gainat +38 bp
0.010
Pangolin splice lossmagnitude shown
-0.093
Pangolin splice gain
0.161

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: c.127dup is a coding frameshift, whereas PTEN PP3 names only splicing variants and missense variants. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 rule specifies a splicing-variant path requiring concordance of SpliceAI and VarSeak, and a separate missense path requiring REVEL > 0.7. NM_000314.8:c.127dup is a coding frameshift, p.(Glu43GlyfsTer9), not a splicing or missense variant; therefore PP3 is outside the governing rule's stated scope. The available SpliceAI result is not used because a predictor outside the applicable variant-type path cannot establish 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 Version 3.2 PP3 rule: the named computational paths are splicing variants (concordance of SpliceAI and VarSeak) and missense variants (REVEL score > 0.7).
  • Case variant consequence: NM_000314.8:c.127dup produces NP_000305.3:p.(Glu43GlyfsTer9), a coding frameshift; no PP3 predictor path is applicable.
Sources
BP4 N/ANot applicable: the coding frameshift is outside PTEN BP4's named splicing-variant and missense predictor paths. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 rule specifies a splicing-variant path requiring concordance of SpliceAI and VarSeak and a missense path requiring REVEL < 0.5. NM_000314.8:c.127dup is a coding frameshift, p.(Glu43GlyfsTer9), outside both named paths. BP4 is therefore not applicable; a no-impact splice prediction cannot negate the truncating protein consequence.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores \< 0.5
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP4 rule: the named computational paths are splicing variants (concordance of SpliceAI and VarSeak) and missense variants (REVEL scores < 0.5).
  • Case variant consequence: NM_000314.8:c.127dup produces NP_000305.3:p.(Glu43GlyfsTer9), a coding frameshift; BP4 is not applicable to this truncating protein consequence.
Sources
BP7 N/ANot applicable: c.127dup is an exonic coding frameshift, not a synonymous or intronic variant at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous variants or intronic variants at or beyond +7/-21 with splice-prediction results showing no impact to the splice consensus sequence or creation of a new splice. NM_000314.8:c.127dup is a coding frameshift in exon 2, not a synonymous or intronic variant; BP7 is outside scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 BP7 rule limits the criterion to synonymous or intronic variants at or beyond +7/-21 with no predicted splice impact.
  • Case variant consequence and location: NM_000314.8:c.127dup is a coding frameshift in exon 2, p.(Glu43GlyfsTer9), not a synonymous or intronic variant.
Sources

Statement

In silico

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

8 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 ↗
  • ACG clinical guideline: Genetic testing and management of hereditary gastrointestinal cancer syndromes.
    Syngal S et al. · 2015
    No paper-specific finding is recorded.
    PMID 25645574 ↗
  • Mutation spectrum and genotype-phenotype analyses in Cowden disease and Bannayan-Zonana syndrome, two hamartoma syndromes with germline PTEN mutation.
    Marsh DJ et al. · 1998
    Marsh et al. describe germline PTEN mutations in Cowden disease and Bannayan-Zonana syndrome families, including 10 nonsense mutations, 6 missense mutations, 6 insertions, 4 deletions, and 3 splice-site mutations among 30 Cowden disease mutations. The exact c.127dup variant is not reported, and no exact-variant control comparison is provided.
    Does not name this variant
    PMID 9467011 ↗
    Quoted passage
    Of the 30 CD PTEN mutations identified, 10 (33%) were nonsense point mutations, six (20%) were missense point mutations, six (20%) were insertions, four (13%) were deletions, three (10%) were splice site mutations and one (3%) was a deletion/insertion mutation (Figs 1 and 2).

    Results, "PTEN mutation analysis in CD and BZS," paragraph 4; Table 1

  • A clinical scoring system for selection of patients for PTEN mutation testing is proposed on the basis of a prospective study of 3042 probands.
    Tan MH et al. · 2011
    Tan et al. report a prospective multicenter cohort of 3,042 probands, of whom 290 (9.5%) had germline pathogenic PTEN mutations. The paper does not explicitly report PTEN c.127dup or p.(Glu43GlyfsTer9), so it does not provide exact-variant phenotype-specificity or case-control evidence.
    Does not name this variant
    PMID 21194675 ↗
    Quoted passage
    Of the 3042 individuals tested, 290 (9.5%) were found to have germline pathogenic PTEN mutations (Table S2).

    Results, PTEN Mutation Spectrum in Patients

  • Clinical genetics evaluation in identifying the etiology of autism spectrum disorders: 2013 guideline revisions.
    Schaefer GB et al. · 2013
    The paper summarizes PTEN mutations in autism-spectrum-disorder cohorts, including 3 of 18 patients with autism and macrocephaly and 15 of 318 patients across additional cohorts, with macrocephaly in all positive cases. It does not mention c.127dup or p.(Glu43GlyfsTer9).
    Does not name this variant
    PMID 23519317 ↗
    Quoted passage
    Of these, three patients (16%) had PTEN mutations. ... The collective data from these studies identified 15 of 318 individuals (5%) with ASDs who had pathogenic PTEN mutations. ... retrospective analysis showed that macrocephaly was present in all positive cases.

    Page 4, section "Single-gene disorders," PTEN paragraph

  • ACMG recommendations for reporting of incidental findings in clinical exome and genome sequencing.
    Green RC et al. · 2013
    The paper provides ACMG recommendations for incidental findings and does not mention PTEN, c.127dup, or p.(Glu43GlyfsTer9); it supplies no phenotype, case-control, or benign-source evidence for this variant.
    Does not name this variant
    PMID 23788249 ↗
  • 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.
    The guideline describes Cowden syndrome/PTEN hamartoma tumor syndrome and its associated cancer risks but does not mention PTEN c.127dup or p.(Glu43GlyfsTer9), and provides no exact-variant case-control or proband score data.
    Does not name this variant
    PMID 25394175 ↗
    Quoted passage
    Cowden syndrome, also known as PTEN hamartoma tumor syndrome (OMIM 158350) Cowden syndrome is caused by mutations in the PTEN gene and is characterized by benign skin findings, increased lifetime risks for breast (30–85%; often early-onset), follicular thyroid (10–38%), renal cell (34%), endometrial (5–28%), and colorectal cancers (9%), and possibly melanoma (6%).

    Page 77, section "Cowden syndrome, also known as PTEN hamartoma tumor syndrome"

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

All source links

Statements for reports

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

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Pathogenic (2 clinical laboratories). (ClinVarID = 482077)

In silico

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

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; COSV99057940, n = 1 times).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.