MétaCan
Menu
← Back to cohort
Record W4404974864 · doi:10.2196/66666

Addressing the “Black Hole” of Low Back Pain Care With Clinical Decision Support: User-Centered Design and Initial Usability Study

2024· article· en· W4404974864 on OpenAlexvenueno aff
Robert S. Rudin, Patricia M. Herman, Robert Vining

Bibliographic record

VenueJMIR Formative Research · 2024
Typearticle
Languageen
FieldMedicine
TopicMusculoskeletal pain and rehabilitation
Canadian institutionsnot available
FundersNational Center for Complementary and Integrative HealthNational Institutes of Health
KeywordsPreprintUsabilityClinical decision support systemHuman–computer interactionComputer scienceDecision support systemMedicineWorld Wide WebData mining

Abstract

fetched live from OpenAlex

Background: Low back pain (LBP) is a highly prevalent problem causing substantial personal and societal burden. Although there are specific types of LBP, each with evidence-based treatment recommendations, most patients receive a nonspecific diagnosis that does not facilitate evidence-based and individualized care. objectives: We designed, developed, and initially tested the usability of a LBP diagnosis and treatment decision support tool based on the available evidence for use by clinicians who treat LBP, with an initial focus on chiropractic care. Methods: Our 3-step user-centered design approach consisted of identifying clinical requirements through the analysis of evidence reviews, iteratively identifying task-based user requirements and developing a working web-based prototype, and evaluating usability through scenario-based interviews and the System Usability Scale. Results: The 5 participating users had an average of 18.5 years of practicing chiropractic medicine. Clinical requirements included 44 patient interview and examination items. Of these, 13 interview items were enabled for all patients and 13 were enabled conditional on other input items. One examination item was enabled for all patients and 16 were enabled conditional on other items. One item was a synthesis of interview and examination items. These items provided evidence of 12 possible working diagnoses of which 3 were macrodiagnoses and 9 were microdiagnoses. Each diagnosis had relevant treatment recommendations and corresponding patient educational materials. User requirements focused on tasks related to inputting data, and reviewing and selecting working diagnoses, treatments, and patient education. User input led to key refinements in the design, such as organizing the input questions by microdiagnosis, adding a patient summary screen that persists during data input and when reviewing output, adding more information buttons and graphics to input questions, and providing traceability by highlighting the input items used by the clinical logic to suggest a working diagnosis. Users believed that it would be important to have the tool accessible from within an electronic health record for adoption within their workflows. The System Usability Scale score for the prototype was 84.75 (range: 67.5-95), considered as the top 10th percentile. Users believed that the tool was easy to use although it would require training and practice on the clinical content to use it effectively. With such training and practice, users believed that it would improve care and shed light on the "black hole" of LBP diagnosis and treatment. Conclusions: Our systematic process of defining clinical requirements and eliciting user requirements to inform a clinician-facing decision support tool produced a prototype application that was viewed positively and with enthusiasm by clinical users. With further planned development, this tool has the potential to guide clinical evaluation, inform more specific diagnosis, and encourage patient education and individualized treatment planning for patients with LBP through the application of evidence at the point of care.

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.066
metaresearch head score (Gemma)0.117
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.066
Threshold uncertainty score0.347

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0660.117
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.001
Science and technology studies0.0010.002
Scholarly communication0.0030.003
Open science0.0020.002
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0010.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.189
GPT teacher head0.512
Teacher spread0.324 · 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

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Formative Research→Same topicMusculoskeletal pain and rehabilitation→French-language works237,207→