0%
Print report
Variant interpretation report

MET c.3082G>C, p.(Asp1028His)

NM_001127500.2:c.3082G>C NP_001120972.1:p.(Asp1028His) Missense · exon 14 View identifiers
Classification
Uncertain significance

Variant description:

No variant summary was recorded for this case.

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

Uncertain.The recorded classification is uncertain significance.

In plain language

Gene-level background from the recorded interpretation.

About MET

MET encodes a receptor tyrosine kinase that serves as the cell-surface receptor for hepatocyte growth factor (HGF). Upon HGF binding, the receptor activates signaling pathways that promote cell growth, survival, movement, and blood vessel formation, and it plays important roles in embryonic development and tissue repair. Mutations in MET are associated with papillary renal cell carcinoma, hepatocellular carcinoma, and various head and neck cancers, and amplification or overexpression of the gene is found in many human cancers, where it can drive tumor growth and spread.

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 Not recorded. 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: 2 Benign evidence criteria: 0
Pathogenic criteria applied · 2
PM2Supporting
PM2 · supporting

Met (Supporting): allele absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0.

PP3Supporting
PP3 · supporting

Met (Supporting): SpliceAI predicts splice-donor loss at the donor position itself (max delta 0.925, above the 0.8 high-precision cutoff).

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: two supporting criteria — PM2 (absent from gnomAD) and PP3 (SpliceAI donor-loss 0.925) — do not reach the evidence threshold for pathogenic or benign classification.

02The sources

Evidence at a glance

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

No screenshot for this evidence
REVEL score
0.374 recorded score

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

ClinVar submissions
Not recorded

A ClinVar laboratory submission summary was not recorded.

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB identified curated literature and non-variant-specific oncogenicity context for review; listed oncogenicity label: not classified.

No listed criterion applied OncoKB ↗
COSMIC
Cancer Hotspots
Somatic evidence
13 recorded samples

This variant has previously been reported in somatic cancers (COSMIC; COSV59259530, n = 13 times).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.

For specialists

Technical detail

ACMG/AMP criteria under Not recorded, with the data and sources behind each one.

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

Met Not met Not assessed Not applicable

No MET-specific ClinGen VCEP/CSPEC was available for this case (cspec.found=false, gene_vcep_dir=null), so generic ACMG/AMP was the only applicable framework for this criteria group.

Codon/residue/domain evidence in this case bundle is sparse: ClinVar has no entry for this exact variant, the dedicated PM5 comparator search found zero same-residue candidates and explicitly recommended not_applicable, no MET-specific functional domain or missense-constraint data was retrieved, and the only hotspot-significance check (cancerhotspots.org) is not registered as a citable source_registry key in this case.

As a result PS1, PM1, PP2, and BP1 are returned as not_assessed pending targeted domain/constraint/comparator-variant data, while PM5 is returned as not_applicable per the case's own explicit PM5-eligibility recommendation.

MET has no ClinGen VCEP/CSPEC on record for this case (cspec.found=false) and no local gene-specific functional framework was supplied (gene_vcep_dir=null, vcep_materials empty), so generic ACMG/AMP PS3/BS3 rules govern.

No functional assay evidence of any kind (validated or otherwise) for this specific variant was located in prefetch.json, evidence.json, literature_pass.json, or vcep_materials.json; literature_pass.json explicitly notes zero PMIDs found across evidence sources.

Both PS3 and BS3 are returned as not_assessed rather than not_met, since the gap is absence of functional data, not evidence of no-effect or evidence contradicting an effect.

MET has no ClinGen VCEP CSPEC and no local gene-specific PP3/BP4 lookup material in this case (framework_mode=generic_acmg); generic ACMG/AMP in-silico evidence rules apply.

This missense variant (p.Asp1028His) has a SpliceAI max delta score of 0.925 for donor loss at the annotated donor position, which is a high-confidence deleterious splicing prediction and drives PP3 (supporting) via the splice-impact path.

REVEL (0.374) and BayesDel (-0.0818303, uncalibrated in this pipeline) do not independently support PP3 or BP4 via the missense path; only the SpliceAI splice-path evidence is counted, avoiding double counting across sub-paths.

BP4 is not met because the strongest computational signal (SpliceAI) points toward a deleterious effect rather than a benign one.

Met · 2

PM2 SupportingMet (Supporting): allele absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0. Details ▾Hide ▴
Reasoning

The variant is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0. This supports PM2 because the allele is not observed in the available population datasets. The underlying records in the bundle provide absence statements but no allele-number, coverage, or ancestry-specific denominator details, so confirmation of database quality and applicability should receive human review.

Rule
generic_acmg_amp: PM2 supporting when the variant is absent or extremely rare in population databases, with disease prevalence and penetrance considered where available
Evidence considered
  • gnomAD v2.1 reports NM_001127500.2:c.3082G>C as absent.
  • gnomAD v4.1 reports NM_001127500.2:c.3082G>C as absent.
  • gnomAD-Canada v1.0 reports NM_001127500.2:c.3082G>C as absent.
  • The case bundle identifies no applicable MET-specific CSPEC/VCEP framework, so generic ACMG/AMP criteria are used.
Still missing
  • The bundled gnomAD records do not include allele-number, coverage, or ancestry-specific denominator details.
  • No MET-specific disease prevalence, penetrance, or maximum credible population-frequency threshold was provided.
Sources
PP3 SupportingMet (Supporting): SpliceAI predicts splice-donor loss at the donor position itself (max delta 0.925, above the 0.8 high-precision cutoff). Details ▾Hide ▴
Reasoning

No MET-specific VCEP/CSPEC PP3/BP4 lookup material is available for this case (framework_mode=generic_acmg, cspec.found=false, vcep_materials empty), so generic ACMG in-silico evidence applies. NM_001127500.2:c.3082G>C (p.Asp1028His) is a missense substitution, but SpliceAI predicts a high-confidence splice-donor-loss event: DS_DL=0.925 at DP_DL=0 (i.e. the predicted loss is at the annotated donor position itself), with a secondary DS_DG=0.477 donor-gain signal; max delta score = 0.925. Using the SpliceAI developer publication's own precision-recall bands (delta >=0.8 corresponds to the high-precision tier), a score of 0.925 is well above the high-precision cutoff and supports a deleterious splicing effect, satisfying PP3 at supporting strength under the generic ACMG framework (no calibrated evidence exists in this pipeline to justify an upgrade to moderate/strong for SpliceAI in the absence of a gene-specific VCEP splicing calibration). On the missense in-silico sub-path, REVEL=0.374 falls in the indeterminate zone (neither reaching a supporting-pathogenic nor supporting-benign REVEL threshold) and BayesDel (-0.0818303) has no verified published threshold available to this pipeline, so neither contributes to PP3 independently; the splice-path evidence alone is sufficient and is not double counted against the missense path.

Rule
generic_acmg_PP3_splicing_high_confidence_spliceai
Evidence considered
  • SpliceAI donor-loss delta score DS_DL=0.925 (DP_DL=0), donor-gain DS_DG=0.477, max delta score=0.925, from the SpliceAI Lookup tool run for NM_001127500.2:c.3082G>C.
  • SpliceAI's own precision-recall calibration (Jaganathan et al. 2019, PMID 30661751) reports that delta scores >=0.8 fall in a high-precision band strongly consistent with a splice-altering effect; this variant's max delta of 0.925 exceeds that band.
  • REVEL score 0.374 (local REVEL v1.3 lookup) is in an indeterminate range that does not meet a supporting-strength pathogenic or benign REVEL threshold, so it is not used to support PP3.
  • BayesDel score -0.0818303 (local BayesDel_170824_noAF lookup) has no verified published calibration threshold available to this pipeline (per project-level review, BayesDel thresholds are not currently confirmed against a named publication), so it is treated as not_available and not used to support or refute PP3.
Still missing
  • No RNA/minigene or transcript-level splicing assay evidence available to confirm the SpliceAI prediction experimentally.
  • No MET-specific VCEP splicing threshold table available to determine whether a stronger-than-supporting strength is warranted for this SpliceAI score.
Sources
spliceai ↗revelbayesdel

Not met · 5 · evaluated, threshold not reached

PP5 Not met: ClinVar has no record for this exact variant and no expert-panel pathogenic classification. Details ▾Hide ▴
Reasoning

PP5 is not met: the exact-variant ClinVar search returned no record for NM_001127500.2:c.3082G>C, and no expert-panel Pathogenic or Likely pathogenic classification is present.

Rule
Apply PP5 only for an exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic classification.
Evidence considered
  • ClinVar exact-variant search returned no result; variation ID, classification, review status, and citations are empty.
  • No qualifying exact-variant ClinVar expert-panel Pathogenic or Likely pathogenic assertion is available; ordinary submissions, aggregate labels, and non-expert assertions do not qualify.
Sources
BA1 Not met: allele is absent from gnomAD, so no population frequency approaches the BA1 threshold. Details ▾Hide ▴
Reasoning

BA1 requires an allele frequency high enough to establish a stand-alone benign observation. NM_001127500.2:c.3082G>C (MET p.Asp1028His) is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0; no population allele frequency or count approaches a BA1 threshold.

Rule
generic_acmg_amp: BA1 requires population frequency above the stand-alone benign threshold; absence cannot satisfy BA1
Evidence considered
  • gnomAD v2.1 reports the variant as absent.
  • gnomAD v4.1 reports the variant as absent.
  • gnomAD-Canada v1.0 reports the variant as absent.
Sources
BS1 Not met: absent from gnomAD v2.1, v4.1, and gnomAD-Canada v1.0, so no elevated allele frequency supports BS1. Details ▾Hide ▴
Reasoning

BS1 requires an allele frequency greater than expected for the disorder. The variant is absent from gnomAD v2.1, gnomAD v4.1, and gnomAD-Canada v1.0, so no elevated population frequency is present to support BS1.

Rule
generic_acmg_amp: BS1 requires an allele frequency greater than expected for the disorder; absence cannot satisfy BS1
Evidence considered
  • gnomAD v2.1 reports the variant as absent.
  • gnomAD v4.1 reports the variant as absent.
  • gnomAD-Canada v1.0 reports the variant as absent.
Sources
BP4 Not met: the dominant in-silico signal (SpliceAI donor loss, max delta 0.925) indicates damage, not a benign effect. Details ▾Hide ▴
Reasoning

No MET-specific VCEP/CSPEC PP3/BP4 lookup material is available for this case, so generic ACMG in-silico evidence applies. The dominant computational signal for this variant is the SpliceAI splice-donor-loss prediction (DS_DL=0.925, max delta 0.925), which is deleterious-direction evidence, not benign-direction, so BP4 cannot be met on the splice path. On the missense in-silico path, REVEL=0.374 sits in an indeterminate zone that does not reach a supporting-strength benign threshold, and BayesDel (-0.0818303) is not usable for PP3/BP4 in this pipeline because no verified published calibration threshold can be named for it. With no in-silico predictor reaching a benign-supporting threshold and the splice predictor actively pointing toward a damaging effect, BP4 is not met.

Rule
generic_acmg_BP4_not_met_deleterious_splice_signal
Evidence considered
  • SpliceAI donor-loss delta score DS_DL=0.925 (max delta 0.925) indicates a predicted deleterious splicing effect, which is inconsistent with applying BP4.
  • REVEL score 0.374 does not reach a supporting-strength benign REVEL threshold, so it does not support BP4.
  • BayesDel score -0.0818303 has no verified published calibration threshold available to this pipeline and is therefore treated as not_available for BP4, consistent with treatment of BayesDel for PP3.
Still missing
  • No calibrated benign-direction threshold reached by REVEL or SpliceAI for this variant.
  • BayesDel cannot be used for BP4 without a named, citable publication establishing its threshold.
Sources
spliceai ↗revelbayesdel
BP6 Not met: ClinVar has no record for this exact variant and no expert-panel benign classification exists. Details ▾Hide ▴
Reasoning

BP6 is not met: the exact-variant ClinVar search returned no record for NM_001127500.2:c.3082G>C, and no expert-panel Benign or Likely benign classification is present.

Rule
Apply BP6 only for an exact-variant ClinVar expert-panel Benign or Likely benign classification.
Evidence considered
  • ClinVar exact-variant search returned no result; variation ID, classification, review status, and citations are empty.
  • No qualifying exact-variant ClinVar expert-panel Benign or Likely benign assertion is available; ordinary submissions, aggregate labels, and non-expert assertions do not qualify.
Sources

Not assessed · 16 · no assessment recorded

PS1 Not assessed: no established pathogenic variant producing the identical p.Asp1028His change via a different nucleotide was found. Details ▾Hide ▴
Reasoning

PS1 requires an established pathogenic variant that produces the identical amino acid change (p.Asp1028His) via a different nucleotide substitution. The ClinVar lookup performed in this case searched only for the exact variant NM_001127500.2:c.3082G>C and returned no result (variant absent from ClinVar); no search was performed for alternate codon changes at residue 1028 that would also yield p.Asp1028His and be classified pathogenic/likely pathogenic. No such comparator was surfaced anywhere else in the case bundle.

Evidence considered
  • case_summary.json ClinVar lookup for this exact variant returned exact_match=false and evidence_sentence 'This variant is absent from ClinVar', but this search targeted only the exact c.3082G>C variant, not other codon-1028 substitutions producing the same amino acid change.
Still missing
  • No targeted ClinVar/literature search was performed for alternate nucleotide substitutions at MET codon 1028 producing the same p.Asp1028His change classified as pathogenic/likely pathogenic.
  • No MET-specific VCEP/CSPEC PS1 rule was available (cspec.found=false, gene_vcep_dir=null) to define codon-level PS1 application criteria.
Sources
PS2 Not assessed: no parental testing or genotype data were available to evaluate a possible de novo occurrence. Details ▾Hide ▴
Reasoning

No proband-level de novo assessment is possible from the case-evidence bundle. The bundle contains no documented parental testing, confirmed maternity/paternity, parental genotypes, or de novo observation for NM_001127500.2:c.3082G>C (MET p.Asp1028His).

Rule
Generic ACMG/AMP PS2 requires a confirmed de novo occurrence in the proband, with maternity/paternity confirmed and phenotype consistent with the relevant disorder; strength cannot be assigned without those data.
Evidence considered
  • The governing framework retrieved for this case is the generic ACMG/AMP fallback because no MET-specific VCEP/CSPEC framework was available.
  • The consolidated case-evidence bundle provides no parental-testing or confirmed de novo evidence for this variant.
Still missing
  • Proband phenotype and clinical indication
  • Testing results for both biological parents
  • Confirmation of maternity and paternity
  • Assessment of parental mosaicism and test sensitivity
  • Independent confirmation that the variant is absent in both parents
Sources
generic_acmg_combination_rules
PS3 Not assessed: no functional assay data (kinase, splicing, or cell-based) for this variant were available. Details ▾Hide ▴
Reasoning

No gene-specific VCEP/CSPEC framework is available for MET (cspec.found=false, framework_mode=generic_acmg), so generic ACMG PS3 applies. No functional assay data (kinase activity assays, splicing minigene assays, cell-based proliferation/transformation assays, or any other validated functional study) for NM_001127500.2:c.3082G>C (p.Asp1028His) was found anywhere in the case bundle: prefetch.json contains no functional assay source, literature_pass.json reports zero PMIDs found, and the PVS1-targeted germline literature search returned only gene-context papers unrelated to this specific variant's functional characterization. No source in this bundle provides validated in vitro/in vivo assay results, assay controls, or biological relevance data for this exact variant.

Still missing
  • No functional assay evidence (biochemical, cell-based, or splicing) identified for this variant in any source reviewed.
  • No CSPEC/VCEP functional assay specification available for MET to define approved assay types or strength calibration.
PS4 Not assessed: no germline case-control cohort or enrichment statistic was available for this variant. Details ▾Hide ▴
Reasoning

PS4 cannot be assessed because the case bundle contains no phenotype-defined germline case-control cohort, affected-case and control counts, or enrichment statistic for NM_001127500.2:c.3082G>C (MET p.Asp1028His). The COSMIC observation is somatic cancer occurrence and is not evidence of germline case-control enrichment.

Rule
PS4 requires statistically significant enrichment of the variant in affected individuals compared with appropriate controls; somatic database presence alone is insufficient.
Evidence considered
  • COSMIC reports COSV59259530 13 times in somatic cancers, but provides no germline case-control analysis.
  • The literature pass contains zero PMIDs and no relevant phenotype-prevalence publication.
Still missing
  • A phenotype-defined affected cohort and appropriate controls are needed.
  • Variant counts, cohort methodology, and an odds ratio or equivalent enrichment statistic are unavailable.
PM1 Not assessed: no germline mutational-hotspot or critical-domain annotation for residue 1028 was available. Details ▾Hide ▴
Reasoning

No MET-specific VCEP/CSPEC framework defining a mutational hotspot or critical functional domain boundary around residue 1028 was available in this case (cspec.found=false, gene_vcep_dir=null). The case bundle's cancerhotspots.org lookup (a somatic-cancer significance-testing resource, not a registered source_registry key in this case) reported that D1028 does not lie in a statistically significant hotspot, but this tool is not designed to assess ACMG PM1 germline functional-domain enrichment and is not present as a citable source_registry entry, so it cannot be used as a grounded evidence_ref here. No independent domain/structural annotation (e.g., UniProt kinase-domain boundaries, ClinGen-curated critical region) was retrieved in this case to establish or refute PM1.

Still missing
  • No MET-specific critical/functional domain definition (e.g., kinase domain boundaries, juxtamembrane region) with mutational density data was retrieved to evaluate PM1 at residue 1028.
  • The cancerhotspots.org check exists only in evidence.json/case_summary.json and lacks a corresponding source_registry key, so it cannot be cited as evidence_refs for this determination without violating the exact-key requirement.
PM3 Not assessed: no affected-proband, segregation, or trans-phase data were available. Details ▾Hide ▴
Reasoning

No applicable MET-specific VCEP or gene-specific framework was available, so the generic ACMG/AMP PM3 concept was considered. The case bundle contains no affected-proband observations, family segregation data, phase information, or confirmed pathogenic/likely pathogenic allele reported in trans with NM_001127500.2:c.3082G>C. PM3 cannot therefore be assigned.

Rule
Generic ACMG/AMP PM3: pathogenic or likely pathogenic variants observed in trans in affected individuals with a recessive disorder; strength depends on the number and quality of informative observations.
Evidence considered
  • The case bundle reports no literature PMIDs, no ClinVar record, and no VCEP materials for this variant.
  • The case bundle provides no affected-proband, pedigree, inheritance, compound-heterozygous, or phase observations relevant to PM3.
Still missing
  • Affected-proband or family-level observations for this variant are unavailable.
  • No confirmed pathogenic/likely pathogenic allele and no experimentally established phase in trans are documented.
PM6 Not assessed: no documented unconfirmed de novo occurrence was available. Details ▾Hide ▴
Reasoning

No unconfirmed de novo occurrence is documented in the case-evidence bundle. There is no proband/parent genotype information, phenotype description, or publication-based case report supporting NM_001127500.2:c.3082G>C as apparently de novo.

Rule
Generic ACMG/AMP PM6 may be considered for an apparently de novo occurrence when parental testing is unavailable, but requires documented proband and phenotype context; no strength is assigned here.
Evidence considered
  • The governing framework retrieved for this case is the generic ACMG/AMP fallback because no MET-specific VCEP/CSPEC framework was available.
  • The consolidated case-evidence bundle contains no case report, proband record, parental results, or apparently de novo observation for this variant.
Still missing
  • A documented proband carrying the variant
  • Parental testing or a documented reason that parental testing was unavailable
  • Phenotype consistency with a relevant MET-associated disorder
  • Evidence supporting maternity and paternity or the limitations of their confirmation
Sources
generic_acmg_combination_rules
PP1 Not assessed: no familial segregation data were available for this variant. Details ▾Hide ▴
Reasoning

No familial segregation data are available for NM_001127500.2:c.3082G>C. The case-evidence bundle does not identify affected relatives, unaffected relatives, informative meioses, or genotype/phenotype results from any family members.

Rule
Generic ACMG/AMP PP1 requires cosegregation of the variant with disease in affected family members; supporting strength depends on the number and informativeness of meioses and cannot be assigned without family data.
Evidence considered
  • The governing framework retrieved for this case is the generic ACMG/AMP fallback because no MET-specific VCEP/CSPEC framework was available.
  • The consolidated case-evidence bundle contains no segregation study, pedigree, family genotypes, or informative meioses for this variant.
Still missing
  • Family pedigree and phenotype information
  • Genotypes of affected relatives
  • Genotypes of unaffected relatives
  • Number of informative meioses
  • Assessment of phenotype specificity and phenocopies
Sources
generic_acmg_combination_rules
PP2 Not assessed: no MET missense-constraint metric or curated benign-missense-rate data were available. Details ▾Hide ▴
Reasoning

PP2 requires establishing that missense variation is a common mechanism of disease in MET with a low rate of benign missense variation. No MET-specific VCEP/CSPEC PP2 specification, missense constraint metric (e.g., gnomAD missense Z-score/O:E), or curated benign-missense-rate statement was present anywhere in the case bundle (cspec.found=false; no constraint data retrieved in prefetch/evidence/case_summary).

Still missing
  • No missense constraint metric (gnomAD Z-score, missense O:E) for MET was retrieved in this case.
  • No MET-specific VCEP/CSPEC statement on missense as a disease mechanism was available to ground a PP2 determination.
PP4 Not assessed: no patient phenotype or clinical diagnosis was provided. Details ▾Hide ▴
Reasoning

PP4 cannot be assessed because no patient phenotype, clinical diagnosis, family history, or disease-specific phenotype spectrum is provided. No MET-specific specification was retrieved, so the generic ACMG/AMP rule applies.

Rule
PP4 may be used when the patient's phenotype or family history is highly specific for a disease with a single-gene etiology; absent phenotype information is insufficient.
Evidence considered
  • The case bundle contains no phenotype description or phenotype-defined case evidence.
  • The bundle reports no applicable MET ClinGen CSPEC/VCEP framework; generic ACMG/AMP fallback was used.
Still missing
  • The patient's clinical phenotype and diagnostic indication are unavailable.
  • A highly specific phenotype-genotype correlation for the relevant disease context is not documented.
BS2 Not assessed: no observations of the variant in healthy adults or unaffected individuals were documented. Details ▾Hide ▴
Reasoning

No evidence in the case bundle documents the variant in healthy adults, unaffected individuals, or healthy homozygotes. Absence from population databases is relevant to PM2 but does not establish the BS2 observation required for this criterion.

Rule
generic_acmg_amp: BS2 requires observation in healthy adults or healthy homozygotes despite a disorder expected to manifest early and fully penetrantly
Still missing
  • No documented healthy-adult carriers or healthy homozygotes were identified.
  • No phenotype-confirmed control cohort or family segregation dataset was provided for BS2 assessment.
BS3 Not assessed: no functional assay evidence showing normal protein function was available. Details ▾Hide ▴
Reasoning

No gene-specific VCEP/CSPEC framework is available for MET (cspec.found=false, framework_mode=generic_acmg), so generic ACMG BS3 applies. No functional assay data showing normal/benign functional impact for NM_001127500.2:c.3082G>C (p.Asp1028His) was found anywhere in the case bundle. literature_pass.json reports zero PMIDs found, and no source_registry entry corresponds to a functional/assay study of this variant.

Still missing
  • No functional assay evidence (biochemical, cell-based, or splicing) identified for this variant in any source reviewed.
  • No CSPEC/VCEP functional assay specification available for MET to define approved assay types or strength calibration.
BS4 Not assessed: no affected individual lacking the variant (non-segregation) was documented. Details ▾Hide ▴
Reasoning

No non-segregation evidence is available. The case-evidence bundle does not document any clearly affected individual who lacks the variant, nor does it provide a pedigree or informative relatives suitable for evaluating BS4.

Rule
Generic ACMG/AMP BS4 requires a well-established affected individual or family member who lacks the variant, with appropriate consideration of phenotype specificity, penetrance, and phenocopies; no assessment is possible here.
Evidence considered
  • The governing framework retrieved for this case is the generic ACMG/AMP fallback because no MET-specific VCEP/CSPEC framework was available.
  • The consolidated case-evidence bundle contains no affected relative reported as negative for the variant and no other non-segregation evidence.
Still missing
  • Affected relatives with reliable clinical phenotyping
  • Variant testing results for affected relatives
  • Pedigree structure and age-dependent penetrance context
  • Evaluation for phenocopies and reduced penetrance
Sources
generic_acmg_combination_rules
BP1 Not assessed: no citable evidence that MET disease is primarily caused by truncating variants was available. Details ▾Hide ▴
Reasoning

BP1 requires establishing that MET is a gene where disease is primarily caused by truncating/loss-of-function variants such that missense variants are generally benign. No MET-specific VCEP/CSPEC BP1 specification or gene-level missense-vs-truncating mechanism statement grounded to a citable source was available in this case bundle to support or refute that characterization.

Still missing
  • No MET-specific VCEP/CSPEC statement characterizing the gene's primary disease mechanism (missense-driven vs. truncating-driven) was available to ground a BP1 determination.
  • The pvs1_gene_context literature search in this case surfaced mostly non-MET-gene papers (BRCA2, ANK1, CTNNA1) and only one MET-specific paper (PMID:26637977, an exon-skipping splicing mechanism, not a classic truncating-LOF missense-benign argument), so it does not establish a reliable gene-level mechanism basis for BP1.
BP2 Not assessed: no observations of this variant in trans or in cis with a pathogenic variant were available. Details ▾Hide ▴
Reasoning

No applicable MET-specific VCEP or gene-specific framework was available, so the generic ACMG/AMP BP2 concept was considered. The case bundle contains no observations establishing this variant in trans with a pathogenic/likely pathogenic variant for a dominant disorder or in cis with a pathogenic/likely pathogenic variant for a recessive disorder. BP2 cannot therefore be assigned.

Rule
Generic ACMG/AMP BP2: variant observed in trans with a pathogenic variant for a fully penetrant dominant disorder, or in cis with a pathogenic variant for a recessive disorder.
Evidence considered
  • The case bundle provides no family segregation, parental testing, affected-proband, or phase observations relevant to BP2.
  • The case bundle reports no literature PMIDs, no ClinVar record, and no VCEP materials that establish a qualifying cis or trans observation.
Still missing
  • Inheritance mode and disease-relevant parental or family phase data are unavailable.
  • No confirmed pathogenic/likely pathogenic variant and no cis/trans relationship are documented for this case.
BP5 Not assessed: no clinical phenotype or independent alternate molecular basis for disease was provided. Details ▾Hide ▴
Reasoning

BP5 cannot be assessed because no affected individual, clinical phenotype, or independent alternate molecular basis for the disease is provided. The somatic COSMIC record does not establish an alternate molecular etiology for a clinical case.

Rule
BP5 requires the variant to be found in an affected individual with an alternate molecular basis for the disease; somatic database occurrence alone is insufficient.
Evidence considered
  • COSMIC reports somatic cancer observations for the variant but does not provide a clinical case with an alternate molecular basis.
  • No case-level molecular diagnosis or alternate pathogenic variant was included in the case bundle.
Still missing
  • A documented affected individual and phenotype are needed.
  • An independent molecular explanation for the phenotype, distinct from this variant, is needed.
Not applicable · 5· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 N/ANot applicable: c.3082G>C is a missense substitution, not a null variant class covered by PVS1. Details ▾Hide ▴
Reasoning

PVS1 (ClinGen SVI PVS1 recommendations, PMC6185798, pvs1_generic_framework) applies only to null variant classes — nonsense, frameshift, canonical ±1/2 splice-consensus, translation-initiation-codon loss, and stop-loss variants — each expected to trigger nonsense-mediated decay or otherwise abolish normal protein function. NM_001127500.2:c.3082G>C in MET is a missense substitution predicted to produce NP_001120972.1:p.(Asp1028His). As a result, no null-variant mechanism (nonsense-mediated decay, truncation, or canonical splice disruption) is triggered by this variant class, so PVS1's structural prerequisite is not met by this variant class. This determination was made deterministically from the variant's consequence class, prior to LLM adjudication, because no structured VCEP criteria-combination framework governs this case (framework_complete=false); the generic ACMG/AMP 2015 fallback applies.

Rule
deterministic_prefilter: requires_null_variant_class
Evidence considered
  • Deterministic consequence classification: missense (prefetch.json normalized protein consequence)
Sources
pvs1_generic_framework ↗generic_acmg_combination_rules
PM4 N/ANot applicable: missense substitution causes no protein length change, which PM4 requires. Details ▾Hide ▴
Reasoning

PM4 (Richards et al. 2015, PMID:25741868) applies to protein length changes: in-frame insertions/deletions in a non-repetitive region, or stop-loss variants that extend the protein past the reference stop codon. NM_001127500.2:c.3082G>C in MET is a missense substitution predicted to produce NP_001120972.1:p.(Asp1028His). As a result, no change in protein length occurs, so there is nothing for this criterion to evaluate, so PM4's structural prerequisite is not met by this variant class. This determination was made deterministically from the variant's consequence class, prior to LLM adjudication, because no structured VCEP criteria-combination framework governs this case (framework_complete=false); the generic ACMG/AMP 2015 fallback applies.

Rule
deterministic_prefilter: requires_stop_loss_or_nonrepeat_indel
Evidence considered
  • Deterministic consequence classification: missense (prefetch.json normalized protein consequence)
Sources
pvs1_generic_framework ↗generic_acmg_combination_rules
PM5 N/ANot applicable: no pathogenic missense change at codon 1028 was identified for comparison. Details ▾Hide ▴
Reasoning

The case's dedicated PM5 comparator-collection step explicitly found zero total candidates (same_residue_candidates=0, expert_panel_plp_candidates=0, non_expert_majority_plp_candidates=0, conflicted_candidates=0) and flagged eligible_for_classic_pm5_search=false, with an explicit recommendation level of 'not_applicable' stating that classic same-residue PM5 semantics could not be safely confirmed and instructing not to apply PM5 from this artifact alone. No other source in the bundle supplies an alternate pathogenic missense change at codon 1028.

Evidence considered
  • pm5_candidates.json summary: eligible_for_classic_pm5_search=false, recommendation.level='not_applicable', candidate_summary shows 0 total candidates seen and 0 same-residue candidates, with hermes_instruction to not apply PM5 from this artifact alone.
Still missing
  • No same-residue comparator variants were identified or reviewed; if future comparator data becomes available (e.g., a pathogenic MET p.Asp1028X variant), PM5 should be re-evaluated.
Sources
pm5_candidates
BP3 N/ANot applicable: missense substitution does not alter protein length in a repetitive region, which BP3 requires. Details ▾Hide ▴
Reasoning

BP3 (Richards et al. 2015, PMID:25741868) applies to in-frame insertions/deletions located in a repetitive region without a known function. NM_001127500.2:c.3082G>C in MET is a missense substitution predicted to produce NP_001120972.1:p.(Asp1028His). As a result, the variant does not alter protein length within a repeat region, so there is nothing for this criterion to evaluate, so BP3's structural prerequisite is not met by this variant class. This determination was made deterministically from the variant's consequence class, prior to LLM adjudication, because no structured VCEP criteria-combination framework governs this case (framework_complete=false); the generic ACMG/AMP 2015 fallback applies.

Rule
deterministic_prefilter: requires_repeat_region_indel
Evidence considered
  • Deterministic consequence classification: missense (prefetch.json normalized protein consequence)
Sources
pvs1_generic_framework ↗generic_acmg_combination_rules
BP7 N/ANot applicable: BP7 applies only to synonymous variants; this is a missense substitution. Details ▾Hide ▴
Reasoning

BP7 (Richards et al. 2015, PMID:25741868) is defined for a synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence and the nucleotide is not highly conserved. NM_001127500.2:c.3082G>C in MET is a missense substitution predicted to produce NP_001120972.1:p.(Asp1028His). As a result, the encoded protein sequence is altered, so the criterion's silent-variant premise does not hold regardless of any splicing prediction, so BP7's structural prerequisite is not met by this variant class. This determination was made deterministically from the variant's consequence class, prior to LLM adjudication, because no structured VCEP criteria-combination framework governs this case (framework_complete=false); the generic ACMG/AMP 2015 fallback applies.

Rule
deterministic_prefilter: requires_synonymous
Evidence considered
  • Deterministic consequence classification: missense (prefetch.json normalized protein consequence)
Sources
generic_acmg_combination_rules

Identifiers

Gene
MET
Transcript
NM_001127500.2
Coding (HGVS c.)
NM_001127500.2:c.3082G>C
Protein (HGVS p.)
NP_001120972.1:p.(Asp1028His)
GRCh38
chr7:116771989 G>C
GRCh37
chr7:116412043 G>C
Location and type
Exon 14 · missense
COSMIC
COSV59259530

Gene diagram

Every interpreted variant in MET, mapped onto the exon structure of NM_001127500.2. Select a row to find it on the plot.

METNM_001127500.2
Fetching transcript structure from UCSC…
gnomAD v4.1 Allele count data not recorded
gnomAD v2.1 Allele count data not recorded
gnomAD-Canada v1.0 Allele 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 -140 bp
0.364
SpliceAI acceptor gainat +104 bp
0.000
SpliceAI donor lossat +0 bp
0.925
SpliceAI donor gainat -79 bp
0.477
Pangolin splice lossmagnitude shown
-0.805
Pangolin splice gain
0.408

Other predictors

REVEL
0.374
BayesDel
-0.082

How the predictions were used

PP3 SupportingMet (Supporting): SpliceAI predicts splice-donor loss at the donor position itself (max delta 0.925, above the 0.8 high-precision cutoff). Details ▾Hide ▴
Reasoning

No MET-specific VCEP/CSPEC PP3/BP4 lookup material is available for this case (framework_mode=generic_acmg, cspec.found=false, vcep_materials empty), so generic ACMG in-silico evidence applies. NM_001127500.2:c.3082G>C (p.Asp1028His) is a missense substitution, but SpliceAI predicts a high-confidence splice-donor-loss event: DS_DL=0.925 at DP_DL=0 (i.e. the predicted loss is at the annotated donor position itself), with a secondary DS_DG=0.477 donor-gain signal; max delta score = 0.925. Using the SpliceAI developer publication's own precision-recall bands (delta >=0.8 corresponds to the high-precision tier), a score of 0.925 is well above the high-precision cutoff and supports a deleterious splicing effect, satisfying PP3 at supporting strength under the generic ACMG framework (no calibrated evidence exists in this pipeline to justify an upgrade to moderate/strong for SpliceAI in the absence of a gene-specific VCEP splicing calibration). On the missense in-silico sub-path, REVEL=0.374 falls in the indeterminate zone (neither reaching a supporting-pathogenic nor supporting-benign REVEL threshold) and BayesDel (-0.0818303) has no verified published threshold available to this pipeline, so neither contributes to PP3 independently; the splice-path evidence alone is sufficient and is not double counted against the missense path.

Rule
generic_acmg_PP3_splicing_high_confidence_spliceai
Evidence considered
  • SpliceAI donor-loss delta score DS_DL=0.925 (DP_DL=0), donor-gain DS_DG=0.477, max delta score=0.925, from the SpliceAI Lookup tool run for NM_001127500.2:c.3082G>C.
  • SpliceAI's own precision-recall calibration (Jaganathan et al. 2019, PMID 30661751) reports that delta scores >=0.8 fall in a high-precision band strongly consistent with a splice-altering effect; this variant's max delta of 0.925 exceeds that band.
  • REVEL score 0.374 (local REVEL v1.3 lookup) is in an indeterminate range that does not meet a supporting-strength pathogenic or benign REVEL threshold, so it is not used to support PP3.
  • BayesDel score -0.0818303 (local BayesDel_170824_noAF lookup) has no verified published calibration threshold available to this pipeline (per project-level review, BayesDel thresholds are not currently confirmed against a named publication), so it is treated as not_available and not used to support or refute PP3.
Still missing
  • No RNA/minigene or transcript-level splicing assay evidence available to confirm the SpliceAI prediction experimentally.
  • No MET-specific VCEP splicing threshold table available to determine whether a stronger-than-supporting strength is warranted for this SpliceAI score.
Sources
spliceai ↗revelbayesdel
BP4 Not met: the dominant in-silico signal (SpliceAI donor loss, max delta 0.925) indicates damage, not a benign effect. Details ▾Hide ▴
Reasoning

No MET-specific VCEP/CSPEC PP3/BP4 lookup material is available for this case, so generic ACMG in-silico evidence applies. The dominant computational signal for this variant is the SpliceAI splice-donor-loss prediction (DS_DL=0.925, max delta 0.925), which is deleterious-direction evidence, not benign-direction, so BP4 cannot be met on the splice path. On the missense in-silico path, REVEL=0.374 sits in an indeterminate zone that does not reach a supporting-strength benign threshold, and BayesDel (-0.0818303) is not usable for PP3/BP4 in this pipeline because no verified published calibration threshold can be named for it. With no in-silico predictor reaching a benign-supporting threshold and the splice predictor actively pointing toward a damaging effect, BP4 is not met.

Rule
generic_acmg_BP4_not_met_deleterious_splice_signal
Evidence considered
  • SpliceAI donor-loss delta score DS_DL=0.925 (max delta 0.925) indicates a predicted deleterious splicing effect, which is inconsistent with applying BP4.
  • REVEL score 0.374 does not reach a supporting-strength benign REVEL threshold, so it does not support BP4.
  • BayesDel score -0.0818303 has no verified published calibration threshold available to this pipeline and is therefore treated as not_available for BP4, consistent with treatment of BayesDel for PP3.
Still missing
  • No calibrated benign-direction threshold reached by REVEL or SpliceAI for this variant.
  • BayesDel cannot be used for BP4 without a named, citable publication establishing its threshold.
Sources
spliceai ↗revelbayesdel
BP7 N/ANot applicable: BP7 applies only to synonymous variants; this is a missense substitution. Details ▾Hide ▴
Reasoning

BP7 (Richards et al. 2015, PMID:25741868) is defined for a synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence and the nucleotide is not highly conserved. NM_001127500.2:c.3082G>C in MET is a missense substitution predicted to produce NP_001120972.1:p.(Asp1028His). As a result, the encoded protein sequence is altered, so the criterion's silent-variant premise does not hold regardless of any splicing prediction, so BP7's structural prerequisite is not met by this variant class. This determination was made deterministically from the variant's consequence class, prior to LLM adjudication, because no structured VCEP criteria-combination framework governs this case (framework_complete=false); the generic ACMG/AMP 2015 fallback applies.

Rule
deterministic_prefilter: requires_synonymous
Evidence considered
  • Deterministic consequence classification: missense (prefetch.json normalized protein consequence)
Sources
generic_acmg_combination_rules

Statement

In silico

SpliceAI predicts possible splice impact for this variant (max delta score = 0.93). REVEL score = 0.374. BayesDel score = -0.0818303.

0 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata.

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

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 possible splice impact for this variant (max delta score = 0.93). REVEL score = 0.374. BayesDel score = -0.0818303.

Functional

OncoKB identified curated literature and non-variant-specific oncogenicity context for review; listed oncogenicity label: not classified.

Somatic

This variant does not lie in a statistically significant hotspot. This variant has previously been reported in somatic cancers (COSMIC; COSV59259530, n = 13 times).

Cancer Hotspots

This variant does not lie in a statistically significant hotspot.