0%
Print report
Variant interpretation report

PTEN c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro

NM_000314.8:c.764_776delinsCAGAGTACCC NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro) In frame indel unknown · exon 7 View identifiers
Classification
Uncertain significance

Variant description:

The PTEN NM_000314.8:c.764_776delinsCAGAGTACCC (NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro)) in-frame deletion-insertion variant has not previously been reported in somatic cancers (COSMIC). Based on available guidelines, this variant is considered to be a Variant of Uncertain Significance (VUS).

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

Uncertain.The recorded classification is uncertain significance.

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: 1 Benign evidence criteria: 0
Pathogenic criteria applied · 1
PM2Supporting
PM2 · supporting

Met at supporting strength: the variant is 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: Uncertain significance

VUS: PM2 (supporting) was met, but no pathogenic or benign combination rule was satisfied under the PTEN Expert Panel framework.

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

Recorded SpliceAI maximum delta score: 0.012. 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 did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. PTEN, a lipid and protein phosphatase, is one of the most frequently mutated genes in cancer.

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: 1 met · 4 not met · 11 not assessed · 12 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 group, PS4 and BP5 remain not assessed because the required variant-specific phenotype or alternate-diagnosis evidence is absent; PP4, PP5, and BP6 are not applicable under the PTEN VCEP specification.

Met · 1

PM2 SupportingVCEPMet at supporting strength: the variant is 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 permits PM2 at supporting strength when a variant is absent from population databases or has 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 reported absent from gnomAD v2.1 and v4.1, and no subpopulation allele is reported.

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 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 (GRCh37) reports the variant absent.
  • gnomAD v4.1 (GRCh38) reports the variant absent.
Sources

Not met · 4 · evaluated, threshold not reached

PM1 VCEPNot met: residues 255-259 lie outside all VCEP-approved catalytic motifs 90-94, 123-130, and 166-168, with no reported hotspot. Details ▾Hide ▴
Reasoning

The PTEN VCEP defines PM1 to include residues in catalytic motifs 90-94, 123-130, and 166-168 of NP_000305.3. The altered interval spans residues 255-259, outside every specified catalytic motif; the authoritative domain_tables entry for PTEN is empty, and the collected Cancer Hotspots query found no hotspot row. Therefore the VCEP PM1 requirement is not met.

VCEP rule
Located in a mutational hot spot and/or critical and well-established functional domain. Defined to include residues in catalytic motifs: 90-94, 123-130, 166-168 (NP_ 000305.3)
Evidence considered
  • PTEN VCEP PM1 domain definition: catalytic motifs at residues 90-94, 123-130, and 166-168 on NP_000305.3.
  • The normalized protein consequence is p.(Val255_His259delinsAlaGluTyrPro), so the altered interval is 255-259 and does not overlap any listed motif.
  • Cancer Hotspots query for PTEN V255 returned no result; the VCEP text does not provide a separate hotspot route that overrides its defined motif regions.
Sources
PM4 VCEPNot met: residues 255-259 are altered, but the PTEN VCEP PM4 gate requires an in-frame indel to affect catalytic motifs 90-94, 123-130, or 166-168. Details ▾Hide ▴
Reasoning

The variant is an in-frame deletion-insertion replacing residues Val255 through His259 with Ala-Glu-Tyr-Pro, so it produces a protein length change. However, the PTEN VCEP restricts PM4 for in-frame insertions or deletions to variants impacting at least one residue in a catalytic motif; the VCEP PM1 motifs are residues 90-94, 123-130, and 166-168. The affected residues 255-259 do not overlap any specified catalytic motif, and the variant does not cause a protein extension. Therefore, PM4 is not met.

VCEP rule
For in-frame insertions or deletions, criteria may apply only if the variant impacts at least one residue in one of the catalytic motifs specified in the PM1 criteria. Criteria will also apply for variants resulting in protein extension. ... 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: in-frame insertions or deletions may apply only when at least one residue in a PM1 catalytic motif is impacted; protein extension is also eligible.
  • PTEN VCEP PM1 catalytic motifs: residues 90-94, 123-130, and 166-168 in NP_000305.3.
  • Variant normalization: NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro), an in-frame replacement affecting residues 255-259; no protein extension.
Sources
cspec ↗pvs1_variant_assessment
BA1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, rather than exceeding the VCEP's 0.00056 (0.056%) threshold. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires BA1 for a gnomAD filtering allele frequency above 0.00056 (0.056%). The variant is reported absent from gnomAD v2.1 and gnomAD v4.1, so no filtering allele frequency above this threshold is present.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP BA1 rule: gnomAD filtering allele frequency >0.00056 (0.056%).
  • gnomAD v2.1 (GRCh37) reports the variant absent; no allele frequency or homozygote count is reported.
  • gnomAD v4.1 (GRCh38) reports the variant absent; no allele frequency or homozygote count is reported.
Sources
BS1 VCEPNot met: no gnomAD allele frequency is observed, whereas BS1 Strong requires 0.000043-0.00056 (0.0043%-0.056%). Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires BS1 Strong for a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%). The variant is absent from gnomAD v2.1 and gnomAD v4.1, with no observed allele frequency in that interval.

VCEP rule
gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%)
Evidence considered
  • ClinGen PTEN VCEP BS1 Strong rule: gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • gnomAD v2.1 (GRCh37) reports the variant absent; no allele frequency is reported.
  • gnomAD v4.1 (GRCh38) reports the variant absent; no allele frequency is reported.
Sources

Not assessed · 11 · no assessment recorded

PS1 VCEPNot assessed: no qualifying pathogenic comparator was identified for the complex p.(Val255_His259delinsAlaGluTyrPro) change. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires the same amino acid change as a previously established pathogenic variant, or a different variant at the same nucleotide position as a pathogenic splicing variant with at least equivalent predicted impact. The case contains no qualifying pathogenic comparator for the complex in-frame protein change p.(Val255_His259delinsAlaGluTyrPro), so PS1 cannot be evaluated from the available evidence.

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
  • PTEN VCEP PS1 rule: same amino acid change as a previously established pathogenic variant, or a different variant at the same nucleotide position as a pathogenic splicing variant with equal or greater predicted impact.
  • Normalized consequence: NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro); the collected PM5 comparator search found 0 candidates and 0 same-residue candidates.
Still missing
  • A documented previously established pathogenic variant with the same amino acid change, or a qualifying pathogenic splicing comparator at the same nucleotide position, is unavailable.
Sources
cspec ↗pm5_candidates
PS2 VCEPNot assessed: no proband disease status, family-history information, or confirmed maternity and paternity is documented for the required de novo observation. Details ▾Hide ▴
Reasoning

The available case evidence contains no proband phenotype or disease-status documentation, no family-history statement, and no parental testing or maternity/paternity confirmation. Therefore, the VCEP requirement for a de novo observation in a patient with disease and no family history cannot be evaluated.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • The reviewed case bundle contains no proband phenotype or disease-status record, family-history assessment, parental genotype results, or maternity/paternity confirmation relevant to PS2.
Still missing
  • Proband phenotype and disease-status documentation
  • Family-history assessment
  • Parental genotype testing with confirmed maternity and paternity
Sources
PS3 VCEPNot assessed: mmc2.xlsx contains no exact row for the in-frame delins, so no VCEP-qualified phosphatase activity or high-confidence cumulative score is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS3_Moderate from Mighell et al. 2018 Table S2 only when the exact variant is listed with high confidence and has phosphatase activity (cumulative score) ≤ -1.11. The governing mmc2.xlsx full-text conversion was searched for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, and p.V255_H259delinsAEYP; no exact entry was found. The table contains distinct single-residue substitutions and a Val255 deletion, but neither is the assessed in-frame delins and neither can establish PS3 for this variant. No other qualifying functional result for this variant is available in the supplied evidence.

VCEP rule
Well-established _in vitro_ or _in vivo_ functional studies supportive of a damaging effect on the gene or gene product. * Phosphatase activity ≤ -1.11 per Mighell et al. 2018, PMID: 29706350.
Evidence considered
  • ClinGen PTEN VCEP specification v3.2, PS3: PS3_Moderate requires the Mighell et al. 2018 Table S2 variant row to be TRUE under High_conf and applies when the cumulative phosphatase score is ≤ -1.11.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, Table S2: exact searches for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, and p.V255_H259delinsAEYP returned no row; distinct Val255 single-residue substitutions and Val255Del are not the assessed variant and were not substituted for it.
  • The supplied case evidence contains no variant-specific functional assay result that meets another PS3 path.
Still missing
  • No exact entry for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, or p.V255_H259delinsAEYP was found in mmc2.xlsx full-text conversion; therefore the required high-confidence cumulative score is unavailable.
  • No variant-specific RNA, mini-gene, or other qualifying functional assay result is available in the supplied evidence.
Sources
PS4 VCEPNot assessed: no affected/control counts, odds ratio, confidence interval, or PTEN phenotype-specific proband scores are available to evaluate PS4. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits PS4 from a sufficiently powered case-control study only when the odds ratio is >2, p<0.05, and the 95% confidence interval lower limit is >1.5; it also permits phenotype-specific evidence from independent proband specificity scores. The case contains no reported affected/control counts, odds ratio, confidence interval, p-value, proband Cleveland Clinic scores, pediatric phenotype scores, or variant-bearing probands. gnomAD absence alone does not establish the VCEP's case-control requirement, and no papers were present in literature_pass.json packet.ai_classified_papers for verification. Therefore PS4 cannot be evaluated.

VCEP rule
This criterion is unlikely to be used in this manner for a condition as rare as PHTS. However, if sufficiently powered, a case-control study finding an odds ratio >2 for a PHTS component phenotype with p<0.05 and 95% confidence interval with lower limit >1.5, this criteria may be applied. However, this criterion may not be applied in combination with PP4. ... PS4: Probands with specificity score of 4-15.5. ... PS4_Moderate: Probands with specificity score of 2-3.5. ... PS4_Supporting: Proband(s) with specificity score of 1-1.5.
Evidence considered
  • ClinGen PTEN VCEP specification v3.2 PS4 instructions: a sufficiently powered case-control study requires odds ratio >2, p<0.05, and a 95% confidence-interval lower limit >1.5; phenotype-specific use requires independent proband specificity scores.
  • The case evidence reports the variant absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada, but provides no affected/control carrier counts or case-control estimate.
  • literature_pass.json reports total_pmids=0 and no criterion-screened papers; therefore there are no packet.ai_classified_papers PS4 papers to verify.
Still missing
  • Affected and control carrier counts or frequencies from a sufficiently powered study
  • Odds ratio, p-value, and 95% confidence interval, or data sufficient to calculate them
  • Independent proband Cleveland Clinic scores or pediatric phenotype scores
  • Variant-specific literature evidence
Sources
PM6 VCEPNot assessed: no assumed de novo observation, proband disease status, or no-family-history documentation is available for PM6 evaluation. Details ▾Hide ▴
Reasoning

The available case evidence contains no assumed de novo observation, proband phenotype or disease-status documentation, family-history statement, or parental testing information. The VCEP PM6 rule therefore cannot be evaluated.

VCEP rule
Assumed _de novo,_ but without confirmation of paternity and maternity, in proband with the disease and no family history.
Evidence considered
  • The reviewed case bundle contains no proband phenotype or disease-status record, family-history assessment, parental genotype results, or reported de novo observation relevant to PM6.
Still missing
  • Evidence that the variant is de novo or presumed de novo
  • Proband phenotype and disease-status documentation
  • Family-history assessment
  • Parental testing or documentation that maternity and paternity are unconfirmed
Sources
PP1 VCEPNot assessed: zero affected-family-member segregation observations and zero documented meioses are available to compare with the VCEP thresholds. Details ▾Hide ▴
Reasoning

The available case evidence provides no affected relatives, variant-positive family members, segregation observations, or meioses. Consequently, none of the VCEP PP1 thresholds of 3–4, 5–6, or at least 7 observed meioses can be evaluated.

VCEP rule
Co-segregation with disease in multiple affected family members, with ≥7 meioses observed across at least two families. ... Co-segregation with disease in multiple affected family members, with 5 or 6 meioses observed. ... Co-segregation with disease in multiple affected family members, with 3 or 4 meioses observed.
Evidence considered
  • The reviewed case bundle contains no affected relatives, family-member genotypes, co-segregation observations, meiosis count, or family-specific segregation data relevant to PP1.
Still missing
  • Affected relatives and their clinical phenotypes
  • Family-member genotypes
  • Documented informative meioses and family count
Sources
BS2 VCEPNot assessed: gnomAD reports absence and provides no homozygous observation or parental-confirmation data required by the VCEP. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires observation of the variant in the homozygous state in a healthy or PHTS-unaffected individual, with one observation if homozygous status is confirmed and two if it is not confirmed. The available gnomAD records report the variant as absent and provide no homozygous observations or parental-confirmation data, so BS2 cannot be evaluated.

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 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.
  • gnomAD v2.1 and gnomAD v4.1 both report the variant absent and provide no homozygote observations or parental-confirmation data.
Still missing
  • A confirmed homozygous observation in a healthy or PHTS-unaffected individual, or two unconfirmed homozygous observations, is unavailable.
Sources
BS3 VCEPNot assessed: mmc2.xlsx contains no exact row for the in-frame delins, so no VCEP-qualified phosphatase activity above zero or high-confidence benign assay result is available. Details ▾Hide ▴
Reasoning

The PTEN VCEP permits BS3_Supporting from Mighell et al. 2018 Table S2 only when the exact variant is listed with high confidence and has phosphatase activity (cumulative score) > 0. The governing mmc2.xlsx full-text conversion was searched for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, and p.V255_H259delinsAEYP; no exact entry was found. The table contains distinct single-residue substitutions and a Val255 deletion, but neither is the assessed in-frame delins and neither can establish BS3 for this variant. No other qualifying benign functional result for this variant is available in the supplied evidence.

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 specification v3.2, BS3_Supporting: BS3_Supporting requires the Mighell et al. 2018 Table S2 variant row to be TRUE under High_conf and applies when the cumulative phosphatase score is > 0.
  • Mighell et al. 2018 supplementary file mmc2.xlsx, Table S2: exact searches for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, and p.V255_H259delinsAEYP returned no row; distinct Val255 single-residue substitutions and Val255Del are not the assessed variant and were not substituted for it.
  • The supplied case evidence contains no variant-specific functional study demonstrating no damaging effect on protein function.
Still missing
  • No exact entry for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, or p.V255_H259delinsAEYP was found in mmc2.xlsx full-text conversion; therefore the required high-confidence cumulative score is unavailable.
  • No variant-specific functional study demonstrating no damaging effect on protein function is available in the supplied evidence.
Sources
BS4 VCEPNot assessed: no affected family member with genotype and phenotype data is documented, so lack of segregation in one or more families cannot be determined. Details ▾Hide ▴
Reasoning

The available case evidence provides no affected family members with genotype and phenotype data, and therefore no documented lack of segregation in one or more families. The VCEP BS4 rule cannot be evaluated.

VCEP rule
Lack of segregation in affected members of two or more families. ... Lack of segregation in affected members of one family.
Evidence considered
  • The reviewed case bundle contains no family segregation table, affected-relative genotypes, affected-relative phenotypes, or non-segregation observations relevant to BS4.
Still missing
  • Affected family members and their phenotypes
  • Variant genotypes for affected family members
  • Family-specific non-segregation assessment
Sources
BP2 VCEPNot assessed: zero affected-proband or cis/trans observations with a different pathogenic or likely pathogenic PTEN variant are available. Details ▾Hide ▴
Reasoning

The governing 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 materials contain no affected-proband, family, phase, cis/trans, or co-occurring pathogenic/likely pathogenic PTEN-variant observations for this variant; ClinVar returned no record and the literature packet contained zero PMIDs. Therefore, BP2 cannot be assessed, rather than being considered absent.

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 Specifications Version 3.2 BP2 rule: "Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants."
  • ClinVar query for NM_000314.8:c.764_776delinsCAGAGTACCC returned no record; consequently, no ClinVar phase or co-occurring PTEN-variant observation is available.
  • The case literature packet contains zero PMIDs, and no affected-proband, family, cis/trans, or phase-unknown co-occurring PTEN-variant observation is provided.
Still missing
  • Affected-proband or family-level observations pairing this variant with a different pathogenic or likely pathogenic PTEN variant.
  • Documented cis/trans or phase-unknown relationships and the pathogenic or likely pathogenic status of the other PTEN variant(s).
Sources
BP5 VCEPNot assessed: no two cases with an alternate highly penetrant molecular diagnosis and non-overlapping PTEN histories are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP requires at least two cases in which the variant is found with an alternate molecular basis for disease; the other gene/disorder must be highly penetrant and the patient's personal or family history must show no overlap between that disorder and PTEN. The available case evidence contains no such cases, alternate-gene findings, penetrance assessment, or non-overlapping personal/family histories. Therefore BP5 cannot be evaluated.

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.
Evidence considered
  • ClinGen PTEN VCEP specification v3.2 requires at least two such cases and additionally requires a highly penetrant alternate gene/disorder with no personal or family-history overlap with PTEN.
  • The available case evidence does not document an alternate molecular diagnosis or the required clinical histories.
Still missing
  • At least two variant-positive cases with an alternate molecular basis
  • Evidence that each alternate gene/disorder is highly penetrant
  • Personal and family histories demonstrating no overlap with PTEN for each case
Sources
Not applicable · 12· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: the exon 7 in-frame indel is outside the PTEN VCEP decision tree's covered null, splice-site, exon-deletion, duplication, and initiation-codon variant classes. Details ▾Hide ▴
Reasoning

The PTEN VCEP PVS1 rule directs use of the PTEN PVS1 decision tree. This variant is an in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, producing p.(Val255_His259delinsAlaGluTyrPro) in exon 7; it is not a nonsense, frameshift, canonical splice-site, exon-deletion, duplication, or initiation-codon variant covered by the decision tree. Therefore, PVS1 is not applicable. No exact notation for this variant was found in PVS1_DecisionTree_PTEN.pdf.txt after searching c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, and p.V255_H259delinsAEYP.

VCEP rule
Use PTEN PVS1 decision tree.
Evidence considered
  • PTEN VCEP PVS1 CSPEC entry: 'Use PTEN PVS1 decision tree.'
  • PTEN PVS1 decision tree: covered classes are nonsense/frameshift, GT-AG splice sites, exon deletions, duplications, and initiation-codon variants; no in-frame indel path is present.
  • Variant assessment: NM_000314.8:c.764_776delinsCAGAGTACCC; NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro); exon 7; consequence_class in_frame_indel_unknown; canonical_splice_consensus false.
Still missing
  • No exact match for c.764_776delinsCAGAGTACCC, p.Val255_His259delinsAlaGluTyrPro, or p.V255_H259delinsAEYP was found in /Users/gs_agent/LYFESCI_HERMES_v11/vcep_db/PTEN/fulltext/PVS1_DecisionTree_PTEN.pdf.txt.
Sources
PM3 VCEPNot applicable: the PTEN VCEP Version 3.2 CSPEC explicitly designates PM3 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP Version 3.2 CSPEC entry explicitly marks PM3 as not applicable. Therefore, PM3 is not evaluated for this PTEN variant, regardless of the absence of phase or affected-proband observations in the available case materials.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen PTEN Expert Panel Specifications Version 3.2 CSPEC entry for PM3: applicability is "Not Applicable".
Sources
PM5 N/ANot applicable: the variant is an in-frame indel spanning residues 255-259, whereas the VCEP PM5 rule requires a missense change. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule is limited to a missense change at an amino acid residue and additionally requires a BLOSUM62 comparison with a known pathogenic or likely pathogenic missense change. This variant is an in-frame indel producing p.(Val255_His259delinsAlaGluTyrPro), not a missense change, 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
  • PTEN VCEP PM5 rule requires a missense change at an amino acid residue with a previously seen pathogenic or likely pathogenic different missense change and a BLOSUM62 score no greater than the known variant.
  • The normalized consequence is p.(Val255_His259delinsAlaGluTyrPro), classified as an in-frame indel rather than a missense variant; the PM5 candidate artifact therefore found 0 candidates.
Sources
cspec ↗pm5_candidates
PP2 N/ANot applicable: PP2 requires a missense variant, but this variant is an in-frame indel affecting residues 255-259. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP2 rule applies to a missense variant in a gene with a low rate of benign missense variation and missense disease mechanism. The case variant is an in-frame indel, not a missense variant, so the rule 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
  • PTEN VCEP PP2 rule applies to a missense variant in a gene with a low rate of benign missense variation where missense variants are a common disease mechanism.
  • The normalized protein consequence is p.(Val255_His259delinsAlaGluTyrPro), an in-frame indel rather than a missense variant.
Sources
PP3 N/ANot applicable: this is an in-frame indel, whereas PTEN PP3 names only splicing concordance or missense REVEL > 0.7. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 rule names only splicing variants assessed by concordance of SpliceAl and VarSeak, and missense variants assessed by REVEL score > 0.7. This variant is an in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, producing p.(Val255_His259delinsAlaGluTyrPro), so it lies outside both named computational paths. The available SpliceAI score is therefore not evidence for PP3 under this rule.

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: in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the VCEP PP3 rule does not name an in-frame-indel path; it names SpliceAl and VarSeak concordance for splicing variants and REVEL > 0.7 for missense variants.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 Use 2 rather than allowing independent PP4 application. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks PP4 not applicable because phenotype specificity has been incorporated into PS4 Use 2. PP4 is therefore not used independently under this governing framework.

VCEP rule
Phenotype specificity has been incorporated into the rule specifications for PS4 Use 2.
Evidence considered
  • The PTEN VCEP CSPEC entry lists PP4 as not applicable and states that phenotype specificity has been incorporated into PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP explicitly prohibits use of PP5 under its specification. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly states that PP5 is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee, so no reputable-source pathogenic assertion can activate PP5 in this framework.

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 and instructs that this criterion is not for use.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly marks BP1 as not applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks BP1 as not applicable. No BP1 evidence can therefore be assigned under this governing specification.

VCEP rule
Not Applicable
Evidence considered
  • The PTEN VCEP criteria entry for BP1 is explicitly marked 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, regardless of whether an in-frame indel occurs in a repetitive region without known function. BP3 is therefore not assessed as an applicable benign criterion for this variant.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • PTEN VCEP BP3 entry: applicability is 'Not applicable' and instructions state, 'This rule is not applicable to PTEN.'
Sources
BP4 N/ANot applicable: this is an in-frame indel, whereas PTEN BP4 names only splicing concordance or missense REVEL < 0.5. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 rule names only splicing variants assessed by concordance of SpliceAl and VarSeak, and missense variants assessed by REVEL scores < 0.5. This variant is an in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, producing p.(Val255_His259delinsAlaGluTyrPro), so it lies outside both named computational paths. The available SpliceAI score is therefore not evidence for BP4 under this rule.

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: in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the VCEP BP4 rule does not name an in-frame-indel path; it names SpliceAl and VarSeak concordance for splicing variants and REVEL < 0.5 for missense variants.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly prohibits use of BP6 under its specification. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly states that BP6 is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee, so BP6 cannot be applied.

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 and instructs that this criterion is not for use.
Sources
BP7 N/ANot applicable: BP7 covers synonymous or intronic variants at or beyond +7/-21, not this exonic in-frame indel. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous variants or intronic variants at or beyond +7/-21 with splice prediction algorithms predicting no impact to the splice consensus sequence or no creation of a new splice. This variant is an in-frame exonic indel in exon 7, not a synonymous or intronic variant, so BP7 is outside its governing scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • Variant location and consequence: exonic in-frame indel in exon 7, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the variant is outside BP7's synonymous/intronic scope.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.764_776delinsCAGAGTACCC
Protein (HGVS p.)
NP_000305.3:p.(Val255_His259delinsAlaGluTyrPro)
GRCh38
chr10:87957982 TAGAGTTCTTCCA>CAGAGTACCC
GRCh37
chr10:89717739 TAGAGTTCTTCCA>CAGAGTACCC
Location and type
Exon 7 · in frame indel unknown

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 -273 bp
0.012
SpliceAI acceptor gainat -75 bp
0.007
SpliceAI donor lossat -150 bp
0.006
SpliceAI donor gainat -227 bp
0.001
Pangolin splice lossmagnitude shown
-0.008
Pangolin splice gain
0.016

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: this is an in-frame indel, whereas PTEN PP3 names only splicing concordance or missense REVEL > 0.7. Details ▾Hide ▴
Reasoning

The PTEN VCEP PP3 rule names only splicing variants assessed by concordance of SpliceAl and VarSeak, and missense variants assessed by REVEL score > 0.7. This variant is an in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, producing p.(Val255_His259delinsAlaGluTyrPro), so it lies outside both named computational paths. The available SpliceAI score is therefore not evidence for PP3 under this rule.

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: in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the VCEP PP3 rule does not name an in-frame-indel path; it names SpliceAl and VarSeak concordance for splicing variants and REVEL > 0.7 for missense variants.
Sources
BP4 N/ANot applicable: this is an in-frame indel, whereas PTEN BP4 names only splicing concordance or missense REVEL < 0.5. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP4 rule names only splicing variants assessed by concordance of SpliceAl and VarSeak, and missense variants assessed by REVEL scores < 0.5. This variant is an in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, producing p.(Val255_His259delinsAlaGluTyrPro), so it lies outside both named computational paths. The available SpliceAI score is therefore not evidence for BP4 under this rule.

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: in-frame indel, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the VCEP BP4 rule does not name an in-frame-indel path; it names SpliceAl and VarSeak concordance for splicing variants and REVEL < 0.5 for missense variants.
Sources
BP7 N/ANot applicable: BP7 covers synonymous or intronic variants at or beyond +7/-21, not this exonic in-frame indel. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP7 rule applies only to synonymous variants or intronic variants at or beyond +7/-21 with splice prediction algorithms predicting no impact to the splice consensus sequence or no creation of a new splice. This variant is an in-frame exonic indel in exon 7, not a synonymous or intronic variant, so BP7 is outside its governing scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond +7/-21 for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice.
Evidence considered
  • Variant location and consequence: exonic in-frame indel in exon 7, NM_000314.8:c.764_776delinsCAGAGTACCC, p.(Val255_His259delinsAlaGluTyrPro).
  • The available SpliceAI max delta score of 0.012 was not used because the variant is outside BP7's synonymous/intronic scope.
Sources

Statement

In silico

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

0 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata.

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 did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. PTEN, a lipid and protein phosphatase, is one of the most frequently mutated genes in cancer.

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.