Journal article icon

Journal article

Whole-genome comparative analysis of two carbapenem-resistant ST-258 klebsiella pneumoniae strains isolated during a North-Eastern Ohio outbreak: differences within the high heterogeneity zones

Abstract:

Klebsiella pneumoniae has become one of the most dangerous causative agents of hospital infections due to the acquisition of resistance to carbapenems, one of the last resort families of antibiotics. Resistance is usually mediated by carbapenemases coded for by different classes of genes. A prolonged outbreak of carbapenem-resistant K. pneumoniae infections has been recently described in northeastern Ohio. Most strains isolated from patients during this outbreak belong to MLST sequence type 258 (ST258). To understand more about this outbreak two isolates (strains 140 and 677), one of them responsible for a fatal infection, were selected for genome comparison analyses. Whole genome map and sequence comparisons demonstrated that both strains are highly related showing 99% average nucleotide identity. However, the genomes differ at the so-called high heterogeneity zone (HHZ) and other minor regions. This study identifies the potential value of the HHZ as a potential marker for K. pneumoniae clinical and epidemiological studies.

Publication status:
Published
Peer review status:
Peer reviewed

Actions

Access Document

Publisher copy:
10.1093/gbe/evw135

Authors

More by this author
Role:
Author
ORCID:
0000-0002-9176-924X
More by this author
Role:
Author
ORCID:
0000-0002-3972-9208



Publisher:
Oxford University Press
Journal:
Genome Biology and Evolution More from this journal
Volume:
8
Issue:
6
Pages:
2036–2043
Publication date:
2016-06-11
Acceptance date:
2016-05-31
DOI:
EISSN:
1759-6653
ISSN:
1759-6653
Pmid:
27289094


Language:
English
Keywords:
Pubs id:
pubs:627639
UUID:
uuid:1b3f69d6-7233-4bda-9162-eb43f62af5bf
Local pid:
pubs:627639
Source identifiers:
627639
Deposit date:
2019-07-03
ARK identifier:

Terms of use


Views and Downloads






If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP