MétaCan
Menu
Back to cohort
Record W2324973240 · doi:10.1177/2327857914031007

Identification of EMR Hardware and Space Design Requirements using Human Factors Analyses

2014· article· en· W2324973240 on OpenAlex
Catherine Campbell, C Kramer, Shelley Kelsey, W. James King

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

VenueProceedings of the International Symposium on Human Factors and Ergonomics in Health Care · 2014
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsUniversity of OttawaChildren's Hospital of Eastern Ontario
Fundersnot available
KeywordsWorkflowUsabilityDocumentationIdentification (biology)Task (project management)Sociotechnical systemComputer scienceProcess (computing)Process managementKnowledge managementSystems engineeringEngineeringHuman–computer interactionDatabase

Abstract

fetched live from OpenAlex

Electronic Medical Records (EMR) are being implemented globally in the hope of improving patient care, provider coordination, documentation accuracy, and information availability. Numerous factors impact successful EMR implementation including usability, accessibility and unique characteristics of the sociotechnical system within which it will be used. This paper describes the application of human factors methods to support effective EMR implementation at one pediatric hospital. The focus is on the problem of hardware selection and placement – a topic that has not received much attention in the literature to date. The requirements gathering process for two outpatient clinics included a task and gap analysis of current clinic workflows that led to the identification of specific hardware and design recommendations supporting future EMR workflows. Lessons learned post-implementation and requirements associated with hospital wide practices were extrapolated to generate guiding principles that apply to EMR implementation in other outpatient clinics.

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.001
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.031
Threshold uncertainty score0.709

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.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.160
GPT teacher head0.448
Teacher spread0.289 · 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