0%
Print report
Variant interpretation report

PMS2 c.1567T>A, p.(Ser523Thr)

NM_000535.7:c.1567T>A NP_000526.2:p.(Ser523Thr) Missense · exon 11 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: 0 Benign evidence criteria: 2
Pathogenic criteria applied · 0

No pathogenic criterion marked as applied in the recorded assessment.

Benign criteria applied · 2
BS1Strong
BS1 · strong

Met, Strong: gnomAD v4.1 grpmax FAF is 0.00045665, within the PMS2 VCEP BS1 range of 0.00028 to less than 0.0028.

BP4Supporting
BP4 · supporting

Met, Supporting: the governing PMS2 HCI prior probability is 0.0008, below the VCEP BP4 cutoff of <0.11.

Recorded classification: Likely benign

Likely Benign: BS1 (strong) plus BP4 (supporting) satisfy the PMS2 InSiGHT VCEP's Rule18 benign combination.

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
270 / 1,613,828 alleles

gnomAD v4.1: 270 / 1,613,828 alleles. Recorded AF 0.000167304. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.000162798; MAF= 0.01628%, 46/282558 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000457277; MAF= 0.04573%, 14/30616 alleles, homozygotes = 0); grpmax FAF= 0.00027587.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.00016286644951140066, 3/18420 alleles, homozygotes = 0).

No screenshot for this evidence
REVEL score
0.262 recorded score

Recorded REVEL score: 0.262. Refer to the recorded PP3/BP4 rationale for interpretation.

ClinVar submissions
18 reported laboratory submissions

11 Likely benign · 5 Uncertain significance · 1 likely benign · 1 Benign. ClinVar API review status: criteria provided, conflicting classifications.

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. PMS2, an endonuclease involved in DNA repair, is altered in various cancers.

No listed criterion applied OncoKB ↗
COSMIC
Cancer Hotspots
Somatic evidence
No matching record reported

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

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.

For specialists

Technical detail

ACMG/AMP criteria under ClinGen PMS2 VCEP v2.0, with the data and sources behind each one.

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

Met Not met Not assessed Not applicable

For PMS2 p.Ser523Thr, the applicable VCEP excludes PM1, PP2, and BP1; no qualifying same-amino-acid Pathogenic comparator supports PS1 and no qualifying same-residue Pathogenic/Likely Pathogenic comparator supports PM5.

The governing PMS2 InSiGHT VCEP framework was applied rather than generic ACMG population thresholds.

gnomAD v4.1 all-comers data were used because the VCEP specifies gnomAD v4 and does not require a non-cancer or exome-only subset.

Population evidence supports BS1 Strong only; BA1 and PM2 are not met, and BS2 remains unassessed because the required individual-level phase and phenotype evidence is unavailable.

Met · 2

BS1 StrongMet, Strong: gnomAD v4.1 grpmax FAF is 0.00045665, within the PMS2 VCEP BS1 range of 0.00028 to less than 0.0028. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 VCEP specifies BS1 Strong when the gnomAD v4 grpmax filtering allele frequency is at least 0.00028 and less than 0.0028 (0.028–0.28%), and the variant is not an excluded founder pathogenic variant. The gnomAD v4.1 grpmax FAF is 0.00045665 (0.045665%), which falls within that interval; therefore BS1 Strong is met. The variant has no observed homozygotes, and the elevated South Asian frequency does not exceed the VCEP BS1-to-BA1 range.

Rule
PMS2 InSiGHT VCEP BS1 Strong: gnomAD v4 grpmax filtering allele frequency ≥0.00028 and <0.0028 (0.028–0.28%) and variant excluded as a founder pathogenic variant.
Evidence considered
  • The PMS2 VCEP specifies BS1 Strong at gnomAD v4 grpmax filtering allele frequency ≥0.00028 and <0.0028 (0.028–0.28%), provided the variant is not an excluded founder pathogenic variant.
  • gnomAD v4.1 reports grpmax FAF 0.00045665 (0.045665%), corresponding to 3 alleles in the highest grpmax population, and reports zero homozygotes.
Sources
BP4 SupportingMet, Supporting: the governing PMS2 HCI prior probability is 0.0008, below the VCEP BP4 cutoff of <0.11. Details ▾Hide ▴
Reasoning

This is a missense variant, and the governing PMS2 VCEP directly assigns BP4 Supporting when the HCI MAPP/PP2 Prior P score is <0.11. The exact HCI-PRIORS-PMS2 row for c.1567T>A (p.S523T) reports an HCI prior probability of 0.0008 and custom PP2 score of 0.031, both below the governing <0.11 cutoff. This direct VCEP assignment is used; SpliceAI is not used because the variant is missense.

Rule
PMS2 VCEP BP4 Supporting: missense variant with HCI MAPP/PP2 Prior P <0.11.
Evidence considered
  • The governing PMS2 VCEP specifies BP4 Supporting for a missense variant with HCI MAPP/PP2 Prior P <0.11.
  • The exact HCI-PRIORS-PMS2 row for c.1567T>A / p.S523T reports HCI prior probability 0.0008 and custom PP2 score 0.031, satisfying the VCEP BP4 rule.
Sources
cspec ↗vcep_hci_priors_pms2

Not met · 5 · evaluated, threshold not reached

PS1 Not met: the only reported alternate-nucleotide Ser523Thr observation was not established as Pathogenic by the PMS2 VCEP. Details ▾Hide ▴
Reasoning

The PMS2 VCEP PS1 rule requires a different nucleotide change producing the same amino-acid substitution that was previously established by the VCEP as Pathogenic, or a qualifying splice-site comparison. The target is NM_000535.7:c.1567T>A, p.Ser523Thr. PMID:17016615 reports a Ser523Thr substitution from a different nucleotide change (TCC to ACC, reported at nucleotide 1591) in 2 of 20 breast carcinomas, but it does not establish that comparator as VCEP-Pathogenic and the report is not a qualifying VCEP classification. No qualifying pathogenic same-amino-acid comparator was identified; therefore PS1 is not met.

Rule
A predicted missense substitution encoding the same amino acid change with a different underlying nucleotide change previously established by this VCEP as Pathogenic, and not a predicted or confirmed splice defect.
Evidence considered
  • The PMS2 VCEP requires a same-amino-acid substitution from a different nucleotide that was established by the VCEP as Pathogenic.
  • PMID:17016615 reports Ser523Thr from a different nucleotide change in 2 of 20 invasive breast carcinomas but does not establish the comparator as VCEP-Pathogenic.
Still missing
  • No VCEP-established Pathogenic same-amino-acid comparator was identified.
Sources
PM2 Not met: gnomAD v4.1 overall AF is 0.000167304, above the PMS2 VCEP PM2 threshold of less than 0.00002. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 VCEP specifies PM2 Supporting for an absent or extremely rare allele frequency below 0.00002 (less than 1 in 50,000 alleles) in gnomAD v4. The gnomAD v4.1 all-comers total allele frequency is 0.000167304 (270/1,613,828 alleles), above the VCEP threshold; therefore PM2 is not met. The variant is also observed in multiple ancestry groups and has zero homozygotes, but the observed allele frequency is sufficient to preclude PM2.

Rule
PMS2 InSiGHT VCEP PM2 Supporting: absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
Evidence considered
  • The PMS2 VCEP specifies PM2 Supporting for an absent or extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
  • gnomAD v4.1 reports an overall AF of 0.000167304, based on 270 of 1,613,828 alleles, with zero homozygotes; the highest ancestry-specific AF is 0.000581995 in South Asian individuals.
Sources
PM5 Not met: zero qualifying Pathogenic or Likely Pathogenic same-residue comparators were identified for Ser523. Details ▾Hide ▴
Reasoning

The PMS2 VCEP PM5 rule requires a different missense change at the same amino-acid residue that was classified by the VCEP as Pathogenic or Likely Pathogenic at the protein level and not because of aberrant splicing; the rule also requires PP3 supporting for the target missense change. The residue is Ser523, but the collected comparator review found zero same-residue candidates, zero expert-panel Pathogenic/Likely Pathogenic candidates, and zero non-expert majority candidates. Therefore no qualifying comparator is available to apply PM5.

Rule
Missense change at an amino-acid residue where a different missense change was classified by this VCEP as Pathogenic on the protein level and not due to aberrant splicing; use only if PP3 is supporting. Use PM5 Supporting when the other variant is Likely Pathogenic, and PM5 when it is Pathogenic.
Evidence considered
  • The PMS2 VCEP requires a different missense change at the same residue, classified as Pathogenic or Likely Pathogenic at the protein level and not due to aberrant splicing; PM5 also requires PP3 supporting for the target.
  • The PM5 comparator review found zero same-residue candidates, including zero expert-panel or non-expert-majority Pathogenic/Likely Pathogenic candidates.
Still missing
  • A qualifying VCEP-classified Pathogenic or Likely Pathogenic different missense change at residue Ser523 is not available.
Sources
cspec ↗pm5_candidates
PP3 Not met: the governing PMS2 HCI prior probability is 0.0008, below the VCEP PP3 Supporting threshold of >0.68. Details ▾Hide ▴
Reasoning

This is a missense variant, so the PMS2 VCEP missense computational rule applies. The governing HCI-PRIORS-PMS2 entry for c.1567T>A (p.S523T) reports HCI prior probability 0.0008 and custom PP2 score 0.031, neither of which reaches the VCEP PP3 thresholds (>0.81 for Moderate or >0.68 and <=0.81 for Supporting). The available REVEL score is 0.262 and does not provide an independent basis to meet PP3. SpliceAI is not used for PP3 because this is a missense variant.

Rule
PMS2 VCEP PP3: missense variant with MAPP/PP2 Prior P >0.81 = Moderate, or >0.68 and <=0.81 = Supporting.
Evidence considered
  • The governing PMS2 VCEP specifies PP3 Moderate for an HCI MAPP/PP2 Prior P score >0.81 and PP3 Supporting for >0.68 and <=0.81.
  • The exact HCI-PRIORS-PMS2 row for c.1567T>A / p.S523T reports HCI prior probability 0.0008, MAPP score 2.35, and custom PP2 score 0.031.
  • The case consequence is missense (PMS2 c.1567T>A, p.S523T), so SpliceAI is not an applicable PP3 path; the available REVEL score is 0.262 and does not meet the supplied generic PP3 Supporting threshold of 0.644 (ClinGen SVI calibration, PMID:36413997).
Sources
cspec ↗vcep_hci_priors_pms2revel
BA1 Not met: gnomAD v4.1 grpmax FAF is 0.00045665, below the PMS2 VCEP BA1 threshold of 0.0028. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 VCEP specifies BA1 when the gnomAD v4 grpmax filtering allele frequency is at least 0.0028 (0.28%) and the variant is not an excluded founder pathogenic variant. The gnomAD v4.1 grpmax FAF for NM_000535.7:c.1567T>A is 0.00045665 (0.045665%), well below 0.0028; therefore BA1 is not met. The available population data also show no homozygotes, but this does not alter the BA1 conclusion.

Rule
PMS2 InSiGHT VCEP BA1: gnomAD v4 grpmax filtering allele frequency ≥0.0028 (0.28%) and variant excluded as a founder pathogenic variant.
Evidence considered
  • The PMS2 VCEP specifies BA1 at gnomAD v4 grpmax filtering allele frequency ≥0.0028 (0.28%), provided the variant is not an excluded founder pathogenic variant.
  • gnomAD v4.1 reports grpmax FAF 0.00045665 (0.045665%), with the highest population frequency in South Asian individuals at AF 0.000581995 and no homozygotes.
Sources

Not assessed · 9 · no assessment recorded

PS2 Not assessed: no proband-level parental testing, de novo confirmation, LS-spectrum tumor, or tumor MSI/IHC evidence is available to assign VCEP de novo points. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP requires de novo points based on a proband with an LS-spectrum tumor: 2 points when both maternity and paternity are confirmed with MMR-deficient tumor data, 1 point when both are confirmed without tumor data, or 0.5 points when de novo status is assumed with maternity and/or paternity unconfirmed. The available case evidence provides no proband-level parental testing, maternity or paternity confirmation, de novo assertion, LS-spectrum tumor diagnosis, MSI/IHC result, or methylation result, so no de novo points can be assigned.

Rule
PMS2 InSiGHT VCEP v2.0 PS2: >=4 de novo points = Very Strong; 2-3.5 points = Strong; 1-1.5 points = Moderate; 0.5 points = Supporting.
Evidence considered
  • The PMS2 InSiGHT VCEP version 2.0 assigns 2, 1, or 0.5 de novo points according to parental confirmation and LS-spectrum tumor evidence.
  • The case materials contain no documented proband, parental testing, de novo status, or qualifying tumor findings for this variant.
Still missing
  • Proband-level evidence that the variant is de novo
  • Maternity and paternity testing status
  • LS-spectrum tumor diagnosis and MSI/IHC/methylation results
Sources
PS3 Not assessed: no variant-specific functional assay or calibrated functional odds are reported for PMS2 p.Ser523Thr. Details ▾Hide ▴
Reasoning

The applicable InSiGHT PMS2 VCEP requires a calibrated functional assay with functional odds for pathogenicity >2.08 for PS3 Supporting, >4.3 and <=18.7 for PS3 Moderate, or >18.7 for PS3 Strong; alternatively, an MMR function defect may support PS3 Moderate. The available variant-specific literature identifies p.Ser523Thr only as a neutral in-silico PON-MMR prediction and reports no functional assay, MMR activity measurement, protein-expression study, or RNA assay for NM_000535.7:c.1567T>A. OncoKB likewise reports no variant-specific reviewed functional evidence. Therefore, PS3 cannot be assigned.

Rule
Calibrated functional assays with functional odds for Pathogenicity > 18.7 (Strong); >4.3 and <=18.7 or MMR function defect following the functional assay flowchart (Moderate); >2.08 and <=4.3 (Supporting).
Evidence considered
  • The PMS2 InSiGHT VCEP specifies PS3 Supporting for calibrated functional odds >2.08 and <=4.3, Moderate for odds >4.3 and <=18.7 or an MMR function defect following the functional assay flowchart, and Strong for odds >18.7.
  • PMS2 p.Ser523Thr is listed in PMID:22290698 as a neutral PON-MMR in-silico prediction; the paper reports no variant-specific functional assay or clinical functional result.
  • OncoKB reports no variant-specific reviewed functional evidence for this variant.
Still missing
  • A validated, variant-specific PMS2 functional assay with calibrated functional odds or an MMR function-defect assessment is unavailable.
Sources
PM3 Not assessed: no affected-proband, homozygous, or phase-resolved in-trans pathogenic PMS2 observation is documented to assign VCEP PM3 points. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 VCEP v2.0 applies PM3 using an allelic-observation point system: at least 4 points supports Very Strong, 2–3.5 Strong, 1–1.5 Moderate, and 0.5 Supporting. The reviewed case evidence does not document an affected proband with NM_000535.7:c.1567T>A in trans with a known pathogenic or likely pathogenic PMS2 variant, a confirmed homozygous state, or other qualifying phase-resolved biallelic observation. PMID:26232782 mentions c.1567T>A only as a PMS2/PMS2CL paralogous sequence variant and reports no clinical or segregation data for it; PMID:22290698 lists S523T as a neutral in-silico prediction without clinical, phase, or segregation observations. Therefore no PM3 points can be assigned from the available evidence.

Rule
PMS2 VCEP v2.0 PM3 point system: ≥4 points Very Strong; 2–3.5 Strong; 1–1.5 Moderate; 0.5 Supporting.
Evidence considered
  • PMS2 VCEP v2.0 specifies PM3 point thresholds of ≥4 for Very Strong, 2–3.5 for Strong, 1–1.5 for Moderate, and 0.5 for Supporting.
  • The report by Nomura et al. mentions c.1567T>A as a paralogous sequence variant during PMS2/PMS2CL sequencing, but does not report it as the patient's mutation or provide clinical, segregation, or phase data for this variant.
  • The PON-MMR paper lists PMS2 S523T under neutral predictions and provides no clinical case, segregation, phase, or biallelic observation for this variant.
Still missing
  • Affected-proband observations with the variant are needed.
  • A confirmed pathogenic or likely pathogenic PMS2 allele in trans, or confirmed homozygosity, and phase evidence are needed to assign PM3 points.
Sources
PP1 Not assessed: no pedigree, informative meioses, phenotype-linked genotypes, or combined Bayes likelihood ratio is reported for PP1 evaluation. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP requires a combined segregation Bayes likelihood ratio greater than 2.08 for Supporting, greater than 4.3 and up to 18.7 for Moderate, or greater than 18.7 in at least two families for Strong. No affected or unaffected relatives, pedigree, informative meioses, phenotype-linked genotypes, or calculated Bayes likelihood ratio are reported for NM_000535.7:c.1567T>A, so PP1 cannot be assigned.

Rule
PMS2 InSiGHT VCEP v2.0 PP1: 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 sets PP1 thresholds at combined Bayes likelihood ratios >2.08 to 4.3 for Supporting, >4.3 to 18.7 for Moderate, and >18.7 in at least two families for Strong.
  • The available case evidence reports no family segregation data or Bayes likelihood ratio for this variant.
Still missing
  • Pedigree with affected and unaffected relatives
  • Variant genotypes and disease phenotypes for informative relatives
  • Combined segregation Bayes likelihood ratio
Sources
PP4 Not assessed: no case-specific CRC/endometrial tumor count or qualifying MSI-H and PMS2-consistent protein-loss result is available for the PP4 thresholds. Details ▾Hide ▴
Reasoning

PP4 is applicable under the PMS2 VCEP, but the available case evidence does not provide a case-specific CRC or endometrial tumor count, MSI status, tumor-genome result, or PMS2-consistent loss of MMR protein expression. The exact-variant paper mentioning c.1567T>A identifies it only as a paralogous sequence variant and reports no phenotype or tumor result. Therefore the PP4 threshold cannot be assessed. The governing VCEP rules are: Strong requires ≥3 independent CRC/endometrial MSI-H tumors in ≥2 families with qualifying tumor testing and/or consistent MMR protein loss; Moderate requires 2 independent qualifying tumors; Supporting requires 1 qualifying tumor.

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. MSI-H tumor with inconsistent protein expression does not meet PP4. Moderate: 2 independent CRC/Endometrial MSI-H tumors using a standard panel of 5-10 markers or tumor genome and/or loss of MMR protein expression consistent with the variant location. Strong: ≥3 independent CRC/Endometrial MSI-H tumors in ≥2 families using a standard panel of 5-10 markers or tumor genome and/or loss of MMR protein expression consistent with the variant location.
Evidence considered
  • The PMS2 VCEP defines PP4 Supporting as 1 qualifying CRC/endometrial MSI-H tumor, Moderate as 2 independent qualifying tumors, and Strong as ≥3 independent tumors in ≥2 families, with qualifying MSI/tumor-genome and/or MMR-protein evidence consistent with PMS2.
  • PMID:26232782 mentions c.1567T>A only as a paralogous sequence variant during PMS2/PMS2CL sequencing and does not report a clinical phenotype, tumor MSI result, or MMR-protein result for this variant.
Still missing
  • Case-specific tumor phenotype data are needed: tumor type, number of independent tumors and families, MSI or tumor-genome results, and PMS2-consistent MMR protein expression.
Sources
BS2 Not assessed: no qualifying in-trans pathogenic variant, age-specific cancer phenotype, CMMRD assessment, or confirmed phase data are available. Details ▾Hide ▴
Reasoning

The PMS2 VCEP requires co-occurrence in trans with a known pathogenic sequence variant in PMS2, a colorectal cancer diagnosis after age 45 or another Lynch syndrome cancer above its median age of onset, absence of CMMRD manifestations, and parental or offspring testing to confirm phase. The available case evidence contains no qualifying individual-level co-occurrence, phenotype, CMMRD assessment, or confirmed phase data, so BS2 cannot be assessed.

Rule
PMS2 InSiGHT VCEP BS2 Strong: co-occurrence in trans with a known pathogenic PMS2 sequence variant in a patient with colorectal cancer after age 45 or another Lynch syndrome cancer above its median age of onset, without CMMRD manifestations; phase must be confirmed through parents or offspring.
Evidence considered
  • The PMS2 VCEP BS2 rule requires in-trans co-occurrence with a known pathogenic PMS2 sequence variant, an age-qualified Lynch syndrome cancer phenotype, no prior or current CMMRD manifestations, and phase confirmation through parents or offspring.
  • No qualifying individual-level co-occurrence, phenotype, CMMRD assessment, or confirmed phase evidence is present in the reviewed case materials.
Still missing
  • A documented individual with this variant and a known pathogenic PMS2 variant confirmed in trans is needed.
  • The required age-specific Lynch syndrome cancer phenotype and absence of CMMRD manifestations must be documented.
  • Parental or offspring testing is needed to confirm phase.
Sources
BS3 Not assessed: no variant-specific protein, RNA, MMR activity, or calibrated functional assay demonstrates proficient function for p.Ser523Thr. Details ▾Hide ▴
Reasoning

The applicable InSiGHT PMS2 VCEP requires calibrated functional odds for pathogenicity <=0.05 for BS3 Strong or >0.05 and <=0.48 for BS3 Supporting; for missense variants, its flowchart also requires variant-specific proficient function in protein and mRNA-based laboratory assays for BS3 Supporting. The available evidence contains no variant-specific protein, RNA, MMR activity, expression, or calibrated functional assay for NM_000535.7:c.1567T>A. The PON-MMR neutral prediction is computational and cannot establish proficient function. Therefore, BS3 cannot be assigned.

Rule
Calibrated functional assays with functional odds for Pathogenicity <= 0.05 (Strong); >0.05 and <=0.48 or variant-specific proficient function in protein and mRNA-based laboratory assays (Supporting).
Evidence considered
  • The PMS2 InSiGHT VCEP specifies BS3 Strong for calibrated functional odds for pathogenicity <=0.05 and BS3 Supporting for odds >0.05 and <=0.48, or variant-specific proficient function in protein and mRNA-based laboratory assays under the MMR functional assay flowchart.
  • PMID:22290698 reports only a neutral computational PON-MMR prediction for S523T and provides no variant-specific functional assay demonstrating proficient protein or mRNA function.
  • OncoKB reports no variant-specific reviewed functional evidence for this variant.
Still missing
  • Variant-specific protein and mRNA-based laboratory assays or calibrated functional odds demonstrating proficient function are unavailable.
Sources
BS4 Not assessed: no non-segregating affected relative, informative pedigree data, or combined Bayes likelihood ratio is reported for BS4 evaluation. Details ▾Hide ▴
Reasoning

The PMS2 InSiGHT VCEP requires lack of co-segregation demonstrated by a combined Bayes likelihood ratio below 0.05 for Strong or greater than 0.05 and up to 0.48 for Supporting. No pedigree, affected-relative non-segregation, unaffected-carrier observation, informative meioses, or Bayes likelihood ratio is reported for NM_000535.7:c.1567T>A, so BS4 cannot be assigned.

Rule
PMS2 InSiGHT VCEP v2.0 BS4: combined Bayes likelihood ratio <0.05 = Strong; >0.05 and <=0.48 = Supporting.
Evidence considered
  • The PMS2 InSiGHT VCEP sets BS4 thresholds at a combined Bayes likelihood ratio <0.05 for Strong and >0.05 to 0.48 for Supporting.
  • The available case evidence reports no non-segregation observations or Bayes likelihood ratio for this variant.
Still missing
  • Pedigree with disease status and variant genotypes
  • Documented non-segregation in affected relatives
  • Combined segregation Bayes likelihood ratio
Sources
BP5 Not assessed: no case-specific MSS, MMR-protein, BRAF V600E, or MLH1-methylation findings are available for the BP5 tumor-count thresholds. Details ▾Hide ▴
Reasoning

BP5 is applicable under the PMS2 VCEP, but no case-specific evidence establishes the required benign tumor pattern. There are no reported counts of CRC/endometrial tumors with MSS or no MMR-protein loss, no LS-spectrum tumors with MMR-protein loss inconsistent with PMS2, and no qualifying BRAF V600E or MLH1-methylation result. Accordingly, neither the Supporting rule of 2 or 3 tumors or 1 qualifying BRAF/methylation result nor the Strong rule of ≥4 tumors or ≥2 qualifying BRAF/methylation results can be assessed. No numeric comparison is applicable to this qualitative tumor-count rule.

Rule
Supporting: 2 or 3 tumors with MSS and/or no loss of MMR protein expression and/or LS-spectrum tumors with loss of MMR protein(s) inconsistent with the gene demonstrating genetic variation, or 1 BRAF V600E/MLH1 methylation result with MSI-H/MLH1 loss. Strong: ≥4 such tumors, or ≥2 BRAF V600E/MLH1 methylation results with MSI-H/MLH1 loss.
Evidence considered
  • The PMS2 VCEP defines BP5 Supporting as 2 or 3 qualifying tumors or 1 qualifying BRAF V600E/MLH1-methylation result, and Strong as ≥4 qualifying tumors or ≥2 such results; none is documented for this case.
Still missing
  • Case-specific benign tumor evidence is needed: qualifying tumor count and pathology, MMR-protein expression, MSI status, and any BRAF V600E or MLH1-methylation results.
Sources
Not applicable · 12· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: NM_000535.7:c.1567T>A is a missense variant, p.Ser523Thr, not a specified PMS2 loss-of-function or qualifying splice-altering class. Details ▾Hide ▴
Reasoning

PVS1 is not applicable. NM_000535.7:c.1567T>A is annotated as the missense variant NP_000526.2:p.(Ser523Thr) on the preferred PMS2 transcript NM_000535.7. It is not a nonsense, frameshift, canonical splice-site, exon-level deletion/duplication, or confirmed splice-aberrant variant that creates a loss-of-function consequence. The PMS2 InSiGHT VCEP PVS1 decision tree limits PVS1 to specified loss-of-function and qualifying splice-altering classes; therefore no PVS1 strength tier is assigned.

Rule
PMS2 InSiGHT VCEP PVS1 decision tree: PVS1 is restricted to specified nonsense/frameshift, qualifying splice-site, large genomic alteration, or confirmed splice-aberration loss-of-function variants.
Evidence considered
  • The case normalization identifies NM_000535.7:c.1567T>A as NP_000526.2:p.(Ser523Thr), a missense substitution on the preferred PMS2 transcript NM_000535.7.
  • The PMS2 InSiGHT VCEP PVS1 decision tree specifies PVS1 for defined nonsense, frameshift, canonical splice, large genomic alteration, and qualifying confirmed splice-aberration scenarios; it does not apply PVS1 to an isolated missense substitution.
Sources
cspec ↗vcep_pvs1_decisiontree_mmr
PS4 VCEPNot applicable: the PMS2 VCEP explicitly excludes PS4 proband-counting evidence because tumor IHC is evaluated through PP4. Details ▾Hide ▴
Reasoning

The applicable InSiGHT PMS2 VCEP specification explicitly marks PS4 as not applicable and states that, because tumor IHC data are available for variant classification through PP4, PS4 is not used for MMR variant classification by proband counting. The VCEP source gives no PS4 strength rule to apply.

VCEP rule
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.
Evidence considered
  • The PMS2 InSiGHT VCEP specification labels PS4 not applicable and states that PS4 has not been utilized for MMR variant classification using proband counting due to available tumor IHC data.
Sources
PM1 VCEPNot applicable: the governing PMS2 VCEP designates PM1 as Not Applicable, and no authoritative domain-table entry is present. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP specifies PM1 as Not Applicable. The vcep_materials.json domain_tables object is present but empty, so there is no authoritative gene-specific domain entry to evaluate at residue 523; the VCEP applicability designation controls over generic PM1 use.

VCEP rule
Not Applicable.
Evidence considered
  • The governing PMS2 VCEP explicitly designates PM1 as Not Applicable.
  • The gene-specific domain_tables object is empty; no authoritative PMS2 critical-domain interval is supplied for residue 523.
Sources
cspec ↗vcep_mmr_functional_domains
PM4 VCEPNot applicable: the PMS2 VCEP explicitly designates PM4 as not applicable, and c.1567T>A produces only the amino-acid substitution p.Ser523Thr. Details ▾Hide ▴
Reasoning

PM4 is not applicable under the ClinGen InSiGHT PMS2 Version 2.0 specification. The VCEP explicitly labels PM4 as Not Applicable. Independently, this variant is a single-nucleotide missense substitution, p.Ser523Thr, rather than a protein-length-changing in-frame indel or other alteration for which generic PM4 would ordinarily be considered.

VCEP rule
PMS2 InSiGHT VCEP Version 2.0: PM4 applicability is Not Applicable.
Evidence considered
  • The PMS2 InSiGHT Hereditary Colorectal Cancer/Polyposis VCEP Version 2.0 explicitly lists PM4 as Not Applicable.
  • The normalized consequence is a missense substitution, NP_000526.2:p.(Ser523Thr), with no protein-length change or in-frame indel consequence.
Sources
PM6 VCEPNot applicable: the governing PMS2 InSiGHT VCEP version 2.0 explicitly designates PM6 as not applicable. Details ▾Hide ▴
Reasoning

The governing PMS2 InSiGHT VCEP version 2.0 explicitly marks PM6 as not applicable. No generic PM6 assessment is used because the gene-specific specification takes precedence.

VCEP rule
PMS2 InSiGHT VCEP v2.0: PM6 is not applicable.
Evidence considered
  • The PMS2 InSiGHT VCEP version 2.0 lists PM6 as not applicable.
Sources
PP2 VCEPNot applicable: the governing PMS2 VCEP explicitly designates PP2 as Not Applicable. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP explicitly designates PP2 as Not Applicable. No generic PP2 assessment is used when the applicable gene-specific specification excludes the criterion.

VCEP rule
Not Applicable.
Evidence considered
  • The governing PMS2 VCEP explicitly designates PP2 as Not Applicable.
Sources
PP5 VCEPNot applicable: the PMS2 VCEP excludes PP5, and ClinVar has no exact-variant expert-panel Pathogenic or Likely pathogenic classification. Details ▾Hide ▴
Reasoning

The applicable InSiGHT PMS2 VCEP explicitly marks PP5 not applicable and states that it is not for use. Independently, the ClinVar evidence shows no exact-variant expert-panel submission; the reported classification is Likely benign with single-submitter review status, so it cannot trigger PP5 under the required exact-variant expert-panel rule.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PMS2 VCEP labels PP5 not applicable and states that the criterion is not for use.
  • ClinVar reports no expert-panel submission for NM_000535.7:c.1567T>A and reports Likely benign with criteria provided by a single submitter; this is not an expert-panel Pathogenic or Likely pathogenic assertion and cannot trigger PP5.
Sources
BP1 VCEPNot applicable: the governing PMS2 VCEP explicitly designates BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The governing PMS2 VCEP explicitly designates BP1 as Not Applicable. No generic BP1 assessment is used when the applicable gene-specific specification excludes the criterion.

VCEP rule
Not Applicable.
Evidence considered
  • The governing PMS2 VCEP explicitly designates BP1 as Not Applicable.
Sources
BP2 VCEPNot applicable: the PMS2 VCEP v2.0 explicitly designates BP2 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT PMS2 VCEP v2.0 explicitly designates BP2 as Not Applicable. Accordingly, BP2 is not evaluated for NM_000535.7:c.1567T>A, regardless of the absence or presence of an unphased co-occurrence observation.

VCEP rule
PMS2 VCEP v2.0: BP2 is Not Applicable.
Evidence considered
  • The PMS2 VCEP v2.0 criterion table explicitly lists BP2 with applicability: Not Applicable.
Sources
BP3 VCEPNot applicable: the PMS2 VCEP designates BP3 as not applicable, and this SNV causes p.Ser523Thr rather than an in-frame repeat-region indel. Details ▾Hide ▴
Reasoning

BP3 is not applicable under the ClinGen InSiGHT PMS2 Version 2.0 specification, which explicitly labels BP3 as Not Applicable. The variant is a missense SNV, p.Ser523Thr, not an in-frame deletion or insertion in a repetitive region; the available repeat/paralog context does not override the VCEP applicability decision.

VCEP rule
PMS2 InSiGHT VCEP Version 2.0: BP3 applicability is Not Applicable.
Evidence considered
  • The PMS2 InSiGHT Hereditary Colorectal Cancer/Polyposis VCEP Version 2.0 explicitly lists BP3 as Not Applicable.
  • The variant is a single-nucleotide missense change, p.Ser523Thr, with no in-frame deletion or insertion and therefore no BP3-type protein consequence.
Sources
BP6 VCEPNot applicable: the PMS2 VCEP excludes BP6, and ClinVar has no exact-variant expert-panel Benign or Likely benign classification. Details ▾Hide ▴
Reasoning

The applicable InSiGHT PMS2 VCEP explicitly marks BP6 not applicable and states that it is not for use. Independently, the ClinVar evidence shows no exact-variant expert-panel submission; the available Likely benign and Benign labels are ordinary laboratory/aggregate submissions, not an expert-panel assertion, so they cannot trigger BP6 under the required rule.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The PMS2 VCEP labels BP6 not applicable and states that the criterion is not for use.
  • ClinVar reports no expert-panel submission for NM_000535.7:c.1567T>A; the available Likely benign and Benign classifications are laboratory/aggregate submissions and do not satisfy the exact-variant expert-panel requirement for BP6.
Sources
BP7 N/ANot applicable: PMS2 c.1567T>A is a missense SNV encoding p.S523T, not a synonymous or qualifying intronic variant. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous or qualifying intronic variants. PMS2 c.1567T>A is a missense SNV encoding p.S523T, so BP7 is outside its scope and is not evaluated.

Rule
PMS2 VCEP BP7: synonymous or intronic variant at or beyond -21/+7 (5'/3' exonic).
Evidence considered
  • The PMS2 VCEP BP7 rule applies to synonymous or qualifying intronic variants, whereas this variant is annotated as missense (p.S523T).
Sources

Identifiers

Gene
PMS2
Transcript
NM_000535.7
Coding (HGVS c.)
NM_000535.7:c.1567T>A
Protein (HGVS p.)
NP_000526.2:p.(Ser523Thr)
GRCh38
chr7:5987198 A>T
GRCh37
chr7:6026829 A>T
Location and type
Exon 11 · missense
ClinVar
3063704, 127763

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 270 / 1,613,828 alleles AF 0.000167 · 0 homozygotes · FAF 0.000457
gnomAD v2.1 46 / 282,558 alleles AF 0.000163 · 0 homozygotes · FAF 0.000276
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 0.00017 · 270 / 1,613,828 alleles · 0 hom · FAF 0.00046
South Asian53 / 91,066 0.00058
European (non-Finnish)198 / 1,179,914 0.00017
Remaining individuals6 / 62,504 9.6e-05
Admixed American4 / 59,966 6.7e-05
European (Finnish)4 / 63,952 6.3e-05
African/African American4 / 74,974 5.3e-05
East Asian1 / 44,874 2.2e-05
0 alternate alleles recorded in 3 other groups: Amish, Middle Eastern, Ashkenazi Jewish.

gnomAD v2.1

AF 0.00016 · 46 / 282,558 alleles · 0 hom · FAF 0.00028
South Asian14 / 30,616 0.00046
European (non-Finnish)28 / 129,000 0.00022
Remaining individuals1 / 7,216 0.00014
European (Finnish)2 / 25,116 8e-05
Admixed American1 / 35,436 2.8e-05
0 alternate alleles recorded in 3 other groups: African/African American, Ashkenazi Jewish, East Asian.

gnomAD-Canada

AF not recorded · ? / ? alleles

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 0.000167304; MAF= 0.01673%, 270/1613828 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000581995; MAF= 0.05820%, 53/91066 alleles, homozygotes = 0); grpmax FAF= 0.00045665.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.000162798; MAF= 0.01628%, 46/282558 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000457277; MAF= 0.04573%, 14/30616 alleles, homozygotes = 0); grpmax FAF= 0.00027587.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.00016286644951140066, 3/18420 alleles, homozygotes = 0).

Open the gnomAD-Canada detail page →

SpliceAI and Pangolin

SpliceAI acceptor lossat -76 bp
0.013
SpliceAI acceptor gainat +461 bp
0.005
SpliceAI donor lossat +14 bp
0.002
SpliceAI donor gainat -439 bp
0.002
Pangolin splice lossmagnitude shown
-0.023
Pangolin splice gain
0.001

Other predictors

REVEL
0.262
BayesDel
-0.405

How the predictions were used

BP4 SupportingMet, Supporting: the governing PMS2 HCI prior probability is 0.0008, below the VCEP BP4 cutoff of <0.11. Details ▾Hide ▴
Reasoning

This is a missense variant, and the governing PMS2 VCEP directly assigns BP4 Supporting when the HCI MAPP/PP2 Prior P score is <0.11. The exact HCI-PRIORS-PMS2 row for c.1567T>A (p.S523T) reports an HCI prior probability of 0.0008 and custom PP2 score of 0.031, both below the governing <0.11 cutoff. This direct VCEP assignment is used; SpliceAI is not used because the variant is missense.

Rule
PMS2 VCEP BP4 Supporting: missense variant with HCI MAPP/PP2 Prior P <0.11.
Evidence considered
  • The governing PMS2 VCEP specifies BP4 Supporting for a missense variant with HCI MAPP/PP2 Prior P <0.11.
  • The exact HCI-PRIORS-PMS2 row for c.1567T>A / p.S523T reports HCI prior probability 0.0008 and custom PP2 score 0.031, satisfying the VCEP BP4 rule.
Sources
cspec ↗vcep_hci_priors_pms2
PP3 Not met: the governing PMS2 HCI prior probability is 0.0008, below the VCEP PP3 Supporting threshold of >0.68. Details ▾Hide ▴
Reasoning

This is a missense variant, so the PMS2 VCEP missense computational rule applies. The governing HCI-PRIORS-PMS2 entry for c.1567T>A (p.S523T) reports HCI prior probability 0.0008 and custom PP2 score 0.031, neither of which reaches the VCEP PP3 thresholds (>0.81 for Moderate or >0.68 and <=0.81 for Supporting). The available REVEL score is 0.262 and does not provide an independent basis to meet PP3. SpliceAI is not used for PP3 because this is a missense variant.

Rule
PMS2 VCEP PP3: missense variant with MAPP/PP2 Prior P >0.81 = Moderate, or >0.68 and <=0.81 = Supporting.
Evidence considered
  • The governing PMS2 VCEP specifies PP3 Moderate for an HCI MAPP/PP2 Prior P score >0.81 and PP3 Supporting for >0.68 and <=0.81.
  • The exact HCI-PRIORS-PMS2 row for c.1567T>A / p.S523T reports HCI prior probability 0.0008, MAPP score 2.35, and custom PP2 score 0.031.
  • The case consequence is missense (PMS2 c.1567T>A, p.S523T), so SpliceAI is not an applicable PP3 path; the available REVEL score is 0.262 and does not meet the supplied generic PP3 Supporting threshold of 0.644 (ClinGen SVI calibration, PMID:36413997).
Sources
cspec ↗vcep_hci_priors_pms2revel
BP7 N/ANot applicable: PMS2 c.1567T>A is a missense SNV encoding p.S523T, not a synonymous or qualifying intronic variant. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous or qualifying intronic variants. PMS2 c.1567T>A is a missense SNV encoding p.S523T, so BP7 is outside its scope and is not evaluated.

Rule
PMS2 VCEP BP7: synonymous or intronic variant at or beyond -21/+7 (5'/3' exonic).
Evidence considered
  • The PMS2 VCEP BP7 rule applies to synonymous or qualifying intronic variants, whereas this variant is annotated as missense (p.S523T).
Sources

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.01). REVEL score = 0.262. BayesDel score = -0.405143. HCI prior probability for pathogenicity = 0.0008. MAPP score = 2.35. Custom PP2 score = 0.031.

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

Recorded publications

  • The mismatch repair gene hPMS2 is mutated in primary breast cancer.
    Balogh GA et al. · 2006
    The paper reports a Ser-to-Thr substitution at codon 523 in 2 of 20 invasive breast carcinomas, but specifies a different nucleotide change (TCC to ACC at nucleotide 1591) and does not establish the comparator as a VCEP-Pathogenic variant.
    Does not name this variant
    PMID 17016615 ↗
    Quoted passage
    523 Ser x Thr TCC x ACC 1591 2/20

    Table IV, hPMS2 missense mutations from invasive breast carcinomas

  • ASCO 2006 update of recommendations for the use of tumor markers in gastrointest
    No paper-specific finding is recorded.
    PMID 17060676 ↗
  • Identification of individuals at risk for Lynch syndrome using targeted evaluati
    No paper-specific finding is recorded.
    PMID 22167527 ↗
  • Classification of mismatch repair gene missense variants with PON-MMR.
    Ali H et al. · 2012
    This paper lists PMS2 S523T among neutral predictions from the PON-MMR in-silico predictor, but reports no proband, parental testing, pedigree segregation, informative meioses, or non-segregation result for the variant.
    Names this variant
    PMID 22290698 ↗
    Quoted passage
    S523T

    Table 3, ‘Predicted Pathogenic and Neutral MMR Missense Variants,’ PMS2 under ‘Neutral’

  • Multitarget stool DNA testing for colorectal-cancer screening.
    No paper-specific finding is recorded.
    PMID 25006736 ↗
  • 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
    No paper-specific finding is recorded.
    PMID 25741868 ↗
  • A case of early onset rectal cancer of Lynch syndrome with a novel deleterious PMS2 mutation.
    Nomura S et al. · 2015
    This case report explicitly lists c.1567T>A as a paralogous sequence variant detected during PMS2/PMS2CL sequencing, but the reported patient carried PMS2 c.1492del11; no segregation, de novo, parental-testing, or non-segregation result is provided for c.1567T>A.
    Names this variant
    PMID 26232782 ↗
    Quoted passage
    The three other PVSs detected were: c.1556A > G, c.1559C > T and c.1567T > A (Supplementary data, Figure).

    Case report and genetic analysis, sequencing results, p. 990

  • Improving performance of multigene panels for genomic analysis of cancer predisp
    No paper-specific finding is recorded.
    PMID 26845104 ↗

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= 0.000167304; MAF= 0.01673%, 270/1613828 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000581995; MAF= 0.05820%, 53/91066 alleles, homozygotes = 0); grpmax FAF= 0.00045665.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 0.000162798; MAF= 0.01628%, 46/282558 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 0.000457277; MAF= 0.04573%, 14/30616 alleles, homozygotes = 0); grpmax FAF= 0.00027587.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 0.00016286644951140066, 3/18420 alleles, homozygotes = 0).

ClinVar

This variant has been reported in ClinVar as Likely benign (11 clinical laboratories) and as Uncertain significance (5 clinical laboratories) and as likely benign (1 clinical laboratory) and as Benign (1 clinical laboratory). (ClinVarID = 127763)

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.01). REVEL score = 0.262. BayesDel score = -0.405143. HCI prior probability for pathogenicity = 0.0008. MAPP score = 2.35. Custom PP2 score = 0.031.

Functional

OncoKB did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. PMS2, an endonuclease involved in DNA repair, is altered in various cancers.

Somatic

This variant does not lie in a statistically significant hotspot. This variant has not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.