0%
Print report
Variant interpretation report

POLE c.62+9C>T, p.?

NM_006231.4:c.62+9C>T NP_006222.2:p.? Unknown · intron 1 View identifiers
Classification
Uncertain significance

Variant description:

The POLE NM_006231.4:c.62+9C>T (NP_006222.2:p.?) intronic 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 POLE

POLE encodes the catalytic subunit of DNA polymerase epsilon, the enzyme that replicates the leading strand of DNA during cell division and participates in DNA repair. It contains a proofreading domain that corrects replication errors, keeping the accumulation of mutations in check. Germline mutations in POLE cause polyposis and predispose to colorectal cancer, and are also linked to a rare syndrome of facial dysmorphism, immunodeficiency, livedo, and short stature. Somatic mutations, particularly in the proofreading domain, occur in colorectal and endometrial cancers, where they drive an ultra-mutated tumor phenotype and are associated with better responses to immune checkpoint inhibitors.

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 León-Castillo et al. 2020 custom POLE framework. 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
PM2Moderate
PM2 · moderate

Met at Moderate: the highest relevant AF is 1.04e-5, below the supplied 0.0001 PM2 cutoff, with one allele and no homozygotes.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: PM2 (moderate) is the only met criterion and does not satisfy any POLE pathogenic or benign 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.

gnomAD v4.1
gnomAD v2.1
Population frequency
1 / 1,479,516 alleles

gnomAD v4.1: 1 / 1,479,516 alleles. Recorded AF 6.75897e-07. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 1.03778e-05; MAF= 0.00104%, 1/96360 alleles, homozygotes = 0) and has highest observed frequency in the Admixed American population (AF= 5.003e-05; MAF= 0.00500%, 1/19988 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI score
0.009 maximum delta

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

No listed criterion applied SpliceAI ↗
ClinVar submissions
1 reported laboratory submissions

1 Likely benign. ClinVar API review status: criteria provided, single submitter.

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 León-Castillo et al. 2020 custom POLE framework, with the data and sources behind each one.

28 criteria with recorded statuses: 1 met · 5 not met · 11 not assessed · 11 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

No variant-specific validated functional assay evidence was identified for NM_006231.4:c.62+9C>T.

The available SpliceAI result is computational evidence and cannot substitute for the functional-study requirements of PS3 or BS3.

PS3 and BS3 are therefore not_assessed rather than not_met.

PS4 is governed by the custom POLE framework and is not met because the variant is intronic, not an exact qualifying missense hotspot, and has no matching entry in the searchable PDF or Supplementary Table S1.

PP4 and BP5 are not assessed because the case lacks the patient phenotype, family-history, case-level, and alternate-molecular-basis information required by their generic definitions.

PP5 and BP6 are not met because the only exact ClinVar assertion is a single-submitter Likely benign classification with zero expert-panel submissions; ordinary laboratory submissions do not satisfy the required expert-panel evidence.

All three criteria are not applicable because PP3 and BP4 are restricted by the local POLE framework to exact missense variants, while generic BP7 is restricted to synonymous variants; this variant is intronic with predicted protein consequence p.?.

Met · 1

PM2 ModerateACMG_2015Met at Moderate: the highest relevant AF is 1.04e-5, below the supplied 0.0001 PM2 cutoff, with one allele and no homozygotes. Details ▾Hide ▴
Reasoning

PM2 is met at the requested ACMG/AMP 2015 Moderate strength under the supplied generic calibration. The variant is present only once in the relevant population datasets and at extremely low frequency: gnomAD v2.1 non-cancer exomes report AF=1.0393065746533913e-05 (1/96,218; homozygotes=0), gnomAD v2.1 all-comers exomes report AF=1.0377750103777502e-05 (1/96,360; homozygotes=0), and gnomAD v4.1 reports AF=6.758967121680333e-07 (1/1,479,516; homozygotes=0). These are all below the supplied PM2 cutoff of 0.0001; the governing records do not indicate a qualifying non-cancer or exome-only VCEP rule that would change this assessment.

Rule
PM2: Absent from controls (or at extremely low frequency if recessive) in Exome Sequencing Project, 1000 Genomes or Exome Aggregation Consortium.
Evidence considered
  • gnomAD v2.1 non-cancer exomes: AC=1, AN=96,218, AF=1.0393065746533913e-05, homozygotes=0; this is the relevant non-cancer exome figure when considering that subset.
  • gnomAD v2.1 all-comers exomes: AC=1, AN=96,360, AF=1.0377750103777502e-05, homozygotes=0.
  • gnomAD v4.1 all-comers: AC=1, AN=1,479,516, AF=6.758967121680333e-07, homozygotes=0; gnomAD v3.1 non-cancer is absent.
  • The supplied generic PM2 calibration is <=0.0001 (0.01%, ACMG/AMP 2015, PMID:25741868); each available frequency is below that cutoff.
Sources

Not met · 5 · evaluated, threshold not reached

PS4 VCEPNot met: the POLE rule requires an exact recurrent missense hotspot with combined endometrial-cancer count >=10, but this intronic c.62+9C>T variant is not listed. Details ▾Hide ▴
Reasoning

The governing POLE framework requires PS4_Supporting only for an exact POLE missense variant recurrent in both COSMIC and TCGA endometrial carcinoma cohorts, with combined EC count >=10, and in the established/pathogenic set. NM_006231.4:c.62+9C>T is intronic with protein consequence p.? and is not one of the specified missense variants. Exact searches found no c.62+9C>T, p.?, or p.? entry in PATH-250-323.pdf.txt or PATH-250-323-s002.xlsx.txt; PATH-250-323-s001.tif has no converted text and is therefore a documented review gap. No case-control counts or variant-specific PS4 paper were present; literature_pass.json has an empty ai_classified_papers list. The framework's required applicability and exact-variant conditions are not satisfied.

VCEP rule
Apply PS4_Supporting only when the exact POLE missense variant is recurrent in both the COSMIC and TCGA endometrial carcinoma cohorts in Supplementary Table S1, has a combined EC count >=10, and belongs to the established/pathogenic set highlighted by León-Castillo et al. 2020. Under the current package this supports p.P286R, p.V411L, p.A456P, and p.S297F. Do not upgrade above Supporting because the evidence source is somatic recurrence context rather than germline case-control evidence.
Evidence considered
  • PATH-250-323.pdf.txt: exact searches for c.62+9C>T, p.?, and p.? found no matching variant entry; the paper's established set is missense hotspot variants, not this intronic variant.
  • PATH-250-323-s002.xlsx.txt: exact searches for c.62+9C>T, p.?, and p.? found no matching variant entry in the recurrent COSMIC/TCGA table.
  • PATH-250-323-s001.tif: converted text unavailable; visual review remains a gap rather than evidence of absence.
  • The case normalization identifies NM_006231.4:c.62+9C>T as intronic with NP_006222.2:p.?; literature_pass.json reports ai_classified_papers as empty.
Still missing
  • PATH-250-323-s001.tif was unavailable as searchable text, so its visual content could not be checked for this variant.
  • No variant-specific case-control counts or odds ratio were available.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s001
PP5 ACMG_2015Not met: ClinVar has one single-submitter Likely benign record and zero expert-panel submissions, not an expert-panel Pathogenic or Likely pathogenic classification. Details ▾Hide ▴
Reasoning

The exact ClinVar record for NM_006231.4:c.62+9C>T is Likely benign from one clinical laboratory with criteria provided, single-submitter review status and zero expert-panel submissions. This is not an exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic classification, so PP5 is not met. The cited PMID:28492532 is a general ACMG-AMP refinement paper and is not a variant-specific expert-panel pathogenic assertion.

Rule
Reputable source recently reports variant as pathogenic, but the evidence is not available to the laboratory to perform an independent evaluation.
Evidence considered
  • ClinVar variation 240587 exactly matches NM_006231.4(POLE):c.62+9C>T and reports Likely benign, criteria provided, single submitter; expert_panel_submissions = 0.
  • The ClinVar submission audit identifies SCV001692399 as a single clinical-laboratory submission and PMID:28492532 as its citation; no expert-panel Pathogenic/Likely pathogenic assertion is present.
Sources
BA1 ACMG_2015Not met: observed allele frequencies are 6.76e-7 to 1.04e-5, far below the 0.05 BA1 threshold. Details ▾Hide ▴
Reasoning

BA1 is not met. The governing population data do not show a qualifying filtering allele frequency: gnomAD v2.1 all-comers exomes report 1/96,360 alleles (AF 1.0377750103777502e-05), and the non-cancer exome subset reports 1/96,218 (AF 1.0393065746533913e-05); gnomAD v4.1 reports 1/1,479,516 total alleles (AF 6.758967121680333e-07). The available records provide no grpmax FAF, but every observed AF is far below the 0.05 BA1 threshold, and the highest point estimate is also from 1 observed allele rather than a qualifying high-frequency signal.

Rule
BA1: Allele frequency is above 5% in Exome Sequencing Project, 1000 Genomes or Exome Aggregation Consortium.
Evidence considered
  • gnomAD v2.1 all-comers exomes: AC=1, AN=96,360, AF=1.0377750103777502e-05, homozygotes=0; no grpmax FAF was reported.
  • gnomAD v2.1 non-cancer exomes: AC=1, AN=96,218, AF=1.0393065746533913e-05, homozygotes=0; no grpmax FAF was reported.
  • gnomAD v4.1 all-comers: AC=1, AN=1,479,516, AF=6.758967121680333e-07, homozygotes=0; no grpmax FAF was reported.
  • The supplied generic BA1 calibration is >=0.05 (ACMG/AMP 2015 stand-alone benign allele frequency, PMID:25741868); all observed frequencies are below it.
Sources
BS1 ACMG_2015Not met: the highest observed AF is 1.04e-5, below the supplied 0.01 BS1 default and not greater than expected for the disorder. Details ▾Hide ▴
Reasoning

BS1 is not met. The relevant frequency evidence is far below the supplied generic 0.01 threshold: gnomAD v2.1 all-comers exomes AF=1.0377750103777502e-05 and non-cancer exomes AF=1.0393065746533913e-05, while gnomAD v4.1 AF=6.758967121680333e-07. No grpmax FAF is reported, and the data do not show an allele frequency greater than expected for the disorder. A maximum-credible-frequency calculation is unnecessary because the observed frequencies are orders of magnitude below 1%.

Rule
BS1: Allele frequency is greater than expected for the disorder.
Evidence considered
  • gnomAD v2.1 all-comers exomes: AF=1.0377750103777502e-05 from 1/96,360 alleles; no grpmax FAF was reported.
  • gnomAD v2.1 non-cancer exomes: AF=1.0393065746533913e-05 from 1/96,218 alleles; no grpmax FAF was reported.
  • gnomAD v4.1 all-comers: AF=6.758967121680333e-07 from 1/1,479,516 alleles; no grpmax FAF was reported.
  • The supplied generic BS1 calibration is >=0.01, with Whiffin et al. 2017 (PMID:28518168) identified as the preferred per-gene maximum-credible-frequency reference; these frequencies do not approach that threshold.
Sources
BP6 ACMG_2015Not met: the exact ClinVar record is single-submitter Likely benign with zero expert-panel submissions, so it does not satisfy the BP6 evidence requirement. Details ▾Hide ▴
Reasoning

The exact ClinVar record is Likely benign from one clinical laboratory with criteria provided, single-submitter status and zero expert-panel submissions. Generic BP6 requires an exact-variant ClinVar expert-panel Benign or Likely benign classification; the available record is not expert-panel evidence, so BP6 is not met.

Rule
Reputable source recently reports variant as benign, but the evidence is not available to the laboratory to perform an independent evaluation.
Evidence considered
  • ClinVar variation 240587 exactly matches NM_006231.4(POLE):c.62+9C>T and reports Likely benign, criteria provided, single submitter; expert_panel_submissions = 0.
  • The ClinVar submission audit identifies one clinical-laboratory submission, SCV001692399, and no expert-panel classification.
Sources

Not assessed · 11 · no assessment recorded

PS2 ACMG_2015Not assessed: no documented affected proband, family history, or confirmed maternity and paternity for this variant. Details ▾Hide ▴
Reasoning

No documented proband disease phenotype, family history, parental genotypes, or confirmed maternity and paternity are available to evaluate a de novo occurrence. The required PS2 elements therefore cannot be assessed.

Rule
De novo (both maternity and paternity confirmed) in a patient with the disease and no family history.
Evidence considered
  • No proband phenotype, family history, parental genotype, or maternity/paternity confirmation is documented in the available case evidence.
Still missing
  • Documented disease phenotype in the proband
  • Family history status
  • Variant testing results for both biological parents
  • Confirmation of maternity and paternity
PS3 ACMG_2015Not assessed: no variant-specific validated in vitro or in vivo functional assay result is available to establish a damaging effect. Details ▾Hide ▴
Reasoning

No variant-specific validated in vitro or in vivo functional study is documented for NM_006231.4:c.62+9C>T. The available evidence includes a SpliceAI prediction (maximum delta score 0.009), but this is computational prediction rather than a functional assay and cannot establish PS3. Therefore, the criterion remains not_assessed rather than not_met.

Rule
Well-established in vitro or in vivo functional studies supportive of a damaging effect on the gene or gene product.
Evidence considered
  • The available case evidence contains no variant-specific in vitro or in vivo functional assay result for NM_006231.4:c.62+9C>T.
  • SpliceAI reports a maximum delta score of 0.009, which is computational prediction and not functional-study evidence; it was not used to apply PS3.
Still missing
  • Variant-specific validated functional assay data demonstrating a damaging effect on POLE or its product are unavailable.
  • Assay validation, reproducibility, controls, and biological relevance for this variant cannot be evaluated.
PM3 ACMG_2015Not assessed: no affected-proband observation or parental/offspring testing establishes this variant in trans with a pathogenic variant. Details ▾Hide ▴
Reasoning

No affected-proband case observations, pathogenic partner variant, parental or offspring testing, or phase information are documented for NM_006231.4:c.62+9C>T. Therefore, the required observation of this variant in trans with a pathogenic variant cannot be assessed.

Rule
PM3: For recessive disorders, detected in trans with a pathogenic variant ... Note: This requires testing of parents (or offspring) to determine phase.
Still missing
  • Affected-proband observations involving this variant are not documented.
  • A pathogenic variant in the same gene is not documented.
  • Parental or offspring testing establishing phase is not documented.
  • The inheritance mode relevant to this case is not documented.
PM6 ACMG_2015Not assessed: no affected patient with an assumed de novo variant and incomplete parental testing is documented. Details ▾Hide ▴
Reasoning

No report documents an assumed de novo occurrence in an affected patient, and no parental testing or family-history information is provided. PM6 cannot be assessed from the available evidence.

Rule
Assumed de novo, but without confirmation of paternity and maternity.
Evidence considered
  • No assumed de novo observation, affected-patient report, or incomplete parental testing is documented in the available case evidence.
Still missing
  • Documented affected patient
  • Evidence that the variant was assumed de novo
  • Parental testing status
  • Family history status
PP1 ACMG_2015Not assessed: no affected relatives or informative variant segregation data are documented for evaluating co-segregation. Details ▾Hide ▴
Reasoning

No affected relatives, informative meioses, variant-status results, or family segregation data are documented. Consequently, co-segregation with disease in multiple affected family members cannot be assessed.

Rule
Co-segregation with disease in multiple affected family members in a gene definitively known to cause the disease.
Evidence considered
  • No affected-family-member observations, genotype results, or segregation counts are documented in the available case evidence.
Still missing
  • Number and phenotypes of affected relatives
  • Variant results for affected relatives
  • Variant results for unaffected relatives where informative
  • Informative meioses or segregation analysis
PP4 ACMGNot assessed: no patient phenotype or family-history details were available to test the PP4 specificity requirement. Details ▾Hide ▴
Reasoning

No patient phenotype, family history, or disease diagnosis specific enough to evaluate whether the phenotype is highly specific for a disease with a single genetic etiology was provided in the reviewed case evidence.

Rule
Patient’s phenotype or family history is highly specific for a disease with a single genetic etiology.
Still missing
  • Patient phenotype, diagnosis, and relevant family history are unavailable for PP4 assessment.
BS2 ACMG_2015Not assessed: no homozygotes were observed, but the single carrier is not documented as a healthy adult under a fully penetrant early-onset disease model. Details ▾Hide ▴
Reasoning

BS2 is not assessed. The population records show no homozygotes (gnomAD v2.1 all-comers: 0; non-cancer exomes: 0; gnomAD v4.1: 0), but they do show one heterozygous allele. The available evidence does not establish that the carrier was a phenotypically healthy adult, nor does it establish the relevant disorder's inheritance, early-age full penetrance, or whether a heterozygous observation is incompatible with disease. Therefore the strict BS2 healthy-adult requirement cannot be adjudicated from these records.

Rule
BS2: Observed in a healthy adult individual for a recessive (homozygous), dominant (heterozygous), or X-linked (hemizygous) disorder, with full penetrance expected at an early age.
Evidence considered
  • gnomAD v2.1 all-comers exomes: AC=1 and homozygotes=0; non-cancer exomes: AC=1 and homozygotes=0.
  • gnomAD v4.1 all-comers: AC=1 and homozygotes=0.
  • No source documents the observed carrier as a healthy adult or supplies the disease-specific inheritance and penetrance assumptions required for BS2.
Still missing
  • Documented phenotype and age of the gnomAD carrier are unavailable.
  • The governing disease inheritance model and expectation of full penetrance at an early age are not established in the supplied evidence.
Sources
BS3 ACMG_2015Not assessed: no variant-specific validated in vitro or in vivo functional assay result is available to establish a non-damaging effect. Details ▾Hide ▴
Reasoning

No variant-specific validated in vitro or in vivo functional study is documented for NM_006231.4:c.62+9C>T. The available evidence includes a SpliceAI prediction (maximum delta score 0.009), but this is computational prediction rather than a functional assay and cannot establish absence of a damaging effect. Therefore, the criterion remains not_assessed rather than not_met.

Rule
Well-established in vitro or in vivo functional studies show no damaging effect on protein function or splicing.
Evidence considered
  • The available case evidence contains no variant-specific in vitro or in vivo functional assay result for NM_006231.4:c.62+9C>T.
  • SpliceAI reports a maximum delta score of 0.009, which is computational prediction and not functional-study evidence; it was not used to apply BS3.
Still missing
  • Variant-specific validated functional assay data demonstrating no damaging effect on POLE protein function or splicing are unavailable.
  • Assay validation, reproducibility, controls, and biological relevance for this variant cannot be evaluated.
BS4 ACMG_2015Not assessed: no affected relatives lacking the variant are documented to demonstrate absence of segregation. Details ▾Hide ▴
Reasoning

No affected family members with documented absence of the variant are identified. Because neither non-segregation observations nor family structure and phenotype information are available, BS4 cannot be assessed.

Rule
Lack of segregation in affected members of a family.
Evidence considered
  • No affected relative documented as variant-negative, family structure, or non-segregation observation is available in the case evidence.
Still missing
  • Affected relatives and their clinical phenotypes
  • Variant testing results for affected relatives
  • Family structure and informative relationships
  • Assessment of phenocopies or multiple pathogenic variants
BP2 ACMG_2015Not assessed: no phase data establish this variant in trans or cis with a pathogenic variant. Details ▾Hide ▴
Reasoning

No case-level phase data document this variant in trans with a pathogenic variant in a fully penetrant dominant disorder, or in cis with a pathogenic variant in any inheritance pattern. The criterion therefore cannot be assessed.

Rule
BP2: Observed in trans with a pathogenic variant for a fully penetrant dominant gene/disorder or observed in cis with a pathogenic variant in any inheritance pattern.
Still missing
  • No parental or offspring testing establishes cis or trans phase.
  • No pathogenic partner variant is documented.
  • The inheritance mode and penetrance of the relevant disorder are not documented.
BP5 ACMGNot assessed: no affected case with an independently established alternate molecular basis for disease was available. Details ▾Hide ▴
Reasoning

No affected-patient case report or other evidence was available showing this variant in a case with an alternate molecular basis for disease. The available ClinVar record has no condition label and does not establish an alternate molecular diagnosis.

Rule
Variant found in a case with an alternate molecular basis for disease.
Evidence considered
  • The exact ClinVar record has an empty condition label and provides no alternate molecular basis for disease; no variant-specific case-control or case report evidence was identified.
Still missing
  • No case-level phenotype and alternate molecular diagnosis were available for BP5 assessment.
Sources
Not applicable · 11· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: c.62+9C>T is an intronic substitution outside the PVS1-named null-variant classes, including canonical ±1/2 splice sites, and has protein consequence p.? . Details ▾Hide ▴
Reasoning

NM_006231.4:c.62+9C>T is an intronic single-nucleotide substitution in exon 1i, with no predicted protein consequence (NP_006222.2:p.?). It is outside the PVS1 variant classes named by the governing rule: it is not a nonsense or frameshift variant, not a canonical +/−1 or 2 splice-site variant, not an initiation-codon variant, and not a single- or multi-exon deletion. The case evidence also records canonical_splice_consensus=false and apply_generic_pvs1_framework=false; therefore PVS1 is not applicable, despite the gene-level LOF gate being eligible.

Rule
Null variant (nonsense, frameshift, canonical +/−1 or 2 splice sites, initiation codon, single or multi-exon deletion) in a gene where loss of function (LOF) is a known mechanism of disease.
Evidence considered
  • NM_006231.4:c.62+9C>T is annotated as intronic in exon 1i; the predicted protein consequence is NP_006222.2:p.?.
  • The variant assessment records canonical_splice_consensus=false, consequence_class=unknown, variant_bucket=other, and apply_generic_pvs1_framework=false.
  • The gene-level PVS1 context records POLE loss of function as an eligible disease mechanism, but that gate does not convert this non-null intronic substitution into a PVS1-eligible variant.
Sources
pvs1_variant_assessmentpvs1_gene_context
PS1 N/ANot applicable: the intronic c.62+9C>T variant has protein consequence p.?, so no same-amino-acid substitution exists for comparison. Details ▾Hide ▴
Reasoning

PS1 evaluates a previously established pathogenic change producing the same amino-acid substitution. NM_006231.4:c.62+9C>T is intronic, with the normalized protein consequence NP_006222.2:p.?, so no amino-acid change can be compared and the splicing caveat applies.

Rule
Same amino acid change as a previously established pathogenic variant regardless of nucleotide change. ... Caveat: Beware of changes that impact splicing rather than at the amino acid/protein level.
Evidence considered
  • The case normalization identifies NM_006231.4:c.62+9C>T as intronic and NP_006222.2:p.?, preventing protein-level same-amino-acid comparison.
PM1 N/ANot applicable: the POLE framework restricts PM1 to exact exonuclease-domain missense substitutions, while c.62+9C>T is intronic and p.? . Details ▾Hide ▴
Reasoning

The governing León-Castillo custom POLE framework limits PM1 to listed POLE exonuclease-domain missense substitutions: five established hotspots, six exact pathogenic non-hotspot substitutions, and four exact uncertain-tier substitutions. The queried variant is intronic (c.62+9C>T; p.?) and is absent from both PATH-250-323.pdf and PATH-250-323-s002.xlsx; it is therefore outside every PM1 route. The domain_tables key in vcep_materials.json is empty, so there is no additional authoritative domain list to check. PATH-250-323-s001.tif was unavailable for conversion and remains a review gap, but its declared purpose is visual support and no protein residue can be assigned to this intronic variant.

VCEP rule
Apply PM1_Strong to the five established POLE exonuclease-domain hotspot missense variants emphasized by León-Castillo et al. 2020: p.P286R, p.V411L, p.S297F, p.A456P, and p.S459F. These are the exact hotspot substitutions repeatedly treated in the paper as pathogenic for the POLE-ultramutated phenotype in endometrial carcinoma. ... Apply PM1_Moderate to the exact non-hotspot exonuclease-domain missense variants identified in the paper as recurrent and POLE-score >=4 / classified as pathogenic in the TCGA-based analysis: p.F367S, p.L424I, p.M295R, p.P436R, p.M444K, and p.D368Y. Use this only for these exact substitutions, not all substitutions at the same codon. ... Apply PM1_Supporting to exact recurrent exonuclease-domain missense variants that the paper places in the POLE-score 3 / uncertain tier rather than the pathogenic tier: p.A465V, p.L424V, p.T278M, and p.A428T. This captures hotspot/domain context without promoting them to the paper's pathogenic set.
Evidence considered
  • vcep_materials.json lists the PM1 routes as exact missense substitutions: five established hotspots (p.P286R, p.V411L, p.S297F, p.A456P, p.S459F), six exact pathogenic non-hotspots (p.F367S, p.L424I, p.M295R, p.P436R, p.M444K, p.D368Y), and four exact uncertain-tier variants (p.A465V, p.L424V, p.T278M, p.A428T).
  • PATH-250-323.pdf was searched for c.62+9C>T, 62+9, and p.?; no entry for the queried variant was found. The paper's relevant Table 1/Table 3 lists protein-level exonuclease-domain variants, not this intronic variant.
  • PATH-250-323-s002.xlsx, Supplementary Table S1, was searched for c.62+9C>T, 62+9, and p.?; no entry for the queried variant was found. The table lists recurrent somatic protein variants and counts, including the established hotspots, but not c.62+9C>T.
  • PATH-250-323-s001.tif is declared in the VCEP index but its converted full text is unavailable; it was not assumed to be empty.
Still missing
  • PATH-250-323-s001.tif was unavailable for conversion; no visual review was possible.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s001
PM4 N/ANot applicable: c.62+9C>T is an intronic single-nucleotide substitution with protein consequence p.?, not a documented in-frame indel or stop-loss variant. Details ▾Hide ▴
Reasoning

NM_006231.4:c.62+9C>T is an intronic single-nucleotide substitution with predicted protein consequence NP_006222.2:p.?. It does not produce a documented in-frame deletion, in-frame insertion, or stop-loss change, and therefore lies outside the variant types named by PM4. No protein-length change is established for this variant.

Rule
Protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants.
Evidence considered
  • The variant is NM_006231.4:c.62+9C>T, annotated in exon 1i intronic sequence, with NP_006222.2:p.? and no documented protein-length change.
  • The variant assessment records consequence_class=unknown and variant_bucket=other, rather than an in-frame deletion, insertion, or stop-loss consequence.
Sources
pvs1_variant_assessment
PM5 N/ANot applicable: the intronic c.62+9C>T variant has protein consequence p.?, so PM5 cannot compare alternate missense changes at one residue. Details ▾Hide ▴
Reasoning

PM5 requires a novel missense change at an amino-acid residue with a previously pathogenic different missense change. This variant is intronic and has protein consequence p.?, so it has no amino-acid residue or missense change to which PM5 can apply.

Rule
Novel missense change at an amino acid residue where a different missense change determined to be pathogenic has been seen before. ... Caveat: Beware of changes that impact splicing rather than at the amino acid/protein level.
Evidence considered
  • The case normalization identifies c.62+9C>T as intronic with NP_006222.2:p.? and no residue position or alternate amino acid.
PP2 N/ANot applicable: PP2 is restricted to missense variants, whereas c.62+9C>T is intronic and produces protein consequence p.?. Details ▾Hide ▴
Reasoning

PP2 is defined for a missense variant in a gene with a low rate of benign missense variation and missense disease mechanism. NM_006231.4:c.62+9C>T is intronic with protein consequence p.?, not a missense variant, so the criterion's named variant type is not met.

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 normalization identifies the queried variant as intronic, with NP_006222.2:p.? and no missense consequence.
PP3 N/ANot applicable: the POLE PP3 rule is restricted to exact missense variants, whereas c.62+9C>T is intronic with predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

The governing POLE framework limits its custom PP3 rule to an exact missense variant appearing in Supplementary Table S2 or S3, with a REVEL class and benign-result count satisfying the specified thresholds. NM_006231.4:c.62+9C>T is intronic and has predicted protein consequence p.?, so it is outside this PP3 rule's missense scope; no PP3 evidence is assigned. The variant was not found under c.62+9C>T or p.? in PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, or PATH-250-323-s004.xlsx.

VCEP rule
Apply PP3_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'likely disease causing' (including minor spelling variants), and the number of benign in silico results is <=1. If the variant is absent from the supplementary tables, do not use this custom PP3 rule and fall back to the project's generic in-silico workflow.
Evidence considered
  • The governing custom POLE PP3 rule states: "Apply PP3_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'likely disease causing' (including minor spelling variants), and the number of benign in silico results is <=1. If the variant is absent from the supplementary tables, do not use this custom PP3 rule and fall back to the project's generic in-silico workflow."
  • Case normalization identifies NM_006231.4:c.62+9C>T as intronic with NP_006222.2:p.?, not a missense substitution.
  • PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, and PATH-250-323-s004.xlsx were searched for c.62+9C>T and p.?; no matching entry was found.
Still missing
  • No entry for c.62+9C>T or p.? was found in PATH-250-323.pdf.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s002.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s003.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s004.xlsx.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s003vcep_path_250_323_s004
BP1 N/ANot applicable: BP1 is restricted to missense variants, whereas c.62+9C>T is intronic and produces protein consequence p.?. Details ▾Hide ▴
Reasoning

BP1 is defined for a missense variant in a gene for which primarily truncating variants cause disease. NM_006231.4:c.62+9C>T is intronic with protein consequence p.?, not a missense variant, so the criterion's named variant type is not met.

Rule
Missense variant in a gene for which primarily truncating variants are known to cause disease.
Evidence considered
  • The case normalization identifies the queried variant as intronic, with NP_006222.2:p.? and no missense consequence.
BP3 N/ANot applicable: c.62+9C>T is an intronic single-nucleotide substitution, not an in-frame deletion or insertion in a repetitive region without known function. Details ▾Hide ▴
Reasoning

NM_006231.4:c.62+9C>T is an intronic single-nucleotide substitution with no documented in-frame deletion or insertion and no resulting protein-length change. It therefore does not meet the variant-type requirement for BP3, irrespective of whether a repetitive region is established.

Rule
In frame-deletions/insertions in a repetitive region without a known function.
Evidence considered
  • The variant is annotated as intronic c.62+9C>T in exon 1i, with predicted protein consequence NP_006222.2:p.?.
  • No in-frame deletion or insertion is documented; the case assessment instead records consequence_class=unknown and variant_bucket=other.
Sources
pvs1_variant_assessment
BP4 N/ANot applicable: the POLE BP4 rule is restricted to exact missense variants, whereas c.62+9C>T is intronic with predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

The governing POLE framework limits its custom BP4 rule to an exact missense variant appearing in Supplementary Table S2 or S3, with REVEL class Likely benign/Likely-benign and at least four benign in silico results. NM_006231.4:c.62+9C>T is intronic and has predicted protein consequence p.?, so it is outside this BP4 rule's missense scope; no BP4 evidence is assigned. The variant was not found under c.62+9C>T or p.? in PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, or PATH-250-323-s004.xlsx.

VCEP rule
Apply BP4_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'Likely benign' or 'Likely-benign', and the number of benign in silico results is >=4. If the variant is absent from the supplementary tables, do not use this custom BP4 rule and fall back to the project's generic in-silico workflow.
Evidence considered
  • The governing custom POLE BP4 rule states: "Apply BP4_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'Likely benign' or 'Likely-benign', and the number of benign in silico results is >=4. If the variant is absent from the supplementary tables, do not use this custom BP4 rule and fall back to the project's generic in-silico workflow."
  • Case normalization identifies NM_006231.4:c.62+9C>T as intronic with NP_006222.2:p.?, not a missense substitution.
  • PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, and PATH-250-323-s004.xlsx were searched for c.62+9C>T and p.?; no matching entry was found.
Still missing
  • No entry for c.62+9C>T or p.? was found in PATH-250-323.pdf.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s002.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s003.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s004.xlsx.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s003vcep_path_250_323_s004
BP7 N/ANot applicable: BP7 requires a synonymous variant, but c.62+9C>T is intronic and has predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants. NM_006231.4:c.62+9C>T is intronic, with predicted protein consequence p.?, and is not a synonymous coding substitution; therefore BP7 is outside its generic ACMG/AMP 2015 scope. No BP7 evidence is assessed.

Rule
A synonymous variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved.
Evidence considered
  • Case normalization identifies NM_006231.4:c.62+9C>T as an intronic variant with predicted protein consequence NP_006222.2:p.?.

Identifiers

Gene
POLE
Transcript
NM_006231.4
Coding (HGVS c.)
NM_006231.4:c.62+9C>T
Protein (HGVS p.)
NP_006222.2:p.?
GRCh38
chr12:132687245 G>A
GRCh37
chr12:133263831 G>A
Location and type
Intron 1 · unknown
ClinVar
240587

Gene diagram

Every interpreted variant in POLE, mapped onto the exon structure of NM_006231.4. Select a row to find it on the plot.

POLENM_006231.4
Fetching transcript structure from UCSC…
gnomAD v4.1 1 / 1,479,516 alleles AF 6.76e-07 · 0 homozygotes
gnomAD v2.1 1 / 96,360 alleles AF 1.04e-05 · 0 homozygotes
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 6.8e-07 · 1 / 1,479,516 alleles · 0 hom
European (non-Finnish)1 / 1,115,504 9e-07
0 alternate alleles recorded in 9 other groups: Remaining individuals, Admixed American, European (Finnish), Amish, East Asian, Middle Eastern, South Asian, Ashkenazi Jewish, African/African American.

gnomAD v2.1

AF 1e-05 · 1 / 96,360 alleles · 0 hom
Admixed American1 / 19,988 5e-05
0 alternate alleles recorded in 7 other groups: African/African American, Ashkenazi Jewish, East Asian, European (Finnish), European (non-Finnish), Remaining individuals, South Asian.

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 6.75897e-07; MAF= 0.00007%, 1/1479516 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.96456e-07; MAF= 0.00009%, 1/1115504 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 1.03778e-05; MAF= 0.00104%, 1/96360 alleles, homozygotes = 0) and has highest observed frequency in the Admixed American population (AF= 5.003e-05; MAF= 0.00500%, 1/19988 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -124 bp
0.000
SpliceAI acceptor gainat -460 bp
0.000
SpliceAI donor lossat -124 bp
0.009
SpliceAI donor gainat +2 bp
0.000
Pangolin splice lossmagnitude shown
-0.010
Pangolin splice gain
0.003

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 N/ANot applicable: the POLE PP3 rule is restricted to exact missense variants, whereas c.62+9C>T is intronic with predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

The governing POLE framework limits its custom PP3 rule to an exact missense variant appearing in Supplementary Table S2 or S3, with a REVEL class and benign-result count satisfying the specified thresholds. NM_006231.4:c.62+9C>T is intronic and has predicted protein consequence p.?, so it is outside this PP3 rule's missense scope; no PP3 evidence is assigned. The variant was not found under c.62+9C>T or p.? in PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, or PATH-250-323-s004.xlsx.

VCEP rule
Apply PP3_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'likely disease causing' (including minor spelling variants), and the number of benign in silico results is <=1. If the variant is absent from the supplementary tables, do not use this custom PP3 rule and fall back to the project's generic in-silico workflow.
Evidence considered
  • The governing custom POLE PP3 rule states: "Apply PP3_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'likely disease causing' (including minor spelling variants), and the number of benign in silico results is <=1. If the variant is absent from the supplementary tables, do not use this custom PP3 rule and fall back to the project's generic in-silico workflow."
  • Case normalization identifies NM_006231.4:c.62+9C>T as intronic with NP_006222.2:p.?, not a missense substitution.
  • PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, and PATH-250-323-s004.xlsx were searched for c.62+9C>T and p.?; no matching entry was found.
Still missing
  • No entry for c.62+9C>T or p.? was found in PATH-250-323.pdf.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s002.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s003.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s004.xlsx.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s003vcep_path_250_323_s004
BP4 N/ANot applicable: the POLE BP4 rule is restricted to exact missense variants, whereas c.62+9C>T is intronic with predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

The governing POLE framework limits its custom BP4 rule to an exact missense variant appearing in Supplementary Table S2 or S3, with REVEL class Likely benign/Likely-benign and at least four benign in silico results. NM_006231.4:c.62+9C>T is intronic and has predicted protein consequence p.?, so it is outside this BP4 rule's missense scope; no BP4 evidence is assigned. The variant was not found under c.62+9C>T or p.? in PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, or PATH-250-323-s004.xlsx.

VCEP rule
Apply BP4_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'Likely benign' or 'Likely-benign', and the number of benign in silico results is >=4. If the variant is absent from the supplementary tables, do not use this custom BP4 rule and fall back to the project's generic in-silico workflow.
Evidence considered
  • The governing custom POLE BP4 rule states: "Apply BP4_Supporting when the exact missense variant appears in Supplementary Table S2 or S3, the REVEL class is 'Likely benign' or 'Likely-benign', and the number of benign in silico results is >=4. If the variant is absent from the supplementary tables, do not use this custom BP4 rule and fall back to the project's generic in-silico workflow."
  • Case normalization identifies NM_006231.4:c.62+9C>T as intronic with NP_006222.2:p.?, not a missense substitution.
  • PATH-250-323.pdf, PATH-250-323-s002.xlsx, PATH-250-323-s003.xlsx, and PATH-250-323-s004.xlsx were searched for c.62+9C>T and p.?; no matching entry was found.
Still missing
  • No entry for c.62+9C>T or p.? was found in PATH-250-323.pdf.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s002.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s003.xlsx.
  • No entry for c.62+9C>T or p.? was found in PATH-250-323-s004.xlsx.
Sources
vcep_path_250_323vcep_path_250_323_s002vcep_path_250_323_s003vcep_path_250_323_s004
BP7 N/ANot applicable: BP7 requires a synonymous variant, but c.62+9C>T is intronic and has predicted protein consequence p.?. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants. NM_006231.4:c.62+9C>T is intronic, with predicted protein consequence p.?, and is not a synonymous coding substitution; therefore BP7 is outside its generic ACMG/AMP 2015 scope. No BP7 evidence is assessed.

Rule
A synonymous variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved.
Evidence considered
  • Case normalization identifies NM_006231.4:c.62+9C>T as an intronic variant with predicted protein consequence NP_006222.2:p.?.

Statement

In silico

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

1 paper record 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

  • Sherloc: a comprehensive refinement of the ACMG-AMP variant classification criteria.
    Nykamp K et al. · 2017
    No paper-specific finding is recorded.
    PMID 28492532 ↗

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

This variant is present in gnomAD v4.1 (AF= 6.75897e-07; MAF= 0.00007%, 1/1479516 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.96456e-07; MAF= 0.00009%, 1/1115504 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 1.03778e-05; MAF= 0.00104%, 1/96360 alleles, homozygotes = 0) and has highest observed frequency in the Admixed American population (AF= 5.003e-05; MAF= 0.00500%, 1/19988 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Likely benign (1 clinical laboratory). (ClinVarID = 240587)

In silico

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

Somatic

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