0%
Print report
Variant interpretation report

BRAF c.1799T>A, p.(Val600Glu)

NM_004333.6:c.1799T>A NP_004324.2:p.(Val600Glu) Missense · exon 15 View identifiers
Classification
Likely pathogenic

Variant description:

No variant summary was recorded for this case.

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

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

In plain language

Gene-level background from the recorded interpretation.

About BRAF

BRAF encodes a protein kinase that helps control the MAPK/ERK signaling pathway, which regulates cell growth, division, and specialization. Changes in BRAF are associated with cardiofaciocutaneous, Noonan, and Costello syndromes. BRAF is an oncogene, and abnormal activation of its signaling can drive cancers including melanoma, thyroid cancer, colorectal cancer, lung cancer, lymphoma, and hairy cell leukemia.

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 BRAF 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.

Pathogenic evidence criteria: 4 Benign evidence criteria: 0
Pathogenic criteria applied · 4
PS3Moderate
PS3 · moderate

Met at moderate strength: two or more VCEP-approved functional assays show V600E increases MEK/ERK pathway signaling.

PM1Moderate
PM1 · moderate

Met at moderate strength: residue 600 lies within the VCEP-approved CR3 activation segment (amino acids 594-627).

PM2Supporting
PM2 · supporting

Met at supporting strength: the variant is effectively absent from gnomAD, with 2 of 1,612,922 v4.1 exome alleles (AF 1.24e-06). Strictly read, 1-2 observed alleles do not satisfy 'absent', and supporting is the only tier this ruleset allows.

PP3Supporting
PP3 · supporting

Met at supporting strength: REVEL 0.931 exceeds the VCEP missense threshold of 0.7.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Likely pathogenic

Likely Pathogenic from 2 moderate criteria (PS3, PM1) plus 2 supporting criteria (PM2, PP3) under BRAF v2.3 Rule14.

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
2 / 1,612,922 alleles

gnomAD v4.1: 2 / 1,612,922 alleles. Recorded AF 1.23999e-06. Recorded homozygote count 0.

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.97994e-06; MAF= 0.00040%, 1/251260 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26669e-05; MAF= 0.00327%, 1/30612 alleles, homozygotes = 0).

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

No screenshot for this evidence
REVEL score
0.931 recorded score

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

No screenshot for this evidence
ClinVar submissions
11 reported laboratory submissions

7 Pathogenic · 2 Likely pathogenic · 2 Uncertain significance.

Context only ClinVar ↗
Functional evidence
Statement recorded

OncoKB identified variant-specific curated literature and context relevant to functional review; biological-effect context: Gain-of-function; curated oncogenicity label: Oncogenic.

COSMIC
Cancer Hotspots
Somatic evidence
31792 recorded samples

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

Cancer Hotspots

This variant lies in a statistically significant hotspot.

For specialists

Technical detail

ACMG/AMP criteria under ClinGen BRAF VCEP v2.3, with the data and sources behind each one.

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

Met Not met Not assessed Not applicable

Framework: the governing specification is the ClinGen RASopathy Expert Panel specification for BRAF v2.3 (cspec doc 643243119, framework_mode=vcep, precedence rank 1); all five criteria in this group were adjudicated against that VCEP text, with generic ACMG/AMP used only where the VCEP is silent.

Variant/codon context: NM_004333.6:c.1799T>A = NP_004324.2:p.(Val600Glu), missense, exon 15, codon 600 (GTG>GAG); the variant is essentially absent from gnomAD, so residue 600 carries no benign population variation.

PM1 met at Moderate: residue 600 lies within the VCEP-approved CR3 activation segment (AA 594-627), one of the four critical well-established functional domains the VCEP permits for PM1 (exon 6, exon 11, P-loop AA 459-474, CR3 AA 594-627); the VCEP rule is domain-based and forbids residue-specific reasoning under PM1, and the VCEP domain_tables object is empty so the rule text itself supplied the domain list.

PS1 not applicable to this variant: the only retrieved p.(Val600Glu) record is the identical c.1799T>A change, so no distinct alternate-nucleotide same-amino-acid comparator exists in evidence, and the BRAF/RAF1 analogous-residue branch could not be checked because the VCEP RAF alignment is image-only.

PM5 not assessed: the dedicated same-codon comparator search returned zero usable candidates and no other bundle source documents individually citable pathogenic codon-600 substitutions, so PM5 would require an ungrounded comparator claim.

PP2 not assessed: the VCEP rule requires a BRAF gnomAD missense z score >3.09 and no gene-level constraint value exists anywhere in this case's evidence.

BP1 not applicable: the VCEP confines BP1 to truncating variants under the gain-of-function RASopathy mechanism, and this is a missense substitution.

Framework used: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119; RASopathy, autosomal dominant; rule_payload gives a criteria-combination scoring model). All four criteria assigned to this group (PS2, PM6, PP1, BS4) are flagged Applicable in that specification, so generic ACMG/AMP definitions were used only to read the underlying criterion intent, with the VCEP strength/point thresholds applied where applicable.

VCEP strengths relevant here: PS2 and PM6 use the SVI de novo point system (PS2: 1/2/4 points = Moderate/Strong/Very Strong; PM6: 0.5/1/2 points = Supporting/Moderate/Strong) with full points only for RASopathy phenotypes and reduced points when phenotypic information is minimal; PP1 uses >=3/>=5/>=7 informative meioses = Supporting/Moderate/Strong with segregation in more than one family recommended; BS4 is Benign Strong and requires only one informative meiosis.

This case is a variant-level review of BRAF NM_004333.6:c.1799T>A (p.Val600Glu) with no proband, no phenotype, no family history, no parental testing and no segregation data. Consequently none of PS2, PM6, PP1 or BS4 can be assessed: there is no de novo or assumed de novo occurrence to score and no informative meiosis in either direction.

No pathogenic or benign weight is contributed by this group. Any final classification must therefore rest on the other criterion groups; PS2/PM6/PP1 were not affirmed, and BS4 was neither met nor excluded.

Framework-specific context worth recording: this residue change is the predominant recurrent somatic BRAF mutation in cancer (PMID:12068308), so de novo status can only be credited from germline (non-tumour) testing with confirmed maternity and paternity.

Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119), applied because the case was run in vcep mode for BRAF; generic ACMG/AMP rules were not used to score any criterion in this group.

No criterion in this group is met. PS4 and BP5 could not be scored because the framework requires case-level, phenotype-specified point scoring and the bundle contains no case-level clinical, phenotype, or point data (both not_assessed). PP4 is not applicable under the VCEP, which routes phenotype specificity into PS4. PP5 and BP6 were assessed against the exact-variant ClinVar expert-panel gate and are not met: the record has 0 expert-panel submissions and single-submitter review status, so its aggregate laboratory labels cannot trigger either criterion.

The exact-variant evidence that does exist is dominated by somatic tumour observations (COSMIC somatic count 31,792; melanoma, papillary thyroid carcinoma, colorectal carcinoma, low-grade astrocytoma, germ cell tumour, vascular malformation) and by functional GOF assays; neither supplies germline case-control enrichment or phenotype specificity for a RASopathy proband, and genomic/functional criteria are adjudicated by other groups.

Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF Version 2.3 (CSPEC doc 643243119) is present and applicable, so the generic lab fallback thresholds for PP3/BP4 (generic REVEL 0.750/0.250 cutoffs, generic SpliceAI 0.2/0.1 cutoffs) were not used.

Variant consequence type is missense: NM_004333.6:c.1799T>A -> NP_004324.2:p.(Val600Glu) (BRAF V600E, exon 15 kinase domain). Exactly one computational path - the missense protein-impact path - was therefore evaluated, per the VCEP rule 'For missense variants: REVEL >= 0.7'.

PP3 met (supporting): local REVEL v1.3 score 0.931 >= 0.7 BRAF VCEP cutoff.

BP4 not met: the BRAF VCEP BP4 missense rule requires REVEL <= 0.3; observed REVEL is 0.931.

BP7 not applicable: the variant is a missense, not a synonymous/intronic (non-canonical)/non-coding variant, which is BP7's precondition.

No double counting: the REVEL score was used only once (PP3); SpliceAI (max delta 0.007, no predicted splice impact) was recorded as checked but was not used as support for the missense variant's PP3/BP4, and absence of predicted splice impact is not evidence about the substituted amino acid.

BayesDel (0.335473) was not used for PP3/BP4 because no verified published BayesDel threshold is available to this pipeline.

No BRAF VCEP PP3/BP4 lookup spreadsheet pre-assigning a code for this variant was found; the VCEP materials present (RAF-Alignment.xlsx for analogous-residue analyses; SVI-RASopathy-VCEP-V2-Approved-Functional-Studies.xlsx for functional assays) contain no in-silico per-variant assignments.

All four population criteria were adjudicated against the governing ClinGen RASopathy Expert Panel BRAF specification v2.3 (cspec), which supplies the applicable thresholds: BA1 = gnomAD filtering allele frequency >=0.05% (stand alone); BS1 = gnomAD filtering allele frequency >=0.025% (strong); PM2 = absent from controls (gnomAD), Supporting tier only; BS2 = point-based (-4 Strong / -1 Supporting) using healthy homozygous or healthy heterozygous individuals, including apparently unaffected heterozygous parent/sibling samples. Generic ACMG/AMP frequency thresholds were not needed because a gene-specific specification exists.

Population frequency is essentially null: 1/251,260 exome alleles in gnomAD v2.1 (AF 3.98e-06, homozygotes = 0) and 2/1,612,922 exome alleles in gnomAD v4.1 (AF 1.24e-06, homozygotes = 0), with the single South Asian observation being the only non-zero ancestry group and no homozygote anywhere.

Benign frequency criteria therefore fail by a wide margin: the highest observed subpopulation AF (3.267e-05 in v2.1; 1.098e-05 in v4.1) is still ~8-23 fold below the BS1 0.025% threshold and ~15-45 fold below the BA1 0.05% threshold, so no benign stand-alone or benign strong population evidence is available for this variant.

BS2 fails because its required observations are absent rather than merely weakly documented: zero homozygotes in both datasets, no phenotyped healthy heterozygous adult, and no genotype/phenotype data for unaffected parents or siblings in the bundle; RASopathy is an autosomal dominant condition with age-dependent, incomplete penetrance, so unscreened heterozygous presence in a population database cannot demonstrate a healthy adult in whom full penetrance at an early age would be expected.

PM2 is met at the CSPEC-permitted Supporting strength: the variant is present at a rate (1-2 alleles in >1.6 million) that is ~3-4 orders of magnitude below the cohort-level thresholds of the same specification, with no homozygotes and no ancestry-specific enrichment. The only interpretive tension is the literal CSPEC wording 'must be absent' versus 1-2 observed alleles; this is flagged in the PM2 gaps_remaining and in the group warnings, and the frequency evidence is recorded as quantitative rather than absolute.

Threshold/artefact considerations were explicitly checked: (a) gnomAD grpmax filtering allele frequency — the statistic named by the BA1/BS1 rules — was not returned by the lookup (null for v2.1 and v4.1), so popmax subpopulation AF was used as a conservative upper bound and the benign criteria still fail; (b) the gnomAD genome component contributed no alleles in either dataset (genome_an = 0), so all frequencies are exome-only; (c) gnomAD-Canada v1.0 (HostSeq) timed out, leaving the Canadian cohort unchecked; (d) because this variant is a dominant somatic hotspot (COSMIC COSV56056643, 31,792 somatic occurrences), low-level population observations may include somatic/mosaic or technical signal, which affects how 'absent' is interpreted for PM2 but cannot manufacture benign frequency evidence for BA1/BS1.

Group net effect on classification: PM2 Supporting (met) is the only population criterion satisfied; BA1, BS1 and BS2 are not met. Population data neither support a benign classification nor contradict a pathogenic one, and no benign stand-alone criterion was triggered.

Met · 4

PS3 ModerateMet at moderate strength: two or more VCEP-approved functional assays show V600E increases MEK/ERK pathway signaling. Details ▾Hide ▴
Reasoning

The BRAF VCEP Version 2.3 framework specifies PS3 Supporting for one approved assay and PS3 Moderate for two or more different approved assays. Variant-specific studies of BRAF V600E provide two biologically relevant, pathway-based functional readouts: elevated MEK phosphorylation/RAF-MEK pathway activity and increased ERK-dependent transcriptional output in V600E BRAF tumor cells, plus cell-based MEK/ERK signaling response to RAF inhibition. These correspond to distinct approved pathway functional assay types in the VCEP functional-studies resource and support the gain-of-function mechanism for BRAF V600E. No evidence supports escalation to Strong under the VCEP rule.

Rule
BRAF VCEP Version 2.3 PS3: Moderate = two or more different approved assays; Supporting = one approved assay.
Evidence considered
  • The BRAF VCEP Version 2.3 rule states: PS3 Moderate requires two or more different approved assays; PS3 Supporting requires one approved assay.
  • The VCEP approved functional-studies resource lists MEK Activation Assay and ERK Activation Assay as pathway-specific approved assay types, and BRAF Kinase Activity as a gene-specific approved assay type.
  • PMID:19251651 directly studies V600E BRAF tumor cells and reports elevated RAF/MEK signaling and V600E-specific MEK-dependent transcriptional output. The study used seven V600E BRAF cell lines, MEK inhibition, pMEK/pERK immunoblotting, gene-expression profiling, quantitative RT-PCR/immunoblot confirmation, and xenograft experiments; it found elevated pMEK and increased ERK pathway output in V600E BRAF cells.
  • PMID:20179705 directly studies BRAFV600E in cell-based signaling experiments and reports that RAF inhibition inhibited MEK/ERK signaling in BRAFV600E tumors/cells, with comparison to MEK inhibition and assessment of pathway behavior in the presence or absence of mutant RAS.
Still missing
  • The extracted case bundle does not provide complete assay-level quantitative control details for every experiment, such as all replicate counts and full positive/negative control specifications.
Sources
cspec ↗vcep_svi_rasopathy_vcep_v2_approved_functional_studiesPMID:19251651 ↗PMID:20179705 ↗
PM1 ModerateMet at moderate strength: residue 600 lies within the VCEP-approved CR3 activation segment (amino acids 594-627). Details ▾Hide ▴
Reasoning

The BRAF VCEP v2.3 restricts PM1 to critical, well-established functional domains named in its supplementary domain table: exon 6, exon 11, the P-loop (AA 459-474) and the CR3 activation segment (AA 594-627), and explicitly excludes residue-specific reasoning from PM1 (that is PM5's scope). p.(Val600Glu) alters residue 600, which falls inside the CR3 activation segment (AA 594-627) and is encoded by exon 15; membership in any single approved domain satisfies the rule. vcep_materials.json 'domain_tables' is empty for BRAF, so the authoritative approved-domain list was taken directly from the governing VCEP rule text rather than re-derived, and the VCEP RAF-Alignment workbook could not be parsed further (alignment sheet is image-only). PM1 is therefore met at Moderate strength on domain membership alone; the case hotspot artifact (statistically significant V600 hotspot, screenshot-level) and the domain-localising literature are corroborative only.

Rule
Moderate: Applicable only to critical and well-established functional domains available in the supplementary table (exon 6, exon 11, P-loop [AA 459-474], CR3 activation segment [AA 594-627]). Not applicable to specific amino acid residues (see PM5).
Evidence considered
  • cspec (BRAF VCEP v2.3) PM1 rule: 'Applicable only to critical and well-established functional domains available in the supplementary table (exon 6, exon 11, P-loop [AA 459-474], CR3 activation segment [AA 594-627]). Not applicable to specific amino acid residues (see PM5).' Residue 600 lies within 594-627 (CR3 activation segment).
  • vcep_materials.json domain_tables is {} for BRAF, so no VCEP domain-table entry existed to consult; the PM1 domain list in the VCEP rule text was used instead.
  • vcep_raf_alignment (RAF-Alignment.xlsx) was inspected for the RAF-family domain alignment but its alignment sheet is image-only (no extractable text), so it neither corroborates nor contradicts the residue-600 domain assignment.
  • PMID:22855150 states the exact variant p.V600E 'is located in the kinase domain of the protein (exon 15)', consistent with the CR3 activation segment being within the BRAF kinase domain.
  • PMID:22142829 reports the exact activating BRAFV600E change recurrently in tumours (neuroblastoma, embryonal rhabdomyosarcoma, Ewing sarcoma), consistent with a functionally critical, recurrently substituted activation-segment residue.
  • Case hotspot artifact (cancerhotspots.org screenshot) records 'This variant lies in a statistically significant hotspot' with summary 'V600 hotspot row partially parsed' and warning 'Regex extraction partial; verify screenshot'; treated as corroborating context only, since the row data could not be verified.
Sources
PM2 SupportingMet at supporting strength: the variant is effectively absent from gnomAD, with 2 of 1,612,922 v4.1 exome alleles (AF 1.24e-06). Strictly read, 1-2 observed alleles do not satisfy 'absent', and supporting is the only tier this ruleset allows. Details ▾Hide ▴
Reasoning

BRAF RASopathy CSPEC v2.3 PM2 is 'The variant must be absent from controls (gnomAD)'; although the CSPEC default strength is listed as Pathogenic Moderate, only the Supporting tier is applicable in this ruleset, so PM2 can only be applied at Supporting. The variant is effectively absent: gnomAD v4.1 exomes contain 2/1,612,922 alleles (AF 1.24e-06; 0 homozygotes; popmax South Asian 1/91,076, AF 1.098e-05) and gnomAD v2.1 exomes contain 1/251,260 alleles (AF 3.98e-06; 0 homozygotes; popmax South Asian 1/30,612, AF 3.267e-05). Strictly read, 'absent' is not satisfied because 1-2 alleles were observed, so this call rests on the standard interpretation of the rule as 'absent or at extremely low frequency': the observation rate is ~3-4 orders of magnitude below the cohort-level thresholds used by this same specification (BS1 0.025%), is at the boundary of what allele-count-based databases can distinguish from a low-level somatic, mosaic, or technical signal for a variant that is a dominant somatic hotspot, and no homozygote or recurrent population haplotype is present. PM2 is therefore awarded at Supporting only, and its point value is small relative to the rest of the case. Human review is flag-free only because the frequency question itself is unambiguous; the interpretive caveat is recorded in gaps_remaining and warnings.

Rule
The variant must be absent from controls (gnomAD) — CSPEC BRAF v2.3, applicable strength tier: Supporting only.
Evidence considered
  • Governing rule (cspec): BRAF RASopathy CSPEC v2.3 PM2 instructionsToUse = 'The variant must be absent from controls (gnomAD)'; defaultStrength is Pathogenic Moderate but the strength_rules list marks only the Supporting tier as Applicable, so PM2 may only be applied at Supporting.
  • gnomad_v4 (gnomAD v4.1 exomes, GRCh38): total 2/1,612,922 alleles, AF 1.23999e-06 (0.000124%), homozygotes = 0; highest subpopulation South Asian 1/91,076 (AF 1.09798e-05); all other ancestry groups 0 alleles.
  • gnomad_v2 (gnomAD v2.1 exomes, GRCh37): total 1/251,260 alleles, AF 3.97994e-06 (0.000398%), homozygotes = 0; highest subpopulation South Asian 1/30,612 (AF 3.26669e-05); all other subpopulations 0 alleles.
  • Observed frequency is ~63-202 fold lower than the BS1 threshold (0.025%) used by this same CSPEC document and ~126-403 fold lower than the BA1 threshold (0.05%), i.e. at or below the level at which a 1-2 allele count in an exome database cannot be distinguished from a low-level artefact or mosaic signal rather than a genuine germline allele; the variant is a dominant somatic hotspot, so this caveat applies specifically here.
  • Somatic-database context in this case bundle (COSMIC, COSV56056643) records 31,792 somatic occurrences of this variant, and PMID:22855150 states that V600E is the most common BRAF mutation in colorectal carcinoma (~90% of BRAF mutations) in the kinase domain (exon 15); this establishes the variant as a recurrent tumour-acquired hotspot, which is why its near-absence (rather than literal absence) in germline population databases is treated as PM2-supporting rather than as a benign population signal.
  • PMID:12068308 reports the same kinase-domain hotspot substitution using the pre-renumbering notation V599E (nucleotide T1796A), found in 35 of 38 melanoma BRAF mutations (92%) with elevated kinase activity and NIH3T3 transformation; it is used only for the somatic-hotspot framing of PM2 and is not variant-exact evidence (see warnings).
  • gnomad_canada: 'Not available in gnomAD-Canada v1.0.' with '<urlopen error timed out>' — the HostSeq cohort could not be queried, so absence was not additionally confirmed there.
Still missing
  • Literal-rule caveat: the BRAF CSPEC v2.3 PM2 text reads 'must be absent from controls (gnomAD)' and the variant is not literally absent (1-2 heterozygous alleles, no homozygotes); if the governing framework is read strictly as zero observations required, PM2 would fail. Confirm the VCEP's intended reading of 'absent' for a recurrent somatic hotspot before final sign-out.
  • gnomAD-COSMIC context: the somatic recurrence of this variant in tumours (see warnings) means the low-level population observations cannot be cleanly classified as germline; tumour-normal or read-level confirmation of the gnomAD observations is not available in this bundle.
  • gnomAD-Canada v1.0 (HostSeq) returned no result (request timed out), so absence could not be confirmed in that cohort.
  • gnomAD genome components returned genome_an = 0 in both datasets (exome-only frequencies), and grpmax filtering allele frequency was null, so the population evidence base is thinner than a full gnomAD v4 exome+genome review.
Sources
PP3 SupportingMet at supporting strength: REVEL 0.931 exceeds the VCEP missense threshold of 0.7. Details ▾Hide ▴
Reasoning

NM_004333.6:c.1799T>A is a missense substitution, NP_004324.2:p.(Val600Glu) (BRAF V600E), so it is adjudicated on the missense protein-impact path. The governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) states for PP3: 'For missense variants: REVEL >= 0.7', at Pathogenic Supporting strength. The local REVEL v1.3 lookup returns REVEL = 0.931 for this variant, which exceeds the 0.7 VCEP cutoff, so PP3 is met at supporting strength. BayesDel (0.335473) was not used because no verified published calibration for these criteria is available to this pipeline. The SpliceAI result was deliberately NOT used as support: a spliced-path score cannot clear a missense variant's protein-level effect, and no predicted splice impact is not evidence about the substituted amino acid.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC PP3: for missense variants, REVEL >= 0.7 -> PP3 supporting
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF Version 2.3 (CSPEC doc 643243119) PP3 rule, Supporting strength, applicability 'Applicable': 'For missense variants: REVEL >= 0.7. For splicing impact, predicted outcome must match disease mechanism.'
  • Local REVEL v1.3 predictor lookup (revel-v1.3_chrom_07_130418334_149129625.csv.zip) for chr7:140753336 A>T (GRCh38) / chr7:140453136 A>T (GRCh37) returned REVEL = 0.931, i.e. above the BRAF VCEP 0.7 missense cutoff.
  • Variant normalized as NM_004333.6:c.1799T>A / NP_004324.2:p.(Val600Glu) (1-letter p.(V600E)), a missense change, so the missense (not splice) computational path applies.
  • BayesDel_170824_noAF returned 0.335473 for this variant; excluded from PP3 because no verified published BayesDel threshold is available to this pipeline.
  • SpliceAI lookup for NM_004333.6:c.1799T>A returned DS_AG 0.001, DS_AL 0.007, DS_DG 0.007, DS_DL 0.000 (max delta 0.007) with the variant consequence recorded as 'sequence_variant'; this result was not used for PP3 because a missense variant is judged on its protein-impact (REVEL) score, and absence of predicted splice impact says nothing about the p.Val600Glu substitution.
  • ACMG/AMP 2015 standards (PMID 25741868) define PP3 as multiple lines of computational evidence supporting a deleterious effect, with the caveat that PP3 may be used only once per variant.
Still missing
  • No VCEP PP3/BP4 lookup spreadsheet pre-assigning a code for this variant exists in the BRAF VCEP materials (only RAF-Alignment.xlsx for analogous-residue work and the functional-study spreadsheet), so PP3 rests on the CSPEC REVEL threshold plus the local REVEL score alone.
  • BayesDel is available (0.335473) but remains uncalibrated for PP3/BP4 in this pipeline and was not counted.
Sources

Not met · 7 · evaluated, threshold not reached

PM4 Not met: p.(Val600Glu) is a missense substitution with no protein-length change, whereas PM4 requires an in-frame indel or stop-loss change. Details ▾Hide ▴
Reasoning

The variant is a missense substitution, p.(Val600Glu), with no protein-length change. It is neither an in-frame insertion/deletion nor a stop-loss variant, so PM4 is not met. The governing BRAF specification states that there are no known repetitive areas in the gene and otherwise uses PM4 as described.

Rule
ClinGen RASopathy Expert Panel BRAF v2.3: PM4 moderate; no known repetitive areas in BRAF; use as described.
Evidence considered
  • NM_004333.6:c.1799T>A produces the single-residue substitution p.(Val600Glu), with the predicted and reference protein sequences retaining the same length through the terminal stop codon.
  • The governing BRAF RASopathy Expert Panel specification retains PM4 at moderate strength, states that BRAF has no known repetitive areas, and directs use as described; the required protein-length-altering variant consequence is absent.
Sources
PP5 Not met: the ClinVar record has 0 expert-panel (three-star) submissions, which PP5 requires to trigger. Details ▾Hide ▴
Reasoning

PP5 is only triggered by an exact-variant ClinVar expert-panel (three-star) classification of Pathogenic or Likely pathogenic. For this variant the ClinVar record has 0 expert-panel submissions, the overall review status is 'criteria provided, single submitter', and every audited submission carries is_expert_panel = false; the assertions are ordinary laboratory/research submissions and the aggregate label, which must never trigger PP5. The exact-variant record is in fact Pathogenic overall, but that is an aggregate/non-expert label and is not usable evidence for PP5. Independently, the governing BRAF RASopathy VCEP v2.3 also marks PP5 as not for use ('not for use as recommended by the ClinGen SVI VCEP Review Committee'). PP5 is therefore not met.

Rule
PP5 requires an exact-variant ClinVar expert-panel Pathogenic/Likely pathogenic assertion (three-star); ordinary laboratory submissions, aggregate labels and non-expert assertions never trigger it. ClinGen RASopathy Expert Panel BRAF v2.3 additionally designates PP5 as Not Applicable for this VCEP.
Evidence considered
  • Rules applied: PP5 requires a disease-specific, exact-variant ClinVar expert-panel classification (Pathogenic/Likely pathogenic) and is awarded at supporting strength; ordinary laboratory submissions, aggregate ClinVar labels, and non-expert assertions do not qualify.
  • ClinVar variation 13961 (NM_004333.6(BRAF):c.1799T>A, p.Val600Glu) has review status 'criteria provided, single submitter' and 0 expert-panel submissions; source_data.expert_panels is empty, and the submission audit records is_expert_panel = false for every accession inspected (including SCV000035247-SCV000035250, SCV000043966, SCV000061601, SCV001450230, SCV000112810, SCV005812663).
  • ClinVar's overall label for the record is 'Pathogenic' with 7 laboratories Pathogenic, 2 Likely pathogenic and 2 Uncertain significance, but this is an aggregate non-expert assertion and was deliberately not used to support PP5.
  • ClinGen RASopathy Expert Panel BRAF v2.3 states for PP5: 'This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.'
Still missing
  • No exact-variant ClinVar expert-panel classification exists for this variant; if one is published in future, PP5 would be re-evaluated against the exact-variant three-star assertion only.
Sources
BA1 Not met: even the highest subpopulation frequency (3.27e-05, South Asian) falls about 15-fold below the 0.05% BA1 threshold. Details ▾Hide ▴
Reasoning

Governing framework is the ClinGen RASopathy Expert Panel BRAF specification v2.3 (cspec), which sets BA1 as stand-alone benign at a gnomAD filtering allele frequency >=0.05%. The variant is orders of magnitude below that: gnomAD v4.1 exomes show 2/1,612,922 alleles (AF 1.24e-06; 0 homozygotes) and gnomAD v2.1 exomes show 1/251,260 alleles (AF 3.98e-06; 0 homozygotes). Even taking the highest single-subpopulation frequency observed anywhere (South Asian, 3.267e-05 in v2.1; 1.098e-05 in v4.1) as a deliberately conservative upper bound for the CSPEC-specified filtering allele frequency, BA1 still fails by roughly 15-45 fold. No benign stand-alone population evidence exists, and no ancestry-specific or threshold artifact is large enough to change this. The generic ACMG/AMP fallback (>1-5% population frequency) is met even less.

Rule
GnomAD filtering allele frequency >=0.05% (Benign Stand Alone; only applicable tier in BRAF CSPEC v2.3).
Evidence considered
  • Governing rule (cspec): BRAF RASopathy CSPEC v2.3, BA1 = 'GnomAD filtering allele frequency >=0.05%', default strength Benign Stand Alone, and the Stand Alone tier is the only applicable strength tier.
  • gnomad_v4 (gnomAD v4.1 exomes, GRCh38 chr7-140753336-A-T): total AC/AN = 2/1,612,922, total AF = 1.23999e-06 (0.000124%), homozygotes = 0; exome component 2/1,461,618 (AF 1.369e-06); highest subpopulation = South Asian, 1/91,076 (AF 1.09798e-05 = 0.001098%), homozygotes = 0. This is ~403-fold (total AF) and ~45-fold (popmax AF) below the 0.05% BA1 threshold.
  • gnomad_v2 (gnomAD v2.1 exomes, GRCh37 7-140453136-A-T): total AC/AN = 1/251,260, total AF = 3.97994e-06 (0.000398%), homozygotes = 0; highest subpopulation = South Asian, 1/30,612 (AF 3.26669e-05 = 0.003267%), homozygotes = 0. This is ~126-fold (total AF) and ~15-fold (popmax AF) below the 0.05% BA1 threshold.
  • All 33 reported gnomAD v2.1 subpopulations and all reported v4.1 subpopulations with non-zero alleles are the single South Asian observation; no other ancestry group reaches or approaches the threshold, so there is no ancestry-specific frequency artifact that would rescue BA1.
  • The gnomAD lookup returned grpmax_faf, exome_grpmax_faf and genome_grpmax_faf as null, so the exact filtering-allele-frequency statistic named by the CSPEC rule was unavailable; because popmax AF bounds FAF from above and already fails by more than an order of magnitude, BA1 is unmet under either metric.
  • gnomad_canada: query to the gnomAD-Canada v1.0 (HostSeq genomes) service returned 'Not available in gnomAD-Canada v1.0.' with error '<urlopen error timed out>' — no Canadian frequency data are available for this variant, so this source neither supports nor refutes BA1.
Still missing
  • The CSPEC-specified metric (gnomAD grpmax filtering allele frequency) was not returned by the gnomAD lookup (grpmax_faf = null for both v2.1 and v4.1); popmax subpopulation AF was used as a conservative upper bound for FAF, and the conclusion is unchanged because that upper bound already sits ~15-45x below the 0.05% threshold.
  • The gnomAD genome component returned zero alleles observed (genome_an = 0) for both v2.1 and v4.1, so the reported frequencies are exome-only and genome-level frequency (including gnomAD v4 genomes) is unverified.
  • gnomAD-Canada v1.0 (HostSeq) lookup timed out ('<urlopen error timed out>'), so the Canadian population frequency could not be checked; this is a source-coverage gap, not evidence of absence.
Sources
BS1 Not met: even the highest subpopulation frequency (3.27e-05, South Asian) falls clearly below the 0.025% BS1 threshold. Details ▾Hide ▴
Reasoning

BRAF RASopathy CSPEC v2.3 sets BS1 as benign strong at a gnomAD filtering allele frequency >=0.025%. Observed frequencies are far below that: gnomAD v4.1 exome total AF 1.24e-06 (2/1,612,922; 0 homozygotes) and gnomAD v2.1 exome total AF 3.98e-06 (1/251,260; 0 homozygotes). The highest any-subpopulation frequency (South Asian, 3.267e-05 in v2.1; 1.098e-05 in v4.1) — used as a deliberately conservative stand-in for the CSPEC-specified filtering allele frequency, which the lookup did not return — is still ~8-23 fold below the 0.025% threshold. The variant is therefore far rarer than expected for the RASopathy disease spectrum at the CSPEC-specified AF, and the standard ACMG/AMP reading of BS1 (allele frequency greater than expected for the disorder) is likewise unmet. No frequency-based benign strong evidence is available.

Rule
GnomAD filtering allele frequency >=0.025% (Benign Strong; only applicable tier in BRAF CSPEC v2.3).
Evidence considered
  • Governing rule (cspec): BRAF RASopathy CSPEC v2.3, BS1 = 'GnomAD filtering allele frequency >=0.025%' at Benign Strong, and Strong is the only applicable tier.
  • gnomad_v4 (gnomAD v4.1 exomes): total AF 1.23999e-06 (2/1,612,922 alleles), homozygotes = 0; popmax South Asian AF 1.09798e-05 (1/91,076), homozygotes = 0 — i.e. ~202-fold below the 0.025% threshold on total AF and ~23-fold below it on popmax AF.
  • gnomad_v2 (gnomAD v2.1 exomes): total AF 3.97994e-06 (1/251,260 alleles), homozygotes = 0; popmax South Asian AF 3.26669e-05 (1/30,612), homozygotes = 0 — i.e. ~63-fold below the 0.025% threshold on total AF and ~8-fold below it on popmax AF.
  • No ancestry group other than the single South Asian observation carries this allele in either dataset, so there is no ancestry-specific frequency artifact that would push the variant over the 0.025% threshold.
  • gnomad_canada: 'Not available in gnomAD-Canada v1.0.' (query timed out against the HostSeq service), so no additional population frequency data could be obtained.
Still missing
  • gnomAD grpmax filtering allele frequency (the CSPEC-named statistic for BS1) was not retrieved (grpmax_faf = null for v2.1 and v4.1); popmax subpopulation AF was substituted as a conservative upper bound and the conclusion is unchanged.
  • gnomAD genome component returned genome_an = 0 in both datasets, so frequencies are exome-only; genome-level frequency remains unverified.
  • gnomAD-Canada v1.0 (HostSeq) did not return a result (request timed out), so the Canadian population frequency of this variant is unknown.
Sources
BS2 Not met: no homozygotes were observed and the 1-2 heterozygous carriers carry no phenotype information, so no BS2 points are awarded. Details ▾Hide ▴
Reasoning

BRAF RASopathy CSPEC v2.3 makes BS2 a point-based rule (-4 points = Strong; -1 point = Supporting) with explicit phenotypic specifications: points are based on healthy homozygous or healthy heterozygous individuals, with reduced points for apparently unaffected heterozygous individuals and applicability to parent or sibling samples during clinical family evaluations. None of the required observations exists for this variant. There are zero homozygotes in both population datasets examined (0/251,260 in gnomAD v2.1; 0/1,612,922 in gnomAD v4.1), so the Strong tier cannot be scored. The only observations are 1-2 heterozygous alleles in unscreened population samples, which carry no phenotype information; RASopathy (MONDO:0021060) is an autosomal dominant disorder with age-dependent, incomplete penetrance and variable expressivity, so mere presence of a heterozygous allele in a population database cannot establish an apparently healthy adult in whom full penetrance would be expected at an early age, nor an apparently unaffected heterozygous parent or sibling. The case bundle contains no genotype data for unaffected relatives of the proband. No BS2 points are therefore awarded.

Rule
Point-based BS2: >= -4 Points (Benign Strong) or >= -1 Point (Benign Supporting); phenotypic specifications require healthy homozygous/heterozygous individuals, with reduced points for apparently unaffected heterozygous individuals in parent or sibling samples (BRAF CSPEC v2.3).
Evidence considered
  • Governing rule (cspec): BRAF RASopathy CSPEC v2.3 BS2, Point-based scoring '>= -4 Points' (Strong) or '>= -1 Point' (Supporting), with phenotypic specifications based on healthy homozygote or heterozygote individuals, reduced points for apparently unaffected heterozygous individuals, applicable to parent or sibling samples during clinical family evaluations.
  • gnomad_v2: homozygote count = 0 among 251,260 exome alleles screened (and 0 in every one of the 33 reported subpopulations), so no healthy homozygous individual was observed.
  • gnomad_v4: homozygote count = 0 among 1,612,922 exome alleles screened (exome 0/1,461,618; popmax South Asian 0/91,076), so no healthy homozygous individual was observed in the larger, more recent dataset either.
  • The only individuals carrying this allele in gnomAD are 1 (v2.1) and 2 (v4.1) heterozygous exome samples with no phenotype, age, or clinical annotation; because RASopathy is an autosomal dominant condition with age-dependent and incomplete penetrance and variable expressivity, heterozygous presence in an unscreened population sample is not sufficient evidence of an unaffected adult in whom full penetrance at an early age would be expected.
  • The case bundle contains no genotype or phenotype information for unaffected parents or siblings of the proband, so the CSPEC BS2 phenotypic-specification pathway (reduced points for apparently unaffected heterozygous relatives) cannot be scored.
  • gnomad_canada: 'Not available in gnomAD-Canada v1.0.' (HostSeq query timed out) — no additional adult cohort could be checked for homozygous or healthy heterozygous carriers.
Still missing
  • No healthy homozygous individual and no phenotyped healthy heterozygous adult carrier is available from any consulted source; the BS2 Strong (-4 points) requirement cannot be tested, and the Supporting (-1 point) requirement cannot be met from gnomAD, which lacks phenotype and age information.
  • No apparently unaffected heterozygous parent/sibling sample (the CSPEC phenotypic specification for BS2 points) is present in this case bundle for this variant; family-member carrier status and phenotype would need to be supplied by the segregation/de novo evidence group or the clinical record.
  • gnomAD-Canada v1.0 (HostSeq) returned no result (request timed out), so an additional adult population cohort could not be screened for homozygous or healthy heterozygous carriers.
Sources
BP4 Not met: REVEL 0.931 is far above the 0.3 missense threshold BP4 requires for benign support. Details ▾Hide ▴
Reasoning

NM_004333.6:c.1799T>A (p.Val600Glu) is a missense variant, so BP4 is assessed on the missense path. The governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) BP4 rule is 'For missense variants: REVEL <= 0.3'. The local REVEL v1.3 score is 0.931, which is far above 0.3, so the BP4 benign-supporting threshold is not met. The splice sub-rule of BP4 ('predicted outcome is negligible or does not match disease mechanism') cannot be used to meet BP4 for this missense variant, and in any case the CSPEC requires its in-silico criteria to be counted only once per variant; the same REVEL score that supports PP3 cannot also support BP4. BP4 is therefore not met.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC BP4: for missense variants, REVEL <= 0.3 -> BP4 supporting (not satisfied)
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications for BRAF Version 2.3 (CSPEC doc 643243119) BP4 rule, Supporting strength, applicability 'Applicable': 'For missense variants: REVEL <= 0.3. For splicing variants: predicted outcome is negligible or does not match disease mechanism.'
  • Local REVEL v1.3 predictor lookup returned REVEL = 0.931 for this variant, which does not satisfy the <= 0.3 BP4 cutoff.
  • Variant consequence is a missense substitution p.(Val600Glu); the BP4 splicing sub-rule applies to splicing variants and cannot be substituted for the missense assessment.
  • BayesDel_170824_noAF returned 0.335473; excluded because no verified published BayesDel calibration is available to this pipeline.
  • ACMG/AMP 2015 standards (PMID 25741868) define BP4 as multiple lines of computational evidence suggesting no impact, with the caveat that BP4 may be used only once per variant.
Still missing
  • None affecting the BP4 call: the VCEP missense threshold requires REVEL <= 0.3 and the observed REVEL is 0.931.
Sources
BP6 Not met: the ClinVar record has 0 expert-panel (three-star) submissions, and none of its assertions are benign. Details ▾Hide ▴
Reasoning

BP6 is only triggered by an exact-variant ClinVar expert-panel (three-star) classification of Benign or Likely benign. The ClinVar record for this variant has 0 expert-panel submissions and review status 'criteria provided, single submitter'; no expert-panel benign assertion exists, and the record's non-expert submissions are Pathogenic/Likely pathogenic/Uncertain significance only. Ordinary laboratory submissions, aggregate labels, and non-expert assertions must never trigger BP6, so the criterion is not met. Independently, the governing BRAF RASopathy VCEP v2.3 marks BP6 as not for use.

Rule
BP6 requires an exact-variant ClinVar expert-panel Benign/Likely benign assertion (three-star); ordinary laboratory submissions, aggregate labels and non-expert assertions never trigger it. ClinGen RASopathy Expert Panel BRAF v2.3 additionally designates BP6 as Not Applicable for this VCEP.
Evidence considered
  • Rules applied: BP6 requires a disease-specific, exact-variant ClinVar expert-panel classification (Benign/Likely benign) and is awarded at supporting strength; ordinary laboratory submissions, aggregate ClinVar labels and non-expert assertions never trigger it.
  • ClinVar variation 13961 records 0 expert-panel submissions and review status 'criteria provided, single submitter'; the submission audit shows is_expert_panel = false for all inspected accessions and there is no benign or likely benign submission for the exact variant.
  • ClinGen RASopathy Expert Panel BRAF v2.3 states for BP6: 'This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.'
Still missing
  • No exact-variant ClinVar expert-panel benign classification exists; BP6 would only be re-evaluated if such an expert-panel Benign/Likely benign assertion appeared.
Sources

Not assessed · 9 · no assessment recorded

PS2 Not assessed: no proband, family history, or parental testing was available to establish the confirmed de novo occurrence PS2 requires. Details ▾Hide ▴
Reasoning

The applicable framework is the ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119, RASopathy, autosomal dominant), in which PS2 is Applicable and scored with the SVI de novo point system (1 point = Moderate, 2 points = Strong, 4 points = Very Strong; full points with RASopathy phenotypes, reduced points when phenotypic information is minimal). PS2 requires a de novo occurrence with both maternity and paternity confirmed in a patient with the disease and no family history. This case bundle is variant-level only: it contains no proband phenotype, no family history, no parental testing, and no reported de novo occurrence for NM_004333.6:c.1799T>A. No de novo observation can therefore be counted and no points can be assigned; the criterion is not assessable rather than affirmatively excluded. Additional caveat for future assessment: this residue change (p.Val600Glu, reported as V599E in PMID:12068308) is a recurrent somatic BRAF mutation in cancer, so any apparently de novo result must be documented in germline (non-tumour) tissue with confirmed maternity and paternity before PS2 can be credited.

Rule
ClinGen RASopathy VCEP BRAF v2.3, PS2 (Applicable) - de novo with both maternity and paternity confirmed in a patient with the disease and no family history; point-based strength via ClinGen SVI Proposal for De Novo Criteria v1.1: 1 point = Moderate, 2 points = Strong, 4 points = Very Strong. No de novo point is assignable without proband/parental data.
Evidence considered
  • Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119; inheritance autosomal dominant, RASopathy). PS2 is listed as Applicable with point-based strength rules: '4 Points' (Very Strong), '2 Points' (Strong), '1 Point' (Moderate).
  • Framework instructionsToUse for PS2 quote: 'Follow SVI recommendations for point-based scoring in conjunction with PM6 (see Reference 1) and phenotypic specifications: full points awarded with RASopathy phenotypes, reduced points applicable to cases with minimal phenotypic information (i.e. prenatal cases, cases with a clinical order of a RASopathy panel without clinical information, and cases with limited clinical information in other global tests (such as WES)).'
  • Framework original ACMG definition retained for PS2 quote: 'De novo (both maternity and paternity confirmed) in a patient with the disease and no family history. Note: Confirmation of paternity only is insufficient. Egg donation, surrogate motherhood, errors in embryo transfer, etc. can contribute to non-maternity.'
  • The framework's Reference 1 is the ClinGen SVI Proposal for De Novo Criteria v1.1 (https://clinicalgenome.org/site/assets/files/3461/svi_proposal_for_de_novo_criteria_v1_1.pdf), the source of the point-based PS2/PM6 scheme reproduced in the BRAF ruleset.
  • No proband-level data exist in this case bundle: the case_summary contains only variant-level evidence (normalization, ClinVar records, gnomAD, SpliceAI, REVEL, BayesDel, OncoKB, COSMIC, hotspots) and no patient phenotype, family history or parental testing result, so no de novo occurrence can be counted.
  • All six ClinVar criterion-lead submissions consulted (SCV000035247, SCV000035248, SCV000035249, SCV000043966, SCV000035250, SCV000061601; submitters OMIM x5 and Laboratory for Molecular Medicine, Mass General Brigham) carry review status 'no assertion criteria provided' and no expert-panel submissions are present (expert_panel_submissions = 0), so no submitter-documented de novo evidence exists.
  • Keyword screen of all seven fetched full texts ('de novo' counts: PMID:12068308 = 0, PMID:15035987 = 0, PMID:19251651 = 0, PMID:20179705 = 0, PMID:22142829 = 0, PMID:25741868 discusses the criterion generically, PMID:22855150's single 'de novo' hit concerns Lynch syndrome MMR germline testing, not BRAF) found no germline de novo occurrence of this variant.
  • Caveat grounded in PMID:12068308 (which describes the identical residue change as V599E): the variant is the most common recurrent somatic BRAF mutation in cancer ('a single substitution (V599E) accounting for 80%'), so tumour-derived detection cannot substitute for a germline de novo finding with confirmed maternity and paternity.
Still missing
  • No proband is described in the case bundle: no patient phenotype, no indication of RASopathy clinical features, and no family history.
  • No parental testing result (maternity and paternity confirmation) for NM_004333.6:c.1799T>A is available; PS2 explicitly cannot be met if paternity alone is confirmed.
  • No de novo occurrence of this variant in a patient is reported by any source consulted (ClinVar criterion-lead submissions carry 'no assertion criteria provided'; none of the seven fetched full texts reports a germline de novo event).
  • Phenotype-specific point allocation cannot be applied because there is no phenotypic information (framework awards reduced points for prenatal/panel-order/WES cases with limited clinical information).
Sources
PS4 Not assessed: no germline RASopathy case counts or phenotype data were available, which PS4 requires to assign points. Details ▾Hide ▴
Reasoning

The governing framework is the ClinGen RASopathy Expert Panel specification for BRAF v2.3, which does not use the generic PS4 prevalence rule for this gene. It requires point-based scoring of autosomal-dominant cases with phenotypic specifications: at least 1 point for supporting, 3 points for moderate, and 5 points for strong PS4, with full points awarded for RASopathy phenotypes and reduced points for cases with minimal phenotypic information. No qualifying case-level data exist in this bundle: there is no proband phenotype, no RASopathy case count, no point assignment, and no case-control or cohort enrichment analysis for the germline RASopathy phenotype. The exact-variant full texts and ClinVar submissions that do exist are predominantly somatic-origin tumour observations (melanoma, papillary thyroid carcinoma, colorectal carcinoma, low-grade astrocytoma, nonseminomatous germ cell tumour, vascular malformation), and the ACMG/AMP framework explicitly states it is not intended for interpretation of somatic variation, so somatic tumour mutation frequency cannot substitute for germline case-control enrichment under this VCEP. ClinVar's own record for this variant is a single-submitter laboratory record (7 laboratories Pathogenic, 2 Likely pathogenic, 2 Uncertain significance; 0 expert-panel submissions), and criterion leads must not be inferred from another source's final classification. PS4 therefore cannot be scored and is left not_assessed with the specific gaps recorded.

Rule
ClinGen RASopathy Expert Panel BRAF v2.3 PS4: strength adjustment using point-based scoring for autosomal dominant cases with phenotypic specifications; Supporting >=1 point, Moderate >=3 points, Strong >=5 points; full points with RASopathy phenotypes, reduced points for minimal phenotypic information.
Evidence considered
  • ClinGen RASopathy Expert Panel BRAF v2.3 (cspec doc 643243119) PS4 is applicable with strength adjustment by point-based scoring for autosomal dominant cases: '>=5 points' = Strong, '>=3 points' = Moderate, '>=1 points' = Supporting, with full points only for RASopathy phenotypes and reduced points for cases with minimal phenotypic information.
  • The evidence bundle contains no case-level clinical data for the case under review (no phenotype, HPO terms, indication, or family history), so no VCEP PS4 points can be assigned.
  • PMID:12068308 reports that BRAF mutations are concentrated in the kinase domain and that a single substitution (reported in that paper as V599E, the numbering corresponding to V600E) accounted for 80-92% of BRAF mutations in the screened cancers; this is somatic tumour mutation screening (545 cancer cell lines and 378 primary cancers/short-term cultures), not germline prevalence in RASopathy probands versus controls.
  • PMID:22855150 states the most common BRAF mutation in colorectal carcinoma is the V600E substitution, located in the kinase domain encoded by exon 15, accounting for approximately 90% of BRAF mutations; this is a somatic tumour biomarker prevalence statement, not a germline case-control enrichment measure.
  • PMID:22142829 reports BRAF V600E by Sequenom hotspot screening in somatic paediatric solid tumours (1/192 neuroblastoma, 1/60 embryonal rhabdomyosarcoma, 1/75 Ewing sarcoma); these are tumour observations with no RASopathy phenotype information and no control comparison.
  • PMID:25741868 states that the ACMG/AMP sequence variant interpretation approach 'is intended for interpretation of variants observed in patients with suspected inherited (primarily Mendelian) disorders' and 'is not intended for the interpretation of somatic variation', which is why the somatic tumour frequency data above cannot be used for PS4 in this germline framework.
  • ClinVar variation 13961 is recorded as Pathogenic with review status 'criteria provided, single submitter' and 0 expert-panel submissions; the germline submissions present (e.g. SCV001450230, SCV000112810, SCV005812663) carry the condition label 'not provided' with no case counts or phenotype detail, and the somatic-origin submissions carry tumour condition labels.
  • No case-control odds ratio, relative risk, or proband-versus-control comparison for this exact variant was found in the bundle.
Still missing
  • Case-level germline proband data with RASopathy phenotypic detail sufficient to assign VCEP PS4 points (or an explicit VCEP point total).
  • A case-control or cohort enrichment analysis of this exact variant in probands with a RASopathy phenotype versus population controls.
  • Full texts of the PS4 candidate PMIDs from the literature triage (12447372, 12619120, 12960123, 25950823, 26389333, 32605662) were not retrieved for this case, so their case-level content could not be examined.
Sources
PM5 Not assessed: no other established pathogenic amino-acid change at codon 600 was identified to serve as the required comparison. Details ▾Hide ▴
Reasoning

The BRAF VCEP v2.3 defines PM5 as a count of DIFFERENT already-established [likely] pathogenic amino-acid changes at the SAME codon as the variant under review (1 such change = Moderate; at least 2 different such changes observed in at least 5 probands = Strong). The case's dedicated same-residue comparator collection (pm5_candidates.json) reviewed 8 candidate records, identified 0 same-residue candidates, and returned the recommendation 'no_useful_candidates_found' with an explicit instruction not to apply PM5 from that artifact alone. No other source in the bundle enumerates verified, individually citable pathogenic codon-600 substitutions: the hotspot artifact records V600 as a statistically significant hotspot but its row data was not parsed ('V600 hotspot row partially parsed'; warning 'Regex extraction partial; verify screenshot'), and no ClinVar comparator record for another codon-600 substitution was retrieved. PM5 therefore cannot be adjudicated without an ungrounded comparator claim, and is returned not_assessed with human review flagged.

Rule
Moderate: 1 [likely] pathogenic residue change at the same codon. Strong: >=2 different [likely] pathogenic residue changes at the same codon observed in >=5 probands.
Evidence considered
  • cspec (BRAF VCEP v2.3) PM5 rules: Moderate = '1 [likely] pathogenic residue change at the same codon'; Strong = '>=2 different [likely] pathogenic residue changes at the same codon observed in >=5 probands'; cspec v2.3 release note states 'Observed in >=5 probands' was removed from PM5 at Moderate strength.
  • pm5_candidates.json: pm5_mode 'classic_same_residue_missense', total_candidates_seen 8, same_residue_candidates 0, expert_panel_plp_candidates 0, recommendation.level 'no_useful_candidates_found' with hermes_instruction to review collected same-residue comparators and not to apply PM5 from that artifact alone.
  • Case hotspot artifact (cancerhotspots.org screenshot, BRAF V600) could not be resolved to substitution-level comparator data because row extraction was partial.
Still missing
  • No validated same-codon comparator: pm5_candidates.json found 0 same-residue candidates among 8 reviewed records; a manual curated search for other established pathogenic BRAF codon-600 substitutions (individually citable per substitution) is required before PM5 can be adjudicated.
  • The Cancer Hotspots result for V600 is screenshot-only with incomplete regex extraction, so it cannot yet serve as documented evidence of multiple established pathogenic substitutions at codon 600.
Sources
cspec ↗pm5_candidates
PM6 Not assessed: no proband or parental genotyping was available, so neither an observed nor an assumed de novo occurrence could be scored. Details ▾Hide ▴
Reasoning

The applicable framework is the ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119), in which PM6 is Applicable and scored with the SVI de novo point system (0.5 points = Supporting, 1 point = Moderate, 2 points = Strong), used in conjunction with PS2 and with phenotype-dependent point allocation. PM6 requires an assumed de novo occurrence without confirmation of maternity and paternity. The case bundle contains no proband and no parental genotyping of any kind, so there is neither an observed nor an assumed de novo occurrence to score. Screening of the ClinVar submissions and of all seven fetched full texts found no report of this variant arising de novo in a patient. PM6 is therefore not assessable, not affirmatively excluded.

Rule
ClinGen RASopathy VCEP BRAF v2.3, PM6 (Applicable) - assumed de novo without confirmation of paternity and maternity; point-based strength via ClinGen SVI Proposal for De Novo Criteria v1.1: 0.5 points = Supporting, 1 point = Moderate, 2 points = Strong. No assumed de novo occurrence is available to score.
Evidence considered
  • Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119). PM6 is listed as Applicable with point-based strength rules: '2 Points' (Strong), '1 Point' (Moderate), '0.5 Points' (Supporting).
  • Framework instructionsToUse for PM6 quote: 'Follow SVI recommendations for point-based scoring in conjunction with PS2 (see Reference 1) and phenotypic specifications: full points awarded with RASopathy phenotypes, reduced points applicable to cases with minimal phenotypic information (i.e. prenatal cases, cases with a clinical order of a RASopathy panel without clinical information, and cases with limited clinical information in other global tests (such as WES)).'
  • Framework original ACMG definition retained for PM6 quote: 'Assumed de novo, but without confirmation of paternity and maternity.'
  • The framework's Reference 1 (source of the PM6 point thresholds) is the ClinGen SVI Proposal for De Novo Criteria v1.1 (https://clinicalgenome.org/site/assets/files/3461/svi_proposal_for_de_novo_criteria_v1_1.pdf).
  • No parental genotypes, trio information or assumed-de-novo assertion exists anywhere in the case bundle; the only ClinVar submissions usable as criterion leads (SCV000035247, SCV000035248, SCV000035249, SCV000043966, SCV000035250, SCV000061601) have 'no assertion criteria provided' review status.
  • Full-text screen for this criterion found no de novo or assumed de novo report for the variant: PMID:12068308 (somatic cancer cohorts), PMID:15035987 and PMID:19251651 and PMID:20179705 (functional/signalling studies), PMID:22142829 (somatic paediatric tumour screen) and PMID:22855150 (colorectal biomarker consensus) contain no proband-level inheritance data for BRAF c.1799T>A.
  • Caveat grounded in PMID:12068308: the same residue change (reported there as V599E) is the dominant recurrent somatic BRAF mutation in cancer, so tumour-tissue detection must not be mistaken for a de novo germline event.
Still missing
  • No proband is described in the case bundle and no parental genotype information is available, so PM6's premise (an assumed de novo occurrence) is absent.
  • No published or submitted report of a de novo or assumed de novo occurrence of NM_004333.6:c.1799T>A in a patient with a RASopathy was identified among the sources consulted.
  • Phenotype-dependent point allocation (full vs reduced points) cannot be applied without any clinical information about the tested individual.
Sources
PP1 Not assessed: no family pedigree or informative meioses were available to test co-segregation of the variant with disease. Details ▾Hide ▴
Reasoning

The applicable framework is the ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119), in which PP1 is Applicable with meiosis-count thresholds (>=3 informative meioses = Supporting, >=5 = Moderate, >=7 = Strong) and the recommendation that segregation be shown in more than one family. PP1 requires co-segregation of the variant with disease in affected family members. This case bundle contains no family, no pedigree, no affected relative genotypes and therefore no informative meioses; segregation was not tested or reported by any source consulted. The criterion cannot be assessed at any strength. No lack of segregation is implied either, so the finding does not argue against pathogenicity.

Rule
ClinGen RASopathy VCEP BRAF v2.3, PP1 (Applicable) - co-segregation with disease in affected family members; >=3 informative meioses = Supporting, >=5 = Moderate, >=7 = Strong; segregation in more than one family recommended. Zero informative meioses available.
Evidence considered
  • Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119). PP1 is listed as Applicable with strength rules: '>=7 informative meioses' (Strong), '>=5 informative meioses' (Moderate), '>=3 informative meioses' (Supporting).
  • Framework instructionsToUse for PP1 quote: 'Segregation in more than one family is recommended.' Framework original ACMG definition retained: 'Co-segregation with disease in multiple affected family members in a gene definitively known to cause the disease.'
  • The case bundle contains no pedigree, no family history and no relative genotypes, so the number of informative meioses is zero and no PP1 strength tier can be reached.
  • Full-text keyword screen of all seven fetched publications for segregation/parental/family-history content returned no co-segregation data for BRAF c.1799T>A; the corpus is uniformly somatic-cancer or functional (PMID:12068308, PMID:15035987, PMID:19251651, PMID:20179705, PMID:22142829, PMID:22855150) or the generic ACMG/AMP framework (PMID:25741868).
  • ClinVar review of the identical variant record (variation IDs 13961 and 178963) shows no expert-panel submission (expert_panel_submissions = 0) and the six criterion-lead submissions (SCV000035247, SCV000035248, SCV000035249, SCV000043966, SCV000035250, SCV000061601) provide no assertion criteria, i.e. no documented segregation evidence.
  • Because no family data were evaluated, absence of PP1 must not be read as evidence of non-segregation; PP1 and BS4 are both uninformative in this case.
Still missing
  • No pedigree or family data are present in the case bundle: no affected relatives, no genotype data for relatives, and no meiosis count.
  • PP1 requires at least 3 informative meioses for Supporting evidence (>=5 Moderate, >=7 Strong) and segregation in more than one family is recommended; zero informative meioses are available.
  • No segregation study for BRAF c.1799T>A was identified in the literature consulted (all seven fetched full texts are somatic-cancer or functional studies with no family-level inheritance data).
  • ClinVar provides no segregation assertions for this variant (no expert-panel submissions; all criterion-lead submissions have 'no assertion criteria provided').
Sources
PP2 Not assessed: no BRAF missense z score or gnomAD gene-constraint metric was available, which PP2 requires. Details ▾Hide ▴
Reasoning

The BRAF VCEP v2.3 operationalises PP2 as a single gene-level test at Supporting strength: 'Missense z score is >3.09 in gnomAD'. No BRAF missense z score, and no gnomAD gene-constraint metric of any kind, is present in the supplied case evidence: the gnomAD artifacts contain only position-level allele counts for this variant, and the local hci_prior lookup returned found=false. Because the gene-level input the governing rule requires is absent, PP2 cannot be assessed; a missense z score recalled from memory is not acceptable as a substitute for a sourced value, and the rule was not broadened to generic 'missense mechanism' reasoning.

Rule
Supporting: Missense z score is >3.09 in gnomAD.
Evidence considered
  • cspec (BRAF VCEP v2.3) PP2: applicability Applicable, default strength Pathogenic Supporting, rule 'Missense z score is >3.09 in gnomAD.'
  • Case artefacts contain gnomAD allele-frequency/variant records for this position only (gnomad_v2, gnomad_v4, gnomad_canada), and hci_prior.json lookup found=false, so no BRAF gene-level missense z score is available in this bundle.
Still missing
  • A sourced BRAF missense z score from gnomAD (or an equivalent gene-constraint artifact) is required; the case bundle contains no such value, so PP2 cannot be evaluated.
Sources
BS4 Not assessed: no family pedigree or affected-relative genotypes were available to demonstrate non-segregation of the variant. Details ▾Hide ▴
Reasoning

The applicable framework is the ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119), in which BS4 is Applicable at Benign Strong strength and, unlike generic ACMG/AMP, 'Requires only one informative meiosis'. BS4 requires demonstration that the variant does not segregate with disease in affected members of a family. No family, pedigree, meiosis or affected-relative genotype is present in this case bundle, and no source consulted reports non-segregation for NM_004333.6:c.1799T>A. The criterion is therefore not assessable and must not be applied as benign evidence.

Rule
ClinGen RASopathy VCEP BRAF v2.3, BS4 (Applicable, Benign Strong) - lack of segregation in affected members of a family; requires only one informative meiosis. No informative meiosis available, so BS4 cannot be applied.
Evidence considered
  • Governing framework: ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF v2.3 (cspec doc 643243119). BS4 is listed as Applicable at default strength Benign Strong with the single strength rule 'Requires only one informative meiosis.'
  • Framework instructionsToUse for BS4 quote: 'Lack of segregation in affected members of a family.' Original ACMG/AMP definition retained: 'Lack of segregation in affected members of a family. Caveat: The presence of phenocopies for common phenotypes (i.e. cancer, epilepsy) can mimic lack of segregation among affected individuals. Also, families may have more than one pathogenic variant contributing to an autosomal dominant disorder, further confounding an apparent lack of segregation.'
  • The case bundle contains no pedigree, no family members and no meiosis results, so there is no segregation observation at all (neither co-segregation nor non-segregation) for this variant.
  • Full-text screen of the seven fetched publications found no segregation analyses for BRAF c.1799T>A; the corpus is somatic-cancer/functional (PMID:12068308, PMID:15035987, PMID:19251651, PMID:20179705, PMID:22142829, PMID:22855150) plus the generic ACMG/AMP guidance paper (PMID:25741868), none of which reports family segregation for this variant.
  • ClinVar data for this variant document classification counts only (7 clinical laboratories Pathogenic, 2 Likely pathogenic, 2 Uncertain significance; variation IDs 13961 and 178963) with no expert-panel submission and no assertion criteria from the criterion-lead submitters, and therefore contain no BS4-relevant segregation findings.
  • No benign-direction evidence is being accrued from this criterion: status is not_assessed (data absent), not a judgement that the variant segregates with disease.
Still missing
  • No family data are available, so the single informative meiosis the RASopathy specification requires for BS4 cannot be evaluated.
  • No report of lack of segregation of BRAF c.1799T>A was found in the ClinVar submissions (no assertion criteria provided) or in any of the seven fetched full texts.
  • BS4 cannot be inferred from the absence of segregation data; a family study showing the variant in unaffected or segregation-discordant relatives would be required.
Sources
BP2 Not assessed: no second BRAF pathogenic variant or phase determination was available to establish an alternative molecular cause. Details ▾Hide ▴
Reasoning

BP2 is applicable under the BRAF VCEP framework, which requires an alternative molecular cause of a RASopathy in the same gene, with phenotype consistent with the expected severity, and uses phase-sensitive evidence such as an additional pathogenic variant in trans or cis. The case bundle contains no affected-proband or family-level observation documenting a second BRAF pathogenic variant, no cis/trans phase determination, and no alternative molecular cause in the same gene. Therefore BP2 cannot be assessed from the available evidence.

Rule
Points are awarded for an alternative molecular cause of a RASopathy in the same gene (and/or in conjunction with BP5) and the phenotype is consistent with expected severity of the RASopathy. Supporting: ≥ (-1) Point; Moderate: ≥ (-2) Points; Strong: ≥ (-4) Points.
Evidence considered
  • The ClinGen RASopathy VCEP specification for BRAF Version 2.3 states that BP2 is applicable when there is an alternative molecular cause of a RASopathy in the same gene and the phenotype is consistent with the expected severity of the RASopathy.
  • The VCEP BP2 rule uses point-based strength thresholds: Supporting at 1 negative point or more, Moderate at 2 negative points or more, and Strong at 4 negative points or more.
  • The supplied case evidence documents the BRAF c.1799T>A (p.Val600Glu) variant but does not provide a second BRAF pathogenic variant, affected-proband phase observation, or cis/trans determination for this case.
Still missing
  • Documented affected-proband or family observation containing an additional pathogenic or likely pathogenic BRAF variant.
  • Validated cis/trans phase information for the target variant and any additional BRAF variant.
  • Phenotypic documentation establishing consistency with the expected severity of the BRAF RASopathy.
  • If an alternative molecular cause is asserted, the specific variant and supporting clinical evidence are required.
Sources
BP5 Not assessed: no co-occurring causative variant or phenotype severity data were available to assign negative points. Details ▾Hide ▴
Reasoning

Under the governing BRAF RASopathy VCEP v2.3, BP5 is awarded through negative point-based scoring: points are given for an alternative molecular cause of a RASopathy in a different gene (and/or in conjunction with BP2) with a phenotype consistent with the expected RASopathy severity, or for a phenotype inconsistent with RASopathy that is fully explained by a different causative variant (for example on WES). Thresholds are at least -1 point (supporting), -2 points (moderate) and -4 points (strong). The bundle contains no individual-level molecular or phenotypic data for the case under review - no co-occurring causative variant, no RASopathy phenotype severity description, and no negative point assignment - so the criterion cannot be scored and is left not_assessed rather than being asserted as absent. Nothing in the reviewed literature or ClinVar submissions documents an alternate molecular basis for this variant.

Rule
ClinGen RASopathy Expert Panel BRAF v2.3 BP5: negative point-based scoring for an alternative molecular cause of a RASopathy in a different gene and/or for a phenotype inconsistent with RASopathy fully explained by a different causative variant; Supporting >=-1 point, Moderate >=-2 points, Strong >=-4 points.
Evidence considered
  • ClinGen RASopathy Expert Panel BRAF v2.3 BP5 (applicable) instructions: 'Points are awarded for an alternative molecular cause of a RASopathy in a different gene (and/or in conjunction with BP2) and the phenotype is consistent with expected severity of the RASopathy. Points are also awarded for phenotypes inconsistent with a RASopathy and fully explained by a different causative variant (e.g. WES testing).'
  • The framework thresholds for BP5 are '>= (-1) Point' = Supporting, '>= (-2) Points' = Moderate and '>= (-4) Points' = Strong.
  • No alternate molecular basis, dual diagnosis, or non-RASopathy explanation is documented anywhere in the bundle for this case, and no case-level clinical data are present to evaluate it.
Still missing
  • Individual-level molecular and phenotypic data for the case under review documenting an alternative causative variant (same or different gene) and the corresponding VCEP negative point assignment.
  • Case-level phenotype information sufficient to judge whether the observed phenotype is inconsistent with a RASopathy and fully explained by another causative variant.
Sources
Not applicable · 8· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 VCEPNot applicable: the BRAF v2.3 specification marks PVS1 not applicable, and p.(Val600Glu) is a missense substitution rather than a loss-of-function change. Details ▾Hide ▴
Reasoning

Not applicable under the governing ClinGen RASopathy Expert Panel BRAF v2.3 specification, which marks PVS1 as not applicable. The normalized preferred-transcript consequence is the single amino-acid substitution p.(Val600Glu), not a predicted loss-of-function variant.

VCEP rule
ClinGen RASopathy Expert Panel BRAF v2.3: PVS1 is not applicable.
Evidence considered
  • The governing BRAF RASopathy Expert Panel specification (v2.3; preferred transcript NM_004333.6) lists PVS1 as not applicable.
  • NM_004333.6:c.1799T>A is normalized to NP_004324.2:p.(Val600Glu), a missense substitution; it does not introduce a premature termination codon, frameshift, canonical splice-site change, or initiation-loss event.
Sources
PS1 N/ANot applicable: c.1799T>A is itself the canonical pathogenic p.(Val600Glu) record, so no different nucleotide change exists to serve as its comparator. Flagged for human review: the specification wording could also be read as making that identical record sufficient. Details ▾Hide ▴
Reasoning

PS1 requires the variant under assessment to share its amino-acid change with a previously established pathogenic variant produced by a DIFFERENT nucleotide change (BRAF VCEP v2.3 PS1: 'Same amino acid change as a previously established pathogenic variant regardless of nucleotide change. Applicable for observed analogous residue positions in BRAF and RAF1.'). NM_004333.6:c.1799T>A is itself the canonical, extensively catalogued BRAF record conferring NP_004324.2:p.(Val600Glu) (ClinVar variation 13961, Pathogenic; the same c.1799T>A nucleotide change), so there is no independent same-amino-acid comparator for PS1 to operate on and the criterion is not applicable to this variant. The VCEP's paralogous-residue branch (analogous positions in BRAF/RAF1) could not be evaluated: the VCEP RAF-Alignment workbook supplies its alignment only as embedded images with no extractable residue mapping, and no registry source documents an established pathogenic RAF1 change at the position analogous to BRAF Val600. Because the CSPEC wording ('regardless of nucleotide change') can also be read as making the identical p.(Val600Glu) record sufficient, this disposition is flagged for human confirmation; PS1 is not used to infer any other criterion.

Rule
Strong: Same amino acid change as a previously established pathogenic variant regardless of nucleotide change. Applicable for observed analogous residue positions in BRAF and RAF1.
Evidence considered
  • cspec (ClinGen RASopathy VCEP specifications for BRAF v2.3) PS1 rule text: 'Same amino acid change as a previously established pathogenic variant regardless of nucleotide change. Applicable for observed analogous residue positions in BRAF and RAF1.' at Strong strength.
  • clinvar was consulted only to identify the retrieved record carrying this amino acid change: the matched record is exactly NM_004333.6(BRAF):c.1799T>A (p.Val600Glu) (variation 13961), i.e. the same nucleotide change, so it is not a distinct same-amino-acid comparator; no criterion was inferred from any classification.
  • pm5_candidates.json: same-residue comparator harvesting reviewed 8 records and returned 0 same-residue candidates and no alternate-nucleotide p.(Val600Glu) comparator.
  • vcep_raf_alignment (RAF-Alignment.xlsx): the 'RAF alignment' sheet is an image-only sheet (1x1 used range, two embedded PNGs, no residue-level text), so the BRAF/RAF1 analogous-residue pathway of PS1 could not be checked from this artifact.
  • Legacy-numbering BRAF literature that reports the same substitution as p.Val599Glu (PMID:12068308, PMID:15035987) was reviewed but not used as a PS1 comparator, because it does not name the transcript-specific p.(Val600Glu) change and cannot supply a distinct alternate-nucleotide record.
Still missing
  • No alternate-nucleotide BRAF variant encoding p.(Val600Glu) with an independently established pathogenic status was retrieved; the only p.(Val600Glu) record in evidence is the identical c.1799T>A change (ClinVar variation 13961).
  • The BRAF/RAF1 analogous-residue branch of the VCEP PS1 rule could not be checked: the VCEP RAF-Alignment workbook alignment sheet contains only embedded images (no machine-readable text) and no registry source documents a pathogenic RAF1 variant at the analogous position.
Sources
PM3 VCEPNot applicable: BRAF v2.3 designates PM3 not applicable because BRAF RASopathy disease is inherited autosomal dominant, not recessive. Details ▾Hide ▴
Reasoning

The applicable ClinGen RASopathy VCEP specification for BRAF Version 2.3 designates PM3 as not applicable. The framework specifies autosomal dominant inheritance for the BRAF RASopathy context, so the recessive-disease in-trans evidence model for PM3 is not used.

VCEP rule
Not applicable.
Evidence considered
  • The ClinGen RASopathy VCEP specification for BRAF Version 2.3 lists PM3 as not applicable and provides no PM3 strength rule.
  • The same specification identifies autosomal dominant inheritance for the BRAF RASopathy disease context.
Sources
PP4 VCEPNot applicable: BRAF v2.3 routes phenotype-specificity evidence to PS4 and explicitly designates PP4 not applicable. Details ▾Hide ▴
Reasoning

The governing BRAF RASopathy VCEP v2.3 specification explicitly designates PP4 as not applicable and routes phenotype-specificity evidence into PS4, stating 'Not applicable, see PS4.' Because the gene-specific framework removes this criterion, PP4 cannot be awarded here regardless of phenotype information. No case phenotype data exist in the bundle in any event.

VCEP rule
ClinGen RASopathy Expert Panel BRAF v2.3: PP4 Not Applicable ('Not applicable, see PS4.').
Evidence considered
  • ClinGen RASopathy Expert Panel BRAF v2.3 lists PP4 with applicability 'Not applicable' and the instruction 'Not applicable, see PS4.', i.e. the phenotype-specificity concept is handled inside PS4 rather than as a separate supporting pathogenic criterion.
  • PP4 (phenotype or family history highly specific for a disease with a single genetic etiology) is therefore superseded by PS4 in this framework and is not scored separately.
Sources
BS3 VCEPNot applicable: BRAF v2.3 explicitly marks BS3 not applicable, so no benign functional evidence criterion is assigned. Details ▾Hide ▴
Reasoning

The applicable BRAF VCEP Version 2.3 framework explicitly marks BS3 as Not Applicable. Therefore, no benign functional evidence criterion is assigned, regardless of the absence of a benign assay result in the reviewed evidence.

VCEP rule
BRAF VCEP Version 2.3: BS3 Not Applicable.
Evidence considered
  • The BRAF VCEP Version 2.3 criterion specification lists BS3 as Not Applicable.
Sources
BP1 N/ANot applicable: BP1 targets truncating variants, whereas p.(Val600Glu) is a missense substitution in a gene whose mechanism is gain of function. Details ▾Hide ▴
Reasoning

The BRAF VCEP v2.3 states that BP1 'has contraindications for use with RASopathies' and restricts it to truncating variants (nonsense, frameshift, canonical splice site, initiation codon, whole-gene or multi-exon deletion) in genes without an established loss-of-function correlation to disease, given the gain-of-function RASopathy mechanism. NM_004333.6:c.1799T>A is a missense substitution (NP_004324.2:p.(Val600Glu)) in exon 15, not a truncating or canonical splice variant, so the variant class the rule targets is not met and BP1 is not applicable.

Rule
Supporting: This rule has contraindications for use with RASopathies. Given the disease mechanism is gain-of-function for RASopathies, BP1 should be used for any truncating variant (nonsense, frameshift, affects canonical splice sites, initiation codon, entire gene or multi exon deletion) in genes without established LOF correlation to disease.
Evidence considered
  • cspec (BRAF VCEP v2.3) BP1 rule: 'This rule has contraindications for use with RASopathies. Given the disease mechanism is gain-of-function for RASopathies, BP1 should be used for any truncating variant (nonsense, frameshift, affects canonical splice sites, initiation codon, entire gene or multi exon deletion) in genes without established LOF correlation to disease.'
  • Case variant record: NM_004333.6:c.1799T>A, NP_004324.2:p.(Val600Glu), consequence_class missense, exon 15, not a canonical splice consensus change (pvs1_variant_assessment).
Sources
BP3 VCEPNot applicable: BRAF v2.3 marks BP3 not applicable, and this is a single-residue substitution rather than an in-frame length change. Details ▾Hide ▴
Reasoning

Not applicable under the governing ClinGen RASopathy Expert Panel BRAF v2.3 specification, which marks BP3 as not applicable. Independently, this is a single-residue substitution rather than an in-frame protein-length change in a repetitive region.

VCEP rule
ClinGen RASopathy Expert Panel BRAF v2.3: BP3 is not applicable.
Evidence considered
  • The governing BRAF RASopathy Expert Panel specification (v2.3) lists BP3 as not applicable.
  • NM_004333.6:c.1799T>A produces p.(Val600Glu), a missense substitution rather than an in-frame insertion or deletion; the BRAF specification also states that there are no known repetitive areas in the gene.
Sources
BP7 N/ANot applicable: c.1799T>A is a coding missense change, not a synonymous, intronic, or non-coding variant as BP7 requires. Details ▾Hide ▴
Reasoning

BP7 as specified by the governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) applies to 'A synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved', and the specification adds that the rule is also applicable to intronic positions (except canonical splice sites) or non-coding variants. NM_004333.6:c.1799T>A is a coding missense substitution, p.(Val600Glu), not a synonymous, intronic or non-coding variant, so BP7 is not applicable. The available SpliceAI result (max delta 0.007, no predicted splice impact) does not create BP7 applicability for a missense change, and it is not being double-counted with the REVEL-based PP3 call.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC BP7: synonymous/intronic (non-canonical)/non-coding variant with no predicted splice impact and non-conserved nucleotide (not applicable to missense variants)
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications for BRAF Version 2.3 (CSPEC doc 643243119) BP7 rule, Supporting strength, applicability 'Applicable': 'A synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved. This rule is also applicable for intronic positions (except canonical splice sites) or non-coding variants and should be used in conjunction with BP4.'
  • Variant normalized as NM_004333.6:c.1799T>A / NP_004324.2:p.(Val600Glu); the change is a coding missense substitution, so the BP7 synonymous/intronic/non-coding precondition is not met.
  • SpliceAI lookup recorded the variant consequence as 'sequence_variant' with max delta 0.007 (DS_AG 0.001, DS_AL 0.007, DS_DG 0.007, DS_DL 0.000); checked for completeness but not used to establish BP7, since BP7 requires a synonymous/intronic/non-coding variant and this variant is missense.
  • ACMG/AMP 2015 standards (PMID 25741868) define BP7 as a synonymous variant with no predicted splice impact and no highly conserved nucleotide.
Still missing
  • Not applicable: no synonymous/intronic/non-coding consequence exists for this variant to evaluate.
Sources

Identifiers

Gene
BRAF
Transcript
NM_004333.6
Coding (HGVS c.)
NM_004333.6:c.1799T>A
Protein (HGVS p.)
NP_004324.2:p.(Val600Glu)
GRCh38
chr7:140753336 A>T
GRCh37
chr7:140453136 A>T
Location and type
Exon 15 · missense
ClinVar
13961, 178963
COSMIC
COSV56056643

Gene diagram

Every interpreted variant in BRAF, mapped onto the exon structure of NM_004333.6. Select a row to find it on the plot.

BRAFNM_004333.6
Fetching transcript structure from UCSC…
gnomAD v4.1 2 / 1,612,922 alleles AF 1.24e-06 · 0 homozygotes
gnomAD v2.1 1 / 251,260 alleles AF 3.98e-06 · 0 homozygotes
gnomAD-Canada v1.0 Allele count data not recorded

By genetic ancestry

gnomAD v4.1

AF 1.2e-06 · 2 / 1,612,922 alleles · 0 hom
South Asian1 / 91,076 1.1e-05
European (non-Finnish)1 / 1,179,108 8.5e-07
0 alternate alleles recorded in 8 other groups: Remaining individuals, Admixed American, European (Finnish), Amish, East Asian, Middle Eastern, Ashkenazi Jewish, African/African American.

gnomAD v2.1

AF 4e-06 · 1 / 251,260 alleles · 0 hom
South Asian1 / 30,612 3.3e-05
0 alternate alleles recorded in 7 other groups: African/African American, Admixed American, Ashkenazi Jewish, East Asian, European (Finnish), European (non-Finnish), Remaining individuals.

Statements

gnomAD v4.1

This variant is present in gnomAD v4.1 (AF= 1.23999e-06; MAF= 0.00012%, 2/1612922 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 1.09798e-05; MAF= 0.00110%, 1/91076 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.97994e-06; MAF= 0.00040%, 1/251260 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26669e-05; MAF= 0.00327%, 1/30612 alleles, homozygotes = 0).

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat +57 bp
0.007
SpliceAI acceptor gainat +6 bp
0.001
SpliceAI donor lossat +477 bp
0.000
SpliceAI donor gainat -61 bp
0.007
Pangolin splice lossmagnitude shown
-0.046
Pangolin splice gain
0.051

Other predictors

REVEL
0.931
BayesDel
0.335

How the predictions were used

PP3 SupportingMet at supporting strength: REVEL 0.931 exceeds the VCEP missense threshold of 0.7. Details ▾Hide ▴
Reasoning

NM_004333.6:c.1799T>A is a missense substitution, NP_004324.2:p.(Val600Glu) (BRAF V600E), so it is adjudicated on the missense protein-impact path. The governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) states for PP3: 'For missense variants: REVEL >= 0.7', at Pathogenic Supporting strength. The local REVEL v1.3 lookup returns REVEL = 0.931 for this variant, which exceeds the 0.7 VCEP cutoff, so PP3 is met at supporting strength. BayesDel (0.335473) was not used because no verified published calibration for these criteria is available to this pipeline. The SpliceAI result was deliberately NOT used as support: a spliced-path score cannot clear a missense variant's protein-level effect, and no predicted splice impact is not evidence about the substituted amino acid.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC PP3: for missense variants, REVEL >= 0.7 -> PP3 supporting
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for BRAF Version 2.3 (CSPEC doc 643243119) PP3 rule, Supporting strength, applicability 'Applicable': 'For missense variants: REVEL >= 0.7. For splicing impact, predicted outcome must match disease mechanism.'
  • Local REVEL v1.3 predictor lookup (revel-v1.3_chrom_07_130418334_149129625.csv.zip) for chr7:140753336 A>T (GRCh38) / chr7:140453136 A>T (GRCh37) returned REVEL = 0.931, i.e. above the BRAF VCEP 0.7 missense cutoff.
  • Variant normalized as NM_004333.6:c.1799T>A / NP_004324.2:p.(Val600Glu) (1-letter p.(V600E)), a missense change, so the missense (not splice) computational path applies.
  • BayesDel_170824_noAF returned 0.335473 for this variant; excluded from PP3 because no verified published BayesDel threshold is available to this pipeline.
  • SpliceAI lookup for NM_004333.6:c.1799T>A returned DS_AG 0.001, DS_AL 0.007, DS_DG 0.007, DS_DL 0.000 (max delta 0.007) with the variant consequence recorded as 'sequence_variant'; this result was not used for PP3 because a missense variant is judged on its protein-impact (REVEL) score, and absence of predicted splice impact says nothing about the p.Val600Glu substitution.
  • ACMG/AMP 2015 standards (PMID 25741868) define PP3 as multiple lines of computational evidence supporting a deleterious effect, with the caveat that PP3 may be used only once per variant.
Still missing
  • No VCEP PP3/BP4 lookup spreadsheet pre-assigning a code for this variant exists in the BRAF VCEP materials (only RAF-Alignment.xlsx for analogous-residue work and the functional-study spreadsheet), so PP3 rests on the CSPEC REVEL threshold plus the local REVEL score alone.
  • BayesDel is available (0.335473) but remains uncalibrated for PP3/BP4 in this pipeline and was not counted.
Sources
BP4 Not met: REVEL 0.931 is far above the 0.3 missense threshold BP4 requires for benign support. Details ▾Hide ▴
Reasoning

NM_004333.6:c.1799T>A (p.Val600Glu) is a missense variant, so BP4 is assessed on the missense path. The governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) BP4 rule is 'For missense variants: REVEL <= 0.3'. The local REVEL v1.3 score is 0.931, which is far above 0.3, so the BP4 benign-supporting threshold is not met. The splice sub-rule of BP4 ('predicted outcome is negligible or does not match disease mechanism') cannot be used to meet BP4 for this missense variant, and in any case the CSPEC requires its in-silico criteria to be counted only once per variant; the same REVEL score that supports PP3 cannot also support BP4. BP4 is therefore not met.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC BP4: for missense variants, REVEL <= 0.3 -> BP4 supporting (not satisfied)
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications for BRAF Version 2.3 (CSPEC doc 643243119) BP4 rule, Supporting strength, applicability 'Applicable': 'For missense variants: REVEL <= 0.3. For splicing variants: predicted outcome is negligible or does not match disease mechanism.'
  • Local REVEL v1.3 predictor lookup returned REVEL = 0.931 for this variant, which does not satisfy the <= 0.3 BP4 cutoff.
  • Variant consequence is a missense substitution p.(Val600Glu); the BP4 splicing sub-rule applies to splicing variants and cannot be substituted for the missense assessment.
  • BayesDel_170824_noAF returned 0.335473; excluded because no verified published BayesDel calibration is available to this pipeline.
  • ACMG/AMP 2015 standards (PMID 25741868) define BP4 as multiple lines of computational evidence suggesting no impact, with the caveat that BP4 may be used only once per variant.
Still missing
  • None affecting the BP4 call: the VCEP missense threshold requires REVEL <= 0.3 and the observed REVEL is 0.931.
Sources
BP7 N/ANot applicable: c.1799T>A is a coding missense change, not a synonymous, intronic, or non-coding variant as BP7 requires. Details ▾Hide ▴
Reasoning

BP7 as specified by the governing ClinGen RASopathy Expert Panel BRAF specification (v2.3, doc 643243119) applies to 'A synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved', and the specification adds that the rule is also applicable to intronic positions (except canonical splice sites) or non-coding variants. NM_004333.6:c.1799T>A is a coding missense substitution, p.(Val600Glu), not a synonymous, intronic or non-coding variant, so BP7 is not applicable. The available SpliceAI result (max delta 0.007, no predicted splice impact) does not create BP7 applicability for a missense change, and it is not being double-counted with the REVEL-based PP3 call.

Rule
ClinGen RASopathy VCEP (BRAF) v2.3 CSPEC BP7: synonymous/intronic (non-canonical)/non-coding variant with no predicted splice impact and non-conserved nucleotide (not applicable to missense variants)
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications for BRAF Version 2.3 (CSPEC doc 643243119) BP7 rule, Supporting strength, applicability 'Applicable': 'A synonymous (silent) variant for which splicing prediction algorithms predict no impact to the splice consensus sequence nor the creation of a new splice site AND the nucleotide is not highly conserved. This rule is also applicable for intronic positions (except canonical splice sites) or non-coding variants and should be used in conjunction with BP4.'
  • Variant normalized as NM_004333.6:c.1799T>A / NP_004324.2:p.(Val600Glu); the change is a coding missense substitution, so the BP7 synonymous/intronic/non-coding precondition is not met.
  • SpliceAI lookup recorded the variant consequence as 'sequence_variant' with max delta 0.007 (DS_AG 0.001, DS_AL 0.007, DS_DG 0.007, DS_DL 0.000); checked for completeness but not used to establish BP7, since BP7 requires a synonymous/intronic/non-coding variant and this variant is missense.
  • ACMG/AMP 2015 standards (PMID 25741868) define BP7 as a synonymous variant with no predicted splice impact and no highly conserved nucleotide.
Still missing
  • Not applicable: no synonymous/intronic/non-coding consequence exists for this variant to evaluate.
Sources

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.01). REVEL score = 0.931. BayesDel score = 0.335473.

7 paper records listed. 6 cited in the classification.

Cited in the classification

  • Mutations of the BRAF gene in human cancer.
    Davies H et al. · 2002 Jun 27
    The founding systematic BRAF cancer-mutation screen reports that BRAF mutations cluster in the kinase domain and that a single substitution, reported in that paper's older numbering as V599E (the same amino-acid substitution as p.Val600Glu in current transcript numbering; the paper gives nucleotide change T1796A), accounted for 80% of BRAF mutations including 35/38 melanoma mutations, with elevated kinase activity, ERK1/2 phosphorylation, NIH3T3 transformation and RAS-independent growth of the mutant-expressing lines. The paper does not use NM_004333.6 c.1799T>A or NP_004324.2 p.(V600E) notation, so it was reviewed but not used as a distinct same-amino-acid comparator for PS1 and not cited for a criterion in this group.
    → PM2 · supporting Does not name this variant
    PMID 12068308 ↗
    Source detail
    All mutations are within the kinase domain, with a single substitution (V599E) accounting for 80%. Mutated BRAF proteins have elevated kinase activity and are transforming in NIH3T3 cells. Furthermore, RAS function is not required for the growth of cancer cell lines with the V599E mutation.

    Location Abstract; Results paragraphs describing mutation frequency and functional characterization; Table 1; Table 2; Table 3

    Context Somatic mutation screening of 545 cancer cell lines and 378 primary cancers/short-term cultures; BRAF kinase cascade assays and ERK1/2 phosphorylation assays in transiently transfected COS cells; NIH3T3 focus-transformation assays; RAS-neutralizing antibody and MEK-inhibitor treatment of cancer cell lines.

  • (V600E)BRAF is associated with disabled feedback inhibition of RAF-MEK signaling and elevated transcriptional output of the pathway.
    Pratilas et al. show that BRAF V600E tumours have disabled feedback inhibition of RAF-MEK signalling and elevated transcriptional output of the pathway, defining MEK/ERK-dependent gene expression signatures. This is a functional/signalling study in tumour models and contains no proband-level inheritance, de novo or segregation information for the variant.
    → PS3 · moderate Names this variant
    PMID 19251651 ↗
    Source detail
    Tumors with mutant BRAF and those with receptor tyrosine kinase (RTK) activation have similar levels of phosphorylated ERK, but only the former depend on ERK signaling for proliferation.

    Location Abstract and Results (MEK/ERK-dependent transcriptional output in BRAF-mutant tumours)

    Context Tumour cell-line and xenograft signalling studies defining MEK/ERK-dependent gene expression signatures in BRAF-mutant versus RTK-driven tumours.

  • RAF inhibitors transactivate RAF dimers and ERK signalling in cells with wild-type BRAF.
    Poulikakos et al. study BRAF V600E explicitly and show that ATP-competitive RAF inhibitors inhibit MEK/ERK signalling in BRAF V600E cells, while increased RAS activity promotes RAF dimerisation/transactivation and resistance, with reported clinical responses to PLX4032 in BRAF V600E tumours. The paper is mechanistic/clinical-trial oriented and provides no germline de novo or family segregation evidence.
    → PS3 · moderate Names this variant
    PMID 20179705 ↗
    Source detail
    In BRAFV600E tumors, RAS is not activated, thus transactivation is minimal and ERK signaling is inhibited in cells exposed to RAF inhibitors.

    Location Results, opening paragraph; Results, paragraph beginning 'Nevertheless, the clinical utility of these inhibitors…'; clinical implications section

    Context Cell-based MEK/ERK signalling assays in 293H and HT29 cells expressing endogenous or introduced BRAFV600E with RAF inhibitors (PLX4032/PLX4720) versus a MEK inhibitor, plus discussion of a phase I PLX4032 trial in metastatic melanoma.

  • Oncogene mutation profiling of pediatric solid tumors reveals significant subsets of embryonal rhabdomyosarcoma and neuroblastoma with mutated genes in growth signaling pathways.
    This paediatric solid-tumour hotspot screen reports the exact activating BRAFV600E change in three tumours (one neuroblastoma, one embryonal rhabdomyosarcoma, one Ewing sarcoma) detected by Sequenom MassARRAY and verified by Sanger sequencing. It documents recurrent occurrence of the same amino-acid change at residue 600 in the activation segment, which was used as corroborating residue/domain context for PM1; it does not compare same-codon substitutions and so was not used for PM5.
    → PM1 · moderate Names this variant
    PMID 22142829 ↗
    Source detail
    BRAF mutations were identified in 1% (2/192) of NB samples, 1.7% (1/60) of ERMS samples, and 1.3% (1/75) of ES samples. The ERMS and ES samples harbored the activating BRAFV600E mutation. One NB sample carried the BRAFV600E mutation, while the other carried the less common BRAFD594V mutation.

    Location Results, paragraph beginning “BRAF mutations were identified”

    Context Sequenom MassARRAY hotspot mutation screen of paediatric solid-tumour samples, with identified mutations verified by bidirectional Sanger sequencing.

  • Guidelines for biomarker testing in colorectal carcinoma (CRC): a national consensus of the Spanish Society of Pathology (SEAP) and the Spanish Society of Medical Oncology (SEOM).
    This colorectal-carcinoma biomarker consensus states that the V600E substitution is the most common BRAF mutation (about 90% of BRAF mutations) and localises it to the protein kinase domain encoded by exon 15. It names the exact protein change p.V600E (without the c.1799T>A coding notation), so it was used to corroborate that residue 600 lies within the BRAF kinase domain, consistent with the VCEP CR3 activation-segment domain assignment used for PM1.
    → PM1 · moderate → PM2 · supporting Names this variant
    PMID 22855150 ↗
    Source detail
    The most common mutation (*90 %) is the V600E substitution, located in the kinase domain of the protein (exon 15). BRAF mutations and KRAS mutations are mutually exclusive, so the former are never found in KRAS-mutated tumours and vice versa. They are associated with the presence of high microsatellite instability (MSI-H) induced by acquired defects in MMR enzyme function [13, 31]. In other contexts, particularly in advanced disease, the presence of BRAF mutations is associated with a worse prognosis [13, 31, 33, 34, 38, 42, 43].

    Location Molecular markers of metastatic CRC, subsection “BRAF,” page 731; subsection “BRAF testing,” page 735

    Context Consensus review of biomarker testing in colorectal carcinoma; the paper states that BRAF V600E can be studied by sequencing but does not report a variant-specific cohort or functional assay.

  • 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.
    Standard ACMG/AMP 2015 interpretation framework paper; it defines PS2, PM6, PP1 and BS4 but reports no variant-, gene- or family-specific data for BRAF. It states explicitly that the approach is intended for inherited (primarily Mendelian) disorders and not for somatic variation, so its PS2/PM6 language only supplies the generic criterion definitions that the RASopathy VCEP specifications then modify with point-based scoring.
    → PP3 · supporting Does not name this variant
    PMID 25741868 ↗
    Source detail
    The following approach to evaluating evidence for a variant is intended for interpretation of variants observed in patients with suspected inherited (primarily Mendelian) disorders in a clinical diagnostic laboratory setting. It is not intended for the interpretation of somatic variation, pharmacogenomic (PGx) variants, or variants in genes associated with multigenic non-Mendelian complex disorders.

    Location Proposed Criteria for Interpretation of Sequence Variants (PS2, PM6, PP1, BS4 definitions), page 6 and criteria tables

    Context Consensus recommendation / guideline document for sequence variant interpretation (no cohort, assay or family data).

Other recorded publications

  • Mechanism of activation of the RAF-ERK signaling pathway by oncogenic mutations of B-RAF.
    Reports that oncogenic B-RAF mutations are concentrated in the kinase domain and characterises the activation-segment substitution reported in that paper's older numbering as V599E (same amino-acid substitution as p.Val600Glu; not the transcript-specific notation), showing approximately 500-fold higher kinase-domain activity than wild type even after dephosphorylation, constitutive RAS-independent ERK stimulation in cells, and structural disruption of the inactive DFG/activation-segment conformation. Reviewed for this group's residue/domain question and, because it does not name p.(Val600Glu), deliberately not used as a PS1/PM5 comparator or cited for a criterion.
    Does not name this variant
    PMID 15035987 ↗
    Quoted passage
    The V599EΔB-RAF kinase domain was ∼500-fold more active than WTΔB-RAF (data not shown). Thus the Glu substitution for Val599 exerts its stimulatory effect on kinase activity within the context of the kinase domain of B-RAF, and this suggests that B-RAF activation is not simply a release from the autoinhibitory restraints conferred by the N-terminal region. Moreover, because we dephosphorylated the purified B-RAF kinase domain, the high activity of V599EΔB-RAF indicates that activation segment phosphorylation is not required for the kinase activity of the mutant protein.

    Results and Discussion, “Expression, Purification, and Enzyme Activity of WT B-RAF and V599E B-RAF Kinase Domains”

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= 1.23999e-06; MAF= 0.00012%, 2/1612922 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 1.09798e-05; MAF= 0.00110%, 1/91076 alleles, homozygotes = 0).

gnomAD v2.1

This variant is present in gnomAD v2.1 (AF= 3.97994e-06; MAF= 0.00040%, 1/251260 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26669e-05; MAF= 0.00327%, 1/30612 alleles, homozygotes = 0).

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Pathogenic (7 clinical laboratories) and as Likely pathogenic (2 clinical laboratories) and as Uncertain significance (2 clinical laboratories). (ClinVarID = 13961)

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.01). REVEL score = 0.931. BayesDel score = 0.335473.

Functional

OncoKB identified variant-specific curated literature and context relevant to functional review; biological-effect context: Gain-of-function; curated oncogenicity label: Oncogenic.

Somatic

This variant lies in a statistically significant hotspot. This variant has previously been reported in somatic cancers (COSMIC; COSV56056643, n = 31792 times).

Cancer Hotspots

This variant lies in a statistically significant hotspot.