Nomenclature for alleles of the thiopurine methyltransferase gene
Bibliographic record
Abstract
The drug-metabolizing enzyme thiopurine methyltransferase (TPMT) has become one of the best examples of pharmacogenomics to be translated into routine clinical practice. TPMT metabolizes the thiopurines 6-mercaptopurine, 6-thioguanine, and azathioprine, drugs that are widely used for treatment of acute leukemias, inflammatory bowel diseases, and other disorders of immune regulation. Since the discovery of genetic polymorphisms in the TPMT gene, many sequence variants that cause a decreased enzyme activity have been identified and characterized. Increasingly, to optimize dose, pretreatment determination of TPMT status before commencing thiopurine therapy is now routine in many countries. Novel TPMT sequence variants are currently numbered sequentially using PubMed as a source of information; however, this has caused some problems as exemplified by two instances in which authors' articles appeared on PubMed at the same time, resulting in the same allele numbers given to different polymorphisms. Hence, there is an urgent need to establish an order and consensus to the numbering of known and novel TPMT sequence variants. To address this problem, a TPMT nomenclature committee was formed in 2010, to define the nomenclature and numbering of novel variants for the TPMT gene. A website (http://www.imh.liu.se/tpmtalleles) serves as a platform for this work. Researchers are encouraged to submit novel TPMT alleles to the committee for designation and reservation of unique allele numbers. The committee has decided to renumber two alleles: nucleotide position 106 (G>A) from TPMT*24 to TPMT*30 and position 611 (T>C, rs79901429) from TPMT*28 to TPMT*31. Nomenclature for all other known alleles remains unchanged.
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.004 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.006 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.022 | 0.020 |
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".