MétaCan
Menu
Back to cohort
Record W2146765982 · doi:10.2340/16501977-0952

Usability testing of two e-learning resources: Methods to maximize potential for clinician use

2012· article· en· W2146765982 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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Rehabilitation Medicine · 2012
Typearticle
Languageen
FieldComputer Science
TopicUsability and User Interface Design
Canadian institutionsUniversity of Toronto
FundersCanadian Institutes of Health Research
KeywordsUsabilityNavigabilitySession (web analytics)Resource (disambiguation)Relevance (law)Quality (philosophy)CategorizationComputer scienceCognitive walkthroughWeb usabilityHuman–computer interactionWorld Wide WebArtificial intelligence

Abstract

fetched live from OpenAlex

RATIONALE AND OBJECTIVES: Rigorous usability testing of e-learn-ing resources is an important prerequisite to their wide-spread use among clinicians. This study demonstrates the application of an evidence-based approach to usability testing of two stroke-related e-learning resources (StrokEngine). METHODS: 14 stroke rehabilitation clinicians (occupational therapists and physiotherapists) from Ontario, Canada participated in a 1.5 h in-person testing session. Clinicians navigated StrokEngine in search of information to answer questions on stroke assessment/intervention. Their search patterns were observed and clinicians provided verbal/written feedback about StrokEngine. Content analysis was used to generate themes and categorize them under two broad categories: facilitators and barriers to use. RESULTS: Five key facilitators and three key barriers to Strok-Engine use were identified and related to screen format, layout/organization, ease of navigation, quality of content, likelihood of using StrokEngine in the future, and system dysfunctions. All 14 clinicians were very or extremely satisfied with the layout/organization, quality and clinical relevance of the content, stating that they were likely to use StrokEngine in the future. CONCLUSION: All identified barriers from this study were addressed with website modifications in order to maximize the usability and navigability of StrokEngine. This rigorous methodology for usability testing can be applied during the design process of any e-learning resource.

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.016
metaresearch head score (Gemma)0.057
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.421
Threshold uncertainty score0.951

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0160.057
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.097
GPT teacher head0.414
Teacher spread0.316 · 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