Variant evidence review
A label difference is the start of comparison, not the conclusion
Two tools can return different classifications without processing the same identity, evidence snapshot or rule specification. A defensible comparison records inputs and criterion-level outputs before judging concordance.
Agent question
Are these tools evaluating the same allele, transcript, evidence date and ACMG/AMP specification?
Normalize the comparison
Use one public variant representation and record each tool’s normalized output. Compare supported scope, transcript, data versions, applied criteria, strengths and unavailable evidence.
Common sources of discordance
Differences can reflect evidence freshness, gene-specific specifications, transcript context, population thresholds, computational calibration, handling of conflicting assertions or unavailable data.
- Variant and assembly mismatch
- Transcript or consequence mismatch
- Different source versions
- Different gene-specific specifications
- Different criterion strengths or combinations
- Missing or inaccessible evidence
- Different handling of ambiguity and conflicts
Public references
Clinical and data boundary
Folklore Clinical Variant Interpretation MCP is published by Helena Bioinformatics. It accepts public variant-level queries only, not patient, phenotype, family, segregation or private case data. Its results are automated decision support for qualified professional review, not a diagnosis or treatment recommendation.