0%
Print report
Variant interpretation report

PTEN c.165-10_209+6del, p.?

NM_000314.8:c.165-10_209+6del NP_000305.3:p.? Unknown View identifiers
Classification
Uncertain significance

Variant description:

No variant summary was recorded for this case.

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: 2 Benign evidence criteria: 0
Pathogenic criteria applied · 2
PVS1Strong
PVS1 · strong

Met, strong: the PTEN tree assigns strong PVS1 to an in-frame single-exon 3 deletion, with a 45-nucleotide coding deletion and SpliceAI maximum delta 0.996.

PM2Supporting
PM2 · supporting

Met at supporting: the variant is absent from gnomAD v2.1 and v4.1, below the PTEN PM2 threshold of 0.00001 allele frequency.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: PVS1 (strong) plus PM2 (supporting) do not satisfy any ClinGen PTEN Expert Panel Version 3.2 pathogenic or likely pathogenic combination rule.

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

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

No listed criterion applied SpliceAI ↗
ClinVar submissions
Not recorded

A ClinVar laboratory submission summary was not recorded.

Context only ClinVar ↗
No screenshot for this evidence
Functional evidence
Not recorded

No standalone functional evidence summary is recorded in evidence_summary.functional.

No listed criterion applied OncoKB ↗
Somatic evidence
No matching record reported

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

Context only COSMIC ↗
For specialists

Technical detail

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

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

Met Not met Not assessed Not applicable

PVS1 is met at strong strength under the PTEN-specific decision tree for an in-frame single-exon 3 deletion.

PM4 is not met because the PTEN VCEP limits in-frame deletion use to deletions affecting specified catalytic motifs or causing protein extension.

BP3 is not applicable under the PTEN VCEP specification.

All five requested codon/residue/domain criteria are not applicable because the variant is a multi-base intronic deletion with unresolved protein consequence NP_000305.3:p.?; no missense residue comparison is available.

The applicable governing framework is the ClinGen PTEN Expert Panel specification, version 3.2.

No case-level proband, parental-testing, de novo, affected-relative segregation, meiosis, or affected variant-negative non-segregation observations were available to adjudicate PS2, PM6, PP1, or BS4.

All four requested criteria are therefore not assessed rather than met, not met, or not applicable.

PP3, BP4, and BP7 are all not_applicable because the case variant is a coding-spanning deletion with protein consequence p.?, not a missense or synonymous variant and not an isolated qualifying intronic/splice-region variant.

The available SpliceAI max delta of 0.996 was intentionally not evaluated because predictor evidence cannot bring an out-of-scope protein-length-changing deletion within PP3 or BP4 scope.

Population evidence is limited to the requested criteria: PM2 is met at supporting strength because the variant is absent from default all-comers gnomAD v2.1 and v4.1; BA1, BS1, and BS2 are not met.

The PTEN Expert Panel Version 3.2 specification governs these assessments and does not require the failed non-cancer gnomAD subset queries.

Met · 2

PVS1 StrongMet, strong: the PTEN tree assigns strong PVS1 to an in-frame single-exon 3 deletion, with a 45-nucleotide coding deletion and SpliceAI maximum delta 0.996. Details ▾Hide ▴
Reasoning

The governing PTEN PVS1 decision tree applies to NM_000314.8 and assigns PVS1_Strong when a single-exon deletion preserves the reading frame, the deleted exon is exon 3, and the altered region is critical to protein function. NM_000314.8:c.165-10_209+6del spans exon 3 and its flanking splice regions; the deleted coding interval c.165_209 is 45 nucleotides, consistent with an in-frame exon-3 deletion. SpliceAI predicts a strong splice effect (maximum delta 0.996), supporting exon loss or altered splicing. The variant is well 5-prime of p.D375/c.1121, and exon 3 is present in the biologically relevant transcript. The searched PVS1_DecisionTree_PTEN.pdf contains no variant-specific row for c.165-10_209+6del or p.?, so the assigned strength comes from the named PTEN decision-tree branch rather than a pre-assigned variant entry.

Rule
PTEN PVS1 decision tree: single exon deletion preserving the reading frame; exon 3 is a critical altered region; assign PVS1_Strong.
Evidence considered
  • The PTEN-specific decision tree states that a single exon 3 deletion preserving the reading frame, with exon 3 critical to protein function, receives PVS1_Strong.
  • The normalized variant is NM_000314.8:c.165-10_209+6del, spanning exon 3 and flanking intronic sequence; c.165_209 is a 45-nucleotide coding interval.
  • SpliceAI reports DS_AL 0.976 and DS_DL 0.996, with maximum delta score 0.996, consistent with substantial splice impact.
  • The PTEN VCEP framework uses NM_000314.8 as the preferred transcript and directs PVS1 assessment to the PTEN decision tree.
Still missing
  • PVS1_DecisionTree_PTEN.pdf was searched for c.165-10_209+6del and p.?; no variant-specific entry was found.
  • No RNA or minigene assay directly confirms the transcript-level splice product or NMD behavior for this variant.
Sources
vcep_pvs1_decisiontree_ptencspec ↗spliceai ↗
PM2 SupportingMet at supporting: the variant is absent from gnomAD v2.1 and v4.1, below the PTEN PM2 threshold of 0.00001 allele frequency. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 specifies PM2 at supporting strength when the variant is absent 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 absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets, satisfying the PTEN PM2 supporting rule. The failed non-cancer subset queries do not prevent assessment because the PTEN specification does not require a non-cancer subset or an exome-only source for PM2.

Rule
PTEN VCEP v3.2: PM2 supporting when absent or <0.00001 (0.001%) allele frequency; subpopulation with multiple alleles <0.00002 (0.002%)
Evidence considered
  • PTEN Expert Panel Version 3.2 specifies PM2 supporting for absence or allele frequency <0.00001 (0.001%) in gnomAD or another large sequenced population; any subpopulation with multiple alleles must be <0.00002 (0.002%).
  • The variant was reported absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets, satisfying the PTEN PM2 supporting threshold.
  • The gnomAD v2.1 and v3.1 non-cancer queries failed, but the PTEN PM2 specification does not require those subsets; the default all-comers datasets were therefore used.
Sources

Not met · 4 · evaluated, threshold not reached

PM4 Not met: the 45-nucleotide in-frame deletion is outside PTEN catalytic motifs 90-94, 123-130, and 166-168 required by the VCEP PM4 rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM4 rule permits in-frame insertions or deletions only when they affect at least one residue in a defined catalytic motif, or when they cause a protein extension. The coding segment removed by this exon 3 deletion is 45 nucleotides and is predicted to be in-frame, but exon 3 corresponds to the N-terminal region before the PTEN catalytic motifs at residues 90-94, 123-130, and 166-168. The variant is not a stop-loss or protein-extension event, and no evidence places the deleted region in a repeat region or any listed catalytic motif. Therefore the VCEP-specific PM4 requirement is not met.

Rule
PTEN VCEP PM4: in-frame deletion must affect a residue in catalytic motifs 90-94, 123-130, or 166-168, or cause protein extension; neither condition is met.
Evidence considered
  • The PTEN VCEP PM4 specification restricts in-frame deletions to those affecting at least one residue in a listed catalytic motif or causing protein extension.
  • The deleted coding interval c.165_209 is 45 nucleotides and lies in exon 3, before the PTEN catalytic motifs at residues 90-94, 123-130, and 166-168.
  • SpliceAI predicts splice impact with maximum delta 0.996, but this does not establish a catalytic-motif deletion or protein extension for PM4.
Sources
BA1 Not met: the variant is absent from gnomAD v2.1 and v4.1, yielding observed frequency 0 versus the PTEN BA1 threshold >0.00056. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 BA1 rule requires 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 datasets, so its observed allele frequency is 0 and does not meet BA1. The failed non-cancer subset queries were not used because the PTEN specification does not require a non-cancer subset for BA1.

Rule
PTEN VCEP v3.2: gnomAD filtering allele frequency >0.00056 (0.056%)
Evidence considered
  • PTEN Expert Panel Version 3.2 specifies BA1 only when gnomAD filtering allele frequency is >0.00056 (0.056%).
  • The variant was reported absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets; therefore the observed frequency is 0.
  • The gnomAD v2.1 and v3.1 non-cancer queries failed, but those subsets are not required by the PTEN BA1 specification and were not treated as evidence.
Sources
BS1 Not met: gnomAD v2.1 and v4.1 show observed frequency 0, below the PTEN BS1 supporting lower bound of 0.0000043. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 defines BS1 as a gnomAD filtering allele frequency from 0.000043 (0.0043%) up to 0.00056 (0.056%) for strong evidence, or 0.0000043 (0.00043%) up to 0.000043 (0.0043%) for supporting evidence. The variant is absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets, with observed frequency 0, so neither BS1 range is met. The failed non-cancer subset queries were not used because the PTEN specification does not require a non-cancer subset for BS1.

Rule
PTEN VCEP v3.2: BS1 strong at 0.000043–0.00056; BS1 supporting at 0.0000043–0.000043
Evidence considered
  • PTEN Expert Panel Version 3.2 defines BS1 strong as 0.000043–0.00056 and BS1 supporting as 0.0000043–0.000043 allele frequency.
  • The variant was reported absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets; therefore the observed frequency is 0 and below both BS1 ranges.
  • The gnomAD v2.1 and v3.1 non-cancer queries failed, but those subsets are not required by the PTEN BS1 specification and were not treated as evidence.
Sources
BS2 Not met: the variant is absent from gnomAD v2.1 and v4.1, providing zero homozygous population observations required by the PTEN BS2 rule. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel Version 3.2 BS2 rule requires the variant to be observed in the homozygous state in a healthy or PHTS-unaffected individual, with one observation if homozygosity is confirmed or two if it is not confirmed. The variant is absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets, so there is no population observation supporting homozygosity and BS2 is not met.

Rule
PTEN VCEP v3.2: homozygous in a healthy or PHTS-unaffected individual; one confirmed or two unconfirmed observations
Evidence considered
  • PTEN Expert Panel Version 3.2 requires a confirmed homozygous observation in a healthy or PHTS-unaffected individual for BS2 strong, or two unconfirmed homozygous observations for BS2 strong.
  • The variant was reported absent from the default all-comers gnomAD v2.1 and gnomAD v4.1 datasets, so no homozygous population observation is available.
Sources

Not assessed · 9 · no assessment recorded

PS2 Not assessed: no documented proband, parental testing, maternity or paternity confirmation, or qualifying de novo observation is available for the PS2 rule. Details ▾Hide ▴
Reasoning

The PTEN Expert Panel specification requires a documented de novo observation with both maternity and paternity confirmed for PS2 at strong strength, or defined combinations of proven and assumed de novo observations for very strong strength. The available case evidence does not document a proband, parental testing, maternity or paternity confirmation, family history, or any qualifying de novo observation. Therefore, PS2 cannot be assessed.

Rule
De novo (both maternity and paternity confirmed) observation in a patient with the disease and no family history; very strong strength requires two proven, four assumed, or one proven plus two assumed de novo observations.
Evidence considered
  • The PTEN Expert Panel specifies strong PS2 for a de novo observation with both maternity and paternity confirmed in a patient with the disease and no family history.
  • No case-level proband, parental-testing, maternity, paternity, family-history, or de novo observation data are documented in the available case evidence.
Still missing
  • Documented proband with the disease phenotype
  • Parental testing results for the variant
  • Maternity and paternity confirmation
  • Family history sufficient to establish absence of familial disease
  • Number and quality of proven or assumed de novo observations
Sources
PS3 Not assessed: the intronic deletion has no governing mmc2 missense-table entry or available variant-specific assay demonstrating abnormal splicing. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP permits PS3 for RNA, mini-gene, or other assays demonstrating abnormal splicing, and permits PS3_Moderate from Mighell et al. 2018 only when the variant is a high-confidence Table S2 missense entry with Cum_score <= -1.11. The queried variant is the intronic deletion NM_000314.8:c.165-10_209+6del (NP_000305.3:p.?), and the governing mmc2.xlsx full-text table contains no entry for c.165-10_209+6del, p.?, or this intronic deletion; no case RNA or other variant-specific functional assay is present in the supplied evidence. Therefore PS3 cannot be assigned from the available functional evidence.

Rule
PTEN VCEP PS3: RNA, mini-gene, or other assay demonstrating an impact on splicing; PS3_Moderate for Mighell et al. 2018 Table S2 high-confidence variants with Cum_score <= -1.11.
Evidence considered
  • The ClinGen PTEN VCEP PS3 specification allows strong evidence for an assay showing splicing impact and PS3_Moderate for Mighell et al. 2018 Table S2 high-confidence missense variants with cumulative score <= -1.11.
  • The governing mmc2.xlsx full-text file was searched for c.165-10_209+6del, p.?, and the corresponding intronic coordinates; no matching variant entry was found.
  • Case normalization identifies NM_000314.8:c.165-10_209+6del as an intronic deletion with predicted protein consequence NP_000305.3:p.?, and the case evidence contains no variant-specific RNA, mini-gene, or other functional assay result.
Still missing
  • No entry for c.165-10_209+6del or p.? was found in the governing mmc2.xlsx full-text file; the file is restricted to PTEN missense functional-assay data.
  • No variant-specific RNA, mini-gene, or other functional assay demonstrating abnormal splicing was available in the case evidence.
Sources
cspec ↗vcep_mmc2
PS4 Not assessed: no proband specificity scores or case-control enrichment statistics are available to compare with the PTEN PS4 requirements. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification permits PS4 from 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 across independent probands: 1 point per adult with Cleveland Clinic score ≥30, 0.5 points for score 25-29, 1 point per child with pediatric phenotype score ≥5, or 0.5 points for score 4 subject to the stated exclusions. The available case evidence contains no proband phenotype or family-history scores, no independent-proband specificity score, and no case-control enrichment results for this variant, so PS4 cannot be assessed.

Rule
PTEN EP Commentary: 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. Use 2: Patient’s phenotype or family history is highly specific for a disease with a single genetic etiology. Phenotype specificity scores are added across independent probands. 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.
Evidence considered
  • The PTEN VCEP source states that a sufficiently powered case-control study may support PS4 when odds ratio >2, p<0.05, and the 95% confidence interval lower limit >1.5.
  • The PTEN VCEP source defines phenotype-specific scoring as 1 point for an adult Cleveland Clinic score ≥30, 0.5 points for 25-29, 1 point for a pediatric phenotype score ≥5, and 0.5 points for score 4 with exclusions.
  • The case evidence reports no proband phenotype scores, family-history specificity scores, or case-control enrichment statistics for this variant.
Still missing
  • Obtain phenotype and family-history data for independent probands, including Cleveland Clinic or pediatric phenotype scores.
  • If using case-control evidence, obtain odds ratio, p-value, and 95% confidence interval for the exact variant or qualifying PHTS phenotype.
Sources
PM6 Not assessed: no presumed de novo observation, proband disease documentation, parental testing, or family-history information is available for PM6. Details ▾Hide ▴
Reasoning

The PTEN Expert Panel specification permits PM6 for presumed de novo occurrence without confirmed maternity and paternity in a patient with the disease and no family history, with higher strengths requiring specified numbers of proven or assumed observations. The available case evidence contains no documented proband, phenotype, parental testing, family history, or presumed de novo observation. Therefore, PM6 cannot be assessed.

Rule
Assumed de novo, but without confirmation of paternity and maternity, in a proband with the disease and no family history; higher strengths require the specified combinations of proven and assumed de novo observations.
Evidence considered
  • The PTEN Expert Panel specifies moderate PM6 for an assumed de novo variant without confirmed maternity and paternity in a patient with the disease and no family history.
  • No case-level presumed de novo, parental-testing, phenotype, or family-history data are documented in the available case evidence.
Still missing
  • Documented proband with the disease phenotype
  • Evidence that the variant is presumed de novo
  • Parental testing or explicit lack of parental confirmation
  • Family history showing no relevant disease
  • Additional proven or assumed de novo observations if increased strength is considered
Sources
PP1 Not assessed: no affected relatives, segregation results, or counted meioses are documented, so the PTEN thresholds of 3, 5, or 7 meioses cannot be evaluated. Details ▾Hide ▴
Reasoning

The PTEN Expert Panel specification requires co-segregation with disease in multiple affected family members and assigns supporting strength for 3 or 4 observed meioses, moderate strength for 5 or 6 meioses, and strong strength for at least 7 meioses across at least two families. No affected relatives, segregation results, family structure, or meioses are documented in the available case evidence. Therefore, PP1 cannot be assessed.

Rule
Co-segregation with disease in multiple affected family members: supporting for 3 or 4 observed meioses, moderate for 5 or 6 observed meioses, and strong for at least 7 meioses across at least two families.
Evidence considered
  • The PTEN Expert Panel specifies PP1 supporting for 3 or 4 meioses, moderate for 5 or 6 meioses, and strong for at least 7 meioses across at least two families.
  • No case-level affected-relative, pedigree, variant-status, segregation, or meiosis data are documented in the available case evidence.
Still missing
  • Affected family members with phenotype documentation
  • Variant status in each informative relative
  • Pedigree or family structure
  • Number of informative meioses
  • Evidence from one or more families
Sources
BS3 Not assessed: no variant-specific RNA or mini-gene assay shows preserved splicing, and the governing missense functional table contains no entry for this intronic deletion. Details ▾Hide ▴
Reasoning

The ClinGen PTEN VCEP requires an RNA, mini-gene, or other assay demonstrating no splicing impact for BS3 in intronic variants; its BS3_Supporting phosphatase-assay pathway applies to high-confidence missense entries in Mighell et al. 2018 Table S2 with phosphatase activity score >0. The queried variant is the intronic deletion NM_000314.8:c.165-10_209+6del (NP_000305.3:p.?), and the governing mmc2.xlsx full-text table contains no entry for c.165-10_209+6del, p.?, or this intronic deletion; no case assay demonstrates preserved splicing. Therefore BS3 cannot be assigned from the available functional evidence.

Rule
PTEN VCEP BS3: for intronic or synonymous variants, RNA, mini-gene, or other assay demonstrating no impact on splicing; BS3_Supporting for Mighell et al. 2018 high-confidence variants with phosphatase activity score >0.
Evidence considered
  • The ClinGen PTEN VCEP BS3 specification requires an RNA, mini-gene, or other assay showing no splicing impact for intronic variants; BS3_Supporting from Mighell et al. 2018 is limited to high-confidence missense functional results with phosphatase activity score >0.
  • The governing mmc2.xlsx full-text file was searched for c.165-10_209+6del, p.?, and the corresponding intronic coordinates; no matching variant entry was found.
  • Case normalization identifies NM_000314.8:c.165-10_209+6del as an intronic deletion with predicted protein consequence NP_000305.3:p.?, and the case evidence contains no variant-specific assay demonstrating preserved splicing.
Still missing
  • No entry for c.165-10_209+6del or p.? was found in the governing mmc2.xlsx full-text file; the file is restricted to PTEN missense functional-assay data.
  • No variant-specific RNA, mini-gene, or other functional assay demonstrating no splicing impact was available in the case evidence.
Sources
cspec ↗vcep_mmc2
BS4 Not assessed: no affected variant-negative relatives or family-level non-segregation observations are documented for the one-family or two-family BS4 thresholds. Details ▾Hide ▴
Reasoning

The PTEN Expert Panel specification requires lack of segregation in affected members of one family for BS4 at supporting strength and two or more families for strong strength, while recognizing phenocopies and multiple pathogenic variants as confounders. No affected relatives, variant-negative affected individuals, family pedigrees, or non-segregation observations are documented in the available case evidence. Therefore, BS4 cannot be assessed.

Rule
Lack of segregation in affected members of one family supports BS4 at supporting strength; lack of segregation in affected members of two or more families supports strong strength.
Evidence considered
  • The PTEN Expert Panel specifies BS4 supporting for lack of segregation in one family and BS4 strong for lack of segregation in two or more families, with phenocopies and multiple pathogenic variants as confounders.
  • No case-level affected-relative, variant-negative, pedigree, family-count, or non-segregation data are documented in the available case evidence.
Still missing
  • Affected relatives evaluated for the variant
  • Variant-negative status in affected relatives
  • Family pedigrees and number of families
  • Phenotype specificity and assessment of phenocopy risk
  • Assessment for additional pathogenic variants that could confound segregation
Sources
BP2 Not assessed: no documented cis/trans phase or qualifying co-occurring pathogenic PTEN variant observations are available for the required BP2 rule. Details ▾Hide ▴
Reasoning

The PTEN Expert Panel specification permits BP2 at supporting strength when the variant is observed in trans with a pathogenic or likely pathogenic PTEN variant, or in at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants. The available case evidence contains no affected-proband observations, allelic phase information, co-occurring PTEN variants, or documented pathogenic/likely pathogenic variants in cis or trans; therefore BP2 cannot be assessed.

Rule
PTEN VCEP BP2 Supporting: 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
  • The governing PTEN Expert Panel rule requires either observation in trans with a pathogenic or likely pathogenic PTEN variant, or at least three observations in cis and/or phase unknown with different pathogenic or likely pathogenic PTEN variants.
  • No qualifying co-occurring PTEN variant, affected-proband observation, or cis/trans phase observation is documented in the reviewed case evidence.
Still missing
  • Documented affected-proband observations with a qualifying second PTEN pathogenic or likely pathogenic variant.
  • Reliable phase information establishing trans, or at least three qualifying cis/phase-unknown observations.
Sources
BP5 Not assessed: no two qualifying cases with a highly penetrant alternate diagnosis and non-overlapping PTEN history are documented. Details ▾Hide ▴
Reasoning

The PTEN VCEP allows BP5 at supporting strength only when the variant is found in at least two cases with an alternate molecular basis, the other gene or disorder is highly penetrant, and the personal or family history shows no overlap between that disorder and PTEN. The available evidence contains no qualifying cases, alternate molecular diagnosis, penetrance assessment, or non-overlapping phenotype/family-history documentation, so BP5 cannot be assessed.

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
  • The PTEN VCEP requires at least two BP5 cases and requires the alternate gene or disorder to be highly penetrant with no overlap between the patient's personal or family history and PTEN.
  • The case evidence provides no qualifying BP5 cases or alternate molecular diagnosis.
Still missing
  • Identify at least two cases carrying the exact variant with a documented alternate molecular basis for disease.
  • Verify high penetrance of the alternate disorder and absence of phenotype or family-history overlap with PTEN.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PS1 N/ANot applicable: c.165-10_209+6del is a multi-base intronic deletion with NP_000305.3:p.? rather than a missense amino-acid change. Details ▾Hide ▴
Reasoning

The PTEN VCEP PS1 rule requires the same amino-acid change as an established pathogenic variant, or a different variant at the same nucleotide position as a pathogenic splicing variant with comparable predicted impact. This variant is NM_000314.8:c.165-10_209+6del, a multi-base intronic deletion with normalized protein consequence NP_000305.3:p.?, so there is no defined amino-acid change for PS1 and no qualifying comparator was identified in the available ClinVar query.

Rule
PTEN VCEP PS1: same amino acid change as a previously established pathogenic variant regardless of nucleotide change, or a different variant at the same nucleotide position as a pathogenic splicing variant with equal or greater predicted impact.
Evidence considered
  • The PTEN VCEP PS1 specification is based on a previously established pathogenic same-amino-acid change or a qualifying same-position pathogenic splice comparator.
  • The normalized consequence is NP_000305.3:p.? for NM_000314.8:c.165-10_209+6del, and the available ClinVar query returned no record or comparator.
  • Because the variant has no defined amino-acid substitution, PS1 is not applicable.
Sources
PM1 N/ANot applicable: the deletion has no resolved protein residue, so it cannot be assessed against PTEN catalytic motifs 90-94, 123-130, or 166-168. Details ▾Hide ▴
Reasoning

The governing PTEN VCEP defines PM1 at moderate strength for a mutational hotspot or critical functional domain, specifically including catalytic-motif residues 90-94, 123-130, and 166-168 of NP_000305.3. The variant has no resolved protein residue or amino-acid consequence (NP_000305.3:p.?), and vcep_materials.json contains no domain_tables entry for PTEN; therefore residue-domain or hotspot assessment cannot apply to this intronic deletion.

Rule
PTEN VCEP PM1 Moderate: located in a mutational hotspot and/or critical, well-established functional domain, including residues 90-94, 123-130, and 166-168 of NP_000305.3.
Evidence considered
  • The PTEN VCEP PM1 rule defines the critical catalytic-motif residue intervals as 90-94, 123-130, and 166-168 in NP_000305.3.
  • The variant is NM_000314.8:c.165-10_209+6del with normalized protein consequence NP_000305.3:p.?, so no residue can be compared with any approved motif or domain.
  • The case-specific vcep_materials.json has no PTEN domain_tables entry; regardless, the unresolved protein consequence prevents a residue-domain PM1 assessment.
Sources
PM3 VCEPNot applicable: the PTEN Expert Panel specification explicitly designates PM3 as not applicable for this autosomal-dominant disorder. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification, Version 3.2, explicitly designates PM3 as not applicable for PTEN. PTEN hamartoma tumor syndrome is autosomal dominant, and no recessive PM3 framework is provided by the governing specification.

VCEP rule
PTEN VCEP PM3 applicability: Not Applicable.
Evidence considered
  • The governing ClinGen PTEN Expert Panel specification Version 3.2 lists PM3 as Not Applicable.
  • The same specification identifies PTEN hamartoma tumor syndrome as autosomal dominant.
Sources
PM5 N/ANot applicable: NP_000305.3:p.? provides no amino-acid residue or BLOSUM62 substitution for the PTEN PM5 missense rule. Details ▾Hide ▴
Reasoning

The PTEN VCEP PM5 rule requires a missense change at an amino-acid residue where a different pathogenic or likely pathogenic missense change has been observed, with the interrogated variant's BLOSUM62 score no greater than the known variant. This variant is an intronic deletion with NP_000305.3:p.? and therefore has no amino-acid residue or BLOSUM62 substitution to evaluate; the PM5 candidate artifact also identified no candidates.

Rule
PTEN VCEP PM5 Moderate: missense change at an amino-acid residue where a different missense change determined pathogenic or likely pathogenic has been seen, with the interrogated variant's BLOSUM62 score equal to or less than the known variant.
Evidence considered
  • The PTEN VCEP PM5 specification is restricted to a missense change at a residue with a different pathogenic or likely pathogenic missense comparator and requires BLOSUM62 comparison.
  • The normalized protein consequence is NP_000305.3:p.? for this multi-base intronic deletion, so no residue-level missense comparison or BLOSUM62 score exists.
  • The collected PM5 candidate set contains zero same-residue candidates and marks classic PM5 as ineligible because the consequence is not missense.
Sources
cspec ↗pm5_candidates
PP2 N/ANot applicable: this is an intronic deletion with NP_000305.3:p.?, not a missense variant required by the PTEN PP2 rule. 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. NM_000314.8:c.165-10_209+6del is an intronic deletion with unresolved protein consequence NP_000305.3:p.?, not a missense variant, so PP2 does not apply.

Rule
PTEN VCEP PP2 Supporting: missense variant in a gene with a low rate of benign missense variation and where missense variants are a common mechanism of disease.
Evidence considered
  • The PTEN VCEP PP2 specification explicitly requires a missense variant.
  • The case variant is NM_000314.8:c.165-10_209+6del and its normalized protein consequence is NP_000305.3:p.?, so it is not a missense substitution for PP2 purposes.
Sources
PP3 N/ANot applicable: the c.165-10_209+6del deletion changes protein structure rather than representing a missense or qualifying intronic/splice-region variant. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning the coding interval c.165-c.209 and flanking intronic sequence, with protein consequence p.?; it is not a missense or qualifying intronic/splice-region variant for the calibrated PP3 computational path. SpliceAI was therefore not evaluated for PP3.

Rule
PP3 applies only to missense variants or qualifying intronic/splice-region variants through the applicable calibrated predictor path; protein-length-changing deletions are out of scope.
Evidence considered
  • The case variant is NM_000314.8:c.165-10_209+6del with protein consequence NP_000305.3:p.?; the deletion spans coding sequence and is outside PP3 scope.
  • The PTEN VCEP framework is the governing specification, but it provides no PP3 rule that overrides the criterion's stated missense or qualifying splice-region/intronic scope.
Sources
PP4 VCEPNot applicable: the PTEN VCEP incorporates phenotype specificity into PS4 rather than applying PP4 separately. Details ▾Hide ▴
Reasoning

The ClinGen PTEN Expert Panel specification marks PP4 as not applicable and states that phenotype specificity has been incorporated into PS4 Use 2; therefore PP4 is not applied separately for PTEN.

VCEP rule
Not applicable for PTEN; phenotype specificity has been incorporated into PS4 Use 2.
Evidence considered
  • The PTEN VCEP lists PP4 as not applicable and explicitly states that phenotype specificity is incorporated into PS4 Use 2.
Sources
PP5 VCEPNot applicable: the PTEN VCEP excludes PP5, and ClinVar has no exact-variant expert-panel pathogenic assertion. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks PP5 as not applicable and recommends that it not be used. Independently, the exact variant has no ClinVar result and therefore has no exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic assertion that could support PP5.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP states: ‘This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.’
  • ClinVar returned no result for NM_000314.8:c.165-10_209+6del, so no exact-variant expert-panel Pathogenic or Likely pathogenic classification is available.
Sources
BP1 VCEPNot applicable: the PTEN VCEP marks BP1 not applicable, and this variant is an intronic deletion rather than a missense change. Details ▾Hide ▴
Reasoning

The governing PTEN VCEP lists BP1 as not applicable. Independently, the variant is a multi-base intronic deletion with NP_000305.3:p.? rather than a missense variant, so the generic missense-oriented BP1 concept is not applicable.

VCEP rule
PTEN VCEP BP1: Not Applicable.
Evidence considered
  • The PTEN VCEP framework explicitly marks BP1 as Not Applicable.
  • The variant is NM_000314.8:c.165-10_209+6del with normalized protein consequence NP_000305.3:p.?, not a missense variant.
Sources
BP3 VCEPNot applicable: the PTEN VCEP excludes BP3, and SpliceAI maximum delta 0.996 predicts splice impact rather than a benign repeat-region change. Details ▾Hide ▴
Reasoning

The PTEN VCEP specification declares BP3 not applicable. In addition, this variant is a splice-region/exon deletion with strong predicted splice impact (SpliceAI maximum delta 0.996), not an established benign in-frame deletion confined to a repeat region.

VCEP rule
PTEN VCEP BP3 is not applicable.
Evidence considered
  • The PTEN VCEP specification lists BP3 as not applicable for PTEN.
  • SpliceAI reports a maximum delta score of 0.996, indicating predicted splice impact rather than a benign repeat-region in-frame change.
Sources
BP4 N/ANot applicable: the c.165-10_209+6del deletion changes protein structure rather than representing a missense or qualifying intronic/splice-region variant. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning the coding interval c.165-c.209 and flanking intronic sequence, with protein consequence p.?; it is not a missense or qualifying intronic/splice-region variant for the calibrated BP4 computational path. The available SpliceAI score was therefore not evaluated for BP4.

Rule
BP4 applies only to missense variants or qualifying intronic/splice-region variants through the applicable calibrated predictor path; protein-length-changing deletions are out of scope.
Evidence considered
  • The case variant is NM_000314.8:c.165-10_209+6del with protein consequence NP_000305.3:p.?; the deletion spans coding sequence and is outside BP4 scope.
  • The PTEN VCEP BP4 specification addresses splicing variants through concordant SpliceAI and VarSeak or missense variants through REVEL, neither of which applies to this protein-length-changing deletion.
Sources
BP6 VCEPNot applicable: the PTEN VCEP excludes BP6, and ClinVar has no exact-variant expert-panel benign assertion. Details ▾Hide ▴
Reasoning

The PTEN VCEP marks BP6 as not applicable and recommends that it not be used. Independently, the exact variant has no ClinVar result and therefore has no exact-variant ClinVar expert-panel Benign or Likely benign assertion that could support BP6.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PTEN VCEP states: ‘This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.’
  • ClinVar returned no result for NM_000314.8:c.165-10_209+6del, so no exact-variant expert-panel Benign or Likely benign classification is available.
Sources
BP7 N/ANot applicable: c.165-10_209+6del is a coding-spanning deletion, not a synonymous variant eligible for BP7. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning coding sequence and flanking intronic sequence, not a synonymous variant; BP7 therefore cannot be evaluated.

Rule
BP7 applies only to synonymous variants; this coding-spanning deletion is outside scope.
Evidence considered
  • The variant notation and protein consequence are NM_000314.8:c.165-10_209+6del and NP_000305.3:p.?; this is not a synonymous change.
  • Under this adjudication, BP7 is restricted to synonymous variants; this deletion is not synonymous.
Sources

Identifiers

Gene
PTEN
Transcript
NM_000314.8
Coding (HGVS c.)
NM_000314.8:c.165-10_209+6del
Protein (HGVS p.)
NP_000305.3:p.?
GRCh38
chr10:87925501 TTTTGTTTTAAGGTTTTTGGATTCAAAGCATAAAAACCATTACAAGATATACAATCTGTAAG>T
GRCh37
chr10:89685258 TTTTGTTTTAAGGTTTTTGGATTCAAAGCATAAAAACCATTACAAGATATACAATCTGTAAG>T
Location and type
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 +12 bp
0.976
SpliceAI acceptor gainat -218 bp
0.000
SpliceAI donor lossat +56 bp
0.996
SpliceAI donor gainat +401 bp
0.000
Pangolin splice lossmagnitude shown
-0.920
Pangolin splice gain
0.007

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: the c.165-10_209+6del deletion changes protein structure rather than representing a missense or qualifying intronic/splice-region variant. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning the coding interval c.165-c.209 and flanking intronic sequence, with protein consequence p.?; it is not a missense or qualifying intronic/splice-region variant for the calibrated PP3 computational path. SpliceAI was therefore not evaluated for PP3.

Rule
PP3 applies only to missense variants or qualifying intronic/splice-region variants through the applicable calibrated predictor path; protein-length-changing deletions are out of scope.
Evidence considered
  • The case variant is NM_000314.8:c.165-10_209+6del with protein consequence NP_000305.3:p.?; the deletion spans coding sequence and is outside PP3 scope.
  • The PTEN VCEP framework is the governing specification, but it provides no PP3 rule that overrides the criterion's stated missense or qualifying splice-region/intronic scope.
Sources
BP4 N/ANot applicable: the c.165-10_209+6del deletion changes protein structure rather than representing a missense or qualifying intronic/splice-region variant. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning the coding interval c.165-c.209 and flanking intronic sequence, with protein consequence p.?; it is not a missense or qualifying intronic/splice-region variant for the calibrated BP4 computational path. The available SpliceAI score was therefore not evaluated for BP4.

Rule
BP4 applies only to missense variants or qualifying intronic/splice-region variants through the applicable calibrated predictor path; protein-length-changing deletions are out of scope.
Evidence considered
  • The case variant is NM_000314.8:c.165-10_209+6del with protein consequence NP_000305.3:p.?; the deletion spans coding sequence and is outside BP4 scope.
  • The PTEN VCEP BP4 specification addresses splicing variants through concordant SpliceAI and VarSeak or missense variants through REVEL, neither of which applies to this protein-length-changing deletion.
Sources
BP7 N/ANot applicable: c.165-10_209+6del is a coding-spanning deletion, not a synonymous variant eligible for BP7. Details ▾Hide ▴
Reasoning

Not applicable: NM_000314.8:c.165-10_209+6del is a deletion spanning coding sequence and flanking intronic sequence, not a synonymous variant; BP7 therefore cannot be evaluated.

Rule
BP7 applies only to synonymous variants; this coding-spanning deletion is outside scope.
Evidence considered
  • The variant notation and protein consequence are NM_000314.8:c.165-10_209+6del and NP_000305.3:p.?; this is not a synonymous change.
  • Under this adjudication, BP7 is restricted to synonymous variants; this deletion is not synonymous.
Sources

Statement

In silico

SpliceAI predicts possible splice impact for this variant (max delta score = 1.00).

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 possible splice impact for this variant (max delta score = 1.00).

Somatic

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