0%
Print report
Variant interpretation report

PTEN c.585_586del, p.(Phe195LeufsTer6)

NM_000314.8:c.585_586del NP_000305.3:p.(Phe195LeufsTer6) Frameshift · exon 6 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 at very strong strength: the frameshift creates a stop at p.200, well 5' of the VCEP 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 VCEP's <0.00001 (0.001%) PM2 population-frequency requirement.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Likely pathogenic

Likely Pathogenic: PTEN VCEP Rule20 is satisfied by PVS1 (very strong) plus PM2 (supporting).

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

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

No listed criterion applied SpliceAI ↗
ClinVar submissions
Not recorded

A ClinVar laboratory submission summary was not recorded.

Context only ClinVar ↗
Functional evidence
Statement recorded

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

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

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

Cancer Hotspots

This variant 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

For this consequence-only group, the PTEN VCEP supports full-strength PVS1 for the NM_000314.8 frameshift at p.195 producing a premature stop before p.D375; PM4 and BP3 are not applicable under their VCEP rules.

PS2, PM6, PP1, and BS4 are not assessed because the available evidence contains no proband de novo documentation, parental testing, affected-family segregation, countable meioses, or affected-family non-segregation data.

PS3 and BS3 are not assessed because the governing PTEN functional-assay file has no matching variant entry and the reviewed papers provide no variant-specific functional result.

Under the ClinGen PTEN Expert Panel Version 3.2 specification, PP4, PP5, and BP6 are not applicable; PS4 and BP5 are not assessed because their required VCEP-specific evidence is unavailable.

All three requested computational criteria are not_applicable because the variant is an exonic coding frameshift, outside the variant classes named by PP3, BP4, and BP7.

Population evidence supports PM2 at supporting strength because the variant is absent from gnomAD v2.1 and v4.1; BA1, BS1, and BS2 are not met because no qualifying frequency or homozygous observation is reported.

Met · 2

PVS1 Very strongVCEPMet at very strong strength: the frameshift creates a stop at p.200, well 5' of the VCEP p.D375 NMD threshold in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.585_586del is a frameshift producing NP_000305.3:p.(Phe195LeufsTer6) / p.(F195Lfs*6). The premature stop is at amino acid 200, 175 residues 5' of the VCEP's p.D375 (c.1121) threshold, in the VCEP-designated biologically relevant transcript NM_000314.8. The PTEN VCEP PVS1 decision tree assigns PVS1 to a nonsense or frameshift variant predicted to undergo NMD when the stop codon or disruption is at or 5' to p.D375 and the exon is present in NM_000314.8; no named downgrade rule applies. The requested searches of PVS1_DecisionTree_PTEN.pdf.txt found no direct row for c.585_586del, p.Phe195LeufsTer6, or p.F195Lfs*6, so the call is based on the governing decision-tree path and case consequence facts rather than a pre-assigned variant-specific row.

VCEP rule
Use PTEN PVS1 decision tree. ... 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 consequence facts: NM_000314.8:c.585_586del is a frameshift with NP_000305.3:p.(Phe195LeufsTer6) / p.(F195Lfs*6).
  • ClinGen PTEN VCEP PVS1 decision tree: the stop/disruption is at or 5' to p.D375 (c.1121), and the biologically relevant transcript is NM_000314.8; this is the full-strength PVS1 path.
  • PVS1_DecisionTree_PTEN.pdf.txt was searched under c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no pre-assigned variant-specific row was present.
Still missing
  • PVS1_DecisionTree_PTEN.pdf.txt was searched for c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no direct variant-specific entry was found.
Sources
PM2 SupportingVCEPMet at supporting: the variant is absent from gnomAD v2.1 and v4.1, satisfying the VCEP's <0.00001 (0.001%) PM2 population-frequency requirement. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PM2 at supporting strength when a variant is present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present within a subpopulation, that subpopulation frequency must be <0.00002 (0.002%). NM_000314.8:c.585_586del is absent from the default all-comers gnomAD v2.1 and v4.1 datasets, satisfying the stated population-absence criterion.

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 instruction: criteria may be applied below 0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present within a subpopulation, that subpopulation frequency must be below 0.00002 (0.002%).
  • gnomAD v2.1 all-comers: NM_000314.8:c.585_586del absent.
  • gnomAD v4.1 all-comers: NM_000314.8:c.585_586del absent.
Sources

Not met · 4 · evaluated, threshold not reached

PM1 VCEPNot met: residue 195 is outside the VCEP catalytic motifs 90-94, 123-130, and 166-168, and no hotspot was reported. Details ▾Hide ▴
Reasoning

The VCEP defines PM1 to include PTEN catalytic-motif residues 90-94, 123-130, and 166-168 in NP_000305.3. The variant alters residue 195, outside all three explicitly defined motifs, and the case evidence reports no statistically significant hotspot for PTEN F195. No PM1 qualifying location is therefore present.

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 PM1 rule defines the included catalytic motifs as residues 90-94, 123-130, and 166-168 of NP_000305.3; the variant is p.(Phe195LeufsTer6), affecting residue 195.
  • The hotspot query for PTEN F195 reported no statistically significant hotspot.
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 BA1 rule requires a gnomAD filtering allele frequency >0.00056 (0.056%). NM_000314.8:c.585_586del is absent from gnomAD v2.1 and gnomAD v4.1, so no qualifying population frequency is present 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: NM_000314.8:c.585_586del absent; no allele frequency or homozygote count reported.
  • gnomAD v4.1 all-comers: NM_000314.8:c.585_586del absent; no allele frequency or homozygote count reported.
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, so its frequency is not within either VCEP BS1 interval. Details ▾Hide ▴
Reasoning

The PTEN VCEP BS1 thresholds require a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) for strong evidence, or from 0.0000043 (0.00043%) up to 0.000043 (0.0043%) for supporting evidence. NM_000314.8:c.585_586del is absent from gnomAD v2.1 and gnomAD 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: NM_000314.8:c.585_586del absent; no allele frequency reported.
  • gnomAD v4.1 all-comers: NM_000314.8:c.585_586del absent; no allele frequency reported.
Sources
BS2 VCEPNot met: no homozygous observations are reported in gnomAD v2.1 or v4.1, while the VCEP requires one confirmed or two unconfirmed observations. Details ▾Hide ▴
Reasoning

The PTEN VCEP BS2 rule requires observation in the homozygous state in a healthy or PHTS-unaffected individual, with one confirmed observation or two if homozygous status is not confirmed; the supporting rule requires two homozygous observations without clinical data or BS2 with BS1. The variant is absent from gnomAD v2.1 and v4.1, with no homozygous observations, so BS2 is not met.

VCEP rule
Observed in the homozygous state in a healthy or PHTS-unaffected individual. One observation if homozygous status confirmed, two if not confirmed. To be applied at supporting evidence level if BS1 is also applied. ... 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 rule: observed in the homozygous state in a healthy or PHTS-unaffected individual; one observation if homozygous status is confirmed and two if not confirmed; supporting level applies if BS1 is also applied.
  • ClinGen PTEN VCEP Version 3.2 BS2 supporting rule: two homozygous observations with no clinical data provided, or BS2 when BS1 is also applied.
  • gnomAD v2.1 all-comers: NM_000314.8:c.585_586del absent; no homozygous observation reported.
  • gnomAD v4.1 all-comers: NM_000314.8:c.585_586del absent; no homozygous observation reported.
Sources

Not assessed · 9 · no assessment recorded

PS2 VCEPNot assessed: no documented de novo observation with confirmed maternity and paternity, disease, and absence of family history is available. Details ▾Hide ▴
Reasoning

The case evidence contains no documented affected proband observation with confirmed maternity and paternity, no family-history assessment, and no parental test results. Therefore the PTEN VCEP PS2 rule cannot be evaluated without substituting unsupported assumptions.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • No proband, parental-testing, or family-history evidence relevant to PS2 was documented in the available case evidence.
  • The variant is NM_000314.8:c.585_586del, predicted as a frameshift, but variant consequence alone does not establish de novo occurrence.
Still missing
  • Affected proband documentation
  • Confirmed maternity and paternity
  • Family-history assessment
Sources
PS3 VCEPNot assessed: mmc2 Table S2 contains no matching frameshift entry, and no reviewed paper provides variant-specific functional evidence meeting a PS3 threshold. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS3 for validated functional evidence, including PS3_Moderate from Mighell et al. 2018 when the Table S2 phosphatase-assay result is high confidence and the cumulative score is ≤ -1.11, and PS3_Supporting for specified abnormal functional assays. The governing mmc2.xlsx file was searched for c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no entry was found. The variant is a frameshift, whereas mmc2 Table S2 contains missense saturation-mutagenesis variants. The two functional-theme papers in the case evidence were also reviewed through their extracted findings: neither mentions this variant or provides a variant-specific damaging assay. Therefore, the available evidence does not permit a PS3 strength assignment.

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 rule: PS3_Moderate requires phosphatase activity ≤ -1.11 per Mighell et al. 2018, PMID: 29706350; PS3_Supporting covers phosphatase activity <50% of wild type or specified abnormal cellular/transgenic assays.
  • Mighell et al. 2018 supplementary mmc2.xlsx, Table S2: searched for c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no matching row was found. The table describes protein-level missense variants and high-confidence phosphatase-assay results.
  • PTEN: life as a tumor suppressor (PMID:11237521): extracted paper finding states that c.585_586del and p.(F195Lfs*6) are not mentioned and no assay specific to this variant is described.
  • Essential role for nuclear PTEN in maintaining chromosomal integrity (PMID:17218262): extracted paper finding states that c.585_586del and p.(F195Lfs*6) are not mentioned; reported experiments concern other PTEN truncations and PTEN-null models.
Still missing
  • No c.585_586del, p.Phe195LeufsTer6, or p.F195Lfs*6 entry was found in mmc2.xlsx full text, including the Table S2 variant records.
  • No variant-specific validated damaging functional assay result is available in the reviewed case evidence.
Sources
PS4 VCEPNot assessed: no VCEP-qualified phenotype-specific proband score or case-control odds ratio, p-value, and confidence interval is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from phenotype-specific proband scores or a sufficiently powered case-control study. The available evidence provides no Cleveland Clinic score, pediatric phenotype score, independent-proband specificity total, odds ratio, p-value, or confidence interval for this variant. Therefore, no VCEP PS4 strength can be assigned.

VCEP rule
Probands with specificity score 4-15.5 (see text) OR The prevalence of the variant in affected individuals is significantly increased compared with the prevalence in controls.
Evidence considered
  • The PTEN VCEP PS4 rule provides phenotype-specific proband-score ranges and a case-control alternative.
  • No Cleveland Clinic score, pediatric phenotype score, independent-proband specificity total, odds ratio, p-value, or confidence interval for NM_000314.8:c.585_586del is present in the available case evidence.
Still missing
  • A qualifying VCEP PS4 evaluation requires independent-proband phenotype scores or a sufficiently powered case-control study with odds ratio, p-value, and 95% confidence interval.
Sources
PM6 VCEPNot assessed: no de novo observation, disease status, family-history assessment, or parental-confirmation data are documented for the required PM6 thresholds. Details ▾Hide ▴
Reasoning

The case evidence contains no assumed or presumed de novo observation in a patient with disease and no family history, and no information about maternity or paternity confirmation. None of the VCEP PM6 observation-count thresholds can therefore 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; or assumed de novo, but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • No proband-level de novo observations or parental-testing results relevant to PM6 were documented in the available case evidence.
  • No evidence establishes whether the patient has disease or no family history, so presumed, assumed, and proven de novo categories cannot be assigned.
Still missing
  • De novo observation count
  • Affected-patient documentation
  • Family-history assessment
  • Maternity and paternity confirmation status
Sources
PP1 VCEPNot assessed: no affected family members or countable segregation meioses are documented for the VCEP minimum of 3 meioses. Details ▾Hide ▴
Reasoning

The case evidence contains no affected relatives, familial genotype-phenotype observations, segregation results, or countable meioses. The VCEP PP1 thresholds of 3 or more meioses cannot be assessed.

VCEP rule
Co-segregation with disease in multiple affected family members, with >=7 meioses observed across at least two families; 5 or 6 meioses observed; or 3 or 4 meioses observed.
Evidence considered
  • No family segregation data or meiosis count relevant to PP1 was documented in the available case evidence.
  • No published paper in the available literature extracts reports segregation of NM_000314.8:c.585_586del in affected family members.
Still missing
  • Affected family-member observations
  • Familial variant testing results
  • Countable meioses
Sources
BS3 VCEPNot assessed: mmc2 Table S2 contains no matching frameshift entry, and no reviewed paper provides variant-specific functional evidence showing preserved protein function. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits BS3 for validated functional evidence showing no damaging effect, including BS3_Supporting from Mighell et al. 2018 when the Table S2 phosphatase-assay result is high confidence and the cumulative score is >0, and BS3_Strong for well-established functional studies showing no damaging effect. The governing mmc2.xlsx file was searched for c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no entry was found. The variant is a frameshift, whereas mmc2 Table S2 contains missense saturation-mutagenesis variants. The two functional-theme papers in the case evidence were also reviewed through their extracted findings: neither mentions this variant or provides a variant-specific benign functional assay. Therefore, the available evidence does not permit a BS3 strength assignment.

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 rule: BS3_Supporting permits phosphatase activity >0 per Mighell et al. 2018, PMID: 29706350; BS3_Strong requires well-established functional studies showing no damaging effect on protein function.
  • Mighell et al. 2018 supplementary mmc2.xlsx, Table S2: searched for c.585_586del, p.Phe195LeufsTer6, and p.F195Lfs*6; no matching row was found. The table describes protein-level missense variants and high-confidence phosphatase-assay results.
  • PTEN: life as a tumor suppressor (PMID:11237521): extracted paper finding states that c.585_586del and p.(F195Lfs*6) are not mentioned and no assay specific to this variant is described.
  • Essential role for nuclear PTEN in maintaining chromosomal integrity (PMID:17218262): extracted paper finding states that c.585_586del and p.(F195Lfs*6) are not mentioned; reported experiments concern other PTEN truncations and PTEN-null models.
Still missing
  • No c.585_586del, p.Phe195LeufsTer6, or p.F195Lfs*6 entry was found in mmc2.xlsx full text, including the Table S2 variant records.
  • No variant-specific validated functional assay showing no damaging effect is available in the reviewed case evidence.
Sources
BS4 VCEPNot assessed: no affected-family non-segregation observation is documented for either the one-family or two-family VCEP BS4 threshold. Details ▾Hide ▴
Reasoning

The case evidence contains no affected family members in whom the variant fails to segregate and no family-level non-segregation observations. The VCEP BS4 one-family and two-or-more-family rules cannot be evaluated.

VCEP rule
Lack of segregation in affected members of two or more families; or lack of segregation in affected members of one family.
Evidence considered
  • No affected relatives with negative variant testing or other non-segregation evidence were documented in the available case evidence.
  • No published paper in the available literature extracts reports non-segregation of NM_000314.8:c.585_586del in affected family members.
Still missing
  • Affected-family variant observations
  • Family-level non-segregation evidence
  • Number of families evaluated
Sources
BP2 VCEPNot assessed: no phase or allelic observations establish trans with one pathogenic variant or three cis/unknown-phase observations with different PTEN variants. Details ▾Hide ▴
Reasoning

The PTEN VCEP 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 affected-proband, phase, cis/trans, or other allelic observations for NM_000314.8:c.585_586del, so BP2 cannot be evaluated.

VCEP rule
Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
  • ClinGen PTEN Expert Panel Version 3.2 CSPEC rule for BP2 requires trans with a pathogenic or likely pathogenic PTEN variant, or at least three cis and/or phase-unknown observations with different pathogenic/likely pathogenic PTEN variants.
  • The case evidence reports no phase, cis/trans, compound-heterozygous, or affected-proband observations for NM_000314.8:c.585_586del.
Still missing
  • Affected-proband or other case-level observations with documented cis/trans or phase-unknown status and the accompanying pathogenic/likely pathogenic PTEN variants are unavailable.
Sources
BP5 VCEPNot assessed: no two qualifying alternate-molecular-basis cases with highly penetrant disease and non-overlapping PTEN histories are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires at least two cases with an alternate molecular basis, a highly penetrant other gene or disorder, and personal or family history demonstrating no overlap between that disorder and PTEN. No such qualifying cases or clinical-history evidence are available for this variant, so BP5 is not assessed.

VCEP rule
At least two such cases are required for criteria to apply. ... Variant found in a case with an alternate molecular basis for disease. Other gene/disorder must be considered highly penetrant AND patient’s personal/family history must demonstrate no overlap between other gene and PTEN.
Evidence considered
  • The PTEN VCEP requires at least two BP5 cases and requires a highly penetrant alternate gene or disorder with no overlap between the alternate disorder and PTEN personal or family history.
  • The available case evidence contains no documented alternate molecular diagnosis or qualifying non-overlapping clinical histories for at least two cases.
Still missing
  • At least two qualifying cases, evidence that the alternate gene or disorder is highly penetrant, and non-overlapping personal or family histories are required for BP5.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: the variant is a frameshift, not a same-amino-acid missense change or a same-position pathogenic splicing variant. Details ▾Hide ▴
Reasoning

The queried variant is NM_000314.8:c.585_586del, a frameshift producing NP_000305.3:p.(Phe195LeufsTer6), not a missense substitution that makes the same amino-acid change as a previously established pathogenic variant. It also is not a different variant at the same nucleotide position as a pathogenic splicing variant. Therefore neither PS1 path in the VCEP rule applies.

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
  • Variant normalization identifies NM_000314.8:c.585_586del as the frameshift NP_000305.3:p.(Phe195LeufsTer6).
  • No PS1-eligible same-amino-acid or same-position pathogenic splicing comparison is applicable to this frameshift.
Sources
PM3 VCEPNot applicable: the PTEN VCEP specification explicitly designates PM3 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specification explicitly marks PM3 as Not Applicable. Therefore, PM3 is not evaluated for this PTEN variant, regardless of the absence or presence of phase, affected-proband, or trans observations.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN Expert Panel Version 3.2 CSPEC entry for PM3: applicability is "Not Applicable."
Sources
PM4 N/ANot applicable: this frameshift causes premature termination at p.200, whereas PTEN PM4 is limited to in-frame length changes and stop-loss extensions. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule applies to protein length changes caused by in-frame deletions or insertions in a non-repeat region, qualifying catalytic-motif in-frame indels, and stop-loss protein extensions. NM_000314.8:c.585_586del is a frameshift producing a premature stop at p.200, not an in-frame indel or stop-loss variant; PM4 is therefore 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
  • PTEN VCEP PM4 rule limits the criterion to in-frame insertions/deletions, qualifying catalytic-motif in-frame indels, and protein extensions from stop-loss variants.
  • Case consequence facts identify NM_000314.8:c.585_586del as a frameshift, NP_000305.3:p.(Phe195LeufsTer6), rather than an in-frame or stop-loss change.
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: PM5 requires a missense change, whereas NM_000314.8:c.585_586del is a frameshift. Details ▾Hide ▴
Reasoning

The VCEP PM5 rule requires a missense change at an amino-acid residue and comparison with a different pathogenic or likely pathogenic missense change at that residue. NM_000314.8:c.585_586del is a frameshift, so the criterion's required variant type is absent.

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
  • Variant normalization identifies NM_000314.8:c.585_586del as the frameshift NP_000305.3:p.(Phe195LeufsTer6), not a missense change.
Sources
PP2 N/ANot applicable: PP2 is limited by the VCEP rule to missense variants, and this variant is a frameshift. Details ▾Hide ▴
Reasoning

The VCEP PP2 rule applies to a missense variant in a gene with a low rate of benign missense variation and a common missense disease mechanism. This variant is a frameshift, not a missense variant, so PP2 does not apply.

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
  • Variant normalization identifies NM_000314.8:c.585_586del as the frameshift NP_000305.3:p.(Phe195LeufsTer6), not a missense variant.
Sources
PP3 N/ANot applicable: the variant is a coding frameshift, whereas PTEN PP3 covers synonymous or intronic splice-impact variants and missense variants with REVEL > 0.7. Details ▾Hide ▴
Reasoning

The VCEP limits PP3 to synonymous or intronic variants assessed with concordant SpliceAl and VarSeak splicing predictions, or to missense variants with REVEL > 0.7. NM_000314.8:c.585_586del is a coding frameshift, not a synonymous, intronic, or missense variant; therefore PP3 is outside its governing scope and the available SpliceAI score 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
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift, predicted p.(Phe195LeufsTer6).
  • The VCEP PP3 specification names SpliceAl plus VarSeak for synonymous or intronic variants and REVEL > 0.7 for missense variants; neither path covers this frameshift.
Sources
PP4 VCEPNot applicable: the PTEN VCEP marks PP4 not applicable and incorporates phenotype specificity into PS4 Use 2. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification marks PP4 as not applicable and states that phenotype specificity is incorporated into PS4 Use 2. PP4 is not assigned independently.

VCEP rule
Not applicable
Evidence considered
  • The PTEN VCEP CSPEC entry lists PP4 as Not applicable.
  • The PTEN VCEP states that phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP states that PP5 is not for use under the VCEP Review Committee recommendation. Details ▾Hide ▴
Reasoning

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

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP CSPEC entry lists PP5 as Not Applicable for this VCEP.
  • The governing PP5 instruction states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP1 VCEPNot applicable: the ClinGen PTEN VCEP specification marks BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP specification marks BP1 as Not Applicable.

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

The ClinGen PTEN VCEP marks BP3 as Not Applicable. BP3 therefore cannot be applied to this variant under the governing PTEN framework, regardless of the frameshift consequence or any repeat-region assessment.

VCEP rule
Not Applicable
Evidence considered
  • The PTEN VCEP CSPEC entry for BP3 explicitly states applicability: Not Applicable.
Sources
BP4 N/ANot applicable: the variant is a coding frameshift, whereas PTEN BP4 covers synonymous or intronic variants and missense variants with REVEL < 0.5. Details ▾Hide ▴
Reasoning

The VCEP limits BP4 to synonymous or intronic variants with benign SpliceAl and VarSeak predictions, or to missense variants with REVEL < 0.5. NM_000314.8:c.585_586del is a coding frameshift, not a synonymous, intronic, or missense variant; therefore BP4 is outside its governing scope and the available SpliceAI max delta score of 0.017 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
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift, predicted p.(Phe195LeufsTer6).
  • The VCEP BP4 specification names SpliceAl plus VarSeak for synonymous or intronic variants and REVEL < 0.5 for missense variants; neither path covers this frameshift.
  • SpliceAI reported max delta score 0.017, but this predictor result is outside BP4 scope for the frameshift and is not counted.
Sources
BP6 VCEPNot applicable: the PTEN VCEP states that BP6 is not for use under the VCEP Review Committee recommendation. Details ▾Hide ▴
Reasoning

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

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP CSPEC entry lists BP6 as Not Applicable for this VCEP.
  • The governing BP6 instruction states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP7 N/ANot applicable: the variant is an exonic coding frameshift, whereas PTEN BP7 covers synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The VCEP BP7 rule applies to synonymous or intronic variants at or beyond +7/-21 with splice predictions showing no impact. NM_000314.8:c.585_586del is an exonic coding frameshift, not a synonymous or intronic variant; therefore BP7 is outside its governing scope and no splice prediction is needed for this criterion.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift in exon 6, predicted p.(Phe195LeufsTer6).
  • The VCEP BP7 specification requires a synonymous or intronic variant at or beyond +7/-21; this exonic frameshift does not meet that scope.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.585_586del
Protein (HGVS p.)
NP_000305.3:p.(Phe195LeufsTer6)
GRCh38
chr10:87952209 TTC>T
GRCh37
chr10:89711966 TTC>T
Location and type
Exon 6 · frameshift

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 -91 bp
0.016
SpliceAI acceptor gainat -74 bp
0.000
SpliceAI donor lossat +50 bp
0.017
SpliceAI donor gainat +54 bp
0.000

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: the variant is a coding frameshift, whereas PTEN PP3 covers synonymous or intronic splice-impact variants and missense variants with REVEL > 0.7. Details ▾Hide ▴
Reasoning

The VCEP limits PP3 to synonymous or intronic variants assessed with concordant SpliceAl and VarSeak splicing predictions, or to missense variants with REVEL > 0.7. NM_000314.8:c.585_586del is a coding frameshift, not a synonymous, intronic, or missense variant; therefore PP3 is outside its governing scope and the available SpliceAI score 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
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift, predicted p.(Phe195LeufsTer6).
  • The VCEP PP3 specification names SpliceAl plus VarSeak for synonymous or intronic variants and REVEL > 0.7 for missense variants; neither path covers this frameshift.
Sources
BP4 N/ANot applicable: the variant is a coding frameshift, whereas PTEN BP4 covers synonymous or intronic variants and missense variants with REVEL < 0.5. Details ▾Hide ▴
Reasoning

The VCEP limits BP4 to synonymous or intronic variants with benign SpliceAl and VarSeak predictions, or to missense variants with REVEL < 0.5. NM_000314.8:c.585_586del is a coding frameshift, not a synonymous, intronic, or missense variant; therefore BP4 is outside its governing scope and the available SpliceAI max delta score of 0.017 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
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift, predicted p.(Phe195LeufsTer6).
  • The VCEP BP4 specification names SpliceAl plus VarSeak for synonymous or intronic variants and REVEL < 0.5 for missense variants; neither path covers this frameshift.
  • SpliceAI reported max delta score 0.017, but this predictor result is outside BP4 scope for the frameshift and is not counted.
Sources
BP7 N/ANot applicable: the variant is an exonic coding frameshift, whereas PTEN BP7 covers synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The VCEP BP7 rule applies to synonymous or intronic variants at or beyond +7/-21 with splice predictions showing no impact. NM_000314.8:c.585_586del is an exonic coding frameshift, not a synonymous or intronic variant; therefore BP7 is outside its governing scope and no splice prediction is needed for this criterion.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • Variant normalization identifies NM_000314.8:c.585_586del as a coding frameshift in exon 6, predicted p.(Phe195LeufsTer6).
  • The VCEP BP7 specification requires a synonymous or intronic variant at or beyond +7/-21; this exonic frameshift does not meet that scope.
Sources

Statement

In silico

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

2 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.
    The paper does not explicitly mention PTEN c.585_586del or NP_000305.3:p.(F195Lfs*6) and describes no assay or cohort specific to this variant.
    Does not name this variant
    PMID 11237521 ↗
    Quoted passage
    PTEN is a 403-amino-acid protein which contains a phosphatase domain (residues 1–185)

    Figure 2 and the accompanying DOMAIN STRUCTURE OF PTEN section

  • Essential role for nuclear PTEN in maintaining chromosomal integrity.
    The paper does not mention PTEN c.585_586del or NP_000305.3:p.(F195Lfs*6); its experiments concern PTEN-null models and other truncating mutants, not this variant.
    Does not name this variant
    PMID 17218262 ↗
    Quoted passage
    Our data demonstrate that PTEN performs its centromere-associated function through a phosphatase-independent mechanism.

    Results, Physical Association of PTEN with Centromeres Is Crucial for Chromosome Stability, and subsequent sections on PTEN189/PTEN233 mutants

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

All source links

Statements for reports

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

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant is absent from ClinVar.

In silico

SpliceAI predicts 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 not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.