Skip to content
2000
Volume 20, Issue 35
  • ISSN: 0929-8673
  • E-ISSN: 1875-533X

Abstract

Isoniazid (INH) is one of the most commonly used drugs in treatment of human tuberculosis and the most efficient. Although it has been 60 years since isoniazid was introduced in anti-tubercular therapy and despite the simplicity of its chemical structure (C6H7N3O) with few functional groups, its exact mechanism of action, which could account for its specificity and exceptional potency against Mycobacterium tuberculosis and justify all profiles of INH-resistance, remains elusive and debatable. This complexity can find an explanation in the high reactivity of INH and also in the possibility that multiple targets and pathways could co-exist for this medicinal agent. Indeed, since the discovery of isoniazid’s anti-tubercular potency, several propositions for its mode of action have been reported, including its conversion, by a catalase peroxidase within M. tuberculosis, into an active metabolite able, after reaction with NAD, to inhibit an enzyme (InhA) crucial to M. tuberculosis survival. This represents the most consensual mechanism described to date. Nevertheless, none of the proposed mechanisms considered independently can explain the singular and privileged action of the isoniazid structure on the tubercle bacillus, or all the profiles of resistance. The aim of this paper is to reconsider the literature reporting the different modes of action described for isoniazid in the light of the present and most relevant knowledge, with special attention to understanding the molecular mechanistic aspects of the drug’s action.

Loading

Article metrics loading...

/content/journals/cmc/10.2174/15672050113109990203
2013-11-01
2025-05-05
Loading full text...

Full text loading...

/content/journals/cmc/10.2174/15672050113109990203
Loading
This is a required field
Please enter a valid email address
Approval was a Success
Invalid data
An Error Occurred
Approval was partially successful, following selected items could not be processed due to error
Please enter a valid_number test