Five-step scale from benign to pathogenic. This variant is uncertain. Select a step to read what it means.
This variantScenario
BenignPathogenic
Uncertain.The recorded classification is uncertain significance.
In plain language
Gene-level background from the recorded interpretation.
Words with a dotted underline have a short definition. Hover or tap them.
About KRAS
KRAS encodes a small GTPase in the RAS family that cycles between active and inactive states to regulate cell growth and signaling through pathways such as MAPK/ERK and PI3K/AKT/mTOR. Activating changes in KRAS are common drivers of many cancers, including pancreatic, colorectal, and lung cancers, where they promote uncontrolled cell proliferation. Germline alterations in KRAS also cause developmental disorders such as Noonan syndrome and cardio-facio-cutaneous syndrome, which carry an increased predisposition to cancer.
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 KRAS VCEP v2.3. 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.
Met (Supporting): the variant is absent from gnomAD v2.1, v4.1, and gnomAD-Canada v1.0.
Benign criteria applied · 1
BP1Supporting
BP1 · supporting
Met (Supporting): p.(Glu98Ter) truncates the protein in KRAS, a gain-of-function disease gene without established loss-of-function correlation.
Recorded classification: Uncertain significance
VUS: only PM2 (Supporting, absent from gnomAD) and BP1 (Supporting, truncating variant in a gain-of-function gene) were met; no pathogenic or benign rule is satisfied.
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
Not recorded
gnomAD v4.1 allele counts were not recorded for this variant.
ACMG/AMP criteria under ClinGen KRAS VCEP v2.3, with the data and sources behind each one.
28 criteria with recorded statuses: 2 met · 3 not met · 9 not assessed · 14 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.
KRAS is governed by the ClinGen RASopathy VCEP specification v2.3, which explicitly sets PVS1 and BP3 to Not Applicable at the gene level, reflecting that RASopathy disease mechanism is gain-of-function/dominant-negative rather than loss-of-function/haploinsufficiency.
This is a nonsense variant (NM_033360.4:c.292G>T, p.(Glu98Ter)); PM4 (protein length change) does not apply because PM4 addresses in-frame indels and stop-loss variants, not nonsense truncations, independent of the VCEP's repeat-region note.
The VCEP's BP1 rule (outside this criterion group) is the intended pathway for evaluating truncating variants like this one in RASopathy genes, not PVS1/PM4/BP3.
Variant is a nonsense/truncating change, p.(Glu98Ter), which is fundamentally incompatible with the missense-based PS1 and PM5 comparator rules in the KRAS RASopathy VCEP v2.3 spec, and PP2 is globally not applicable for KRAS under this spec.
PM1's four defined critical domains (P-loop, SW1, SW2, SAK) do not include residue 98, so PM1 is not met.
BP1 applies because the variant is truncating and the KRAS RASopathy VCEP spec both explicitly instructs BP1 use for truncating variants under the gene's GOF-only mechanism and independently marks PVS1 not applicable for KRAS, though the dedicated dosage-sensitivity supplement was not available to fully corroborate the LOF-correlation determination.
PS3 is applicable per the RASopathy VCEP framework but no VCEP-approved functional assay (RAS/MEK/ERK activation) results were located for this specific nonsense variant, p.(Glu98Ter); the only functional-adjacent annotation (OncoKB) is a discordant curated database label, not an approved assay result, so PS3 is not_assessed pending human review of primary functional data sources.
BS3 is marked Not Applicable by the governing RASopathy VCEP specification for KRAS.
Variant is NM_033360.4:c.292G>T, a nonsense (stop-gain) change producing NP_203524.1:p.(Glu98Ter), not a missense or synonymous variant.
The KRAS RASopathy VCEP (cspec v2.3) scopes PP3/BP4 to missense variants (REVEL threshold) or splicing-impact matching disease mechanism, and scopes BP7 to synonymous/intronic non-coding variants. None of these applicability conditions are met by a nonsense variant.
SpliceAI predicts no significant splice impact (max delta 0.054), which is consistent with the variant's mechanism being nonsense-mediated truncation rather than splicing disruption; this does not activate the PP3/BP4 splicing-impact alternate path since the disease mechanism here is not splicing.
BayesDel score (0.655873) is available but withheld from PP3/BP4 consideration per pipeline policy: no verified published calibration threshold/PMID exists for BayesDel.
REVEL is not available (variant is not missense), consistent with not_applicable for the missense in-silico path.
The ClinGen RASopathy Expert Panel KRAS v2.3 specification is the governing framework for BA1, BS1, BS2, and PM2; generic ACMG/AMP population rules were not substituted.
BA1 and BS1 are not met because the variant is absent from gnomAD v2.1 and v4.1, far below the VCEP thresholds of 0.05% and 0.025%, respectively.
BS2 is not assessed because there are no phenotypically characterized healthy or apparently unaffected carrier observations that can receive a VCEP point score.
PM2_Supporting is met because the variant is absent from gnomAD v2.1 and v4.1; gnomAD-Canada v1.0 is concordantly negative.
No criteria match.
Met · 2
PM2SupportingMet (Supporting): the variant is absent from gnomAD v2.1, v4.1, and gnomAD-Canada v1.0.
Details ▾Hide ▴
Reasoning
PM2_Supporting is met. The governing ClinGen RASopathy Expert Panel KRAS v2.3 rule requires the variant to be absent from controls (gnomAD). Direct queries found this variant absent from both gnomAD v2.1 and gnomAD v4.1. Its additional absence from gnomAD-Canada v1.0 is concordant. No frequency, ancestry-specific enrichment, or homozygote observation creates a threshold artifact.
Rule
The variant must be absent from controls (gnomAD); Supporting strength (ClinGen RASopathy Expert Panel KRAS v2.3).
Evidence considered
The KRAS RASopathy VCEP v2.3 PM2 rule assigns Supporting strength when the variant is absent from controls (gnomAD).
Direct variant queries reported NM_033360.4:c.292G>T / GRCh37 12-25378706-C-A absent from gnomAD v2.1 and GRCh38 chr12-25225772-C-A absent from gnomAD v4.1; gnomAD-Canada v1.0 also reported absence.
BP1SupportingMet (Supporting): p.(Glu98Ter) truncates the protein in KRAS, a gain-of-function disease gene without established loss-of-function correlation.
Details ▾Hide ▴
Reasoning
The KRAS RASopathy VCEP v2.3 spec directs that, because the RASopathy disease mechanism is gain-of-function, BP1 should be applied to any truncating variant (nonsense, frameshift, canonical splice-site, initiation codon, or whole-gene/multi-exon deletion) in genes without an established loss-of-function correlation to disease. NM_033360.4:c.292G>T produces p.(Glu98Ter), a nonsense/truncating variant. This same VCEP v2.3 spec independently marks PVS1 'Not Applicable' for KRAS, consistent with KRAS RASopathy pathogenicity being driven by gain-of-function/activating missense mechanisms rather than loss-of-function, supporting BP1 applicability here. OncoKB's variant-level annotation for this allele also characterizes its biological effect as likely loss-of-function, consistent with a benign-leaning truncating change under a GOF disease mechanism.
Rule
BP1 (VCEP KRAS v2.3): Truncating variant in a gene without established LOF-disease correlation, given RASopathy GOF mechanism.
Evidence considered
cSpec (KRAS RASopathy VCEP v2.3) BP1 rule: 'Given the disease mechanism is gain-of-function for RASopathies, BP1 should be used for any truncating variant ... in genes without established LOF correlation to disease.'
cSpec (KRAS RASopathy VCEP v2.3) marks PVS1 'Not Applicable' for KRAS, consistent with a GOF-only disease mechanism and absence of an established LOF-disease correlation for this gene within the spec.
OncoKB variant page for KRAS E98* records biological-effect context as 'Likely Loss-of-function', consistent with this nonsense variant acting through loss rather than gain of function.
Still missing
The VCEP BP1 rule text refers reviewers to supplemental gene-specific dosage-sensitivity material to confirm KRAS lacks an established LOF-disease correlation; that supplemental dosage table was not present in this case's VCEP materials bundle, so this determination relies on the spec's PVS1='Not Applicable' designation for KRAS as a proxy rather than direct dosage-sensitivity documentation.
PM1Not met: residue 98 falls outside the four critical domains (P-loop, Switch I, Switch II, SAK) defined by the VCEP.
Details ▾Hide ▴
Reasoning
PM1 in the KRAS RASopathy VCEP v2.3 spec is restricted to four critical, well-established functional domains: P-loop (aa 10-17), Switch I/SW1 (aa 25-40), Switch II/SW2 (aa 57-64), and the SAK region (aa 145-156), and is explicitly stated as not applicable to specific amino acid residues (which fall under PM5 instead). Residue 98 (Glu98) does not fall within any of these four domains, so PM1 is not met.
Rule
PM1 (VCEP KRAS v2.3): Applicable only to critical/well-established functional domains (P-loop 10-17, SW1 25-40, SW2 57-64, SAK 145-156).
Evidence considered
cSpec (KRAS RASopathy VCEP v2.3) PM1 rule and the VCEP domain-alignment slide deck restrict PM1 to P-loop (10-17), SW1 (25-40), SW2 (57-64), and SAK (145-156); residue 98 falls outside all four ranges.
BA1Not met: the variant is absent from gnomAD, so the >=0.05% frequency threshold for BA1 cannot be reached.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy Expert Panel KRAS v2.3 specification defines BA1 as gnomAD filtering allele frequency >=0.05% (Stand Alone). This variant is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0, so no total or ancestry-specific frequency can meet the BA1 threshold.
The KRAS RASopathy VCEP v2.3 BA1 rule requires a gnomAD filtering allele frequency of at least 0.05%.
Direct variant queries reported NM_033360.4:c.292G>T / GRCh37 12-25378706-C-A absent from gnomAD v2.1 and GRCh38 chr12-25225772-C-A absent from gnomAD v4.1 and gnomAD-Canada v1.0.
BS1Not met: the variant is absent from gnomAD, so the >=0.025% frequency threshold for BS1 cannot be reached.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy Expert Panel KRAS v2.3 specification defines BS1 as gnomAD filtering allele frequency >=0.025% (Strong). The variant is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0; it therefore cannot meet this threshold. Disease prevalence, autosomal-dominant inheritance, and penetrance need not be recalibrated because the applicable VCEP specification supplies the threshold.
The KRAS RASopathy VCEP v2.3 BS1 rule requires a gnomAD filtering allele frequency of at least 0.025%.
Direct variant queries reported NM_033360.4:c.292G>T / GRCh37 12-25378706-C-A absent from gnomAD v2.1 and GRCh38 chr12-25225772-C-A absent from gnomAD v4.1 and gnomAD-Canada v1.0.
PS2Not assessed: no affected proband with parental testing is documented, so de novo occurrence cannot be confirmed.
Details ▾Hide ▴
Reasoning
No affected proband with parental testing is documented for this variant; confirmed de novo occurrence cannot be established.
Rule
KRAS RASopathy VCEP PS2: 1 point = Moderate; 2 points = Strong; 4 points = Very Strong.
Evidence considered
The KRAS RASopathy VCEP specification uses PS2 point-based strengths: 1 point (Moderate), 2 points (Strong), and 4 points (Very Strong). The supplied case evidence contains no germline proband, parental genotype, parentage, or phenotype data for NM_033360.4:c.292G>T.
Still missing
Variant testing results for both biological parents, including confirmation of parentage, are needed.
For each confirmed de novo proband, phenotype specificity and the RASopathy diagnosis must be documented to assign the VCEP point total.
PS3Not assessed: no VCEP-approved functional assay (RAS, MEK, or ERK activation) results were available for this variant.
Details ▾Hide ▴
Reasoning
The ClinGen RASopathy VCEP (cspec v2.3) makes PS3 applicable for KRAS, requiring one or more of the VCEP-approved functional assays (RAS Activation Assay, MEK Activation Assay, ERK Activation Assay) to reach Supporting (1 assay) or Moderate (2+ assays) strength. No results from any of these approved assays for this specific variant, NM_033360.4:c.292G>T (p.Glu98Ter), were found in the case bundle. OncoKB annotates a 'biological-effect context' of Likely Loss-of-function but an overall curated oncogenicity label of Likely Neutral for this variant; this is a curated database summary, not a description of a VCEP-approved wet-lab functional assay, is internally discordant, and does not specify assay methodology, controls, or replicate data, so it cannot be used to satisfy PS3. The two full-text literature papers retrieved for functional/OncoKB themes (PMID:28978093, PMID:34117033) were searched for this exact variant and neither mentions c.292G>T, p.Glu98Ter, or p.E98* anywhere in the text; they discuss KRAS/NRAS mutations in colorectal cancer cohorts generally without addressing this specific nonsense variant, so they cannot be grounded citations for PS3.
Evidence considered
cspec (RASopathy VCEP v2.3) defines PS3 for KRAS as Supporting for one approved assay, Moderate for two or more different approved assays, drawn from the VCEP-approved functional studies list (RAS Activation Assay, MEK Activation Assay, ERK Activation Assay, and gene-specific assays for other RASopathy genes)
OncoKB entry for KRAS p.E98* reports biological-effect context 'Likely Loss-of-function' but curated oncogenicity label 'Likely Neutral' -- an internally discordant, non-assay-based curation that does not meet the VCEP's approved-assay requirement for PS3
PMID:28978093 (Molecular characterization of circulating colorectal tumor cells) full text was searched for c.292G>T, Glu98Ter, and E98* and does not mention this variant
PMID:34117033 (Clinical and Functional Characterization of Atypical KRAS/NRAS Mutations in Metastatic Colorectal Cancer) full text was searched for c.292G>T, Glu98Ter, and E98* and does not mention this variant
Still missing
No RAS Activation Assay, MEK Activation Assay, or ERK Activation Assay data identified for p.(Glu98Ter)
OncoKB curated classification is discordant (Likely Loss-of-function biological effect vs Likely Neutral oncogenicity label) and is not a described wet-lab assay, so it cannot substitute for an approved functional study
No variant-specific full-text literature identified describing a validated functional assay for this variant
PS4Not assessed: no germline RASopathy case series or proband counts were available to establish enrichment.
Details ▾Hide ▴
Reasoning
The KRAS RASopathy VCEP specification uses a point-based PS4 framework (Supporting at >=1 point, Moderate at >=3 points, Strong at >=5 points). The case bundle contains no germline RASopathy case series, phenotype-defined proband count, control comparison, or point assignment for p.(Glu98Ter). Somatic cancer observations cannot establish enrichment for the germline RASopathy indication.
The governing ClinGen RASopathy Expert Panel KRAS v2.3 framework specifies PS4 at Supporting for >=1 point, Moderate for >=3 points, and Strong for >=5 points.
COSMIC records three somatic cancer observations, which are not phenotype-defined germline RASopathy cases and do not provide a PS4 enrichment comparison.
Still missing
Phenotype-defined germline RASopathy proband data for p.(Glu98Ter), including the VCEP point calculation and any case-control enrichment analysis, are required.
PM6Not assessed: no proband with untested parents is documented, so assumed de novo occurrence cannot be established.
Details ▾Hide ▴
Reasoning
No proband occurrence with unavailable or untested parental samples is documented; assumed de novo occurrence cannot be established.
Rule
KRAS RASopathy VCEP PM6: 0.5 point = Supporting; 1 point = Moderate; 2 points = Strong.
Evidence considered
The KRAS RASopathy VCEP specification uses PM6 point-based strengths: 0.5 point (Supporting), 1 point (Moderate), and 2 points (Strong). The supplied case evidence contains no germline proband or parental-testing status for this variant.
Still missing
Document one or more affected probands carrying NM_033360.4:c.292G>T with parental samples unavailable or untested.
For each occurrence, document phenotype specificity and the RASopathy diagnosis to assign VCEP de novo points.
The KRAS RASopathy VCEP specification assigns PP1 at Supporting for at least 3 informative meioses, Moderate for at least 5, and Strong for at least 7. No pedigree or relative testing data are present in the supplied case evidence.
Still missing
Provide pedigrees and genotype/phenotype results for informative relatives to count cosegregation meioses.
At least 3, 5, or 7 informative meioses are required for Supporting, Moderate, or Strong evidence, respectively.
BS2Not assessed: no observation of the variant in a healthy individual was documented.
Details ▾Hide ▴
Reasoning
The applicable KRAS VCEP specification uses a phenotypically specified points-based BS2 rule (-4 points for Strong or -1 point for Supporting), rather than generic ACMG BS2. No evidence documents the variant in a healthy homozygous or heterozygous individual, an apparently unaffected family member, or any other observation that can be scored under that rule. The variant is absent from all queried population datasets and thus supplies no homozygote or carrier observation.
Rule
Points-based BS2: -4 points (Strong) or -1 point (Supporting), using RASopathy VCEP phenotypic specifications (ClinGen RASopathy Expert Panel KRAS v2.3).
Evidence considered
The KRAS RASopathy VCEP v2.3 BS2 rule assigns Strong at -4 points and Supporting at -1 point based on phenotypic specifications.
Direct variant queries reported the variant absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0; no homozygote or healthy-carrier observation is available from these sources.
Still missing
Phenotypically characterized healthy or apparently unaffected carrier observations, with the information needed to assign the VCEP BS2 point score, are unavailable.
The KRAS RASopathy VCEP specification permits BS4 at Strong strength with one informative meiosis. The supplied case evidence contains no pedigree, relative genotype, or phenotype information.
Still missing
Provide genotype and phenotype data for at least one informative meiosis demonstrating non-segregation, with phenotyping adequate for the relevant KRAS-associated condition.
BP2Not assessed: no affected-proband or phase data were available for the VCEP's BP2 point-based evidence.
Details ▾Hide ▴
Reasoning
No affected-proband observation, second pathogenic variant, phase determination, or phenotype information is provided to award the VCEP BP2 point-based evidence.
Rule
KRAS RASopathy VCEP v2.3 BP2: alternative molecular cause in the same gene with phenotype-consistent severity; Supporting ≥ -1 point, Moderate ≥ -2 points, Strong ≥ -4 points.
Evidence considered
The KRAS RASopathy VCEP specifies BP2 as a point-based criterion for an alternative molecular cause of a RASopathy in the same gene, with phenotype consistent with expected severity; Supporting, Moderate, and Strong require at least -1, -2, and -4 points, respectively.
The consolidated case bundle contains no germline affected-proband observation or co-occurring pathogenic/likely pathogenic KRAS variant, no cis/trans phase result, and no phenotype/severity data from which BP2 points can be assigned.
Still missing
An affected-proband genotype showing a pathogenic or likely pathogenic alternative molecular cause in KRAS, with phase if relevant.
Phenotype and severity information demonstrating consistency with the expected RASopathy severity for the alternative molecular cause.
BP5Not assessed: no phenotype or alternate molecular diagnosis was available for BP5 point scoring.
Details ▾Hide ▴
Reasoning
The KRAS RASopathy VCEP specification applies BP5 by a point system (Supporting at >=-1 point, Moderate at >=-2 points, Strong at >=-4 points). No patient phenotype, alternate molecular diagnosis, or negative-point calculation is available in the bundle for p.(Glu98Ter).
The governing KRAS RASopathy VCEP specification sets BP5 thresholds at >=-1 point (Supporting), >=-2 points (Moderate), and >=-4 points (Strong).
No individual-level alternate-diagnosis evidence or BP5 point total is provided for this variant.
Still missing
A phenotype-documented individual with an independently established alternate molecular diagnosis and the corresponding VCEP negative-point calculation is required.
Not applicable · 14· recorded as not applicableShow reasons ▾Hide reasons ▴PVS1VCEPNot applicable: the RASopathy VCEP excludes PVS1 for KRAS, whose disease mechanism is gain-of-function rather than loss.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy VCEP specification (KRAS v2.3, cspec) explicitly marks PVS1 as Not Applicable for this gene. This variant, NM_033360.4:c.292G>T (NP_203524.1:p.(Glu98Ter)), is a nonsense change producing a premature stop codon, but the VCEP's own gene-level applicability table overrides the generic PVS1 loss-of-function framework because RASopathy disease mechanism for KRAS is gain-of-function/dominant-negative, not haploinsufficiency. The VCEP framework is consistent with this: its BP1 rule instructs that any truncating variant (nonsense, frameshift, canonical splice, initiation codon, or multi-exon deletion) should instead be considered supporting evidence FOR BENIGN in genes without established LOF-disease correlation, which is the opposite direction from PVS1. A generic PVS1 scaffold (pvs1_variant_assessment) in the case bundle suggested a default PVS1 strength assuming generic fallback, but this is superseded by the VCEP's explicit Not Applicable designation, which takes precedence per the applicable-framework hierarchy.
VCEP rule
PVS1 applicability: Not Applicable (ClinGen RASopathy VCEP KRAS v2.3)
Evidence considered
cspec KRAS v2.3 criteria table lists PVS1 with applicability: Not Applicable.
cspec KRAS v2.3 BP1 rule text states RASopathy disease mechanism is gain-of-function, so truncating variants (nonsense, frameshift, canonical splice, initiation codon, whole-gene/multi-exon deletion) should be evaluated toward BP1 (benign) rather than PVS1, in genes without established LOF-disease correlation.
Variant is classified as nonsense (protein_1l: NP_203524.1:p.(E98*)) per case_summary normalization, consistent with the pvs1_variant_assessment scaffold's consequence_class of nonsense, but the VCEP-specific override controls over the generic PMC6185798 PVS1 framework.
PS1N/ANot applicable: p.(Glu98Ter) is a nonsense change, and PS1 requires a missense change matching an established pathogenic variant.
Details ▾Hide ▴
Reasoning
NM_033360.4:c.292G>T produces NP_203524.1:p.(Glu98Ter), a nonsense/stop-gain variant, not a missense substitution. The KRAS RASopathy VCEP PS1 rule ('Same amino acid change as a previously established pathogenic variant regardless of nucleotide change') is written for the classic scenario of two different nucleotide changes converging on the same missense amino-acid substitution. There is no established pathogenic variant in the evidence bundle sharing the same p.(Glu98Ter) outcome via a different nucleotide change, and the pm5_candidates artifact independently confirms this variant's consequence class (nonsense) falls outside the classic same-residue/same-change comparator framework used by this VCEP spec.
Rule
PS1 (VCEP KRAS v2.3): Same amino acid change as a previously established pathogenic variant regardless of nucleotide change.
Evidence considered
cSpec (KRAS RASopathy VCEP v2.3) PS1 rule text requires the same amino acid change as an established pathogenic variant, framed around missense substitutions.
pm5_candidates.json states the variant consequence class is nonsense, not missense, and explicitly falls outside the classic same-residue comparator framework this spec's PM5/PS1-adjacent logic relies on.
Still missing
No comparator search was performed for an independently established pathogenic p.(Glu98Ter) allele arising from a different nucleotide substitution; if one exists in ClinVar it was not surfaced by this case's evidence collection.
PM3VCEPNot applicable: the KRAS RASopathy VCEP specification does not apply PM3 to this gene.
Details ▾Hide ▴
Reasoning
PM3 is not applicable under the KRAS ClinGen RASopathy Expert Panel specification.
VCEP rule
KRAS RASopathy VCEP v2.3: PM3 — Not applicable.
Evidence considered
The governing KRAS ClinGen RASopathy Expert Panel specification explicitly designates PM3 as not applicable. The specified disease context is autosomal dominant RASopathy, so recessive in-trans evidence is not part of this framework.
PM4N/ANot applicable: a nonsense substitution is not an in-frame indel or stop-loss change, which PM4 requires.
Details ▾Hide ▴
Reasoning
The VCEP KRAS v2.3 PM4 rule ('No known repetitive areas in gene. Use as described.') retains the standard ACMG/AMP PM4 scope, which applies to in-frame insertions/deletions or stop-loss variants that alter protein length, not to nonsense variants producing premature truncation. NM_033360.4:c.292G>T is a single-nucleotide substitution creating a premature stop codon (p.Glu98Ter), not an in-frame indel or stop-loss event, so it does not fall within the PM4 protein-length-change scope regardless of the absence of repetitive regions in KRAS.
Rule
PM4: standard scope applies (no repeat-region exclusion) per cspec, but variant is a nonsense substitution, not an in-frame indel/stop-loss, so PM4 is not applicable
Evidence considered
cspec KRAS v2.3 PM4 rule: 'No known repetitive areas in gene. Use as described,' confirming standard scope (in-frame indel/stop-loss protein length change) applies without repeat-region exclusion, but this variant type (nonsense substitution) is outside that scope.
case_summary normalization confirms variant consequence is nonsense (NP_203524.1:p.(E98*)), i.e. premature truncation via stop-gain rather than an in-frame length-altering event.
PM5N/ANot applicable: p.(Glu98Ter) is a nonsense change, not a missense substitution, so the same-residue PM5 rule does not apply.
Details ▾Hide ▴
Reasoning
The KRAS RASopathy VCEP v2.3 PM5 rule is a classic same-residue, alternate-amino-acid-change missense rule (≥1 or ≥2 other [likely] pathogenic residue changes at the same codon). This variant, p.(Glu98Ter), is a nonsense/truncating change, not a missense substitution, so it is not eligible for evaluation under this PM5 framework. The dedicated pm5_candidates lookup for this case explicitly returned eligible_for_classic_pm5_search=false with the same rationale and performed no comparator search.
Rule
PM5 (VCEP KRAS v2.3): ≥1 [likely] pathogenic residue change at the same codon (missense-only framework).
Evidence considered
pm5_candidates.json: 'Framework is classic same-residue missense PM5, but the variant consequence class (nonsense) is not missense'; eligible_for_classic_pm5_search is false and no candidate comparators were collected.
PP2VCEPNot applicable: the KRAS RASopathy VCEP explicitly marks PP2 as not applicable for this gene.
Details ▾Hide ▴
Reasoning
The KRAS RASopathy VCEP v2.3 specification explicitly marks PP2 as 'Not Applicable' for this gene, overriding the generic ACMG PP2 (missense-constrained-gene) criterion.
PP3N/ANot applicable: the REVEL rule covers only missense variants, and SpliceAI shows no splice impact (max delta 0.054).
Details ▾Hide ▴
Reasoning
NM_033360.4:c.292G>T (p.(Glu98Ter)) is a nonsense (stop-gain) variant, not a missense variant, so the KRAS RASopathy VCEP (cspec v2.3) PP3 rule -- 'For missense variants: REVEL >=0.7' -- does not apply; REVEL is not computed for this consequence class (score not_available/null in the bundle). The cspec PP3 rule also allows a splicing-impact path ('For splicing impact, predicted outcome must match disease mechanism'), but SpliceAI shows no significant splice disruption (max delta score 0.054, all DS scores <0.1), so even under that alternate path the prediction does not support a deleterious splicing effect. This variant's predicted pathogenic mechanism is nonsense-mediated truncation/PVS1, not splicing or missense in-silico impact, so PP3 is not applicable rather than not_met.
Rule
cspec PP3 (KRAS RASopathy VCEP v2.3): For missense variants REVEL >=0.7; for splicing impact predicted outcome must match disease mechanism.
Evidence considered
cspec (ClinGen RASopathy VCEP v2.3): PP3 rule scoped to missense variants via REVEL >=0.7, or to splicing impact matching disease mechanism.
SpliceAI: max_delta_score=0.054 (DS_AG 0.001, DS_AL 0.054, DS_DG 0.002, DS_DL 0.0), evidence_sentence 'SpliceAI predicts no significant splice impact for this variant'.
Variant consequence class is nonsense (stop-gain), per pvs1_variant_assessment consequence_class='nonsense', not missense and not a canonical splice-site change.
Case artifact guidance explicitly notes: 'For canonical splice variants, do not stack PP3 for the same splice-effect prediction evidence' -- reinforcing that splicing PP3 is not intended to be layered onto a variant already assessed via the nonsense/PVS1 pathway, and this variant is not even a canonical splice variant.
Still missing
REVEL score not available for this variant (not a missense change, so not expected).
PP5VCEPNot applicable: the VCEP marks PP5 not applicable, and the variant is absent from ClinVar.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy Expert Panel KRAS v2.3 specification explicitly marks PP5 as not applicable. Independently, the exact variant is absent from ClinVar, so there is no exact-variant ClinVar expert-panel Pathogenic/Likely pathogenic assertion that could satisfy the requested restriction.
VCEP rule
ClinGen RASopathy Expert Panel KRAS v2.3: PP5 not applicable; expert-panel-only PP5 restriction was also checked.
Evidence considered
The KRAS RASopathy VCEP specification lists PP5 applicability as 'Not Applicable'.
ClinVar search for KRAS NM_033360.4:c.292G>T returned no result; therefore no exact-variant expert-panel Pathogenic/Likely pathogenic assertion is present.
BS3VCEPNot applicable: the KRAS RASopathy VCEP explicitly marks BS3 as not applicable.
Details ▾Hide ▴
Reasoning
The ClinGen RASopathy VCEP (cspec v2.3) explicitly marks BS3 as Not Applicable for KRAS in this framework version, so BS3 is not adjudicated regardless of any functional data presence or absence.
Evidence considered
cspec (RASopathy VCEP v2.3) lists BS3 with applicability 'Not Applicable' for KRAS
BP3VCEPNot applicable: the VCEP marks BP3 not applicable, and this is a nonsense substitution, not an in-frame indel.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy VCEP specification (KRAS v2.3, cspec) explicitly marks BP3 as Not Applicable for this gene, so no assessment of an in-frame indel in a non-functional/repeat region is performed. This is also moot for the variant type here (nonsense substitution), which is not the in-frame indel category BP3 addresses.
VCEP rule
BP3 applicability: Not Applicable (ClinGen RASopathy VCEP KRAS v2.3)
Evidence considered
cspec KRAS v2.3 criteria table lists BP3 with applicability: Not Applicable.
BP4N/ANot applicable: the REVEL-based BP4 rule covers only missense variants, and BayesDel lacks a verified calibration threshold.
Details ▾Hide ▴
Reasoning
The cspec BP4 rule is scoped to missense variants via REVEL (<=0.3); this is a nonsense variant, so the missense in-silico path does not apply and REVEL is not available. BayesDel score is present (0.655873) but per pipeline policy no verified published calibration threshold is available for BayesDel, so it cannot be used for BP4 regardless of value. SpliceAI shows no splice disruption (max delta 0.054), which would be consistent with a benign splicing prediction, but a negative splicing signal is not informative BP4 evidence for a nonsense variant whose predicted pathogenic mechanism is truncation/PVS1, not splicing -- applying BP4 here would not meaningfully counter or support classification and is outside the CSPEC's defined missense/splicing scope for this variant type.
cspec (ClinGen RASopathy VCEP v2.3): BP4 rule scoped to missense variants via REVEL <=0.3.
SpliceAI: max_delta_score=0.054, no significant splice impact predicted, but not informative for BP4 given the variant's nonsense/truncating mechanism.
BayesDel score 0.655873 recorded but excluded from PP3/BP4 consideration because no verified published threshold/PMID for BayesDel is available to this pipeline.
Variant consequence class is nonsense (stop-gain), not missense, per pvs1_variant_assessment.
Still missing
REVEL score not available (variant is not missense).
BayesDel score available (0.655873) but has no verified published calibration threshold usable by this pipeline for PP3/BP4.
BP6VCEPNot applicable: the VCEP marks BP6 not applicable, and the variant is absent from ClinVar.
Details ▾Hide ▴
Reasoning
The governing ClinGen RASopathy Expert Panel KRAS v2.3 specification explicitly marks BP6 as not applicable. Independently, the exact variant is absent from ClinVar, so there is no exact-variant ClinVar expert-panel Benign/Likely benign assertion that could satisfy the requested restriction.
VCEP rule
ClinGen RASopathy Expert Panel KRAS v2.3: BP6 not applicable; expert-panel-only BP6 restriction was also checked.
Evidence considered
The KRAS RASopathy VCEP specification lists BP6 applicability as 'Not Applicable'.
ClinVar search for KRAS NM_033360.4:c.292G>T returned no result; therefore no exact-variant expert-panel Benign/Likely benign assertion is present.
BP7N/ANot applicable: BP7 applies only to synonymous or intronic variants, not nonsense changes.
Details ▾Hide ▴
Reasoning
The cspec BP7 rule applies only to synonymous (silent) variants or intronic/non-coding positions (excluding canonical splice sites) where splicing prediction shows no impact and the nucleotide is not highly conserved. NM_033360.4:c.292G>T is a nonsense (stop-gain) variant producing p.(Glu98Ter), not a synonymous or intronic/non-coding change, so BP7 is categorically not applicable regardless of the SpliceAI result.
Rule
cspec BP7 (KRAS RASopathy VCEP v2.3): Synonymous or intronic/non-coding variant with no predicted splice consensus/new splice site impact and non-conserved nucleotide.
Evidence considered
cspec (ClinGen RASopathy VCEP v2.3): BP7 rule text explicitly restricted to synonymous variants or intronic/non-coding positions (excluding canonical splice sites).
Variant consequence class is nonsense (stop-gain) per pvs1_variant_assessment, not synonymous or intronic.
Every interpreted variant in KRAS, mapped onto the exon structure of NM_033360.4. Select a row to find it on the plot.
KRASNM_033360.4
Fetching transcript structure from UCSC…
Exons
—
Transcript span
—
Strand
—
Variants mapped
—
Source
UCSC ncbiRefSeqCurated
All variants in KRAS—Select a row to find it on the plot; use the link to open its page.
Protein
Location
Classification
Link
gnomAD v4.1Allele count data not recorded
gnomAD v2.1Allele count data not recorded
gnomAD-Canada v1.0Allele count data not recorded
Statements
gnomAD v4.1
Absent from gnomAD v4.1.
gnomAD v2.1
Absent from gnomAD v2.1.
gnomAD-Canada
Absent from gnomAD-Canada v1.0.
SpliceAI and Pangolin
SpliceAI acceptor lossat -1 bp
0.054
SpliceAI acceptor gainat +1 bp
0.001
SpliceAI donor lossat -409 bp
0.000
SpliceAI donor gainat +170 bp
0.002
Pangolin splice lossmagnitude shown
-0.031
Pangolin splice gain
0.002
Other predictors
REVEL
Not available
BayesDel
0.656
How the predictions were used
PP3N/ANot applicable: the REVEL rule covers only missense variants, and SpliceAI shows no splice impact (max delta 0.054).
Details ▾Hide ▴
Reasoning
NM_033360.4:c.292G>T (p.(Glu98Ter)) is a nonsense (stop-gain) variant, not a missense variant, so the KRAS RASopathy VCEP (cspec v2.3) PP3 rule -- 'For missense variants: REVEL >=0.7' -- does not apply; REVEL is not computed for this consequence class (score not_available/null in the bundle). The cspec PP3 rule also allows a splicing-impact path ('For splicing impact, predicted outcome must match disease mechanism'), but SpliceAI shows no significant splice disruption (max delta score 0.054, all DS scores <0.1), so even under that alternate path the prediction does not support a deleterious splicing effect. This variant's predicted pathogenic mechanism is nonsense-mediated truncation/PVS1, not splicing or missense in-silico impact, so PP3 is not applicable rather than not_met.
Rule
cspec PP3 (KRAS RASopathy VCEP v2.3): For missense variants REVEL >=0.7; for splicing impact predicted outcome must match disease mechanism.
Evidence considered
cspec (ClinGen RASopathy VCEP v2.3): PP3 rule scoped to missense variants via REVEL >=0.7, or to splicing impact matching disease mechanism.
SpliceAI: max_delta_score=0.054 (DS_AG 0.001, DS_AL 0.054, DS_DG 0.002, DS_DL 0.0), evidence_sentence 'SpliceAI predicts no significant splice impact for this variant'.
Variant consequence class is nonsense (stop-gain), per pvs1_variant_assessment consequence_class='nonsense', not missense and not a canonical splice-site change.
Case artifact guidance explicitly notes: 'For canonical splice variants, do not stack PP3 for the same splice-effect prediction evidence' -- reinforcing that splicing PP3 is not intended to be layered onto a variant already assessed via the nonsense/PVS1 pathway, and this variant is not even a canonical splice variant.
Still missing
REVEL score not available for this variant (not a missense change, so not expected).
BP4N/ANot applicable: the REVEL-based BP4 rule covers only missense variants, and BayesDel lacks a verified calibration threshold.
Details ▾Hide ▴
Reasoning
The cspec BP4 rule is scoped to missense variants via REVEL (<=0.3); this is a nonsense variant, so the missense in-silico path does not apply and REVEL is not available. BayesDel score is present (0.655873) but per pipeline policy no verified published calibration threshold is available for BayesDel, so it cannot be used for BP4 regardless of value. SpliceAI shows no splice disruption (max delta 0.054), which would be consistent with a benign splicing prediction, but a negative splicing signal is not informative BP4 evidence for a nonsense variant whose predicted pathogenic mechanism is truncation/PVS1, not splicing -- applying BP4 here would not meaningfully counter or support classification and is outside the CSPEC's defined missense/splicing scope for this variant type.
cspec (ClinGen RASopathy VCEP v2.3): BP4 rule scoped to missense variants via REVEL <=0.3.
SpliceAI: max_delta_score=0.054, no significant splice impact predicted, but not informative for BP4 given the variant's nonsense/truncating mechanism.
BayesDel score 0.655873 recorded but excluded from PP3/BP4 consideration because no verified published threshold/PMID for BayesDel is available to this pipeline.
Variant consequence class is nonsense (stop-gain), not missense, per pvs1_variant_assessment.
Still missing
REVEL score not available (variant is not missense).
BayesDel score available (0.655873) but has no verified published calibration threshold usable by this pipeline for PP3/BP4.
BP7N/ANot applicable: BP7 applies only to synonymous or intronic variants, not nonsense changes.
Details ▾Hide ▴
Reasoning
The cspec BP7 rule applies only to synonymous (silent) variants or intronic/non-coding positions (excluding canonical splice sites) where splicing prediction shows no impact and the nucleotide is not highly conserved. NM_033360.4:c.292G>T is a nonsense (stop-gain) variant producing p.(Glu98Ter), not a synonymous or intronic/non-coding change, so BP7 is categorically not applicable regardless of the SpliceAI result.
Rule
cspec BP7 (KRAS RASopathy VCEP v2.3): Synonymous or intronic/non-coding variant with no predicted splice consensus/new splice site impact and non-conserved nucleotide.
Evidence considered
cspec (ClinGen RASopathy VCEP v2.3): BP7 rule text explicitly restricted to synonymous variants or intronic/non-coding positions (excluding canonical splice sites).
Variant consequence class is nonsense (stop-gain) per pvs1_variant_assessment, not synonymous or intronic.
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.05). BayesDel score = 0.655873.
2 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
Molecular characterization of circulating colorectal tumor cells defines genetic signatures for individualized cancer care.
Targeted sequencing study of circulating tumor cells (CTCs) versus matched primary tumors in colorectal cancer patients, characterizing KRAS/NRAS/BRAF mutation concordance; full text does not mention the specific variant p.(Glu98Ter)/c.292G>T.
Clinical and Functional Characterization of Atypical KRAS/NRAS Mutations in Metastatic Colorectal Cancer.
Clinical/functional characterization of atypical KRAS/NRAS mutations in metastatic colorectal cancer using an in vitro cell-based functional annotation assay across large tissue and cfDNA cohorts; full text does not mention the specific variant p.(Glu98Ter)/c.292G>T.
The evidence statements recorded by the interpretation pipeline. They have not been reinterpreted by the page.
gnomAD v4.1
Absent from gnomAD v4.1.
gnomAD v2.1
Absent from gnomAD v2.1.
gnomAD-Canada
Absent from gnomAD-Canada v1.0.
ClinVar
This variant is absent from ClinVar.
In silico
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.05). BayesDel score = 0.655873.
Functional
OncoKB identified variant-specific curated literature and context relevant to functional review; biological-effect context: Likely Loss-of-function; curated oncogenicity label: Likely Neutral.
Somatic
This variant does not lie in a statistically significant hotspot. This variant has previously been reported in somatic cancers (COSMIC; COSV55821941, n = 3 times).
Cancer Hotspots
This variant does not lie in a statistically significant hotspot.
This variant was interpreted by pipeline 7.1.5.
The current version is 11.0.07.
Re-running queues a fresh interpretation; the result replaces this page when complete.
Re-runs are not free. Blank draws on today's public interpretation allowance; with a code, it uses one of that code's uses.