MétaCan
Menu
Back to cohort
Record W1533598587 · doi:10.1197/jamia.m2589

Costs Associated with Developing and Implementing a Computerized Clinical Decision Support System for Medication Dosing for Patients with Renal Insufficiency in the Long-term Care Setting

2008· article· en· W1533598587 on OpenAlexaff
Terry S. Field, Paula A. Rochon, Monica Lee, Linda Gavendo, Sujha Subramanian, Sonja Hoover, Joann Baril, Jerry H. Gurwitz

Bibliographic record

VenueJournal of the American Medical Informatics Association · 2008
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsBaycrest Hospital
FundersAgency for Healthcare Research and Quality
KeywordsDosingClinical decision support systemMedicineOrder entryInformaticsDecision support systemMedical emergencyIntensive care medicineEmergency medicineInternal medicineComputer scienceData mining

Abstract

fetched live from OpenAlex

A team of physicians, pharmacists, and informatics professionals developed a CDSS added to a commercial electronic medical record system to provide prescribers with patient-specific maximum dosing recommendations based on renal function. We tracked the time spent by team members and used US national averages of relevant hourly wages to estimate costs. The team required 924.5 hours and $48,668.57 in estimated costs to develop 94 alerts for 62 drugs. The most time intensive phase of the project was preparing the contents of the CDSS (482.25 hours, $27,455.61). Physicians were the team members with the highest time commitment (414.25 hours, $25,902.04). Estimates under alternative scenarios found lower total cost estimates with the existence of a valid renal dosing database ($34,200.71) or an existing decision support add-on for renal dosing ($23,694.51). Development of a CDSS for a commercial computerized prescriber order entry system requires extensive commitment of personnel, particularly among clinical staff.

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 imitation

Not 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.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.030
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.019
Threshold uncertainty score0.044

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.030
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0030.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.031
GPT teacher head0.416
Teacher spread0.385 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

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".

Quick stats

Citations59
Published2008
Admission routes1
Has abstractyes

Explore more

Same venueJournal of the American Medical Informatics AssociationSame topicElectronic Health Records SystemsFrench-language works237,207