0%
Print report
Variant interpretation report

PTPN11 c.226G>A, p.Glu76Lys

NM_002834.5:c.226G>A NP_002825.3:p.(Glu76Lys) Missense · exon 3 View identifiers
Classification
Uncertain significance

Variant description:

The PTPN11 NM_002834.5:c.226G>A (NP_002825.3:p.(Glu76Lys)) missense variant has previously been reported in somatic cancers (COSMIC; COSV61004889, n = 184 times), and lies in a statistically significant hotspot (cancerhotspots.org). Experimental evidence: E76K is listed in the approved PTPN11 SHP-2 phosphatase assay's P/LP/VUS validation controls, satisfying the VCEP one-approved-assay rule. Based on available guidelines, this variant is considered to be a Variant of Uncertain Significance (VUS).

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

Uncertain.The recorded classification is uncertain significance.

In plain language

Gene-level background from the recorded interpretation.

About PTPN11

PTPN11 encodes SHP2, a protein tyrosine phosphatase that helps regulate signaling pathways controlling cell growth, development, metabolism, and movement. Inherited changes in PTPN11 are associated with Noonan syndrome and LEOPARD syndrome, which can increase the risk of juvenile myelomonocytic leukemia and related blood disorders. PTPN11 acts as an oncogene, and acquired changes in the gene occur in several cancers, especially juvenile myelomonocytic 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 PTPN11 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
PS3Supporting
PS3 · supporting

Met, supporting: E76K is listed in the approved PTPN11 SHP-2 phosphatase assay's P/LP/VUS validation controls, satisfying the VCEP one-approved-assay rule.

PM1Moderate
PM1 · moderate

Met at Moderate: residue 76 falls within the VCEP-approved directly interacting N-SH2/PTPN domain interval of amino acids 69-77.

PM2Supporting
PM2 · supporting

Met at Supporting: the variant was absent from all-comers gnomAD v2.1 and v4.1 and from the available non-cancer subsets.

PP3Supporting
PP3 · supporting

Met (Supporting): REVEL score 0.863 meets the VCEP PP3 missense threshold of >= 0.7.

Benign criteria applied · 0

No benign criterion marked as applied in the recorded assessment.

Recorded classification: Uncertain significance

VUS: PS3 (supporting), PM1 (moderate), PM2 (supporting), and PP3 (supporting) do not satisfy any PTPN11 VCEP combination rule.

02The sources

Evidence at a glance

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

No screenshot for this evidence
REVEL score
0.863 recorded score

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

ClinVar submissions
9 reported laboratory submissions

8 Pathogenic · 1 Uncertain significance. ClinVar API review status: criteria provided, conflicting classifications.

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
184 recorded samples

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

Cancer Hotspots

This variant lies in a statistically significant hotspot.

For specialists

Technical detail

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

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

Met Not met Not assessed Not applicable

All four requested segregation/de novo criteria are not_assessed because the available evidence does not document parental testing, de novo status, family segregation, non-segregation, or informative meioses.

PS4 is not assessed because the available E76K report is a somatic myeloid-malignancy observation without VCEP-compatible germline RASopathy phenotype-specific case-control data or a point score.

PP4, PP5, and BP6 are not applicable under the PTPN11 VCEP; BP5 is not assessed because no alternate molecular cause or VCEP point score is documented.

Met · 4

PS3 SupportingVCEPMet, supporting: E76K is listed in the approved PTPN11 SHP-2 phosphatase assay's P/LP/VUS validation controls, satisfying the VCEP one-approved-assay rule. Details ▾Hide ▴
Reasoning

The ClinGen RASopathy VCEP approved-functional-studies table lists the PTPN11 SHP-2 phosphatase activity assay as approved. This gene-specific assay measures substrate dephosphorylation, includes WT and vector controls, three to four independent technical experiments, 16 pathogenic/likely pathogenic validation controls and 17 benign/likely benign validation controls, and defines increased dephosphorylation as abnormal. The queried E76K variant is explicitly included among the P/LP/VUS validation controls for this approved assay. The VCEP PS3 rule assigns Supporting strength when one approved assay is available; therefore PS3 is met at Supporting strength. PMID:14644997 independently reports E76K-associated increased Ba/F3-cell survival after IL-3 withdrawal, but its ERK/Akt phosphorylation results were not uniformly increased and are not used to upgrade the VCEP-calibrated strength.

VCEP rule
Well-established in vitro or in vivo functional studies supportive of a damaging effect on the gene or gene product. Approved assays are available in the supplemental materials. ... One approved assay.
Evidence considered
  • SVI-RASopathy-VCEP-V2-Approved-Functional-Studies.xlsx, sheet 'SHP-2 Phosphatase Activity', PTPN11 column: approved assay; substrate dephosphorylation readout; biological replicates not met; technical replicates met (3/4 independent experiments); WT positive control and vector negative control met; 16 P/LP validation controls and 17 B/LB validation controls; normal readout normal dephosphorylation; abnormal readout increased dephosphorylation; proposed strength PS3/BS3.
  • SVI-RASopathy-VCEP-V2-Approved-Functional-Studies.xlsx, sheet 'SHP-2 Phosphatase Activity', validation-controls row: E76K is explicitly listed as 'E76K - P/LP/VUS'.
  • PMID:14644997: Table 1 and functional studies report the exact E76K variant and enhanced Ba/F3-cell survival after IL-3 withdrawal; the paper did not show increased ERK or Akt phosphorylation under the tested conditions, so it does not justify strength beyond the VCEP-approved-assay calibration.
Sources
PM1 ModerateVCEPMet at Moderate: residue 76 falls within the VCEP-approved directly interacting N-SH2/PTPN domain interval of amino acids 69-77. Details ▾Hide ▴
Reasoning

The VCEP limits PM1 to critical, well-established functional domains listed in its supplementary table and specifies directly interacting residues between the N-SH2 and PTPN domains, including amino acids 69-77. The variant is p.Glu76Lys at residue 76, which lies within the explicitly listed 69-77 interval; no domain_tables entry is present for PTPN11 in vcep_materials.json. The variant is not excluded as a specific residue under PM1 because the rule's exclusion refers to the separate PM5 route, while the applicable evidence here is domain membership.

VCEP rule
Applicable only to critical and well-established functional domains available in the supplementary table (Directly interacting residues between N-SH2 and PTPN domains [AA 4, AA 7-9, AA 58-63, AA 69-77, AA 247, AA 251, AA 255, AA 256, AA 258, AA 261, AA 265, AA 278-281, AA 284]). Not applicable to specific amino acid residues (see PM5).
Evidence considered
  • PTPN11 VCEP PM1 rule lists directly interacting N-SH2 and PTPN residues AA 4, AA 7-9, AA 58-63, AA 69-77, AA 247, AA 251, AA 255, AA 256, AA 258, AA 261, AA 265, AA 278-281, and AA 284.
  • The queried protein change is NP_002825.3:p.(Glu76Lys), so residue 76 is within the approved AA 69-77 interval.
  • vcep_materials.json contains an empty domain_tables object for this case; the governing CSPEC PM1 domain list is therefore the available authoritative VCEP domain specification.
Sources
PM2 SupportingVCEPMet at Supporting: the variant was absent from all-comers gnomAD v2.1 and v4.1 and from the available non-cancer subsets. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP applies PM2 at Supporting strength when the variant is absent from controls in gnomAD. NM_002834.5:c.226G>A (p.Glu76Lys) was absent from all-comers gnomAD v2.1 and v4.1, and was also absent from gnomAD v2.1 non-cancer exomes and gnomAD v3.1 non-cancer genomes; PM2 Supporting is met.

VCEP rule
The variant must be absent from controls (gnomAD).
Evidence considered
  • PTPN11 VCEP Version 2.3 CSPEC PM2 entry: the variant must be absent from controls (gnomAD); Supporting is the applicable strength.
  • gnomAD v2.1 all-comers query for 12-112888210-G-A: search status absent.
  • gnomAD v4.1 all-comers query for 12-112450406-G-A: search status absent.
  • gnomAD v2.1 non-cancer exomes query: absent; gnomAD v3.1 non-cancer genomes query: absent.
Sources
PP3 SupportingVCEPMet (Supporting): REVEL score 0.863 meets the VCEP PP3 missense threshold of >= 0.7. Details ▾Hide ▴
Reasoning

The variant is missense, NP_002825.3:p.(Glu76Lys), so the VCEP's missense PP3 path applies. The governing rule requires REVEL >= 0.7 for missense variants. The available REVEL score is 0.863, which meets that threshold; this is sufficient for PP3 Supporting. The SpliceAI result (maximum delta score 0.021) is not used for PP3 because the missense path is independently satisfied by the named REVEL predictor, and the same splice prediction is not double-counted in another criterion.

VCEP rule
For missense variants: REVEL >= 0.7. For splicing impact, predicted outcome must match disease mechanism.
Evidence considered
  • VCEP CSPEC PP3 rule: for missense variants, REVEL >= 0.7.
  • Local REVEL predictor lookup: NM_002834.5:c.226G>A / NP_002825.3:p.(Glu76Lys), REVEL = 0.863; this exceeds the VCEP threshold of 0.7.
  • Variant consequence is missense: NP_002825.3:p.(Glu76Lys). SpliceAI max delta score = 0.021 was not counted for PP3 because the VCEP missense path names REVEL, and predictions are not double-counted across criteria.
Sources

Not met · 5 · evaluated, threshold not reached

PS1 VCEPNot met: no independently reported nucleotide change producing the same pathogenic p.Glu76Lys amino acid substitution is documented. Details ▾Hide ▴
Reasoning

The VCEP requires the same amino acid change as a previously established pathogenic PTPN11 variant regardless of nucleotide change. The available literature and ClinVar material document the queried NM_002834.5:c.226G>A, p.(Glu76Lys) variant itself, including its occurrence in leukemia, but do not document a different nucleotide change producing the same p.Glu76Lys amino acid change as a previously established pathogenic variant. Therefore PS1 is not met.

VCEP rule
Same amino acid change as a previously established pathogenic variant in _PTPN11_ regardless of nucleotide change.
Evidence considered
  • The queried variant is NM_002834.5:c.226G>A, NP_002825.3:p.(Glu76Lys).
  • Loh et al. report the queried c.226G>A/Glu76Lys variant in leukemia specimens; this is the same nucleotide and amino acid change, not an alternate-nucleotide comparator.
  • ClinVar variation 13336 has conflicting classifications and no expert-panel submission in the supplied record; it does not establish a separate same-amino-acid comparator variant.
Still missing
  • A validated comparator with a different nucleotide change but the same p.Glu76Lys consequence would be needed to meet PS1.
Sources
PM5 VCEPNot met: the comparator collection contains 0 same-residue candidates, below the VCEP requirement of 1 likely pathogenic change at codon 76. Details ▾Hide ▴
Reasoning

The VCEP assigns PM5 at Moderate strength for one likely pathogenic residue change at the same codon, and Strong strength only for at least two different likely pathogenic residue changes at the same codon observed in at least five probands. The supplied PM5 comparator collection contains eight candidates but zero same-residue candidates, so neither PM5 threshold is met.

VCEP rule
≥2 different [likely] pathogenic residues changes at the same codon observed in ≥5 probands. ... 1 [likely] pathogenic residue change at the same codon.
Evidence considered
  • The queried variant affects codon 76 (p.Glu76Lys).
  • The PM5 comparator candidate collection reports total_candidates_seen = 8 and same_residue_candidates = 0.
  • No collected comparator satisfies the VCEP requirement for a likely pathogenic alternate residue change at the same codon.
Still missing
  • A likely pathogenic missense change at codon 76 is required for PM5 Moderate; two such changes and at least five probands are required for PM5 Strong.
Sources
cspec ↗pm5_candidates
BA1 VCEPNot met: the variant was absent from gnomAD v2.1 and v4.1, rather than reaching the VCEP's 0.05% filtering allele-frequency threshold. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP requires a gnomAD filtering allele frequency of at least 0.05% for BA1. NM_002834.5:c.226G>A (p.Glu76Lys) was absent from all-comers gnomAD v2.1 and v4.1, and also absent from gnomAD v2.1 non-cancer exomes and gnomAD v3.1 non-cancer genomes; therefore the BA1 frequency threshold is not met.

VCEP rule
GnomAD filtering allele frequency ≥0.05%.
Evidence considered
  • PTPN11 VCEP Version 2.3 CSPEC BA1 entry: GnomAD filtering allele frequency ≥0.05%.
  • gnomAD v2.1 all-comers query for 12-112888210-G-A: search status absent; no allele-frequency record returned.
  • gnomAD v4.1 all-comers query for 12-112450406-G-A: search status absent; no allele-frequency record returned.
  • gnomAD v2.1 non-cancer exomes query: absent; gnomAD v3.1 non-cancer genomes query: absent.
Sources
BS1 VCEPNot met: the variant was absent from gnomAD v2.1 and v4.1, rather than reaching the VCEP's 0.025% filtering allele-frequency threshold. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP requires a gnomAD filtering allele frequency of at least 0.025% for BS1. NM_002834.5:c.226G>A (p.Glu76Lys) was absent from all-comers gnomAD v2.1 and v4.1, and also absent from gnomAD v2.1 non-cancer exomes and gnomAD v3.1 non-cancer genomes; therefore the BS1 frequency threshold is not met.

VCEP rule
GnomAD filtering allele frequency ≥0.025%.
Evidence considered
  • PTPN11 VCEP Version 2.3 CSPEC BS1 entry: GnomAD filtering allele frequency ≥0.025%.
  • gnomAD v2.1 all-comers query for 12-112888210-G-A: search status absent; no allele-frequency record returned.
  • gnomAD v4.1 all-comers query for 12-112450406-G-A: search status absent; no allele-frequency record returned.
  • gnomAD v2.1 non-cancer exomes query: absent; gnomAD v3.1 non-cancer genomes query: absent.
Sources
BP4 VCEPNot met: REVEL score 0.863 exceeds the VCEP BP4 missense threshold of <= 0.3. Details ▾Hide ▴
Reasoning

The variant is missense, so BP4 is within the VCEP rule's stated scope. The governing rule requires REVEL <= 0.3 for missense variants. The available REVEL score is 0.863, which does not meet the <= 0.3 benign-prediction threshold. Therefore BP4 is not met. The low SpliceAI score is not substituted for the VCEP's named missense predictor and is not independently used for BP4.

VCEP rule
For missense variants: REVEL <= 0.3.
Evidence considered
  • VCEP CSPEC BP4 rule: for missense variants, REVEL <= 0.3.
  • Local REVEL predictor lookup: NM_002834.5:c.226G>A / NP_002825.3:p.(Glu76Lys), REVEL = 0.863; this exceeds the VCEP threshold of 0.3, so BP4 is not met.
  • SpliceAI max delta score = 0.021 was not substituted for REVEL because the VCEP BP4 rule for this missense situation names REVEL.
Sources

Not assessed · 9 · no assessment recorded

PS2 VCEPNot assessed: no documented proband-parent testing or de novo point count is available to apply the VCEP PS2 thresholds. Details ▾Hide ▴
Reasoning

The available case evidence does not document that the PTPN11 c.226G>A (p.Glu76Lys) variant is de novo, does not identify parental genotypes, and does not provide a VCEP de novo point count. Therefore, the VCEP PS2 strength cannot be assigned.

VCEP rule
4 Points. ... 2 Points. ... 1 Point.
Evidence considered
  • No proband-parent genotype results, confirmed de novo status, or de novo point assignment are documented for NM_002834.5:c.226G>A (p.Glu76Lys).
Still missing
  • Documented parental genotypes and confirmation that the variant is absent in both unaffected parents are missing.
  • The VCEP PS2 point assignment cannot be determined without the proband and parental evidence required for scoring.
Sources
PS4 VCEPNot assessed: E76K was reported in 3 JMML and 1 AML specimens, but no germline RASopathy case-control counts, OR/RR, confidence interval, or PS4 point score were reported. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP defines PS4 using point-based scoring for autosomal-dominant cases with RASopathy phenotypic specifications. Its governing rule requires that the prevalence of the variant in affected individuals be significantly increased versus controls; the VCEP reproduces the ACMG/AMP case-control guidance that RR or OR must be >5.0 with a confidence interval excluding 1.0, while multiple unrelated patients with the same phenotype and absence from controls may support moderate evidence in very rare variants. PMID:14644997 verifies NM_002834.5:c.226G>A (p.Glu76Lys) in 3 JMML specimens and 1 AML specimen, but this is a somatic myeloid-malignancy mutation cohort, not a germline RASopathy case-control comparison, and it supplies no affected/control counts, OR or RR, confidence interval, or VCEP PS4 point score. The available evidence therefore cannot evaluate PS4 under this VCEP; no case-control conclusion or strength assignment is made.

VCEP rule
Strength adjustment using point-based scoring for autosomal dominant cases with 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)). ... The prevalence of the variant in affected individuals is significantly increased compared to the prevalence in controls. ... Note 1: Relative risk (RR) or odds ratio (OR), as obtained from case-control studies, is >5.0 and the confidence interval around the estimate of RR or OR does not include 1.0. See manuscript for detailed guidance. ... Note 2: In instances of very rare variants where case-control studies may not reach statistical significance, the prior observation of the variant in multiple unrelated patients with the same phenotype, and its absence in controls, may be used as moderate level of evidence. ... ≥5 points. ... ≥3 points. ... ≥1 points.
Evidence considered
  • ClinGen RASopathy VCEP PTPN11 v2.3 PS4 rule: point-based scoring applies to autosomal-dominant cases with RASopathy phenotypic specifications; the rule's affected-versus-control prevalence and >5.0 RR/OR guidance could not be evaluated from the available evidence.
  • PMID:14644997, Table 1 and Table 3: PTPN11 c.226G>A (Glu76Lys/E76K) occurred in 3 JMML specimens and 1 AML specimen; the study context was PTPN11 mutation screening in myeloid malignancies, not a germline RASopathy case-control cohort.
  • The literature packet's ai_classified_papers array is empty; the available variant-specific full-text extraction for PMID:14644997 was checked directly for phenotype/prevalence evidence and does not provide PS4 case-control counts or an OR/RR confidence interval.
Still missing
  • A VCEP-compatible germline RASopathy phenotype-specific PS4 point score is unavailable.
  • No affected/control counts or matched-control frequency permitting calculation of OR/RR and its 95% CI are available.
Sources
PM6 VCEPNot assessed: no apparently de novo occurrence without parental testing or VCEP PM6 point assignment is documented. Details ▾Hide ▴
Reasoning

The available evidence does not document an apparently de novo occurrence without parental testing, nor does it provide the VCEP point assignment for such evidence. The VCEP PM6 criterion therefore cannot be evaluated.

VCEP rule
2 Points. ... 1 Point. ... 0.5 Points.
Evidence considered
  • No parental-testing-independent de novo observation or VCEP PM6 point assignment is documented for NM_002834.5:c.226G>A (p.Glu76Lys).
Still missing
  • A documented apparently de novo occurrence and the evidence supporting it are missing.
  • The VCEP PM6 point assignment cannot be determined from the available case evidence.
Sources
PP1 VCEPNot assessed: zero informative meioses are documented, so none of the VCEP PP1 thresholds can be applied. Details ▾Hide ▴
Reasoning

The available case evidence contains no documented affected relatives, family segregation results, or informative meioses for NM_002834.5:c.226G>A (p.Glu76Lys). The VCEP PP1 thresholds therefore cannot be evaluated.

VCEP rule
≥7 informative meioses. ... ≥5 informative meioses. ... ≥3 informative meioses.
Evidence considered
  • No family segregation data or informative meiosis count is documented for NM_002834.5:c.226G>A (p.Glu76Lys).
Still missing
  • Affected-relative genotypes and phenotypes are not documented.
  • The number of informative meioses is not available.
Sources
PP2 VCEPNot assessed: the required PTPN11 gnomAD missense z score is unavailable, so comparison with the >3.09 threshold is impossible. Details ▾Hide ▴
Reasoning

The VCEP requires a missense z score greater than 3.09 in gnomAD. The supplied case evidence contains no PTPN11 missense z score, so the criterion cannot be evaluated under the VCEP rule without substituting an unapproved metric.

VCEP rule
Missense z score is >3.09 in gnomAD.
Still missing
  • PTPN11's gnomAD missense z score is required.
Sources
BS2 VCEPNot assessed: no qualifying healthy homozygote or heterozygote observation and no VCEP BS2 point assignment are documented. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP evaluates BS2 using point-based scoring from healthy homozygote or heterozygote observations, with reduced points for apparently unaffected heterozygotes and applicability to parent or sibling samples during clinical family evaluations. The available population evidence documents absence from gnomAD but does not document a qualifying healthy homozygote or heterozygote, unaffected parent or sibling, phenotype assessment, or BS2 point assignment; therefore BS2 cannot be assessed.

VCEP rule
Strength adjustment using point-based scoring based on phenotypic specifications. 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.
Evidence considered
  • PTPN11 VCEP Version 2.3 CSPEC BS2 entry: strength adjustment uses point-based scoring based on phenotypic specifications, including healthy homozygote or heterozygote individuals and parent or sibling samples during clinical family evaluations.
  • The variant is absent from gnomAD v2.1 and v4.1, but absence is not a documented healthy-carrier or healthy-homozygote observation and does not supply a BS2 point score.
Still missing
  • A documented healthy adult homozygote or heterozygote observation for this variant.
  • For an apparently unaffected heterozygote, clinical phenotype and relationship information needed for the VCEP point score.
  • The VCEP BS2 point assignment derived from any qualifying parent, sibling, or population observation.
Sources
BS4 VCEPNot assessed: no non-segregating carrier or informative meiosis is documented to meet the VCEP BS4 requirement. Details ▾Hide ▴
Reasoning

The available case evidence does not document an unaffected relative who carries the variant, a non-segregation observation, or any informative meiosis. The VCEP BS4 requirement cannot therefore be evaluated.

VCEP rule
Requires only one informative meiosis.
Evidence considered
  • No unaffected carrier relative, non-segregation result, or informative meiosis is documented for NM_002834.5:c.226G>A (p.Glu76Lys).
Still missing
  • An unaffected relative carrying the variant and the corresponding phenotype assessment are not documented.
  • The required informative meiosis is not documented.
Sources
BP2 VCEPNot assessed: no qualifying second pathogenic variant, cis/trans phase, and phenotype evidence is documented for the BP2 point thresholds. Details ▾Hide ▴
Reasoning

The VCEP permits BP2 when an alternative molecular cause of a RASopathy is present in the same gene and the phenotype is consistent with the expected severity, with point-based strength thresholds. The available case evidence does not document a second pathogenic variant in cis or trans with NM_002834.5:c.226G>A, establish phase, or provide a qualifying alternative molecular cause and phenotype assessment; therefore no BP2 strength can be assigned.

VCEP 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.
Evidence considered
  • The case-specific evidence identifies NM_002834.5:c.226G>A (p.Glu76Lys) but contains no documented second pathogenic allele, cis/trans phase result, or qualifying affected-proband genotype observation.
  • The available ClinVar and literature records report classifications or variant-specific observations, but do not provide the phase and alternative-molecular-cause evidence required by the VCEP BP2 instructions.
Still missing
  • Documented identification of a second pathogenic variant in PTPN11 or another qualifying alternative molecular cause.
  • Parental or other molecular testing establishing whether the variants are in cis or trans.
  • Phenotype documentation sufficient to determine consistency with the expected RASopathy severity under the VCEP rule.
Sources
BP5 VCEPNot assessed: no alternate-gene causative variant, fully explanatory alternate diagnosis, or VCEP BP5 point score is documented. Details ▾Hide ▴
Reasoning

BP5 is applicable under the PTPN11 VCEP when an alternative molecular cause of a RASopathy in a different gene is present, with a phenotype consistent with the expected severity, or when a phenotype inconsistent with RASopathy is fully explained by a different causative variant. The case evidence contains no alternative causative variant, no alternate-gene molecular diagnosis, no documented phenotype fully explained by another variant, and no BP5 point score. The criterion therefore cannot be evaluated under the VCEP and is not assessed.

VCEP rule
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). ... ≥ (-4) Points. ... ≥ (-2) Points. ... ≥ (-1) Point.
Evidence considered
  • The VCEP BP5 instruction requires an alternative molecular cause in a different gene, or a non-RASopathy phenotype fully explained by a different causative variant; neither is documented for this case.
  • No BP5 score is available to test the VCEP thresholds: >= (-4) points for Strong, >= (-2) points for Moderate, or >= (-1) point for Supporting.
Still missing
  • An alternative molecular diagnosis and the associated VCEP BP5 point score are unavailable.
Sources
Not applicable · 10· recorded as not applicable Show reasons ▾Hide reasons ▴
PVS1 VCEPNot applicable: c.226G>A is a missense p.(Glu76Lys) variant, whereas the VCEP PVS1 rule is marked not applicable for RASopathy-specific assessment. Details ▾Hide ▴
Reasoning

PVS1 is not applicable under the PTPN11 RASopathy VCEP specification. The assessed variant is NM_002834.5:c.226G>A, a missense change producing p.(Glu76Lys) in exon 3, not a null variant of the types listed in the VCEP's PVS1 summary. The VCEP also explicitly marks PVS1 as not applicable for these RASopathy-specific criteria.

VCEP rule
LOF and/or haploinsufficiency has not been clearly identified as disease mechanisms for these genes relative to the RASopathy spectrum phenotype, therefore in general this rule is not applicable. Note that PTPN11 is currently the only gene with a confirmed association to another non-RASopathy disorder due to LOF alleles. Variants in PTPN11 with predicted LOF should not be evaluated by these RASopathy specific criteria, but should defer to non-adjusted criteria.
Evidence considered
  • VCEP PVS1 entry: applicability is "Not applicable" for the RASopathy-specific criteria.
  • Variant-level assessment: NM_002834.5:c.226G>A; NP_002825.3:p.(Glu76Lys); consequence class missense; exon 3; canonical splice consensus false.
Sources
cspec ↗pvs1_variant_assessment
PM3 VCEPNot applicable: the PTPN11 VCEP explicitly marks PM3 as not applicable. Details ▾Hide ▴
Reasoning

The ClinGen RASopathy Expert Panel PTPN11 Version 2.3 specification explicitly marks PM3 as not applicable; therefore phase, affected-proband observations, and trans/cis observations cannot activate PM3 in this framework.

VCEP rule
Not applicable.
Evidence considered
  • ClinGen RASopathy Expert Panel PTPN11 Version 2.3 CSPEC entry for PM3: applicability is "Not applicable" and instructions are "Not applicable."
Sources
PM4 N/ANot applicable: p.(Glu76Lys) is a missense substitution with no protein-length change, in-frame indel, or stop-loss consequence. Details ▾Hide ▴
Reasoning

PM4 is not applicable because the VCEP limits this criterion to protein length changes caused by in-frame deletions or insertions in a non-repeat region, or to stop-loss variants. NM_002834.5:c.226G>A is a missense variant, p.(Glu76Lys), with no protein-length change and no stop-loss or in-frame indel consequence.

VCEP rule
Protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants. ... No known repetitive areas in gene. Use as described.
Evidence considered
  • VCEP PM4 instruction: "Protein length changes due to in-frame deletions/insertions in a non-repeat region or stop-loss variants."
  • Variant-level assessment: NM_002834.5:c.226G>A is missense and produces NP_002825.3:p.(Glu76Lys).
Sources
cspec ↗pvs1_variant_assessment
PP4 VCEPNot applicable: the PTPN11 VCEP explicitly directs phenotype-specific evidence to PS4 instead of using PP4 independently. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP explicitly marks PP4 as not applicable and directs evaluation to PS4 instead. PP4 is therefore not used independently.

VCEP rule
Not applicable, see PS4.
Evidence considered
  • The VCEP CSPEC entry for PP4 states: Not applicable, see PS4.
Sources
PP5 VCEPNot applicable: the PTPN11 VCEP prohibits PP5 use, regardless of pathogenic classifications reported by reputable sources. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP marks PP5 as not applicable and states that the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. Independent literature evidence is not converted to PP5.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The VCEP CSPEC PP5 entry states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BS3 VCEPNot applicable: the PTPN11 VCEP Version 2.3 explicitly marks BS3 as not applicable. Details ▾Hide ▴
Reasoning

The PTPN11 Version 2.3 VCEP CSPEC entry explicitly marks BS3 as Not Applicable. BS3 therefore cannot be assigned, regardless of the available functional assay data.

VCEP rule
Well-established in vitro or in vivo functional studies show no damaging effect on protein function or splicing.
Evidence considered
  • ClinGen RASopathy Expert Panel Specifications for PTPN11 Version 2.3, BS3 criterion entry: applicability is 'Not Applicable'; the entry states that well-established functional studies showing no damaging effect would otherwise define BS3.
Sources
BP1 N/ANot applicable: BP1 is restricted to named truncating variant types, whereas this variant is the missense substitution p.Glu76Lys. Details ▾Hide ▴
Reasoning

The VCEP's BP1 rule restricts use to truncating variants, specifically nonsense, frameshift, canonical splice-site, initiation-codon, entire-gene, or multi-exon deletions in genes without established loss-of-function correlation. This variant is a missense substitution, NM_002834.5:c.226G>A p.(Glu76Lys), and does not fall within any named BP1 variant type.

VCEP 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. See the supplemental material regarding dosage sensitivity information for each individual gene and potential association to disorders associated with LOF variants.
Evidence considered
  • Variant consequence is missense: NM_002834.5:c.226G>A, NP_002825.3:p.(Glu76Lys).
  • The VCEP BP1 rule names nonsense, frameshift, canonical splice-site, initiation-codon, entire-gene, and multi-exon deletion variants, not missense substitutions.
Sources
BP3 VCEPNot applicable: the VCEP marks BP3 not applicable because no known benign repetitive areas exist in RASopathy genes. Details ▾Hide ▴
Reasoning

BP3 is explicitly marked not applicable by the PTPN11 RASopathy VCEP because there are no known benign repetitive areas in RASopathy genes. The assessed variant is also a missense substitution rather than an in-frame deletion or insertion in a repetitive region.

VCEP rule
No known benign repetitive areas in RASopathy genes.
Evidence considered
  • VCEP BP3 entry: applicability is "Not applicable" and instructions state, "No known benign repetitive areas in RASopathy genes."
Sources
BP6 VCEPNot applicable: the PTPN11 VCEP prohibits BP6 use, regardless of benign classifications reported by reputable sources. Details ▾Hide ▴
Reasoning

The PTPN11 VCEP marks BP6 as not applicable and states that the criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee. Benign reports are not converted to BP6.

VCEP rule
This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Evidence considered
  • The VCEP CSPEC BP6 entry states that this criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee.
Sources
BP7 N/ANot applicable: BP7 covers synonymous, intronic, or non-coding variants, whereas this variant is missense p.(Glu76Lys). Details ▾Hide ▴
Reasoning

The VCEP BP7 rule applies to synonymous variants and also to intronic positions except canonical splice sites or non-coding variants. This variant is a missense coding variant, NP_002825.3:p.(Glu76Lys), so it lies outside BP7's stated scope. BP7 is therefore not_applicable without evaluating splice-prediction or conservation evidence.

VCEP rule
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.
Evidence considered
  • VCEP CSPEC BP7 rule scope includes synonymous variants, intronic positions except canonical splice sites, and non-coding variants; the queried variant is missense p.(Glu76Lys) and is outside that scope.
Sources

Identifiers

Gene
PTPN11
Transcript
NM_002834.5
Coding (HGVS c.)
NM_002834.5:c.226G>A
Protein (HGVS p.)
NP_002825.3:p.(Glu76Lys)
GRCh38
chr12:112450406 G>A
GRCh37
chr12:112888210 G>A
Location and type
Exon 3 · missense
ClinVar
13336
COSMIC
COSV61004889

Gene diagram

Every interpreted variant in PTPN11, mapped onto the exon structure of NM_002834.5. Select a row to find it on the plot.

PTPN11NM_002834.5
Fetching transcript structure from UCSC…
gnomAD v4.1 Allele count data not recorded
gnomAD v2.1 Allele count data not recorded
gnomAD-Canada v1.0 Allele count data not recorded

Statements

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

SpliceAI and Pangolin

SpliceAI acceptor lossat -85 bp
0.021
SpliceAI acceptor gainat -177 bp
0.013
SpliceAI donor lossat +106 bp
0.001
SpliceAI donor gainat -48 bp
0.001
Pangolin splice lossmagnitude shown
-0.008
Pangolin splice gain
0.008

Other predictors

REVEL
0.863
BayesDel
0.484

How the predictions were used

PP3 SupportingVCEPMet (Supporting): REVEL score 0.863 meets the VCEP PP3 missense threshold of >= 0.7. Details ▾Hide ▴
Reasoning

The variant is missense, NP_002825.3:p.(Glu76Lys), so the VCEP's missense PP3 path applies. The governing rule requires REVEL >= 0.7 for missense variants. The available REVEL score is 0.863, which meets that threshold; this is sufficient for PP3 Supporting. The SpliceAI result (maximum delta score 0.021) is not used for PP3 because the missense path is independently satisfied by the named REVEL predictor, and the same splice prediction is not double-counted in another criterion.

VCEP rule
For missense variants: REVEL >= 0.7. For splicing impact, predicted outcome must match disease mechanism.
Evidence considered
  • VCEP CSPEC PP3 rule: for missense variants, REVEL >= 0.7.
  • Local REVEL predictor lookup: NM_002834.5:c.226G>A / NP_002825.3:p.(Glu76Lys), REVEL = 0.863; this exceeds the VCEP threshold of 0.7.
  • Variant consequence is missense: NP_002825.3:p.(Glu76Lys). SpliceAI max delta score = 0.021 was not counted for PP3 because the VCEP missense path names REVEL, and predictions are not double-counted across criteria.
Sources
BP4 VCEPNot met: REVEL score 0.863 exceeds the VCEP BP4 missense threshold of <= 0.3. Details ▾Hide ▴
Reasoning

The variant is missense, so BP4 is within the VCEP rule's stated scope. The governing rule requires REVEL <= 0.3 for missense variants. The available REVEL score is 0.863, which does not meet the <= 0.3 benign-prediction threshold. Therefore BP4 is not met. The low SpliceAI score is not substituted for the VCEP's named missense predictor and is not independently used for BP4.

VCEP rule
For missense variants: REVEL <= 0.3.
Evidence considered
  • VCEP CSPEC BP4 rule: for missense variants, REVEL <= 0.3.
  • Local REVEL predictor lookup: NM_002834.5:c.226G>A / NP_002825.3:p.(Glu76Lys), REVEL = 0.863; this exceeds the VCEP threshold of 0.3, so BP4 is not met.
  • SpliceAI max delta score = 0.021 was not substituted for REVEL because the VCEP BP4 rule for this missense situation names REVEL.
Sources
BP7 N/ANot applicable: BP7 covers synonymous, intronic, or non-coding variants, whereas this variant is missense p.(Glu76Lys). Details ▾Hide ▴
Reasoning

The VCEP BP7 rule applies to synonymous variants and also to intronic positions except canonical splice sites or non-coding variants. This variant is a missense coding variant, NP_002825.3:p.(Glu76Lys), so it lies outside BP7's stated scope. BP7 is therefore not_applicable without evaluating splice-prediction or conservation evidence.

VCEP rule
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.
Evidence considered
  • VCEP CSPEC BP7 rule scope includes synonymous variants, intronic positions except canonical splice sites, and non-coding variants; the queried variant is missense p.(Glu76Lys) and is outside that scope.
Sources

Statement

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.02). REVEL score = 0.863. BayesDel score = 0.484499.

7 paper records listed. 1 cited in the classification.

Cited in the classification

  • Mutations in PTPN11 implicate the SHP-2 phosphatase in leukemogenesis.
    Loh ML et al. · 2004 Mar 15
    The paper explicitly reports the queried PTPN11 c.226G>A substitution as Glu76Lys (E76K) in leukemia specimens and describes functional testing of the same E76K mutant. It confirms the identity of the queried variant but does not provide a different nucleotide change producing p.Glu76Lys.
    → PS3 · supporting Names this variant
    PMID 14644997 ↗
    Source detail
    226 G→A Glu76Lys 3

    Location Table 1, PTPN11 mutations detected in JMML; Table 3, PTPN11 mutations detected in myeloid malignancies; Results, Functional and biochemical studies in Ba/F3 cells

    Context PTPN11 mutation screening in JMML and other myeloid malignancies; retroviral expression of wild-type or mutant SHP-2 in Ba/F3 cells followed by IL-3 withdrawal, survival counting, and ERK/Akt phosphorylation assays.

Other recorded publications

  • Somatic mutations in PTPN11 in juvenile myelomonocytic leukemia, myelodysplastic syndromes and acute myeloid leukemia.
    Tartaglia M et al. · 2003
    No paper-specific finding is recorded.
    PMID 12717436 ↗
  • Functional analysis of PTPN11/SHP-2 mutants identified in Noonan syndrome and ch
    No paper-specific finding is recorded.
    PMID 15834506 ↗
  • PTPN11 (Shp2) mutations in LEOPARD syndrome have dominant negative, not activati
    No paper-specific finding is recorded.
    PMID 16377799 ↗
  • Identification of cryptotanshinone as an inhibitor of oncogenic protein tyrosine
    No paper-specific finding is recorded.
    PMID 23957426 ↗
  • Molecular basis of gain-of-function LEOPARD syndrome-associated SHP2 mutations.
    No paper-specific finding is recorded.
    PMID 24935154 ↗
  • Mutations in PTPN11, encoding the protein tyrosine phosphatase SHP-2, cause Noonan syndrome.
    Tartaglia M et al. · 2001
    No paper-specific finding is recorded.
    PMID 11704759 ↗

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

All source links

Statements for reports

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

gnomAD v4.1

Absent from gnomAD v4.1.

gnomAD v2.1

Absent from gnomAD v2.1.

gnomAD-Canada

Not available in gnomAD-Canada v1.0.

ClinVar

This variant has been reported in ClinVar as Pathogenic (8 clinical laboratories) and as Uncertain significance (1 clinical laboratory). (ClinVarID = 13336)

In silico

SpliceAI predicts no significant splice impact for this variant (max delta score = 0.02). REVEL score = 0.863. BayesDel score = 0.484499.

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; COSV61004889, n = 184 times).

Cancer Hotspots

This variant lies in a statistically significant hotspot.