MétaCan
Menu
Back to cohort
Record W2128397890 · doi:10.1177/1460458214530137

Use of mobile devices in the emergency department: A scoping review

2014· review· en· W2128397890 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

VenueHealth Informatics Journal · 2014
Typereview
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsMobile deviceEmergency departmentMedical emergencyHealth careQuality (philosophy)Mobile technologyClinical decision support systemMedicineComputer scienceNursingWorld Wide WebPolitical science

Abstract

fetched live from OpenAlex

Electronic health records are increasingly used in regional health authorities, healthcare systems, hospitals, and clinics throughout North America. The emergency department provides care for urgent and critically ill patients. Over the past several years, emergency departments have become more computerized. Tablet computers and Smartphones are increasingly common in daily use. As part of the computerization trend, we have seen the introduction of handheld computers, tablets, and Smartphones into practice as a way of providing health professionals (e.g. physicians, nurses) with access to patient information and decision support in the emergency department. In this article, we present a scoping review and outline the current state of the research using mobile devices in the emergency departments. Our findings suggest that there is very little research evidence that supports the use of these mobile devices, and more research is needed to better understand and optimize the use of mobile devices. Given the prevalence of handheld devices, it is inevitable that more decision support, charting, and other activities will be performed on these devices. These developments have the potential to improve the quality and timeliness of care but should be thoroughly evaluated.

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.014
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Research integrity
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.577
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0140.001
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0040.000
Bibliometrics0.0010.001
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.003
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.248
GPT teacher head0.555
Teacher spread0.307 · 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