0%
Print report
Variant interpretation report

PMS2 c.1145-11C>T, p.?

NM_000535.7:c.1145-11C>T NP_000526.2:p.? Unknown · intron 10 View identifiers
Classification
Likely benign

Variant description:

No variant summary was recorded for this case.

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

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

In plain language

Gene-level background from the recorded interpretation.

About PMS2

PMS2 is a DNA mismatch-repair protein that works with MLH1 to correct replication errors, including mismatches and small insertion or deletion loops. It acts as a tumor suppressor, and inherited loss of PMS2 function can cause Lynch syndrome and constitutional mismatch repair deficiency, increasing the risk of colorectal, endometrial, ovarian, urothelial, and other cancers. Loss of PMS2 function in tumors can cause hypermutation and microsatellite instability, which may make some cancers responsive to certain immunotherapies.

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 PMS2 VCEP v2.0. 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: 2
Pathogenic criteria applied · 1
PP3Supporting
PP3 · supporting

Met at Supporting: SpliceAI max delta 0.213 meets the PMS2 VCEP non-canonical splice threshold of >=0.2.

Benign criteria applied · 2
BS1Strong
BS1 · strong

Met at Strong: gnomAD v4.1 Grpmax FAF was 0.00072958, within the VCEP BS1 interval of 0.00028 to below 0.0028.

BP7Supporting
BP7 · supporting

Met at Supporting: c.1145-11C>T is intronic at -11, within the PMS2 VCEP BP7 range of -21/+7.

Recorded classification: Likely benign

Likely Benign: BS1 (strong) plus BP7 (supporting) satisfy the ClinGen InSiGHT PMS2 Version 2.0 Rule18; PP3 is also supporting.

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
99 / 1,558,792 alleles

gnomAD v4.1: 99 / 1,558,792 alleles. Recorded AF 6.35107e-05. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.00012918; MAF= 0.01292%, 31/239976 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000883739; MAF= 0.08837%, 27/30552 alleles, homozygotes = 0); grpmax FAF= 0.0006231.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.0001085894233901618, 2/18418 alleles, homozygotes = 0).

SpliceAI score
0.213 maximum delta

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

ClinVar submissions
7 reported laboratory submissions

3 Likely benign · 3 Benign · 1 Likely Benign. ClinVar API review status: criteria provided, multiple submitters, no conflicts.

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 PMS2 VCEP v2.0, with the data and sources behind each one.

28 criteria with recorded statuses: 3 met · 4 not met · 10 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

For this consequence/LOF group, the PMS2-specific VCEP framework takes precedence: PVS1 is not met for this non-canonical intronic −11 variant, while PM4 and BP3 are explicitly not applicable.

Met · 3

PP3 SupportingMet at Supporting: SpliceAI max delta 0.213 meets the PMS2 VCEP non-canonical splice threshold of >=0.2. Details ▾Hide ▴
Reasoning

The variant is an intronic non-canonical splice-region variant, so the PMS2 VCEP splice-impact branch applies. SpliceAI reports a maximum delta score of 0.213 for NM_000535.7:c.1145-11C>T. The governing PMS2 VCEP specification assigns PP3_Supporting for a predicted splice defect at a non-canonical splice nucleotide with SpliceAI delta score >= 0.2; therefore PP3 is met at Supporting strength. The HCI-PRIORS-PMS2.txt.txt table was searched for c.1145-11C>T, p.?, and p.? and has no exact entry; that missense-only lookup is not needed because the VCEP splice rule directly governs this intronic variant.

Rule
Predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >= 0.2 as specified by the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP specification states that PP3_Supporting applies to a predicted splice defect at a non-canonical splice nucleotide when SpliceAI delta score is >= 0.2.
  • SpliceAI reports DS_AL 0.213 as the maximum delta score for NM_000535.7:c.1145-11C>T, with the predicted acceptor-loss event at a non-canonical intronic position.
  • The indexed HCI-PRIORS-PMS2.txt.txt file is a missense-only lookup table and was searched under c.1145-11C>T, p.?, and p.? without an exact entry.
Still missing
  • No exact c.1145-11C>T, p.?, or p.? entry was found in HCI-PRIORS-PMS2.txt.txt; the file is indexed for missense variants, while this variant is intronic.
Sources
cspec ↗spliceai ↗vcep_hci_priors_pms2
BS1 StrongMet at Strong: gnomAD v4.1 Grpmax FAF was 0.00072958, within the VCEP BS1 interval of 0.00028 to below 0.0028. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 VCEP specifies BS1 Strong for gnomAD v4 Grpmax filtering allele frequency >=0.00028 and <0.0028 (0.028-0.28%), provided the variant is not a founder pathogenic variant. The gnomAD v4.1 joint Grpmax FAF is 0.00072958 (0.072958%), which lies within this interval. No founder designation is present in the available evidence; BS1 Strong is met.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.00028 and < 0.0028 (0.028-0.28%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • The InSiGHT PMS2 VCEP Version 2.0 defines BS1 Strong as gnomAD v4 Grpmax filtering allele frequency >=0.00028 and <0.0028 (0.028-0.28%), excluding founder pathogenic variants.
  • gnomAD v4.1 reports joint Grpmax FAF 0.00072958 (0.072958%), based on 99/1,558,792 total alleles and 0 homozygotes; the South Asian subgroup has AF 0.000887134 (80/90,178 alleles).
Sources
BP7 SupportingMet at Supporting: c.1145-11C>T is intronic at -11, within the PMS2 VCEP BP7 range of -21/+7. Details ▾Hide ▴
Reasoning

The variant is intronic at c.1145-11, which is at or beyond -21 relative to the exon boundary and therefore falls within the PMS2 VCEP BP7 scope of intronic variants at or beyond -21/+7. The VCEP assigns BP7_Supporting to such variants; BP7 is met at Supporting strength. This criterion is applied from variant location and is not an additional use of the SpliceAI prediction.

Rule
A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic) satisfies BP7_Supporting under the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP BP7 rule applies at Supporting strength to synonymous or intronic variants at or beyond -21/+7 relative to the exonic boundary.
  • NM_000535.7:c.1145-11C>T is an intronic variant located 11 bases upstream of the exon boundary, within the specified BP7 range.
Sources

Not met · 4 · evaluated, threshold not reached

PVS1 Not met: NM_000535.7:c.1145-11C>T is an intronic −11 variant outside the PMS2 VCEP’s ±1/2 splice-site PVS1 rule. Details ▾Hide ▴
Reasoning

The applicable PMS2-specific InSiGHT VCEP Version 2.0 framework recognizes PVS1 at the canonical IVS ±1 or ±2 splice sites when exon skipping or cryptic splice use disrupts the reading frame and is predicted to undergo NMD. NM_000535.7:c.1145-11C>T is an intronic position 11 bases upstream of the exon boundary, not a canonical ±1/2 splice-site variant; its predicted protein consequence is p.? and no patient RNA assay demonstrating a null transcript or NMD-triggering aberrant transcript is available. SpliceAI reports a max delta score of 0.213, which indicates a possible non-canonical splice impact but does not establish the VCEP PVS1 requirements. Therefore PVS1 is not met under the governing PMS2 VCEP framework.

Rule
PMS2 InSiGHT VCEP Version 2.0 PVS1: canonical IVS ±1/2 splice variants qualify for full strength only when exon skipping or cryptic splice use disrupts the reading frame and is predicted to undergo NMD.
Evidence considered
  • The PMS2 InSiGHT VCEP Version 2.0 PVS1 rule specifies canonical IVS ±1/2 splice variants with reading-frame disruption and predicted NMD for the full-strength splice-site pathway.
  • VariantValidator maps NM_000535.7:c.1145-11C>T to intronic position −11 with predicted protein consequence NP_000526.2:p.? and no exon annotation for a protein-altering consequence.
  • SpliceAI scores are DS_AG 0.01, DS_AL 0.213, DS_DG 0.018, and DS_DL 0.003; max delta is 0.213, indicating possible splice impact but not proving a PVS1-qualifying null transcript or NMD outcome.
Still missing
  • No patient-derived RNA evidence establishes aberrant splicing that produces a premature stop codon or qualifying in-frame deletion.
  • No demonstrated exon-skipping or cryptic-splice outcome establishes reading-frame disruption and NMD.
  • Variant-level exon annotation and protein consequence remain unresolved beyond p.?
Sources
PM2 Not met: gnomAD v4.1 total AF was 0.0000635107, exceeding the VCEP PM2 threshold of less than 0.00002. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 VCEP specifies PM2 Supporting when the allele frequency is <0.00002 (<1 in 50,000 alleles) in gnomAD v4. The gnomAD v4.1 all-comers total AF is 0.0000635107 (99/1,558,792 alleles), above the VCEP threshold, and the non-cancer datasets also do not establish absence: v2.1 non-cancer exomes AF 0.000136764 (31/226,668) and v3.1 non-cancer genomes AF 0.0000338094 (5/147,888). Therefore PM2 is not met.

Rule
Absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4 dataset.
Evidence considered
  • The InSiGHT PMS2 VCEP Version 2.0 defines PM2 Supporting as absent or allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
  • gnomAD v4.1 all-comers reports AF 0.0000635107 (99/1,558,792 alleles), with 0 homozygotes; its highest population AF is South Asian at 0.000887134 (80/90,178 alleles).
  • For the available non-cancer subsets, gnomAD v2.1 non-cancer exomes reports AF 0.000136764 (31/226,668 alleles; homozygotes 0), and gnomAD v3.1 non-cancer genomes reports AF 0.0000338094 (5/147,888 alleles; homozygotes 0).
Sources
BA1 Not met: gnomAD v4.1 Grpmax FAF was 0.00072958, below the VCEP BA1 threshold of 0.0028. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 VCEP specifies BA1 at gnomAD v4 Grpmax filtering allele frequency >=0.0028 (0.28%), with exclusion of a founder pathogenic variant. The gnomAD v4.1 joint Grpmax FAF is 0.00072958 (0.072958%), below 0.0028; therefore BA1 is not met. No founder designation is needed to change this frequency-based conclusion.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.0028 (0.28%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • The InSiGHT PMS2 VCEP Version 2.0 defines BA1 as gnomAD v4 Grpmax filtering allele frequency >=0.0028 (0.28%) and excludes founder pathogenic variants.
  • gnomAD v4.1 reports joint Grpmax FAF 0.00072958 (0.072958%), with the highest observed population frequency in South Asian individuals at 0.000887134 (80/90,178 alleles; homozygotes 0).
Sources
BP4 Not met: SpliceAI max delta 0.213 exceeds the PMS2 VCEP no-impact threshold of <=0.1. Details ▾Hide ▴
Reasoning

The variant is an intronic non-canonical splice-region variant, for which the PMS2 VCEP BP4 rule requires SpliceAI to predict no splicing impact with delta score <= 0.1. The observed SpliceAI maximum delta score is 0.213, which exceeds that cutoff; therefore BP4 is not met. The HCI-PRIORS-PMS2.txt.txt table was searched for c.1145-11C>T, p.?, and p.? and has no exact entry; it is indexed for missense variants and does not override the applicable intronic SpliceAI rule.

Rule
For intronic and synonymous variants, SpliceAI predicts no splicing impact with delta score <= 0.1 as specified by the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP specification requires SpliceAI delta score <= 0.1 for BP4 in intronic and synonymous variants.
  • SpliceAI reports a maximum delta score of 0.213 for NM_000535.7:c.1145-11C>T, above the VCEP BP4 cutoff.
  • The indexed HCI-PRIORS-PMS2.txt.txt file is a missense-only lookup table and was searched under c.1145-11C>T, p.?, and p.? without an exact entry.
Still missing
  • No exact c.1145-11C>T, p.?, or p.? entry was found in HCI-PRIORS-PMS2.txt.txt; the file is indexed for missense variants, while this variant is intronic.
Sources
cspec ↗spliceai ↗vcep_hci_priors_pms2

Not assessed · 10 · no assessment recorded

PS1 Not assessed: SpliceAI max delta is 0.213, but no qualifying pathogenic comparator at the same non-canonical splice nucleotide is documented. Details ▾Hide ▴
Reasoning

The PMS2 VCEP permits PS1 for a variant affecting the same non-canonical splice nucleotide as a confirmed Pathogenic or Likely Pathogenic splice variant, provided the new variant has a similar or worse SpliceAI prediction. This variant is intronic, has an unknown protein consequence (NP_000526.2:p.?), and has SpliceAI maximum delta 0.213, but the available evidence does not document a qualifying comparator at the same splice nucleotide or its SpliceAI score. Therefore PS1 cannot be adjudicated from the available evidence.

Rule
A predicted missense substitution that encodes the same amino acid change with a different underlying nucleotide change previously established by this VCEP as Pathogenic (not a predicted or confirmed splice defect). OR variants affecting the same non-canonical splice nucleotide as a confirmed Pathogenic splice variant with similar or worse splicing in silico prediction using SpliceAI. The analogous Likely Pathogenic rule requires PM2_supporting for the missense pathway.
Evidence considered
  • The PMS2 VCEP PS1 rule includes variants affecting the same non-canonical splice nucleotide as a confirmed Pathogenic splice variant with similar or worse SpliceAI prediction, or the analogous Likely Pathogenic rule.
  • The case variant is NM_000535.7:c.1145-11C>T with protein consequence NP_000526.2:p.? and SpliceAI maximum delta score 0.213.
  • No qualifying same-nucleotide Pathogenic or Likely Pathogenic comparator and comparator SpliceAI score are documented in the available case evidence.
Still missing
  • A confirmed Pathogenic or Likely Pathogenic comparator affecting the same non-canonical splice nucleotide, with its SpliceAI prediction, is needed.
Sources
PS2 Not assessed: no proband-level de novo observation, parental confirmation, tumor consistency, or de novo point total is documented. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP specifies PS2 using de novo points: 2 points per proband when both maternity and paternity are confirmed and the proband has an LS-spectrum tumor with MMR-deficient tumor data consistent with the affected gene; 1 point when both parents are confirmed but tumor MSI/IHC/methylation data are unavailable; and 0.5 points for assumed de novo status with maternity and/or paternity unconfirmed. The available case evidence contains no proband-level de novo observation, parental testing results, maternity or paternity confirmation, tumor phenotype data, or de novo point calculation for NM_000535.7:c.1145-11C>T, so PS2 cannot be assigned.

Rule
Proband with a de novo variant with both maternity and paternity confirmed in a case with MMR deficient LS spectrum tumor consistent with the affected gene: 2 points per proband; or both parents confirmed with an LS-spectrum tumor but no tumor MSI/IHC/methylation data: 1 point per proband; or assumed de novo with maternity and/or paternity unconfirmed and an LS-spectrum tumor: 0.5 points per proband. PS2 Very Strong requires >=4 de novo points, Strong 2-3.5, Moderate 1-1.5, Supporting 0.5.
Evidence considered
  • The PMS2 InSiGHT VCEP PS2 rule assigns 2 de novo points per proband with confirmed maternity and paternity plus an MMR-deficient LS-spectrum tumor consistent with the affected gene, 1 point with confirmed parents but no tumor data, and 0.5 points when maternity and/or paternity are unconfirmed.
  • No proband-level de novo, parental-testing, tumor-consistency, or de novo-point evidence was present for this variant.
Still missing
  • Document the proband's LS-spectrum phenotype and tumor MSI/IHC/methylation findings, if available.
  • Document testing of both biological parents and whether maternity and paternity are confirmed.
  • Calculate the applicable VCEP de novo points per proband and across probands.
Sources
PS3 Not assessed: no variant-specific functional or RNA assay is reported; SpliceAI max delta 0.213 is predictive, not functional evidence. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 Version 2.0 specification requires calibrated functional odds, an MMR function defect established through the functional-assay flowchart, or qualifying monoallelic-expression evidence for PS3. No variant-specific protein-function assay, MMR activity assay, or RNA assay is reported for NM_000535.7:c.1145-11C>T. SpliceAI predicts a possible splice effect with a maximum delta score of 0.213, but this is computational prediction rather than functional evidence and cannot satisfy PS3. The available literature extraction contains only general ACMG guidance and no assay result for this variant.

Rule
Calibrated functional assays with functional odds for pathogenicity >4.3 and <= 18.7 OR MMR function defect following functional assay flowchart OR variants with monoallelic expression: complete loss of expression (<10% of wild-type in cDNA without puromycin) of the variant allele. Full-length transcript should be analysed with and without NMD block.
Evidence considered
  • The ClinGen InSiGHT PMS2 Version 2.0 rule permits PS3 Strong only for calibrated functional assays with functional odds for pathogenicity >18.7, PS3 Moderate for odds >4.3 and <=18.7 or a qualifying MMR function defect/complete loss of variant-allele expression, and PS3 Supporting for odds >2.08 and <=4.3.
  • The PMS2 functional assay flowchart directs variants with predicted splicing impact to splicing assays; no variant-specific splicing assay result is present.
  • SpliceAI reports DS_AL 0.213 as the maximum delta score, which is a computational splice-impact prediction and not an experimental functional assay.
  • The extracted literature includes general guidance that splice-site impact requires RNA or protein confirmation, but does not report a PMS2 c.1145-11C>T assay result.
Still missing
  • Variant-specific RNA splicing analysis with appropriate controls and nonsense-mediated-decay considerations is unavailable.
  • Variant-specific calibrated protein or MMR activity assay with assay controls and a validated functional odds estimate is unavailable.
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchartspliceai ↗PMID:25741868 ↗
PM3 Not assessed: no affected-proband CMMRD observation or pathogenic PMS2 partner with documented phase is available to assign the VCEP's PM3 points. Details ▾Hide ▴
Reasoning

The PMS2 VCEP defines PM3 for co-occurrence of the evaluated variant with a known pathogenic or likely pathogenic PMS2 variant in a patient with clinical features consistent with CMMRD. A pathogenic/likely pathogenic partner variant, affected-proband observation, and phase are not documented for this case, so no PM3 points can be assigned; the VCEP point thresholds are 0.5 for Supporting, 1–1.5 for Moderate, 2–3.5 for Strong, and ≥4 for Very Strong.

Rule
Co-occurrence with a known pathogenic/likely pathogenic sequence variant in the same gene in a patient with clinical features consistent with CMMRD; pathogenic/likely pathogenic in trans = 1.0 point, phase unknown = 0.5 points; sum all cases. Strength: Supporting = 0.5 points, Moderate = 1–1.5 points, Strong = 2–3.5 points, Very Strong = ≥4 points.
Evidence considered
  • The PMS2 VCEP PM3 rule requires co-occurrence with a known pathogenic or likely pathogenic variant in the same gene in a patient with clinical features consistent with CMMRD.
  • The PMS2 VCEP assigns 1.0 point for a pathogenic/likely pathogenic variant in trans and 0.5 points when phase is unknown; no qualifying partner observation or phase information is documented here.
Still missing
  • Affected-proband clinical features consistent with CMMRD are not documented.
  • A known pathogenic or likely pathogenic PMS2 partner variant is not documented.
  • Phase of the evaluated variant relative to any partner variant is not documented.
Sources
PP1 Not assessed: no informative pedigree, meioses, affected-relative testing, or combined Bayes Likelihood Ratio is documented. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP requires co-segregation evidence evaluated with a combined Bayes Likelihood Ratio: greater than 18.7 for PP1 Strong in at least two families, greater than 4.3 through 18.7 for PP1 Moderate, and greater than 2.08 through 4.3 for PP1 Supporting. No affected-relative genotypes, unaffected-relative genotypes, pedigree structure, meioses, family count, or calculated Bayes Likelihood Ratio is documented for this variant, so PP1 cannot be assigned.

Rule
Co-segregation with disease in pedigree(s) with a combined Bayes Likelihood Ratio >18.7 in >=2 families: Strong; >4.3 and <=18.7: Moderate; >2.08 and <=4.3: Supporting.
Evidence considered
  • The PMS2 InSiGHT VCEP PP1 thresholds are combined Bayes Likelihood Ratio >18.7 for Strong, >4.3 to <=18.7 for Moderate, and >2.08 to <=4.3 for Supporting.
  • No segregation pedigree, relative testing, informative meiosis count, family count, or Bayes Likelihood Ratio was present for this variant.
Still missing
  • Provide pedigrees identifying affected and unaffected relatives and their phenotype status.
  • Provide variant testing results for informative relatives and the number of informative meioses.
  • Calculate the combined Bayes Likelihood Ratio across families using the VCEP-recommended segregation method.
Sources
PP4 Not assessed: no patient-specific MSI, tumor-genome, or PMS2 IHC result is available to satisfy the PP4 tumor-evidence rule. Details ▾Hide ▴
Reasoning

PP4 is applicable under the InSiGHT PMS2 specification, requiring one or more CRC/endometrial MSI-H tumors or tumor-genome evidence and/or MMR protein loss consistent with the variant location. The case evidence contains no patient-specific tumor MSI, tumor-genome, or PMS2 IHC result, so no PP4 strength can be assigned.

Rule
Supporting: 1 CRC/endometrial MSI-H tumor using a standard panel of 5-10 markers or tumor genome and/or loss of MMR protein expression consistent with the variant location; Moderate: 2 independent tumors; Strong: at least 3 independent tumors in at least 2 families. MSI-H tumor with inconsistent protein expression does not meet PP4.
Evidence considered
  • The governing InSiGHT PMS2 Version 2.0 PP4 rule requires one CRC/endometrial MSI-H tumor with a standard marker panel or tumor genome and/or MMR protein loss consistent with the variant location; the available case evidence does not report such patient-specific findings.
Still missing
  • Patient-specific tumor MSI result using the specified marker panel or tumor genome result
  • Patient-specific MMR immunohistochemistry result with loss consistent with PMS2 variant location
  • Tumor independence and family information if multiple tumors are used
Sources
BS2 Not assessed: no documented in-trans pathogenic PMS2 variant, phase confirmation, qualifying age, or CMMRD assessment is available for the BS2 rule. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 VCEP restricts BS2 Strong to documented in-trans co-occurrence with a known pathogenic sequence variant in the same gene in an appropriately aged Lynch-syndrome cancer patient without clinical manifestations of CMMRD, with phase confirmation by parental or offspring testing. The available case evidence contains no such patient-level co-occurrence, phase, age, or CMMRD assessment, so BS2 cannot be evaluated.

Rule
Co-occurrence in trans with a known pathogenic sequence variant in the same gene in a patient with colorectal cancer after age 45 (or other LS cancer above the median age of onset for that cancer in LS), and who has no previous or current evidence of clinical manifestations of CMMRD; confirmation of phase requires testing of parents or offspring.
Evidence considered
  • The InSiGHT PMS2 VCEP Version 2.0 requires BS2 Strong for in-trans co-occurrence with a known pathogenic sequence variant in PMS2 in a qualifying patient, plus phase confirmation by parents or offspring and no clinical manifestations of CMMRD.
  • The available case evidence provides population allele counts and frequencies but does not provide a qualifying patient-level co-occurrence or the required phase, age, and CMMRD information.
Still missing
  • A qualifying patient-level co-occurrence with a known pathogenic PMS2 variant is not documented.
  • Phase confirmation, cancer age, and absence of CMMRD manifestations are not documented.
Sources
BS3 Not assessed: no variant-specific benign functional or RNA result is reported; SpliceAI max delta 0.213 cannot establish proficient function. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 Version 2.0 specification requires calibrated functional odds <=0.05 for BS3 Strong, calibrated odds >0.05 and <=0.48 for BS3 Supporting, or variant-specific proficient protein and mRNA-based laboratory results under the MMR functional assay flowchart. No variant-specific benign/proficient protein assay, MMR activity assay, or RNA assay is reported for NM_000535.7:c.1145-11C>T. The SpliceAI maximum delta score of 0.213 is a computational prediction and cannot establish normal splicing or proficient function. Therefore BS3 cannot be assigned.

Rule
Calibrated functional assays with functional odds for pathogenicity <=0.05 OR synonymous substitutions and intronic variants with no associated mRNA aberration as determined by laboratory assays conducted with nonsense-mediated-decay inhibition. Whenever abnormal transcripts are identified at similar levels in controls they will be considered naturally occurring isoforms and not mRNA aberrations. BS3 Supporting: calibrated functional assays with functional odds for pathogenicity >0.05 and <=0.48 OR variant-specific proficient function in protein and mRNA-based lab assays as per MMR functional assay flowchart.
Evidence considered
  • The ClinGen InSiGHT PMS2 Version 2.0 rule permits BS3 Strong for calibrated functional odds for pathogenicity <=0.05 or qualifying normal mRNA findings, and BS3 Supporting for calibrated odds >0.05 and <=0.48 or variant-specific proficient protein and mRNA-based assays.
  • The PMS2 functional assay flowchart requires variant-specific assay evidence to classify proficient versus deficient MMR function; no such result is available for this variant.
  • SpliceAI reports DS_AL 0.213 as the maximum delta score, which cannot establish normal splicing or proficient function because it is not an experimental assay.
  • The extracted literature provides only general methodological guidance and no variant-specific benign functional result.
Still missing
  • Variant-specific RNA assay demonstrating no mRNA aberration, including appropriate nonsense-mediated-decay inhibition where applicable, is unavailable.
  • Variant-specific protein-function or MMR activity assay demonstrating proficient function with validated controls is unavailable.
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchartspliceai ↗PMID:25741868 ↗
BS4 Not assessed: no documented non-segregating affected relatives, informative meioses, or combined Bayes Likelihood Ratio is available. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP requires lack of co-segregation to be evaluated using a combined Bayes Likelihood Ratio, with BS4 Strong below 0.05 and BS4 Supporting greater than 0.05 through 0.48. No affected-family-member non-segregation observations, phenotype assessments, informative meioses, pedigree data, or combined Bayes Likelihood Ratio is documented for this variant. Therefore, BS4 cannot be assigned; absence of segregation data is not evidence of non-segregation.

Rule
Lack of co-segregation with disease in pedigree(s) with a combined Bayes Likelihood Ratio <0.05: Strong; >0.05 and <=0.48: Supporting.
Evidence considered
  • The PMS2 InSiGHT VCEP BS4 thresholds are combined Bayes Likelihood Ratio <0.05 for Strong and >0.05 to <=0.48 for Supporting.
  • No affected-relative non-segregation, informative meiosis, pedigree, or Bayes Likelihood Ratio evidence was present for this variant; missing segregation data were not treated as non-segregation.
Still missing
  • Provide pedigrees and phenotype assessments for affected relatives tested for the variant.
  • Provide variant results for informative affected and unaffected relatives and the number of informative meioses.
  • Calculate the combined Bayes Likelihood Ratio for lack of co-segregation across pedigrees.
Sources
BP5 Not assessed: no tumor MSS/IHC, BRAF V600E, or MLH1 methylation findings are available for the BP5 alternate-basis rule. Details ▾Hide ▴
Reasoning

BP5 is applicable under the InSiGHT PMS2 specification when there are alternate-molecular-basis findings: at least 2 tumors for supporting or at least 4 tumors for strong evidence, or the specified BRAF V600E/MLH1 methylation findings. The case evidence does not report tumor MSS/IHC, inconsistent MMR loss, BRAF V600E, or MLH1 methylation results, so BP5 cannot be assigned.

Rule
Supporting: 2 or 3 tumors with MSS and/or no loss of MMR protein expression and/or inconsistent MMR protein loss, or 1 specified BRAF V600E/MLH1 methylation finding; Strong: at least 4 tumors or at least 2 specified BRAF V600E/MLH1 methylation findings.
Evidence considered
  • The governing InSiGHT PMS2 Version 2.0 BP5 rule requires 2 or 3 qualifying tumors for supporting evidence or at least 4 qualifying tumors for strong evidence, or the specified BRAF V600E/MLH1 methylation finding; none is reported in the available case evidence.
Still missing
  • Patient-specific tumor MSS and MMR-protein-expression results
  • Patient-specific BRAF V600E or MLH1 methylation result where applicable
  • Number and independence of qualifying tumors
Sources
Not applicable · 11· recorded as not applicable Show reasons ▾Hide reasons ▴
PS4 VCEPNot applicable: the PMS2 VCEP explicitly excludes PS4 because tumor IHC evidence is evaluated through PP4 instead. Details ▾Hide ▴
Reasoning

The InSiGHT PMS2 Version 2.0 specification explicitly states that PS4 is not applicable because tumor IHC data are available for variant classification through PP4; therefore PS4 proband-counting or case-control evidence is not used for this VCEP.

VCEP rule
PS4 is not applicable for this VCEP because tumor IHC data are used for classification through PP4.
Evidence considered
  • The governing InSiGHT PMS2 Version 2.0 rule states: "Due to the availability of tumor IHC data for variant classification (see PP4), PS4 has not been utilized for MMR variant classification using proband counting."
Sources
PM1 VCEPNot applicable: the PMS2 VCEP explicitly marks PM1 as not applicable, and no approved PMS2 domain-table entry is supplied. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP specification explicitly marks PM1 as Not Applicable. The vcep_materials domain_tables object contains no PMS2 entry, so there is no authoritative approved critical-domain interval to apply to this variant.

VCEP rule
Not Applicable
Evidence considered
  • The governing PMS2 VCEP framework lists PM1 as Not Applicable.
  • The supplied vcep_materials domain_tables object is empty, so no approved PMS2 critical functional domain is available for residue assessment.
Sources
PM4 VCEPNot applicable: the PMS2 VCEP explicitly excludes PM4, and this intronic variant has no established in-frame protein length change. Details ▾Hide ▴
Reasoning

The governing PMS2 InSiGHT VCEP Version 2.0 explicitly designates PM4 as not applicable. This variant is intronic, has no established in-frame protein length change, and is annotated with predicted protein consequence p.?, so there is no qualifying protein length change to evaluate under PM4.

VCEP rule
PMS2 InSiGHT VCEP Version 2.0: PM4 is not applicable.
Evidence considered
  • The PMS2 InSiGHT VCEP Version 2.0 lists PM4 as Not Applicable.
  • The normalized consequence is intronic NM_000535.7:c.1145-11C>T with predicted protein consequence NP_000526.2:p.?, not an established in-frame deletion or insertion.
Sources
PM5 N/ANot applicable: this is an intronic variant with protein consequence p.? rather than a missense change eligible for same-residue PM5. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP PM5 rule is restricted to a missense change at an amino-acid residue with a different VCEP-classified missense change. This variant is intronic with an unknown protein consequence (NP_000526.2:p.?), and the VCEP PM5 comparator search found no eligible candidate.

Rule
Missense change at an amino acid residue where a different missense change was classified by this VCEP as Pathogenic or Likely Pathogenic on the protein level and not due to aberrant splicing; PM5 requires PP3 supporting for the missense change.
Evidence considered
  • The PMS2 VCEP PM5 rule requires a missense change at an amino-acid residue with a different VCEP-classified missense change and excludes evidence due to aberrant splicing.
  • The normalized consequence is NP_000526.2:p.? and the collected PM5 artifact identifies the consequence class as unknown, not missense, with zero same-residue candidates.
Sources
cspec ↗pm5_candidates
PM6 VCEPNot applicable: the PMS2 VCEP incorporates assumed de novo evidence into PS2 at 0.5 points rather than using PM6. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP explicitly marks PM6 as not applicable. Its assumed-de novo scenario is incorporated into the VCEP's PS2 point framework at 0.5 points per proband when maternity and/or paternity are unconfirmed, rather than being assigned as PM6.

VCEP rule
PM6 is not applicable under the PMS2 InSiGHT VCEP; assumed de novo evidence with unconfirmed maternity and/or paternity is evaluated under PS2 at 0.5 de novo points per proband.
Evidence considered
  • The PMS2 InSiGHT VCEP labels PM6 not applicable and directs assumed de novo cases with unconfirmed maternity and/or paternity to the PS2 0.5-point category.
Sources
PP2 VCEPNot applicable: the PMS2 VCEP explicitly marks PP2 as not applicable, and this variant is intronic rather than missense. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP specification explicitly marks PP2 as Not Applicable; the variant is also intronic rather than a missense variant for which generic PP2 would ordinarily be considered.

VCEP rule
Not Applicable
Evidence considered
  • The governing PMS2 VCEP framework lists PP2 as Not Applicable.
  • The normalized consequence is NP_000526.2:p.? for the intronic variant NM_000535.7:c.1145-11C>T.
Sources
PP5 VCEPNot applicable: the PMS2 VCEP excludes PP5, and ClinVar reports zero exact-variant expert-panel submissions. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 Version 2.0 specification marks PP5 as not applicable. ClinVar contains only ordinary single-submitter classifications for the exact variant and reports zero expert-panel submissions; these assertions cannot trigger PP5 under the required expert-panel-only rule.

VCEP rule
PP5 is not applicable for this VCEP; in any event, PP5 may be applied only to an exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic classification, not to ordinary laboratory submissions or aggregate labels.
Evidence considered
  • The InSiGHT PMS2 Version 2.0 specification states that PP5 is not applicable for this VCEP.
  • The exact ClinVar record for NM_000535.7:c.1145-11C>T has eight submissions, all single-submitter records, with zero expert-panel submissions; the reported benign/likely benign labels therefore cannot trigger PP5.
Sources
BP1 VCEPNot applicable: the PMS2 VCEP explicitly marks BP1 as not applicable, and this variant is intronic rather than missense. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP specification explicitly marks BP1 as Not Applicable; the variant is intronic rather than a missense variant for which generic BP1 would ordinarily be considered.

VCEP rule
Not Applicable
Evidence considered
  • The governing PMS2 VCEP framework lists BP1 as Not Applicable.
  • The normalized consequence is NP_000526.2:p.? for the intronic variant NM_000535.7:c.1145-11C>T.
Sources
BP2 VCEPNot applicable: the PMS2 VCEP explicitly designates BP2 as not applicable for this gene-specific framework. Details ▾Hide ▴
Reasoning

The applicable ClinGen InSiGHT PMS2 VCEP specification explicitly designates BP2 as Not Applicable. Therefore, BP2 is not evaluated for this PMS2 variant, regardless of whether any possible cis/trans co-occurrence information is available.

VCEP rule
Not Applicable
Evidence considered
  • The ClinGen InSiGHT PMS2 Version 2.0 specification lists BP2 as Not Applicable.
Sources
BP3 VCEPNot applicable: the PMS2 VCEP excludes BP3, and this is an intronic variant rather than an in-frame repeat-region insertion or deletion. Details ▾Hide ▴
Reasoning

The governing PMS2 InSiGHT VCEP Version 2.0 explicitly designates BP3 as not applicable and states that in-frame deletions or insertions in repetitive regions without a known function are not used. This variant is intronic rather than an in-frame deletion or insertion, so BP3 cannot be applied.

VCEP rule
PMS2 InSiGHT VCEP Version 2.0: BP3 is not applicable; the generic in-frame repeat-region rule is not used.
Evidence considered
  • The PMS2 InSiGHT VCEP Version 2.0 lists BP3 as Not Applicable and instructs that the in-frame repeat-region rule is not used.
  • VariantValidator annotates NM_000535.7:c.1145-11C>T as an intronic variant with predicted protein consequence NP_000526.2:p.?, not an in-frame insertion or deletion.
Sources
BP6 VCEPNot applicable: the PMS2 VCEP excludes BP6, and ClinVar reports zero exact-variant expert-panel submissions. Details ▾Hide ▴
Reasoning

The governing InSiGHT PMS2 Version 2.0 specification marks BP6 as not applicable and states that it is not for use. ClinVar reports zero exact-variant expert-panel submissions; ordinary laboratory benign or likely benign assertions and aggregate labels cannot trigger BP6 under the required expert-panel-only rule.

VCEP rule
BP6 is not applicable for this VCEP; in any event, BP6 may be applied only to an exact-variant ClinVar expert-panel Benign or Likely benign classification, not to ordinary laboratory submissions or aggregate labels.
Evidence considered
  • The InSiGHT PMS2 Version 2.0 specification states that BP6 is not applicable and is not for use.
  • The exact ClinVar record for NM_000535.7:c.1145-11C>T has zero expert-panel submissions; its ordinary single-submitter benign/likely benign assertions cannot trigger BP6.
Sources

Identifiers

Gene
PMS2
Transcript
NM_000535.7
Coding (HGVS c.)
NM_000535.7:c.1145-11C>T
Protein (HGVS p.)
NP_000526.2:p.?
GRCh38
chr7:5987631 G>A
GRCh37
chr7:6027262 G>A
Location and type
Intron 10 · unknown
ClinVar
492248

Gene diagram

Every interpreted variant in PMS2, mapped onto the exon structure of NM_000535.7. Select a row to find it on the plot.

PMS2NM_000535.7
Fetching transcript structure from UCSC…
gnomAD v4.1 99 / 1,558,792 alleles AF 6.35e-05 · 0 homozygotes · FAF 0.00073
gnomAD v2.1 31 / 239,976 alleles AF 0.000129 · 0 homozygotes · FAF 0.000623
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 6.4e-05 · 99 / 1,558,792 alleles · 0 hom · FAF 0.00073
South Asian80 / 90,178 0.00089
African/African American5 / 74,106 6.7e-05
Admixed American2 / 59,878 3.3e-05
Remaining individuals2 / 60,956 3.3e-05
European (non-Finnish)10 / 1,136,346 8.8e-06
0 alternate alleles recorded in 5 other groups: European (Finnish), Amish, East Asian, Middle Eastern, Ashkenazi Jewish.

gnomAD v2.1

AF 0.00013 · 31 / 239,976 alleles · 0 hom · FAF 0.00062
South Asian27 / 30,552 0.00088
African/African American1 / 14,498 6.9e-05
Admixed American1 / 34,426 2.9e-05
European (non-Finnish)2 / 110,000 1.8e-05
0 alternate alleles recorded in 4 other groups: Ashkenazi Jewish, East Asian, European (Finnish), Remaining individuals.

gnomAD-Canada

AF not recorded · ? / ? alleles

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 6.35107e-05; MAF= 0.00635%, 99/1558792 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000887134; MAF= 0.08871%, 80/90178 alleles, homozygotes = 0); grpmax FAF= 0.00072958.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.00012918; MAF= 0.01292%, 31/239976 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000883739; MAF= 0.08837%, 27/30552 alleles, homozygotes = 0); grpmax FAF= 0.0006231.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.0001085894233901618, 2/18418 alleles, homozygotes = 0).

Open the gnomAD-Canada detail page →

SpliceAI and Pangolin

SpliceAI acceptor lossat +28 bp
0.213
SpliceAI acceptor gainat -11 bp
0.010
SpliceAI donor lossat -10 bp
0.003
SpliceAI donor gainat -220 bp
0.018
Pangolin splice lossmagnitude shown
-0.156
Pangolin splice gain
0.088

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

PP3 SupportingMet at Supporting: SpliceAI max delta 0.213 meets the PMS2 VCEP non-canonical splice threshold of >=0.2. Details ▾Hide ▴
Reasoning

The variant is an intronic non-canonical splice-region variant, so the PMS2 VCEP splice-impact branch applies. SpliceAI reports a maximum delta score of 0.213 for NM_000535.7:c.1145-11C>T. The governing PMS2 VCEP specification assigns PP3_Supporting for a predicted splice defect at a non-canonical splice nucleotide with SpliceAI delta score >= 0.2; therefore PP3 is met at Supporting strength. The HCI-PRIORS-PMS2.txt.txt table was searched for c.1145-11C>T, p.?, and p.? and has no exact entry; that missense-only lookup is not needed because the VCEP splice rule directly governs this intronic variant.

Rule
Predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >= 0.2 as specified by the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP specification states that PP3_Supporting applies to a predicted splice defect at a non-canonical splice nucleotide when SpliceAI delta score is >= 0.2.
  • SpliceAI reports DS_AL 0.213 as the maximum delta score for NM_000535.7:c.1145-11C>T, with the predicted acceptor-loss event at a non-canonical intronic position.
  • The indexed HCI-PRIORS-PMS2.txt.txt file is a missense-only lookup table and was searched under c.1145-11C>T, p.?, and p.? without an exact entry.
Still missing
  • No exact c.1145-11C>T, p.?, or p.? entry was found in HCI-PRIORS-PMS2.txt.txt; the file is indexed for missense variants, while this variant is intronic.
Sources
cspec ↗spliceai ↗vcep_hci_priors_pms2
BP7 SupportingMet at Supporting: c.1145-11C>T is intronic at -11, within the PMS2 VCEP BP7 range of -21/+7. Details ▾Hide ▴
Reasoning

The variant is intronic at c.1145-11, which is at or beyond -21 relative to the exon boundary and therefore falls within the PMS2 VCEP BP7 scope of intronic variants at or beyond -21/+7. The VCEP assigns BP7_Supporting to such variants; BP7 is met at Supporting strength. This criterion is applied from variant location and is not an additional use of the SpliceAI prediction.

Rule
A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic) satisfies BP7_Supporting under the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP BP7 rule applies at Supporting strength to synonymous or intronic variants at or beyond -21/+7 relative to the exonic boundary.
  • NM_000535.7:c.1145-11C>T is an intronic variant located 11 bases upstream of the exon boundary, within the specified BP7 range.
Sources
BP4 Not met: SpliceAI max delta 0.213 exceeds the PMS2 VCEP no-impact threshold of <=0.1. Details ▾Hide ▴
Reasoning

The variant is an intronic non-canonical splice-region variant, for which the PMS2 VCEP BP4 rule requires SpliceAI to predict no splicing impact with delta score <= 0.1. The observed SpliceAI maximum delta score is 0.213, which exceeds that cutoff; therefore BP4 is not met. The HCI-PRIORS-PMS2.txt.txt table was searched for c.1145-11C>T, p.?, and p.? and has no exact entry; it is indexed for missense variants and does not override the applicable intronic SpliceAI rule.

Rule
For intronic and synonymous variants, SpliceAI predicts no splicing impact with delta score <= 0.1 as specified by the PMS2 VCEP.
Evidence considered
  • The PMS2 VCEP specification requires SpliceAI delta score <= 0.1 for BP4 in intronic and synonymous variants.
  • SpliceAI reports a maximum delta score of 0.213 for NM_000535.7:c.1145-11C>T, above the VCEP BP4 cutoff.
  • The indexed HCI-PRIORS-PMS2.txt.txt file is a missense-only lookup table and was searched under c.1145-11C>T, p.?, and p.? without an exact entry.
Still missing
  • No exact c.1145-11C>T, p.?, or p.? entry was found in HCI-PRIORS-PMS2.txt.txt; the file is indexed for missense variants, while this variant is intronic.
Sources
cspec ↗spliceai ↗vcep_hci_priors_pms2

Statement

In silico

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

7 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata. None of the listed paper records explicitly indicates that the variant is named.

Recorded publications

  • Standards and guidelines for the interpretation of sequence variants: a joint consensus recommendation of the American College of Medical Genetics and Genomics and the Association for Molecular Pathology.
    Richards S et al. · 2015
    The paper provides general ACMG guidance that predicted splice-site effects require confirmation by RNA or protein analysis; it does not report PMS2 c.1145-11C>T or any variant-specific functional result.
    Does not name this variant
    PMID 25741868 ↗
    Quoted passage
    For splice site variants, the variant may lead to exon skipping, shortening or inclusion of intronic material, due to alternative donor/acceptor site usage or creation of new sites. Although splice site variants are predicted to lead to a null effect, confirmation of impact requires functional analysis by either RNA or protein analysis.

    Proposed Criteria for Interpretation of Sequence Variants, PVS1 Null variants

  • Practice parameters for the identification and testing of patients at risk for dominantly inherited colorectal cancer--supporting documentation.
    Church J et al. · 2001
    No paper-specific finding is recorded.
    PMID 11598466 ↗
  • Informing family members of individuals with Lynch syndrome: a guideline for clinical geneticists.
    No paper-specific finding is recorded.
    PMID 23535968 ↗
  • A practice guideline from the American College of Medical Genetics and Genomics and the National Society of Genetic Counselors: referral indications for cancer predisposition assessment.
    No paper-specific finding is recorded.
    PMID 25394175 ↗
  • Hereditary colorectal cancer syndromes: American Society of Clinical Oncology Clinical Practice Guideline endorsement of the familial risk-colorectal cancer: European Society for Medical Oncology Clinical Practice Guidelines.
    Stoffel EM et al. · 2015
    No paper-specific finding is recorded.
    PMID 25452455 ↗
  • Lynch Syndrome: A Primer for Urologists and Panel Recommendations.
    Mork M et al. · 2015
    No paper-specific finding is recorded.
    PMID 25711197 ↗
  • Sherloc: a comprehensive refinement of the ACMG-AMP variant classification criteria.
    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.35107e-05; MAF= 0.00635%, 99/1558792 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000887134; MAF= 0.08871%, 80/90178 alleles, homozygotes = 0); grpmax FAF= 0.00072958.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.00012918; MAF= 0.01292%, 31/239976 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000883739; MAF= 0.08837%, 27/30552 alleles, homozygotes = 0); grpmax FAF= 0.0006231.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.0001085894233901618, 2/18418 alleles, homozygotes = 0).

ClinVar

This variant has been reported in ClinVar as Likely benign (3 clinical laboratories) and as Benign (3 clinical laboratories) and as Likely Benign (1 clinical laboratory). (ClinVarID = 492248)

In silico

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

Somatic

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