0%
Print report
Variant interpretation report

PTEN c.786del, p.Asn262LysfsTer4

NM_000314.8:c.786del NP_000305.3:p.(Asn262LysfsTer4) Frameshift · exon 7 View identifiers
Classification
Likely pathogenic

Variant description:

The PTEN NM_000314.8:c.786del (NP_000305.3:p.(Asn262LysfsTer4)) frameshift variant has not previously been reported in somatic cancers (COSMIC). 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 at very strong strength: the exon 7 frameshift creates a premature stop at codon 265, 5' of the p.D375 NMD threshold in NM_000314.8.

PM2Supporting
PM2 · supporting

Met at Supporting: the variant is absent from gnomAD v2.1 and v4.1, consistent with the VCEP requirement of <0.00001 (0.001%) allele frequency.

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

Recorded SpliceAI maximum delta score: 0.069. 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
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 · 3 not met · 10 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

PS2, PM6, PP1, and BS4 are all not assessed because the supplied case evidence contains no proband-level de novo or parental-testing data and no affected-family segregation or non-segregation data.

All three requested criteria are not_applicable because the PTEN VCEP scopes PP3 and BP4 to synonymous/intronic or missense situations and BP7 to synonymous/intronic variants, while NM_000314.8:c.786del is an exonic frameshift.

Met · 2

PVS1 Very strongVCEPMet at very strong strength: the exon 7 frameshift creates a premature stop at codon 265, 5' of the p.D375 NMD threshold in NM_000314.8. Details ▾Hide ▴
Reasoning

NM_000314.8:c.786del is a frameshift producing NP_000305.3:p.(Asn262LysfsTer4) / p.(N262Kfs*4). The premature stop is at codon 265, 5' of the VCEP threshold p.D375 (c.1121), and exon 7 is present in the biologically relevant transcript NM_000314.8; this follows the VCEP decision-tree path for a nonsense or frameshift predicted to undergo NMD and therefore assigns full PVS1. No exact variant row was found in PVS1_DecisionTree_PTEN.pdf.txt, so the governing decision-tree row was applied to the documented consequence and transcript facts.

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
  • Variant facts: NM_000314.8:c.786del is a frameshift in exon 7, producing NP_000305.3:p.(Asn262LysfsTer4) / p.(N262Kfs*4).
  • PVS1_DecisionTree_PTEN.pdf.txt, page 1, nonsense or frameshift row: the predicted-NMD path for a stop codon or disruption at or 5' to p.D375 (c.1121) in an exon present in NM_000314.8 assigns PVS1.
  • The variant's premature stop at codon 265 is 5' of p.D375 (codon 375), and exon 7 is present in the biologically relevant NM_000314.8 transcript.
Still missing
  • No exact entry for c.786del, p.Asn262LysfsTer4, or p.N262Kfs*4 was found in PVS1_DecisionTree_PTEN.pdf.txt; the applicable decision-tree row was used instead.
Sources
PM2 SupportingVCEPMet at Supporting: the variant is absent from gnomAD v2.1 and v4.1, consistent with the VCEP requirement of <0.00001 (0.001%) allele frequency. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP permits PM2 at Supporting strength when a variant is present at <0.00001 (0.001%) allele frequency in gnomAD or another large sequenced population; if multiple alleles are present within a subpopulation, that subpopulation frequency must be <0.00002 (0.002%). The variant was absent from all-comers gnomAD v2.1 and v4.1, satisfying the VCEP's ultra-rare population requirement; no non-cancer-only source is specified by this VCEP rule.

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
  • gnomAD v2.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no allele frequency reported.
  • gnomAD v4.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no allele frequency reported.
  • The VCEP PM2 rule states: 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%).
Sources

Not met · 3 · evaluated, threshold not reached

PM1 VCEPNot met: the frameshift begins at residue 262, outside all VCEP-approved PM1 catalytic motifs (90-94, 123-130, and 166-168). Details ▾Hide ▴
Reasoning

The PTEN VCEP defines PM1 as a variant located in a mutational hotspot and/or critical functional domain, specifically catalytic-motif residues 90-94, 123-130, or 166-168 on NP_000305.3. The variant's frameshift begins at Asn262, outside every specified PM1 region. vcep_materials.json has no domain_tables entry for PTEN, and the available hotspot evidence reports no statistically significant hotspot; the VCEP does not name a source-specific somatic hotspot route that would independently qualify this variant.

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 VCEP PM1 specification defines the critical regions as catalytic-motif residues 90-94, 123-130, and 166-168 (NP_000305.3).
  • The variant protein consequence is NP_000305.3:p.(Asn262LysfsTer4), placing the first altered residue at 262, outside all three specified regions.
  • vcep_materials.json contains no PTEN domain_tables entry, and the Cancer Hotspots result for PTEN N262 is no result; the VCEP text does not identify cancerhotspots.org or COSMIC as a qualifying PM1 hotspot source.
Sources
cspec ↗pvs1_variant_assessmenthotspots ↗
BA1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, rather than exceeding the BA1 threshold of >0.00056 (0.056%). Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires gnomAD filtering allele frequency >0.00056 (0.056%) for BA1. The variant was absent from the all-comers gnomAD v2.1 and v4.1 records, so no allele frequency reaches this threshold.

VCEP rule
gnomAD Filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • gnomAD v2.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no filtering allele frequency reported.
  • gnomAD v4.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no filtering allele frequency reported.
  • The VCEP's BA1 rule is gnomAD Filtering allele frequency >0.00056 (0.056%).
Sources
BS1 VCEPNot met: the variant is absent from gnomAD v2.1 and v4.1, with no filtering allele frequency in either BS1 interval beginning at 0.0000043 (0.00043%). Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) for BS1, or 0.0000043 (0.00043%) up to 0.000043 (0.0043%) for BS1 Supporting. The variant was absent from the all-comers gnomAD v2.1 and v4.1 records, so neither frequency interval is met.

VCEP rule
gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) ... Allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
Evidence considered
  • gnomAD v2.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no filtering allele frequency reported.
  • gnomAD v4.1 all-comers record for NM_000314.8:c.786del: absent; source_data was empty, with no filtering allele frequency reported.
  • The VCEP's BS1 Strong interval is gnomAD Filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%).
  • The VCEP's BS1 Supporting interval is allele frequency from 0.0000043 (0.00043%) up to 0.000043 (0.0043%).
Sources

Not assessed · 10 · no assessment recorded

PS2 VCEPNot assessed: no proband-level parental testing, de novo observation, disease status, or family-history evidence is available. Details ▾Hide ▴
Reasoning

The available case evidence contains no proband-level report establishing a de novo observation, no parental testing results, no confirmation of maternity or paternity, and no documentation of disease or family-history status. Therefore the PTEN VCEP PS2 rule cannot be evaluated.

VCEP rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history.
Evidence considered
  • No proband, parental-testing, de novo, or family-history evidence was present in the supplied case-evidence records.
  • Applied the ClinGen PTEN VCEP PS2 rule requiring a de novo observation in a patient with the disease and no family history, with both maternity and paternity confirmed for the Strong level.
Still missing
  • Proband-level de novo observation for NM_000314.8:c.786del
  • Parental testing results with confirmed maternity and paternity
  • Proband disease phenotype and family-history status
Sources
PS3 VCEPNot assessed: this frameshift has no c.786del, p.Asn262LysfsTer4, or p.N262Kfs*4 assay row in the governing mmc2.xlsx dataset. Details ▾Hide ▴
Reasoning

The PTEN variant is a frameshift, NM_000314.8:c.786del, p.(Asn262LysfsTer4)/p.(N262Kfs*4), rather than a missense variant. The governing PTEN VCEP evidence source mmc2.xlsx is the Mighell et al. 2018 saturation-mutagenesis phosphatase assay dataset, whose applicable indexed use is for missense variants and whose Table S2 requires a high-confidence variant row before applying PS3_Moderate. Direct searches of the complete converted mmc2.xlsx text for c.786del, p.Asn262LysfsTer4, and p.N262Kfs*4 found no entry; therefore no VCEP-qualified phosphatase result, high-confidence flag, or PS3 strength can be assigned. No variant-specific functional assay result for this frameshift is available in the reviewed case 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_Moderate is tied to the Mighell et al. 2018 PTEN phosphatase assay and requires the variant to be listed as TRUE under the Table S2 high-confidence column before use.
  • PTEN mmc2.xlsx converted full text, Table S2: direct searches for c.786del, p.Asn262LysfsTer4, and p.N262Kfs*4 found no matching variant row; the file's indexed assay data are for missense variants.
  • The normalized case variant is NM_000314.8:c.786del, predicted to produce p.(Asn262LysfsTer4), a frameshift consequence.
Still missing
  • No entry for c.786del, p.Asn262LysfsTer4, or p.N262Kfs*4 was found in the complete converted text of mmc2.xlsx; consequently, no Table S2 cumulative score or high-confidence flag is available.
  • No independent variant-specific functional assay result for this frameshift was available in the reviewed case evidence.
Sources
PS4 VCEPNot assessed: no variant-carrier case/control counts, odds ratio, or VCEP phenotype-specificity scores are available to evaluate PS4. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP permits PS4 for a sufficiently powered case-control study when the odds ratio is >2, p<0.05, and the 95% confidence-interval lower limit is >1.5; it also permits phenotype-specific scoring of independent probands, with 1 point for an adult Cleveland Clinic score >=30, 0.5 for 25-29, 1 point for a child pediatric phenotype score >=5, or 0.5 for a score of 4. No affected-proband phenotype scores, variant-carrier case counts, unaffected-control counts, or case-control statistics are available here. literature_pass.json contains no packet.ai_classified_papers entries to verify, and the available literature packet contains only general functional papers without variant-specific case-control or phenotype-specific evidence. gnomAD v2.1, v4.1, and Canada report the variant as absent, so the VCEP condition that PS4 may not be applied if BS1 applies is not triggered; however, absence in population databases alone does not satisfy the VCEP PS4 rule. The governing case-control operator is the VCEP's literal >2 condition: no observed odds ratio is available, so no substituted inequality can be evaluated and PS4 remains not_assessed.

VCEP rule
This criterion may not be applied if BS1 applies. Phenotype specificity scores are added across independent probands and calculated as follows: ... PS4\_Very Strong: Probands with specificity score ≥16. 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. ... 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.
Evidence considered
  • ClinGen PTEN VCEP PS4 rule: a sufficiently powered case-control study may apply PS4 when the odds ratio is >2, p<0.05, and the 95% confidence-interval lower limit is >1.5; the VCEP also specifies phenotype-specificity scoring across independent probands.
  • The VCEP PS4 rule states that PS4 may not be applied if BS1 applies; gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada each report NM_000314.8:c.786del as absent, with no BS1-range frequency shown.
  • The literature packet has total_pmids=2, ai_classified_papers=[], and no criterion-screened variant-specific case-control or phenotype-specific findings; the two listed papers are general PTEN functional papers.
Still missing
  • Affected-proband counts and matched unaffected-control counts for NM_000314.8:c.786del, or a reported odds ratio with p value and 95% confidence interval.
  • Independent proband phenotype data sufficient to calculate Cleveland Clinic or pediatric phenotype specificity scores.
Sources
PM6 VCEPNot assessed: no presumed de novo observations, parental-testing results, proband disease status, or family-history evidence is available. Details ▾Hide ▴
Reasoning

The available case evidence contains no presumed or assumed de novo observations, no parental-testing results, no proband phenotype or disease-status documentation, and no family-history information. The VCEP PM6 thresholds 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
  • No presumed or assumed de novo observations or associated parental-testing, disease-status, or family-history evidence were present in the supplied case-evidence records.
  • Applied the ClinGen PTEN VCEP PM6 rule defining Very Strong, Strong, and Moderate de novo evidence by the number and confirmation status of observations.
Still missing
  • Number of presumed or assumed de novo observations
  • Maternity and paternity confirmation status for each observation
  • Proband disease phenotype and family-history status
Sources
PP1 VCEPNot assessed: no affected relatives, co-segregation observations, or countable meioses are available for the variant. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected family members, variant-positive relatives, co-segregation observations, or countable meioses. The VCEP PP1 strength thresholds of 3–4, 5–6, or at least 7 meioses cannot therefore be evaluated.

VCEP rule
Co-segregation with disease in multiple affected family members, with 3 or 4 meioses observed.
Evidence considered
  • No family segregation data, affected relatives, variant-positive relatives, or meiosis count was present in the supplied case-evidence records.
  • Applied the ClinGen PTEN VCEP PP1 thresholds requiring co-segregation in multiple affected family members with 3 or more observed meioses.
Still missing
  • Affected family members with phenotype information
  • Variant status in affected relatives
  • Countable informative meioses and family count
Sources
BS2 VCEPNot assessed: gnomAD reports the variant absent and provides no homozygous observations or clinical and parental-confirmation data required by BS2. 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 confirmed observation or two observations if homozygous status is not confirmed. The available gnomAD records report the variant as absent and provide no homozygote observations or individual-level clinical and 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
  • gnomAD v2.1 all-comers record for NM_000314.8:c.786del: absent; no homozygote count or individual-level record was reported.
  • gnomAD v4.1 all-comers record for NM_000314.8:c.786del: absent; no homozygote count or individual-level record was reported.
  • The VCEP requires the variant to be observed 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.
Still missing
  • No documented homozygous observation in a healthy or PHTS-unaffected individual.
  • No homozygote confirmation status or individual-level clinical information.
Sources
BS3 VCEPNot assessed: this frameshift has no c.786del, p.Asn262LysfsTer4, or p.N262Kfs*4 assay row in the governing mmc2.xlsx dataset. Details ▾Hide ▴
Reasoning

The PTEN variant is a frameshift, NM_000314.8:c.786del, p.(Asn262LysfsTer4)/p.(N262Kfs*4), rather than a missense variant. The governing PTEN VCEP evidence source mmc2.xlsx is the Mighell et al. 2018 saturation-mutagenesis phosphatase assay dataset, whose applicable indexed use is for missense variants and whose Table S2 requires a high-confidence variant row before applying BS3_Supporting. Direct searches of the complete converted mmc2.xlsx text for c.786del, p.Asn262LysfsTer4, and p.N262Kfs*4 found no entry; therefore no VCEP-qualified phosphatase score greater than zero or BS3 strength can be assigned. No variant-specific functional assay demonstrating no damaging effect for this frameshift is available in the reviewed case 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 may use the Mighell et al. 2018 phosphatase assay only when the variant is listed as TRUE under the Table S2 high-confidence column and its phosphatase activity is greater than zero.
  • PTEN mmc2.xlsx converted full text, Table S2: direct searches for c.786del, p.Asn262LysfsTer4, and p.N262Kfs*4 found no matching variant row; the file's indexed assay data are for missense variants.
  • The normalized case variant is NM_000314.8:c.786del, predicted to produce p.(Asn262LysfsTer4), a frameshift consequence.
Still missing
  • No entry for c.786del, p.Asn262LysfsTer4, or p.N262Kfs*4 was found in the complete converted text of mmc2.xlsx; consequently, no Table S2 cumulative score or high-confidence flag is available.
  • No independent variant-specific functional assay result demonstrating no damaging effect for this frameshift was available in the reviewed case evidence.
Sources
BS4 VCEPNot assessed: no affected-family non-segregation observations or family-level segregation analysis is available. Details ▾Hide ▴
Reasoning

The available case evidence contains no affected family members with documented non-segregation and no family-level segregation analysis. The VCEP BS4 rule cannot be evaluated for either one-family supporting evidence or two-or-more-family strong evidence.

VCEP rule
Lack of segregation in affected members of one family.
Evidence considered
  • No affected-family variant testing, non-segregation observation, or family-level segregation analysis was present in the supplied case-evidence records.
  • Applied the ClinGen PTEN VCEP BS4 rule distinguishing lack of segregation in affected members of one family from lack of segregation in affected members of two or more families.
Still missing
  • Affected family members tested for the variant
  • Documented non-segregation in one or more families
  • Number of families with evaluable affected-member data
Sources
BP2 VCEPNot assessed: no qualifying trans observation or at least three cis/phase-unknown observations with different pathogenic PTEN variants are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP BP2 rule requires either observation of NM_000314.8:c.786del in trans with a pathogenic or likely pathogenic PTEN variant, or at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants. The available case evidence contains no documented affected-proband observation, paired PTEN variant, phase determination, or qualifying count of cis/phase-unknown observations, so BP2 cannot be evaluated.

VCEP rule
Observed in trans with a pathogenic or likely pathogenic PTEN variant OR at least three observations in cis and/or phase unknown with different pathogenic/likely pathogenic PTEN variants.
Evidence considered
  • ClinGen PTEN Expert Panel Specifications, BP2 entry: the rule requires 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 or likely pathogenic PTEN variants.
  • The reviewed case evidence documents NM_000314.8:c.786del but does not document a qualifying paired PTEN pathogenic/likely pathogenic variant, phase, affected-proband observation, or three qualifying cis/phase-unknown observations.
Still missing
  • Documented case-level or literature observations pairing c.786del with a different pathogenic or likely pathogenic PTEN variant, including phase and affected-proband context, are unavailable.
  • The required count of at least three cis and/or phase-unknown observations with different pathogenic or likely pathogenic PTEN variants cannot be established.
Sources
BP5 VCEPNot assessed: no two cases with a highly penetrant alternate diagnosis and documented non-overlapping PTEN history are available for BP5. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires at least two cases in which the variant is found with an alternate molecular basis for disease, requires the other gene/disorder to be highly penetrant, and requires the patient's personal or family history to demonstrate no overlap between that disorder and PTEN. The available case materials contain no alternate molecular diagnosis, no two qualifying cases, and no personal or family-history comparison. The VCEP BP5 rule has no numeric threshold or comparison operator; therefore no numeric inequality is applicable. The criterion cannot be evaluated from the available evidence and is not_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.
Evidence considered
  • ClinGen PTEN VCEP BP5 instructions require at least two such cases, a highly penetrant alternate gene/disorder, and personal/family history demonstrating no overlap between the alternate disorder and PTEN.
  • No alternate molecular diagnosis, qualifying case series, or relevant personal/family-history evidence is present in the supplied case materials.
Still missing
  • At least two qualifying cases carrying NM_000314.8:c.786del with a documented alternate molecular basis for disease.
  • Evidence that each alternate gene/disorder is highly penetrant and that each patient's personal/family history does not overlap PTEN.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: c.786del is a frameshift, whereas PS1 requires the same amino-acid change or a specified pathogenic splicing comparison. Details ▾Hide ▴
Reasoning

The queried variant is NM_000314.8:c.786del, a frameshift yielding NP_000305.3:p.(Asn262LysfsTer4), not a same-amino-acid missense change and not a different variant at the same nucleotide position as a pathogenic splicing variant. 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
  • The case variant is NM_000314.8:c.786del with consequence class frameshift and protein consequence NP_000305.3:p.(Asn262LysfsTer4).
  • The PTEN VCEP PS1 rule is restricted to a 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.
Sources
cspec ↗pvs1_variant_assessment
PM3 VCEPNot applicable: the PTEN VCEP explicitly states that PM3 is not applicable to PTEN. Details ▾Hide ▴
Reasoning

PM3 is not applicable under the ClinGen PTEN Expert Panel specification, which explicitly excludes this criterion for PTEN. No recessive-disease phase or trans-observation assessment is therefore performed.

VCEP rule
This rule is not applicable to PTEN.
Evidence considered
  • ClinGen PTEN Expert Panel Specifications, PM3 entry: applicability is not applicable and the instruction states, "This rule is not applicable to PTEN."
Sources
PM4 N/ANot applicable: the variant is a frameshift with a premature stop, whereas PTEN PM4 is limited to in-frame length changes and stop-loss extensions. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule applies to protein length changes caused by in-frame deletions or insertions in a non-repeat region, including catalytic-motif in-frame indels, and to stop-loss protein extensions. This variant is a frameshift with a premature stop, not an in-frame insertion/deletion or stop-loss variant, so PM4 is not applicable.

VCEP rule
Protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants. Applies to in-frame insertions or deletions impacting at least one residue in a catalytic motif (see PM1), and variants causing protein extension.
Evidence considered
  • The variant assessment classifies NM_000314.8:c.786del as a frameshift producing p.(Asn262LysfsTer4).
  • CSPEC PTEN PM4 rule: protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants; the rule also names catalytic-motif in-frame indels and protein extension.
Sources
cspec ↗pvs1_variant_assessment
PM5 N/ANot applicable: c.786del is a frameshift, but PM5 requires a missense change at a residue with a different pathogenic or likely pathogenic missense change. 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 seen, with the interrogated variant's BLOSUM62 score no greater than the known variant. NM_000314.8:c.786del is a frameshift, so this missense-specific criterion does not apply.

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
  • The case variant is classified as a frameshift, not a missense variant.
  • The PTEN VCEP PM5 rule explicitly requires a missense change and a BLOSUM62 comparison with a different pathogenic or likely pathogenic missense change at the same residue.
Sources
cspec ↗pvs1_variant_assessment
PP2 N/ANot applicable: PP2 requires a missense variant, whereas NM_000314.8:c.786del is a frameshift. Details ▾Hide ▴
Reasoning

The 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. This 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
  • The case variant is classified as a frameshift rather than a missense variant.
  • The PTEN VCEP PP2 rule begins with the required variant type: missense variant.
Sources
cspec ↗pvs1_variant_assessment
PP3 N/ANot applicable: PP3 covers synonymous/intronic splicing-impact predictions or missense REVEL >0.7, whereas c.786del is an exonic frameshift. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP limits PP3 to synonymous or intronic variants with SpliceAl and VarSeak predicted splicing impact, or to missense variants with REVEL score > 0.7. NM_000314.8:c.786del is an exonic frameshift, p.(Asn262LysfsTer4), so it is outside PP3 scope. The available SpliceAI max delta score of 0.069 is not used because SpliceAI alone is not a named PP3 path for this frameshift situation.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic). May also be applied to missense variants with REVEL score > 0.7.
Evidence considered
  • The VCEP applicability instruction specifies synonymous or intronic variants assessed with SpliceAl and VarSeak, and missense variants assessed with REVEL > 0.7.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift.
  • SpliceAI reported max delta score 0.069, but that prediction is not used for PP3 because the variant is outside the VCEP-defined PP3 scope and VarSeak evidence is not a governing path for this frameshift.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 Use 2 rather than allowing independent PP4 application. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks PP4 as not applicable and states that phenotype specificity has been incorporated into PS4 Use 2; therefore PP4 is not independently assessed.

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

The ClinGen PTEN VCEP marks PP5 as not applicable and explicitly recommends that this criterion not be used.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • ClinGen PTEN VCEP PP5 entry: applicability is Not Applicable for this VCEP and the instruction says the criterion is not for use.
Sources
BP1 VCEPNot applicable: the PTEN VCEP explicitly designates BP1 as not applicable. Details ▾Hide ▴
Reasoning

The PTEN VCEP explicitly marks BP1 as Not Applicable. No BP1 evidence may therefore be assigned under this governing specification.

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

The PTEN VCEP explicitly marks BP3 as not applicable. BP3 therefore cannot be assigned to this frameshift variant, regardless of whether a repeat-region context is available.

VCEP rule
Not Applicable
Evidence considered
  • CSPEC PTEN criteria entry for BP3 explicitly states applicability: Not Applicable.
Sources
BP4 N/ANot applicable: BP4 covers synonymous/intronic no-splicing predictions or missense REVEL <0.5, while c.786del is an exonic frameshift. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP limits BP4 to synonymous or intronic variants with concordant SpliceAl and VarSeak predictions of no splicing impact, or to missense variants with REVEL score < 0.5. NM_000314.8:c.786del is an exonic frameshift, p.(Asn262LysfsTer4), so BP4 is not applicable; a no-splice-impact prediction would not negate its truncating protein consequence.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score < 0.5.
Evidence considered
  • The VCEP applicability instruction specifies synonymous or intronic variants assessed with SpliceAl and VarSeak, and missense variants assessed with REVEL < 0.5.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift.
  • SpliceAI reported max delta score 0.069, but this does not support BP4 for a frameshift because the truncating protein effect remains present and the VCEP does not define a frameshift BP4 path.
Sources
BP6 VCEPNot applicable: the PTEN VCEP explicitly recommends that BP6 not be used. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP marks BP6 as not applicable and explicitly recommends that this criterion not be used.

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

The ClinGen PTEN VCEP BP7 rule applies only to synonymous or intronic variants at or beyond +7/-21 with predictions of no splice-consensus impact or new splice creation. NM_000314.8:c.786del is an exonic frameshift, so it is outside BP7 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
  • The VCEP BP7 rule requires a synonymous or intronic variant at or beyond +7/-21 and no predicted splice-consensus impact or new splice creation.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift; therefore BP7 is upstream not applicable and no splicing predictor is needed.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.786del
Protein (HGVS p.)
NP_000305.3:p.(Asn262LysfsTer4)
GRCh38
chr10:87958003 AC>A
GRCh37
chr10:89717760 AC>A
Location and type
Exon 7 · 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 -96 bp
0.069
SpliceAI acceptor gainat -207 bp
0.012
SpliceAI donor lossat +16 bp
0.002
SpliceAI donor gainat -171 bp
0.013
Pangolin splice lossmagnitude shown
-0.070
Pangolin splice gain
0.005

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: PP3 covers synonymous/intronic splicing-impact predictions or missense REVEL >0.7, whereas c.786del is an exonic frameshift. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP limits PP3 to synonymous or intronic variants with SpliceAl and VarSeak predicted splicing impact, or to missense variants with REVEL score > 0.7. NM_000314.8:c.786del is an exonic frameshift, p.(Asn262LysfsTer4), so it is outside PP3 scope. The available SpliceAI max delta score of 0.069 is not used because SpliceAI alone is not a named PP3 path for this frameshift situation.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict a splicing impact (SpliceAl: scores 0.5-1 are consider evidence of pathogenic. VarSeak: Class 4 and 5 are consider evidence of pathogenic). May also be applied to missense variants with REVEL score > 0.7.
Evidence considered
  • The VCEP applicability instruction specifies synonymous or intronic variants assessed with SpliceAl and VarSeak, and missense variants assessed with REVEL > 0.7.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift.
  • SpliceAI reported max delta score 0.069, but that prediction is not used for PP3 because the variant is outside the VCEP-defined PP3 scope and VarSeak evidence is not a governing path for this frameshift.
Sources
BP4 N/ANot applicable: BP4 covers synonymous/intronic no-splicing predictions or missense REVEL <0.5, while c.786del is an exonic frameshift. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP limits BP4 to synonymous or intronic variants with concordant SpliceAl and VarSeak predictions of no splicing impact, or to missense variants with REVEL score < 0.5. NM_000314.8:c.786del is an exonic frameshift, p.(Asn262LysfsTer4), so BP4 is not applicable; a no-splice-impact prediction would not negate its truncating protein consequence.

VCEP rule
**PTEN EP Specification:** To be applied to synonymous or intronic variants where SpliceAl and VarSeak _in silico_ models predict no splicing impact (SpliceAl: scores 0-0.2 are considered evidence of benign. VarSeak: Class 1 and 2 are considered evidence of benign). Not to be applied for variants which may impact the intron 1 splice donor or acceptor sites, and to be used cautiously for variants which may impact the intron 6 splice acceptor. May also be applied to missense variants with REVEL score < 0.5.
Evidence considered
  • The VCEP applicability instruction specifies synonymous or intronic variants assessed with SpliceAl and VarSeak, and missense variants assessed with REVEL < 0.5.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift.
  • SpliceAI reported max delta score 0.069, but this does not support BP4 for a frameshift because the truncating protein effect remains present and the VCEP does not define a frameshift BP4 path.
Sources
BP7 N/ANot applicable: BP7 requires a synonymous or intronic variant at or beyond +7/-21, whereas c.786del is an exonic frameshift. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP BP7 rule applies only to synonymous or intronic variants at or beyond +7/-21 with predictions of no splice-consensus impact or new splice creation. NM_000314.8:c.786del is an exonic frameshift, so it is outside BP7 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
  • The VCEP BP7 rule requires a synonymous or intronic variant at or beyond +7/-21 and no predicted splice-consensus impact or new splice creation.
  • The variant is NM_000314.8:c.786del in exon 7 with predicted protein consequence p.(Asn262LysfsTer4), an exonic frameshift; therefore BP7 is upstream not applicable and no splicing predictor is needed.
Sources

Statement

In silico

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

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

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.