Association between Response to Albendazole Treatment and β-Tubulin Genotype Frequencies in Soil-transmitted Helminths
Bibliographic record
Abstract
BACKGROUND: Albendazole (ABZ), a benzimidazole (BZ) anthelmintic (AH), is commonly used for treatment of soil-transmitted helminths (STHs). Its regular use increases the possibility that BZ resistance may develop, which, in veterinary nematodes is caused by single nucleotide polymorphisms (SNPs) in the β-tubulin gene at positions 200, 167 or 198. The relative importance of these SNPs varies among the different parasitic nematodes of animals studied to date, and it is currently unknown whether any of these are influencing BZ efficacy against STHs in humans. We assessed ABZ efficacy and SNP frequencies before and after treatment of Ascaris lumbricoides, Trichuris trichiura and hookworm infections. METHODS: Studies were performed in Haiti, Kenya, and Panama. Stool samples were examined prior to ABZ treatment and two weeks (Haiti), one week (Kenya) and three weeks (Panama) after treatment to determine egg reduction rate (ERR). Eggs were genotyped and frequencies of each SNP assessed. FINDINGS: In T. trichiura, polymorphism was detected at codon 200. Following treatment, there was a significant increase, from 3.1% to 55.3%, of homozygous resistance-type in Haiti, and from 51.3% to 67.8% in Kenya (ERRs were 49.7% and 10.1%, respectively). In A. lumbricoides, a SNP at position 167 was identified at high frequency, both before and after treatment, but ABZ efficacy remained high. In hookworms from Kenya we identified the resistance-associated SNP at position 200 at low frequency before and after treatment while ERR values indicated good drug efficacy. CONCLUSION: Albendazole was effective for A. lumbricoides and hookworms. However, ABZ exerts a selection pressure on the β-tubulin gene at position 200 in T. trichiura, possibly explaining only moderate ABZ efficacy against this parasite. In A. lumbricoides, the codon 167 polymorphism seemed not to affect drug efficacy whilst the polymorphism at codon 200 in hookworms was at such low frequency that conclusions cannot be drawn.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".