Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
BMC Genomics. 2008 May 28;9:249. doi: 10.1186/1471-2164-9-249.

Stabilization of the genome of the mismatch repair deficient Mycobacterium tuberculosis by context-dependent codon choice.

Author information

  • 1Institut für Medizinische Mikrobiologie, Universität Zürich, Gloriastrasse 30/32, CH-8006 Zürich, Switzerland. rwanner@immv.uzh.ch

Abstract

BACKGROUND:

The rate at which a stretch of DNA mutates is determined by the cellular systems for DNA replication and repair, and by the nucleotide sequence of the stretch itself. One sequence feature with a particularly strong influence on the mutation rate are nucleotide repeats. Some microbial pathogens use nucleotide repeats in their genome to stochastically vary phenotypic traits and thereby evade host defense. However, such unstable sequences also come at a cost, as mutations are often deleterious. Here, we analyzed how these opposing forces shaped genome stability in the human pathogen Mycobacterium tuberculosis. M. tuberculosis lacks a mismatch repair system, and this renders nucleotide repeats particularly unstable.

RESULTS:

We found that proteins of M. tuberculosis are encoded by using codons in a context-dependent manner that prevents the emergence of nucleotide repeats. This context-dependent codon choice leads to a strong decrease in the estimated frame-shift mutation rate and thus to an increase in genome stability.

CONCLUSION:

These results indicate that a context-specific codon choice can partially compensate for the lack of a mismatch repair system, and helps to maintain genome integrity in this pathogen.

PMID:
18507851
[PubMed - indexed for MEDLINE]
PMCID:
PMC2430213
Free PMC Article

Images from this publication.See all images (4)Free text

Figure 1
Figure 2
Figure 3
Figure 4
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for BioMed Central Icon for PubMed Central
    Loading ...
    Write to the Help Desk