0%
Print report
Variant interpretation report

PTEN c.922_923insT, p.(Arg308LeufsTer4)

NM_000314.8:c.922_923insT NP_000305.3:p.(Arg308LeufsTer4) Frameshift · exon 8 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 c.922_923 frameshift is 5' of PTEN's c.1121/p.D375 NMD cutoff in NM_000314.8.

PM2Supporting
PM2 · supporting

Met at supporting strength: the variant was absent from gnomAD v2.1 and v4.1, satisfying the VCEP's <0.00001 (0.001%) population-frequency requirement.

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 Version 3.2 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.014 maximum delta

Recorded SpliceAI maximum delta score: 0.014. 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

The consequence is a PTEN frameshift at c.922_923 producing p.(Arg308LeufsTer4), before the VCEP's c.1121/p.D375 NMD cutoff; this supports full-strength PVS1.

PM4 does not apply because the variant is not an in-frame insertion/deletion, stop-loss, or protein-extension variant.

BP3 is explicitly not applicable to PTEN under the VCEP specification.

Among the requested criteria, PP4, PP5, and BP6 are explicitly not applicable under PTEN VCEP version 3.2; PS4 and BP5 lack the VCEP-required case-specific evidence and are not assessed.

Met · 2

PVS1 Very strongVCEPMet at very strong strength: the c.922_923 frameshift is 5' of PTEN's c.1121/p.D375 NMD cutoff in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.922_923insT is a frameshift producing NP_000305.3:p.(Arg308LeufsTer4) / p.(R308Lfs*4). The PTEN VCEP PVS1 workflow applies PVS1 to frameshift variants predicted to undergo NMD and places the PTEN NMD cutoff at c.1121 (p.D375). This variant disrupts the coding sequence at c.922_923, 5' of c.1121, and the decision-tree diagram explicitly 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 in the biologically relevant NM_000314.8 transcript. No exact variant row was found in PVS1_DecisionTree_PTEN.pdf.txt under c.922_923insT, p.Arg308LeufsTer4, or p.R308Lfs*4; the result is therefore based on the governing decision-tree branch rather than a pre-assigned variant-specific row.

VCEP rule
PVS1 applies to variants predicted to result in nonsense-mediated decay (NMD); the predicted NMD cutoff for PTEN occurs at c.1121 (p.D375).
Evidence considered
  • Variant normalization: NM_000314.8:c.922_923insT produces NP_000305.3:p.(Arg308LeufsTer4) / p.(R308Lfs*4), and the consequence class is frameshift.
  • ClinGen PTEN VCEP PVS1 instructions: PVS1 applies to variants predicted to result in NMD, with the predicted PTEN NMD cutoff at c.1121 (p.D375).
  • PVS1_DecisionTree_PTEN.pdf, page 1: the frameshift/nonsense branch places variants predicted to undergo NMD with a stop codon or disruption at or 5' to p.D375 on the PVS1 branch; the biologically relevant transcript is NM_000314.8.
  • Searches of PVS1_DecisionTree_PTEN.pdf.txt for c.922_923insT, p.Arg308LeufsTer4, and p.R308Lfs*4 returned no exact variant-specific row.
Still missing
  • No exact variant entry was found in PVS1_DecisionTree_PTEN.pdf.txt for c.922_923insT, p.Arg308LeufsTer4, or p.R308Lfs*4.
Sources
PM2 SupportingVCEPMet at supporting strength: the variant was absent from gnomAD v2.1 and v4.1, satisfying the VCEP's <0.00001 (0.001%) population-frequency requirement. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP PM2 rule applies at supporting strength when a variant is absent from population databases or is present at less than 0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present in a subpopulation, that subpopulation frequency must be less than 0.00002 (0.002%). The variant was absent from gnomAD v2.1 and v4.1. The VCEP does not specify a non-cancer or exome-only source for PM2, so the default all-comers gnomAD results were used.

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 rule: absent in population; databases present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population, with <0.00002 (0.002%) required in a subpopulation if multiple alleles are present.
  • gnomAD v2.1 result for NM_000314.8:c.922_923insT: search_status=absent.
  • gnomAD v4.1 result for NM_000314.8:c.922_923insT: search_status=absent.
  • No PTEN VCEP PM2 instruction in the governing criterion requires a non-cancer or exome-only population source; all-comers gnomAD v2.1 and v4.1 were used as the default sources.
Sources

Not met · 4 · evaluated, threshold not reached

PM1 VCEPNot met: residue 308 is outside the VCEP catalytic motifs 90–94, 123–130, and 166–168, with no documented hotspot evidence. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM1 rule assigns moderate evidence for a variant in a mutational hotspot or critical, well-established functional domain and specifically defines catalytic motifs at residues 90-94, 123-130, and 166-168. The variant changes residue 308 and vcep_materials.json contains no PTEN domain_tables entry adding another approved domain, so residue 308 is outside every VCEP-listed catalytic motif and no VCEP hotspot evidence is 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
  • ClinGen PTEN VCEP Version 3.2 CSPEC PM1 rule: critical functional regions include catalytic-motif residues 90-94, 123-130, and 166-168 of NP_000305.3.
  • Variant normalization places the frameshift at protein residue Arg308: NP_000305.3:p.(Arg308LeufsTer4).
  • vcep_materials.json domain_tables for PTEN is empty; therefore no additional authoritative PTEN domain-table interval is available to include.
  • Cancer Hotspots search for PTEN R308 returned no statistically significant hotspot row.
Sources
BA1 VCEPNot met: the variant was absent from gnomAD v2.1 and v4.1, rather than exceeding the >0.00056 (0.056%) BA1 threshold. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BA1 threshold is a gnomAD filtering allele frequency greater than 0.00056 (0.056%). The variant was absent from gnomAD v2.1 and gnomAD v4.1, so no allele frequency exceeding the BA1 threshold was observed. The VCEP does not specify a non-cancer or exome-only source for BA1; the default all-comers gnomAD results were therefore used.

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 result for NM_000314.8:c.922_923insT: search_status=absent; no allele-frequency or homozygote record was returned.
  • gnomAD v4.1 result for NM_000314.8:c.922_923insT: search_status=absent; no allele-frequency or homozygote record was returned.
  • No PTEN VCEP BA1 instruction in the governing criterion requires a non-cancer or exome-only population source; all-comers gnomAD v2.1 and v4.1 were used as the default sources.
Sources
BS1 VCEPNot met: the variant was absent from gnomAD v2.1 and v4.1, so its frequency did not reach the 0.0000043 (0.00043%) BS1-supporting lower bound. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP defines BS1 Strong as a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%), with a supporting range from 0.0000043 (0.00043%) up to 0.000043 (0.0043%). The variant was absent from gnomAD v2.1 and gnomAD v4.1, so neither BS1 frequency range is met. The VCEP does not specify a non-cancer or exome-only source for BS1; the default all-comers gnomAD results were used.

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 result for NM_000314.8:c.922_923insT: search_status=absent; no allele-frequency record was returned.
  • gnomAD v4.1 result for NM_000314.8:c.922_923insT: search_status=absent; no allele-frequency record was returned.
  • No PTEN VCEP BS1 instruction in the governing criterion requires a non-cancer or exome-only population source; all-comers gnomAD v2.1 and v4.1 were used as the default sources.
Sources
BS2 VCEPNot met: gnomAD v2.1 and v4.1 reported no variant observation, so no homozygous healthy or PHTS-unaffected individual was identified. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires observation of the variant in the homozygous state in a healthy or PHTS-unaffected individual. The variant was absent from gnomAD v2.1 and v4.1, and therefore there is no homozygous observation supporting BS2. The BS1-dependent supporting downgrade is not relevant because BS1 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 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; apply at supporting level if BS1 is also applied.
  • gnomAD v2.1 result for NM_000314.8:c.922_923insT: search_status=absent; no homozygous observation was returned.
  • gnomAD v4.1 result for NM_000314.8:c.922_923insT: search_status=absent; no homozygous observation was returned.
Sources

Not assessed · 9 · no assessment recorded

PS2 VCEPNot assessed: No documented proband de novo observation, confirmed maternity and paternity, disease status, or family-history evidence is available. Details ▾Hide ▴
Reasoning

No proband-level de novo observation, parental maternity/paternity testing, family history, or phenotype-specific proband evidence is documented for NM_000314.8:c.922_923insT. Therefore, the PTEN VCEP PS2 thresholds cannot be evaluated.

Evidence considered
  • The case materials contain no documented proband-level de novo observation or parental testing result for NM_000314.8:c.922_923insT.
  • The PTEN VCEP PS2 rule requires de novo observations in a patient with the disease and no family history, with strength depending on proven versus assumed observations.
Still missing
  • Proband disease status and phenotype-specific documentation
  • Confirmed maternity and paternity testing
  • Family-history status
  • Additional proven or assumed de novo observations, if any
Sources
PS3 VCEPNot assessed: mmc2.xlsx contains no matching variant entry, and no qualifying functional assay result demonstrates a damaging effect for this frameshift. Details ▾Hide ▴
Reasoning

The variant is a frameshift, NP_000305.3:p.(Arg308LeufsTer4), not a missense variant. The governing mmc2.xlsx file was searched in full for c.922_923insT, p.Arg308LeufsTer4, and p.R308Lfs*4; no entry was found. Therefore the Mighell et al. 2018 phosphatase-activity pathway cannot be evaluated for this variant. The case evidence contains no qualifying RNA, mini-gene, splicing, cellular, or other functional assay result demonstrating a damaging effect, so PS3 is not assessed rather than inferred from the predicted truncation.

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 may use RNA, mini-gene, or other assays demonstrating splicing impact; PS3_Moderate uses Mighell et al. 2018 Table S2 with high-confidence status and phosphatase activity <= -1.11.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, converted full text: searches for c.922_923insT, p.Arg308LeufsTer4, and p.R308Lfs*4 returned no matching row; the indexed assay is specified for missense variants.
  • The available case evidence identifies the variant as a frameshift, NP_000305.3:p.(Arg308LeufsTer4), and provides no variant-specific qualifying functional assay result.
Still missing
  • No matching c.922_923insT, p.Arg308LeufsTer4, or p.R308Lfs*4 entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No qualifying variant-specific functional assay result is available for PS3 assessment.
Sources
PS4 VCEPNot assessed: no PTEN phenotype-specificity score, proband count, or qualifying case-control result is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from a sufficiently powered case-control study with odds ratio >2 for a PHTS component phenotype, p<0.05, and a 95% confidence-interval lower limit >1.5, or from phenotype-specificity scores accumulated across independent probands. The available case evidence contains no qualifying case-control odds ratio, p-value, confidence interval, Cleveland Clinic score, pediatric phenotype score, or independent-proband specificity total. Therefore PS4 cannot be assessed.

VCEP rule
Probands with specificity score ≥16 (see text). ... 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. ... Probands with specificity score of 2-3.5 (see text). ... Phenotype specific for disease with single genetic etiology. Proband(s) with specificity score of 1-1.5 (see text).
Evidence considered
  • ClinGen PTEN VCEP specification v3.2: PS4 requires either a qualifying case-control result or a specificity score derived from independent probands; no such case-specific values are present in the available evidence.
Still missing
  • Qualifying case-control odds ratio, p-value, and 95% confidence interval are unavailable.
  • Independent proband phenotype scores and the resulting PS4 specificity total are unavailable.
Sources
PM6 VCEPNot assessed: No assumed de novo observation with disease status, unconfirmed maternity and paternity, and no family history is documented. Details ▾Hide ▴
Reasoning

No assumed de novo observation, proband disease status, parental maternity/paternity information, or family-history information is documented for NM_000314.8:c.922_923insT. Therefore, the PTEN VCEP PM6 thresholds cannot be evaluated.

Evidence considered
  • The case materials contain no documented presumed de novo proband observation or parental testing result for NM_000314.8:c.922_923insT.
  • The PTEN VCEP PM6 rule requires an assumed de novo observation in a patient with the disease and no family history, with stronger levels requiring multiple observations or a highly specific phenotype.
Still missing
  • Assumed de novo observation in a proband
  • Proband disease and phenotype documentation
  • Maternity and paternity testing status
  • Family-history status
  • Any additional PM6 or PS2 observations
Sources
PP1 VCEPNot assessed: No affected-family co-segregation data or meiosis count is documented, so the minimum 3-meiosis threshold cannot be evaluated. Details ▾Hide ▴
Reasoning

No affected relatives, variant-positive relatives, co-segregation observations, family count, or meiosis count is documented for NM_000314.8:c.922_923insT. Therefore, the PTEN VCEP PP1 strength thresholds cannot be evaluated.

Evidence considered
  • The case materials contain no documented family segregation results or observed meioses for NM_000314.8:c.922_923insT.
  • The PTEN VCEP PP1 rule requires co-segregation in multiple affected family members and assigns supporting, moderate, or strong evidence according to 3-4, 5-6, or at least 7 observed meioses, respectively.
Still missing
  • Affected family members tested for the variant
  • Co-segregation results and phenotype status for each relative
  • Number of observed meioses
  • Number of families represented
Sources
BS3 VCEPNot assessed: mmc2.xlsx contains no matching variant entry, and no qualifying functional study shows no damaging effect on this frameshift’s protein function. Details ▾Hide ▴
Reasoning

The variant is a frameshift, NP_000305.3:p.(Arg308LeufsTer4), not a missense variant. The governing mmc2.xlsx file was searched in full for c.922_923insT, p.Arg308LeufsTer4, and p.R308Lfs*4; no entry was found. Therefore the Mighell et al. 2018 phosphatase-activity pathway cannot be evaluated for this variant. No qualifying functional study showing no damaging effect on protein function is available, so BS3 is not assessed and no benign functional evidence is assigned.

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 may use an in vitro or in vivo functional study showing no damaging effect on protein function; Mighell et al. 2018 Table S2 requires high-confidence status and phosphatase activity > 0.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, converted full text: searches for c.922_923insT, p.Arg308LeufsTer4, and p.R308Lfs*4 returned no matching row; the indexed assay is specified for missense variants.
  • The available case evidence identifies the variant as a frameshift, NP_000305.3:p.(Arg308LeufsTer4), and provides no variant-specific qualifying benign functional assay result.
Still missing
  • No matching c.922_923insT, p.Arg308LeufsTer4, or p.R308Lfs*4 entry was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/mmc2.xlsx.txt.
  • No qualifying variant-specific functional study showing no damaging effect on protein function is available for BS3 assessment.
Sources
BS4 VCEPNot assessed: No family-level lack-of-segregation observation is documented, so the one-family and two-family thresholds cannot be evaluated. Details ▾Hide ▴
Reasoning

No affected relatives, family-level segregation analysis, or non-segregation observation is documented for NM_000314.8:c.922_923insT. Therefore, the PTEN VCEP BS4 threshold for one versus two or more families cannot be evaluated.

Evidence considered
  • The case materials contain no documented affected-family non-segregation result for NM_000314.8:c.922_923insT.
  • The PTEN VCEP BS4 rule assigns supporting evidence for lack of segregation in one family and strong evidence for lack of segregation in affected members of two or more families.
Still missing
  • Affected family members and their variant results
  • Documented lack of segregation, if present
  • Number of families with non-segregation
  • Assessment of phenotype overlap or possible phenocopies
Sources
BP2 VCEPNot assessed: no qualifying phase-resolved observation with a pathogenic or likely pathogenic PTEN variant is documented. Details ▾Hide ▴
Reasoning

BP2 is applicable in the PTEN VCEP framework, but the available case evidence documents no affected-proband observation with this variant in trans with a pathogenic or likely pathogenic PTEN variant, and no three observations in cis or phase unknown with different pathogenic or likely pathogenic PTEN variants. Phase, parental/offspring testing, and qualifying allelic observations are therefore insufficient to determine whether BP2 is met.

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 CSPEC BP2 entry: the criterion requires either observation 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 contains no documented phase, parental/offspring testing, affected-proband allelic observation, or qualifying cis/trans/unknown-phase PTEN partner variant for NM_000314.8:c.922_923insT.
Still missing
  • Phase-resolved case or family observations pairing NM_000314.8:c.922_923insT with a pathogenic or likely pathogenic PTEN variant are unavailable.
  • No documented count of at least three cis or phase-unknown observations with different pathogenic or likely pathogenic PTEN variants is available.
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/disorder, and personal or family history demonstrating no overlap between that disorder and PTEN. The available case evidence does not document two qualifying cases, an alternate molecular diagnosis, or the required non-overlapping personal/family histories. Therefore BP5 cannot be assessed.

VCEP rule
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 specification v3.2 requires at least two qualifying cases and the specified alternate-disorder penetrance and history conditions; those case details are unavailable.
Still missing
  • At least two cases with an alternate molecular basis are not documented.
  • Highly penetrant alternate gene/disorder and non-overlapping personal/family histories are not documented.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: this exonic frameshift is neither a same-amino-acid missense change nor a pathogenic splicing-site alternative. Details ▾Hide ▴
Reasoning

The PTEN VCEP PS1 rule is limited to the same amino acid change as an established pathogenic variant or a different variant at the same nucleotide position as a pathogenic splicing variant with at least equivalent predicted impact. NM_000314.8:c.922_923insT is an exonic frameshift, p.(Arg308LeufsTer4), not a missense change producing a defined amino-acid substitution and not a splice-site variant, so it lies outside the named PS1 variant types.

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
  • ClinGen PTEN VCEP Version 3.2 CSPEC PS1 rule: applies to the same amino-acid change as an established pathogenic variant or an alternative at the same nucleotide position as a pathogenic splicing variant.
  • Variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly marks PM3 as not applicable to PTEN. Details ▾Hide ▴
Reasoning

PM3 is not applicable because the ClinGen PTEN VCEP specification explicitly states that this rule is not applicable to PTEN. Therefore, phase, affected-proband observations, and inheritance evidence cannot activate PM3 under this governing framework.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 CSPEC PM3 entry: applicability is "Not applicable" and the instructions state, "This rule is not applicable to PTEN."
Sources
PM4 N/ANot applicable: the c.922_923 insertion is frameshift, whereas PTEN PM4 names only in-frame length changes, stop-loss variants, and protein extensions. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule is limited to protein length changes from in-frame insertions or deletions in a non-repeat region, in-frame changes affecting a catalytic motif, stop-loss variants, and protein extensions. NM_000314.8:c.922_923insT is a frameshift that creates a premature termination codon, not an in-frame insertion/deletion, stop-loss, or protein extension; PM4 therefore does not apply.

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
  • ClinGen PTEN VCEP PM4 rule: protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants; it also covers qualifying catalytic-motif in-frame changes and protein extensions.
  • Variant normalization identifies NM_000314.8:c.922_923insT as the frameshift p.(Arg308LeufsTer4), which is outside the variant types named by the PM4 rule.
Sources
PM5 N/ANot applicable: PM5 requires a missense variant, whereas this variant is a frameshift at c.922_923. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule requires a missense change at an amino-acid residue where a different pathogenic or likely pathogenic missense change has been observed, together with the required BLOSUM62 comparison. NM_000314.8:c.922_923insT is a frameshift, not a missense variant, so PM5 is outside its specified variant type.

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
  • ClinGen PTEN VCEP Version 3.2 CSPEC PM5 rule: requires a missense change at a residue with a previously observed pathogenic or likely pathogenic different missense change and a BLOSUM62 comparison.
  • Variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources
PP2 N/ANot applicable: PP2 is restricted to missense variants, while NM_000314.8:c.922_923insT is a frameshift. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP2 rule applies to missense variants in a gene with a low rate of benign missense variation where missense variants are a common disease mechanism. This variant is an exonic frameshift, not a missense variant, so it is outside the rule's stated scope.

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
  • ClinGen PTEN VCEP Version 3.2 CSPEC PP2 rule: requires a missense variant in a gene with low benign missense variation and missense disease mechanism.
  • Variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources
PP3 N/ANot applicable: the variant is an exonic frameshift, whereas PTEN PP3 covers synonymous or intronic variants and missense variants with REVEL >0.7. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PP3 to synonymous or intronic variants with concordant SpliceAl and VarSeak evidence of splicing impact, with a separate missense REVEL path. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), so it lies outside every PP3 applicability path. SpliceAI data are therefore not used for PP3.

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
  • ClinGen PTEN VCEP specification v3.2, PP3 instructions: PP3 applies to synonymous or intronic variants with splicing-impact predictions, or to missense variants with REVEL score >0.7.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources
PP4 VCEPNot applicable: the PTEN VCEP explicitly marks PP4 as not applicable and incorporates phenotype specificity into PS4. Details ▾Hide ▴
Reasoning

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

VCEP rule
Not applicable
Evidence considered
  • ClinGen PTEN VCEP specification v3.2 marks PP4 as not applicable and directs phenotype-specificity assessment to PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP explicitly states that PP5 is not for use. 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.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP specification v3.2 marks PP5 as not applicable for this VCEP.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly marks BP1 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP explicitly marks BP1 as not applicable. No BP1 evidence is therefore assigned regardless of the variant's consequence or available gene-level information.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN VCEP Version 3.2 CSPEC BP1 entry: applicability is "Not Applicable."
Sources
BP3 VCEPNot applicable: the PTEN VCEP explicitly states that BP3 is not applicable to PTEN. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP3 as not applicable to PTEN. The variant's frameshift consequence and premature termination are consequently not evaluated under BP3.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN VCEP BP3 entry: applicability is Not applicable and the instruction states, 'This rule is not applicable to PTEN.'
Sources
BP4 N/ANot applicable: the variant is an exonic frameshift, whereas PTEN BP4 covers synonymous or intronic variants and missense variants with REVEL <0.5. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4 to synonymous or intronic variants with concordant SpliceAl and VarSeak evidence of no splicing impact, with a separate missense REVEL path. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), so it lies outside every BP4 applicability path. The available SpliceAI score is consequently not evidence for BP4.

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
  • ClinGen PTEN VCEP specification v3.2, BP4 instructions: BP4 applies to synonymous or intronic variants with no-impact SpliceAl and VarSeak predictions, or to missense variants with REVEL score <0.5.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
  • SpliceAI result (not used for BP4 because the variant is outside scope): max delta score 0.014.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly states that BP6 is not for use. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks BP6 as not applicable for this VCEP 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
  • ClinGen PTEN VCEP specification v3.2 marks BP6 as not applicable for this VCEP.
Sources
BP7 N/ANot applicable: the variant is an exonic frameshift, whereas PTEN BP7 covers only synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule covers only synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), and is therefore outside BP7 scope; no splice-prediction result can make BP7 applicable.

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 specification v3.2, BP7 instructions: intronic variants must be positioned at or beyond +7/-21.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.922_923insT
Protein (HGVS p.)
NP_000305.3:p.(Arg308LeufsTer4)
GRCh38
chr10:87961014 C>CT
GRCh37
chr10:89720771 C>CT
Location and type
Exon 8 · 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 -77 bp
0.014
SpliceAI acceptor gainat +172 bp
0.000
SpliceAI donor lossat +104 bp
0.001
SpliceAI donor gainat +349 bp
0.003
Pangolin splice lossmagnitude shown
-0.103
Pangolin splice gain
0.004

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

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

The PTEN VCEP limits PP3 to synonymous or intronic variants with concordant SpliceAl and VarSeak evidence of splicing impact, with a separate missense REVEL path. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), so it lies outside every PP3 applicability path. SpliceAI data are therefore not used for PP3.

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
  • ClinGen PTEN VCEP specification v3.2, PP3 instructions: PP3 applies to synonymous or intronic variants with splicing-impact predictions, or to missense variants with REVEL score >0.7.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources
BP4 N/ANot applicable: the variant is an exonic frameshift, whereas PTEN BP4 covers synonymous or intronic variants and missense variants with REVEL <0.5. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4 to synonymous or intronic variants with concordant SpliceAl and VarSeak evidence of no splicing impact, with a separate missense REVEL path. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), so it lies outside every BP4 applicability path. The available SpliceAI score is consequently not evidence for BP4.

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
  • ClinGen PTEN VCEP specification v3.2, BP4 instructions: BP4 applies to synonymous or intronic variants with no-impact SpliceAl and VarSeak predictions, or to missense variants with REVEL score <0.5.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
  • SpliceAI result (not used for BP4 because the variant is outside scope): max delta score 0.014.
Sources
BP7 N/ANot applicable: the variant is an exonic frameshift, whereas PTEN BP7 covers only synonymous or intronic variants at or beyond +7/-21. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule covers only synonymous or intronic variants at or beyond +7/-21. NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted to cause p.(Arg308LeufsTer4), and is therefore outside BP7 scope; no splice-prediction result can make BP7 applicable.

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 specification v3.2, BP7 instructions: intronic variants must be positioned at or beyond +7/-21.
  • Case variant normalization: NM_000314.8:c.922_923insT is an exonic frameshift in exon 8, predicted as NP_000305.3:p.(Arg308LeufsTer4).
Sources

Statement

In silico

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

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.
    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 ↗

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.01).

Functional

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

Somatic

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