MétaCan
Menu
Back to cohort
Record W2801795794 · doi:10.2196/resprot.9379

A Decision Support System to Enhance Self-Management of Low Back Pain: Protocol for the selfBACK Project

2018· article· en· W2801795794 on OpenAlex
Paul Jarle Mork

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJMIR Research Protocols · 2018
Typearticle
Languageen
FieldMedicine
TopicMusculoskeletal pain and rehabilitation
Canadian institutionsnot available
FundersEuropean Commission
KeywordsProtocol (science)Statement (logic)Computer scienceClinical decision support systemDecision support systemMedicineMedical educationAlternative medicineArtificial intelligence

Abstract

fetched live from OpenAlex

BACKGROUND: Low back pain (LBP) is a leading cause of disability worldwide. Most patients with LBP encountered in primary care settings have nonspecific LBP, that is, pain with an unknown pathoanatomical cause. Self-management in the form of physical activity and strength and flexibility exercises along with patient education constitute the core components of the management of nonspecific LBP. However, the adherence to a self-management program is challenging for most patients, especially without feedback and reinforcement. Here we outline a protocol for the design and implementation of a decision support system (DSS), selfBACK, to be used by patients themselves to promote self-management of LBP. OBJECTIVE: The main objective of the selfBACK project is to improve self-management of nonspecific LBP to prevent chronicity, recurrence and pain-related disability. This is achieved by utilizing computer technology to develop personalized self-management plans based on individual patient data. METHODS: The decision support is conveyed to patients via a mobile phone app in the form of advice for self-management. Case-based reasoning (CBR), a technology that utilizes knowledge about previous cases along with data about the current patient case, is used to tailor the advice to the current patient, enabling a patient-centered intervention based on what has and has not been successful in previous patient cases. The data source for the CBR system comprises initial patient data collected by a Web-based questionnaire, weekly patient reports (eg, symptom progression), and a physical activity-detecting wristband. The effectiveness of the selfBACK DSS will be evaluated in a multinational, randomized controlled trial (RCT), targeting care-seeking patients with nonspecific LBP. A process evaluation will be carried out as an integral part of the RCT to document the implementation and patient experiences with selfBACK. RESULTS: The selfBACK project was launched in January 2016 and will run until the end of 2020. The final version of the selfBACK DSS will be completed in 2018. The RCT will commence in February 2019 with pain-related disability at 3 months as the primary outcome. The trial results will be reported according to the CONSORT statement and the extended CONSORT-EHEALTH checklist. Exploitation of the results will be ongoing throughout the project period based on a business plan developed by the selfBACK consortium. Tailored digital support has been proposed as a promising approach to improve self-management of chronic disease. However, tailoring self-management advice according to the needs, motivation, symptoms, and progress of individual patients is a challenging task. Here we outline a protocol for the design and implementation of a stand-alone DSS based on the CBR technology with the potential to improve self-management of nonspecific LBP. CONCLUSIONS: The selfBACK project will provide learning regarding the implementation and effectiveness of an app-based DSS for patients with nonspecific LBP. REGISTERED REPORT IDENTIFIER: RR1-10.2196/9379.

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.009
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: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Protocol · Consensus signal: Protocol
Teacher disagreement score0.412
Threshold uncertainty score0.511

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0090.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.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.110
GPT teacher head0.551
Teacher spread0.441 · 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