0%
Print report
Variant interpretation report

MSH6 c.242C>T, p.(Ala81Val)

NM_000179.3:c.242C>T NP_000170.1:p.(Ala81Val) Missense · exon 1 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: 0 Benign evidence criteria: 1
Pathogenic criteria applied · 0

No pathogenic criterion marked as applied in the recorded assessment.

Benign criteria applied · 1
BP4Supporting
BP4 · supporting

Met, supporting: exact HCI prior 0.0035 is below the MSH6 VCEP BP4 threshold of <0.11 for missense variants.

Recorded classification: Uncertain significance

VUS: BP4 (supporting) is the only met criterion, and it does not satisfy an InSiGHT MSH6 pathogenic or benign combination rule.

02The sources

Evidence at a glance

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

gnomAD v4.1
gnomAD v2.1
Population frequency
164 / 1,439,308 alleles

gnomAD v4.1: 164 / 1,439,308 alleles. Recorded AF 0.000113944. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.4827e-05; MAF= 0.00348%, 3/86140 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.0047e-05; MAF= 0.00800%, 3/37478 alleles, homozygotes = 0); grpmax FAF= 1.591e-05.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

No screenshot for this evidence
REVEL score
0.216 recorded score

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

ClinVar submissions
12 reported laboratory submissions

7 Uncertain significance · 5 Likely benign.

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

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

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

Met Not met Not assessed Not applicable

The variant is NM_000179.3:c.242C>T, encoding NP_000170.1:p.(Ala81Val) in MSH6.

The governing InSiGHT MSH6 VCEP makes PM1, PP2, and BP1 not applicable.

No verified same-amino-acid PS1 comparator was identified, while PM5 remains unassessed because the same-residue comparator harvest was incomplete after an HTTP 429 failure.

No variant-specific functional evidence was identified that satisfies the MSH6 VCEP PS3 or BS3 rules; both criteria remain not assessed pending validated assay data.

The applicable MSH6 VCEP specification excludes PS4, PP5, and BP6.

PP4 and BP5 remain unassessed because the available exact-variant cancer observations do not include the tumor molecular findings and qualifying counts required by the VCEP rules.

No numeric threshold applies to the assessed criteria in this group; therefore no threshold inequality is applicable.

This group evaluated only PP3, BP4, and BP7. The variant is missense, making PP3 and BP4 applicable and BP7 not applicable.

The exact governing MSH6 HCI lookup entry assigns a prior probability of 0.0035, which directly meets VCEP BP4_Supporting and does not meet a VCEP PP3 threshold.

SpliceAI, REVEL, and BayesDel were not combined as independent evidence; the exact VCEP HCI assignment governs the missense PP3/BP4 call, and BayesDel lacks an applicable calibrated cutoff.

Met · 1

BP4 SupportingMet, supporting: exact HCI prior 0.0035 is below the MSH6 VCEP BP4 threshold of <0.11 for missense variants. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so BP4 is within scope. The governing MSH6 HCI-PRIORS table contains the exact entry c.242C>T / p.A81V with HCI prior probability 0.0035. The MSH6 InSiGHT VCEP directly assigns BP4_Supporting to missense variants with HCI prior probability <0.11; therefore BP4 is met at Supporting strength. REVEL 0.216 does not meet the generic BP4_Supporting threshold <=0.29, and no additional predictor is needed because the governing exact HCI lookup already assigns the criterion. The SpliceAI max delta is 0.32, but the VCEP SpliceAI BP4 alternative applies to intronic and synonymous variants, not this missense variant.

Rule
MSH6 InSiGHT VCEP BP4: missense variant with HCI prior probability <0.11 = Supporting; alternatively, for intronic or synonymous variants, SpliceAI delta <=0.1 = Supporting.
Evidence considered
  • The exact HCI-PRIORS-MSH6 table entry for c.242C>T / p.A81V assigns HCI prior probability 0.0035.
  • The MSH6 InSiGHT VCEP specifies BP4_Supporting for a missense variant with HCI prior probability <0.11.
  • REVEL score is 0.216, which is also below the supplied generic BP4_Supporting cutoff of <=0.29 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997), although the exact VCEP HCI assignment is governing.
  • SpliceAI max delta is 0.32; the MSH6 VCEP's BP4 SpliceAI alternative is for intronic and synonymous variants and is not applied to this missense variant.
Sources
vcep_hci_priors_msh6cspec ↗revelspliceai ↗

Not met · 6 · evaluated, threshold not reached

PVS1 Not met: NM_000179.3:c.242C>T is a missense variant producing p.(Ala81Val), outside the MSH6 VCEP PVS1 null-variant categories. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, NM_000179.3:c.242C>T (NP_000170.1:p.(Ala81Val)), in the preferred MSH6 transcript. The MSH6 InSiGHT VCEP PVS1 specification applies to nonsense/frameshift variants, qualifying large genomic alterations, canonical splice-site variants with the specified transcript consequences, and qualifying RNA-confirmed splicing aberrations; it does not apply to this missense variant. No PVS1 null-variant consequence, NMD assessment, exon-skipping event, or protein truncation is established.

Rule
MSH6 InSiGHT VCEP Version 2.0 PVS1 rule: qualifying nonsense/frameshift, large genomic alteration, canonical splice-site, or specified RNA-confirmed splicing consequences; not applicable to a missense substitution.
Evidence considered
  • The preferred transcript is NM_000179.3 and the predicted consequence is missense, p.(Ala81Val).
  • The MSH6 InSiGHT VCEP PVS1 specification defines PVS1 for qualifying nonsense/frameshift, large genomic alteration, canonical splice, and specified RNA-confirmed splicing consequences; missense variants are not included.
  • The case-level PVS1 assessment records no applicable generic null-variant bucket and identifies the consequence as missense.
Sources
cspec ↗pvs1_variant_assessment
PS1 Not met: no documented VCEP-Pathogenic alternate nucleotide change producing the same p.Ala81Val substitution was identified. Details ▾Hide ▴
Reasoning

The MSH6 VCEP PS1 rule requires a different nucleotide change producing the same amino-acid substitution, established by the VCEP as Pathogenic, or an equivalent splice-nucleotide scenario. The case variant is NM_000179.3:c.242C>T (NP_000170.1:p.(Ala81Val)); the collected ClinVar and literature evidence contains no documented pathogenic comparator for the same amino-acid change, and the available paper extractions do not mention this variant or an applicable same-amino-acid comparator. Therefore PS1 is not met.

Rule
A predicted missense substitution that encodes the same amino acid change with a different underlying nucleotide change previously established by this VCEP as Pathogenic (not a predicted or confirmed splice defect).
Evidence considered
  • The governing MSH6 VCEP defines PS1 as a different nucleotide change encoding the same amino-acid change previously established by the VCEP as Pathogenic, excluding predicted or confirmed splice defects.
  • The queried variant is NM_000179.3:c.242C>T, encoding NP_000170.1:p.(Ala81Val).
  • The collected ClinVar record and reviewed paper extractions provide no documented VCEP-Pathogenic alternate nucleotide change producing p.Ala81Val; the extracted papers do not explicitly mention c.242C>T or p.(A81V).
Sources
PM2 Not met: gnomAD v4.1 total AF is 0.000113943645, exceeding the MSH6 PM2 threshold of <0.00002. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 Version 2.0 specification defines PM2 Supporting as absent or extremely rare in gnomAD v4, with allele frequency <0.00002 (<1 in 50,000 alleles). gnomAD v4.1 reports total AF 0.000113943645 (164/1,439,308 alleles), grpmax FAF 0.00012624, and highest population AF 0.000145039 in Europeans (non-Finnish); all exceed 0.00002. The non-cancer subset is not the governing source for this VCEP rule.

Rule
Absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4 dataset.
Evidence considered
  • InSiGHT MSH6 Version 2.0 specifies PM2 Supporting for gnomAD v4 allele frequency <0.00002 (<1 in 50,000 alleles).
  • gnomAD v4.1 reports total AF 0.000113943645 from 164 of 1,439,308 alleles, grpmax FAF 0.00012624, and highest population AF 0.000145039 in Europeans (non-Finnish), all above 0.00002.
  • The VCEP explicitly names gnomAD v4, so the available gnomAD v2.1 and non-cancer subset values do not replace the governing gnomAD v4 assessment.
Sources
PP3 Not met: HCI prior 0.0035 is below the MSH6 VCEP PP3 threshold of >0.68, and REVEL 0.216 is below the generic 0.644 threshold. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so PP3 is within scope. The governing InSiGHT MSH6 VCEP specifies PP3_Moderate for an HCI prior probability >0.81 and PP3_Supporting for a probability >0.68 and <=0.81; the exact HCI lookup entry for c.242C>T / p.A81V assigns 0.0035, which does not meet either PP3 threshold. REVEL is 0.216, below the supplied generic PP3_Supporting threshold of 0.644 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997). The VCEP's SpliceAI PP3 rule is limited to predicted splice defects at non-canonical splicing nucleotides, whereas this is a coding missense variant; therefore the SpliceAI max delta of 0.32 is not applied to PP3. BayesDel (-0.293941) has no established generic ACMG strength calibration and the MSH6 VCEP does not specify a BayesDel cutoff.

Rule
MSH6 InSiGHT VCEP PP3: HCI prior probability >0.81 = Moderate; >0.68 and <=0.81 = Supporting; alternatively SpliceAI delta >=0.2 only for predicted splice defects at non-canonical splicing nucleotides.
Evidence considered
  • The exact HCI-PRIORS-MSH6 table entry for c.242C>T / p.A81V assigns HCI prior probability 0.0035; the governing MSH6 VCEP thresholds are >0.81 for PP3_Moderate and >0.68 to <=0.81 for PP3_Supporting.
  • The MSH6 InSiGHT VCEP PP3 SpliceAI alternative is specified for predicted splice defects at non-canonical splicing nucleotides; c.242C>T is a coding missense substitution, so its SpliceAI result is not used for PP3.
  • REVEL score is 0.216, below the supplied generic PP3_Supporting cutoff of 0.644 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997).
  • BayesDel score is -0.293941; no generic ACMG strength calibration is established and the governing MSH6 VCEP provides no BayesDel cutoff.
Sources
vcep_hci_priors_msh6cspec ↗revelbayesdel
BA1 Not met: gnomAD v4.1 grpmax FAF is 0.00012624, below the MSH6 BA1 threshold of 0.0022. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 Version 2.0 specification requires gnomAD v4 grpmax filtering allele frequency >=0.0022 (0.22%) for BA1, with exclusion of a founder pathogenic variant. gnomAD v4.1 reports a grpmax FAF of 0.00012624 (0.012624%), total AF 0.000113943645, and 164/1,439,308 alleles; this is below the BA1 threshold. No founder pathogenic-variant exception is needed to reach the threshold.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.0022 (0.22%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • InSiGHT MSH6 Version 2.0 specifies BA1 at gnomAD v4 grpmax FAF >=0.0022 (0.22%) and requires exclusion of a founder pathogenic variant.
  • gnomAD v4.1 reports grpmax FAF 0.00012624 (0.012624%), total AF 0.000113943645, and 164 of 1,439,308 alleles for NM_000179.3:c.242C>T (p.Ala81Val).
Sources
BS1 Not met: gnomAD v4.1 grpmax FAF is 0.00012624, below the MSH6 BS1 lower boundary of 0.00022. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 Version 2.0 specification requires gnomAD v4 grpmax filtering allele frequency >=0.00022 and <0.0022 (0.022%-0.22%) for BS1, with exclusion of a founder pathogenic variant. gnomAD v4.1 reports a grpmax FAF of 0.00012624 (0.012624%), which is below the lower BS1 boundary; therefore the criterion is 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
  • InSiGHT MSH6 Version 2.0 specifies BS1 at gnomAD v4 grpmax FAF >=0.00022 and <0.0022 (0.022%-0.22%), with exclusion of a founder pathogenic variant.
  • gnomAD v4.1 reports grpmax FAF 0.00012624 (0.012624%), below 0.00022.
Sources

Not assessed · 10 · no assessment recorded

PS2 Not assessed: no documented de novo observation with maternity and paternity confirmation or variant-specific tumor evidence is available for this variant. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP PS2 rule is applicable and assigns 2 points per proband when a de novo variant is documented with confirmed maternity and paternity in a proband with an MMR-deficient Lynch-spectrum tumor, 1 point when maternity and paternity are confirmed without tumor MSI/IHC/methylation data, or 0.5 points when de novo status is assumed and one or both parents are unconfirmed. The available case evidence does not document a proband, parental testing, maternity or paternity confirmation, de novo observation, or a variant-specific Lynch-spectrum tumor result for NM_000179.3:c.242C>T (p.Ala81Val); therefore no PS2 points or strength can be assigned.

Rule
Proband with a de novo variant with both maternity and paternity confirmed in a case with MMR deficient LS spectrum tumor receives 2 points; with both maternity and paternity confirmed but no tumor MSI/IHC/methylation data, 1 point; with assumed de novo status and maternity and/or paternity unconfirmed, 0.5 points. PS2 strength is Very Strong for >=4 points, Strong for 2-3.5 points, Moderate for 1-1.5 points, and Supporting for 0.5 points.
Evidence considered
  • The MSH6 InSiGHT VCEP Version 2.0 specifies PS2 point assignments of 2, 1, or 0.5 based on confirmed parental relationships, tumor evidence, and assumed de novo status.
  • The case evidence contains no documented variant-specific proband de novo finding, parental testing, maternity or paternity confirmation, or Lynch-spectrum tumor MSI/IHC/methylation result.
Still missing
  • A documented proband with the variant is needed.
  • Parental testing and explicit maternity and paternity confirmation are needed to establish de novo status.
  • Variant-specific Lynch-spectrum tumor MSI/IHC and methylation results are needed for the 2-point PS2 category.
Sources
PS3 Not assessed: no variant-specific functional assay result or calibrated pathogenicity odds are available for MSH6 c.242C>T. Details ▾Hide ▴
Reasoning

The 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 following its functional-assay flowchart. The available variant-specific literature review identified no assay result for NM_000179.3:c.242C>T (NP_000170.1:p.(Ala81Val)); the reviewed papers either did not mention the variant or provided only general classification methodology. No calibrated functional odds, validated assay result, assay controls, or flowchart-resolvable MMR defect are available, so PS3 cannot be applied.

Rule
Calibrated functional assays with functional odds for pathogenicity > 18.7 (Strong); >4.3 and <=18.7 (Moderate); >2.08 and <=4.3 (Supporting); or MMR function defect following the functional assay flowchart.
Evidence considered
  • The MSH6 VCEP PS3 thresholds are calibrated functional odds for pathogenicity >18.7 for strong, >4.3 and <=18.7 for moderate, and >2.08 and <=4.3 for supporting evidence.
  • The MSH6 VCEP functional-assay flowchart requires an assay pathway capable of establishing an MMR function defect; no such variant-specific result is documented here.
  • The reviewed paper with PMID:26467025 describes a general variant-scoring system and does not report MSH6 c.242C>T or a variant-specific functional assay result.
  • The reviewed paper with PMID:27363726 evaluates a clinical history-weighting algorithm and does not report MSH6 c.242C>T or a variant-specific functional assay result.
Still missing
  • A validated, variant-specific MSH6 functional assay with appropriate controls and a calibrated functional odds estimate is needed.
  • Alternatively, two concordant functional assays sufficient to demonstrate an MMR function defect under the MSH6 VCEP flowchart are needed.
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchartPMID:26467025 ↗PMID:27363726 ↗
PM3 Not assessed: no qualifying affected-proband biallelic observation or documented cis/trans phase was available to assign the MSH6 PM3 point thresholds. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT MSH6 Version 2.0 specification defines PM3 using calibrated biallelic evidence points: 0.5 points for Supporting, 1–1.5 for Moderate, 2–3.5 for Strong, and ≥4 for Very Strong. The available case evidence contains no qualifying affected-proband observation with a second pathogenic or likely pathogenic MSH6 variant, no documented cis/trans phase, and no confirmed biallelic inheritance for NM_000179.3:c.242C>T (p.Ala81Val), so a PM3 point score cannot be assigned.

Rule
MSH6 VCEP PM3: ≥4 points = Very Strong; 2–3.5 points = Strong; 1–1.5 points = Moderate; 0.5 points = Supporting.
Evidence considered
  • The MSH6 Version 2.0 VCEP specifies PM3 strengths by biallelic evidence points: 0.5 points for Supporting, 1–1.5 for Moderate, 2–3.5 for Strong, and ≥4 for Very Strong.
  • No case-specific affected-proband, second pathogenic-variant, homozygosity, or cis/trans-phase observation was identified for NM_000179.3:c.242C>T (p.Ala81Val).
Still missing
  • A documented affected proband with a second pathogenic or likely pathogenic MSH6 variant is absent.
  • Phase information establishing the variants are in trans, or evidence of homozygosity, is absent.
  • No PM3 point score can therefore be calculated under the MSH6 VCEP framework.
Sources
PM5 Not assessed: 0 same-residue candidates were available, but comparator harvesting ended with an HTTP 429 failure, leaving PM5 evidence incomplete. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP requires a different missense change at the same amino-acid residue that is Pathogenic or Likely Pathogenic at the protein level and not due to aberrant splicing; PM5 also requires PP3 Supporting for the queried missense variant. The queried residue is Ala81, but the available PM5 comparator artifact reports 0 same-residue candidates among 9 candidates seen and records an HTTP 429 soft failure during harvesting. Because the comparator search was incomplete and no verified same-residue classification is available, PM5 cannot be reliably adjudicated from the collected evidence.

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. Only use PM5 if PP3 is supporting for the missense change. Use PM5_Supporting if the other variant is Likely Pathogenic due to a missense alteration.
Evidence considered
  • The governing MSH6 VCEP requires a different missense change at the same amino-acid residue, classified Pathogenic or Likely Pathogenic at the protein level and not due to aberrant splicing; PM5 use also requires PP3 Supporting for the queried missense change.
  • The queried variant is NP_000170.1:p.(Ala81Val), affecting residue Ala81.
  • The PM5 comparator artifact reports 9 candidates seen but 0 same-residue candidates, with no expert-panel or non-expert-majority Pathogenic/Likely Pathogenic comparator and an HTTP 429 harvesting error.
Still missing
  • A complete, independently verified search for alternate missense substitutions at MSH6 residue Ala81 with VCEP Pathogenic or Likely Pathogenic protein-level classification is required.
  • The governing PM5 rule requires PP3 Supporting for the queried missense variant; this group does not adjudicate PP3.
Sources
cspec ↗pm5_candidates
PP1 Not assessed: no pedigree segregation data or combined Bayes likelihood ratio is reported, so the VCEP thresholds >2.08, >4.3, and >18.7 cannot be evaluated. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP requires co-segregation to be evaluated using the combined Bayes likelihood ratio, multiplying results across multiple pedigrees. It assigns PP1 Supporting for a combined Bayes likelihood ratio >2.08 and <=4.3, Moderate for >4.3 and <=18.7, and Strong for >18.7 in at least two families. No affected or unaffected relatives, meioses, pedigree information, segregation testing, or calculated Bayes likelihood ratio is documented for NM_000179.3:c.242C>T (p.Ala81Val), so PP1 cannot be assessed.

Rule
Co-segregation with disease in pedigrees has PP1 Supporting strength for a combined Bayes likelihood ratio >2.08 and <=4.3, Moderate for >4.3 and <=18.7, and Strong for >18.7 in at least two families; results from multiple pedigrees are multiplied together.
Evidence considered
  • The MSH6 InSiGHT VCEP specifies PP1 Supporting for a combined Bayes likelihood ratio >2.08 and <=4.3, Moderate for >4.3 and <=18.7, and Strong for >18.7 in at least two families.
  • The case evidence provides no variant-specific pedigree, affected-relative segregation, unaffected-relative testing, meiosis count, or combined Bayes likelihood ratio.
Still missing
  • A pedigree with affected and unaffected relatives is needed.
  • Variant testing results for informative relatives and the number of informative meioses are needed.
  • A combined Bayes likelihood ratio calculated under the VCEP-recommended approach is needed.
Sources
PP4 Not assessed: exact-variant cancer observations lack the required MSI-H, tumor-genome, or MSH6-consistent IHC findings and qualifying tumor count. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP requires tumor-specific phenotype evidence: 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 for PP4 supporting; two independent tumors for moderate; or at least three independent tumors in at least two families for strong. The available exact-variant ClinVar trail reports observation in ovarian and colorectal cancer but does not document MSI status, IHC protein loss, tumor-genome testing, or the number and independence of qualifying tumors. Therefore the PP4 rule cannot be applied from the available evidence.

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 qualifying tumors. Strong: >=3 independent qualifying tumors in >=2 families.
Evidence considered
  • The VCEP PP4 supporting rule requires one CRC or endometrial MSI-H tumor with a standard marker panel or tumor genome and/or MMR protein loss consistent with the variant location; the moderate and strong rules require two or at least three qualifying independent tumors, respectively.
  • An exact-variant ClinVar submission signal reports c.242C>T in an individual with ovarian cancer and an individual with colorectal cancer, but the available record does not provide the required MSI, tumor-genome, IHC, or qualifying-count details.
  • PMID:23047549 describes an ovarian-cancer cohort and does not explicitly mention MSH6 c.242C>T or p.(A81V).
Still missing
  • Variant-specific MSI status or tumor-genome results are unavailable.
  • Variant-specific MMR immunohistochemistry results consistent with MSH6 loss are unavailable.
  • The number, independence, and family distribution of qualifying CRC or endometrial tumors are not documented.
Sources
BS2 Not assessed: no documented MSH6 pathogenic-variant co-occurrence in trans with qualifying cancer age, CMMRD assessment, and confirmed phase. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 Version 2.0 specification limits BS2 Strong to 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 CMMRD; phase must be confirmed through parental or offspring testing. The available population data show zero homozygotes but do not document the required individual-level co-occurrence, phenotype, age, CMMRD assessment, or phase confirmation.

Rule
Co-occurrence in trans with a known pathogenic sequence variant in the same gene in a patient with colorectal cancer after age 45 (or other LS cancer above the median age of onset for that cancer in LS), and who has no previous or current evidence of clinical manifestations of CMMRD; confirmation of phase requires testing of parents or offspring.
Evidence considered
  • InSiGHT MSH6 Version 2.0 requires BS2 Strong co-occurrence in trans with a known pathogenic variant in the same gene in a qualifying cancer patient, absence of CMMRD manifestations, and phase confirmation through parents or offspring.
  • gnomAD v4.1 reports zero homozygotes, but this population summary is not evidence of the VCEP's required individual-level co-occurrence scenario.
Still missing
  • Individual-level co-occurrence in trans with a known pathogenic MSH6 sequence variant is not documented.
  • Qualifying colorectal or other Lynch-syndrome cancer age, absence of CMMRD manifestations, and parental or offspring phase confirmation are not documented.
Sources
BS3 Not assessed: no variant-specific proficient-function assay result or calibrated benign functional odds are available for MSH6 c.242C>T. Details ▾Hide ▴
Reasoning

The MSH6 VCEP permits BS3 strong for calibrated functional assays with functional odds for pathogenicity <=0.05, and BS3 supporting for calibrated functional odds >0.05 and <=0.48 or variant-specific proficient function in protein and mRNA-based assays following the MMR functional-assay flowchart. The available variant-specific literature review identified no assay result for NM_000179.3:c.242C>T (NP_000170.1:p.(Ala81Val)); the reviewed papers either did not mention the variant or provided only general classification methodology. No calibrated benign functional odds, validated proficient-function assay, assay controls, or flowchart-resolvable benign result are available, so BS3 cannot be applied.

Rule
Calibrated functional assays with functional odds for pathogenicity <=0.05 (Strong) or >0.05 and <=0.48 (Supporting); alternatively, variant-specific proficient function in protein and mRNA-based assays following the MMR functional assay flowchart.
Evidence considered
  • The MSH6 VCEP BS3 thresholds are calibrated functional odds for pathogenicity <=0.05 for strong and >0.05 and <=0.48 for supporting evidence.
  • The MSH6 VCEP also allows BS3 supporting for variant-specific proficient protein and mRNA function evaluated through its functional-assay flowchart, but no such result is documented here.
  • The reviewed paper with PMID:26467025 describes a general variant-scoring system and does not report MSH6 c.242C>T or a variant-specific benign functional assay result.
  • The reviewed paper with PMID:27363726 evaluates a clinical history-weighting algorithm and does not report MSH6 c.242C>T or a variant-specific benign functional assay result.
Still missing
  • A validated, variant-specific MSH6 functional assay with appropriate wild-type, deficient, and other relevant controls is needed.
  • A calibrated functional odds estimate <=0.48, or variant-specific proficient protein and mRNA function under the MSH6 VCEP flowchart, is needed.
Sources
cspec ↗vcep_functional_assay_svi_documentation_mmrvcep_functional_assay_flowchartPMID:26467025 ↗PMID:27363726 ↗
BS4 Not assessed: no non-segregation observations or combined Bayes likelihood ratio is reported, so the BS4 thresholds <0.05 and 0.05-0.48 cannot be evaluated. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP assigns BS4 Supporting strength for lack of co-segregation with a combined Bayes likelihood ratio >0.05 and <=0.48, and Strong strength for a combined Bayes likelihood ratio <0.05. No variant-negative affected relatives, discordant pedigree observations, non-segregation testing, or combined Bayes likelihood ratio is documented for NM_000179.3:c.242C>T (p.Ala81Val), so BS4 cannot be assessed.

Rule
Lack of co-segregation with disease has BS4 Strong strength for a combined Bayes likelihood ratio <0.05 and Supporting strength for a combined Bayes likelihood ratio >0.05 and <=0.48.
Evidence considered
  • The MSH6 InSiGHT VCEP specifies BS4 Strong for a combined Bayes likelihood ratio <0.05 and Supporting for >0.05 and <=0.48.
  • The case evidence provides no variant-specific non-segregation observation, discordant relative testing, pedigree data, or combined Bayes likelihood ratio.
Still missing
  • A pedigree containing informative affected or unaffected relatives with discordant variant status is needed.
  • Variant testing results for relatives who do not show expected co-segregation are needed.
  • A combined Bayes likelihood ratio for lack of co-segregation is needed.
Sources
BP5 Not assessed: no variant-specific MSS, MMR-IHC inconsistency, BRAF V600E, MLH1 methylation, or qualifying tumor count is documented. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP permits BP5 supporting for 2 or 3 tumors with MSS and/or no loss of MMR protein expression and/or an LS-spectrum tumor with MMR protein loss inconsistent with MSH6, or for one BRAF V600E colon tumor or one MLH1-methylated LS-spectrum tumor with MSI-H/MLH1 loss; BP5 strong requires at least 4 tumors or at least 2 such BRAF/methylation findings. No variant-specific tumor MSS, IHC, BRAF V600E, MLH1 methylation, or qualifying tumor-count evidence is available, so BP5 cannot be assessed.

Rule
Supporting: 2 or 3 tumors with MSS and/or no loss of MMR protein expression and/or inconsistent LS-spectrum MMR protein loss, or 1 BRAF V600E/MLH1-methylation finding with MSI-H/MLH1 loss. Strong: >=4 tumors or >=2 BRAF V600E/MLH1-methylation findings.
Evidence considered
  • The VCEP BP5 supporting rule requires 2 or 3 qualifying tumors with MSS and/or no MMR protein loss, or one qualifying BRAF V600E or MLH1-methylation finding; the strong rule requires >=4 tumors or >=2 such molecular findings.
  • The exact-variant evidence only indicates ovarian and colorectal cancer observations without the tumor molecular details required by the VCEP BP5 rule.
Still missing
  • Variant-specific tumor MSS/MSI results and MMR immunohistochemistry are unavailable.
  • Variant-specific BRAF V600E or MLH1 methylation results are unavailable.
  • The number and independence of potentially qualifying tumors are not documented.
Sources
Not applicable · 11· recorded as not applicable Show reasons ▾Hide reasons ▴
PS4 VCEPNot applicable: the MSH6 VCEP specification explicitly excludes PS4 from MMR variant classification using proband counting. Details ▾Hide ▴
Reasoning

The governing MSH6 InSiGHT VCEP specification marks PS4 as not applicable and states: "Due to the availability of tumor IHC data for variant classification (see PP4), PS4 has not been utilized for MMR variant classification using proband counting." The specification therefore precludes PS4 for this MSH6 assessment, regardless of the available literature or ClinVar submission history.

VCEP rule
Not applicable; the VCEP states that PS4 has not been utilized for MMR variant classification using proband counting because tumor IHC data are available for classification.
Evidence considered
  • The MSH6 InSiGHT VCEP Version 2.0 marks PS4 as not applicable and explicitly states that PS4 is not used for MMR variant classification using proband counting.
Sources
PM1 VCEPNot applicable: the MSH6 VCEP explicitly marks PM1 Not Applicable, and no approved domain-table entry is present for residue 81. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP explicitly marks PM1 as Not Applicable. In addition, vcep_materials.json contains an empty domain_tables object, so there is no authoritative approved MSH6 critical-domain entry in that field against which residue 81 could be matched. PM1 is therefore not applicable under the governing framework.

VCEP rule
PM1 is not applicable under the governing MSH6 VCEP specification.
Evidence considered
  • The governing InSiGHT MSH6 VCEP lists PM1 with applicability Not Applicable.
  • The authoritative vcep_materials.json domain_tables field is empty; no approved MSH6 functional-domain interval is available there for residue 81.
  • The variant encodes p.Ala81Val, so residue 81 was the relevant domain-table position to check.
Sources
cspec ↗vcep_mmr_functional_domains
PM4 VCEPNot applicable: the MSH6 VCEP explicitly excludes PM4, and this variant causes a missense substitution without a protein-length change. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP Version 2.0 explicitly designates PM4 as not applicable. This variant is a missense substitution, p.(Ala81Val), and there is no established in-frame insertion/deletion or other protein-length change to evaluate under PM4.

VCEP rule
MSH6 InSiGHT VCEP Version 2.0: PM4 not applicable.
Evidence considered
  • The MSH6 InSiGHT VCEP Version 2.0 lists PM4 as Not Applicable.
  • NM_000179.3:c.242C>T is a missense variant encoding p.(Ala81Val), not an in-frame indel or other protein-length alteration.
Sources
PM6 VCEPNot applicable: the MSH6 InSiGHT VCEP Version 2.0 explicitly designates PM6 as not applicable. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP Version 2.0 explicitly designates PM6 as not applicable. The criterion is therefore not used, regardless of whether an unconfirmed de novo observation is present.

VCEP rule
PM6 is not applicable under the MSH6 InSiGHT VCEP Version 2.0.
Evidence considered
  • The MSH6 InSiGHT VCEP Version 2.0 lists PM6 as not applicable and provides no PM6 evidence rule for this gene-specific framework.
Sources
PP2 VCEPNot applicable: the governing MSH6 VCEP explicitly marks PP2 Not Applicable. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP explicitly marks PP2 as Not Applicable. No generic PP2 assessment is substituted because an applicable gene-specific specification takes precedence.

VCEP rule
PP2 is not applicable under the governing MSH6 VCEP specification.
Evidence considered
  • The governing InSiGHT MSH6 VCEP lists PP2 with applicability Not Applicable, so generic PP2 is not applied.
Sources
PP5 VCEPNot applicable: the MSH6 VCEP excludes PP5, and ClinVar has zero exact-variant expert-panel submissions. Details ▾Hide ▴
Reasoning

The governing MSH6 InSiGHT VCEP marks PP5 as not applicable and states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. In addition, the exact-variant ClinVar record has zero expert-panel submissions and contains only ordinary laboratory submissions, so no permitted expert-panel pathogenic or likely pathogenic assertion exists.

VCEP rule
Not applicable for this VCEP; PP5 is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The MSH6 VCEP Version 2.0 marks PP5 not applicable and says it is not for use.
  • The exact-variant ClinVar audit reports zero expert-panel submissions; available submissions are ordinary laboratory assertions and include uncertain-significance or likely-benign classifications, not an expert-panel pathogenic or likely pathogenic classification.
Sources
BP1 VCEPNot applicable: the governing MSH6 VCEP explicitly marks BP1 Not Applicable. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP explicitly marks BP1 as Not Applicable. No generic BP1 assessment is substituted because an applicable gene-specific specification takes precedence.

VCEP rule
BP1 is not applicable under the governing MSH6 VCEP specification.
Evidence considered
  • The governing InSiGHT MSH6 VCEP lists BP1 with applicability Not Applicable, so generic BP1 is not applied.
Sources
BP2 VCEPNot applicable: the MSH6 Version 2.0 VCEP explicitly excludes BP2, so no co-occurrence threshold is applied. Details ▾Hide ▴
Reasoning

The ClinGen InSiGHT MSH6 Version 2.0 specification explicitly lists BP2 as not applicable. Therefore, BP2 is not evaluated for NM_000179.3:c.242C>T (p.Ala81Val), regardless of whether any co-occurrence or phase information is available.

VCEP rule
MSH6 VCEP BP2: Not Applicable.
Evidence considered
  • The MSH6 Version 2.0 VCEP explicitly marks BP2 as Not Applicable.
Sources
BP3 VCEPNot applicable: the MSH6 VCEP explicitly excludes BP3, and this missense variant does not create an in-frame repeat-region deletion. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT VCEP Version 2.0 explicitly designates BP3 as not applicable. This variant is a missense substitution, p.(Ala81Val), rather than an in-frame deletion in a repetitive region, and no repeat-region protein-length alteration is established.

VCEP rule
MSH6 InSiGHT VCEP Version 2.0: BP3 not applicable.
Evidence considered
  • The MSH6 InSiGHT VCEP Version 2.0 lists BP3 as Not Applicable.
  • NM_000179.3:c.242C>T is a missense variant encoding p.(Ala81Val), with no documented in-frame deletion or repeat-region protein-length change.
Sources
BP6 VCEPNot applicable: the MSH6 VCEP excludes BP6, and ClinVar has no exact-variant expert-panel benign assertion. Details ▾Hide ▴
Reasoning

The governing MSH6 InSiGHT VCEP marks BP6 as not applicable and states that it is not for use. Independently, the exact-variant ClinVar audit reports zero expert-panel submissions; therefore ordinary laboratory likely-benign submissions and the aggregate ClinVar label cannot trigger BP6 under the specified evidence policy.

VCEP rule
Not applicable for this VCEP; BP6 is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The MSH6 VCEP Version 2.0 marks BP6 not applicable and says it is not for use.
  • The exact-variant ClinVar audit reports zero expert-panel submissions; likely-benign classifications are from ordinary laboratory submissions and cannot satisfy the expert-panel requirement.
Sources
BP7 N/ANot applicable: c.242C>T changes Ala81 to Val and is missense, whereas BP7 is limited to synonymous or qualifying intronic variants. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants, with the MSH6 VCEP also allowing specified intronic variants. NM_000179.3:c.242C>T produces NP_000170.1:p.(Ala81Val), a missense substitution, so BP7 is outside its criterion scope and is not evaluated.

Rule
MSH6 InSiGHT VCEP BP7: synonymous or intronic variant at or beyond -21/+7 of an exon; not applicable to missense variants.
Evidence considered
  • The case normalization identifies NM_000179.3:c.242C>T as NP_000170.1:p.(Ala81Val) / p.(A81V), a missense variant.
  • The MSH6 InSiGHT VCEP BP7 rule applies to synonymous or specified intronic variants, not missense substitutions.
Sources

Identifiers

Gene
MSH6
Transcript
NM_000179.3
Coding (HGVS c.)
NM_000179.3:c.242C>T
Protein (HGVS p.)
NP_000170.1:p.(Ala81Val)
GRCh38
chr2:47783475 C>T
GRCh37
chr2:48010614 C>T
Location and type
Exon 1 · missense
ClinVar
1731649, 127571

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 164 / 1,439,308 alleles AF 0.000114 · 0 homozygotes · FAF 0.000126
gnomAD v2.1 3 / 86,140 alleles AF 3.48e-05 · 0 homozygotes · FAF 1.59e-05
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 0.00011 · 164 / 1,439,308 alleles · 0 hom · FAF 0.00013
European (non-Finnish)159 / 1,096,258 0.00015
African/African American3 / 66,738 4.5e-05
Remaining individuals2 / 55,154 3.6e-05
0 alternate alleles recorded in 7 other groups: Admixed American, European (Finnish), Amish, East Asian, Middle Eastern, South Asian, Ashkenazi Jewish.

gnomAD v2.1

AF 3.5e-05 · 3 / 86,140 alleles · 0 hom · FAF 1.6e-05
European (non-Finnish)3 / 37,478 8e-05
0 alternate alleles recorded in 7 other groups: African/African American, Admixed American, Ashkenazi Jewish, East Asian, European (Finnish), Remaining individuals, South Asian.

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 0.000113944; MAF= 0.01139%, 164/1439308 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 0.000145039; MAF= 0.01450%, 159/1096258 alleles, homozygotes = 0); grpmax FAF= 0.00012624.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.4827e-05; MAF= 0.00348%, 3/86140 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.0047e-05; MAF= 0.00800%, 3/37478 alleles, homozygotes = 0); grpmax FAF= 1.591e-05.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat +203 bp
0.000
SpliceAI acceptor gainat -108 bp
0.000
SpliceAI donor lossat +18 bp
0.006
SpliceAI donor gainat -5 bp
0.320
Pangolin splice lossmagnitude shown
-0.070
Pangolin splice gain
0.180

Other predictors

REVEL
0.216
BayesDel
-0.294

How the predictions were used

BP4 SupportingMet, supporting: exact HCI prior 0.0035 is below the MSH6 VCEP BP4 threshold of <0.11 for missense variants. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so BP4 is within scope. The governing MSH6 HCI-PRIORS table contains the exact entry c.242C>T / p.A81V with HCI prior probability 0.0035. The MSH6 InSiGHT VCEP directly assigns BP4_Supporting to missense variants with HCI prior probability <0.11; therefore BP4 is met at Supporting strength. REVEL 0.216 does not meet the generic BP4_Supporting threshold <=0.29, and no additional predictor is needed because the governing exact HCI lookup already assigns the criterion. The SpliceAI max delta is 0.32, but the VCEP SpliceAI BP4 alternative applies to intronic and synonymous variants, not this missense variant.

Rule
MSH6 InSiGHT VCEP BP4: missense variant with HCI prior probability <0.11 = Supporting; alternatively, for intronic or synonymous variants, SpliceAI delta <=0.1 = Supporting.
Evidence considered
  • The exact HCI-PRIORS-MSH6 table entry for c.242C>T / p.A81V assigns HCI prior probability 0.0035.
  • The MSH6 InSiGHT VCEP specifies BP4_Supporting for a missense variant with HCI prior probability <0.11.
  • REVEL score is 0.216, which is also below the supplied generic BP4_Supporting cutoff of <=0.29 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997), although the exact VCEP HCI assignment is governing.
  • SpliceAI max delta is 0.32; the MSH6 VCEP's BP4 SpliceAI alternative is for intronic and synonymous variants and is not applied to this missense variant.
Sources
vcep_hci_priors_msh6cspec ↗revelspliceai ↗
PP3 Not met: HCI prior 0.0035 is below the MSH6 VCEP PP3 threshold of >0.68, and REVEL 0.216 is below the generic 0.644 threshold. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, so PP3 is within scope. The governing InSiGHT MSH6 VCEP specifies PP3_Moderate for an HCI prior probability >0.81 and PP3_Supporting for a probability >0.68 and <=0.81; the exact HCI lookup entry for c.242C>T / p.A81V assigns 0.0035, which does not meet either PP3 threshold. REVEL is 0.216, below the supplied generic PP3_Supporting threshold of 0.644 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997). The VCEP's SpliceAI PP3 rule is limited to predicted splice defects at non-canonical splicing nucleotides, whereas this is a coding missense variant; therefore the SpliceAI max delta of 0.32 is not applied to PP3. BayesDel (-0.293941) has no established generic ACMG strength calibration and the MSH6 VCEP does not specify a BayesDel cutoff.

Rule
MSH6 InSiGHT VCEP PP3: HCI prior probability >0.81 = Moderate; >0.68 and <=0.81 = Supporting; alternatively SpliceAI delta >=0.2 only for predicted splice defects at non-canonical splicing nucleotides.
Evidence considered
  • The exact HCI-PRIORS-MSH6 table entry for c.242C>T / p.A81V assigns HCI prior probability 0.0035; the governing MSH6 VCEP thresholds are >0.81 for PP3_Moderate and >0.68 to <=0.81 for PP3_Supporting.
  • The MSH6 InSiGHT VCEP PP3 SpliceAI alternative is specified for predicted splice defects at non-canonical splicing nucleotides; c.242C>T is a coding missense substitution, so its SpliceAI result is not used for PP3.
  • REVEL score is 0.216, below the supplied generic PP3_Supporting cutoff of 0.644 from the ClinGen SVI REVEL calibration (Pejaver et al. 2022, PMID:36413997).
  • BayesDel score is -0.293941; no generic ACMG strength calibration is established and the governing MSH6 VCEP provides no BayesDel cutoff.
Sources
vcep_hci_priors_msh6cspec ↗revelbayesdel
BP7 N/ANot applicable: c.242C>T changes Ala81 to Val and is missense, whereas BP7 is limited to synonymous or qualifying intronic variants. Details ▾Hide ▴
Reasoning

BP7 applies only to synonymous variants, with the MSH6 VCEP also allowing specified intronic variants. NM_000179.3:c.242C>T produces NP_000170.1:p.(Ala81Val), a missense substitution, so BP7 is outside its criterion scope and is not evaluated.

Rule
MSH6 InSiGHT VCEP BP7: synonymous or intronic variant at or beyond -21/+7 of an exon; not applicable to missense variants.
Evidence considered
  • The case normalization identifies NM_000179.3:c.242C>T as NP_000170.1:p.(Ala81Val) / p.(A81V), a missense variant.
  • The MSH6 InSiGHT VCEP BP7 rule applies to synonymous or specified intronic variants, not missense substitutions.
Sources

Statement

In silico

SpliceAI predicts possible splice impact for this variant (max delta score = 0.32). REVEL score = 0.216. BayesDel score = -0.293941. HCI prior probability for pathogenicity = 0.0035. MAPP score = 4.76. Custom PP2 score = 0.003.

8 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

  • Frequency of mutations in mismatch repair genes in a population-based study of women with ovarian cancer.
    Pal T et al. · 2012
    This population-based ovarian-cancer study sequenced MSH6 and other mismatch-repair genes and reported pathogenic mutations and unclassified missense variants, but it does not explicitly mention MSH6 c.242C>T or p.(A81V), nor does it provide variant-specific MSI, IHC, BRAF, methylation, or alternate-molecular-basis evidence.
    Does not name this variant
    PMID 23047549 ↗
    Quoted passage
    Germline genetic testing of coding regions in the MLH1, MSH2 and MSH6 genes revealed sequence changes at 161 different nucleotides. As shown in Table 2, nine pathogenic mutations were found, five in MSH6, two in MLH1 and two in MSH2.

    Results, paragraph 2

  • CoDP: predicting the impact of unclassified genetic variants in MSH6 by the combination of different properties of the protein.
    Terui H et al. · 2013
    This paper describes a computational method for assessing MSH6 missense variants but does not explicitly mention c.242C>T or p.(A81V) and provides no variant-specific phenotype, tumor, or alternate-molecular-basis evidence relevant to PP4 or BP5.
    Does not name this variant
    PMID 23621914 ↗
    Quoted passage
    In this study, we built CoDP, the new prediction tool to assess the MSH6 missense variants.

    Conclusion

  • ACMG recommendations for reporting of incidental findings in clinical exome and
    No paper-specific finding is recorded.
    PMID 23788249 ↗
  • Endometrial cancer: a review and current management strategies: part I.
    SGO Clinical Practice Endometrial Cancer Working Group et al. · 2014
    No paper-specific finding is recorded.
    PMID 24905773 ↗
  • Endometrial cancer: a review and current management strategies: part II.
    No paper-specific finding is recorded.
    PMID 24929052 ↗
  • Standards and guidelines for the interpretation of sequence variants: a joint co
    No paper-specific finding is recorded.
    PMID 25741868 ↗
  • A Standardized DNA Variant Scoring System for Pathogenicity Assessments in Mende
    The paper does not explicitly mention MSH6, c.242C>T, or NP_000170.1:p.(A81V). It therefore provides no variant-specific functional, clinical, segregation, co-occurrence, or population-frequency observations for this variant. The paper describes a general rules-based variant-scoring system applied to variants in 338 genes, using prediction, population-frequency, co-occurrence, segregation, and functional-study data.
    Does not name this variant
    PMID 26467025 ↗
    Quoted passage
    Over 16,500 pathogenicity assessments on 11,894 distinct variants in 338 genes causing neurological, endocrine, and nephrotic genetic disorders were performed on the sequencing data.

    Materials and Methods, Data Collection and Storage

  • Classification of genetic variants in genes associated with Lynch syndrome using a clinical history weighting algorithm.
    Morris B et al. · 2016
    The paper does not explicitly mention MSH6 c.242C>T or NP_000170.1:p.(A81V), and provides no case observation, segregation result, population frequency, or functional assay result for this variant. At the gene level, it describes MSH6 as one of the mismatch-repair genes associated with Lynch syndrome and evaluates a clinical History Weighting Algorithm for classifying MSH6 variants using patients' personal and family cancer histories. In simulated-variant testing, the MSH6 algorithm showed high predictive performance, but these findings concern the algorithm and MSH6 variants generally, not the specified variant.
    Does not name this variant
    PMID 27363726 ↗
    Quoted passage
    Lynch syndrome is a hereditary cancer syndrome associated with high risks of colorectal and endometrial cancer that is caused by pathogenic variants in the mismatch repair genes (MLH1, MSH2, MSH6, PMS2, EPCAM).

    Abstract, Background

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.000113944; MAF= 0.01139%, 164/1439308 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 0.000145039; MAF= 0.01450%, 159/1096258 alleles, homozygotes = 0); grpmax FAF= 0.00012624.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.4827e-05; MAF= 0.00348%, 3/86140 alleles, homozygotes = 0) and has highest observed frequency in the European (non-Finnish) population (AF= 8.0047e-05; MAF= 0.00800%, 3/37478 alleles, homozygotes = 0); grpmax FAF= 1.591e-05.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Uncertain significance (7 clinical laboratories) and as Likely benign (5 clinical laboratories). (ClinVarID = 127571)

In silico

SpliceAI predicts possible splice impact for this variant (max delta score = 0.32). REVEL score = 0.216. BayesDel score = -0.293941. HCI prior probability for pathogenicity = 0.0035. MAPP score = 4.76. Custom PP2 score = 0.003.

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. This variant has not previously been reported in somatic cancers (COSMIC).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.