Why VCF POS different in dbSNP and ClinVar?
Hi,
I simply subset dbSNP with ClinVar using VCF positions via bcftools. I noticed that some of the variants are not present in subset file. I realized that 1 base difference in POS causing that. Also, dbSNP REF and ALT value start 1 base earlier than ClinVar. For example rs1555813914:
(based on GRCh37)
dbSNP
POS: 25304044
REF: ATC
ALT: AAAA
ClinVar
POS: 25304045
REF: TC
ALT: AAA
Why is there such difference?
How annotation tools such as Ensembl VEP can annotate these positions correctly?
Thank you!
• 3,250 views
•
link
written
by
magnolia •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Tool: vareffect — a Rust-based variant effect predictor that replaces VEP
written by LIA Genomics •
-
dbSNP: left-shift vs right-shift of indels
written by Matthew •
-
Bacterial VCF file annotation using snpEff error
written by 1769mkc
-
Filtering VCF based on codon-transcript
written by avelarbio46 •
-
GATK AnnotateVcfWithBamDepth returns zero DP for all variants in VCF
written by ClkElf •
-
bcftools filter by protein prediction
written by storm1907 •
-
Extract gnomad AF for specific position and REF/ALT allele with R
written by Nicolas Rosewick
-
Variant coordinates in dbSNP VCF
written by wjastle •
-
Mpileup BCF/VCF output without non-ref base 'X'?
written by Michi
-
Apply a function over multiple SNPs files
written by l0ka •
Hi magnolia, i recommend you take a step back and read about 3 things:
1) 0-based indexing and 1-based indexing
2) differences between genomic builds
3) correct naming of indels
https://varnomen.hgvs.org/recommendations/DNA/variant/delins/
Thank you for the answer Vincent!
1) I thought VCFs are 1-based. Both files are VCFs so they should have the same POS? Also, if one file is 0-based, then shouldn't almost all positions be unmatched?
2) I downloaded latest releases for both and for GRCh37. Will there be any difference between them? There is no other option. Only GRCh37 and GRCh38.
3) I couldn't figure out what naming indels have to do anything with positions.
I think the two variants are the same, but may not be "normalized" the same (e.g. the dbSNP record in the VCF has an extra A at the start). I am not sure why that would be
Probably one of them is not normalized. Gotta check the sequence I guess. The variants are the same as ClinVar entry is mapped to same rsid.
However, this does not imply that any reference material you might find (i.e. databases of annotations etc.) is 1-based. A lot of resources are not.
Yes, there are thousands and thousands of differences.
No, this is not correct. However, these are certainly the most commonly used.
Please do not take any further action until you understand this. Please see, for example, https://pubmed.ncbi.nlm.nih.gov/25701572/
Thanks a lot for the normalization article! That cleared a lot.
I actually asked differences between dbSNP and ClinVar for GRCh37, not GRCh37 and GRCh38 but apparently, there ARE differences between dbSNP and ClinVar even if they're both for the same reference genome.
Now my question is then do I have to normalize BOTH dbSNP VCF and individual's VCF to annotate correctly? (or in this case both dbSNP and ClinVar)
I guess the way I'd respond is, while you don't "have to" it would be considered best practice.... I have not actually looked for tools that do this recently. If you decide to and need help, let me know.
Thank you so much Vincent. For sure, it's best practice and seems like very important. ClinVar has the normalized alleles. I normalized dbSNP with vt, and they match with ClinVar (though haven't checked ALL positions yet). Seems like it's very crucial for annotation by position and allele.