MétaCan
Menu
Back to cohort
Record W21830674 · doi:10.5220/0002746003240329

DESIGNING A PHYSICIAN-FRIENDLY INTERFACE FOR AN ELECTRONIC MEDICAL RECORD SYSTEM

2010· article· en· W21830674 on OpenAlexaff
Donald C. Craig, Gerard Farrell

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsMemorial University of Newfoundland
Fundersnot available
KeywordsWorkflowUsabilityInterface (matter)Electronic medical recordElectronic health recordComputer scienceMedical recordHealth careUser interfaceUser FriendlyWorld Wide WebMedicineInternet privacyDatabaseHuman–computer interaction

Abstract

fetched live from OpenAlex

An Electronic Medical Record (EMR) system enables a physician to record patients’ health information, request reports from third partly health care providers and retrieve these reports when they are ready. Despite the numerous benefits of EMRs, several factors have inhibited their widespread adoption. An underappreciated but critical factor has been the proliferation of inferior user interfaces which are confusing to navigate and disruptive to a physician’s workflow. To be useful, an EMR must allow physicians to record and query information in a natural manner that accommodates the non-linear nature of their workflow. In particular, an interface must permit a physician to record the minutiae of a patient’s condition while at the same time preserving the physician’s overview of a patient’s record so that any aspect of the patient’s health can be effortlessly queried and inspected. This paper proposes an interface design that attempts to address several of the usability deficiencies associated with current electronic medical record systems in use today.

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.006
metaresearch head score (Gemma)0.015
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.006
Threshold uncertainty score0.031

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.015
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0040.003
Open science0.0020.002
Research integrity0.0030.001
Insufficient payload (model declined to judge)0.0060.003

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.043
GPT teacher head0.443
Teacher spread0.400 · 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 designNot applicable
Domainnot available
GenreMethods

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

Citations4
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicElectronic Health Records SystemsFrench-language works237,207