Drug use evaluation of moxifloxacin (avelox) using a hand-held electronic device at a canadian teaching hospital.
Bibliographic record
Abstract
BACKGROUND: The use of moxifloxacin (Avelox) has increased at Vancouver General Hospital since its introduction onto the formulary in 2002. It is unclear, however, whether the use of the drug is optimal according to its indication. Hand-held electronic devices, such as personal digital assistants (PDAs), are novel tools that can be used during routine patient care to collect data for drug use evaluation (DUE) reviews. OBJECTIVE: We hypothesized that moxifloxacin was over-utilized and that opportunities existed to optimize its use. This study was designed to characterize moxifloxacin use in concordance with evidence-based assessment criteria. The feasibility of using a PDA device as a data-collection tool was also evaluated. DESIGN: An observational DUE was conducted over a 4-week period (from February 17 to March 16, 2007) at Vancouver General Hospital, a 955-bed tertiary care hospital. Inpatients who received at least one dose of moxifloxacin were enrolled. Evidence-based assessment criteria were developed to evaluate the appropriateness of moxifloxacin use, and a PDA database was developed for data collection. The primary endpoint was the proportion of moxifloxacin use for approved first-line indications. RESULTS: A total of 132 patients were included. Eighty-nine patients (67%) received moxifloxacin for first-line indications, including community-acquired pneumonia (57%) and acute exacerbation of chronic bronchitis (10%). Forty-three patients (33%) had alternative indications, primarily hospital-acquired pneumonia (25%). In 129 evaluable patients, approximately half (51%) of the clinical outcomes were successful; 37% were indeterminate; and 12% were failures. General medicine and respiratory service clinicians prescribed moxifloxacin more appropriately compared with surgical service personnel. Most of the pharmacists supported the use of PDAs as DUE data-collection tools. CONCLUSION: Overall, moxifloxacin utilization at Vancouver General Hospital was appropriate according to evidence-based assessment criteria. Additional opportunities to improve its use exist through health care staff education. PDAs are ideal data-collection tools for DUEs, as they can be conveniently used during routine patient care.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| 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.000 | 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 teacher head, 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".