Serum asunaprevir concentrations showing correlation with the extent of liver fibrosis as a factor inducing liver injuries in patients with genotype-1b hepatitis C virus receiving daclatasvir plus asunaprevir therapy
Bibliographic record
Abstract
AIMS: Liver injury can occur during antiviral therapies with direct-acting antivirals (DAAs), potentially necessitating discontinuation of the therapies, with consequent worsening of the sustained viral response (SVR) rates, in patients with hepatitis C virus (HCV). To clarify the mechanisms involved in serum transaminase level elevation, we performed a retrospective evaluation of the serum concentrations of daclatasvir and asunaprevir, both classified as DAAs, in patients receiving treatment with a combination of the two drugs. METHODS: Subjects were 278 Japanese patients with genotype-1b HCV who received daclatasvir plus asunaprevir therapy for more than 4 weeks. Serum concentrations of both the DAAs were measured at 4 weeks after the initiation of therapy. RESULT: Liver injuries including serum AST and/or ALT level elevation to 150 U/L or over were found in 34 patients (12.2%). Multivariate logistic regression analysis identified serum asunaprevir concentrations as being significantly associated with developing liver injury, with an odds ratio of 1.046 (95% confidence interval 1.011-1.082, p<0.05). Serum asunaprevir concentrations showed correlation with the extent of liver fibrosis, estimated by peripheral platelets counts and serum albumin levels and baseline and FIB4 index and serum Mac-2 binding protein glycosylation isomer (M2BPGi) levels at 4 weeks of the therapy; the concentrations were significantly higher among patients showing 3.0 or more of M2BPGi levels than among those with the levels less than 3.0; on the other hand, no such correlation/difference was found in serum daclatasvir concentrations. CONCLUSION: High serum concentrations of serum asunaprevir, which were associated with the extent of liver fibrosis, appear to provoke the occurrence of liver injury in patients with genotype-1b HCV receiving combined daclatasvir plus asunaprevir therapy.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| 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.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".