0%
Print report
Variant interpretation report

MSH6 c.2463A>C, p.(Leu821=)

NM_000179.3:c.2463A>C NP_000170.1:p.(Leu821=) Synonymous · exon 4 View identifiers
Classification
Likely benign

Variant description:

No variant summary was recorded for this case.

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

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

In plain language

Gene-level background from the recorded interpretation.

About 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: 2
Pathogenic criteria applied · 0

No pathogenic criterion marked as applied in the recorded assessment.

Benign criteria applied · 2
BP4Supporting
BP4 · supporting

Met (supporting): SpliceAI max delta 0.001, well below the <=0.1 threshold indicating no splicing impact.

BP7Supporting
BP7 · supporting

Met (supporting): synonymous variant deep in the exon interior (1835 bp from the 5' splice boundary) with SpliceAI max delta 0.001.

Recorded classification: Likely benign

Likely Benign: InSiGHT MSH6 VCEP v2.0 Rule19 (>=2 Benign.Supporting) is satisfied by BP4 and BP7, both supporting.

02The sources

Evidence at a glance

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

gnomAD v4.1
gnomAD v2.1
Population frequency
1 / 1,613,962 alleles

gnomAD v4.1: 1 / 1,613,962 alleles. Recorded AF 6.19593e-07. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 4.01065e-06; MAF= 0.00040%, 1/249336 alleles, homozygotes = 0) and has highest observed frequency in the Ashkenazi Jewish population (AF= 9.96016e-05; MAF= 0.00996%, 1/10040 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI score
0.001 maximum delta

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

ClinVar submissions
3 reported laboratory submissions

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

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB identified curated literature and non-variant-specific oncogenicity context for review; listed oncogenicity label: Unknown Oncogenic Effect.

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: 2 met · 4 not met · 9 not assessed · 13 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.

Met Not met Not assessed Not applicable

MSH6 VCEP (InSiGHT ClinGen cspec v2.0) governs this case (framework_mode: vcep).

NM_000179.3:c.2463A>C, NP_000170.1:p.(Leu821=), is a synonymous variant that does not meet any VCEP PVS1 null-variant category (not nonsense/frameshift, not a canonical +/-1,2 splice variant, not a large genomic alteration, not an initiation-codon variant), and SpliceAI shows no splice impact (max delta 0.001), so PVS1 is not_applicable.

The VCEP explicitly designates PM4 and BP3 as Not Applicable for MSH6, and the variant's synonymous nature (no protein length change, not an in-frame indel) is independently consistent with both criteria not applying.

NM_000179.3:c.2463A>C is a synonymous variant, NP_000170.1:p.(Leu821=), with no amino acid change.

The MSH6 VCEP (InSiGHT CSpec v2.0) explicitly marks PM1, PP2, and BP1 as Not Applicable for this gene.

PS1 and PM5 are missense-comparator criteria under this VCEP; since the variant produces no amino acid change and SpliceAI shows no splice impact (max delta 0.00), neither the missense nor non-canonical-splice pathways of PS1 apply, and PM5's dedicated comparator screen confirmed ineligibility because the variant consequence class is synonymous, not missense.

All five criteria in this group are therefore not_applicable for this variant.

PM3 contributes no evidence because the VCEP-required biallelic CMMRD observation and phase/second-variant data are absent.

BP2 is not applicable under the MSH6-specific VCEP specification.

Variant NM_000179.3:c.2463A>C / NP_000170.1:p.(Leu821=) is synonymous, not missense, so the HCI-PRIORS missense lookup pathway for PP3/BP4 does not apply; only the SpliceAI-based synonymous/intronic pathway is relevant to this group.

SpliceAI shows no meaningful splice impact (max delta score 0.001, all four delta scores <=0.001), which is far below the MSH6 VCEP PP3 splice-defect threshold (delta >=0.2) and comfortably meets the BP4 no-impact threshold (delta <=0.1).

The variant lies deep within exon 4 (c.628-c.3172 exon span), well beyond the -21/+7 proximity zone required to withhold BP7, so the synonymous/intronic BP7_Supporting rule is satisfied independently of, and consistently with, the BP4 SpliceAI finding.

PP3 is not met because the only two governing VCEP pathways to PP3 (missense HCI-prior or non-canonical-splice-nucleotide SpliceAI delta >=0.2) do not apply to this synonymous, non-splice-impacting variant.

Governing framework: ClinGen InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specifications for MSH6 v2.0; generic ACMG/AMP population rules were not used because the gene-specific specification is applicable.

BA1 and BS1 are not met because the gnomAD v4.1 singleton frequency is far below their respective VCEP frequency thresholds.

PM2 is not met using the observed Ashkenazi Jewish AF of 3.37792e-05, which exceeds the VCEP <0.00002 cutoff; this is flagged for human review because Grpmax FAF is unavailable for the singleton while total AF is below the cutoff.

BS2 is not assessed because no qualifying phase-confirmed in-trans co-occurrence or patient clinical context is available.

Met · 2

BP4 SupportingMet (supporting): SpliceAI max delta 0.001, well below the <=0.1 threshold indicating no splicing impact. Details ▾Hide ▴
Reasoning

The MSH6 VCEP BP4 rule states that for intronic and synonymous variants, SpliceAI predicting no splicing impact with delta score <=0.1 supports BP4 (per Walker et al 2023). NM_000179.3:c.2463A>C is synonymous (p.(Leu821=)) and SpliceAI predicts a max delta score of 0.001 (DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0), well below the 0.1 threshold, so BP4_Supporting is met.

Rule
MSH6 VCEP (ClinGen InSiGHT) BP4: For intronic and synonymous variants, SpliceAI predicts no splicing impact with delta score <=0.1 as per Walker et al 2023 (BP4_Supporting). Also applicable to missense variants via HCI-prior <0.11 (not relevant here, variant is synonymous).
Evidence considered
  • prefetch.json compact_evidence.spliceai evidence_sentence: 'SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00).' Raw scores: DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0, max_delta_score=0.001.
  • cspec BP4 rule (MSH6 VCEP v2.0): 'For intronic and synonymous variants: SpliceAI predicts no splicing impact with delta score <=0.1 as per Walker et al 2023.' Variant qualifies as synonymous with delta well under threshold.
Sources
BP7 SupportingMet (supporting): synonymous variant deep in the exon interior (1835 bp from the 5' splice boundary) with SpliceAI max delta 0.001. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous (silent) variant (p.(Leu821=)) located well within the exon interior (exon spans c.628-c.3172; variant sits 1835 bp from the 5' splice boundary and 709 bp from the 3' splice boundary), far beyond the -21/+7 exonic proximity window used by the MSH6 VCEP BP7 rule. SpliceAI corroborates no splice impact (max delta score = 0.001). The VCEP explicitly notes 'Variants may satisfy both BP7 and BP4,' consistent with applying both here from the same non-splice-impact evidence.

Rule
MSH6 VCEP (ClinGen InSiGHT) BP7: A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic) is BP7_Supporting; may be combined with BP4.
Evidence considered
  • case_summary.json compact_evidence.normalization: protein consequence NP_000170.1:p.(Leu821=) confirms synonymous/silent change.
  • prefetch.json compact_evidence.spliceai: max_delta_score=0.001 supports absence of cryptic splice disruption at this exonic position.
  • cspec BP7 rule (MSH6 VCEP v2.0): 'A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic). Variants may satisfy both BP7 and BP4.' Exon boundary data (c.628-c.3172) places the variant far outside the -21/+7 zone.
Sources

Not met · 4 · evaluated, threshold not reached

PM2 Not met: the highest ancestry-specific frequency (3.38e-05 in Ashkenazi Jewish) exceeds the <0.00002 cutoff despite a 6.20e-07 total frequency. Flagged for human review: this rests on a single allele, and Grpmax FAF was unavailable. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 VCEP PM2 rule permits Supporting strength only for an absent/extremely rare allele frequency <0.00002 in gnomAD v4. Although the total v4.1 AF is 6.20e-07, the highest observed ancestry-specific AF is 3.38e-05 (1/29,604 Ashkenazi Jewish alleles), exceeding the stated cutoff. PM2 is therefore not met when the ancestry-specific observed frequency is used. This is a singleton threshold artifact: the calculated Grpmax FAF is unavailable, so human review is recommended before relying on the strict non-application of PM2.

Rule
Absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4 dataset.
Evidence considered
  • The InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel MSH6 v2.0 PM2 rule is Supporting strength for absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
  • gnomAD v4.1 reports total AF 6.19593e-07 (1/1,613,962), zero homozygotes, and one Ashkenazi Jewish allele among 29,604 alleles (AF 3.37792e-05); the Grpmax FAF is null.
Still missing
  • The gnomAD v4 Grpmax FAF is unavailable for this singleton; a VCEP-confirmed convention for applying PM2 to a raw one-allele ancestry-specific frequency above the cutoff would resolve the threshold-artifact uncertainty.
Sources
PP3 Not met: SpliceAI max delta 0.001, far below the 0.2 PP3 threshold; the variant is also not missense. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous variant (NP_000170.1:p.(Leu821=)) located deep within exon 4 (c.628_3172 exon boundaries; variant is 1835 bp from the 5' exon boundary and 709 bp from the 3' exon boundary), not at a non-canonical splice nucleotide. The MSH6 VCEP (ClinGen InSiGHT) PP3 rule only awards PP3 for (a) missense variants via HCI-prior lookup, or (b) predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >=0.2 (Walker et al 2023). This variant is not missense (HCI-prior lookup is inapplicable), and SpliceAI predicts no splice impact (max delta score = 0.001, all DS_AG/AL/DG/DL <=0.001), far below the 0.2 PP3 threshold. No PP3 code applies under the governing VCEP specification.

Rule
MSH6 VCEP (ClinGen InSiGHT) PP3: Missense variant with HCI prior probability >0.81 (Moderate) or >0.68-0.81 (Supporting) as per HCI-PRIORS; OR predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >=0.2 per Walker et al 2023. Neither applies to this synonymous variant with SpliceAI max delta=0.001.
Evidence considered
  • prefetch.json compact_evidence.spliceai: DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0, max_delta_score=0.001 -- no splice impact predicted.
  • case_summary.json compact_evidence.normalization: NP_000170.1:p.(Leu821=) confirms synonymous consequence, not missense, so the HCI-prior missense pathway for PP3 does not apply.
  • cspec PP3 rule (MSH6 VCEP v2.0): Moderate/Supporting strengths require either HCI-prior >0.68 for missense variants, or SpliceAI delta >=0.2 at a non-canonical splice nucleotide -- neither condition is met here.
Sources
BA1 Not met: highest ancestry-specific allele frequency 3.38e-05, far below the 0.0022 BA1 threshold. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 VCEP BA1 rule requires gnomAD v4 Grpmax filtering allele frequency >=0.0022 (0.22%) and exclusion as a founder pathogenic variant. gnomAD v4.1 shows one allele overall (1/1,613,962; total AF 6.20e-07) and its highest observed ancestry-specific AF is 3.38e-05 (1/29,604 Ashkenazi Jewish alleles), both far below 0.0022. BA1 is not met; the founder-exclusion condition cannot alter this threshold failure.

Rule
GnomAD v4 Grpmax filtering allele frequency >= 0.0022 (0.22%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • The InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel MSH6 v2.0 BA1 rule requires gnomAD v4 Grpmax filtering allele frequency >=0.0022 (0.22%) plus exclusion as a founder pathogenic variant.
  • gnomAD v4.1 reports one allele in 1,613,962 total alleles (AF 6.19593e-07), zero homozygotes, and a highest observed Ashkenazi Jewish AF of 3.37792e-05 (1/29,604); Grpmax FAF is null.
Still missing
  • The gnomAD v4 Grpmax FAF field is unavailable for this singleton; however, the highest observed raw ancestry-specific AF is far below the BA1 threshold, so this does not affect the determination.
  • No source documents a separate founder-pathogenic-variant exclusion, but this is not outcome-determinative because the BA1 frequency threshold is not approached.
Sources
BS1 Not met: highest ancestry-specific allele frequency 3.38e-05, more than six-fold below the 0.00022 lower bound. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 VCEP BS1 rule requires gnomAD v4 Grpmax filtering allele frequency >=0.00022 and <0.0022, with exclusion as a founder pathogenic variant. The highest observed gnomAD v4.1 ancestry-specific AF is 3.38e-05 (one Ashkenazi Jewish allele), more than six-fold below the 0.00022 lower bound; total AF is 6.20e-07. BS1 is not met. The null Grpmax FAF is a singleton-data limitation, not a reason to substitute the higher v2.1 Ashkenazi Jewish AF or an unobserved estimate for the v4 rule.

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 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel MSH6 v2.0 BS1 rule requires gnomAD v4 Grpmax filtering allele frequency >=0.00022 and <0.0022 (0.022-0.22%) plus exclusion as a founder pathogenic variant.
  • gnomAD v4.1 reports one allele in the Ashkenazi Jewish population (1/29,604; AF 3.37792e-05), zero homozygotes, total AF 6.19593e-07, and no calculated Grpmax FAF.
Still missing
  • The gnomAD v4 Grpmax FAF field is unavailable for this singleton; the observed v4 ancestry-specific AF remains below the BS1 lower bound.
  • No source documents a separate founder-pathogenic-variant exclusion, but this is not outcome-determinative because the BS1 frequency threshold is not met.
Sources

Not assessed · 9 · no assessment recorded

PS2 Not assessed: no de novo or parental-testing data were available. Details ▾Hide ▴
Reasoning

No proband-level phenotype, parental testing, or confirmed de novo observation is present in the consolidated evidence bundle; de novo points cannot be assigned.

Rule
MSH6 InSiGHT VCEP PS2: ≥4 de novo points = Very Strong; 2–3.5 = Strong; 1–1.5 = Moderate; 0.5 = Supporting.
Evidence considered
  • The MSH6 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specification applies PS2 by cumulative de novo points: 0.5 Supporting, 1–1.5 Moderate, 2–3.5 Strong, and at least 4 Very Strong.
  • The consolidated case evidence contains no individual-level inheritance, parental genotype, or phenotype data for NM_000179.3:c.2463A>C.
Still missing
  • Variant testing in both biological parents, including confirmation of maternity and paternity where required.
  • Proband phenotype and age-at-diagnosis information sufficient to assess phenotype consistency.
  • Number of independent confirmed de novo observations and the corresponding total de novo points.
Sources
PS3 Not assessed: no functional assay or mRNA-based study results were available for this variant. Details ▾Hide ▴
Reasoning

MSH6 VCEP (InSiGHT) specifies PS3 based on calibrated functional assay odds-of-pathogenicity (>18.7 Strong, >4.3-<=18.7 Moderate, >2.08-<=4.3 Supporting), MMR functional assay flowchart outcomes, or monoallelic expression/NMD assays showing <10% wild-type allele expression. No such laboratory functional or mRNA/cDNA-based assay results for NM_000179.3:c.2463A>C (p.Leu821=) were found anywhere in the case evidence bundle (prefetch.json, evidence.json, literature_pass.json, vcep_materials.json). The three ClinVar-linked PMIDs (25741868, 25394175, 28492532) are ACMG/AMP guideline and practice-guideline papers, not variant-specific functional studies, and none report a functional assay for this exact variant. SpliceAI in silico delta scores (max 0.001) are a computational splicing prediction, not a laboratory functional/mRNA assay, and are not applicable evidence for PS3 under this VCEP specification.

Still missing
  • No calibrated MMR functional assay (e.g. cell-based complementation, in vitro MMR activity) odds-of-pathogenicity value available for this variant
  • No patient-derived mRNA/cDNA or NMD-inhibition assay data available to assess monoallelic expression/splicing aberration
  • No variant-specific functional-assay publication identified in the literature packet
PM3 Not assessed: no co-occurring pathogenic MSH6 variant or CMMRD-consistent phenotype data were available. Details ▾Hide ▴
Reasoning

The MSH6 InSiGHT specification requires co-occurrence with a known pathogenic/likely pathogenic MSH6 variant in a patient with clinical features consistent with constitutional mismatch repair deficiency (CMMRD). No such affected-proband observation, second variant, zygosity, or phase information is present in the case-evidence bundle; therefore no PM3 points can be assigned.

Rule
MSH6 InSiGHT VCEP v2.0 PM3: pathogenic/likely pathogenic variant in trans = 1.0 point; phase unknown = 0.5 points; PM3_Supporting requires 0.5 point, PM3_Moderate 1-1.5 points, PM3_Strong 2-3.5 points, and PM3_VeryStrong at least 4 points.
Evidence considered
  • MSH6 InSiGHT VCEP v2.0 PM3 requires co-occurrence with a known pathogenic/likely pathogenic MSH6 variant in a patient with CMMRD-consistent features; a variant in trans contributes 1.0 point and phase-unknown co-occurrence contributes 0.5 points.
  • The consolidated case-evidence bundle provides no affected CMMRD proband, second MSH6 variant, co-occurrence, cis/trans result, or phase-testing result for NM_000179.3:c.2463A>C.
Still missing
  • Affected-proband records with CMMRD-consistent clinical features.
  • The identity and pathogenic/likely pathogenic classification of any second MSH6 variant in the same individual.
  • Phase determination by parental or offspring testing when a second variant is identified.
Sources
PP1 Not assessed: no segregation or pedigree genotype/phenotype data were available. Details ▾Hide ▴
Reasoning

No pedigree-level genotype/phenotype observations or segregation likelihood ratio are provided; PP1 cannot be evaluated.

Rule
MSH6 InSiGHT VCEP PP1: combined Bayes likelihood ratio >18.7 in ≥2 families = Strong; >4.3 to ≤18.7 = Moderate; >2.08 to ≤4.3 = Supporting.
Evidence considered
  • The MSH6 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specification requires a combined co-segregation Bayes likelihood ratio above 2.08 for PP1_Supporting, above 4.3 through 18.7 for PP1_Moderate, and above 18.7 in at least two families for PP1_Strong.
  • The consolidated case evidence contains no family segregation data, informative meioses, or calculated likelihood ratio for NM_000179.3:c.2463A>C.
Still missing
  • Pedigree data with variant genotypes, disease status, ages, and informative meioses.
  • A combined Bayes likelihood ratio from co-segregation analysis, including evidence from at least two families for PP1_Strong.
Sources
PP4 Not assessed: no tumor MSI or MMR immunohistochemistry results were available. Details ▾Hide ▴
Reasoning

No variant-associated CRC/endometrial tumor MSI result or MMR IHC result is present in the consolidated case evidence. Therefore, the VCEP PP4 threshold is not evaluable.

Rule
InSiGHT MSH6 v2.0 PP4: 1 qualifying tumor = Supporting; 2 = Moderate; at least 3 independent tumors in at least 2 families = Strong. For MSH6, IHC consistency requires isolated MSH6 loss.
Evidence considered
  • InSiGHT MSH6 v2.0 permits PP4_Supporting for one, PP4_Moderate for two, and PP4_Strong for at least three independent CRC/endometrial MSI-H tumors and/or MMR IHC results consistent with the variant location; no such tumor observations are supplied for this exact variant.
Still missing
  • Obtain tumor-level evidence for carriers of NM_000179.3:c.2463A>C: MSI testing by a standard 5-10-marker panel or tumor genome and/or MMR IHC. For MSH6, qualifying IHC loss must be isolated MSH6 loss and consistent with the variant location.
Sources
BS2 Not assessed: no in-trans co-occurrence with a pathogenic MSH6 variant in an eligible patient was documented. Details ▾Hide ▴
Reasoning

The applicable InSiGHT MSH6 VCEP BS2 rule is not a general healthy-homozygote rule. It requires a phase-confirmed in-trans co-occurrence with a known pathogenic MSH6 variant in an eligible patient with colorectal cancer after age 45 (or another Lynch syndrome cancer above its median onset age) and no current or prior CMMRD manifestations. No such case, phase, cancer-age, or CMMRD information is present. The zero gnomAD homozygotes do not address this patient-specific requirement.

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), and no previous or current clinical manifestations of CMMRD; phase confirmation requires testing of parents or offspring.
Evidence considered
  • The InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel MSH6 v2.0 BS2 rule requires phase-confirmed in-trans co-occurrence with a known pathogenic MSH6 variant in a clinically eligible patient without CMMRD manifestations.
  • No source in the consolidated case-evidence bundle supplies a qualifying co-occurrence or the required clinical and phase evidence.
Still missing
  • A qualifying patient-level observation of this variant in trans with a known pathogenic MSH6 variant is required.
  • Parental or offspring testing confirming phase is required.
  • The qualifying cancer type and age at diagnosis, and absence of current or prior CMMRD manifestations, must be documented.
Sources
BS3 Not assessed: no NMD-inhibition mRNA assay or calibrated functional assay result was available. Details ▾Hide ▴
Reasoning

MSH6 VCEP (InSiGHT) specifies BS3 based on calibrated functional assay odds-of-pathogenicity (<=0.05 Strong, >0.05-<=0.48 Supporting), or for synonymous/intronic variants, absence of mRNA aberration (splicing or allelic imbalance) determined by NMD-inhibition laboratory assays. This variant, NM_000179.3:c.2463A>C (p.Leu821=), is synonymous, which is the variant class this BS3 rule specifically targets, but no NMD-inhibition mRNA assay, allelic imbalance study, or calibrated cell-based functional assay result for this exact variant was found in the case evidence bundle. SpliceAI predicts a very low max delta score (0.001), consistent with no predicted splicing impact, but this is a computational prediction relevant to BP7/BP4, not the laboratory-based mRNA assay evidence required by the VCEP for BS3.

Still missing
  • No NMD-inhibition mRNA/cDNA assay result available to confirm absence of splicing aberration or allelic imbalance for this synonymous variant
  • No calibrated functional assay odds-of-pathogenicity value available for this variant
  • No variant-specific functional-assay publication identified in the literature packet
BS4 Not assessed: no non-segregation observations or likelihood ratio data were available. Details ▾Hide ▴
Reasoning

No documented non-segregation observations or combined Bayes likelihood ratio are provided; BS4 cannot be evaluated.

Rule
MSH6 InSiGHT VCEP BS4: combined Bayes likelihood ratio <0.05 = Strong; >0.05 to ≤0.48 = Supporting.
Evidence considered
  • The MSH6 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specification assigns BS4_Strong for a combined Bayes likelihood ratio below 0.05 and BS4_Supporting for a ratio above 0.05 through 0.48.
  • The consolidated case evidence contains no non-segregation pedigree data or calculated likelihood ratio for NM_000179.3:c.2463A>C.
Still missing
  • Pedigree data demonstrating lack of co-segregation, with genotype and disease-status information for informative relatives.
  • A combined Bayes likelihood ratio below 0.48 to support BS4, including assessment of age-dependent penetrance and phenocopies.
Sources
BP5 Not assessed: no tumor MSS, MMR IHC, BRAF V600E, or MLH1 methylation results were available. Details ▾Hide ▴
Reasoning

No tumor-level MSS result, retained MMR expression, MMR IHC pattern inconsistent with MSH6, BRAF V600E result, or MLH1 methylation result is present for this exact variant. BP5 cannot be evaluated.

Rule
InSiGHT MSH6 v2.0 BP5: 2-3 qualifying tumors = Supporting; at least 4 = Strong; alternatively, 1 qualifying BRAF V600E/MLH1-methylated MSI-H tumor with MLH1 loss = Supporting and at least 2 = Strong.
Evidence considered
  • InSiGHT MSH6 v2.0 specifies BP5_Supporting for 2-3 CRC/endometrial tumors with MSS and/or retained MMR expression, or LS-spectrum tumors with MMR protein loss inconsistent with the gene; BP5_Strong requires at least 4 such tumors. It also permits Supporting for one and Strong for at least two qualifying BRAF V600E/MLH1-methylated MSI-H tumors with MLH1 loss. No qualifying tumor data are supplied.
Still missing
  • Obtain tumor data for carriers of NM_000179.3:c.2463A>C, including MSI/MSS status, MMR IHC, and where relevant BRAF V600E or MLH1 promoter methylation. The VCEP threshold is 2-3 qualifying tumors for Supporting or at least 4 for Strong; one qualifying BRAF V600E/MLH1-methylated MSI-H tumor with MLH1 loss supports BP5.
Sources
Not applicable · 13· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: this synonymous variant (p.Leu821=) is not a truncating or canonical splice-site change covered by the PVS1 rule. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous substitution, NP_000170.1:p.(Leu821=), not a nonsense, frameshift, initiation-codon, multi-exon deletion/duplication, or canonical +/-1,2 splice-site variant. The InSiGHT/ClinGen MSH6 VCEP (cspec v2.0) PVS1 rule set is restricted to PTC-introducing nonsense/frameshift variants at or before codon 1341/1360, large genomic deletions/duplications, initiation-codon variants, tandem duplications causing frameshift, last-exonic-base G>non-G splice-consensus disruptions, and IVS+/-1,2 splice variants with confirmed or predicted exon skipping/cryptic splice use. This variant does not fall into any of those buckets, so no VCEP PVS1 rule applies. The variant is also not adjacent to a canonical splice consensus sequence (canonical_splice_consensus=false) and SpliceAI predicts no meaningful splice impact (max delta score 0.001), so there is no basis to invoke the VCEP's IVS+/-1,2 splice-based PVS1 pathway either. No mRNA/minigene assay data are present in the bundle to support a confirmed-splicing-aberration pathway.

Rule
MSH6 VCEP PVS1 (cspec v2.0): nonsense/frameshift PTC <=1341 (Very Strong) or 1342-1360 (Moderate); large genomic exon-level alterations (Very Strong); initiation codon (Strong); tandem exon duplication causing frameshift (Strong); last-exon G>non-G disrupting consensus donor (Strong); IVS+/-1,2 splice variants disrupting frame with NMD (Very Strong), preserving frame in critical region (Strong), disrupting frame without NMD (Moderate); confirmed mRNA-assay splicing aberration (Very Strong) -- variant meets none of these buckets.
Evidence considered
  • case_summary.json normalization: protein consequence is NP_000170.1:p.(Leu821=), a synonymous change (no amino acid change), consequence_class recorded as 'synonymous' in pvs1_variant_assessment.
  • pvs1_variant_assessment.json: canonical_splice_consensus=false, exon=null, variant_bucket='other', rationale states the variant does not fall into generic PVS1 null-variant buckets of nonsense, frameshift, or canonical +/-1,2 splice consensus variants.
  • MSH6 VCEP (cspec v2.0) PVS1 rule text restricts Very Strong/Strong/Moderate strengths to: PTC-introducing nonsense/frameshift <= codon 1341 (Very Strong) or codons 1342-1360 (Moderate); large genomic single/multi-exon alterations (Very Strong); initiation codon variants (Strong); tandem exon duplication causing frameshift before last splice junction (Strong); last-exon-base G>non-G with non-GTRRGT donor (Strong); IVS+/-1 or +/-2 variants with exon skipping/cryptic splice use disrupting frame and predicted NMD (Very Strong) or preserving frame in a functionally critical region (Strong); or confirmed mRNA-assay splicing aberrations (Very Strong). None apply to this synonymous, non-splice-consensus variant.
  • spliceai.json (evidence_sentence): SpliceAI predicts no significant splice impact for this variant (max delta score = 0.001, all four donor/acceptor gain/loss deltas <=0.001), consistent with no splice-driven loss-of-function mechanism.
Still missing
  • No patient-derived RNA/minigene splicing assay data available to rule out a cryptic splicing effect beyond the SpliceAI prediction.
Sources
PS1 N/ANot applicable: the variant makes no amino acid change, leaving nothing to compare against known pathogenic variants. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous variant, NP_000170.1:p.(Leu821=) — it does not encode any amino acid change. The MSH6 VCEP (InSiGHT CSpec v2.0) PS1 rule requires either (a) a predicted missense substitution encoding the same amino acid change as an established Pathogenic missense variant via a different nucleotide change, or (b) a variant affecting the same non-canonical splice nucleotide as a confirmed Pathogenic splice variant with similar/worse SpliceAI prediction. Neither applies: this is not a missense change (no amino-acid-altering consequence to compare), and SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00), so it does not qualify as a splice-altering nucleotide change either.

Rule
MSH6 VCEP (InSiGHT CSpec v2.0) PS1: same amino-acid-change missense comparator or same non-canonical splice nucleotide comparator with equal/worse SpliceAI prediction; variant is synonymous with no splice impact, so neither pathway is met.
Evidence considered
  • Normalized protein consequence is NP_000170.1:p.(Leu821=) (synonymous), per case_summary.json normalization block, ruling out the missense pathway of the VCEP PS1 rule.
  • SpliceAI evidence_sentence: 'SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00)', ruling out the non-canonical splice pathway of the VCEP PS1 rule.
Sources
PS4 VCEPNot applicable: the MSH6 VCEP routes tumor immunohistochemistry evidence through PP4, not PS4. Details ▾Hide ▴
Reasoning

The governing InSiGHT MSH6 VCEP specification does not apply PS4, because tumor IHC data are used through PP4 rather than proband counting.

VCEP rule
InSiGHT MSH6 v2.0: PS4 not applicable; tumor IHC evidence is evaluated under PP4 rather than proband counting.
Evidence considered
  • InSiGHT MSH6 v2.0 marks PS4 not applicable and states that PS4 is not used for MMR variant classification using proband counting because tumor IHC data are available through PP4.
Sources
PM1 VCEPNot applicable: the MSH6 VCEP defines no mutational hotspot, and this synonymous variant changes no amino acid. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (InSiGHT CSpec v2.0) explicitly designates PM1 as Not Applicable for this gene (no VCEP-defined mutational hotspot/critical functional domain rule for MSH6). Independently, this variant is synonymous (p.Leu821=) with no amino acid change and no predicted splice impact (SpliceAI max delta = 0.00), so a mutational-hotspot/domain-clustering argument would not be substantively applicable in any case.

VCEP rule
MSH6 VCEP (InSiGHT CSpec v2.0) PM1: applicability = Not Applicable.
Evidence considered
  • cspec criteria list marks PM1 with "applicability": "Not Applicable" for the MSH6 InSiGHT specification.
  • Variant is synonymous (NP_000170.1:p.(Leu821=)) with SpliceAI max delta score 0.00, so no hotspot/domain missense or splice-disruption argument is available.
Sources
PM4 VCEPNot applicable: the MSH6 VCEP marks PM4 not applicable, and the variant does not alter protein length. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (cspec v2.0) explicitly marks PM4 as Not Applicable for this gene, so the VCEP-specific specification takes precedence over the generic ACMG PM4 rule (protein length change from in-frame indel/stop-loss). Independent of the VCEP flag, this variant is also mechanistically inapplicable to PM4: c.2463A>C produces a synonymous substitution, NP_000170.1:p.(Leu821=), with no change in protein length (no in-frame insertion/deletion and no stop-loss).

VCEP rule
MSH6 VCEP (cspec v2.0): PM4 marked Not Applicable for this gene.
Evidence considered
  • cspec MSH6 v2.0 criteria list: PM4 entry has "applicability": "Not Applicable" for this gene-specific framework.
  • case_summary.json normalization: protein consequence NP_000170.1:p.(Leu821=) confirms no amino acid change and no protein length alteration, consistent with PM4 not applying to this synonymous variant regardless of VCEP flag.
Sources
PM5 N/ANot applicable: the variant is synonymous, so there is no amino acid change to compare at codon 821. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (InSiGHT CSpec v2.0) PM5 rule applies only to a missense change at an amino acid residue where a different missense change at that residue was classified Pathogenic/Likely Pathogenic on the protein level (not via aberrant splicing), and requires PP3 to be met. This variant, c.2463A>C, is synonymous (p.Leu821=) and produces no missense/protein-level change, so there is no residue-level amino-acid substitution to compare against other pathogenic missense variants at codon 821. The dedicated PM5 comparator screen for this case explicitly found the variant ineligible for the classic same-residue missense PM5 search because its consequence class is synonymous, not missense.

Rule
MSH6 VCEP (InSiGHT CSpec v2.0) PM5: missense change at a residue with an established Pathogenic/Likely Pathogenic missense change at protein level; not applicable to a synonymous variant with no amino acid change.
Evidence considered
  • pm5_candidates.json: eligible_for_classic_pm5_search=false; reason: "Framework is classic same-residue missense PM5, but the variant consequence class (synonymous) is not missense"; recommendation.level="not_applicable".
  • cspec PM5 rule text requires a missense change at the amino acid residue (not aberrant splicing) with PP3 supporting; this variant has no missense/protein-level change to evaluate.
Sources
cspec ↗pm5_candidates
PM6 VCEPNot applicable: designated not applicable by the MSH6 InSiGHT VCEP specification. Details ▾Hide ▴
Reasoning

PM6 is explicitly designated Not Applicable by the MSH6 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specification.

VCEP rule
MSH6 InSiGHT VCEP: PM6 Not Applicable.
Evidence considered
  • The applicable MSH6 InSiGHT Hereditary Colorectal Cancer/Polyposis Expert Panel specification lists PM6 as Not Applicable.
Sources
PP2 VCEPNot applicable: the MSH6 VCEP marks PP2 not applicable, and the variant is not missense. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (InSiGHT CSpec v2.0) explicitly designates PP2 (missense-in-gene-with-low-benign-missense-rate) as Not Applicable for MSH6. This variant is also not a missense variant (it is synonymous, p.Leu821=), so PP2's underlying premise — a missense substitution in a gene where missense variants are a common mechanism of pathogenicity — does not apply on either the VCEP-specific or mechanistic grounds.

VCEP rule
MSH6 VCEP (InSiGHT CSpec v2.0) PP2: applicability = Not Applicable.
Evidence considered
  • cspec criteria list marks PP2 with "applicability": "Not Applicable" for the MSH6 InSiGHT specification.
  • Variant is synonymous (NP_000170.1:p.(Leu821=)), not a missense substitution, so the PP2 missense-mechanism premise is not met regardless.
Sources
PP5 VCEPNot applicable: the MSH6 VCEP designates PP5 not applicable, with no expert-panel submission on record. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP specification designates PP5 not applicable. Independently, the exact ClinVar record has no expert-panel submission and contains only three single-submitter Likely benign laboratory assertions; it cannot support PP5.

VCEP rule
PP5 requires an exact-variant ClinVar expert-panel Pathogenic/Likely pathogenic assertion; ordinary laboratory submissions and aggregate labels are excluded. The governing MSH6 VCEP also marks PP5 not applicable.
Evidence considered
  • InSiGHT MSH6 v2.0 marks PP5 not applicable.
  • ClinVar variation 918700 exactly matches NM_000179.3(MSH6):c.2463A>C (p.Leu821=), but its three Likely benign submissions are all single-submitter clinical laboratory assertions and the record reports no expert-panel submissions.
Sources
BP1 VCEPNot applicable: the MSH6 VCEP marks BP1 not applicable, and the variant is not missense. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (InSiGHT CSpec v2.0) explicitly designates BP1 (missense variant in a gene where truncating variants are the primary disease mechanism) as Not Applicable for MSH6. This variant is also not a missense variant (it is synonymous, p.Leu821=), so BP1's underlying premise does not apply on either the VCEP-specific or mechanistic grounds.

VCEP rule
MSH6 VCEP (InSiGHT CSpec v2.0) BP1: applicability = Not Applicable.
Evidence considered
  • cspec criteria list marks BP1 with "applicability": "Not Applicable" for the MSH6 InSiGHT specification.
  • Variant is synonymous (NP_000170.1:p.(Leu821=)), not a missense substitution, so the BP1 missense-mechanism premise is not met regardless.
Sources
BP2 VCEPNot applicable: the MSH6 VCEP directs use of BS2 instead of BP2. Details ▾Hide ▴
Reasoning

BP2 is explicitly not applicable in the MSH6 InSiGHT specification, which directs use of BS2 instead. BP2 is therefore not evaluated, irrespective of the absence of co-occurrence or phase data in this case.

VCEP rule
MSH6 InSiGHT VCEP v2.0 BP2: not applicable; BS2 is used instead.
Evidence considered
  • MSH6 InSiGHT VCEP v2.0 marks BP2 as not applicable and states that BS2 is used instead.
Sources
BP3 VCEPNot applicable: the MSH6 VCEP marks BP3 not applicable; the change is also a single-nucleotide substitution, not an in-frame indel. Details ▾Hide ▴
Reasoning

The MSH6 VCEP (cspec v2.0) explicitly marks BP3 as Not Applicable for this gene. BP3 (in-frame indel in a repetitive region without a known function) is also mechanistically inapplicable here because c.2463A>C is a single-nucleotide synonymous substitution, not an in-frame insertion/deletion in a repeat region.

VCEP rule
MSH6 VCEP (cspec v2.0): BP3 marked Not Applicable for this gene.
Evidence considered
  • cspec MSH6 v2.0 criteria list: BP3 entry has "applicability": "Not Applicable" for this gene-specific framework.
  • Variant is a single-nucleotide substitution (c.2463A>C, synonymous), not an in-frame indel, so the underlying BP3 mechanism (repetitive region indel with no functional impact) does not apply regardless of VCEP flag.
Sources
BP6 VCEPNot applicable: the MSH6 VCEP designates BP6 not applicable, with no expert-panel benign assertion on record. Details ▾Hide ▴
Reasoning

The governing MSH6 VCEP specification designates BP6 not applicable. Independently, no exact-variant ClinVar expert-panel Benign/Likely benign assertion is present; the observed Likely benign assertions are ordinary single-submitter laboratory submissions and cannot trigger BP6.

VCEP rule
BP6 requires an exact-variant ClinVar expert-panel Benign/Likely benign assertion; ordinary laboratory submissions and aggregate labels are excluded. The governing MSH6 VCEP also marks BP6 not applicable.
Evidence considered
  • InSiGHT MSH6 v2.0 marks BP6 not applicable.
  • ClinVar variation 918700 exactly matches NM_000179.3(MSH6):c.2463A>C (p.Leu821=), but the three Likely benign submissions are single-submitter laboratory assertions; the record has no expert-panel submission.
Sources

Identifiers

Gene
MSH6
Transcript
NM_000179.3
Coding (HGVS c.)
NM_000179.3:c.2463A>C
Protein (HGVS p.)
NP_000170.1:p.(Leu821=)
GRCh38
chr2:47800446 A>C
GRCh37
chr2:48027585 A>C
Location and type
Exon 4 · synonymous
ClinVar
3904291, 1730684, 918700

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,613,962 alleles AF 6.2e-07 · 0 homozygotes
gnomAD v2.1 1 / 249,336 alleles AF 4.01e-06 · 0 homozygotes
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 6.2e-07 · 1 / 1,613,962 alleles · 0 hom
Ashkenazi Jewish1 / 29,604 3.4e-05
0 alternate alleles recorded in 9 other groups: Remaining individuals, Admixed American, European (Finnish), Amish, East Asian, Middle Eastern, South Asian, African/African American, European (non-Finnish).

gnomAD v2.1

AF 4e-06 · 1 / 249,336 alleles · 0 hom
Ashkenazi Jewish1 / 10,040 0.0001
0 alternate alleles recorded in 7 other groups: African/African American, Admixed American, East Asian, European (Finnish), European (non-Finnish), Remaining individuals, South Asian.

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 6.19593e-07; MAF= 0.00006%, 1/1613962 alleles, homozygotes = 0) and has highest observed frequency in the Ashkenazi Jewish population (AF= 3.37792e-05; MAF= 0.00338%, 1/29604 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 4.01065e-06; MAF= 0.00040%, 1/249336 alleles, homozygotes = 0) and has highest observed frequency in the Ashkenazi Jewish population (AF= 9.96016e-05; MAF= 0.00996%, 1/10040 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat +260 bp
0.000
SpliceAI acceptor gainat -409 bp
0.001
SpliceAI donor lossat -482 bp
0.000
SpliceAI donor gainat -155 bp
0.000
Pangolin splice lossmagnitude shown
-0.002
Pangolin splice gain
0.005

Other predictors

REVEL
Not available
BayesDel
Not available

How the predictions were used

BP4 SupportingMet (supporting): SpliceAI max delta 0.001, well below the <=0.1 threshold indicating no splicing impact. Details ▾Hide ▴
Reasoning

The MSH6 VCEP BP4 rule states that for intronic and synonymous variants, SpliceAI predicting no splicing impact with delta score <=0.1 supports BP4 (per Walker et al 2023). NM_000179.3:c.2463A>C is synonymous (p.(Leu821=)) and SpliceAI predicts a max delta score of 0.001 (DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0), well below the 0.1 threshold, so BP4_Supporting is met.

Rule
MSH6 VCEP (ClinGen InSiGHT) BP4: For intronic and synonymous variants, SpliceAI predicts no splicing impact with delta score <=0.1 as per Walker et al 2023 (BP4_Supporting). Also applicable to missense variants via HCI-prior <0.11 (not relevant here, variant is synonymous).
Evidence considered
  • prefetch.json compact_evidence.spliceai evidence_sentence: 'SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00).' Raw scores: DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0, max_delta_score=0.001.
  • cspec BP4 rule (MSH6 VCEP v2.0): 'For intronic and synonymous variants: SpliceAI predicts no splicing impact with delta score <=0.1 as per Walker et al 2023.' Variant qualifies as synonymous with delta well under threshold.
Sources
BP7 SupportingMet (supporting): synonymous variant deep in the exon interior (1835 bp from the 5' splice boundary) with SpliceAI max delta 0.001. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous (silent) variant (p.(Leu821=)) located well within the exon interior (exon spans c.628-c.3172; variant sits 1835 bp from the 5' splice boundary and 709 bp from the 3' splice boundary), far beyond the -21/+7 exonic proximity window used by the MSH6 VCEP BP7 rule. SpliceAI corroborates no splice impact (max delta score = 0.001). The VCEP explicitly notes 'Variants may satisfy both BP7 and BP4,' consistent with applying both here from the same non-splice-impact evidence.

Rule
MSH6 VCEP (ClinGen InSiGHT) BP7: A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic) is BP7_Supporting; may be combined with BP4.
Evidence considered
  • case_summary.json compact_evidence.normalization: protein consequence NP_000170.1:p.(Leu821=) confirms synonymous/silent change.
  • prefetch.json compact_evidence.spliceai: max_delta_score=0.001 supports absence of cryptic splice disruption at this exonic position.
  • cspec BP7 rule (MSH6 VCEP v2.0): 'A synonymous (silent) or intronic variant at or beyond -21/+7 (5'/3' exonic). Variants may satisfy both BP7 and BP4.' Exon boundary data (c.628-c.3172) places the variant far outside the -21/+7 zone.
Sources
PP3 Not met: SpliceAI max delta 0.001, far below the 0.2 PP3 threshold; the variant is also not missense. Details ▾Hide ▴
Reasoning

NM_000179.3:c.2463A>C is a synonymous variant (NP_000170.1:p.(Leu821=)) located deep within exon 4 (c.628_3172 exon boundaries; variant is 1835 bp from the 5' exon boundary and 709 bp from the 3' exon boundary), not at a non-canonical splice nucleotide. The MSH6 VCEP (ClinGen InSiGHT) PP3 rule only awards PP3 for (a) missense variants via HCI-prior lookup, or (b) predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >=0.2 (Walker et al 2023). This variant is not missense (HCI-prior lookup is inapplicable), and SpliceAI predicts no splice impact (max delta score = 0.001, all DS_AG/AL/DG/DL <=0.001), far below the 0.2 PP3 threshold. No PP3 code applies under the governing VCEP specification.

Rule
MSH6 VCEP (ClinGen InSiGHT) PP3: Missense variant with HCI prior probability >0.81 (Moderate) or >0.68-0.81 (Supporting) as per HCI-PRIORS; OR predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >=0.2 per Walker et al 2023. Neither applies to this synonymous variant with SpliceAI max delta=0.001.
Evidence considered
  • prefetch.json compact_evidence.spliceai: DS_AG=0.001, DS_AL=0.0, DS_DG=0.0, DS_DL=0.0, max_delta_score=0.001 -- no splice impact predicted.
  • case_summary.json compact_evidence.normalization: NP_000170.1:p.(Leu821=) confirms synonymous consequence, not missense, so the HCI-prior missense pathway for PP3 does not apply.
  • cspec PP3 rule (MSH6 VCEP v2.0): Moderate/Supporting strengths require either HCI-prior >0.68 for missense variants, or SpliceAI delta >=0.2 at a non-canonical splice nucleotide -- neither condition is met here.
Sources

Statement

In silico

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

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

Recorded publications

  • Standards and guidelines for the interpretation of sequence variants: a joint consensus recommendation of the American College of Medical Genetics and Genomics and the Association for Molecular Pathology.
    Richards S et al. · 2015
    No paper-specific finding is recorded.
    PMID 25741868 ↗
  • A practice guideline from the American College of Medical Genetics and Genomics and the National Society of Genetic Counselors: referral indications for cancer predisposition assessment.
    Hampel H et al. · 2015
    No paper-specific finding is recorded.
    PMID 25394175 ↗
  • Sherloc: a comprehensive refinement of the ACMG-AMP variant classification criteria.
    Nykamp K et al. · 2017
    No paper-specific finding is recorded.
    PMID 28492532 ↗

Screenshots represent source records captured during evidence collection. Select one to view the recorded source content.

All source links

Statements for reports

The evidence statements recorded by the interpretation pipeline. They have not been reinterpreted by the page.

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 6.19593e-07; MAF= 0.00006%, 1/1613962 alleles, homozygotes = 0) and has highest observed frequency in the Ashkenazi Jewish population (AF= 3.37792e-05; MAF= 0.00338%, 1/29604 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 4.01065e-06; MAF= 0.00040%, 1/249336 alleles, homozygotes = 0) and has highest observed frequency in the Ashkenazi Jewish population (AF= 9.96016e-05; MAF= 0.00996%, 1/10040 alleles, homozygotes = 0).

gnomAD-Canada

Absent from gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Likely benign (3 clinical laboratories). (ClinVarID = 918700)

In silico

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

Functional

OncoKB identified curated literature and non-variant-specific oncogenicity context for review; listed oncogenicity label: Unknown Oncogenic Effect.

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.