0%
Print report
Variant interpretation report

MLH1 c.1964T>C, p.Ile655Thr

NM_000249.4:c.1964T>C NP_000240.1:p.(Ile655Thr) Missense · exon 17 View identifiers
Classification
Likely benign

Variant description:

The MLH1 NM_000249.4:c.1964T>C (NP_000240.1:p.(Ile655Thr)) missense variant has not previously been reported in somatic cancers (COSMIC). Experimental evidence: I655T showed 73.8% repair activity, >75% MLH1 expression, and no detectable transcript-splicing abnormality in exact-variant assays. Based on available guidelines, this variant is considered to be Likely Benign.

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 MLH1

MLH1 encodes a DNA mismatch repair protein that, together with partners such as PMS2, corrects errors that arise during DNA replication. Loss of this repair function leads to the accumulation of mutations, particularly in repetitive microsatellite sequences, and tumors with defective MLH1 typically show high microsatellite instability. Germline mutations in MLH1 cause Lynch syndrome (hereditary non-polyposis colorectal cancer), which strongly predisposes to colorectal, endometrial, ovarian, and other cancers, while biallelic mutations cause constitutional mismatch repair deficiency (CMMRD). Because it normally protects against cancer by maintaining genomic stability, MLH1 acts as a tumor suppressor, and mismatch-repair-deficient tumors often respond well to immunotherapy.

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 MLH1 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
BS3Supporting
BS3 · supporting

Met at Supporting: I655T showed 73.8% repair activity, >75% MLH1 expression, and no detectable transcript-splicing abnormality in exact-variant assays.

BP4Supporting
BP4 · supporting

Met, Supporting: HCI prior probability is 0.0077, below the VCEP BP4 threshold of <0.11.

Recorded classification: Likely benign

Likely Benign: BS3 (supporting) and BP4 (supporting) satisfy the MLH1 VCEP's Rule19 requiring at least two supporting benign criteria.

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
89 / 1,613,532 alleles

gnomAD v4.1: 89 / 1,613,532 alleles. Recorded AF 5.51585e-05. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 9.19892e-05; MAF= 0.00920%, 26/282642 alleles, homozygotes = 0) and has highest observed frequency in the Remaining individuals population (AF= 0.000277085; MAF= 0.02771%, 2/7218 alleles, homozygotes = 0); grpmax FAF= 0.00012675.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 5.432420686657975e-05, 1/18408 alleles, homozygotes = 0).

No screenshot for this evidence
REVEL score
0.594 recorded score

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

ClinVar submissions
17 reported laboratory submissions

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

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. MLH1, a DNA mismatch repair protein, is recurrently altered by deletion and mutation in various cancer types.

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

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

Met Not met Not assessed Not applicable

All three requested criteria are not applicable under the governing MLH1 VCEP specification: PVS1 is limited to specified loss-of-function or splice-altering mechanisms, while PM4 and BP3 are explicitly designated Not Applicable.

The case evidence identifies NM_000249.4:c.1964T>C as NP_000240.1:p.(Ile655Thr) / p.I655T, an exon-17 missense SNV.

The two named VCEP reference files were searched for all three variant notations; no exact-variant entry was found in either file.

PS4, PP5, and BP6 are not applicable under the MLH1 VCEP specification.

PP4 cannot be assessed because the available MSI-H colorectal tumor reports do not document the VCEP-required MLH1 promoter methylation exclusion and do not fully establish the specified MSI assessment path.

BP5 cannot be assessed because the available reports describe MSI-H tumors and do not provide the VCEP-defined benign-pattern tumor or BRAF/methylation evidence.

The VCEP-governed HCI prior lookup is decisive for this missense variant: the exact c.1964T>C / p.I655T row assigns probability 0.0077, meeting BP4_Supporting and meeting neither PP3 threshold.

BP7 is not applicable because the variant is missense rather than synonymous or intronic.

Population evidence does not support BA1, BS1, or PM2 because the gnomAD v4.1 Grpmax FAF is 5.3e-05: below the benign-frequency thresholds for BA1 and BS1 but above the PM2 rarity threshold.

BS2 is not assessed because the required in-trans co-occurrence, phase confirmation, qualifying cancer phenotype, and absence of CMMRD manifestations are not documented.

Met · 2

BS3 SupportingVCEPMet at Supporting: I655T showed 73.8% repair activity, >75% MLH1 expression, and no detectable transcript-splicing abnormality in exact-variant assays. Details ▾Hide ▴
Reasoning

BS3_Supporting is met. The variant-specific protein assay in Takahashi et al. showed 73.8% in-vitro mismatch-repair activity and >75% relative MLH1 expression, supporting retained protein function rather than loss of function. Morak et al. (PMID:31332305) tested the exact c.1964T>C/p.(Ile655Thr) variant in full-length MLH1 transcripts with and without nonsense-mediated-decay inhibition and reported no detectable splicing effect, with biallelic transcript representation. Together, the exact-variant protein and mRNA findings support proficient function under the VCEP flowchart, but the historic protein assay is not one of the exact calibrated assay rows in the SVI documentation and no functional odds are provided; therefore Strong is not assigned.

VCEP rule
Calibrated functional assays with functional odds for Pathogenicity >0.05 & ≤0.48 OR Variant-specific proficient function in protein and mRNA-based lab assays as per MMR functional assay flowchart*.
Evidence considered
  • Takahashi et al. (PMID:17510385), Table 1, row I655T: the exact variant had 73.8% in-vitro mismatch-repair activity and relative MLH1 expression >75% of wild type; the three yeast dominant-mutator assays were positive.
  • Morak et al. (PMID:31332305), Table 1 and the cDNA analysis results: exact MLH1 c.1964T>C p.(Ile655Thr) was included in full-length transcript testing with and without puromycin-mediated NMD inhibition, with no detectable splicing effect and biallelic transcript representation.
  • Functional-assay-flowchart.pdf: the VCEP historic-assay framework directs evaluation of concordant functional results through protein expression and cellular MMR-function branches; the exact-variant results support proficient rather than deficient function.
  • Functional-assay-SVI-documentation-MMR.xlsx, sheet MMR assays: calibrated assays are separately listed with controls and proposed strengths; the exact historic assay PMID:17510385 is not listed, so the calibrated functional-odds branches cannot be used.
Still missing
  • No exact c.1964T>C, p.Ile655Thr, or p.I655T entry was found in Functional-assay-SVI-documentation-MMR.xlsx.txt.
  • No exact c.1964T>C, p.Ile655Thr, or p.I655T entry was found in Functional-assay-flowchart.pdf.txt.
  • No calibrated functional odds for pathogenicity are reported for this variant.
Sources
BP4 SupportingVCEPMet, Supporting: HCI prior probability is 0.0077, below the VCEP BP4 threshold of <0.11. Details ▾Hide ▴
Reasoning

The variant is a missense SNV, and the VCEP directly assigns BP4_Supporting when the exact HCI prior probability is <0.11. The governing HCI table contains c.1964T>C / p.I655T with pathogenicity probability 0.0077, which is below 0.11. The SpliceAI result is not used for BP4 because that alternative is specified by the VCEP only for intronic and synonymous variants.

VCEP rule
Missense variant with HCI-prior probability of pathogenicity <0.11 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) OR For intronic and synonymous variants: SpliceAI predicts no splicing impact with delta score ≤ 0.1 as per Walker et al 2023
Evidence considered
  • HCI-PRIORS-MLH1.txt.txt, row MLH1_04311: c.1964T>C, p.I655T, HCI prior probability 0.0077.
  • The VCEP's SpliceAI BP4 alternative applies to intronic and synonymous variants; this variant is missense, so the exact HCI prior path governs.
Sources

Not met · 7 · evaluated, threshold not reached

PS1 VCEPNot met: the VCEP-listed same-residue comparator p.Ile655Phe is Uncertain significance, not the Pathogenic classification required for PS1. Details ▾Hide ▴
Reasoning

The MLH1 VCEP permits PS1 Strong only when a different nucleotide change producing the same amino-acid change was previously established by this VCEP as Pathogenic and is not a splice defect. The governing VCEP pilot table contains the same-residue comparator NM_000249.4:c.1963A>T (p.Ile655Phe), but classifies it as Uncertain significance, not Pathogenic; the searched VCEP files contain no qualifying Pathogenic same-amino-acid comparator for p.Ile655Thr.

VCEP 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 MLH1 VCEP rule states that PS1 Strong requires a predicted missense substitution encoding the same amino-acid change with a different nucleotide change previously established by this VCEP as Pathogenic, not a predicted or confirmed splice defect.
  • VCEP-pilot-variants---MMR.xlsx.txt, Sheet1 row: NM_000249.4(MLH1):c.1963A>T (p.Ile655Phe), ClinVar ID 1000222, ClinVar classification Uncertain significance, InSiGHT classification Uncertain significance, codes PM2_supporting and BP4.
  • The exact variant was searched in MMR-Functional-domains.pdf.txt under c.1964T>C, p.Ile655Thr, and p.I655T; no entry was found.
Still missing
  • No qualifying Pathogenic same-amino-acid comparator was found in VCEP-pilot-variants---MMR.xlsx.txt; the row for c.1963A>T (p.Ile655Phe) is Uncertain significance.
  • No p.Ile655Thr or c.1964T>C entry was found in MMR-Functional-domains.pdf.txt; that file is a PM1 domain schematic and does not provide a PS1 comparator classification.
Sources
PS3 VCEPNot met: I655T retained 73.8% in-vitro mismatch-repair activity and >75% relative MLH1 expression, rather than demonstrating deficient function. Details ▾Hide ▴
Reasoning

PS3 is not met. Takahashi et al. directly tested I655T in three yeast dominant-mutator assays and an in-vitro mismatch-repair assay: all three yeast assays were positive, in-vitro repair activity was 73.8%, and relative MLH1 expression was >75% of wild type. These results do not show a damaging functional effect. The assay documentation identifies calibrated assays and their validation controls, but does not list PMID:17510385 or this variant as a pre-assigned calibrated result; no calibrated functional odds for pathogenicity are available. The functional-assay flowchart's deficient-function path is therefore not satisfied.

VCEP rule
Calibrated functional assays with functional odds for pathogenicity > 18.7
Evidence considered
  • Takahashi et al. (PMID:17510385), Table 1, row I655T: c.1964T>C was positive in all three yeast dominant-mutator assays, had 73.8% in-vitro mismatch-repair activity, and had relative MLH1 expression >75% of wild type.
  • Functional-assay-SVI-documentation-MMR.xlsx, sheet MMR assays: the VCEP lists validated assay types, positive/negative controls, validation-control counts, calibrated normal/abnormal thresholds, and proposed PS3/BS3 strengths; it contains no exact I655T variant row.
  • Functional-assay-flowchart.pdf: for missense variants without predicted splicing impact, deficient function requires the applicable calibrated assay pathway or concordant assay evidence showing deficient function; the I655T results instead show retained repair activity and expression.
Still missing
  • No exact c.1964T>C, p.Ile655Thr, or p.I655T entry was found in Functional-assay-SVI-documentation-MMR.xlsx.txt.
  • No exact c.1964T>C, p.Ile655Thr, or p.I655T entry was found in Functional-assay-flowchart.pdf.txt.
  • No calibrated functional odds for pathogenicity are reported for this variant.
Sources
PM2 VCEPNot met: gnomAD v4.1 total AF is 5.51585e-05, above the VCEP PM2 threshold of 0.00002 (less than 1 in 50,000 alleles). Details ▾Hide ▴
Reasoning

The governing VCEP PM2 rule requires an absent or extremely rare allele frequency below 0.00002 (less than 1 in 50,000 alleles) in gnomAD v4. The gnomAD v4.1 total AF is 5.51585e-05 (89/1,613,532 alleles), and the Grpmax FAF is 5.3e-05, both above 0.00002; therefore PM2 is not met. The governing VCEP pilot file was searched for c.1964T>C, p.Ile655Thr, and p.I655T; it contains no exact entry for this variant.

VCEP rule
Absent/extremely rare allele frequency <0.00002 (<1 in 50,000 alleles ) in gnomAD v4 dataset
Evidence considered
  • ClinGen InSiGHT MLH1 v2.0 CSPEC PM2 rule: the allele frequency must be <0.00002 (<1 in 50,000 alleles) in gnomAD v4.
  • gnomAD v4.1: total AF 5.51585e-05 from 89/1,613,532 alleles, homozygotes 0, and Grpmax FAF 5.3e-05; the highest population AF is 0.00016442.
  • VCEP-pilot-variants---MMR.xlsx full-text conversion: searched c.1964T>C, p.Ile655Thr, and p.I655T; no exact row for this variant was found.
Still missing
  • VCEP-pilot-variants---MMR.xlsx was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
Sources
PM5 VCEPNot met: the only VCEP-listed alternate residue-655 missense, p.Ile655Phe, is Uncertain significance rather than Pathogenic. Details ▾Hide ▴
Reasoning

The MLH1 VCEP requires a different missense change at the same amino-acid residue classified by this VCEP as Pathogenic on the protein level and not due to aberrant splicing, and permits PM5 only when PP3 is supporting. The governing VCEP pilot table lists the alternate residue-655 change p.Ile655Phe as Uncertain significance, not Pathogenic; no qualifying VCEP Pathogenic comparator was identified, so PM5 is not met.

VCEP 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 other variant is Likely Pathogenic due to a missense alteration.
Evidence considered
  • The MLH1 VCEP PM5 rule requires a different missense change at the same residue classified by this VCEP as Pathogenic on the protein level and not due to aberrant splicing; PM5 is usable only if PP3 is supporting.
  • VCEP-pilot-variants---MMR.xlsx.txt, Sheet1 row: NM_000249.4(MLH1):c.1963A>T (p.Ile655Phe), classified Uncertain significance by InSiGHT, with PM2_supporting and BP4.
  • The PM5 candidate artifact reports zero same-residue candidates and no expert-panel pathogenic or likely pathogenic comparator; it was used only as a search lead, not as classification evidence.
Still missing
  • No same-residue missense comparator classified Pathogenic by this VCEP was found in VCEP-pilot-variants---MMR.xlsx.txt.
  • No p.Ile655Thr, p.I655T, or c.1964T>C entry was found in MMR-Functional-domains.pdf.txt.
Sources
PP3 VCEPNot met: HCI prior probability is 0.0077, below the PP3 Supporting threshold of >0.68 for missense variants. Details ▾Hide ▴
Reasoning

The variant is a missense SNV, so the VCEP missense HCI-prior path is applicable. The governing PP3 thresholds require an HCI prior probability >0.81 for PP3_Moderate or >0.68 and <=0.81 for PP3_Supporting; the exact HCI table row for c.1964T>C / p.I655T assigns a pathogenicity probability of 0.0077. The VCEP's alternative SpliceAI PP3 path is limited to non-canonical splicing nucleotides and therefore does not apply to this coding missense substitution. No PP3 evidence is met.

VCEP rule
Missense variant with HCI prior probability for pathogenicity >0.81 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) ... Missense variant with HCI prior probability for pathogenicity >0.68 & ≤0.81 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) OR Predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >= 0.2 as per Walker et al 2023.
Evidence considered
  • HCI-PRIORS-MLH1.txt.txt, row MLH1_04311: c.1964T>C, p.I655T, HCI prior probability 0.0077; the row also reports MAPP score 6.75 and Custom_PP2 score 0.001, which are not named by the PP3 rule.
  • The case normalization identifies NM_000249.4:c.1964T>C as NP_000240.1:p.(Ile655Thr), a missense SNV; the VCEP SpliceAI alternative is restricted to non-canonical splicing nucleotides and is not applicable here.
Sources
BA1 VCEPNot met: gnomAD v4.1 Grpmax FAF is 0.000053 (0.0053%), below the VCEP BA1 threshold of 0.001 (0.1%). Details ▾Hide ▴
Reasoning

The governing VCEP BA1 threshold is a gnomAD v4 Grpmax filtering allele frequency of at least 0.001 (0.1%), with exclusion of a founder pathogenic variant. The gnomAD v4.1 Grpmax FAF is 0.000053 (5.3e-05; 0.0053%), and the highest observed population AF is 0.00016442, both below 0.001. No founder pathogenic-variant exception is needed because the frequency threshold is not met. The governing VCEP pilot file was searched for c.1964T>C, p.Ile655Thr, and p.I655T; it contains no exact entry for this variant.

VCEP rule
GnomAD v4 Grpmax filtering allele frequency ≥ 0.001 (0.1%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • ClinGen InSiGHT MLH1 v2.0 CSPEC BA1 rule: gnomAD v4 Grpmax filtering allele frequency must be ≥0.001 (0.1%) and the variant must be excluded as a founder pathogenic variant.
  • gnomAD v4.1: total AF 5.51585e-05 from 89/1,613,532 alleles, homozygotes 0; Grpmax FAF 5.3e-05; highest population AF 0.00016442 in Middle Eastern individuals.
  • VCEP-pilot-variants---MMR.xlsx full-text conversion: searched c.1964T>C, p.Ile655Thr, and p.I655T; no exact row for this variant was found.
Still missing
  • VCEP-pilot-variants---MMR.xlsx was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
Sources
BS1 VCEPNot met: gnomAD v4.1 Grpmax FAF is 0.000053 (0.0053%), below the VCEP BS1 lower threshold of 0.0001 (0.01%). Details ▾Hide ▴
Reasoning

The governing VCEP BS1 threshold is a gnomAD v4 Grpmax filtering allele frequency of at least 0.0001 and less than 0.001 (0.01–0.1%), with exclusion of a founder pathogenic variant. The gnomAD v4.1 Grpmax FAF is 0.000053 (5.3e-05; 0.0053%), below the lower threshold of 0.0001, so BS1 is not met. The governing VCEP pilot file was searched for c.1964T>C, p.Ile655Thr, and p.I655T; it contains no exact entry for this variant.

VCEP rule
GnomAD v4 Grpmax filtering allele frequency ≥ 0.0001 and < 0.001 (0.01-0.1%) and variant is excluded as founder pathogenic variant.
Evidence considered
  • ClinGen InSiGHT MLH1 v2.0 CSPEC BS1 rule: gnomAD v4 Grpmax filtering allele frequency must be ≥0.0001 and <0.001 (0.01–0.1%) and the variant must be excluded as a founder pathogenic variant.
  • gnomAD v4.1: Grpmax FAF 5.3e-05 (0.0053%), with total AF 5.51585e-05 from 89/1,613,532 alleles and no homozygotes.
  • VCEP-pilot-variants---MMR.xlsx full-text conversion: searched c.1964T>C, p.Ile655Thr, and p.I655T; no exact row for this variant was found.
Still missing
  • VCEP-pilot-variants---MMR.xlsx was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
Sources

Not assessed · 7 · no assessment recorded

PS2 VCEPNot assessed: affected probands were reported, but no parental testing or evidence establishing de novo origin was provided for PS2 point assignment. Details ▾Hide ▴
Reasoning

The VCEP permits PS2 only for a documented de novo variant in a proband with a Lynch syndrome spectrum tumor, with point assignment determined by confirmation of maternity/paternity and tumor MSI/IHC/methylation data. The available reports document germline MLH1 c.1964T>C/p.I655T in affected individuals, including a colorectal tumor with high microsatellite instability and a gastric-cancer patient, but provide no parental testing or other evidence establishing de novo origin; therefore no PS2 points can be assigned.

Evidence considered
  • ClinGen InSiGHT MLH1 specification v2.0, PS2: two affected individuals were reported with germline c.1964T>C/p.I655T, but neither report documented parental testing or de novo origin.
  • PMID:8938136: a 71-year-old gastric-cancer patient carried the variant in tumor, matched non-tumorous tissue, and blood; one second-degree relative had stomach carcinoma, but no parental testing or de novo assessment was reported.
  • PMID:10970186: patient OG/97-3941 carried germline c.1964T>C/p.I655T and had a high-microsatellite-instability colorectal tumor with later gastric cancer; no segregation or parental analysis was reported.
Still missing
  • Parental testing confirming or excluding the variant in both biological parents.
  • Documented de novo status for an affected proband.
  • For any confirmed de novo proband, tumor MSI/IHC and MLH1 methylation results needed to select the VCEP point category.
Sources
PM3 VCEPNot assessed: no documented CMMRD phenotype or phased pathogenic MLH1 variant in trans, and gnomAD v4.1 grpmax FAF 5.3e-05 exceeds the PM2_Supporting threshold of <0.00002. Details ▾Hide ▴
Reasoning

The MLH1 VCEP PM3 rule requires co-occurrence with a known pathogenic or likely pathogenic variant in the same gene in a patient with clinical features consistent with CMMRD, requires the tested MLH1 variant to meet PM2_Supporting, and assigns points only for a pathogenic/likely pathogenic variant in trans or with phase unknown. The available case evidence documents affected individuals carrying c.1964T>C/p.I655T, but does not document CMMRD features, a second pathogenic or likely pathogenic MLH1 variant, or phase (trans/cis). In addition, gnomAD v4.1 reports a grpmax filtering allele frequency of 5.3e-05, which is above the VCEP PM2 Supporting threshold of <0.00002. Therefore no PM3 points can be assigned and the criterion cannot be assessed from the available qualifying evidence.

VCEP rule
Co-occurrence with a known pathogenic/likely pathogenic sequence variant in the same gene in a patient with clinical features consistent with CMMRD as per Aronson et al 2022 - Refer to “Table for CMMRD diagnosis.pdf”. For MLH1 variants - the variant has to meet PM2\_Supporting criteria.
Evidence considered
  • The VCEP PM3 instructions require co-occurrence with a known pathogenic/likely pathogenic sequence variant in the same gene in a patient with clinical features consistent with CMMRD; no such CMMRD phenotype and second MLH1 variant are documented in the case evidence.
  • The VCEP PM3 instructions assign 1.0 point for a pathogenic/likely pathogenic variant in trans and 0.5 points when phase is unknown; the available reports of c.1964T>C/p.I655T do not establish either relationship to a second pathogenic MLH1 variant.
  • The VCEP PM3 instructions require MLH1 variants to meet PM2_Supporting; gnomAD v4.1 reports grpmax FAF 5.3e-05, above the VCEP threshold of <0.00002.
  • PMID:8938136 reports c.1964T>C/p.I655T in a 71-year-old gastric-cancer patient but provides no second pathogenic MLH1 variant or phase information.
  • PMID:10970186 reports germline c.1964T>C/p.I655T in a colorectal-cancer patient with metachronous gastric cancer but provides no second pathogenic MLH1 variant or phase information.
Still missing
  • Documented CMMRD-compatible clinical features for the individual carrying c.1964T>C/p.I655T
  • A known pathogenic or likely pathogenic MLH1 variant in the same individual
  • Parental or offspring testing, or other validated evidence establishing trans versus cis phase
  • A qualifying PM2_Supporting result under the MLH1 VCEP rule
Sources
PP1 VCEPNot assessed: no informative affected-relative genotypes or combined Bayes Likelihood Ratio were reported; the only family entry was explicitly non-informative. Details ▾Hide ▴
Reasoning

The VCEP requires a combined Bayes Likelihood Ratio from disease co-segregation to assign PP1: >2.08 to 4.3 for Supporting, >4.3 to 18.7 for Moderate, or >18.7 in at least two families for Strong. The available literature reports no informative segregation analysis; one functional-study table lists family information as NI, and the gastric-cancer report mentions one second-degree relative without reporting that relative's genotype, so no combined Bayes Likelihood Ratio is available.

Evidence considered
  • ClinGen InSiGHT MLH1 specification v2.0, PP1: the criterion requires a combined Bayes Likelihood Ratio, with Supporting >2.08 and <=4.3, Moderate >4.3 and <=18.7, or Strong >18.7 in at least two families.
  • PMID:8938136: the patient had one second-degree relative with stomach carcinoma, but the report did not provide that relative's variant genotype or segregation result.
  • PMID:17510385: the I655T row lists family information as NI (not informative), with no additional case-level segregation result.
Still missing
  • Pedigree-level disease status and variant genotypes for affected and unaffected relatives.
  • A combined Bayes Likelihood Ratio calculated under the VCEP segregation framework.
Sources
PP4 VCEPNot assessed: two MSI-H colorectal tumors are reported, but MLH1 promoter methylation exclusion required by the VCEP is undocumented. Details ▾Hide ▴
Reasoning

The VCEP requires one CRC or endometrial MSI-H tumor assessed with a standard 5-10-marker panel or tumor genome and requires MLH1 promoter methylation to be excluded. PMID:10970186 reports this variant in a patient with a high-MSI colorectal tumor, and PMID:11376800 reports it in an MSI-H colorectal tumor, but the available extracts do not establish the required standard-panel/tumor-genome basis and do not document exclusion of MLH1 promoter methylation. The required governing files were searched for c.1964T>C, p.Ile655Thr, and p.I655T: Table-for-CMMRD-diagnosis.pdf.txt and VCEP-pilot-variants---MMR.xlsx.txt; neither contains an entry for this variant.

VCEP rule
1 CRC/Endometrial MSI-H tumor using a standard panel of 5-10 markers<sup>e </sup> 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. For _MLH1_ variants, _MLH1_ promoter methylation is to be excluded in the tumor.
Evidence considered
  • PMID:10970186 reports germline MLH1 c.1964T>C/p.I655T in patient OG/97-3941 with a high-microsatellite-instability colorectal tumor; the study cohort comprised 300 newly diagnosed colorectal cancer patients and 29 high-MSI tumors.
  • PMID:11376800 reports germline MLH1 I655T/c.1964T>C in MSI-H colorectal tumor sample MSI 13; the study screened 345 colorectal cancers and identified 35 MSI-H tumors.
  • The VCEP rule requires MLH1 promoter methylation to be excluded in the tumor, and that exclusion is not reported in the available variant-specific evidence.
  • The exact variant notations were searched in Table-for-CMMRD-diagnosis.pdf.txt and VCEP-pilot-variants---MMR.xlsx.txt; neither file contained a matching entry.
Still missing
  • MLH1 promoter methylation exclusion is not documented for the reported tumor(s).
  • The available evidence does not establish that the reported MSI-H result used the VCEP's specified standard 5-10-marker panel or tumor-genome criterion.
  • No entry for c.1964T>C, p.Ile655Thr, or p.I655T was found in Table-for-CMMRD-diagnosis.pdf.txt.
  • No entry for c.1964T>C, p.Ile655Thr, or p.I655T was found in VCEP-pilot-variants---MMR.xlsx.txt.
Sources
BS2 VCEPNot assessed: no documented in-trans pathogenic MLH1 variant, confirmed phase, qualifying late-onset cancer, or CMMRD assessment is available for the BS2 rule. Details ▾Hide ▴
Reasoning

The governing VCEP BS2 rule requires confirmed in-trans co-occurrence with a known pathogenic variant in the same gene, a qualifying late-onset Lynch-spectrum cancer, absence of CMMRD manifestations, and phase confirmation through parental or offspring testing. The available case evidence provides no documented in-trans pathogenic MLH1 variant, phase confirmation, qualifying patient phenotype, or CMMRD assessment, so the rule cannot be evaluated. The governing VCEP pilot file was searched for c.1964T>C, p.Ile655Thr, and p.I655T; it contains no exact entry for this variant.

VCEP 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<sup>​d​</sup>), and who has no previous or current evidence of clinical manifestations of CMMRD as per Aronson et al 2022 (Refer to 'Table for CMMRD diagnosis.pdf'). Confirmation of phase requires testing of parents or offspring.
Evidence considered
  • ClinGen InSiGHT MLH1 v2.0 CSPEC BS2 rule requires in-trans co-occurrence with a known pathogenic same-gene variant in a patient meeting the specified late-onset cancer condition, no clinical manifestations of CMMRD, and phase confirmation by parental or offspring testing.
  • The reviewed case bundle contains no documented in-trans pathogenic MLH1 variant, phase-confirming parental or offspring test, qualifying cancer-age assessment, or CMMRD assessment.
  • VCEP-pilot-variants---MMR.xlsx full-text conversion: searched c.1964T>C, p.Ile655Thr, and p.I655T; no exact row for this variant was found.
Still missing
  • No case evidence documents a known pathogenic MLH1 variant in trans.
  • No parental or offspring testing confirms phase.
  • No qualifying colorectal or other Lynch-spectrum cancer age and no assessment excluding CMMRD manifestations are available.
  • VCEP-pilot-variants---MMR.xlsx was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
Sources
BS4 VCEPNot assessed: no non-segregating affected relatives or combined Bayes Likelihood Ratio below the VCEP thresholds were reported. Details ▾Hide ▴
Reasoning

The VCEP requires a combined Bayes Likelihood Ratio for lack of co-segregation: less than 0.05 for Strong or greater than 0.05 and no more than 0.48 for Supporting. No affected-relative non-segregation data, pedigree analysis, or combined Bayes Likelihood Ratio was reported, so BS4 cannot be evaluated.

Evidence considered
  • ClinGen InSiGHT MLH1 specification v2.0, BS4: Strong requires a combined Bayes Likelihood Ratio <0.05, and Supporting requires >0.05 and <=0.48; no such value or non-segregation analysis was available.
Still missing
  • Variant genotypes and disease status for informative relatives demonstrating non-segregation.
  • A combined Bayes Likelihood Ratio calculated under the VCEP segregation framework.
Sources
BP5 VCEPNot assessed: reported tumors are MSI-H, whereas BP5 requires qualifying MSS/no-loss tumors or BRAF V600E/MLH1 methylation evidence. Details ▾Hide ▴
Reasoning

The VCEP requires either 2 or 3 qualifying tumors for BP5 Supporting or at least 4 qualifying tumors for BP5 Strong, specifically CRC/endometrial tumors with MSS and/or no MMR-protein loss, or specified LS-spectrum tumors with inconsistent protein loss; an alternative requires BRAF V600E or MLH1 methylation with MSI-H/MLH1 loss. The available variant-specific evidence reports MSI-H colorectal tumors, not the required benign-pattern tumor findings, and does not provide a qualifying tumor count or the BRAF/methylation findings.

VCEP rule
2 or 3 tumors: CRC/Endometrial tumors with MSS and/or no loss of MMR protein expression and/or LS spectrum tumors<sup>d</sup> with loss of MMR protein(s) that is inconsistent with the gene demonstrating genetic variation. OR 1 BRAF V600E (Colon only)/_MLH1_ methylation (in LS spectrum tumor only) with MSI-H/_MLH1_ loss.
Evidence considered
  • PMID:10970186 describes a high-MSI colorectal tumor in a carrier of c.1964T>C, which does not establish the BP5 MSS/no-MMR-loss pathway.
  • PMID:11376800 describes the variant in an MSI-H colorectal tumor, which does not establish the BP5 MSS/no-MMR-loss pathway.
  • No BRAF V600E or MLH1 promoter methylation result meeting the BP5 alternative is reported in the available evidence.
Still missing
  • No qualifying MSS or no-loss-of-MMR-protein tumor count is available for this variant.
  • No qualifying LS-spectrum tumor with MMR-protein loss inconsistent with MLH1 variation is documented.
  • No qualifying BRAF V600E or MLH1 methylation finding with MSI-H/MLH1 loss is documented.
Sources
Not applicable · 12· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: c.1964T>C is an exon-17 missense SNV, while the governing PVS1 decision-tree path applies to nonsense or frameshift variants predicted to undergo NMD. Details ▾Hide ▴
Reasoning

PVS1 is not applicable under the governing MLH1 VCEP rules. NM_000249.4:c.1964T>C, NP_000240.1:p.(Ile655Thr) / p.(I655T), is an SNV annotated as a missense variant in exon 17, not a nonsense or frameshift variant, canonical splice-site variant, large genomic alteration, initiation-codon variant, or confirmed aberrant-splicing variant producing a qualifying loss-of-function consequence. The governing PVS1 decision tree's applicable NMD path is explicitly for nonsense or frameshift variants, and its full-strength PVS1 outcome therefore cannot be applied to this missense SNV. The exact variant was searched in PVS1_DecisionTree_MMR.pdf.txt and VCEP-pilot-variants---MMR.xlsx.txt under c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry was found in either file.

VCEP rule
Nonsense or frameshift | Predicted to undergo NMD: 1) <= codon 684 in MLH1; 2) <= codon 861 in MSH2; 3) <= codon 1317 in MSH6; 4) <= codon 798 in PMS2 | PVS1
Evidence considered
  • Case consequence facts: NM_000249.4:c.1964T>C produces NP_000240.1:p.(Ile655Thr) / p.(I655T), is classified as missense, is not a canonical splice-consensus variant, and lies in exon 17.
  • PVS1_DecisionTree_MMR.pdf.txt, page 1: the NMD-predicted full-strength PVS1 row is specifically for nonsense or frameshift variants; no missense path is provided.
  • Takahashi et al. 2007, Table 1, row I655T: the exact variant is reported as 1964T>C and I655T, confirming a missense substitution.
  • Morak et al. 2019, Table 1 and the class 3 MMR variant results: MLH1 exon 17 c.1964T>C p.(Ile655Thr) is listed as a missense variant, with no detectable splicing effect in full-length transcript analysis.
  • PVS1_DecisionTree_MMR.pdf.txt and VCEP-pilot-variants---MMR.xlsx.txt were each searched for c.1964T>C, p.Ile655Thr, and p.I655T; neither contained an exact row for this variant.
Still missing
  • PVS1_DecisionTree_MMR.pdf.txt was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
  • VCEP-pilot-variants---MMR.xlsx.txt was searched for c.1964T>C, p.Ile655Thr, and p.I655T; no exact entry for this variant was found.
Sources
PS4 VCEPNot applicable: the MLH1 VCEP explicitly marks PS4 Not Applicable. Details ▾Hide ▴
Reasoning

The MLH1 Version 2.0 InSiGHT specification explicitly marks PS4 as Not Applicable. Therefore, no case-control enrichment calculation is performed for this criterion.

VCEP rule
Not Applicable
Evidence considered
  • The governing MLH1 VCEP CSPEC entry lists PS4 applicability as Not Applicable.
Sources
PM1 VCEPNot applicable: the MLH1 VCEP explicitly marks PM1 Not Applicable, regardless of residue 655 appearing within a listed interaction-domain interval. Details ▾Hide ▴
Reasoning

The MLH1 VCEP marks PM1 Not Applicable. The governing domain schematic was nevertheless searched and lists residue 655 within the MLH3/PMS1/PMS2 interaction interval (506-743), but that domain observation cannot override the VCEP's explicit PM1 applicability designation.

VCEP rule
Not Applicable
Evidence considered
  • The MLH1 VCEP CSPEC entry for PM1 states Not Applicable.
  • MMR-Functional-domains.pdf.txt lists MLH1 domains including MLH3/PMS1/PMS2 interaction at residues 506-743; residue 655 falls within that interval, but this cannot override the VCEP's explicit PM1 applicability designation.
Still missing
  • No p.Ile655Thr or c.1964T>C entry was found in MMR-Functional-domains.pdf.txt; the file lists MLH1 domains but the governing CSPEC marks PM1 Not Applicable.
Sources
PM4 VCEPNot applicable: the MLH1 VCEP explicitly designates PM4 as Not Applicable, and c.1964T>C is a missense SNV without a protein-length change. Details ▾Hide ▴
Reasoning

PM4 is explicitly marked Not Applicable in the MLH1 VCEP specification. The variant is an exon-17 missense SNV, not an in-frame insertion/deletion or other protein-length-changing variant for which PM4 could be considered under a generic framework. The VCEP applicability designation governs and no generic PM4 rule is substituted.

VCEP rule
Not Applicable
Evidence considered
  • The MLH1 CSPEC entry for PM4 states applicability: Not Applicable.
  • The exact variant is reported as I655T / c.1964T>C, a missense substitution, in Takahashi et al. 2007, Table 1.
  • Morak et al. 2019, Table 1, lists MLH1 exon 17 c.1964T>C p.(Ile655Thr) in the missense/in-frame-deletion cohort; this is not an in-frame indel and does not change protein length.
Still missing
  • No c.1964T>C, p.Ile655Thr, or p.I655T entry was found in PVS1_DecisionTree_MMR.pdf.txt.
  • No c.1964T>C, p.Ile655Thr, or p.I655T entry was found in VCEP-pilot-variants---MMR.xlsx.txt.
Sources
PM6 VCEPNot applicable: the VCEP marks PM6 as not applicable and directs assumed de novo evidence to its PS2 point system. Details ▾Hide ▴
Reasoning

The VCEP marks PM6 as Not Applicable and directs the reviewer to PS2; assumed de novo evidence is handled within the VCEP PS2 point system rather than PM6.

VCEP rule
Not Applicable
Evidence considered
  • ClinGen InSiGHT MLH1 specification v2.0, PM6 entry: applicability is Not Applicable and the instructions state, "Please see PS2".
Sources
PP2 VCEPNot applicable: the MLH1 VCEP explicitly marks PP2 Not Applicable for this framework. Details ▾Hide ▴
Reasoning

The MLH1 VCEP CSPEC explicitly marks PP2 Not Applicable, so no gene-level missense-mechanism evidence can be assigned under this governing framework.

VCEP rule
Not Applicable
Evidence considered
  • The MLH1 VCEP CSPEC entry for PP2 states Not Applicable.
Sources
PP5 VCEPNot applicable: the MLH1 VCEP explicitly marks PP5 Not Applicable. Details ▾Hide ▴
Reasoning

The MLH1 Version 2.0 InSiGHT specification explicitly marks PP5 as Not Applicable.

VCEP rule
Not Applicable
Evidence considered
  • The governing MLH1 VCEP CSPEC entry lists PP5 applicability as Not Applicable.
Sources
BP1 VCEPNot applicable: the MLH1 VCEP explicitly marks BP1 Not Applicable for this framework. Details ▾Hide ▴
Reasoning

The MLH1 VCEP CSPEC explicitly marks BP1 Not Applicable, so no benign missense-location evidence can be assigned under this governing framework.

VCEP rule
Not Applicable
Evidence considered
  • The MLH1 VCEP CSPEC entry for BP1 states Not Applicable.
Sources
BP2 VCEPNot applicable: the MLH1 VCEP marks BP2 not applicable and directs evaluators to use BS2 instead. Details ▾Hide ▴
Reasoning

The MLH1 VCEP explicitly marks BP2 as not applicable and instructs that BS2 is used instead. Therefore BP2 cannot be assigned regardless of any observed cis or trans relationship.

VCEP rule
BS2 is used instead.
Evidence considered
  • The MLH1 VCEP PM2/BP2 entry states: ‘BS2 is used instead.’ and marks BP2 not applicable.
Sources
BP3 VCEPNot applicable: the MLH1 VCEP explicitly designates BP3 as Not Applicable, and c.1964T>C is a missense SNV rather than an in-frame deletion in a repeat region. Details ▾Hide ▴
Reasoning

BP3 is explicitly marked Not Applicable in the MLH1 VCEP specification. The variant is an exon-17 missense SNV, not an in-frame deletion in a repetitive region or another variant type named by the original BP3 concept. The VCEP applicability designation governs, so repeat-region context cannot activate BP3 for this variant.

VCEP rule
Not Applicable
Evidence considered
  • The MLH1 CSPEC entry for BP3 states applicability: Not Applicable.
  • The exact variant is a missense substitution reported as I655T / c.1964T>C in Takahashi et al. 2007, Table 1.
  • Morak et al. 2019, Table 1, identifies the exact change as MLH1 exon 17 c.1964T>C p.(Ile655Thr), not an in-frame deletion.
Still missing
  • No c.1964T>C, p.Ile655Thr, or p.I655T entry was found in PVS1_DecisionTree_MMR.pdf.txt.
  • No c.1964T>C, p.Ile655Thr, or p.I655T entry was found in VCEP-pilot-variants---MMR.xlsx.txt.
Sources
BP6 VCEPNot applicable: the MLH1 VCEP explicitly marks BP6 Not Applicable. Details ▾Hide ▴
Reasoning

The MLH1 Version 2.0 InSiGHT specification explicitly marks BP6 as Not Applicable.

VCEP rule
Not Applicable
Evidence considered
  • The governing MLH1 VCEP CSPEC entry lists BP6 applicability as Not Applicable.
Sources
BP7 N/ANot applicable: c.1964T>C is a coding missense variant, not a synonymous or intronic variant within BP7 scope. Details ▾Hide ▴
Reasoning

BP7 is limited by the VCEP to synonymous or intronic variants at or beyond -21/+7 of the exonic boundaries. NM_000249.4:c.1964T>C is a coding missense substitution producing p.Ile655Thr, so it is outside BP7 scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond -21/+7 (5′/3′ exonic). Variants may satisfy both BP7 and BP4.
Evidence considered
  • Case normalization identifies NM_000249.4:c.1964T>C as NP_000240.1:p.(Ile655Thr), a missense SNV rather than a synonymous or intronic variant.
Sources

Identifiers

Gene
MLH1
Transcript
NM_000249.4
Coding (HGVS c.)
NM_000249.4:c.1964T>C
Protein (HGVS p.)
NP_000240.1:p.(Ile655Thr)
GRCh38
chr3:37048584 T>C
GRCh37
chr3:37090075 T>C
Location and type
Exon 17 · missense
ClinVar
41638

Gene diagram

Every interpreted variant in MLH1, mapped onto the exon structure of NM_000249.4. Select a row to find it on the plot.

MLH1NM_000249.4
Fetching transcript structure from UCSC…
gnomAD v4.1 89 / 1,613,532 alleles AF 5.52e-05 · 0 homozygotes · FAF 5.3e-05
gnomAD v2.1 26 / 282,642 alleles AF 9.2e-05 · 0 homozygotes · FAF 0.000127
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 5.5e-05 · 89 / 1,613,532 alleles · 0 hom · FAF 5.3e-05
Middle Eastern1 / 6,082 0.00016
European (Finnish)10 / 63,978 0.00016
European (non-Finnish)77 / 1,179,694 6.5e-05
Remaining individuals1 / 62,480 1.6e-05
0 alternate alleles recorded in 6 other groups: Admixed American, Amish, East Asian, South Asian, Ashkenazi Jewish, African/African American.

gnomAD v2.1

AF 9.2e-05 · 26 / 282,642 alleles · 0 hom · FAF 0.00013
Remaining individuals2 / 7,218 0.00028
European (Finnish)4 / 25,086 0.00016
European (non-Finnish)20 / 129,002 0.00016
0 alternate alleles recorded in 5 other groups: African/African American, Admixed American, Ashkenazi Jewish, East Asian, South Asian.

gnomAD-Canada

AF not recorded · ? / ? alleles

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 5.51585e-05; MAF= 0.00552%, 89/1613532 alleles, homozygotes = 0) and has highest observed frequency in the Middle Eastern population (AF= 0.00016442; MAF= 0.01644%, 1/6082 alleles, homozygotes = 0); grpmax FAF= 5.3e-05.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 9.19892e-05; MAF= 0.00920%, 26/282642 alleles, homozygotes = 0) and has highest observed frequency in the Remaining individuals population (AF= 0.000277085; MAF= 0.02771%, 2/7218 alleles, homozygotes = 0); grpmax FAF= 0.00012675.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 5.432420686657975e-05, 1/18408 alleles, homozygotes = 0).

Open the gnomAD-Canada detail page →

SpliceAI and Pangolin

SpliceAI acceptor lossat -10 bp
0.000
SpliceAI acceptor gainat -70 bp
0.002
SpliceAI donor lossat -272 bp
0.000
SpliceAI donor gainat +433 bp
0.003
Pangolin splice lossmagnitude shown
-0.006
Pangolin splice gain
0.001

Other predictors

REVEL
0.594
BayesDel
0.245

How the predictions were used

BP4 SupportingVCEPMet, Supporting: HCI prior probability is 0.0077, below the VCEP BP4 threshold of <0.11. Details ▾Hide ▴
Reasoning

The variant is a missense SNV, and the VCEP directly assigns BP4_Supporting when the exact HCI prior probability is <0.11. The governing HCI table contains c.1964T>C / p.I655T with pathogenicity probability 0.0077, which is below 0.11. The SpliceAI result is not used for BP4 because that alternative is specified by the VCEP only for intronic and synonymous variants.

VCEP rule
Missense variant with HCI-prior probability of pathogenicity <0.11 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) OR For intronic and synonymous variants: SpliceAI predicts no splicing impact with delta score ≤ 0.1 as per Walker et al 2023
Evidence considered
  • HCI-PRIORS-MLH1.txt.txt, row MLH1_04311: c.1964T>C, p.I655T, HCI prior probability 0.0077.
  • The VCEP's SpliceAI BP4 alternative applies to intronic and synonymous variants; this variant is missense, so the exact HCI prior path governs.
Sources
PP3 VCEPNot met: HCI prior probability is 0.0077, below the PP3 Supporting threshold of >0.68 for missense variants. Details ▾Hide ▴
Reasoning

The variant is a missense SNV, so the VCEP missense HCI-prior path is applicable. The governing PP3 thresholds require an HCI prior probability >0.81 for PP3_Moderate or >0.68 and <=0.81 for PP3_Supporting; the exact HCI table row for c.1964T>C / p.I655T assigns a pathogenicity probability of 0.0077. The VCEP's alternative SpliceAI PP3 path is limited to non-canonical splicing nucleotides and therefore does not apply to this coding missense substitution. No PP3 evidence is met.

VCEP rule
Missense variant with HCI prior probability for pathogenicity >0.81 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) ... Missense variant with HCI prior probability for pathogenicity >0.68 & ≤0.81 as per [https://hci-priors.hci.utah.edu/PRIORS](https://hci-priors.hci.utah.edu/PRIORS) OR Predicted splice defect for non-canonical splicing nucleotides using SpliceAI with delta score >= 0.2 as per Walker et al 2023.
Evidence considered
  • HCI-PRIORS-MLH1.txt.txt, row MLH1_04311: c.1964T>C, p.I655T, HCI prior probability 0.0077; the row also reports MAPP score 6.75 and Custom_PP2 score 0.001, which are not named by the PP3 rule.
  • The case normalization identifies NM_000249.4:c.1964T>C as NP_000240.1:p.(Ile655Thr), a missense SNV; the VCEP SpliceAI alternative is restricted to non-canonical splicing nucleotides and is not applicable here.
Sources
BP7 N/ANot applicable: c.1964T>C is a coding missense variant, not a synonymous or intronic variant within BP7 scope. Details ▾Hide ▴
Reasoning

BP7 is limited by the VCEP to synonymous or intronic variants at or beyond -21/+7 of the exonic boundaries. NM_000249.4:c.1964T>C is a coding missense substitution producing p.Ile655Thr, so it is outside BP7 scope.

VCEP rule
A synonymous (silent) or intronic variant at or beyond -21/+7 (5′/3′ exonic). Variants may satisfy both BP7 and BP4.
Evidence considered
  • Case normalization identifies NM_000249.4:c.1964T>C as NP_000240.1:p.(Ile655Thr), a missense SNV rather than a synonymous or intronic variant.
Sources

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00). REVEL score = 0.594. BayesDel score = 0.2451. HCI prior probability for pathogenicity = 0.0077. MAPP score = 6.75. Custom PP2 score = 0.001.

8 paper records listed. 2 cited in the classification.

Cited in the classification

  • Functional analysis of human MLH1 variants using yeast and in vitro mismatch repair assays.
    Takahashi M et al. · 2007 May 15
    Takahashi et al. explicitly report MLH1 c.1964T>C as I655T in a missense-variant functional study; the exact variant is not a truncating or in-frame deletion allele.
    → BS3 · supporting Names this variant
    PMID 17510385 ↗
    Source detail
    I655Tc 1964T>C + + + 73.8 >75 0.35 NI 25

    Location Table 1, Summary of MLH1 variants (continued), row I655T

    Context Three Saccharomyces cerevisiae dominant-mutator assays, an in-vitro mismatch-repair assay, and relative MLH1 expression testing in HCT116-derived extracts/cells.

  • Full-length transcript amplification and sequencing as universal method to test mRNA integrity and biallelic expression in mismatch repair genes.
    Morak M et al. · 2019 Dec
    Morak et al. explicitly list MLH1 exon 17 c.1964T>C p.(Ile655Thr) as a missense/in-frame-deletion cohort variant and report no detectable splice effect; the exact variant is not an in-frame deletion.
    → BS3 · supporting Names this variant
    PMID 31332305 ↗
    Source detail
    MLH1 e17 c.1964T>C p.(lle655Thr) 3 –

    Location Table 1, variants of uncertain significance; Results, subsection Missense variants or small in-frame deletions

    Context Full-length MLH1 transcript amplification and Sanger sequencing from cultured lymphocytes, with and without puromycin-mediated nonsense-mediated decay inhibition, in a cohort of class 3 MMR variants.

Other recorded publications

  • Causes of microsatellite instability in colorectal tumors: implications for hereditary non-polyposis colorectal cancer screening.
    Potocnik U et al. · 2001
    This paper reports germline MLH1 I655T/c.1964T>C in MSI-H colorectal tumor sample MSI 13. The study screened 345 colorectal cancers, including 35 MSI-H tumors, but does not report MLH1 promoter methylation exclusion, MMR-protein loss assessment, or a benign-pattern tumor result for this variant.
    Names this variant
    PMID 11376800 ↗
    Quoted passage
    Three missense mutations in hMLH1 were previously described in Swedish (Q67R, A441T) [41] and German (I655T) [42] population.

    Results, section 3.2.1 (Germline mutations and polymorphisms); Table 2, tumor sample MSI 13

  • Classification of mismatch repair gene missense variants with PON-MMR.
    Ali H et al. · 2012
    No paper-specific finding is recorded.
    PMID 22290698 ↗
  • Guidelines on genetic evaluation and management of Lynch syndrome: a consensus statement by the US Multi-society Task Force on colorectal cancer.
    No paper-specific finding is recorded.
    PMID 25070057 ↗
  • 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.
    No paper-specific finding is recorded.
    PMID 25741868 ↗
  • Analysis for microsatellite instability and mutations of the DNA mismatch repair gene hMLH1 in familial gastric cancer.
    The paper describes the MLH1 c.1964T>C variant as an isoleucine-to-threonine substitution at codon 655 in a gastric-cancer patient and does not provide a VCEP Pathogenic same-residue comparator for PS1 or PM5.
    Names this variant
    PMID 8938136 ↗
    Quoted passage
    Sequencing of non-tumorous and tumor DNA revealed a T to C transition at codon 655, leading to an amino-acid change from isoleucine to threonine. The same aberrant SSCP pattern and sequencing result was also found in genomic DNA isolated from the blood of this patient.

    Results, “Mutation analysis of the hMLH1 gene”; Discussion, paragraph beginning “The hMLH1 gene is one of the mismatch repair genes”

  • Incidence of germline hMLH1 and hMSH2 mutations (HNPCC patients) among newly diagnosed colorectal cancers in a Slovenian population.
    The paper reports germline MLH1 c.1964T>C/p.I655T in patient OG/97-3941, whose colorectal tumor had high microsatellite instability; the patient later developed gastric cancer. No parental testing or segregation analysis was reported.
    Names this variant
    PMID 10970186 ↗
    Quoted passage
    A substitution of Ile to Thr at codon 655 detected in a patient OG/97-3941 was previously reported in a patient with gastric carcinoma.32 Interestingly, also, Slovenian patient OG/97-3941 had a metachronic gastric cancer two years after colon cancer.

    Results and Discussion; Table 1, pathogenic germline hMLH1 and hMSH2 mutations

  • DHPLC mutation analysis of the hereditary nonpolyposis colon cancer (HNPCC) genes hMLH1 and hMSH2.
    No paper-specific finding is recorded.
    PMID 11179758 ↗

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= 5.51585e-05; MAF= 0.00552%, 89/1613532 alleles, homozygotes = 0) and has highest observed frequency in the Middle Eastern population (AF= 0.00016442; MAF= 0.01644%, 1/6082 alleles, homozygotes = 0); grpmax FAF= 5.3e-05.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 9.19892e-05; MAF= 0.00920%, 26/282642 alleles, homozygotes = 0) and has highest observed frequency in the Remaining individuals population (AF= 0.000277085; MAF= 0.02771%, 2/7218 alleles, homozygotes = 0); grpmax FAF= 0.00012675.

gnomAD-Canada

This variant is present in gnomAD-Canada v1.0 (AF= 5.432420686657975e-05, 1/18408 alleles, homozygotes = 0).

ClinVar

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

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.00). REVEL score = 0.594. BayesDel score = 0.2451. HCI prior probability for pathogenicity = 0.0077. MAPP score = 6.75. Custom PP2 score = 0.001.

Functional

OncoKB did not identify variant-specific reviewed functional evidence for this variant; gene-level curated context is available for reviewer follow-up. MLH1, a DNA mismatch repair protein, is recurrently altered by deletion and mutation in various cancer types.

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.