Five-step scale from benign to pathogenic. This variant is uncertain. Select a step to read what it means.
This variantScenario
BenignPathogenic
Uncertain.The recorded classification is uncertain significance.
In plain language
Gene-level background from the recorded interpretation.
Words with a dotted underline have a short definition. Hover or tap them.
About TP53
TP53 encodes the p53 protein, a critical tumor suppressor that acts as a transcription factor to protect cells from damage. When activated by cellular stress such as DNA damage, p53 triggers responses including DNA repair, cell cycle arrest, and programmed cell death (apoptosis) to prevent the propagation of damaged cells. TP53 is the most frequently mutated gene in human cancers, and loss of its function contributes to tumor development, invasion, drug resistance, and genomic instability. Inherited mutations in TP53 cause Li-Fraumeni syndrome, a rare hereditary condition that greatly increases the risk of developing multiple types of cancer at a young age.
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 TP53 VCEP v2.4. The criteria and strengths shown below come from the saved assessment; this page does not recalculate the classification.
Recorded applied criteria
The applied criteria and their strengths are shown as assessed under the stated framework.
Met (Supporting): gnomAD v4.1 total allele frequency is 1.86e-06 (3/1,613,960 alleles), far below the 0.00003 VCEP ceiling.
Benign criteria applied · 0
No benign criterion marked as applied in the recorded assessment.
Recorded classification: Uncertain significance
Total score 1, from PM2_Supporting alone given gnomAD v4.1 AF 1.86e-06, maps to Uncertain Significance under Rule3 (-1 to 5 points).
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
3 / 1,613,960 alleles
gnomAD v4.1: 3 / 1,613,960 alleles. Recorded AF 1.85878e-06. Recorded homozygote count 0.
gnomAD v2.1
This variant is present in gnomAD v2.1 (AF= 3.98483e-06; MAF= 0.00040%, 1/250952 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26968e-05; MAF= 0.00327%, 1/30584 alleles, homozygotes = 0).
ACMG/AMP criteria under ClinGen TP53 VCEP v2.4, with the data and sources behind each one.
28 criteria with recorded statuses: 1 met · 3 not met · 11 not assessed · 13 not applicable. Open any row for the full reasoning, the rule and the evidence behind it.
All five criteria in this group (PS1, PM1, PM5, PP2, BP1) are amino-acid/residue-level rules whose premises require a missense (protein-level) change. NM_000546.5:c.672+6G>A is an intronic single-nucleotide substitution at the +6 position of the exon 6 donor splice site with predicted protein consequence p.? (VariantValidator maps the position to intron 6, exon '6i'), so none of the criteria are structurally applicable.
Governing framework is the ClinGen TP53 Expert Panel Specifications v2.4 (cspec; framework_mode 'vcep'), which is used in preference to generic ACMG. The CSPEC marks PP2 and BP1 'Not applicable' for TP53 outright, and its PM1/PM5/PS1 rules are restricted to missense variants or amino acid substitutions; the CSPEC PM1 hotspot-codon scope (175, 245, 248, 249, 273, 282) and the empty vcep_materials.json domain_tables for TP53 were checked.
No same-residue comparator, hotspot-codon mapping, or somatic recurrence evidence (COSMIC: no record; cancerhotspots data not present) is relevant because the variant produces no amino acid change; any splicing-mediated effect of this +6 donor-region variant would be evaluated under splicing/PVS1-type codes by other criterion groups, not by codon/residue/domain codes.
Adjudication is grounded in the CSPEC rule text and variant consequence; no pipeline-internal code or unverifiable predictor calibration was used.
Governing framework: ClinGen TP53 Expert Panel ACMG/AMP Specifications v2.4 (cspec doc 135637581, framework_mode=vcep, precedence rank 1, Li-Fraumeni syndrome, autosomal dominant). Generic ACMG/AMP rules are not used because an applicable gene-specific VCEP specification exists.
Variant context: NM_000546.5(TP53):c.672+6G>A is an intronic variant at the +6 position of the exon 6 donor splice site (p.?); ClinVar VCV000854158 classifies it as Uncertain significance from two germline clinical-testing submissions, neither of which asserts de novo origin or provides segregation data.
PS2: not_assessed - no de novo occurrence, parental testing, maternity/paternity confirmation, or proband cancer phenotype is documented in any source in the case bundle, so VCEP de novo points cannot be tallied.
PM6: not_applicable - the governing TP53 VCEP v2.4 explicitly dropped PM6 and uses PS2 exclusively for de novo evidence; generic PM6 is not applied because an applicable specification exists.
PP1: not_assessed - no affected family members are documented to carry the variant and no meiosis/segregation data exists from which cosegregation could be counted; population frequency does not block PP1 (BA1/BS1 not met).
BS4: not_assessed - no affected family member has been tested and shown not to carry the variant, so lack of segregation is neither demonstrated nor refuted.
De novo and segregation criteria for this variant can only be resolved with case-level clinical data (proband phenotype, parental testing, family segregation studies) that is not present in this evidence bundle.
Functional group (PS3/BS3) contributes no evidence: c.672+6G>A is an intronic variant at the +6 position of the exon 6 donor splice site (NM_000546.5:c.672+6G>A; p.?), and the governing ClinGen TP53 VCEP v2.4 operationalizes PS3 and BS3 exclusively through protein-function assays (Kato primary; Giacomelli, Kawaguchi, Kotler, Funk) that are scoped to missense variants and small in-frame deletions. The variant-type scope gate therefore makes both codes not applicable, with high confidence and no human review needed.
No RNA-based or other functional assay of this exact variant exists anywhere in the case record, so there is no evidence that would meet PS3 (damaging functional effect) or BS3 (well-established functional studies showing no damaging effect) even under a generic reading; generic ACMG is not invoked because an applicable VCEP specification exists.
SpliceAI for this variant (max delta 0.135, below the VCEP 0.2 threshold) is in silico and was not counted as functional evidence for either PS3 or BS3; per the VCEP, RNA evidence of aberrant splicing would be applied as PVS1_Variable Weight (RNA) and RNA evidence of normal splicing under BP7_Strong — both outside this group.
Remaining path to functional resolution of this VUS: an RNA splicing assay (patient-derived RNA or minigene) for c.672+6G>A; until such data exist, no functional criterion can be applied.
Phenotype-prevalence group (PS4, PP4, PP5, BP5, BP6) contributes no pathogenic or benign points to the classification of TP53 c.672+6G>A under the governing ClinGen TP53 VCEP v2.4 specification.
PS4 is not met: the VCEP points system yields 0 points because no carrier of the exact variant has a documented phenotype (Revised Chompret/Classic LFS criteria or HER2+ breast cancer <40 years) and no case-control enrichment data exist; the two ClinVar observations are VUS without phenotype assertions, and the candidate case-observation publications do not mention the variant.
PP4 is not assessed: the rule requires documented detection of the variant at VAF 5-35% on multigene panel testing, but no VAF/allele-balance data exists for any observation in the case record.
PP5, BP5, and BP6 are declared Not Applicable by the ClinGen TP53 VCEP v2.4 specification; PP5/BP6 additionally lack any exact-variant ClinVar expert-panel (3-star) Pathogenic/Benign classification that could trigger them under the expert-panel-only policy.
No source's final classification was used to infer any criterion: aggregate ClinVar 'Uncertain significance' and laboratory VUS submissions carry no criterion weight for PP5/BP6 or any other code.
Allelic group (PM3, BP2) contributes no evidence to the classification of TP53 c.672+6G>A: both criteria are formally declared 'Not Applicable' by the governing ClinGen TP53 VCEP specification v2.4, which supersedes generic ACMG/AMP for this gene.
No allelic-configuration data exists in the case bundle regardless of framework: the variant is documented only as a heterozygous germline observation (ClinVar VCV000854158 VUS submissions; gnomAD v2.1 1 allele, 0 homozygotes), with no second TP53 variant, no phase determination, and no trans/cis or co-occurrence information.
PM3 is inapplicable because TP53-related Li-Fraumeni syndrome is an autosomal dominant disorder and PM3 is a recessive-mechanism code; BP2 is inapplicable because the TP53 VCEP removes it from TP53 application and no supporting allelic observation is present.
Population evidence is adjudicated under the ClinGen TP53 VCEP Version 2.4 specification (CSPEC doc 135637581), which supersedes generic ACMG/AMP population thresholds for TP53.
gnomAD v4.1 is the primary population source (per the VCEP instruction to prefer the most recent gnomAD), with gnomAD v2.1 as corroboration; the variant is extremely rare (3/1,613,960 alleles, grpmax FAF 3.65e-06, 0 homozygotes), meeting PM2_Supporting and remaining orders of magnitude below the BA1 (0.001) and BS1 (0.0003) thresholds.
BS2 was not assessed because the VCEP rule requires counts of unrelated females aged >=60 years without cancer from a single source, and no such carrier cohort is documented in the case bundle (ClinVar submissions are VUS with no age/phenotype breakout; gnomAD carriers have no phenotype data).
No literature source in the case bundle contains population-frequency, homozygote-count, or unaffected-carrier cohort data for c.672+6G>A, and none of the extracted papers mention the variant; paper_findings is therefore empty for this group.
No criteria match.
Met · 1
PM2SupportingMet (Supporting): gnomAD v4.1 total allele frequency is 1.86e-06 (3/1,613,960 alleles), far below the 0.00003 VCEP ceiling.
Details ▾Hide ▴
Reasoning
PM2_Supporting is met under the TP53 VCEP (v2.4). gnomAD v4.1 (most recent, preferred per VCEP) reports total AF 1.85878e-06 (3/1,613,960 alleles), well below the 0.00003 ceiling. The only qualifying ancestry group with multiple variant alleles is South Asian with AF 2.19635e-05 (2/91,060 alleles), below the 0.00004 multiple-allele threshold; European (non-Finnish) carries a single allele (AF 8.48e-07). Zero homozygotes are reported, and founder-effect groups (Ashkenazi Jewish, Finnish, Amish, Middle Eastern, Remaining) carry zero alleles. gnomAD v2.1 corroborates (total AF 3.98e-06, 1/250,952). Because total AF is far below 0.00003, the VCEP's CHIP-related VAF>0.35 recalculation paragraph is not triggered.
Rule
Apply at supporting level when allele frequency is <0.00003 (0.003%) in gnomAD or another large sequenced population; if multiple alleles are present within any genetic ancestry group, that group's frequency must be <0.00004 (0.004%); founder-effect groups are ignored.
Evidence considered
The TP53 VCEP Version 2.4 PM2 rule applies at supporting level when the allele frequency is <0.00003 (0.003%) in gnomAD or another large sequenced population; if multiple alleles are present within any genetic ancestry group, that group's frequency must be <0.00004 (0.004%); founder-effect genetic ancestry groups are ignored, and the most recent gnomAD should generally be used.
gnomAD v4.1 reports 3 variant alleles among 1,613,960 total alleles (AF 1.85878e-06, below 0.00003), with 2 alleles in South Asian at AF 2.19635e-05 (2/91,060, below 0.00004) and 1 allele in European (non-Finnish) at AF 8.47551e-07 (1/1,179,870); zero homozygotes and grpmax FAF 3.65e-06.
gnomAD v2.1 corroborates extreme rarity: total AF 3.98483e-06 (1/250,952 alleles), highest ancestry AF 3.26968e-05 (1/30,584 South Asian alleles, below 0.00004), zero homozygotes.
PS4Not met: no proband carrying this variant with a documented phenotype was identified, giving 0 points versus the 1-point supporting threshold.
Details ▾Hide ▴
Reasoning
Governing framework is the ClinGen TP53 Expert Panel Specifications v2.4 (framework_mode=vcep), which applies PS4 by a proband-points system: 0.5 point per proband meeting Revised Chompret criteria, 1 point per proband meeting Classic LFS criteria, and 0.5 point per unrelated proband with HER2+ breast cancer diagnosed <40 years (Supporting = 1-1.5 pts; Moderate = 2-3.5 pts; Strong = 4-7.5 pts; Very Strong >= 8 pts). No proband carrying this exact variant (NM_000546.5:c.672+6G>A) with a documented phenotype is present in the case record: ClinVar VCV000854158 holds only two single-submitter 'Uncertain significance' laboratory submissions (Labcorp/Invitae SCV001223750; Color SCV007438756) with no phenotypic assertions, no expert-panel submissions, and no case-level information; both candidate case-observation publications flagged for PS4 (PMID:17392385 ACS breast-MRI guideline; PMID:25394175 ACMG/NSGC referral guideline) were full-text reviewed and do not mention this variant or report any carrier observations; and no case-control or case-series enrichment study for this exact variant exists (COSMIC: no somatic occurrences). Total PS4 points = 0, below the 1-point Supporting threshold; the ACMG/AMP PS4 note-2 pathway (multiple unrelated patients with the same phenotype in the absence of case-control data) is also not available because no shared LFS phenotype is documented for any carrier. PS4 therefore contributes no points toward pathogenicity.
Rule
TP53 VCEP v2.4 PS4 (points-based): 0.5 pt per proband meeting Revised Chompret; 1 pt per proband meeting Classic LFS; 0.5 pt per proband with HER2+ breast cancer <40 y. PS4_Supporting 1-1.5 pts; PS4_Moderate 2-3.5 pts; PS4 4-7.5 pts; PS4_Very Strong >=8 pts.
Evidence considered
Governing specification (source_registry key 'cspec'): ClinGen TP53 VCEP v2.4 PS4 instructions and points rules serialized in case_summary.json - Revised Chompret proband = 0.5 point, Classic LFS proband = 1 point, HER2+ breast cancer <40 years = 0.5 point (not combined with Chompret/Classic points for breast cancer <31 years); PS4_Supporting = 1-1.5 pts, PS4_Moderate = 2-3.5 pts, PS4 = 4-7.5 pts, PS4_Very Strong >= 8 pts.
ClinVar VCV000854158 (source_registry key 'clinvar'): aggregate 'Uncertain significance', review status 'criteria provided, multiple submitters, no conflicts' (2 stars), expert_panels empty; 2 single-submitter germline laboratory submissions (Labcorp/Invitae SCV001223750; Color SCV007438756), both VUS with no phenotype/case information, so no PS4 points can be derived from any submission.
PMID:17392385 (ACS breast MRI screening guideline) was full-text reviewed as a candidate PS4/PP5 case-observation source (paper_extracts.json): TP53/LFS appears only as gene-level risk context; the exact variant c.672+6G>A is not mentioned (variant_mentioned=false) and no case observations of carriers are reported.
PMID:25394175 (ACMG/NSGC cancer-predisposition referral guideline) was full-text reviewed as a candidate PS4/PP5 case-observation source (paper_extracts.json): LFS referral criteria are described at gene level; the exact variant c.672+6G>A is not mentioned (variant_mentioned=false) and no variant-level case observations are reported.
No case-control study, case series, or multiple-unrelated-proband report documenting enrichment of c.672+6G>A among LFS-spectrum cases exists in the case record; COSMIC search returned no somatic occurrence of this variant, and the variant is essentially absent from population controls (gnomAD v4.1: 3/1,613,960 alleles, AF 1.86e-06) - but with no affected-case phenotype documentation, no enrichment argument can be constructed.
Still missing
No proband-level phenotype or cancer-history data (Revised Chompret/Classic LFS status, HER2+ breast cancer <40 years) is available for any carrier of c.672+6G>A; PS4 points could only be tallied if proband phenotypes were supplied.
BA1Not met: the highest gnomAD v4.1 ancestry frequency is 2.20e-05, over 45-fold below the 0.001 BA1 threshold.
Details ▾Hide ▴
Reasoning
BA1 is not met. The TP53 VCEP (v2.4) requires a filtering allele frequency (FAF) >=0.001 (0.1%) in a non-founder continental genetic ancestry group with >=2,000 alleles tested and at least 2 variant alleles. In gnomAD v4.1 (most recent, preferred per VCEP) the highest observed ancestry frequency is 2.19635e-05 (0.0022%, 2/91,060 South Asian alleles) with grpmax FAF 3.65e-06; both are >45-fold below the 0.001 BA1 cutoff. Total AF is 1.85878e-06 (3/1,613,960 alleles) with zero homozygotes. gnomAD v2.1 corroborates rarity (total AF 3.98e-06, 1/250,952; highest ancestry AF 3.27e-05 in South Asian, 1/30,584), also far below the threshold.
Rule
Filtering allele frequency (FAF) of >= 0.001 or 0.1% in gnomAD continental subpopulations of a single genetic ancestry group, excluding founder-effect groups; the group must have >=2,000 alleles tested and a minimum of 2 alleles present.
Evidence considered
The TP53 VCEP Version 2.4 BA1 rule requires filtering allele frequency (FAF) of >=0.001 or 0.1% in gnomAD continental subpopulations of a single genetic ancestry group (excluding founder-effect groups such as Ashkenazi Jewish, Finnish, Amish, Middle Eastern, and Remaining), with >=2,000 alleles tested and a minimum of 2 alleles present; the most recent gnomAD version should generally be used.
gnomAD v4.1 reports total AF 1.85878e-06 (3/1,613,960 alleles; exome 3/1,461,630, genomes 0), highest observed frequency in South Asian 2.19635e-05 (2/91,060 alleles, 0 homozygotes), European (non-Finnish) 8.47551e-07 (1/1,179,870 alleles), and grpmax FAF 3.65e-06; no qualifying ancestry group approaches the 0.001 BA1 threshold.
gnomAD v2.1 reports total AF 3.98483e-06 (1/250,952 alleles, 0 homozygotes) with the highest population frequency in South Asian 3.26968e-05 (1/30,584 alleles); no population approaches the 0.001 BA1 threshold.
BS1Not met: the highest gnomAD v4.1 ancestry frequency is 2.20e-05, far below the 0.0003 BS1 lower threshold.
Details ▾Hide ▴
Reasoning
BS1 is not met. The TP53 VCEP (v2.4) requires a filtering allele frequency (FAF) >=0.0003 (0.03%) and <0.001 in a non-founder continental genetic ancestry group with >=2,000 alleles tested and at least 2 variant alleles. The highest gnomAD v4.1 ancestry frequency is 2.19635e-05 (South Asian, 2/91,060 alleles) and grpmax FAF is 3.65e-06, both more than an order of magnitude below the 0.0003 lower bound. gnomAD v2.1 shows the same picture (highest ancestry AF 3.27e-05, 1/30,584 South Asian alleles, below the 2-allele minimum for that source). No qualifying population reaches the BS1 lower threshold.
Rule
Filtering allele frequency (FAF) of >= 0.0003 but < 0.001 in gnomAD continental subpopulations of a single genetic ancestry group, excluding founder-effect groups; the group must have >=2,000 alleles tested and a minimum of 2 alleles present.
Evidence considered
The TP53 VCEP Version 2.4 BS1 rule requires filtering allele frequency (FAF) of >=0.0003 but <0.001 in gnomAD continental subpopulations of a single genetic ancestry group (excluding founder-effect groups such as Ashkenazi Jewish, Finnish, Amish, Middle Eastern, and Remaining), with >=2,000 alleles tested and a minimum of 2 alleles present.
gnomAD v4.1 reports the highest observed ancestry frequency as 2.19635e-05 in South Asian (2/91,060 alleles, 0 homozygotes) with grpmax FAF 3.65e-06 and total AF 1.85878e-06 (3/1,613,960 alleles); these are below the 0.0003 BS1 lower threshold.
gnomAD v2.1 reports total AF 3.98483e-06 (1/250,952 alleles) and highest ancestry frequency 3.26968e-05 in South Asian (1/30,584 alleles, i.e., a single allele below the 2-allele minimum); frequencies remain below 0.0003.
PVS1Not assessed: insufficient evidence was available to determine whether this intronic +6 donor variant causes loss of function through a null mechanism.
Details ▾Hide ▴
Reasoning
PVS1 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
PS2Not assessed: no de novo occurrence is documented, and neither ClinVar submission reports parental testing for this variant.
Details ▾Hide ▴
Reasoning
No evidence in this case bundle establishes a de novo occurrence of TP53 c.672+6G>A. ClinVar VCV000854158 contains two germline clinical-testing submissions (SCV001223750 Labcorp Genetics/Invitae; SCV007438756 Color Diagnostics), both classified Uncertain significance with criteria provided by a single submitter and no conflicts; neither submission asserts de novo origin, no parental testing or maternity/paternity confirmation is reported, and the only criterion signal present in either submission is PM2 (population databases) in SCV001223750. No proband phenotype or LFS-associated cancer type is documented anywhere in the bundle, so no PS2 points could be tallied from the VCEP Table of LFS Cancers even if de novo status were established. None of the fetched full-text publications mentions the variant. Under the governing TP53 VCEP v2.4, PS2 de novo points (Supporting = 1, Moderate = 2-3, Strong = 4-7, Very Strong >= 8) therefore cannot be scored, and PS2 is not assessable from available evidence.
Rule
TP53 VCEP v2.4 (cspec doc 135637581), PS2: de novo points tallied based on confirmation of maternity and paternity and the cancer(s) seen in the proband (Table of LFS Cancers and Points for PS2 and PP1 Code Application). PS2_Very Strong >= 8 points; PS2 (Strong) 4-7 points; PS2_Moderate 2-3 points; PS2_Supporting 1 point. Probands that are confirmed constitutional mosaics may be counted as confirmed de novo. The VCEP dropped PM6 and uses PS2 exclusively for de novo evidence.
Evidence considered
ClinGen TP53 VCEP ACMG/AMP Specifications v2.4 (cspec doc 135637581; framework_mode=vcep, precedence rank 1) govern this case. PS2 is Applicable: de novo points are tallied based on whether maternity and paternity have been confirmed and the type of cancer(s) seen in the proband, with strength thresholds PS2_Supporting = 1 point, PS2_Moderate = 2-3 points, PS2 = 4-7 points, PS2_Very Strong >= 8 points; confirmed constitutional mosaics may be counted as confirmed de novo cases. The VCEP states it has 'opted to drop PM6 and use PS2 exclusively for de novo evidence.'
ClinVar VCV000854158 (variation name NM_000546.6(TP53):c.672+6G>A) reports 2 germline clinical-testing submissions classified Uncertain significance ('criteria provided, single submitter' each; 2-star 'criteria provided, multiple submitters, no conflicts' at API level); conditions listed are Li-Fraumeni syndrome / hereditary cancer-predisposing syndrome. No submission contains a de novo assertion, parental testing result, or proband phenotype description; the only evidence signal extracted is PM2 (population) in SCV001223750. ClinVar's Uncertain significance label was not used to infer any criterion.
No proband-level clinical data (cancer history, family history, pedigree, parental genotypes) is present in review_manifest.json, case_summary.json, evidence.json, or prefetch.json for this case, so no PS2 de novo points can be tallied under the VCEP table.
paper_extracts.json entries for all fetched full-text publications (PMID:17392385, PMID:25394175, PMID:17576681, PMID:25741868, PMID:9536098) all report variant_mentioned=false for c.672+6G>A; none reports a de novo case of this variant, and none was cited for PS2.
Still missing
Parental testing results (maternity and paternity confirmation) establishing whether the proband's variant is de novo
Proband phenotype/cancer type needed to assign points per the Table of LFS Cancers for PS2 and PP1 Code Application
Any report or assertion of a de novo occurrence of c.672+6G>A in ClinVar submissions, published literature, or case documentation
PM4Not assessed: insufficient evidence was available to evaluate a change in protein length for this intronic variant.
Details ▾Hide ▴
Reasoning
PM4 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
PP1Not assessed: no segregation data exists; no affected relatives are documented as tested for this variant.
Details ▾Hide ▴
Reasoning
No segregation or meiosis data is available for TP53 c.672+6G>A. The ClinVar record VCV000854158 and its two submissions report no family studies, no affected relatives tested, and no cosegregation observations. None of the fetched full-text publications mentions the variant, and no pedigree information exists in the case bundle. With no individuals documented to both carry the variant and have a relevant LFS-associated cancer, no cosegregation meioses can be counted (PP1_Supporting requires 3-4 meioses, PP1_Moderate 5-6, PP1_Strong >= 7 across > 1 family). PP1 is therefore not assessable. Population allele frequencies (gnomAD v4.1 total AF 1.86e-06) are far below the VCEP BS1 threshold, so PP1 is not precluded by BA1/BS1 - the sole reason for non-assessment is the complete absence of segregation data.
Rule
TP53 VCEP v2.4 (cspec doc 135637581), PP1: PP1_Strong = cosegregation observed in >= 7 meioses across > 1 family; PP1_Moderate = 5-6 meioses in/across 1 or more families; PP1_Supporting = 3-4 meioses. Meioses counted for individuals who both carry the variant and have a relevant LFS-associated cancer (may be counted through unaffected obligate carriers). Do not apply PP1 if the variant meets BA1/BS1.
Evidence considered
ClinGen TP53 VCEP ACMG/AMP Specifications v2.4 (cspec doc 135637581), PP1: meioses are counted for individuals who both carry the variant and have a relevant cancer per the Table of LFS Cancers and Points for PS2 and PP1 Code Application; meioses may be counted through unaffected obligate carriers; PP1_Strong = cosegregation in >= 7 meioses across > 1 family, PP1_Moderate = 5-6 meioses in/across 1 or more families, PP1_Supporting = 3-4 meioses; do not apply PP1 if the variant meets BA1/BS1.
ClinVar VCV000854158 submissions (SCV001223750 Labcorp Genetics/Invitae; SCV007438756 Color Diagnostics, both Uncertain significance, germline, criteria provided by single submitter) contain no segregation or family-testing information for this variant.
gnomAD v2.1 (total AF 3.98e-06, 1/250952 alleles) and gnomAD v4.1 (total AF 1.86e-06, 3/1613960 alleles; grpmax FAF 3.65e-06) document that c.672+6G>A is very rare and does not meet the VCEP BA1/BS1 population thresholds, so PP1 is not blocked by population frequency; non-assessment is due solely to the absence of any segregation data.
paper_extracts.json entries for all fetched full-text publications (PMID:17392385, PMID:25394175, PMID:17576681, PMID:25741868, PMID:9536098) report variant_mentioned=false for c.672+6G>A; none provides cosegregation or family data for this variant.
Still missing
Segregation testing results for affected family members (who carries c.672+6G>A and has an LFS-associated cancer), needed to count meioses
Family pedigree/history describing affected relatives and their LFS-associated cancers
Number of informative meioses (3-4 = Supporting, 5-6 = Moderate, >= 7 across > 1 family = Strong)
PP3Not assessed: insufficient evidence was available from in silico prediction tools to score this criterion.
Details ▾Hide ▴
Reasoning
PP3 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
PP4Not assessed: no variant allele fraction (VAF) data was reported, which the TP53 VCEP PP4 rule requires.
Details ▾Hide ▴
Reasoning
The governing ClinGen TP53 VCEP v2.4 specification makes PP4 applicable but only via detection-based rules: PP4_Supporting requires observation of the variant at variant allele fraction (VAF) 5-35% (once with VAF 5-25% and/or multiple times with VAF >25-35%) and PP4_Moderate requires at least 2 independent observations with VAF 5-25%, in each case on multigene panel testing and reflecting a presumed somatic/low-VAF (e.g., CHIP) origin. The required evidence class - VAF at the time of detection - is not captured anywhere in the case record: the two ClinVar submissions are designated germline-origin VUS with no VAF or allele-balance data, no low-VAF (5-35%) detection of c.672+6G>A is documented in any reviewed source, and the case bundle contains no multigene-panel detection report with allele fraction. Whether any observation would satisfy the VAF 5-35% threshold therefore cannot be confirmed or refuted, so PP4 is not assessed rather than scored as met. PP4's caveats (do not apply when BA1/BS1 is met - not met here given AF ~1.86e-06 in gnomAD v4.1; do not apply if the low-VAF variant was identified in a blood-cancer patient; cannot combine PP4 with PS4/PS2/PP1 in the same individual) would additionally need case-level review if VAF data became available.
Rule
TP53 VCEP v2.4 PP4: PP4_Supporting = observation of the variant with VAF 5-35% (once at VAF 5-25% and/or multiple times at VAF >25-35%) on multigene panel testing; PP4_Moderate = >=2 independent observations with VAF 5-25%.
Evidence considered
Governing specification (source_registry key 'cspec'): ClinGen TP53 VCEP v2.4 PP4 rule text serialized in case_summary.json - PP4_Moderate: 'At least 2 independent observations of the variant with VAF 5-25%'; PP4_Supporting: 'Observation of the variant with VAF 5-35% (i.e., once or multiple times with VAF >25-35% and/or once with VAF 5-25%)'; the instructions state the code assumes a somatic origin of the TP53 variant (low VAF due to CHIP/technical issues/mosaicism), requires detection on multigene panel testing, must not be applied if the variant was identified in a blood-cancer patient or meets BA1/BS1, and cannot be combined with phenotype-based codes (PS4/PS2/PP1) in the same individual.
ClinVar VCV000854158 (source_registry key 'clinvar'): both submissions (Labcorp/Invitae SCV001223750; Color SCV007438756) report germline-origin 'Uncertain significance' without any VAF, allele-balance, or detection-context data; no observation of c.672+6G>A at VAF 5-35% is documented anywhere in the case record.
gnomAD population allele fractions are not informative for PP4: gnomAD v4.1 reports 3/1,613,960 alleles (total AF 1.86e-06), which is far below the BA1/BS1 range, but PP4 concerns the VAF of the variant within the tested individual, not population frequency.
Still missing
Variant allele fraction (VAF) at the time of detection is unavailable for every reported observation of c.672+6G>A; PP4_Supporting needs a documented VAF 5-35% observation (PP4_Moderate: >=2 independent observations at VAF 5-25%) on multigene panel testing, and ClinVar submissions do not carry VAF/allele-balance data.
No information on the clinical context of the two laboratory observations (e.g., whether the variant was detected on multigene panel testing and whether the individual had a blood cancer, which would preclude PP4) is available.
BS2Not assessed: no source documents unaffected carriers past age 60 without cancer, which BS2 requires.
Details ▾Hide ▴
Reasoning
BS2 cannot be assessed from the case-evidence bundle. The TP53 VCEP (v2.4) BS2 rule is not population-frequency based: it requires 2-3 unrelated females who reached at least 60 years of age without cancer from a single source (supporting; 4-7 moderate; >=8 strong), excluding individuals with sarcoma diagnosed at age >=61. No source in the bundle documents any such qualifying carrier cohort: ClinVar lists two germline submissions (Labcorp/Invitae and Color), both classifying the variant as Uncertain significance without expert-panel review and without carrier age/phenotype breakout, and gnomAD v2.1/v4.1 provide no age, sex, or disease-status data (3 heterozygous carriers total, 0 homozygotes).
Rule
At least 2 unrelated females who have reached at least 60 years of age without cancer, all from a single source (supporting); 4-7 for moderate; >=8 for strong; individuals with sarcoma diagnosed at age >=61 years are not counted.
Evidence considered
The TP53 VCEP Version 2.4 BS2 rule requires >=8 (strong), 4-7 (moderate), or 2-3 (supporting) unrelated females who have reached at least 60 years of age without cancer, all from a single source, with individuals diagnosed with sarcoma at age >=61 excluded; the case bundle contains no qualifying single-source cohort.
ClinVar (VariationID 854158) reports 2 germline submissions (Labcorp Genetics/Invitae, SCV001223750; Color Diagnostics, SCV007438756), both 'Uncertain significance' with criteria provided by single submitters and no expert-panel review; no carrier age, sex, or cancer-status data usable for BS2 counting is present.
gnomAD v4.1 (3 heterozygous carriers, 0 homozygotes) and gnomAD v2.1 (1 heterozygous carrier, 0 homozygotes) provide population frequencies only, with no phenotype, age, or single-source clinical ascertainment, so their carriers cannot be counted toward BS2.
Still missing
A single source (single lab, database, etc.) documenting at least 2 unrelated female carriers aged >=60 years without cancer is required for BS2_Supporting; the available evidence provides no such individuals or source-level ascertainment details.
For higher strengths the VCEP requires 4-7 qualifying individuals for BS2_Moderate or >=8 for BS2_Strong, with sarcoma diagnosed at age >=61 excluded from the counts.
BS4Not assessed: no family testing is documented to show affected relatives who do not carry the variant.
Details ▾Hide ▴
Reasoning
No data document lack of segregation for TP53 c.672+6G>A. BS4 (Benign Strong) under the TP53 VCEP requires demonstrated lack of segregation in affected family members - i.e., family members diagnosed with LFS-associated cancers who are found NOT to carry the variant. The evidence bundle contains no testing results for affected relatives, no pedigree, and no non-segregation observations; the ClinVar submissions report no family data, and none of the fetched publications mentions the variant. The absence of any family testing means BS4 cannot be assessed (and equally cannot be refuted) from available evidence.
Rule
TP53 VCEP v2.4 (cspec doc 135637581), BS4 (Benign Strong): lack of segregation in affected family members (i.e., family members diagnosed with LFS-associated cancers as described in the Table of LFS Cancers and Points for PS2 and PP1 Code Application).
Evidence considered
ClinGen TP53 VCEP ACMG/AMP Specifications v2.4 (cspec doc 135637581), BS4 (Benign Strong): 'Lack of segregation in affected family members (i.e. family members diagnosed with LFS-associated cancers as described in Table of LFS Cancers and Points for PS2 and PP1 Code Application).' The generic ACMG caveat about phenocopies of common cancers confounding apparent lack of segregation also applies.
ClinVar VCV000854158 and its two submissions (SCV001223750 Labcorp Genetics/Invitae; SCV007438756 Color Diagnostics, both Uncertain significance, germline, criteria provided by single submitter) provide no data on testing of affected family members and no segregation or non-segregation observations.
paper_extracts.json entries for all fetched full-text publications (PMID:17392385, PMID:25394175, PMID:17576681, PMID:25741868, PMID:9536098) report variant_mentioned=false for c.672+6G>A; none reports family testing or segregation data for this variant.
Still missing
Testing results for affected family members (an affected relative with an LFS-associated cancer found not to carry c.672+6G>A) to establish lack of segregation
Family pedigree documenting affected members and their LFS-associated cancer diagnoses per the Table of LFS Cancers and Points for PS2 and PP1 Code Application
Any non-segregation observation reported in ClinVar submissions or the literature
BP3Not assessed: insufficient evidence was available to evaluate whether this variant lies in a functionally silent repetitive region.
Details ▾Hide ▴
Reasoning
BP3 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
BP4Not assessed: insufficient evidence was available from in silico splicing predictors to score this intronic variant.
Details ▾Hide ▴
Reasoning
BP4 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
BP7Not assessed: no RNA splicing assay data exists, which would be required to demonstrate no splicing aberration.
Details ▾Hide ▴
Reasoning
BP7 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
Not applicable · 13· recorded as not applicableShow reasons ▾Hide reasons ▴PS1N/ANot applicable: this intronic splice-site variant produces no amino acid change (p.?) to compare against an established pathogenic missense.
Details ▾Hide ▴
Reasoning
PS1 requires the variant under evaluation to produce the same amino acid change as a previously established pathogenic missense variant (different nucleotide, same codon change). TP53 VCEP v2.4 additionally restricts PS1 to variants asserted Pathogenic (Strong) or Likely Pathogenic (Moderate) under the VCEP's specifications and requires splicing effects to be excluded. NM_000546.5:c.672+6G>A is an intronic substitution at the +6 position of the exon 6 donor splice site with no amino acid change (NP_000537.3:p.?; VariantValidator maps the position to intron 6, '6i'), so there is no protein-level change to compare with any established pathogenic missense. The +6 position falls within the 9-nt 5' splice-site consensus (PMID:17576681), confirming this acts at the RNA/splicing level, not as an amino acid substitution. No same-amino-acid established pathogenic variant was identified in the case evidence. PS1 is therefore structurally inapplicable.
Rule
TP53 VCEP v2.4 PS1 (applicable): Strong if the variant is asserted Pathogenic, Moderate if Likely Pathogenic, per TP53 VCEP specifications; same amino acid change as an established pathogenic variant regardless of nucleotide change; splicing must be excluded (RNA data or SpliceAI < 0.2).
Evidence considered
Governing framework is the ClinGen TP53 Expert Panel Specifications v2.4 (cspec), framework_mode 'vcep'.
Variant normalized as NM_000546.5:c.672+6G>A; predicted protein consequence NP_000537.3:p.?; VariantValidator reports variant_exonic_positions start/end '6i' (intron 6), confirming an intronic, non-missense variant.
CSPEC PS1 rule text: 'Can be applied to variants asserted as Pathogenic following the TP53 VCEP's specifications' (Strong) and 'asserted as Likely Pathogenic' (Moderate); instructions restrict comparison to variants classified under TP53 VCEP specifications and require no splicing difference (RNA or SpliceAI < 0.2).
paper_extracts for PMID:17576681 state the human 5'ss consensus MAG|GURAGU spans position -3 to +6 relative to the exon-intron junction, so c.672+6G>A falls within the intronic 5' splice-site consensus and is an RNA-level change rather than an amino acid substitution; the paper does not mention this variant or any TP53 residue comparator.
No evidence in the case bundle of any established pathogenic variant producing the same amino acid change as this variant (which produces none).
PS3N/ANot applicable: the TP53 functional assays that define PS3 apply only to missense variants, and this intronic variant has no amino acid change.
Details ▾Hide ▴
Reasoning
Governing framework is the ClinGen TP53 VCEP ACMG/AMP Specifications v2.4 (cspec doc 135637581; framework_mode=vcep). Under this specification PS3 is defined exclusively through protein-function assays — Kato et al. 2003 (PMID 12826609) transactivation as the primary assay, with Giacomelli 2018 (PMID 30224644), Kawaguchi 2005 (PMID 16007150), Kotler 2018 (PMID 29979965), and Funk 2025 (PMID 39774325) as eligible supporting assays — and the 'Flowchart for application of functional rule codes' together with Functional-worksheet.xlsx (Supplementary Table S3) scope these codes to missense variants and small in-frame deletions. NM_000546.5:c.672+6G>A is an intronic variant at the +6 position of the exon 6 donor splice site (variant_exonic_positions 6i; predicted protein p.?): it is neither a missense variant nor an in-frame deletion, so no amino-acid substitution exists to look up in the functional worksheet and none of the eligible protein-level assays can have a result for it. The VCEP v2.4 functional-rule caveat additionally states that protein-level functional codes must not be applied when splicing is the effect under assessment: laboratory/RNA evidence of a splicing aberration would be handled under PVS1_Variable Weight (RNA), and PS3 must not be applied at any weight from protein-level assays if PP3 is applied on the basis of SpliceAI. No RNA-based or other functional assay for this exact variant is present anywhere in the case record (literature_pass.json contains no variant-level functional paper; every extracted full text reports variant_mentioned=false), so PS3 cannot be met on any evidence. Generic ACMG is not invoked because an applicable VCEP specification exists. PS3 is therefore not applicable at the variant-type scope gate of the governing framework, and no alternative RNA-based functional evidence is available to assess.
Rule
TP53 VCEP v2.4 PS3 (protein-function assay rules for missense variants and small in-frame deletions only; splicing/RNA evidence routed to PVS1_Variable Weight (RNA))
Evidence considered
ClinGen TP53 VCEP specifications v2.4 (cspec doc 135637581) PS3 rule: PS3_Strong = Non-functional on Kato et al. data AND LOF by majority of other eligible assays; PS3_Moderate = Partially functional on Kato AND LOF by majority of other available assays; PS3_Supporting = Non-functional on Kato AND abnormal on Kawaguchi regardless of other assays (or small deletions with LOF on the majority of available assays). All strengths hinge on Kato transactivation class (non-functional <=20%, partially functional >20-<=75%, functional >75% activity).
VCEP 'Flowchart for application of functional rule codes' (and index guidance) states PS3/BS3 are applied via protein function for missense variants (left branch) and small deletions (right branch); eligible studies are Kato (PMID 12826609), Funk (PMID 39774325), Giacomelli (PMID 30224644), Kotler (PMID 29979965), Kawaguchi (PMID 16007150), plus other assays after expert interpretation as previously reported (PMID 33300245).
VCEP v2.4 release note and PS3/BS3 instructionsToUse caveat: 'Do not apply PS3 at any weight for missense variants using assays done at the protein level (such as Kato et al. or Giacomelli et al.) if PP3 is applied based on SpliceAI. If there is any laboratory evidence, including RNA-seq data, of splicing aberration for the genetic variant being assessed, for which PVS1_Variable Weight (RNA) might be considered instead. Functional missense codes should not be applied if PVS1 is applied for splicing.'
Variant NM_000546.5:c.672+6G>A is intronic at the +6 position of the exon 6 donor (VariantValidator variant_exonic_positions 6i; hgvs_predicted_protein_consequence NP_000537.3:p.?), not a missense or in-frame deletion, so no protein-level assay result (Kato/Giacomelli/Kawaguchi/Kotler/Funk) exists or can exist for it.
Case literature review found no functional study of this variant: literature_pass.json high-priority papers are ClinVar-attached splicing-statistics/guideline papers with no candidate functional criteria; paper_extracts.json reports variant_mentioned=false for every fetched full text (PMID 17392385, 25394175, 17576681, 25741868, 9536098); no c.672+6G>A row appears in the parsed VCEP PVS1-Splicing worksheet rows or PP3-BP4 codes rows (those list c.672G>C, c.672G>T, c.672+1G>C — different variants).
PMID 25741868 (ACMG/AMP 2015 standards) was consulted to calibrate what counts as functional evidence for a splice-region variant: 'Although splice site variants are predicted to lead to a null effect, confirmation of impact requires functional analysis by either RNA or protein analysis' — i.e., in silico prediction alone is not functional evidence for PS3.
PMID 17576681 (Buratti et al. 2007) was consulted for mechanism context only: the human 5' splice-site consensus (MAG|GURAGU) spans -3 to +6, so the +6 intronic position of c.672+6G>A falls within the consensus, but the paper provides no TP53 variant-level functional data (variant_mentioned=false) and cannot support PS3.
SpliceAI lookup for this variant (max delta score 0.135, DS_DL 0.135 donor-loss signal) is an in silico prediction below the VCEP 0.2 splice-effect threshold; it was not treated as functional assay evidence for PS3.
Still missing
No RNA-based functional assay of c.672+6G>A (patient-derived RNA RT-PCR, minigene, or splice reporter) exists in the case record — the only functional modality that could bear on an intronic variant; under the TP53 VCEP, RNA evidence of a splicing aberration would be applied as PVS1_Variable Weight (RNA) rather than PS3.
No variant-specific entry exists or could exist in the VCEP Functional-worksheet (protein-level assay rows cover amino-acid substitutions and small in-frame deletions only); the worksheet contents were not parsed into the bundle, but an intronic +6 variant has no amino-acid-change key regardless.
PM1N/ANot applicable: PM1 hotspot rules apply to missense changes at specific codons, and this intronic variant alters no amino acid (p.?).
Details ▾Hide ▴
Reasoning
The TP53 VCEP v2.4 PM1 rule applies only to missense variants located within hotspot codons 175, 245, 248, 249, 273, 282 (transcript NM_000546.4) at Moderate, or to germline missense variants with 2-9 (Supporting) or >=10 (Moderate) somatic occurrences for the same amino acid change in cancerhotspots.org. NM_000546.5:c.672+6G>A is an intronic variant (intron 6, +6 of the exon 6 donor) with no amino acid change (p.?), so it is not a missense variant, does not alter any listed hotspot codon, and the somatic-occurrence prong (which is limited to missense changes) cannot apply. vcep_materials.json domain_tables contains no entries for TP53 ({}), so no authoritative VCEP domain table places this position in an approved critical functional domain; the CSPEC hotspot-codon list is the operative PM1 scope. COSMIC has no record of this variant. PM1 is not applicable.
Rule
TP53 VCEP v2.4 PM1 (applicable): Moderate for missense variants within codons 175, 245, 248, 249, 273, 282 (NM_000546.4) or germline missense with >=10 cancerhotspots.org somatic occurrences for the same amino acid change; Supporting for germline missense with 2-9 somatic occurrences.
Evidence considered
CSPEC PM1 rule text: Moderate for 'Missense variants within the following codons using transcript NM_00546.4: 175, 245, 248, 249, 273, 282' or germline missense variants with >=10 cancerhotspots.org somatic occurrences for the same amino acid change; Supporting for germline missense with 2-9 somatic occurrences.
vcep_materials.json domain_tables is empty ({}) for TP53; no gene-specific domain-table entry was available to map the residue, so PM1 scope was taken from the CSPEC rule text itself.
Variant is intronic (c.672+6G>A, intron 6 per VariantValidator) with protein consequence p.?, i.e., not a missense variant and no codon is substituted; residue-level hotspot/codon criteria are therefore inapplicable.
COSMIC search returned no record for TP53 c.672+6G>A (no somatic recurrence evidence); the cancerhotspots.org prong of PM1 additionally requires a missense change, which this variant does not produce.
PM3VCEPNot applicable: PM3 requires a recessive disorder, while TP53-related Li-Fraumeni syndrome is autosomal dominant.
Details ▾Hide ▴
Reasoning
The governing framework is the ClinGen TP53 Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for TP53 Version 2.4 (framework_mode=vcep; cspec found, v2.4), which explicitly declares PM3 applicability as 'Not Applicable'. TP53-related Li-Fraumeni syndrome is an autosomal dominant cancer predisposition disorder, and PM3 is a recessive-mechanism code (pathogenic variant observed in trans with a pathogenic variant in a recessive disorder), so it cannot be applied to this dominant-disorder context. Consistent with the specification, the case bundle contains no second TP53 variant, no biallelic or compound-heterozygous observation, and no phase information: ClinVar VCV000854158 holds germline heterozygous 'Uncertain significance' submissions only (2 laboratories, no co-occurring TP53 variant asserted) and gnomAD v2.1 reports 1/250,952 alleles with 0 homozygotes. PM3 therefore contributes no evidence to this case.
Evidence considered
Governing specification: ClinGen TP53 Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for TP53 Version 2.4 (source_registry key 'cspec'; cspec.genome.network rule set), retrieved for this case and serialized in case_summary.json. The specification's criterion rule list declares PM3 'Not Applicable'.
Direct rule text as serialized in case_summary.json cspec section: {"label": "PM3", "applicability": "Not Applicable"}.
TP53-associated Li-Fraumeni syndrome is an autosomal dominant disorder (ClinVar VCV000854158 conditions: Hereditary cancer-predisposing syndrome, Li-Fraumeni syndrome); PM3 in generic ACMG/AMP (PMID 25741868) applies to recessive disorders where the variant is detected in trans with a pathogenic variant, a mechanism that does not apply here.
Case bundle scan for allelic evidence: no second TP53 variant, no phase determination, no trans/cis observation, and no biallelic observation appear anywhere in case_summary.json, prefetch.json, evidence.json, literature_pass.json, or paper_extracts.json (searched terms: second variant, in trans, biallelic, compound heterozyg, homozygous, phase, co-occurrence - all absent).
ClinVar VCV000854158 (source_registry key 'clinvar'): 2 germline 'Uncertain significance' submissions (Labcorp SCV001223750, Color SCV007438756); neither submission asserts a co-occurring second TP53 variant or provides phase information.
gnomAD v2.1 (source_registry key 'gnomad_v2'): variant 17-7578171-C-T present at 1/250,952 alleles (AF 3.98e-06), 0 homozygotes - single heterozygous population observation only, no biallelic carrier.
PM5N/ANot applicable: this intronic variant produces no missense change at a residue where a different pathogenic missense could be compared.
Details ▾Hide ▴
Reasoning
PM5 applies to a novel missense change at an amino acid residue where a different missense change has previously been determined Pathogenic/Likely Pathogenic under the TP53 VCEP's specifications (Strong: >=2 different pathogenic missense variants at the residue; Moderate: 1 pathogenic; Supporting: 1 likely pathogenic with clinical data demonstrating pathogenicity). NM_000546.5:c.672+6G>A is intronic with no amino acid change (p.?), so it is not a missense variant and there is no residue substitution to compare against any pathogenic comparator. The pm5_candidates artifact confirms the consequence class is not missense (recommendation level 'not_applicable', 0 same-residue candidates seen). PM5 is therefore structurally inapplicable; no same-residue missense comparator evidence exists in the case bundle.
Rule
TP53 VCEP v2.4 PM5 (applicable): Strong for a missense variant at a residue with >=2 different missense variants previously determined pathogenic per TP53 VCEP specs; Moderate for 1 such pathogenic variant; Supporting for 1 likely pathogenic variant with clinical data demonstrating pathogenicity.
Evidence considered
CSPEC PM5 rule text: Missense variant at a residue where >=2 different missense variants previously determined pathogenic per TP53 VCEP specs (Strong), 1 pathogenic (Moderate), or 1 likely pathogenic with clinical data demonstrating pathogenicity (Supporting); instructions require splicing to be ruled out with RNA data or SpliceAI < 0.2 and Grantham comparison of the missense changes.
pm5_candidates summary: pm5_mode 'classic_same_residue_missense', eligible_for_classic_pm5_search false because the variant consequence class (unknown) is not missense; total same-residue candidates seen = 0.
Variant is intronic (c.672+6G>A, intron 6) with protein consequence p.?, so it cannot be a 'novel missense change at an amino acid residue' as PM5 requires.
PM6VCEPNot applicable: the TP53 VCEP v2.4 drops PM6, handling all de novo evidence through PS2 instead.
Details ▾Hide ▴
Reasoning
PM6 is not applicable under the governing gene-specific framework: the ClinGen TP53 VCEP v2.4 specification marks PM6 as 'Not applicable' and, in the PS2 instructions, states the VCEP has 'opted to drop PM6 and use PS2 exclusively for de novo evidence' (all de novo evidence, including assumed de novo, is handled through the PS2 points system). Because an applicable VCEP specification exists for TP53, the generic ACMG/AMP PM6 rule is not used for this variant. Independently of framework applicability, no observation of this variant as an assumed de novo event (e.g., parental testing not performed) is documented in ClinVar VCV000854158, the retrieved literature, or any other source in the case bundle.
VCEP rule
TP53 VCEP v2.4 (cspec doc 135637581), PM6: applicability = Not applicable; instructionsToUse = 'See above for PS2_PM6 combined rule'; the PS2 rule text states the VCEP 'opted to drop PM6 and use PS2 exclusively for de novo evidence.'
Evidence considered
ClinGen TP53 VCEP ACMG/AMP Specifications v2.4 (cspec doc 135637581): PM6 entry has applicability 'Not applicable' with instructionsToUse 'See above for PS2_PM6 combined rule', and the PS2 entry states 'To avoid redundancy and increase consistency, the TP53 VCEP has opted to drop PM6 and use PS2 exclusively for de novo evidence.'
Because the TP53 VCEP (an applicable gene-specific ACMG/AMP specification) explicitly removes PM6, generic ACMG/AMP PM6 (assumed de novo without confirmation of maternity/paternity) is not applied to this variant.
Even under a generic fallback reading, no de novo observation of c.672+6G>A - confirmed or assumed - appears in the ClinVar record or any other source in the evidence bundle, so PM6 would not be met regardless.
PP2VCEPNot applicable: PP2 is removed by the TP53 VCEP and applies only to missense variants regardless.
Details ▾Hide ▴
Reasoning
The TP53 VCEP v2.4 specifications declare PP2 'Not applicable' for TP53 (applicability listing and instructionsToUse both state not applicable), so the gene-level missense-mechanism calibration that PP2 encodes is not part of the governing framework. Independently, PP2 by definition applies to missense variants, and c.672+6G>A is an intronic variant with no amino acid change (p.?). PP2 is not applicable on both grounds.
VCEP rule
TP53 VCEP v2.4 PP2: Not applicable (VCEP does not use PP2 for TP53).
Evidence considered
CSPEC PP2 entry: applicability 'Not applicable'; instructionsToUse 'Not applicable'. The TP53 VCEP does not apply PP2.
Variant is intronic (c.672+6G>A) with protein consequence p.?, i.e., not a missense variant, so the criterion's premise (a missense variant in a gene with low benign missense rate where missense is a common mechanism) cannot be evaluated for this variant.
PP5VCEPNot applicable: PP5 is removed by the TP53 VCEP, and no expert-panel pathogenic classification of this variant exists in ClinVar.
Details ▾Hide ▴
Reasoning
The governing ClinGen TP53 VCEP specification v2.4 (cspec) declares PP5 'Not Applicable' ('This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee'), so PP5 is formally removed from TP53 application under this framework. Independently of the specification, the only permitted trigger for PP5 under this pipeline's policy - an exact-variant ClinVar expert-panel (3-star) classification of Pathogenic/Likely Pathogenic - does not exist for this variant: ClinVar VCV000854158 shows expert_panels empty (no expert-panel submissions), an aggregate 'Uncertain significance' label (2 stars, two single-submitter laboratory submissions), and no pathogenic assertion from any reputable expert source. Ordinary laboratory VUS submissions and the aggregate ClinVar label must not trigger PP5. PP5 therefore contributes no evidence toward pathogenicity.
VCEP rule
Not Applicable for this VCEP - PP5 not for use as recommended by the ClinGen SVI VCEP Review Committee (ClinGen TP53 VCEP v2.4).
Evidence considered
Governing specification (source_registry key 'cspec'): ClinGen TP53 VCEP v2.4 declares PP5 applicability 'Not Applicable for this VCEP' with instruction 'This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee' (serialized in case_summary.json/prefetch.json).
ClinVar VCV000854158 (source_registry key 'clinvar'): expert_panels = {} (no ClinGen or other expert-panel submission exists for this variant); aggregate classification 'Uncertain significance' from 2 single-submitter clinical laboratories (Labcorp/Invitae SCV001223750; Color SCV007438756); no Pathogenic/Likely Pathogenic expert-panel classification of the exact variant is present, so the expert-panel-only PP5 policy trigger is not met.
BS3N/ANot applicable: BS3 is defined by protein-function assays for missense variants, and this intronic variant has no amino acid change.
Details ▾Hide ▴
Reasoning
Under the governing ClinGen TP53 VCEP v2.4 specification, BS3 is defined through protein-function assay results (Kato et al. 2003 primary transactivation data plus Giacomelli/Kawaguchi/Kotler/Funk as eligible assays) and is scoped by the functional-rule flowchart and Functional-worksheet.xlsx to missense variants and small in-frame deletions: BS3_Strong = functional on Kato AND no LOF by the majority of available eligible assays; BS3_Supporting = partially functional on Kato AND no evidence of LOF by all available assays. NM_000546.5:c.672+6G>A is an intronic +6 donor variant (p.?) with no amino-acid substitution, so none of these protein-level assays applies and no worksheet row can exist for it. The only splicing-relevant datum in the case, SpliceAI (max delta 0.135), is an in silico prediction and does not constitute a 'well-established functional study showing no damaging effect' (the original ACMG BS3 definition); under the VCEP, absence of a predicted splice effect is addressed by BP4/BP7 rules (BP7_Strong would require RNA splicing assay data demonstrating no splicing aberration per the BP7 rule's Walker et al. 2023 recommendation), not by BS3. No RNA-based functional assay demonstrating normal splicing of this variant is present in the case record. BS3 therefore cannot be met and is not applicable at the variant-type scope gate of the governing framework; generic ACMG is not invoked because an applicable VCEP specification exists.
Rule
TP53 VCEP v2.4 BS3 (protein-function assay rules for missense variants and small in-frame deletions only; no-splice-effect RNA evidence handled under BP7_Strong)
Evidence considered
ClinGen TP53 VCEP specifications v2.4 (cspec doc 135637581) BS3 rule: BS3_Strong = Functional on Kato et al. data AND no loss of function (LOF) by the majority of available eligible assays; BS3_Supporting = Partially functional on Kato et al. data AND no evidence of LOF by all available assays. Kato functional class thresholds: non-functional <=20%, partially functional >20-<=75%, functional >75% activity; BS3 applies only where a Kato (protein-level) result exists for the amino-acid change.
VCEP 'Flowchart for application of functional rule codes' scopes BS3 to missense variants and small in-frame deletions via protein function; c.672+6G>A is intronic (exon 6 donor +6; p.?) and is outside this scope, so no BS3 worksheet lookup applies.
VCEP v2.4 caveat (functional codes and splicing): protein-level functional codes should not be applied where splicing is the assessed effect; laboratory/RNA evidence of a splicing aberration is handled under PVS1_Variable Weight (RNA), and the BP7_Strong rule requires RNA splicing assay data demonstrating no splicing aberration (per Walker et al., 2023 recommendation cited in the BP7 rule) — BS3 is not the VCEP vehicle for intronic splicing evidence in either direction.
SpliceAI lookup for c.672+6G>A (max delta score 0.135; DS_DL 0.135) is an in silico prediction below the VCEP 0.2 splice-effect threshold and was not treated as a validated functional assay; it cannot satisfy BS3's requirement for well-established functional evidence of no damaging effect (original ACMG BS3 definition in PMID 25741868).
No functional assay of the exact variant exists in the case record: paper_extracts.json reports variant_mentioned=false for all fetched full texts, and none of the eligible TP53 functional assay publications (Kato PMID 12826609, Giacomelli PMID 30224644, Kawaguchi PMID 16007150, Kotler PMID 29979965, Funk PMID 39774325) was retrieved for this case; moreover those assays test amino-acid substitutions and cannot interrogate an intronic +6 change.
PMID 25741868 (ACMG/AMP 2015 standards) was consulted: BS3's original definition is 'well-established in vitro or in vivo functional studies show no damaging effect on protein function or splicing'; the paper also states that for splice-site variants, 'confirmation of impact requires functional analysis by either RNA or protein analysis', reinforcing that absence of a confirmed splice effect (in silico only) does not constitute BS3 evidence.
PMID 17576681 (Buratti et al. 2007) was consulted for mechanism context only: +6 lies within the 9-nt human 5' splice-site consensus but single-nucleotide substitutions at +6 are uncommon activators of cryptic sites; the paper contains no TP53 variant-level functional data (variant_mentioned=false) and does not demonstrate normal splicing of this variant.
Still missing
No RNA assay data demonstrating normal splicing of c.672+6G_A exists in the case record; such data would be evaluated under the TP53 VCEP BP7_Strong rule (RNA splicing assay demonstrates no splicing aberration), not BS3, and SpliceAI alone is insufficient.
No variant-specific entry exists or could exist in the VCEP Functional-worksheet for this intronic variant (protein-level assay rows cover amino-acid substitutions and small in-frame deletions only).
BP1VCEPNot applicable: BP1 is removed by the TP53 VCEP and applies only to missense variants.
Details ▾Hide ▴
Reasoning
The TP53 VCEP v2.4 specifications declare BP1 'Not applicable': 'This rule code does not apply to these genes, as truncating variants account for only a portion of disease causing variants' (TP53 is a missense-dominated mechanism gene). Independently, BP1 by definition applies to missense variants, and c.672+6G>A is an intronic variant with no amino acid change (p.?). BP1 is not applicable on both grounds.
VCEP rule
TP53 VCEP v2.4 BP1: Not applicable (truncating variants account for only a portion of TP53 disease-causing variants).
Evidence considered
CSPEC BP1 entry: applicability 'Not applicable'; instructionsToUse 'This rule code does not apply to these genes, as truncating variants account for only a portion of disease causing variants.'
Variant is intronic (c.672+6G>A) with protein consequence p.?, i.e., not a missense variant, so the criterion's premise (missense variant in a gene where primarily truncating variants cause disease) cannot apply.
BP2VCEPNot applicable: BP2 is removed by the TP53 VCEP, and no second TP53 variant or phase information exists.
Details ▾Hide ▴
Reasoning
The governing ClinGen TP53 VCEP specification v2.4 explicitly declares BP2 applicability as 'Not Applicable', so the generic ACMG BP2 rule (variant observed in trans with a pathogenic variant in a fully dominant disorder, or in cis with a pathogenic variant in any inheritance pattern) is not applied under this framework. Independently of the specification, no allelic-configuration evidence exists in the case bundle: no co-occurring second TP53 variant, no phase determination, and no trans/cis observation are documented (ClinVar VCV000854158 contains only heterozygous germline VUS submissions; gnomAD reports a single heterozygous allele with 0 homozygotes). BP2 therefore contributes no evidence to this case under any framework.
Evidence considered
Governing specification: ClinGen TP53 Expert Panel Specifications to the ACMG/AMP Variant Interpretation Guidelines for TP53 Version 2.4 (source_registry key 'cspec'), retrieved for this case and serialized in case_summary.json. The specification's criterion rule list declares BP2 'Not Applicable'.
Direct rule text as serialized in case_summary.json cspec section: {"label": "BP2", "applicability": "Not Applicable"}.
Generic ACMG/AMP BP2 (PMID 25741868) would require the variant to be observed in trans with a pathogenic variant for a fully dominant disorder (or in cis with a pathogenic variant in any inheritance pattern); the TP53 VCEP supersedes generic ACMG and removes this code from TP53 application.
Case bundle scan for allelic evidence: no second TP53 variant, no phase determination, no trans/cis observation, and no co-occurrence data appear anywhere in case_summary.json, prefetch.json, evidence.json, literature_pass.json, or paper_extracts.json (searched terms: second variant, in trans, biallelic, compound heterozyg, phase, co-occurrence - all absent).
ClinVar VCV000854158 (source_registry key 'clinvar'): 2 germline 'Uncertain significance' submissions (Labcorp SCV001223750, Color SCV007438756); neither asserts a second TP53 variant, phase, or trans/cis configuration.
gnomAD v2.1 (source_registry key 'gnomad_v2'): 1/250,952 alleles (AF 3.98e-06), 0 homozygotes - no biallelic carrier observation that could inform any allelic-configuration argument.
BP5VCEPNot applicable: BP5 is removed by the TP53 VCEP, so no alternate-molecular-basis evidence applies.
Details ▾Hide ▴
Reasoning
The governing ClinGen TP53 Expert Panel specification v2.4 (cspec) declares BP5 applicability 'Not Applicable', removing the generic ACMG/AMP BP5 rule (variant found in a case with an alternate molecular basis for disease) from TP53 application under this framework. The specification provides no TP53-specific alternative for this code, so no alternate-molecular-basis evidence can be weighed for NM_000546.5:c.672+6G>A. BP5 therefore contributes no benign evidence to this case.
VCEP rule
Not Applicable for this VCEP - BP5 declared Not Applicable by the ClinGen TP53 VCEP v2.4 specification.
Generic ACMG/AMP BP5 (PMID 25741868) would require documentation of an alternate molecular basis for disease in a case carrying the variant; the TP53 VCEP supersedes generic ACMG for this gene and formally excludes BP5 from TP53 application.
BP6VCEPNot applicable: BP6 is removed by the TP53 VCEP, and no expert-panel benign classification of this variant exists in ClinVar.
Details ▾Hide ▴
Reasoning
The governing ClinGen TP53 VCEP specification v2.4 (cspec) declares BP6 'Not Applicable' ('This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee'), so BP6 is formally removed from TP53 application under this framework. Independently of the specification, the only permitted trigger for BP6 under this pipeline's policy - an exact-variant ClinVar expert-panel (3-star) classification of Benign/Likely Benign - does not exist for this variant: ClinVar VCV000854158 shows expert_panels empty (no expert-panel submissions) and an aggregate 'Uncertain significance' label from two single-submitter laboratory submissions; no benign assertion from any reputable expert source is present. Ordinary laboratory VUS submissions and the aggregate ClinVar label must not trigger BP6. BP6 therefore contributes no benign evidence to this case.
VCEP rule
Not Applicable for this VCEP - BP6 not for use as recommended by the ClinGen SVI VCEP Review Committee (ClinGen TP53 VCEP v2.4).
Evidence considered
Governing specification (source_registry key 'cspec'): ClinGen TP53 VCEP v2.4 declares BP6 applicability 'Not Applicable for this VCEP' with instruction 'This criterion is not for use as recommended by the ClinGen Sequence Variant Interpretation VCEP Review Committee' (serialized in case_summary.json/prefetch.json).
ClinVar VCV000854158 (source_registry key 'clinvar'): expert_panels = {} (no expert-panel submission exists for this variant); aggregate classification 'Uncertain significance' from 2 single-submitter clinical laboratories (Labcorp/Invitae SCV001223750; Color SCV007438756); no Benign/Likely Benign expert-panel classification of the exact variant is present, so the expert-panel-only BP6 policy trigger is not met.
AF 1.9e-06 · 3 / 1,613,960 alleles · 0 hom · FAF 3.7e-06
South Asian2 / 91,060
2.2e-05
European (non-Finnish)1 / 1,179,870
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 / 250,952 alleles · 0 hom
South Asian1 / 30,584
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.85878e-06; MAF= 0.00019%, 3/1613960 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 2.19635e-05; MAF= 0.00220%, 2/91060 alleles, homozygotes = 0); grpmax FAF= 3.65e-06.
gnomAD v2.1
This variant is present in gnomAD v2.1 (AF= 3.98483e-06; MAF= 0.00040%, 1/250952 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26968e-05; MAF= 0.00327%, 1/30584 alleles, homozygotes = 0).
gnomAD-Canada
Not available in gnomAD-Canada v1.0.
SpliceAI and Pangolin
SpliceAI acceptor lossat +101 bp
0.015
SpliceAI acceptor gainat -150 bp
0.000
SpliceAI donor lossat +1 bp
0.135
SpliceAI donor gainat +6 bp
0.001
Pangolin splice lossmagnitude shown
-0.083
Pangolin splice gain
0.004
Other predictors
REVEL
Not available
BayesDel
Not available
How the predictions were used
PP3Not assessed: insufficient evidence was available from in silico prediction tools to score this criterion.
Details ▾Hide ▴
Reasoning
PP3 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
BP4Not assessed: insufficient evidence was available from in silico splicing predictors to score this intronic variant.
Details ▾Hide ▴
Reasoning
BP4 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
BP7Not assessed: no RNA splicing assay data exists, which would be required to demonstrate no splicing aberration.
Details ▾Hide ▴
Reasoning
BP7 could not be assessed because its agent did not produce valid output.
Still missing
attempt 1: Hermes timed out after 200s and left no usable output_file
attempt 2: Hermes timed out after 200s and left no usable output_file
attempt 3: Hermes timed out after 200s and left no usable output_file
Statement
In silico
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.14).
8 paper records listed. No publication is explicitly linked to an applied criterion in the recorded metadata. None of the listed paper records explicitly indicates that the variant is named.
Recorded publications
Aberrant 5' splice sites in human disease genes: mutation pattern, nucleotide structure and comparison of computational tools that predict their utilization.
Buratti E et al. · 2007
This paper is a compilation of 305 mutation-induced aberrant 5' splice sites (5'ss) in 166 human disease genes. It does not mention the TP53 c.672+6G>A variant or any TP53 amino acid residue. Its only relevance to this group is mechanistic: the human 5'ss consensus (MAG|GURAGU) spans position -3 to +6 relative to the exon-intron junction, establishing that c.672+6G>A falls within the 9-nt 5' splice-site consensus at the intronic +6 position and therefore acts at the RNA/splicing level rather than producing an amino acid substitution. The paper reports that point mutations at positions +3, +4, +6 and -2 each accounted for <3% of single-nucleotide substitutions activating cryptic 5'ss, providing no residue-level pathogenicity information and no comparator missense variant for this variant.
Point mutations at positions +3, +4, +6 and −2 each accounted for <3% of all the single-nucleotide substitutions.
Results, 'Distribution of point mutations activating cryptic and/or creating de novo 5'ss' paragraph (Figure 1)
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.
Richards S et al. · 2015
PMID 25741868 is the ACMG/AMP 2015 standards and guidelines for sequence variant interpretation (consensus methods/guidance paper), not a study of TP53 or of this variant (TP53 c.672+6G>A). It defines PS3 as well-established in vitro or in vivo functional studies supportive of a damaging effect and BS3 as well-established functional studies showing no damaging effect on protein function or splicing, and it gives the general guidance that although splice-site variants are predicted to lead to a null effect, confirmation of impact requires functional analysis by either RNA or protein analysis. It was consulted to calibrate what counts as functional evidence for this intronic donor +6 variant; it provides no variant-level or TP53-specific functional assay data.
For splice site variants, the variant may lead to exon skipping, shortening or inclusion of intronic material, due to alternative donor/acceptor site usage or creation of new sites. Although splice site variants are predicted to lead to a null effect, confirmation of impact requires functional analysis by either RNA or protein analysis.
PVS1 Null variants section, paragraph on splice site variants
Statistical features of human exons and their flanking regions.
American Cancer Society guidelines for breast screening with MRI as an adjunct to mammography.
Saslow D et al. · 2007
This paper is an American Cancer Society guideline on breast MRI screening, not a variant-level study. It does not mention the specific variant c.672+6G>A or any specific TP53 mutation. TP53 is referenced only once, in the genetic-testing context of identifying high-risk women: mutations in TP53 cause Li-Fraumeni syndrome, which confers a high risk of breast cancer (alongside PTEN/Cowden syndrome). Table 1 lists Li-Fraumeni syndrome and first-degree relatives among groups for whom annual MRI screening is recommended based on expert consensus opinion. No functional data, case observations, segregation, or population frequency data relevant to this variant or to TP53 variant pathogenicity are provided - it carries no case observation of a c.672+6G>A carrier that could support PS4 points or any PP5 assertion.
A high risk of breast cancer also occurs with mutations in the TP53 gene (Li-Fraumeni syndrome) and the PTEN gene (Cowden and Bannayan-Riley-Ruvalcaba syndromes).
Background section, 'Identification of Women With a High Risk of Breast Cancer' > 'Genetic Testing' subsection (p. 77)
A practice guideline from the American College of Medical Genetics and Genomics and the National Society of Genetic Counselors: referral indications for cancer predisposition assessment.
Hampel H et al. · 2015
This paper is an ACMG/NSGC practice guideline on referral indications for cancer predisposition assessment, not a variant-level study. It does not mention the specific variant c.672+6G>A or any individual TP53 mutation. Its only TP53 content is general gene-level context in the Li-Fraumeni syndrome (LFS) section: LFS is caused by mutations in the TP53 gene and is characterized by core cancers (breast, brain, adrenocortex, non-Ewing sarcoma) with onset often before age 50 and multiple primary tumors; young age at diagnosis and tumor type are indicators of a TP53 mutation; and the paper lists clinical referral criteria (e.g., two LFS-spectrum tumors in close relatives, breast cancer before age 30, adrenocortical tumor, choroid plexus tumor, childhood sarcoma). No functional assay results, case observations of this variant, segregation data, or population frequency data are reported - it cannot supply a documented carrier phenotype for PS4 scoring or any variant-level assertion for PP5.
Li–Fraumeni syndrome (LFS) is caused by mutations in the TP53 gene and is characterized by the core cancers of breast, brain, adrenocortex, and non-Ewing sarcoma, with onset often before age 50 and multiple primary tumors.
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.85878e-06; MAF= 0.00019%, 3/1613960 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 2.19635e-05; MAF= 0.00220%, 2/91060 alleles, homozygotes = 0); grpmax FAF= 3.65e-06.
gnomAD v2.1
This variant is present in gnomAD v2.1 (AF= 3.98483e-06; MAF= 0.00040%, 1/250952 alleles, homozygotes = 0) and has highest observed frequency in the South Asian population (AF= 3.26968e-05; MAF= 0.00327%, 1/30584 alleles, homozygotes = 0).
gnomAD-Canada
Not available in gnomAD-Canada v1.0.
ClinVar
This variant has been reported in ClinVar as Uncertain significance (2 clinical laboratories). (ClinVarID = 854158)
In silico
SpliceAI predicts no significant splice impact for this variant (max delta score = 0.14).
Somatic
This variant has not previously been reported in somatic cancers (COSMIC).
This variant was interpreted by pipeline 7.2.0.
The current version is 11.0.07.
Re-running queues a fresh interpretation; the result replaces this page when complete.
Re-runs are not free. Blank draws on today's public interpretation allowance; with a code, it uses one of that code's uses.