MétaCan
Menu
Back to cohort
Record W2410999545 · doi:10.7573/dic.212287

Effect of variations in treatment regimen and liver cirrhosis on exposure to benzodiazepines during treatment of alcohol withdrawal syndrome

2015· article· en· W2410999545 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueDrugs in Context · 2015
Typearticle
Languageen
FieldMedicine
TopicAlcoholism and Thiamine Deficiency
Canadian institutionsUniversity of British ColumbiaUniversity of Saskatchewan
Fundersnot available
KeywordsMedicineLorazepamDiazepamCirrhosisAlcohol withdrawal syndromeRegimenDosingLiver diseaseAlcoholic liver diseaseDrugAnesthesiaAlcoholPharmacologyInternal medicine

Abstract

fetched live from OpenAlex

PURPOSE: Benzodiazepines (BDZs) are the drugs of choice to prevent the symptoms of alcohol withdrawal syndrome (AWS). Various treatment protocols are published and have been shown to be effective in both office-managed and facility-managed treatment of AWS. The aim of this scientific commentary is to demonstrate the differences in the expected exposure to BDZs during AWS treatment using different treatment regimens available in the literature, in patients with or without alcoholic liver cirrhosis. METHODS: Diazepam and lorazepam AWS protocols were examined and reviewed in the literature, and blood plasma levels were examined and compared, respectively. RESULTS: Considerable variation in the blood levels with the different dosing schedules was found. Because the drugs are metabolized differently, we have also shown that liver disease affects the blood levels of diazepam, but not of lorazepam. CONCLUSIONS: Differences in treatment regimens, the choice of BDZ, as well as the presence of liver cirrhosis can substantially alter the exposure of patients to drugs used for AWS treatment. Outpatient treatment of AWS has been shown to be relatively safe and effective for the treatment of AWS but patients should be carefully monitored.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.097
Threshold uncertainty score0.547

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.021
GPT teacher head0.291
Teacher spread0.270 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it