0%
Print report
Variant interpretation report

PTEN c.69_73del, p.Leu23PhefsTer19

NM_000314.8:c.69_73del NP_000305.3:p.(Leu23PhefsTer19) Frameshift · exon 1 View identifiers
Classification
Likely pathogenic

Variant description:

The PTEN NM_000314.8:c.69_73del (NP_000305.3:p.(Leu23PhefsTer19)) frameshift variant has previously been reported in somatic cancers (COSMIC; COSV105927904, n = 1 time), and lies in a statistically significant hotspot (cancerhotspots.org). This variant is predicted to result in an absent or disrupted protein product. Based on available guidelines, this variant is considered to be Likely Pathogenic.

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

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

In plain language

Gene-level background from the recorded interpretation.

About PTEN

PTEN is a tumor suppressor gene that encodes a phosphatase converting the lipid messenger PIP3 back to PIP2 at the cell membrane, thereby restraining the AKT/mTOR signaling pathway that drives cell growth, proliferation, and survival. It is one of the most frequently mutated genes across many types of human cancer, and its loss promotes unchecked cell growth, survival, and genomic instability, partly through impaired DNA repair. Germline loss-of-function variants in PTEN cause Cowden syndrome, an inherited cancer predisposition disorder associated with elevated risk of breast and thyroid cancer.

LYFE Sciences is an AI system, and it can make mistakes. Criteria may be applied incorrectly, sources may be misread, and a confident-looking classification can still be wrong. Double-check every criterion and its underlying evidence before relying on any call.
01The reasoning

How it was classified

The recorded framework is ClinGen PTEN VCEP v3.2. The criteria and strengths shown below come from the saved assessment; this page does not recalculate the classification.

Recorded applied criteria

The applied criteria and their strengths are shown as assessed under the stated framework.

Pathogenic evidence criteria: 2 Benign evidence criteria: 0
Pathogenic criteria applied · 2
PVS1Very strong
PVS1 · very strong

Met, very strong: the exon 1 frameshift at c.69_73del is 5' to the VCEP's c.1121 NMD threshold in NM_000314.8.

PM2Supporting
PM2 · supporting

Met, Supporting: the variant is absent from gnomAD v2.1 and v4.1, meeting the PTEN PM2 threshold 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.092 maximum delta

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

No listed criterion applied SpliceAI ↗
No screenshot for this evidence
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
1 recorded samples

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

Cancer Hotspots

This variant lies in a statistically significant hotspot.

For specialists

Technical detail

ACMG/AMP criteria under ClinGen PTEN VCEP v3.2, with the data and sources behind each one.

28 criteria with recorded statuses: 2 met · 4 not met · 7 not assessed · 15 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

Within the requested group, only PS4 and BP5 are applicable under the PTEN VCEP; available evidence is insufficient to assess either criterion.

PP4, PP5, and BP6 are explicitly not applicable under the PTEN VCEP v3.2 specification.

Population evidence supports PM2 at Supporting strength only; BA1, BS1, and BS2 are not met because the variant is absent rather than frequent or homozygous in the available default all-comers gnomAD records.

Met · 2

PVS1 Very strongVCEPMet, very strong: the exon 1 frameshift at c.69_73del is 5' to the VCEP's c.1121 NMD threshold in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.69_73del is a frameshift, p.(Leu23PhefsTer19), in exon 1. The PTEN decision tree assigns full PVS1 when a nonsense or frameshift variant is predicted to undergo NMD because the stop codon or disruption is at or 5' to p.D375 (c.1121) and the exon is present in biologically-relevant transcript NM_000314.8. This variant is far 5' of c.1121 and exon 1 is present in NM_000314.8, so the full, non-downgraded tier applies.

VCEP rule
Nonsense or frameshift | Predicted to undergo NMD: stop codon or disruption at or 5' to p.D375 (c.1121) -> exon is present in biologically-relevant transcript NM_000314.8 | PVS1
Evidence considered
  • PVS1_DecisionTree_PTEN.pdf.txt, page 1, nonsense or frameshift row: a variant predicted to undergo NMD with a stop codon or disruption at or 5' to p.D375 (c.1121), in an exon present in biologically-relevant transcript NM_000314.8, is assigned PVS1.
  • pvs1_variant_assessment: NM_000314.8:c.69_73del; NP_000305.3:p.(Leu23PhefsTer19), p.(L23Ffs*19); exon 1; consequence class frameshift.
  • The variant's c.69 position is 5' to the VCEP threshold c.1121, and exon 1 is present in the governing transcript NM_000314.8.
Still missing
  • No exact variant entry was found in PVS1_DecisionTree_PTEN.pdf.txt for c.69_73del, p.Leu23PhefsTer19, or p.L23Ffs*19; the governing decision-tree path was applied.
Sources
PM2 SupportingVCEPMet, Supporting: the variant is absent from gnomAD v2.1 and v4.1, meeting the PTEN PM2 threshold below 0.00001 (0.001%). Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specification permits PM2 at Supporting strength when the variant is absent or present at an allele frequency below 0.00001 (0.001%) 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 the default all-comers gnomAD v2.1 and gnomAD v4.1 records, satisfying the absence 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
  • The PTEN VCEP Version 3.2 PM2 rule requires absence or allele frequency <0.00001 (0.001%) in gnomAD; any subpopulation with multiple alleles must remain <0.00002 (0.002%).
  • The default all-comers gnomAD v2.1 record reports the variant absent.
  • The default all-comers gnomAD v4.1 record reports the variant absent.
Sources

Not met · 4 · evaluated, threshold not reached

PM1 VCEPNot met: residue 23 is outside all VCEP-approved catalytic motifs, which are limited to residues 90-94, 123-130, and 166-168. Details ▾Hide ▴
Reasoning

The variant affects residue 23. The PTEN VCEP defines PM1's critical functional regions as WPD loop residues 90-94, P-loop residues 123-130, and TI-loop residues 166-168; residue 23 is outside all three. Although the case evidence reports a Cancer Hotspots L23 hotspot, the PTEN VCEP's PM1 specification does not name Cancer Hotspots, COSMIC, or another somatic-hotspot route, so that observation cannot establish PM1 under this VCEP-only interpretation.

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
  • The PTEN VCEP defines the complete approved PM1 regions as WPD loop 90-94, P-loop/phosphatase core 123-130, and TI-loop 166-168 (NP_000305.3); the variant is p.(Leu23PhefsTer19), residue 23.
  • Cancer Hotspots evidence reports a statistically significant PTEN L23 hotspot, but the VCEP PM1 specification does not name Cancer Hotspots, COSMIC, or a somatic-hotspot route; therefore the hotspot observation is not an allowed PM1 route here.
Sources
BA1 VCEPNot met: gnomAD v2.1 and v4.1 report the variant absent, not a filtering allele frequency greater than 0.00056 (0.056%). Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specification requires BA1 for a gnomAD filtering allele frequency greater than 0.00056 (0.056%). The variant is absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 records, so no allele frequency meets or exceeds this stand-alone benign threshold.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • The PTEN VCEP Version 3.2 BA1 rule is gnomAD Filtering allele frequency >0.00056 (0.056%).
  • The default all-comers gnomAD v2.1 record reports the variant absent.
  • The default all-comers gnomAD v4.1 record reports the variant absent.
Sources
BS1 VCEPNot met: gnomAD v2.1 and v4.1 report absence, with no allele frequency in the PTEN BS1 range of 0.0000043 to 0.00056. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specification 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 the default all-comers gnomAD v2.1 and gnomAD v4.1 records, providing no frequency in either interval.

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
  • The PTEN VCEP Version 3.2 BS1 Strong rule is gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • The PTEN VCEP Version 3.2 BS1 Supporting rule is allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
  • The default all-comers gnomAD v2.1 record reports the variant absent.
  • The default all-comers gnomAD v4.1 record reports the variant absent.
Sources
BS2 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, with no reported homozygous healthy individual. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specification requires the variant to be observed in the homozygous state in a healthy or PHTS-unaffected individual; one observation is sufficient when homozygosity is confirmed, and two are required when it is unconfirmed. The variant is absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 records, so no homozygous observation is available.

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
  • The PTEN VCEP Version 3.2 BS2 Strong rule requires observation in the homozygous state in a healthy or PHTS-unaffected individual; one observation is sufficient if homozygous status is confirmed, and two if not confirmed.
  • The default all-comers gnomAD v2.1 record reports the variant absent.
  • The default all-comers gnomAD v4.1 record reports the variant absent.
Sources

Not assessed · 7 · no assessment recorded

PS2 VCEPNot assessed: no proband-level de novo observation with confirmed maternity and paternity and no family history is documented. Details ▾Hide ▴
Reasoning

No documented de novo observation is available for this variant: the available evidence contains no proband-level parental testing, confirmation of both maternity and paternity, or family-history assessment. The criterion therefore cannot be evaluated against the PTEN VCEP requirement.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • No proband-level parental testing, maternity/paternity confirmation, family-history assessment, or independent de novo observation is documented in the available case evidence.
Still missing
  • Affected proband phenotype and disease diagnosis
  • Parental testing confirming both maternity and paternity
  • Family-history assessment
  • Any additional independent de novo observations
Sources
PS4 VCEPNot assessed: no case-control counts, odds ratio, confidence interval, or PTEN phenotype-specificity scores are available to evaluate the VCEP PS4 rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from a sufficiently powered case-control study showing an odds ratio >2 for a PHTS component phenotype with p<0.05 and a 95% confidence-interval lower limit >1.5, or from summed phenotype-specificity scores across independent probands. The available case evidence contains no affected/control counts, allele frequencies for a matched control comparison, odds ratio, confidence interval, p-value, Cleveland Clinic scores, pediatric phenotype scores, or variant-specific proband phenotype observations. The literature_pass.json packet has an empty packet.ai_classified_papers list, so there are no pre-classified PS4 papers to verify. PS4 is therefore not assessed; the available population absence does not substitute for the VCEP's case-control or specificity evidence, and no PS4 decision is made in combination with PP4.

VCEP rule
This criterion may not be applied if BS1 applies.  Phenotype specificity scores are added across independent probands and calculated as follows: Adults:  * 1 point per proband with Cleveland Clinic (CC) score ≥ 30 (Tan 2011) * 0.5 points per proband with CC score of 25-29. Children: * 1 point per proband with pediatric phenotype score ≥ 5 (please see supplementary information in manuscript for scoring rubric). * 0.5 points per proband with pediatric phenotype score of 4, but autism/developmental delay/intellectual disability may not contribute to the score. PS4\_Very Strong: Probands with specificity score ≥16 (see text). PS4: Probands with specificity score of 4-15.5. PS4\_Moderate: Probands with specificity score of 2-3.5. PS4\_Supporting: Proband(s) with specificity score of 1-1.5 (see text).
Evidence considered
  • ClinGen PTEN VCEP v3.2 PS4 instructions: sufficiently powered case-control evidence requires odds ratio >2 for a PHTS component phenotype, p<0.05, and a 95% confidence-interval lower limit >1.5; the alternative is a summed phenotype-specificity score across independent probands.
  • The case evidence has no affected/control counts, matched control frequency, odds ratio, confidence interval, p-value, Cleveland Clinic score, pediatric phenotype score, or variant-specific proband phenotype observations.
  • literature_pass.json packet.ai_classified_papers is empty; consequently, no paper was pre-classified as PS4 and no variant-specific PS4 paper could be verified from that packet.
Still missing
  • Affected and control carrier counts or matched-ancestry control frequency for NM_000314.8:c.69_73del
  • Case-control p-value and 95% confidence interval, if a case-control study exists
  • Variant-specific independent-proband Cleveland Clinic scores or pediatric phenotype scores
Sources
PM6 VCEPNot assessed: no affected proband with an assumed or presumed de novo occurrence and documented family-history or parental-confirmation status is available. Details ▾Hide ▴
Reasoning

No assumed or presumed de novo observation is documented for this variant. The available evidence does not establish an affected proband, absence of family history, or whether maternity and paternity were unconfirmed, so none of the VCEP PM6 strength thresholds can 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
  • No assumed or presumed de novo observation, affected proband record, parental-confirmation status, or family-history assessment is documented in the available case evidence.
Still missing
  • Affected proband phenotype and disease diagnosis
  • Evidence that the variant is de novo or presumed de novo
  • Maternity and paternity confirmation status
  • Family-history assessment
  • Additional qualifying de novo observations
Sources
PP1 VCEPNot assessed: zero documented family meioses are available to evaluate the VCEP thresholds of 3–4, 5–6, or at least 7 meioses. Details ▾Hide ▴
Reasoning

No affected relatives, genotype-phenotype observations, family pedigrees, or meioses are documented for this variant. The VCEP PP1 thresholds of 3 or 4, 5 or 6, or at least 7 meioses across at least two families therefore cannot be evaluated.

VCEP rule
Co-segregation with disease in multiple affected family members, with 3 or 4 meioses observed.
Evidence considered
  • No affected family members, informative relatives, pedigrees, segregation results, or meiosis count is documented in the available case evidence.
Still missing
  • Affected family members with phenotype information
  • Variant genotypes in informative relatives
  • Family pedigrees and phase information
  • Count of informative meioses and number of families
Sources
BS4 VCEPNot assessed: no affected-family segregation results are documented for the one-family or two-family VCEP BS4 thresholds. Details ▾Hide ▴
Reasoning

No affected relatives or family-level segregation results are documented, so there is no evidence of lack of segregation in either one family or two or more families. The VCEP BS4 rule cannot be evaluated.

VCEP rule
Lack of segregation in affected members of one family.
Evidence considered
  • No affected-family genotypes, phenotype data, pedigrees, or documented non-segregation result is available in the case evidence.
Still missing
  • Affected family members and their variant genotypes
  • Family-level phenotype information
  • Documented non-segregation in at least one family
  • Number of families with qualifying non-segregation
Sources
BP2 VCEPNot assessed: no documented trans observation or at least three cis/unknown-phase observations with different pathogenic or likely pathogenic PTEN variants. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP2 rule requires either observation of the 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 documents no qualifying trans observation, cis observation, phase-unknown observation, accompanying PTEN variant, or affected-proband allelic observation; BP2 cannot be assessed.

VCEP rule
Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
  • ClinGen PTEN 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."
  • The consolidated case evidence contains no documented qualifying co-occurring PTEN variant, phase result, or affected-proband allelic observation for NM_000314.8:c.69_73del.
Still missing
  • A documented co-occurring pathogenic or likely pathogenic PTEN variant.
  • Confirmed trans phase, or at least three distinct cis and/or phase-unknown observations with different pathogenic or likely pathogenic PTEN variants.
  • Affected-proband and inheritance details for each qualifying observation.
Sources
BP5 VCEPNot assessed: no two qualifying cases with a highly penetrant alternate diagnosis and non-overlapping PTEN personal or family history are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits BP5 at supporting strength only when the variant is found in a case with an alternate molecular basis for disease, the other gene/disorder is highly penetrant, and the patient's personal or family history demonstrates no overlap between that disorder and PTEN. The available case evidence contains no qualifying alternate-gene diagnosis, no two qualifying cases, and no personal/family-history documentation establishing the required absence of phenotype overlap. BP5 is therefore not assessed.

VCEP rule
Variant found in a case with an alternate molecular basis for disease. Other gene/disorder must be considered highly penetrant AND patient’s personal/family history must demonstrate no overlap between other gene and PTEN.
Evidence considered
  • ClinGen PTEN VCEP v3.2 BP5 instructions require at least two such cases and additionally require a highly penetrant alternate gene/disorder with personal and family history demonstrating no overlap between the other gene and PTEN.
  • No qualifying alternate molecular diagnosis, qualifying case series, penetrance documentation, or non-overlapping personal/family history is present in the available case evidence.
Still missing
  • At least two cases carrying the variant with an alternate molecular diagnosis
  • Evidence that the alternate gene/disorder is highly penetrant
  • Personal and family histories showing no overlap between the alternate disorder and PTEN
Sources
Not applicable · 15· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: c.69_73del is a frameshift producing p.(Leu23PhefsTer19), not a same-amino-acid missense or intronic splice-site substitution. Details ▾Hide ▴
Reasoning

The queried variant is NM_000314.8:c.69_73del, a frameshift producing p.(Leu23PhefsTer19), not a same-amino-acid missense change or an intronic splice-site substitution. Therefore the PTEN VCEP PS1 rule does not apply.

VCEP rule
Same amino acid change as a previously established pathogenic variant regardless of nucleotide change OR different variant at same nucleotide position as a pathogenic splicing variant, where in silico models predict impact equal to or greater than the known pathogenic variant.
Evidence considered
  • Case variant consequence: NM_000314.8:c.69_73del; NP_000305.3:p.(Leu23PhefsTer19), frameshift.
  • The PTEN VCEP PS1 rule addresses the same amino-acid change as a pathogenic variant or a different nucleotide at a pathogenic splice site; neither route matches this frameshift.
Sources
PS3 N/ANot applicable: the governing mmc2 assay file covers missense variants, while this variant is a frameshift and has no exact functional-assay entry. Details ▾Hide ▴
Reasoning

The variant is a frameshift, NM_000314.8:c.69_73del, producing p.(Leu23PhefsTer19), whereas the governing PTEN index assigns mmc2.xlsx to missense variants. The file was searched under c.69_73del, p.Leu23PhefsTer19, and p.L23Ffs*19; no exact frameshift entry was found. Table S2 contains the distinct missense variant L23F with Cum_score -1.175036609 and High_conf False, which cannot be transferred to this frameshift. Therefore the Mighell phosphatase assay rule does not apply to this variant.

VCEP rule
PS3 may be applied to the following assays: ... In the supplementary material (Table S2) search for the variant in columns A or B and make sure the variant in question is listed as TRUE under column I (high confidence). If not, do not use as evidence.
Evidence considered
  • Variant normalization: NM_000314.8:c.69_73del is a frameshift producing NP_000305.3:p.(Leu23PhefsTer19), also p.(L23Ffs*19).
  • ClinGen PTEN VCEP Version 3.2 PS3 specification: the Mighell et al. 2018 assay is evaluated by searching Table S2 columns A or B, requiring High_conf TRUE, and applying PS3_Moderate for cumulative scores <= -1.11.
  • PTEN local VCEP index: mmc2.xlsx is declared for PS3 and BS3 with types 'missense'.
  • Mighell et al. 2018 supplementary Table S2, row L23F/Leu23Phe: Cum_score -1.175036609, High_conf False, Imputed_Score -1.522827148; this is a missense comparator and not the assessed frameshift.
Still missing
  • No exact c.69_73del, p.Leu23PhefsTer19, or p.L23Ffs*19 entry was found in the governing file mmc2.xlsx; its L23F row is a distinct missense variant.
Sources
PM3 VCEPNot applicable: the PTEN VCEP explicitly designates PM3 as not applicable to PTEN. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification explicitly states that PM3 is not applicable to PTEN. Therefore, no recessive-phase or affected-proband assessment is performed for this criterion.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN Expert Panel specification v3.2: PM3 instructions state, "This rule is not applicable to PTEN."
Sources
PM4 N/ANot applicable: PM4 is limited to in-frame indels or stop-loss/protein-extension changes, whereas c.69_73del is a frameshift. Details ▾Hide ▴
Reasoning

The PTEN VCEP defines PM4 for protein length changes due to in-frame deletions or insertions in a non-repeat region or for stop-loss variants, including in-frame changes affecting a catalytic motif and protein extensions. This variant is a frameshift that creates a premature termination signal, not an in-frame indel or stop-loss variant, so PM4 is outside the rule's named variant types.

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
  • CSPEC PM4 entry: the rule names in-frame deletions/insertions in a non-repeat region and stop-loss variants, including catalytic-motif in-frame changes and protein extensions.
  • pvs1_variant_assessment classifies NM_000314.8:c.69_73del as a frameshift producing p.(Leu23PhefsTer19).
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: PM5 requires a missense change with a BLOSUM62 comparison, whereas this variant is a frameshift at c.69_73del. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule requires the assessed variant to be a missense change at an amino-acid residue and to have a BLOSUM62 score no greater than the known pathogenic or likely pathogenic missense change. This variant is a frameshift, so PM5 is not applicable.

VCEP rule
Missense change at an amino acid residue where a different missense change determined to be pathogenic or likely pathogenic has been seen before. In addition, variant being interrogated must have BLOSUM62 score equal to or less than the known variant.
Evidence considered
  • Case variant consequence: NM_000314.8:c.69_73del; NP_000305.3:p.(Leu23PhefsTer19), frameshift.
  • The collected PM5 candidate summary contains no same-residue candidates and identifies the variant as ineligible for the classic same-residue missense PM5 search; the VCEP rule itself requires a missense change and BLOSUM62 comparison.
Sources
cspec ↗pm5_candidates
PP2 N/ANot applicable: PP2 is restricted to missense variants, while c.69_73del causes the frameshift p.(Leu23PhefsTer19). Details ▾Hide ▴
Reasoning

The PTEN VCEP PP2 rule is explicitly for a missense variant in a gene with a low rate of benign missense variation and a common missense disease mechanism. The queried variant is a frameshift, so PP2 is not applicable.

VCEP rule
Missense variant in a gene that has a low rate of benign missense variation and where missense variants are a common mechanism of disease.
Evidence considered
  • Case variant consequence: NM_000314.8:c.69_73del; NP_000305.3:p.(Leu23PhefsTer19), frameshift.
  • The PTEN VCEP PP2 rule explicitly begins with 'Missense variant'; no missense-specific gene-mechanism assessment can be applied to this frameshift.
Sources
PP3 N/ANot applicable: PP3 names splicing or missense variants, whereas NM_000314.8:c.69_73del is a frameshift variant. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PP3's named computational paths to splicing variants assessed by concordant SpliceAl and VarSeak predictions or missense variants with REVEL score > 0.7. NM_000314.8:c.69_73del is a frameshift variant, not a synonymous/intronic splicing variant or a missense variant; therefore PP3 is outside its governing scope and is not_applicable. The available SpliceAI score is not used because the VCEP does not name it as a qualifying PP3 predictor for this frameshift situation.

VCEP rule
Multiple lines of computational evidence support a deleterious effect on the gene or gene product. * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL score > 0.7
Evidence considered
  • Variant consequence: frameshift, NP_000305.3:p.(Leu23PhefsTer19).
  • The VCEP PP3 rule names concordant SpliceAl and VarSeak for splicing variants and REVEL score > 0.7 for missense variants; none of those named applicability paths covers this frameshift variant.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 Use 2 and explicitly excludes independent PP4 application. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks PP4 as not applicable and states that phenotype specificity is incorporated into PS4 Use 2. PP4 cannot be applied independently under this governing specification.

VCEP rule
PTEN EP Commentary: Phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Evidence considered
  • ClinGen PTEN VCEP v3.2 PP4 entry: applicability is Not applicable; its commentary states that phenotype specificity has been incorporated into 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 as not applicable and states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. No PP5 evidence is evaluated.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP v3.2 PP5 entry: applicability is Not Applicable for this VCEP and the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BS3 N/ANot applicable: the governing mmc2 assay file covers missense variants, while this variant is a frameshift and has no exact functional-assay entry. Details ▾Hide ▴
Reasoning

The variant is a frameshift, NM_000314.8:c.69_73del, producing p.(Leu23PhefsTer19), whereas the governing PTEN index assigns mmc2.xlsx to missense variants. The file was searched under c.69_73del, p.Leu23PhefsTer19, and p.L23Ffs*19; no exact frameshift entry was found. Table S2 contains the distinct missense variant L23F with Cum_score -1.175036609 and High_conf False, which cannot be transferred to this frameshift. Therefore the Mighell phosphatase assay rule does not apply to this variant.

VCEP rule
In the supplementary material (Table S2) search for the variant in columns A or B and make sure the variant in question is listed as TRUE under column I (high confidence). If not, do not use as evidence.
Evidence considered
  • Variant normalization: NM_000314.8:c.69_73del is a frameshift producing NP_000305.3:p.(Leu23PhefsTer19), also p.(L23Ffs*19).
  • ClinGen PTEN VCEP Version 3.2 BS3 specification: BS3_supporting may use the Mighell et al. 2018 phosphatase assay only after locating the variant in Table S2 columns A or B, confirming High_conf TRUE, and applying the >0 cumulative-score rule.
  • PTEN local VCEP index: mmc2.xlsx is declared for PS3 and BS3 with types 'missense'.
  • Mighell et al. 2018 supplementary Table S2, row L23F/Leu23Phe: Cum_score -1.175036609, High_conf False, Imputed_Score -1.522827148; this is a missense comparator and not the assessed frameshift.
Still missing
  • No exact c.69_73del, p.Leu23PhefsTer19, or p.L23Ffs*19 entry was found in the governing file mmc2.xlsx; its L23F row is a distinct missense variant.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly states that BP1 is not applicable to PTEN. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP1 as not applicable to PTEN, independently of this variant's frameshift consequence.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • The PTEN VCEP applicability entry states: 'This rule is not applicable to PTEN.'
Sources
BP3 VCEPNot applicable: the PTEN VCEP CSPEC explicitly marks BP3 as Not Applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP CSPEC entry marks BP3 as Not Applicable. Therefore BP3 cannot be applied to this variant regardless of its frameshift or protein consequence.

VCEP rule
Not Applicable
Evidence considered
  • CSPEC BP3 entry: applicability is explicitly listed as Not Applicable.
Sources
BP4 N/ANot applicable: BP4 is limited to splicing or missense variants, while this variant is a frameshift despite a SpliceAI max delta of 0.092. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4's named computational paths to splicing variants assessed by concordant SpliceAl and VarSeak predictions or missense variants with REVEL scores < 0.5. NM_000314.8:c.69_73del is a frameshift variant, so a no-splice-impact prediction cannot establish no impact on the gene product and BP4 is not_applicable. The available SpliceAI max delta score of 0.092 is therefore not used for BP4.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores \< 0.5
Evidence considered
  • Variant consequence: frameshift, NP_000305.3:p.(Leu23PhefsTer19).
  • SpliceAI reported max delta score 0.092, but the PTEN VCEP BP4 rule does not make a no-splice-impact result applicable to a frameshift variant.
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 as not applicable and states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. No BP6 evidence is evaluated.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP v3.2 BP6 entry: applicability is Not Applicable for this VCEP and the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP7 N/ANot applicable: BP7 requires a synonymous or intronic variant at or beyond +7/-21, but this variant is an exon 1 frameshift. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous (silent) or intronic variants at or beyond +7/-21 with no predicted splice-consensus impact or new splice creation. NM_000314.8:c.69_73del is a coding frameshift variant in exon 1, not a synonymous or intronic variant; BP7 is therefore outside its governing scope and is not_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
  • Variant consequence and location: exon 1 coding frameshift, NM_000314.8:c.69_73del, NP_000305.3:p.(Leu23PhefsTer19).
  • The VCEP BP7 applicability condition is restricted to synonymous or intronic variants at or beyond +7/-21.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.69_73del
Protein (HGVS p.)
NP_000305.3:p.(Leu23PhefsTer19)
GRCh38
chr10:87864536 TTAGAC>T
GRCh37
chr10:89624293 TTAGAC>T
Location and type
Exon 1 · frameshift
COSMIC
COSV105927904

Gene diagram

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

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

Statements

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -82 bp
0.083
SpliceAI acceptor gainat -267 bp
0.000
SpliceAI donor lossat +88 bp
0.008
SpliceAI donor gainat +12 bp
0.092
Pangolin splice lossmagnitude shown
-0.054
Pangolin splice gain
0.081

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: PP3 names splicing or missense variants, whereas NM_000314.8:c.69_73del is a frameshift variant. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits PP3's named computational paths to splicing variants assessed by concordant SpliceAl and VarSeak predictions or missense variants with REVEL score > 0.7. NM_000314.8:c.69_73del is a frameshift variant, not a synonymous/intronic splicing variant or a missense variant; therefore PP3 is outside its governing scope and is not_applicable. The available SpliceAI score is not used because the VCEP does not name it as a qualifying PP3 predictor for this frameshift situation.

VCEP rule
Multiple lines of computational evidence support a deleterious effect on the gene or gene product. * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL score > 0.7
Evidence considered
  • Variant consequence: frameshift, NP_000305.3:p.(Leu23PhefsTer19).
  • The VCEP PP3 rule names concordant SpliceAl and VarSeak for splicing variants and REVEL score > 0.7 for missense variants; none of those named applicability paths covers this frameshift variant.
Sources
BP4 N/ANot applicable: BP4 is limited to splicing or missense variants, while this variant is a frameshift despite a SpliceAI max delta of 0.092. Details ▾Hide ▴
Reasoning

The PTEN VCEP limits BP4's named computational paths to splicing variants assessed by concordant SpliceAl and VarSeak predictions or missense variants with REVEL scores < 0.5. NM_000314.8:c.69_73del is a frameshift variant, so a no-splice-impact prediction cannot establish no impact on the gene product and BP4 is not_applicable. The available SpliceAI max delta score of 0.092 is therefore not used for BP4.

VCEP rule
Multiple lines of computational evidence suggest no impact on gene or gene product.  * Splicing variants: Concordance of SpliceAl and VarSeak * Missense variants: REVEL scores \< 0.5
Evidence considered
  • Variant consequence: frameshift, NP_000305.3:p.(Leu23PhefsTer19).
  • SpliceAI reported max delta score 0.092, but the PTEN VCEP BP4 rule does not make a no-splice-impact result applicable to a frameshift variant.
Sources
BP7 N/ANot applicable: BP7 requires a synonymous or intronic variant at or beyond +7/-21, but this variant is an exon 1 frameshift. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous (silent) or intronic variants at or beyond +7/-21 with no predicted splice-consensus impact or new splice creation. NM_000314.8:c.69_73del is a coding frameshift variant in exon 1, not a synonymous or intronic variant; BP7 is therefore outside its governing scope and is not_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
  • Variant consequence and location: exon 1 coding frameshift, NM_000314.8:c.69_73del, NP_000305.3:p.(Leu23PhefsTer19).
  • The VCEP BP7 applicability condition is restricted to synonymous or intronic variants at or beyond +7/-21.
Sources

Statement

In silico

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

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

Not available in 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.09).

Functional

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

Somatic

This variant lies in a statistically significant hotspot. This variant has previously been reported in somatic cancers (COSMIC; COSV105927904, n = 1 times).

Cancer Hotspots

This variant lies in a statistically significant hotspot.