ColistinDose, a Mobile App for Determining Intravenous Dosage Regimens of Colistimethate in Critically Ill Adult Patients: Clinician-Centered Design and Development Study
Bibliographic record
Abstract
BACKGROUND: Determining a suitable dose of intravenous colistimethate is challenging because of complicated pharmacokinetics, confusing terminology, and the potential for renal toxicity. Only recently have reliable pharmacokinetic/pharmacodynamic data and dosing recommendations for intravenous colistimethate become available. OBJECTIVE: The aim of this work was to develop a clinician-friendly, easy-to-use mobile app incorporating up-to-date dosing recommendations for intravenous colistimethate in critically ill adult patients. METHODS: Swift programming language and common libraries were used for the development of an app, ColistinDose, on the iPhone operating system (iOS; Apple Inc). The compatibility among different iOS versions and mobile devices was validated. Dosing calculations were based on equations developed in our recent population pharmacokinetic study. Recommended doses generated by the app were validated by comparison against doses calculated manually using the appropriate equations. RESULTS: ColistinDose provides 3 major functionalities, namely (1) calculation of a loading dose, (2) calculation of a daily dose based on the renal function of the patient (including differing types of renal replacement therapies), and (3) retrieval of historical calculation results. It is freely available at the Apple App Store for iOS (version 9 and above). Calculated doses accurately reflected doses recommended in patients with varying degrees of renal function based on the published equations. ColistinDose performs calculations on a local mobile device (iPhone or iPad) without the need for an internet connection. CONCLUSIONS: With its user-friendly interface, ColistinDose provides an accurate and easy-to-use tool for clinicians to calculate dosage regimens of intravenous colistimethate in critically ill patients with varying degrees of renal function. It has significant potential to avoid the prescribing errors and patient safety issues that currently confound the clinical use of colistimethate, thereby optimizing patient treatment.
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.008 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 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".