0%
Print report
Variant interpretation report

MSH6 c.2294G>C, p.(Cys765Ser)

NM_000179.3:c.2294G>C NP_000170.1:p.(Cys765Ser) Missense · exon 4 View identifiers
Classification
Uncertain significance

Variant description:

No variant summary was recorded for this case.

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

Uncertain.The recorded classification is uncertain significance.

In plain language

Gene-level background from the recorded interpretation.

About MSH6

MSH6 encodes a protein in the DNA mismatch repair system, which fixes errors made during DNA replication. Partnering with MSH2, it forms a complex that recognizes and helps correct mismatched DNA bases, keeping the genetic code stable. Inherited mutations in MSH6 cause Lynch syndrome (hereditary nonpolyposis colorectal cancer), raising the risk of colorectal, endometrial, ovarian, and other cancers, while mutations in both copies lead to constitutional mismatch repair deficiency. Because faulty mismatch repair drives tumor development and produces microsatellite instability, MSH6 acts as a tumor suppressor, and cancers with such repair defects often respond well to immune checkpoint inhibitor therapy.

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 MSH6 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: 0
Pathogenic criteria applied · 1
PM2Supporting
PM2 · supporting

Met at Supporting: gnomAD v4.1 total AF 6.20e-07 is below the VCEP PM2 threshold of 0.00002, with zero homozygotes.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: PM2 (supporting) was the only applied criterion, and no ClinGen InSiGHT MSH6 combination rule was satisfied.

02The sources

Evidence at a glance

Evidence summaries and captured source records, where available. Missing entries should not be interpreted as negative findings.

No screenshot for this evidence
REVEL score
0.921 recorded score

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

No listed criterion applied
ClinVar submissions
5 reported laboratory submissions

4 Uncertain significance · 1 Uncertain Significance. ClinVar API review status: criteria provided, multiple submitters, no conflicts.

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. MSH6, a DNA mismatch repair protein, is frequently mutated in colorectal, small bowel, and endometrial cancers.

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

COSMIC could not be reviewed because the browser session was redirected to the login page before search results were available.

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.

For specialists

Technical detail

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

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

The applicable MSH6 VCEP is authoritative for these criteria: PM1, PP2, and BP1 are explicitly Not Applicable.

PS1 and PM5 require qualifying same-amino-acid or same-residue comparators; the collected comparator evidence was incomplete because retrieval failed with HTTP 429, so both remain not assessed rather than being inferred from absence.

The governing framework is the ClinGen InSiGHT Hereditary Colorectal Cancer/Polyposis MSH6 specification, version 2.0.

The available case evidence provides no documented parental testing, de novo observation, informative segregation, or non-segregation data for this variant; no criterion requiring such data can be assigned except that PM6 is explicitly not applicable under the VCEP.

Neither PS3 nor BS3 is assigned because the available evidence lacks a variant-specific functional assay result and calibrated functional odds for NM_000179.3:c.2294G>C (p.Cys765Ser).

The MSH6 InSiGHT Version 2.0 VCEP specification governs this case and takes precedence over generic ACMG criteria for PS4, PP4, PP5, BP5, and BP6.

No exact-variant ClinVar expert-panel Pathogenic/Likely pathogenic or Benign/Likely benign classification is present; the available submissions are laboratory Uncertain significance assertions.

No patient-specific tumor phenotype or case-control enrichment dataset was available to assess PP4 or BP5 under their MSH6-specific rules.

Met · 1

PM2 SupportingMet at Supporting: gnomAD v4.1 total AF 6.20e-07 is below the VCEP PM2 threshold of 0.00002, with zero homozygotes. Details ▾Hide ▴
Reasoning

The governing InSiGHT/ClinGen MSH6 VCEP specifies PM2 at an allele frequency below 0.00002 (less than 1 in 50,000 alleles) in the gnomAD v4 dataset. gnomAD v4.1 reports this variant at total AF 6.195364628185191e-07, with 1 alternate allele among 1,614,110 alleles and zero homozygotes; the highest population AF is 8.47450445335209e-07 in the European non-Finnish population, also with zero homozygotes. The variant is therefore extremely rare under the VCEP threshold, meeting PM2 at Supporting strength.

Rule
Absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4 dataset.
Evidence considered
  • The MSH6 VCEP specifies PM2 at allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
  • gnomAD v4.1 reports total AF 6.195364628185191e-07, based on 1 alternate allele among 1,614,110 alleles, with zero homozygotes.
  • The highest observed population AF is 8.47450445335209e-07 in the European non-Finnish population, with zero homozygotes, which remains below 0.00002.
Sources

Not met · 4 · evaluated, threshold not reached

PP3 Not met: governing MSH6 HCI prior probability is 0.4345, below the PP3 supporting threshold of >0.68. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so PP3 is within scope. The governing MSH6 VCEP specification assigns missense PP3 using the HCI prior lookup: moderate requires a prior probability >0.81 and supporting requires >0.68 and <=0.81. The exact HCI-PRIORS-MSH6 entry for c.2294G>C / p.C765S / p.C765S reports MAPP/PP2 prior probability 0.4345, below the supporting threshold; therefore PP3 is not met. The table also reports a custom PP2 score of 0.690, but that is not the governing HCI prior probability and was not substituted for it. The generic REVEL result (0.921) was not used because the MSH6 VCEP-specific missense HCI-prior rule governs this criterion.

Evidence considered
  • The ClinGen InSiGHT MSH6 VCEP Version 2.0 specification defines missense PP3 as HCI prior probability >0.81 for moderate or >0.68 and <=0.81 for supporting.
  • The exact entry in /Users/gs_agent/LYFESCI_HERMES_v9/vcep_db/MSH6/fulltext/HCI-PRIORS-MSH6.txt.txt was found for c.2294G>C and p.C765S; its table columns identify Custom_PP2_score 0.690, MAPP_score 14.04, and MAPP/PP2_Prior 0.4345.
  • The case evidence records the variant as missense, with the exact HCI prior probability 0.4345 and a REVEL score of 0.921; the VCEP-specific HCI-prior rule takes precedence over generic REVEL thresholds.
Sources
cspec ↗vcep_hci_priors_msh6hci_prior
BA1 Not met: gnomAD v4.1 maximum observed population frequency 8.47e-07 is far below the VCEP BA1 threshold of 0.0022. Details ▾Hide ▴
Reasoning

The governing InSiGHT/ClinGen MSH6 VCEP specifies BA1 when the gnomAD v4 grpmax filtering allele frequency is at least 0.0022 (0.22%) and the variant is not a founder pathogenic variant. gnomAD v4.1 reports an all-comers total allele frequency of 6.195364628185191e-07 (1/1,614,110 alleles), with the highest observed population frequency 8.47450445335209e-07 in the European non-Finnish population (1/1,180,010 alleles); no grpmax value is reported, but all observed frequencies are far below 0.0022. BA1 is therefore not met.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.0022 (0.22%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • The MSH6 VCEP specifies BA1 at gnomAD v4 grpmax filtering allele frequency >=0.0022 (0.22%), excluding founder pathogenic variants.
  • gnomAD v4.1 reports total AF 6.195364628185191e-07 from 1 alternate allele among 1,614,110 alleles, and the highest population AF is 8.47450445335209e-07 in the European non-Finnish population from 1,180,010 alleles.
  • No gnomAD v4 grpmax value is reported for this variant; the available total and population frequencies are each substantially below the VCEP BA1 cutoff.
Sources
BS1 Not met: gnomAD v4.1 maximum observed population frequency 8.47e-07 is below the VCEP BS1 lower threshold of 0.00022. Details ▾Hide ▴
Reasoning

The governing InSiGHT/ClinGen MSH6 VCEP specifies BS1 at a gnomAD v4 grpmax filtering allele frequency of at least 0.00022 and below 0.0022 (0.022-0.22%), provided the variant is not a founder pathogenic variant. gnomAD v4.1 reports a total allele frequency of 6.195364628185191e-07 and a highest observed population frequency of 8.47450445335209e-07; both are below 0.00022. BS1 is therefore not met.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.00022 and < 0.0022 (0.022-0.22%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • The MSH6 VCEP specifies BS1 for gnomAD v4 grpmax filtering allele frequency >=0.00022 and <0.0022 (0.022-0.22%), excluding founder pathogenic variants.
  • gnomAD v4.1 reports total AF 6.195364628185191e-07 and highest population AF 8.47450445335209e-07 in the European non-Finnish population.
  • The observed frequencies are below 0.00022, so the VCEP BS1 interval is not reached.
Sources
BP4 Not met: governing MSH6 HCI prior probability is 0.4345, above the BP4 supporting threshold of <0.11. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so BP4 is within scope. The governing MSH6 VCEP specification assigns missense BP4 when the HCI prior probability is <0.11. The exact HCI-PRIORS-MSH6 entry for c.2294G>C / p.C765S reports an HCI prior probability of 0.4345, which is not below 0.11; therefore BP4 is not met. The SpliceAI max delta score of 0.002 and generic REVEL score of 0.921 were not used to override the governing VCEP-specific HCI-prior missense rule.

Evidence considered
  • The ClinGen InSiGHT MSH6 VCEP Version 2.0 specification defines missense BP4 as HCI prior probability <0.11.
  • The exact entry in /Users/gs_agent/LYFESCI_HERMES_v9/vcep_db/MSH6/fulltext/HCI-PRIORS-MSH6.txt.txt was found for c.2294G>C and p.C765S, with MAPP/PP2 prior probability 0.4345.
  • The case evidence records SpliceAI max delta 0.002 and REVEL 0.921, but neither is used to replace the governing VCEP-specific HCI-prior assessment for this missense variant.
Sources
cspec ↗vcep_hci_priors_msh6hci_prior

Not assessed · 11 · no assessment recorded

PS1 Not assessed: no validated VCEP-Pathogenic alternate-nucleotide comparator for p.Cys765Ser was identified, but the comparator search had a retrieval failure. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP defines PS1 for a missense substitution producing the same amino-acid change as a different nucleotide change previously established by the VCEP as Pathogenic, or for certain non-canonical splice substitutions. The case variant is missense p.Cys765Ser, but the available comparator collection contains no validated alternate-nucleotide p.Cys765Ser established as VCEP Pathogenic, and no splice-variant scenario applies. Because the comparator search reported a soft retrieval failure, absence of a qualifying PS1 comparator cannot be treated as conclusive.

Rule
MSH6 VCEP PS1: same amino-acid change from a different nucleotide change previously established by this VCEP as Pathogenic; specified splice alternative not applicable.
Evidence considered
  • The MSH6 VCEP PS1 rule requires the same amino-acid change from a different nucleotide change previously established by the VCEP as Pathogenic, or a specified non-canonical splice comparison.
  • The variant is a missense substitution, NM_000179.3:c.2294G>C, p.Cys765Ser; the collected comparator search reported zero same-residue candidates and an HTTP 429 retrieval error.
Still missing
  • Confirm through a complete VCEP/ClinVar review whether an alternate-nucleotide MSH6 variant causing p.Cys765Ser is VCEP-Pathogenic.
Sources
cspec ↗pm5_candidates
PS2 Not assessed: no proband-level parental testing or de novo evidence is documented for assigning the VCEP's 0.5–2 points per proband. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP specifies PS2 using de novo points: 2 points per proband when both maternity and paternity are confirmed and an MMR-deficient Lynch-spectrum tumor is documented; 1 point per proband when both parents are confirmed without tumor data; and 0.5 points per proband when maternity and/or paternity are unconfirmed without tumor data. The available case evidence does not document a proband-level de novo observation, parental testing, maternity or paternity confirmation, or an eligible Lynch-spectrum tumor with the required molecular characterization. Therefore, no PS2 points can be assigned.

Rule
MSH6 InSiGHT VCEP v2.0 PS2: 2 de novo points per proband with confirmed maternity and paternity plus an MMR-deficient Lynch-spectrum tumor; 1 point with confirmed maternity and paternity but no tumor data; 0.5 points when maternity and/or paternity are unconfirmed without tumor data; >=4 points PS2_VeryStrong, 2-3.5 PS2_Strong, 1-1.5 PS2_Moderate, and 0.5 PS2_Supporting.
Evidence considered
  • The MSH6 InSiGHT VCEP PS2 rule assigns 2 points per proband for confirmed maternity and paternity with an MMR-deficient Lynch-spectrum tumor, 1 point when both parents are confirmed without tumor data, and 0.5 points when maternity and/or paternity are unconfirmed without tumor data.
  • The reviewed case evidence contains no documented proband-level parental testing, de novo finding, maternity or paternity confirmation, or qualifying tumor molecular results for NM_000179.3:c.2294G>C.
Still missing
  • Documented proband-level testing of the variant in the child and both biological parents.
  • Confirmation of maternity and paternity, if available.
  • Documentation of an eligible Lynch-spectrum tumor and MSI/IHC/methylation results, if available.
Sources
PS3 Not assessed: no variant-specific calibrated functional assay result, functional-odds estimate, or demonstrated MMR defect is available for p.Cys765Ser. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP permits PS3 for calibrated functional assays with functional odds for pathogenicity >18.7 (strong), >4.3 and <=18.7 (moderate), or >2.08 and <=4.3 (supporting), and for a demonstrated MMR function defect under its functional-assay flowchart. The available case evidence identifies this as the missense variant NM_000179.3:c.2294G>C (p.Cys765Ser), but contains no variant-specific calibrated assay result, functional-odds estimate, MMR activity result, protein-expression result, or patient-derived functional assay result. General MSH6 functional-assay publications and VCEP assay documentation establish the applicable framework but do not provide evidence for this variant; therefore PS3 cannot be assigned.

Rule
Calibrated functional assays with functional odds for pathogenicity >18.7 (strong), >4.3 and <=18.7 (moderate), or >2.08 and <=4.3 (supporting); moderate may also be supported by an MMR function defect following the functional assay flowchart.
Evidence considered
  • The MSH6 Version 2.0 VCEP specifies PS3 strong at functional odds for pathogenicity >18.7, moderate at >4.3 and <=18.7, and supporting at >2.08 and <=4.3.
  • The MSH6 functional-assay flowchart requires a calibrated assay or concordant validated functional evidence demonstrating an MMR function defect before assigning PS3.
  • Case-specific records identify NM_000179.3:c.2294G>C (p.Cys765Ser) but provide no variant-specific functional assay measurement or assay-derived classification result.
Still missing
  • Variant-specific calibrated functional assay data or a validated MMR function-defect result is required.
  • If using calibrated evidence, the functional odds for pathogenicity must be reported to select the VCEP strength tier: >2.08, >4.3, or >18.7.
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchart
PM3 Not assessed: no affected-proband observation or confirmed phase with a pathogenic MSH6 variant is documented to assign any PM3 points. Details ▾Hide ▴
Reasoning

The applicable MSH6 InSiGHT VCEP specification assigns PM3 strength by points (supporting at 0.5 points, moderate at 1–1.5, strong at 2–3.5, and very strong at ≥4 points). The available case evidence documents no affected proband with a second pathogenic or likely pathogenic MSH6 variant, no confirmed trans or cis phase, and no informative biallelic inheritance observation; therefore no PM3 points can be assigned.

Rule
PM3: ≥4 points = Very Strong; 2–3.5 points = Strong; 1–1.5 points = Moderate; =0.5 points = Supporting.
Evidence considered
  • The MSH6 VCEP specification defines PM3 using a point system: supporting at 0.5 points, moderate at 1–1.5 points, strong at 2–3.5 points, and very strong at ≥4 points.
  • The reviewed case materials contain no documented affected-proband observation, second pathogenic or likely pathogenic MSH6 allele, or confirmed trans/cis phase for NM_000179.3:c.2294G>C.
  • MSH6 has both autosomal dominant Lynch syndrome and autosomal recessive constitutional mismatch repair deficiency contexts, so PM3 requires explicit biallelic phase and inheritance evidence rather than inference from the gene alone.
Still missing
  • Affected-proband observation involving this variant and a second pathogenic or likely pathogenic MSH6 variant
  • Confirmed trans or cis phase between the variants
  • Inheritance or family data sufficient to establish biallelic disease
Sources
PM5 Not assessed: zero same-residue comparator candidates were collected, but the search recorded an HTTP 429 retrieval failure. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP permits PM5 for a missense change at a residue where a different missense change was classified by the VCEP as Pathogenic, or PM5_Supporting when the comparator is Likely Pathogenic, with the specified dependence on PP3. The target is p.Cys765Ser, but the collected same-residue comparator set contains zero candidates. The collection also records an HTTP 429 retrieval failure, so the absence of a comparator is not sufficiently complete to conclude that PM5 is not met.

Rule
MSH6 VCEP PM5: different missense change at the same residue classified by this VCEP as Pathogenic or Likely Pathogenic on the protein level, not due to aberrant splicing; use only with target PP3 support.
Evidence considered
  • The MSH6 VCEP PM5 rule requires a different missense substitution at the same amino-acid residue classified by the VCEP as Pathogenic or Likely Pathogenic on the protein level and not due to aberrant splicing; it also requires PP3 support for the target missense variant.
  • The collected PM5 candidate artifact reports zero same-residue candidates and an HTTP 429 retrieval error, so comparator absence is incomplete.
Still missing
  • Complete a validated search for alternate missense substitutions at MSH6 residue Cys765 and verify each comparator's VCEP classification and mechanism.
Sources
cspec ↗pm5_candidates
PP1 Not assessed: no informative affected-relative meioses or combined Bayes likelihood ratio is documented against the VCEP's 2.08 supporting threshold. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP requires a combined Bayes likelihood ratio from cosegregation: greater than 2.08 and up to 4.3 supports PP1, greater than 4.3 and up to 18.7 supports PP1_Moderate, and greater than 18.7 in at least two families supports PP1_Strong. No affected-relative pedigree, informative meioses, segregation counts, or combined Bayes likelihood ratio is documented for this variant. Therefore, PP1 cannot be assessed.

Rule
MSH6 InSiGHT VCEP v2.0 PP1: combined Bayes likelihood ratio >2.08 and <=4.3 is Supporting; >4.3 and <=18.7 is Moderate; >18.7 in >=2 families is Strong.
Evidence considered
  • The MSH6 InSiGHT VCEP PP1 thresholds are combined Bayes likelihood ratio >2.08 to <=4.3 for supporting, >4.3 to <=18.7 for moderate, and >18.7 in at least two families for strong evidence.
  • The reviewed case evidence contains no informative pedigree, affected-relative segregation results, meioses, or combined Bayes likelihood ratio for NM_000179.3:c.2294G>C.
Still missing
  • A pedigree identifying tested affected and unaffected relatives.
  • Variant status and phenotype status for each informative relative.
  • A combined Bayes likelihood ratio, ideally calculated using the VCEP-recommended segregation method.
Sources
PP4 Not assessed: no patient-specific MSI, tumor-genome, MMR-protein-loss, or qualifying-tumor-count evidence is available for PP4. Details ▾Hide ▴
Reasoning

The applicable MSH6 InSiGHT specification provides PP4 Supporting for one CRC or endometrial MSI-H tumor, using a standard 5–10-marker panel or tumor genome, and/or loss of MMR protein expression consistent with the variant location; PP4 Moderate requires two independent tumors and PP4 Strong requires at least three. The case materials provide no patient-specific MSI result, tumor-genome result, MMR immunohistochemistry result, or count of qualifying independent tumors for NM_000179.3:c.2294G>C, so PP4 cannot be assessed.

Rule
PP4 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: ≥3 independent tumors.
Evidence considered
  • The MSH6 InSiGHT PP4 rule requires one or more CRC/endometrial MSI-H tumors and/or consistent MMR protein loss, with higher strengths requiring two or at least three independent tumors.
Still missing
  • Patient-specific tumor phenotype data: MSI status or tumor-genome result, MMR protein expression, and number of independent qualifying CRC/endometrial tumors.
Sources
BS2 Not assessed: no qualifying VCEP-defined in-trans co-occurrence and confirmed phase evidence are available for BS2. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP requires BS2 evidence of confirmed co-occurrence in trans with a known pathogenic sequence variant in the same gene in a patient with colorectal cancer after age 45, or another Lynch-syndrome cancer above its median age of onset, without clinical manifestations of constitutional mismatch repair deficiency; phase must be confirmed through parental or offspring testing. The available case materials provide no qualifying co-occurrence, phase, unaffected-homozygote, penetrance, or age-at-diagnosis evidence for this variant. BS2 cannot be assessed from the available evidence.

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 another Lynch-syndrome cancer above the median age of onset), without prior or current clinical manifestations of CMMRD; phase requires parental or offspring testing.
Evidence considered
  • The MSH6 VCEP BS2 rule requires in-trans co-occurrence with a known pathogenic sequence variant, qualifying cancer age, absence of CMMRD manifestations, and phase confirmation through parents or offspring.
  • No qualifying BS2 co-occurrence, phase, or clinical-context record is present in the available case evidence.
Still missing
  • Variant-specific documentation of co-occurrence in trans with a known pathogenic MSH6 sequence variant.
  • Confirmation of phase through parental or offspring testing.
  • Required clinical context: cancer type and age above the applicable Lynch-syndrome median, with no CMMRD manifestations.
Sources
BS3 Not assessed: no variant-specific proficient functional assay result or calibrated functional odds value <=0.48 is available for p.Cys765Ser. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP permits BS3 strong for calibrated functional assays with functional odds for pathogenicity <=0.05, or for synonymous/intronic variants with no mRNA aberration after appropriate testing; it permits BS3 supporting for calibrated functional odds >0.05 and <=0.48 or variant-specific proficient protein- and mRNA-based assay results under the MMR flowchart. This is a missense variant, NM_000179.3:c.2294G>C (p.Cys765Ser), and the available case evidence contains no variant-specific calibrated assay result, functional-odds estimate, proficient protein assay, mRNA assay, or validated benign functional finding. Therefore BS3 cannot be assigned.

Rule
Calibrated functional assays with functional odds for pathogenicity <=0.05 (strong) or >0.05 and <=0.48 (supporting); supporting may also be based on variant-specific proficient protein and mRNA assays under the MMR functional-assay flowchart.
Evidence considered
  • The MSH6 Version 2.0 VCEP specifies BS3 strong at functional odds for pathogenicity <=0.05 and BS3 supporting at >0.05 and <=0.48.
  • The VCEP also allows BS3 supporting for variant-specific proficient protein and mRNA-based laboratory assays performed according to the MMR functional-assay flowchart.
  • Case-specific records identify NM_000179.3:c.2294G>C (p.Cys765Ser) but provide no variant-specific proficient assay result, calibrated functional odds, or benign functional finding.
Still missing
  • Variant-specific calibrated functional assay data or concordant proficient protein and mRNA assay results is required.
  • If using calibrated evidence, the functional odds for pathogenicity must be reported to distinguish BS3 strong (<=0.05) from BS3 supporting (>0.05 and <=0.48).
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchart
BS4 Not assessed: no informative non-segregation data or combined Bayes likelihood ratio is documented against the VCEP's 0.48 upper threshold. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP requires a combined Bayes likelihood ratio below 0.48 for lack of cosegregation: below 0.05 supports BS4_Strong, while greater than 0.05 and up to 0.48 supports BS4_Supporting. No pedigree, unaffected or affected relative testing, informative non-segregation observation, or combined Bayes likelihood ratio is documented. Therefore, BS4 cannot be assessed.

Rule
MSH6 InSiGHT VCEP v2.0 BS4: combined Bayes likelihood ratio <0.05 is Strong; >0.05 and <=0.48 is Supporting.
Evidence considered
  • The MSH6 InSiGHT VCEP BS4 thresholds are a combined Bayes likelihood ratio <0.05 for strong evidence and >0.05 to <=0.48 for supporting evidence.
  • The reviewed case evidence contains no informative non-segregation observations, pedigree data, relative testing results, or combined Bayes likelihood ratio for NM_000179.3:c.2294G>C.
Still missing
  • A pedigree identifying tested relatives and their disease or unaffected status.
  • Variant testing results for informative relatives who do not show expected cosegregation.
  • A combined Bayes likelihood ratio for the non-segregation evidence.
Sources
BP5 Not assessed: no qualifying MSS, MMR-expression, BRAF V600E, MLH1-methylation, or tumor-count evidence is available for BP5. Details ▾Hide ▴
Reasoning

The applicable MSH6 InSiGHT specification defines BP5 Supporting as two or three tumors with MSS and/or no MMR-protein loss and/or an LS-spectrum tumor with MMR-protein loss inconsistent with MSH6, or one BRAF V600E/MLH1-methylation finding in the specified tumor context; Strong requires at least four qualifying tumors or at least two BRAF V600E/MLH1-methylation findings. No patient-specific tumor pathology, MSI/MSS result, MMR-protein expression, BRAF V600E result, MLH1 methylation result, or qualifying tumor count is available, so BP5 cannot be assessed.

Rule
BP5 Supporting: 2 or 3 qualifying tumors, or 1 BRAF V600E/MLH1-methylation finding in the specified context; Strong: ≥4 qualifying tumors or ≥2 such findings.
Evidence considered
  • The MSH6 InSiGHT BP5 rule requires two or three qualifying tumors or one specified BRAF V600E/MLH1-methylation finding for Supporting, and at least four qualifying tumors or two specified findings for Strong.
Still missing
  • Patient-specific tumor pathology data and qualifying tumor count, including MSS/MSI, MMR-protein expression, BRAF V600E, or MLH1 methylation where applicable.
Sources
Not applicable · 12· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: c.2294G>C is a missense change producing p.(Cys765Ser), not a VCEP-defined nonsense, frameshift, splice, or large-alteration loss-of-function variant. Details ▾Hide ▴
Reasoning

The applicable ClinGen InSiGHT MSH6 Version 2.0 specification limits PVS1 to qualifying loss-of-function mechanisms, including nonsense/frameshift variants, specified splice defects, large genomic alterations, and confirmed aberrant splicing that creates a truncation or critical in-frame disruption. NM_000179.3:c.2294G>C is a missense substitution, NP_000170.1:p.(Cys765Ser), with no reported premature termination codon, exon-skipping event, NMD mechanism, or protein-length change; therefore no PVS1 rule applies. The generic SVI PVS1 framework is not used because an applicable MSH6 VCEP specification governs.

Rule
MSH6 VCEP Version 2.0 PVS1 applicability rule
Evidence considered
  • The MSH6 Version 2.0 VCEP PVS1 rule covers nonsense/frameshift variants, specified splice defects, large genomic alterations, and confirmed aberrant splicing with qualifying protein disruption.
  • The case variant is NM_000179.3:c.2294G>C, annotated as the missense substitution NP_000170.1:p.(Cys765Ser); no truncating, splice, NMD, or protein-length-change consequence is reported.
Sources
PS4 VCEPNot applicable: the MSH6 InSiGHT Version 2.0 specification explicitly designates PS4 as Not Applicable. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 Version 2.0 specification explicitly marks PS4 as Not Applicable. Therefore, no generic case-control or phenotype-enrichment PS4 assessment is applied, even though the available case materials contain no variant-specific enrichment dataset.

VCEP rule
PS4: Not Applicable under the MSH6 InSiGHT Version 2.0 specification.
Evidence considered
  • The MSH6 InSiGHT Version 2.0 specification lists PS4 with applicability ‘Not Applicable.’
Sources
PM1 VCEPNot applicable: the MSH6 VCEP explicitly designates PM1 as Not Applicable for this gene. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP explicitly marks PM1 as Not Applicable. Although the variant is at residue 765, the applicable VCEP does not authorize PM1 for MSH6 under this framework. No generic PM1 substitution is permitted when a governing gene-specific specification exists.

VCEP rule
MSH6 VCEP PM1 applicability: Not Applicable.
Evidence considered
  • The governing MSH6 VCEP lists PM1 as Not Applicable, so no domain or hotspot evidence can activate PM1 under this specification.
Sources
PM4 VCEPNot applicable: the MSH6 VCEP explicitly excludes PM4, and c.2294G>C is a missense substitution without a protein-length change. Details ▾Hide ▴
Reasoning

The applicable ClinGen InSiGHT MSH6 Version 2.0 specification explicitly marks PM4 as not applicable. This variant is a missense substitution, not an in-frame deletion or insertion producing a protein-length change; no repeat-region or other qualifying length-altering consequence is reported.

VCEP rule
MSH6 VCEP Version 2.0 PM4 applicability: Not Applicable
Evidence considered
  • The MSH6 Version 2.0 VCEP criteria mark PM4 as Not Applicable.
  • The variant is annotated as missense, NP_000170.1:p.(Cys765Ser), with no in-frame indel or other protein-length change.
Sources
PM6 VCEPNot applicable: the MSH6 InSiGHT VCEP explicitly designates PM6 as not applicable and routes assumed de novo cases through PS2. Details ▾Hide ▴
Reasoning

The governing MSH6 InSiGHT VCEP explicitly marks PM6 as not applicable. Its de novo framework instead handles assumed de novo observations with unconfirmed maternity and/or paternity under PS2 at 0.5 points per proband when the specified Lynch-spectrum tumor condition is met.

VCEP rule
MSH6 InSiGHT VCEP v2.0: PM6 applicability is Not Applicable; assumed de novo cases with unconfirmed maternity and/or paternity are evaluated under PS2.
Evidence considered
  • The MSH6 InSiGHT VCEP lists PM6 as not applicable and specifies the assumed-de-novo scenario under PS2 at 0.5 points per proband.
Sources
PP2 VCEPNot applicable: the MSH6 VCEP explicitly designates PP2 as Not Applicable. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP explicitly marks PP2 as Not Applicable. Therefore the generic PP2 concept of a gene in which missense variants are a common disease mechanism is not used for this variant under the applicable specification.

VCEP rule
MSH6 VCEP PP2 applicability: Not Applicable.
Evidence considered
  • The governing MSH6 VCEP lists PP2 as Not Applicable, overriding generic ACMG/AMP use of this criterion.
Sources
PP5 VCEPNot applicable: the MSH6 specification excludes PP5, and ClinVar has no exact-variant expert-panel Pathogenic or Likely pathogenic classification. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 Version 2.0 specification explicitly marks PP5 as Not Applicable. In addition, the exact-variant ClinVar record is Uncertain significance with no expert-panel submission, so it does not satisfy the required exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic condition for PP5.

VCEP rule
PP5: Not Applicable under the MSH6 InSiGHT Version 2.0 specification; when considered generically, requires an exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic classification.
Evidence considered
  • The MSH6 InSiGHT Version 2.0 specification lists PP5 with applicability ‘Not Applicable.’
  • The exact ClinVar variant record is Uncertain significance with criteria-provided laboratory submissions and no expert-panel submission; ordinary submissions cannot trigger PP5.
Sources
BP1 VCEPNot applicable: the MSH6 VCEP explicitly designates BP1 as Not Applicable. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP explicitly marks BP1 as Not Applicable. Consequently, no benign evidence is assigned from the generic premise that truncating variants are more common than missense variants in this gene.

VCEP rule
MSH6 VCEP BP1 applicability: Not Applicable.
Evidence considered
  • The governing MSH6 VCEP lists BP1 as Not Applicable, overriding generic ACMG/AMP use of this criterion.
Sources
BP2 VCEPNot applicable: the MSH6 Version 2.0 VCEP specification explicitly designates BP2 as not applicable. Details ▾Hide ▴
Reasoning

The applicable ClinGen InSiGHT MSH6 Version 2.0 specification explicitly designates BP2 as not applicable; no BP2 assessment is therefore permitted under the governing framework.

VCEP rule
BP2: Not Applicable.
Evidence considered
  • The governing ClinGen InSiGHT MSH6 Version 2.0 specification explicitly lists BP2 as Not Applicable.
Sources
BP3 VCEPNot applicable: the MSH6 VCEP explicitly excludes BP3, and c.2294G>C is missense rather than a repeat-region in-frame indel. Details ▾Hide ▴
Reasoning

The applicable ClinGen InSiGHT MSH6 Version 2.0 specification explicitly marks BP3 as not applicable. The variant is a missense substitution rather than an in-frame deletion or insertion in a repetitive region, and no repeat-region context is reported that could support BP3 under a generic framework.

VCEP rule
MSH6 VCEP Version 2.0 BP3 applicability: Not Applicable
Evidence considered
  • The MSH6 Version 2.0 VCEP criteria mark BP3 as Not Applicable.
  • The variant is annotated as missense, NP_000170.1:p.(Cys765Ser), with no in-frame deletion or insertion and no reported repetitive-region context.
Sources
BP6 VCEPNot applicable: the MSH6 specification excludes BP6, and ClinVar has no exact-variant expert-panel Benign or Likely benign classification. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 Version 2.0 specification explicitly marks BP6 as Not Applicable. Independently, the exact-variant ClinVar record is Uncertain significance with no expert-panel submission, so no exact-variant expert-panel Benign or Likely benign classification exists to support BP6.

VCEP rule
BP6: Not Applicable under the MSH6 InSiGHT Version 2.0 specification; when considered generically, requires an exact-variant ClinVar expert-panel Benign or Likely benign classification.
Evidence considered
  • The MSH6 InSiGHT Version 2.0 specification lists BP6 with applicability ‘Not Applicable.’
  • The exact ClinVar variant record is Uncertain significance with no expert-panel submission; ordinary laboratory submissions and aggregate labels cannot trigger BP6.
Sources
BP7 N/ANot applicable: c.2294G>C causes the missense substitution p.Cys765Ser, not a synonymous or qualifying intronic change. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants or qualifying intronic variants. This variant is a missense substitution, c.2294G>C (p.Cys765Ser), so BP7 is outside its criterion scope and is not evaluated.

Evidence considered
  • The case normalization identifies NM_000179.3:c.2294G>C as NP_000170.1:p.(Cys765Ser), a missense variant.
  • The MSH6 VCEP Version 2.0 BP7 rule is limited to synonymous or qualifying intronic variants.
Sources

Identifiers

Gene
MSH6
Transcript
NM_000179.3
Coding (HGVS c.)
NM_000179.3:c.2294G>C
Protein (HGVS p.)
NP_000170.1:p.(Cys765Ser)
GRCh38
chr2:47800277 G>C
GRCh37
chr2:48027416 G>C
Location and type
Exon 4 · missense
ClinVar
4825260, 455186, 182644

Gene diagram

Every interpreted variant in MSH6, mapped onto the exon structure of NM_000179.3. Select a row to find it on the plot.

MSH6NM_000179.3
Fetching transcript structure from UCSC…
gnomAD v4.1 1 / 1,614,110 alleles AF 6.2e-07 · 0 homozygotes
gnomAD v2.1 Allele count data not recorded
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 6.2e-07 · 1 / 1,614,110 alleles · 0 hom
European (non-Finnish)1 / 1,180,010 8.5e-07
0 alternate alleles recorded in 9 other groups: Remaining individuals, Admixed American, European (Finnish), Amish, East Asian, Middle Eastern, South Asian, Ashkenazi Jewish, African/African American.

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 6.19536e-07; MAF= 0.00006%, 1/1614110 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.4745e-07; MAF= 0.00008%, 1/1180010 alleles, homozygotes = 0).

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -240 bp
0.002
SpliceAI acceptor gainat -439 bp
0.000
SpliceAI donor lossat -313 bp
0.001
SpliceAI donor gainat +14 bp
0.001
Pangolin splice lossmagnitude shown
-0.002
Pangolin splice gain
0.017

Other predictors

REVEL
0.921
BayesDel
0.498

How the predictions were used

PP3 Not met: governing MSH6 HCI prior probability is 0.4345, below the PP3 supporting threshold of >0.68. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so PP3 is within scope. The governing MSH6 VCEP specification assigns missense PP3 using the HCI prior lookup: moderate requires a prior probability >0.81 and supporting requires >0.68 and <=0.81. The exact HCI-PRIORS-MSH6 entry for c.2294G>C / p.C765S / p.C765S reports MAPP/PP2 prior probability 0.4345, below the supporting threshold; therefore PP3 is not met. The table also reports a custom PP2 score of 0.690, but that is not the governing HCI prior probability and was not substituted for it. The generic REVEL result (0.921) was not used because the MSH6 VCEP-specific missense HCI-prior rule governs this criterion.

Evidence considered
  • The ClinGen InSiGHT MSH6 VCEP Version 2.0 specification defines missense PP3 as HCI prior probability >0.81 for moderate or >0.68 and <=0.81 for supporting.
  • The exact entry in /Users/gs_agent/LYFESCI_HERMES_v9/vcep_db/MSH6/fulltext/HCI-PRIORS-MSH6.txt.txt was found for c.2294G>C and p.C765S; its table columns identify Custom_PP2_score 0.690, MAPP_score 14.04, and MAPP/PP2_Prior 0.4345.
  • The case evidence records the variant as missense, with the exact HCI prior probability 0.4345 and a REVEL score of 0.921; the VCEP-specific HCI-prior rule takes precedence over generic REVEL thresholds.
Sources
cspec ↗vcep_hci_priors_msh6hci_prior
BP4 Not met: governing MSH6 HCI prior probability is 0.4345, above the BP4 supporting threshold of <0.11. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so BP4 is within scope. The governing MSH6 VCEP specification assigns missense BP4 when the HCI prior probability is <0.11. The exact HCI-PRIORS-MSH6 entry for c.2294G>C / p.C765S reports an HCI prior probability of 0.4345, which is not below 0.11; therefore BP4 is not met. The SpliceAI max delta score of 0.002 and generic REVEL score of 0.921 were not used to override the governing VCEP-specific HCI-prior missense rule.

Evidence considered
  • The ClinGen InSiGHT MSH6 VCEP Version 2.0 specification defines missense BP4 as HCI prior probability <0.11.
  • The exact entry in /Users/gs_agent/LYFESCI_HERMES_v9/vcep_db/MSH6/fulltext/HCI-PRIORS-MSH6.txt.txt was found for c.2294G>C and p.C765S, with MAPP/PP2 prior probability 0.4345.
  • The case evidence records SpliceAI max delta 0.002 and REVEL 0.921, but neither is used to replace the governing VCEP-specific HCI-prior assessment for this missense variant.
Sources
cspec ↗vcep_hci_priors_msh6hci_prior
BP7 N/ANot applicable: c.2294G>C causes the missense substitution p.Cys765Ser, not a synonymous or qualifying intronic change. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants or qualifying intronic variants. This variant is a missense substitution, c.2294G>C (p.Cys765Ser), so BP7 is outside its criterion scope and is not evaluated.

Evidence considered
  • The case normalization identifies NM_000179.3:c.2294G>C as NP_000170.1:p.(Cys765Ser), a missense variant.
  • The MSH6 VCEP Version 2.0 BP7 rule is limited to synonymous or qualifying intronic variants.
Sources

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00). REVEL score = 0.921. BayesDel score = 0.498216. HCI prior probability for pathogenicity = 0.4345. MAPP score = 14.04. Custom PP2 score = 0.69.

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

  • American Society of Clinical Oncology Expert Statement: collection and use of a cancer family history for oncology providers.
    Lu KH et al. · 2014
    The paper does not mention MSH6 c.2294G>C or NP_000170.1:p.(C765S). It identifies MSH6 among mismatch-repair genes relevant to Lynch syndrome and describes colorectal cancer with mismatch-repair deficiency, but provides no variant-specific phenotype, tumor, enrichment, or classification evidence.
    Does not name this variant
    PMID 24493721 ↗
    Quoted passage
    Colorectal cancer demonstrating mismatch repair deficiency (via tumor studies including microsatellite instability analysis and/or immunohistochemistry, excluding known somatic causes including hypermethylation of MLH1 promoter and somatic BRAF mutation)

    Table 2; Table 3

  • Lynch Syndrome: A Primer for Urologists and Panel Recommendations.
    Mork M et al. · 2015
    The paper does not mention MSH6 c.2294G>C or p.(C765S). It discusses Lynch syndrome and MSH6-related tumor risks generally, without variant-specific phenotype, tumor, enrichment, or classification data.
    Does not name this variant
    PMID 25711197 ↗
    Quoted passage
    LS is caused by germline mutations in the MMR genes MLH1, MSH2 (and its modifier EPCAM ), MSH6 and PMS2. Pathogenic mutations in these genes lead to the accumulation of DNA errors in replicating cells, notably in microsatellite regions.

    Results, ‘LS Genetics and Neoplasm Spectrum’

  • Standards and guidelines for the interpretation of sequence variants: a joint co
    The paper does not mention MSH6 or the exact variant. Its relevant content is general ACMG/AMP guidance and does not provide variant-specific phenotype, tumor, enrichment, or classification evidence.
    Does not name this variant
    PMID 25741868 ↗
    Quoted passage
    However these are only predictions, and their use in sequence variant interpretation should be used carefully. It is not recommended that these predictions be used as the sole source of evidence to make a clinical assertion.

    Computational (In Silico) Predictive Programs

  • American Society of Clinical Oncology Policy Statement Update: Genetic and Genom
    The paper does not mention MSH6 or the specific variant. It discusses Lynch syndrome generally but provides no variant-specific phenotype, tumor, enrichment, or classification data.
    Does not name this variant
    PMID 26324357 ↗
    Quoted passage
    Identifying inherited mutations in genes such as BRCA1, BRCA2, and the genes associated with Lynch syndrome allows for interventions that can significantly reduce the development of cancer and improve survival.

    Multigene Panel Testing for Cancer Susceptibility

  • Cancer Genetics Risk Assessment and Counseling (PDQ®): Health Professional Versi
    No paper-specific finding is recorded.
    PMID 26389258 ↗
  • Sherloc: a comprehensive refinement of the ACMG-AMP variant classification crite
    The paper does not mention MSH6 or the specific variant. It describes the Sherloc classification framework but provides no variant-specific phenotype, tumor, enrichment, or classification evidence for this variant.
    Does not name this variant
    PMID 28492532 ↗
    Quoted passage
    Missense changes and in-frame deletions/insertions are given a weight of 0 points.

    Functional criteria, ‘Variant type and the expected consequence for gene products’

  • European guidelines from the EHTG and ESCP for Lynch syndrome: an updated third
    The paper does not explicitly mention MSH6 c.2294G>C or p.(C765S). It gives general Lynch syndrome and MSH6 management information, without variant-specific phenotype, tumor, enrichment, or classification data.
    Does not name this variant
    PMID 34043773 ↗
    Quoted passage
    LS is caused by inherited malfunction in one of the four MMR genes named MLH1, MSH2, MSH6 and PMS2. The malfunctioning variants are referred to as path_MLH1, path_MSH2, path_MSH6 and path_PMS2.

    Executive summary of recommendations, General information

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.19536e-07; MAF= 0.00006%, 1/1614110 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.4745e-07; MAF= 0.00008%, 1/1180010 alleles, homozygotes = 0).

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Uncertain significance (4 clinical laboratories) and as Uncertain Significance (1 clinical laboratory). (ClinVarID = 455186)

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00). REVEL score = 0.921. BayesDel score = 0.498216. HCI prior probability for pathogenicity = 0.4345. MAPP score = 14.04. Custom PP2 score = 0.69.

Functional

OncoKB did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. MSH6, a DNA mismatch repair protein, is frequently mutated in colorectal, small bowel, and endometrial cancers.

Somatic

This variant does not lie in a statistically significant hotspot. COSMIC could not be reviewed because the browser session was redirected to the login page before search results were available.

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.