0%
Print report
Variant interpretation report

PTEN c.357dup, p.(Ala120CysfsTer6)

NM_000314.8:c.357dup NP_000305.3:p.(Ala120CysfsTer6) Frameshift · exon 5 View identifiers
Classification
Likely pathogenic

Variant description:

No variant summary was recorded for this case.

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: Full-strength PVS1 applies because the c.357 frameshift is 5' of the VCEP's c.1121 p.D375 NMD threshold in NM_000314.8.

PM2Supporting
PM2 · supporting

Met at Supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the PTEN VCEP requirement for frequency below 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.019 maximum delta

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

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

1 Uncertain significance. ClinVar API review status: no assertion criteria provided.

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; COSV64302704, 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 · 4 not met · 9 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

All four requested segregation/de novo criteria are not_assessed because the case materials provide no proband-level de novo evidence, parental testing, family segregation, meioses, or affected-relative non-segregation data.

Met · 2

PVS1 Very strongVCEPMet: Full-strength PVS1 applies because the c.357 frameshift is 5' of the VCEP's c.1121 p.D375 NMD threshold in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.357dup is a frameshift producing NP_000305.3:p.(Ala120CysfsTer6) / p.(A120Cfs*6). The governing PTEN decision tree covers nonsense or frameshift variants and assigns PVS1 when the variant is predicted to undergo NMD, disrupts at or 5' to p.D375 (c.1121), and the exon is present in the biologically relevant NM_000314.8 transcript. c.357 is 5' to c.1121, and this early truncating frameshift is therefore assigned full PVS1 without a named downgrade. The exact variant notations c.357dup, p.Ala120CysfsTer6, and p.A120Cfs*6 were not found in PVS1_DecisionTree_PTEN.pdf.txt; the file contains the governing generic decision tree rather than a variant-specific pre-assigned row.

VCEP rule
Use PTEN PVS1 decision tree. ... 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 normalization: NM_000314.8:c.357dup produces NP_000305.3:p.(Ala120CysfsTer6) / p.(A120Cfs*6), and the consequence class is frameshift.
  • PTEN PVS1_DecisionTree_PTEN.pdf, page 1: the nonsense/frameshift path assigns PVS1 for a variant predicted to undergo NMD with disruption at or 5' to p.D375 (c.1121) when the exon is present in biologically relevant transcript NM_000314.8.
  • Exact-notation search of PVS1_DecisionTree_PTEN.pdf.txt found no c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 row; no variant-specific pre-assigned code was therefore available in that file.
Still missing
  • No exact c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 entry was found in PVS1_DecisionTree_PTEN.pdf.txt; the generic VCEP decision tree was applied.
  • The case evidence identifies the consequence and governing transcript but does not provide an independently named exon number or direct experimental NMD assay; the VCEP tree path is nevertheless resolved by the early frameshift position and transcript relevance.
Sources
PM2 SupportingVCEPMet at Supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the PTEN VCEP requirement for frequency below 0.00001 (0.001%). Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PM2 at Supporting strength when the variant is absent or present below 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 below 0.00002 (0.002%). The variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP population 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 rule: databases present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present within any subpopulation, that subpopulation allele frequency must be <0.00002 (0.002%).
  • gnomAD v2.1 all-comers query: variant absent, consistent with allele frequency 0 and therefore below 0.00001 (0.001%).
  • gnomAD v4.1 all-comers query: variant absent, consistent with allele frequency 0 and therefore below 0.00001 (0.001%).
Sources

Not met · 4 · evaluated, threshold not reached

PM1 VCEPNot met: the frameshift starts at codon 120, outside the VCEP catalytic-motif intervals 90-94, 123-130, and 166-168. Details ▾Hide ▴
Reasoning

The VCEP PM1 rule defines critical catalytic-motif residues as 90-94, 123-130, and 166-168 of NP_000305.3. The queried frameshift starts at codon 120, which is outside all three approved intervals; vcep_materials.json contains no domain_tables entry for PTEN, and the hotspot assessment was negative.

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
  • CSPEC criterion PM1: approved catalytic-motif intervals are residues 90-94, 123-130, and 166-168 (NP_000305.3).
  • Variant normalization records NP_000305.3:p.(Ala120CysfsTer6), so the initiating codon is 120, outside every listed interval; vcep_materials.json has no PTEN domain_tables entry.
  • Cancer Hotspots result for PTEN A120: no statistically significant hotspot found.
Sources
cspec ↗pm5_candidates
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 assigns BA1 when the gnomAD filtering allele frequency is greater than 0.00056 (0.056%). The variant is absent from gnomAD v2.1 and gnomAD v4.1, so no allele frequency above this threshold is observed and BA1 is not met.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BA1 rule: gnomAD filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1 all-comers query for NC_000010.10:g.89692873dup / 10-89692871-G-GT: search_status absent; no allele-frequency record was returned.
  • gnomAD v4.1 all-comers query for chr10:87933114 G>GT: search_status absent; no allele-frequency record was returned.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, so its observed frequency is not within either 0.0000043–0.00056 BS1 interval. Details ▾Hide ▴
Reasoning

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

VCEP rule
gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) ... Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BS1 Strong rule: gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • ClinGen PTEN VCEP Version 3.2, BS1 Supporting rule: allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • gnomAD v2.1 all-comers query: variant absent; no filtering allele frequency was reported.
  • gnomAD v4.1 all-comers query: variant absent; no filtering allele frequency was reported.
Sources
BS2 VCEPNot met: no homozygous healthy or PHTS-unaffected individual is reported, whereas the VCEP requires one confirmed or two unconfirmed observations. Details ▾Hide ▴
Reasoning

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

VCEP rule
Observed in the homozygous state in a healthy or PHTS-unaffected individual. One observation if homozygous status confirmed, two if not confirmed. To be applied at supporting evidence level if BS1 is also applied.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2, BS2 Strong rule requires a homozygous observation in a healthy or PHTS-unaffected individual; one observation requires confirmed homozygous status and two are required if status is not confirmed.
  • gnomAD v2.1 all-comers query: variant absent, with no homozygote count or homozygous individual reported.
  • gnomAD v4.1 all-comers query: variant absent, with no homozygote count or homozygous individual reported.
Sources

Not assessed · 9 · no assessment recorded

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

The available case evidence identifies NM_000314.8:c.357dup as a PTEN frameshift but provides no proband-level documentation of de novo occurrence, parental testing, maternity or paternity confirmation, or absence of family history. Therefore the PTEN VCEP PS2 rule cannot be evaluated.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • Case evidence identifies NM_000314.8:c.357dup as a PTEN frameshift, NP_000305.3:p.(A120Cfs*6), but contains no proband-level de novo, parental-testing, maternity, paternity, or family-history data.
  • No fetched paper in the case literature packet provides variant-specific clinical, segregation, or de novo evidence for c.357dup.
Still missing
  • Document the affected proband and phenotype consistent with PTEN hamartoma tumor syndrome.
  • Provide parental testing results and whether both maternity and paternity were confirmed.
  • Document whether there is no family history of disease.
Sources
PS3 VCEPNot assessed: mmc2.xlsx has no c.357dup or p.A120Cfs*6 entry, so the VCEP's <= -1.11 phosphatase-score rule cannot be evaluated. Details ▾Hide ▴
Reasoning

The PTEN VCEP specifies PS3_Moderate for a Mighell et al. 2018 Table S2 phosphatase-assay result with phosphatase activity (cumulative score) <= -1.11, provided the variant is listed as high confidence. The governing mmc2.xlsx file was searched for c.357dup, p.Ala120CysfsTer6, and p.A120Cfs*6; none was found. The file contains nearby residue-120 missense entries such as A120C, but those are not the assessed frameshift variant. Because the available governing assay table is explicitly for PTEN missense variants and supplies no result for this frameshift, PS3 cannot be evaluated from the permitted evidence.

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 v3.2 PS3 specification: PS3_Moderate uses Mighell et al. 2018 Table S2, requires a high-confidence listing, and applies when phosphatase activity is <= -1.11.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S2 search: no row for c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6; residue-120 missense rows including A120C are different variants and were not used.
  • The assessed variant is NM_000314.8:c.357dup, predicted p.(Ala120CysfsTer6)/p.(A120Cfs*6), a frameshift rather than a Table S2 missense substitution.
Still missing
  • No exact entry for NM_000314.8:c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No permitted variant-specific functional assay result for this frameshift was available to evaluate PS3.
Sources
PS4 VCEPNot assessed: no case-control odds ratio, confidence interval, or phenotype-specificity score is available to compare with the PTEN PS4 thresholds. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 using either a sufficiently powered case-control result or phenotype-specificity scoring: an odds ratio >2 for a PHTS component phenotype with p<0.05 and a 95% confidence-interval lower limit >1.5, or specificity scores of 1-1.5 for Supporting, 2-3.5 for Moderate, 4-15.5 for Strong, and ≥16 for Very Strong. The available case evidence contains no odds ratio, p-value, confidence interval, proband phenotype, Cleveland Clinic score, pediatric phenotype score, or independent-proband count, so PS4 cannot be evaluated.

Evidence considered
  • No case-control enrichment statistic or phenotype-specificity score was present for NM_000314.8:c.357dup.
  • The available extracted publications did not mention NM_000314.8:c.357dup or NP_000305.3:p.(A120Cfs*6) and supplied no variant-specific clinical cohort evidence.
Still missing
  • Case-control odds ratio, p-value, and 95% confidence interval for a PHTS component phenotype are unavailable.
  • Proband phenotype data and PTEN VCEP specificity scores are unavailable.
Sources
PM6 VCEPNot assessed: no presumed de novo observation, affected proband documentation, family-history assessment, or parental-confirmation data is available. Details ▾Hide ▴
Reasoning

The available case evidence provides no presumed de novo observation for NM_000314.8:c.357dup, no affected proband documentation, no family-history assessment, and no information on maternity or paternity confirmation. The PTEN VCEP PM6 rule therefore cannot be evaluated.

VCEP rule
Assumed _de novo,_ but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • Case evidence contains variant normalization and consequence information but no clinical de novo observation or parental/family-history data.
  • No fetched paper in the case literature packet provides variant-specific clinical, segregation, or de novo evidence for c.357dup.
Still missing
  • Document the affected proband and phenotype consistent with PTEN hamartoma tumor syndrome.
  • Provide evidence supporting presumed de novo occurrence.
  • Document family history and whether maternity and paternity were confirmed.
Sources
PP1 VCEPNot assessed: no affected relatives, segregation results, family structure, or countable meioses are documented for c.357dup. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected relatives, unaffected relatives, family structure, variant-positive or variant-negative relatives, or countable meioses for NM_000314.8:c.357dup. The PTEN VCEP PP1 co-segregation thresholds therefore cannot be evaluated.

VCEP rule
Co-segregation with disease in multiple affected family members, with 3 or 4 meioses observed.
Evidence considered
  • The case evidence bundle contains no family segregation observations or meiosis count for NM_000314.8:c.357dup.
  • No fetched paper in the case literature packet provides variant-specific segregation evidence for c.357dup.
Still missing
  • Provide family pedigree and clinical status of relatives.
  • Provide genotype and phenotype results for informative relatives.
  • Provide the number of informative meioses across families.
Sources
BS3 VCEPNot assessed: mmc2.xlsx has no exact frameshift entry, so the VCEP's >0 phosphatase-activity rule cannot establish benign functional evidence. Details ▾Hide ▴
Reasoning

The PTEN VCEP specifies BS3_Supporting for an in vitro or in vivo study showing no damaging effect on protein function, including a Mighell et al. 2018 Table S2 phosphatase activity score > 0 for a high-confidence variant entry. The governing mmc2.xlsx file was searched for c.357dup, p.Ala120CysfsTer6, and p.A120Cfs*6; none was found. The file contains nearby residue-120 missense entries such as A120C, but those are not the assessed frameshift variant. Therefore, the permitted functional evidence does not provide a benign assay result for this frameshift, and BS3 cannot be evaluated.

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 v3.2 BS3 specification: BS3_Supporting uses an in vitro or in vivo study showing no damaging effect on protein function, with Mighell et al. 2018 phosphatase activity > 0 as the specified Table S2 path.
  • Mighell et al. 2018 supplementary data mmc2.xlsx, Table S2 search: no row for c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6; residue-120 missense rows including A120C are different variants and were not used.
  • The assessed variant is NM_000314.8:c.357dup, predicted p.(Ala120CysfsTer6)/p.(A120Cfs*6), a frameshift rather than a Table S2 missense substitution.
Still missing
  • No exact entry for NM_000314.8:c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No permitted variant-specific functional assay result demonstrating no damaging effect for this frameshift was available to evaluate BS3.
Sources
BS4 VCEPNot assessed: no affected relatives or family-level lack-of-segregation observation is documented for c.357dup. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected family members tested for NM_000314.8:c.357dup and no documented lack of segregation in one or more families. The PTEN VCEP BS4 rule cannot therefore be evaluated.

VCEP rule
Lack of segregation in affected members of one family.
Evidence considered
  • The case evidence bundle contains no affected-relative testing results and no family-level non-segregation observation for NM_000314.8:c.357dup.
  • No fetched paper in the case literature packet provides variant-specific non-segregation evidence for c.357dup.
Still missing
  • Provide family-level testing results for affected relatives.
  • Document whether the variant is absent in affected members and identify the number of families involved.
Sources
BP2 VCEPNot assessed: no cis, trans, or phase data, and no qualifying pathogenic/likely pathogenic PTEN partner observation is documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits BP2 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 documents NM_000314.8:c.357dup and a single ClinVar submission classified as uncertain significance, but provides no affected-proband observations with a pathogenic/likely pathogenic PTEN variant and no cis, trans, or phase information. The criterion therefore 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 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 normalization identifies the queried variant as NM_000314.8:c.357dup (NP_000305.3:p.(Ala120CysfsTer6)); the available case materials contain no cis, trans, or phase assignment and no qualifying affected-proband partner observation.
  • ClinVar variation 2687567 contains one clinical-laboratory submission for NM_000314.8:c.357dup, classified as uncertain significance with no assertion criteria; it does not provide a pathogenic/likely pathogenic PTEN partner or phase information.
Still missing
  • Documented affected-proband observations for NM_000314.8:c.357dup with a pathogenic or likely pathogenic PTEN variant.
  • Validated cis, trans, or phase-unknown relationship for each qualifying PTEN variant pair.
  • At least three qualifying cis and/or phase-unknown observations if the trans path is not established.
Sources
BP5 VCEPNot assessed: no two qualifying cases with a highly penetrant alternate diagnosis and non-overlapping PTEN histories are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires a variant to be found in at least two cases with an alternate molecular basis, with the other gene/disorder considered highly penetrant and each patient's personal or family history demonstrating no overlap between the other gene and PTEN. The available evidence provides no qualifying two-case series, alternate gene diagnosis, penetrance assessment, or non-overlapping personal/family histories, so BP5 cannot be evaluated.

VCEP rule
Variant found in a case with an alternate molecular basis for disease. Other gene/disorder must be considered highly penetrant AND patient’s personal/family history must demonstrate no overlap between other gene and PTEN.
Evidence considered
  • No qualifying alternate molecular diagnosis or two-case series was documented for this variant.
  • No penetrance assessment or personal/family-history comparison excluding overlap with PTEN was documented.
Still missing
  • At least two cases with an alternate molecular basis for disease are unavailable.
  • Evidence that the alternate gene/disorder is highly penetrant and that personal/family histories do not overlap with PTEN is unavailable.
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: the queried variant is a frameshift, p.(Ala120CysfsTer6), not a missense change with a comparable amino-acid substitution. Details ▾Hide ▴
Reasoning

PS1 is not applicable because the queried variant is a frameshift, NP_000305.3:p.(Ala120CysfsTer6), rather than a missense change producing a same-amino-acid substitution; no previously established pathogenic same-amino-acid comparison can therefore be made under this 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
  • CSPEC criterion PS1: the variant is NM_000314.8:c.357dup with consequence frameshift and protein consequence NP_000305.3:p.(Ala120CysfsTer6).
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly designates PM3 as not applicable. Details ▾Hide ▴
Reasoning

Not applicable under the PTEN VCEP specification, which explicitly marks PM3 as not applicable; therefore, no recessive inheritance, affected-proband, or phase evidence is evaluated for this criterion.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN Expert Panel specification v3.2 CSPEC entry for PM3: applicability is "Not Applicable."
Sources
PM4 N/ANot applicable: The variant is a premature-termination frameshift, whereas the VCEP PM4 rule is limited to in-frame length changes, stop-loss, and protein extensions. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PM4 to protein length changes caused by in-frame deletions or insertions in a non-repeat region, stop-loss variants, in-frame indels affecting a catalytic motif, or protein extensions. NM_000314.8:c.357dup is a frameshift with a premature termination codon, not one of those PM4 variant classes, 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
  • Case normalization identifies NM_000314.8:c.357dup as a frameshift producing p.(Ala120CysfsTer6) / p.(A120Cfs*6).
  • The PTEN VCEP PM4 CSPEC entry specifies protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants, including catalytic-motif in-frame indels and protein extensions; a premature-termination frameshift is outside that scope.
  • Exact-notation searches found no matching c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 entry in PVS1_DecisionTree_PTEN.pdf.txt or mmc2.xlsx converted full text.
Still missing
  • No exact c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 entry was found in PVS1_DecisionTree_PTEN.pdf.txt or mmc2.xlsx converted full text; PM4 is excluded by consequence class without a variant-specific row.
Sources
PM5 N/ANot applicable: PM5 requires a missense change, whereas c.357dup is a frameshift producing p.(Ala120CysfsTer6). Details ▾Hide ▴
Reasoning

PM5 is not applicable because the VCEP rule requires a missense change at an amino-acid residue and comparison with a different pathogenic or likely pathogenic missense change; the queried variant is a frameshift at c.357.

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
  • CSPEC criterion PM5 requires a missense change at an amino-acid residue and a different pathogenic or likely pathogenic missense comparator.
  • The PM5 candidate record classifies NM_000314.8:c.357dup as frameshift and reports no eligible classic same-residue missense search.
Sources
cspec ↗pm5_candidates
PP2 N/ANot applicable: PP2 is limited to missense variants, while c.357dup is a frameshift producing p.(Ala120CysfsTer6). Details ▾Hide ▴
Reasoning

PP2 is not applicable because the VCEP rule is explicitly limited to a missense variant, while NM_000314.8:c.357dup is a frameshift variant producing p.(Ala120CysfsTer6).

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
  • CSPEC criterion PP2 requires a missense variant; the case normalization identifies NM_000314.8:c.357dup as a frameshift with protein consequence NP_000305.3:p.(Ala120CysfsTer6).
Sources
PP3 N/ANot applicable: c.357dup is a coding frameshift, outside PP3's synonymous/intronic splice-prediction and missense REVEL scopes. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PP3 to synonymous or intronic variants with pathogenic splice predictions from concordant SpliceAI and VarSeak models, or to missense variants with REVEL score > 0.7. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), so it is outside every variant class named by the PP3 rule. The available SpliceAI max delta of 0.019 is therefore not evidence for PP3 and is not used.

VCEP rule
To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic).  May also be applied to missense variants with REVEL score > 0.7.
Evidence considered
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP PP3 applicability instruction names synonymous or intronic variants requiring concordant SpliceAI and VarSeak predictions, and missense variants with REVEL score > 0.7; it does not name coding frameshifts.
  • SpliceAI max delta score is 0.019, but this predictor result is not used because the variant is outside the PP3 rule scope.
Sources
PP4 VCEPNot applicable: the PTEN VCEP directs phenotype-specific evidence to PS4 Use 2 rather than applying PP4. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks PP4 as not applicable and states that phenotype specificity is incorporated into PS4 Use 2 instead.

VCEP rule
PTEN EP Commentary: Phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Evidence considered
  • ClinGen PTEN VCEP criterion entry for PP4: applicability is Not applicable; its commentary states that phenotype specificity has been incorporated into PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP explicitly prohibits use of PP5 under its governing specification. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks PP5 as not applicable and explicitly 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 criterion entry for PP5: applicability is Not Applicable for this VCEP.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly marks BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks BP1 as Not Applicable.

VCEP rule
Not Applicable
Evidence considered
  • CSPEC criterion BP1 applicability: Not Applicable.
Sources
BP3 VCEPNot applicable: The PTEN VCEP explicitly marks BP3 as Not Applicable for this framework. Details ▾Hide ▴
Reasoning

The PTEN VCEP CSPEC entry explicitly marks BP3 as Not Applicable. BP3 therefore cannot be applied to this variant, regardless of its frameshift or repeat-region context.

VCEP rule
Not Applicable
Evidence considered
  • The PTEN VCEP CSPEC entry for BP3 states applicability: Not Applicable.
  • Exact-notation searches found no matching c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 entry in PVS1_DecisionTree_PTEN.pdf.txt or mmc2.xlsx converted full text.
Still missing
  • No exact c.357dup, p.Ala120CysfsTer6, or p.A120Cfs*6 entry was found in PVS1_DecisionTree_PTEN.pdf.txt or mmc2.xlsx converted full text; the VCEP's explicit BP3 applicability designation controls.
Sources
BP4 N/ANot applicable: c.357dup is a coding frameshift, outside BP4's synonymous/intronic splice-prediction and missense REVEL scopes. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4 to synonymous or intronic variants with benign splice predictions from concordant SpliceAI and VarSeak models, or to missense variants with REVEL score < 0.5. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), so it is outside every variant class named by the BP4 rule. The available SpliceAI max delta of 0.019 is therefore not evidence for BP4 and is not used.

VCEP rule
To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score \< 0.5.
Evidence considered
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP BP4 applicability instruction names synonymous or intronic variants requiring concordant SpliceAI and VarSeak predictions, and missense variants with REVEL score < 0.5; it does not name coding frameshifts.
  • SpliceAI max delta score is 0.019, but this predictor result is not used because the variant is outside the BP4 rule scope.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly prohibits use of BP6 under its governing specification. Details ▾Hide ▴
Reasoning

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

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP criterion entry for BP6: applicability is Not Applicable for this VCEP.
Sources
BP7 N/ANot applicable: c.357dup is a coding frameshift, whereas BP7 is limited to synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous (silent) or intronic variants at or beyond +7/-21. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), not a synonymous or intronic variant, so BP7 is outside scope and no splice-prediction result is needed.

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
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP BP7 rule is restricted to synonymous or intronic variants at or beyond +7/-21; this coding frameshift is outside that scope.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.357dup
Protein (HGVS p.)
NP_000305.3:p.(Ala120CysfsTer6)
GRCh38
chr10:87933114 G>GT
GRCh37
chr10:89692871 G>GT
Location and type
Exon 5 · frameshift
ClinVar
2687567
COSMIC
COSV64302704

Gene diagram

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

PTENNM_000314.8
Fetching transcript structure from UCSC…
gnomAD v4.1 Allele count data not recorded
gnomAD v2.1 Allele count data not recorded
gnomAD-Canada v1.0 Allele count data not recorded

Statements

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat +7 bp
0.006
SpliceAI acceptor gainat -119 bp
0.019
SpliceAI donor lossat +141 bp
0.000
SpliceAI donor gainat +137 bp
0.001
Pangolin splice lossmagnitude shown
-0.043
Pangolin splice gain
0.010

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: c.357dup is a coding frameshift, outside PP3's synonymous/intronic splice-prediction and missense REVEL scopes. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PP3 to synonymous or intronic variants with pathogenic splice predictions from concordant SpliceAI and VarSeak models, or to missense variants with REVEL score > 0.7. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), so it is outside every variant class named by the PP3 rule. The available SpliceAI max delta of 0.019 is therefore not evidence for PP3 and is not used.

VCEP rule
To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic).  May also be applied to missense variants with REVEL score > 0.7.
Evidence considered
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP PP3 applicability instruction names synonymous or intronic variants requiring concordant SpliceAI and VarSeak predictions, and missense variants with REVEL score > 0.7; it does not name coding frameshifts.
  • SpliceAI max delta score is 0.019, but this predictor result is not used because the variant is outside the PP3 rule scope.
Sources
BP4 N/ANot applicable: c.357dup is a coding frameshift, outside BP4's synonymous/intronic splice-prediction and missense REVEL scopes. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4 to synonymous or intronic variants with benign splice predictions from concordant SpliceAI and VarSeak models, or to missense variants with REVEL score < 0.5. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), so it is outside every variant class named by the BP4 rule. The available SpliceAI max delta of 0.019 is therefore not evidence for BP4 and is not used.

VCEP rule
To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score \< 0.5.
Evidence considered
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP BP4 applicability instruction names synonymous or intronic variants requiring concordant SpliceAI and VarSeak predictions, and missense variants with REVEL score < 0.5; it does not name coding frameshifts.
  • SpliceAI max delta score is 0.019, but this predictor result is not used because the variant is outside the BP4 rule scope.
Sources
BP7 N/ANot applicable: c.357dup is a coding frameshift, whereas BP7 is limited to synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous (silent) or intronic variants at or beyond +7/-21. NM_000314.8:c.357dup is a coding frameshift, p.(Ala120CysfsTer6), not a synonymous or intronic variant, so BP7 is outside scope and no splice-prediction result is needed.

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
  • The case variant is NM_000314.8:c.357dup, normalized as NP_000305.3:p.(Ala120CysfsTer6), a coding frameshift.
  • The VCEP BP7 rule is restricted to synonymous or intronic variants at or beyond +7/-21; this coding frameshift is outside that scope.
Sources

Statement

In silico

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

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.
    This paper does not mention PTEN c.357dup or NP_000305.3:p.(A120Cfs*6). It describes PTEN as a 403-amino-acid tumor suppressor whose N-terminal phosphatase domain is essential for its activity, including dephosphorylation of PtdIns-3,4,5-P3 and negative regulation of the PI3K/Akt pathway. No variant-specific clinical or phenotype evidence is provided.
    Does not name this variant
    PMID 11237521 ↗
    Quoted passage
    PTEN’s phosphatase domain has been the focus of numerous studies and its function is essential in PTEN’s tumor-suppressor function.

    DOMAIN STRUCTURE OF PTEN, paragraph 1

  • Essential role for nuclear PTEN in maintaining chromosomal integrity.
    The paper does not mention PTEN c.357dup or NP_000305.3:p.(A120Cfs*6), so it provides no variant-specific clinical, segregation, or population evidence for this exact variant. Its functional findings are gene-level and do not establish PS4 or BP5.
    Does not name this variant
    PMID 17218262 ↗
    Quoted passage
    Disruption of Pten leads to extensive centromere breakage and chromosomal translocations.

    Summary; Results sections 'Essential Role of PTEN in Controlling Chromosomal Integrity' and 'Physical Association of PTEN with Centromeres Is Crucial for Chromosome Stability'

  • 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
    This paper does not mention PTEN c.357dup or NP_000305.3:p.(A120Cfs*6). It states that loss of the tumor suppressor PTEN occurs in approximately 20% of localized prostate cancers and was prognostic in several small studies. No variant-specific functional, case, segregation, or population-frequency data are provided.
    Does not name this variant
    PMID 31829902 ↗
    Quoted passage
    loss of the tumor suppressor PTEN (20% of localized prostate cancers) was found to be prognostic in several small studies.

    Qualifying statements under Recommendation 1.1

  • 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 paper does not mention PTEN, c.357dup, or NP_000305.3:p.(A120Cfs*6), and provides no variant-specific clinical, segregation, or population-frequency data for this variant.
    Does not name this variant
    PMID 35924163 ↗
    Quoted passage
    For PC patients, DNA repair genes of interest include: HRR genes (most significant: BRAC2, BRCA1, ATM; others: ATR, BARD1, BRIP1, CHEK1, CHEK2, FAM175A, GEN1, MRE11A, PALB2, PPP2R2A, NBN, RAD31, RAD51B, RAD51C, RAD51D and RAD54L); MMR genes (MSH2, MSH6); Fanconi anemia genes (FANCA, FANCL); and CDK12 (3–5, 60).

    Section 3.2.3.2, HRR Gene Mutations

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

All source links

Statements for reports

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

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Uncertain significance (1 clinical laboratory). (ClinVarID = 2687567)

In silico

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

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

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.