43
Views
1
CrossRef citations to date
0
Altmetric
Original

1A and 3D gene sequences of coxsackievirus B3 strain CC: Variation and phylogenetic analysis

Full Length Research Paper

, , , &
Pages 8-12 | Received 20 Sep 2006, Accepted 06 Nov 2006, Published online: 11 Jul 2009
 

Abstract

Coxsackievirus B3 (CVB3) was thought to be the most common causative agent of life-threatening viral myocarditis. Coxsackievirus B3 strain CC (CVB3-CC) was isolated in China; however, no sequence data are available. The 1A and 3D regions of CVB3-CC were sequenced and phylogenetic analysis was done with reference to ten other CVB3 strains and all 36 prototype strains of human enterovirus B (HEV-B). Sequence analysis showed that the 1A gene region of CVB3-CC consisted of 207 nucleotides, encoding 69 amino acids; and the 3D gene region was comprised of 1386 nucleotides, encoding 462 amino acids. Variation analysis showed that the 3D gene of CVB3 strain CC varied the least among the two regions. Phylogenetic tree analysis of the 1A and 3D regions indicated that CVB3-CC clustered together with CVB3 Nancy strain suggesting that there may be a close evolutionary relationship between the two strains. Incongruity was observed between the non-structural protein gene and the structural protein gene trees, according to the topological structure, indicating that recombination was occurred among these strains.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.