mutation found in RNA seq data and not in DNA data
2
0
Entering edit mode
2.8 years ago
pingu77 ▴ 20

Hi!

I have a very basic question about cancer. What does it mean from a cancer biology perspective, to have a mutation at the RNA level and not the DNA level? If I have both types of data and I found a mutation just in the RNA seq data and not in the DNA data, what does that imply?

Thanks a lot!

dna rna cancer mutation • 2.0k views
ADD COMMENT
0
Entering edit mode

I found a mutation just in the RNA seq data and not in the DNA data

What is the level of support do you have for that observation in terms of coverage?

ADD REPLY
0
Entering edit mode

Hi GenoMax, thanks for your question! it is low, I have in total 20 reads and the mutation is just in 2 of them.

ADD REPLY
1
Entering edit mode

That would support a sequencing error as a likely cause of mutation, although it is possible that there is a small fraction of mutations in the pool that are caused by RNA polymerase.

ADD REPLY
3
Entering edit mode
2.8 years ago
Mensur Dlakic ★ 28k

This is not a bioinformatics question, but there will likely be some interest in discussing it.

Most likely the mutation means nothing in terms of cancer.

Assuming that it is real and not an artifact of sequencing, a mutation in the coding region can be synonymous, and therefore silent. It can also be a part of RNA editing (C->U or A->I), which is typically regulated and therefore normal. Finally, the mutation may be introduced during sequencing, which is rare but still possible. All of the examples above either would not lead to mutations at a protein level, or those would be desired mutations as part of RNA editing.

I guess it is possible that RNA polymerase would make a mutation in enough molecules for it to be captured by sequencing, but that seems unlikely.

ADD COMMENT
0
Entering edit mode

thanks a lot for you fantastic explanation!

ADD REPLY
0
Entering edit mode

Also a mutation in both data (DNA and RNAseq) is unlikely to lead to mutations at a protein level, right? I guess the most interesting case is when you have a mutation at the DNA level and not at the RNAseq level.

ADD REPLY
1
Entering edit mode

A mutation in coding DNA (and subsequently captured by RNA-seq) could lead to protein mutation with a good probability. Mutations in the third codon position are silent for 7 out of 20 amino-acids, and sometimes even mutation at the first codon position are silent. Still, that leaves plenty of combinations where a mutation in coding DNA would change protein sequence, so I wouldn't call it unlikely.

ADD REPLY
0
Entering edit mode

Thanks a lot again! I think that it is possible to have mutation in coding DNA that are not capture by RNA-seq. For example, if you have a mutation at the exon end (coding DNA, e.g. last three nucleotide of the exon), it could affect the splicing process and if the exon is skipped, you shouldn't be able to capture that mutation in RNAseq. Right?

ADD REPLY
1
Entering edit mode

It is possible. Still, the fact that an exon is skipped would be captured, and a mutation would be indirectly responsible for it.

ADD REPLY
0
Entering edit mode

Would it be possible to have epigenetic marker on the RNA that would disturb the sequencing?

ADD REPLY
0
Entering edit mode

Hi Raphael, thanks for your question.. I have no idea.. Why did you ask it? What could you deduce from it? Thanks!

ADD REPLY
1
Entering edit mode

I know that RNA methylation and other epigenetic modifications have been observed. But my knowledge of this fields stops there and I don't know if it may impact sequencing.

ADD REPLY
0
Entering edit mode
2.8 years ago
Raman2 ▴ 30

RNA expression is tissue specific. Are you looking comparing RNA and DNA data from the same tissue sequenced around the same time?

ADD COMMENT
0
Entering edit mode

Hi raman2, thanks for your reply. The answer is yes for both of your questions :)

ADD REPLY

Login before adding your answer.

Traffic: 2457 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6