Hepatic Safety of Itraconazole
Bibliographic record
Abstract
BACKGROUND: As the use of the newer oral antifungal agents for the treatment of superficial fungal infections becomes more widespread, the issue of safety surrounding their use is becoming an increasingly important consideration. Itraconazole is effective and well tolerated, with most side effects being minor and reversible. The most common adverse events are gastrointestinal upset, headache, and transient skin reaction. There have also been rare reports of hepatitis. OBJECTIVE: To assess the hepatic safety of pulse and continuous itraconazole in the treatment of onychomycosis. METHODS: An analysis was performed on all itraconazole clinical trials sponsored by Janssen Research Foundation in the treatment of onychomycosis, where there was an assessment of laboratory safety. A review of the published literature was also undertaken to assess the hepatic safety of itraconazole in common practice. RESULTS: The data indicate that itraconazole pulse treatment is safe, with no significant differences in the number of code 4 abnormalities (baseline value is in the normal range and at least two values, or the last testing in the observation period, exceed twice the upper limit of normal) in the liver function parameters studied: alanine aminotransferase (ALT), aspartate aminotransferase (AST), alkaline phosphatase, and total bilirubin. The incidence of all the code 4 abnormalities was below 2%. In the literature there are reports of symptomatic hepatitis with itraconazole continuous therapy but no published report of symptomatic hepatotoxicity using the pulse regimen. CONCLUSIONS: Itraconazole pulse therapy for onychomycosis appears to be safe, especially from the perspective of potential liver damage. In the itraconazole package insert liver function tests are recommended for patients receiving continuous itraconazole for periods of time exceeding 1 month. There is no such monitoring requirement for the pulse regimen unless the patient has a history of underlying hepatic disease, the liver function tests are abnormal at baseline, or at any time that there is the development of signs or symptoms suggestive of liver dysfunction.
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.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".