z-logo
Premium
The Cytotoxin‐Hemolysin Genes of Human and Eel Pathogenic Vibrio vulnificus Strains: Comparison of Nucleotide Sequences and Application to the Genetic Grouping
Author(s) -
Senoh Mitsutoshi,
Miyoshi Shinichi,
Okamoto Keinosuke,
Fouz Belen,
Amaro Carmen,
Shinoda Sumio
Publication year - 2005
Publication title -
microbiology and immunology
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.664
H-Index - 70
eISSN - 1348-0421
pISSN - 0385-5600
DOI - 10.1111/j.1348-0421.2005.tb03756.x
Subject(s) - biology , vibrio vulnificus , hemolysin , vibrio , gene , microbiology and biotechnology , vibrionaceae , genetics , vibrio infections , vibrio parahaemolyticus , virulence , bacteria
Vibrio vulnificus can be divided into two groups on the basis of pathogenesis. Group 1 is pathogenic only to humans, whereas group 2 is pathogenic to eels and occasionally to humans. Although both groups produce a 50‐kDa cytotoxin‐hemolysin ( V. vulnificus hemolysin; VVH), the toxins are different. In the present study, the nucleotide sequence of the toxin gene ( vvhA ) of strain CDC B3547 (a group 2 strain) was determined, and the deduced amino acid sequence was compared to that of strain L‐180 (a group 1 strain). The nucleotide sequence of vvhA of strain CDC B3547 was about 96% identical with that of strain L‐180, which results in a difference of 3 amino acid residues in the C‐terminal lectin domain of VVH. Nevertheless, two primer sets for polymerase chain reaction could be designed to differentiate the toxin gene of each strain. When 27 V. vulnificus clinical isolates were tested, group 1 strains (9 strains) were shown to react only to the primers designed for vvhA of strain L‐180; whereas, the gene of group 2 strains (18 strains) could be amplified with the primers for vvhA of strain CDC B3547. These findings may lead to development of a novel genetic grouping system related to the virulence potential or to the host range.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here