Designing a Self-Guided Digital Intervention for Self-Management of Shoulder Pain in People Living With Spinal Cord Injury: Tutorial on Using a Person-Based Approach
Bibliographic record
Abstract
Unlabelled: Shoulder pain is prevalent in people living with spinal cord injury. Technology and digital rehabilitation tools are increasingly available, but this has not yet included the provision of a self-guided exercise intervention focused on managing shoulder pain for people living with spinal cord injury. We drew on the person-based approach (PBA) to intervention development to design a Shoulder Pain Intervention delivered over the interNet (SPIN) to address this gap. However, in preparation for the design process, we found very few published examples of how the PBA had been operationalized. The aim of this paper is to provide a detailed explanation of our approach and how we operationalized the PBA in the design of SPIN to maximize relevance and engagement. Our design process followed the key PBA steps, combining additional evidence and theoretical components. Each step ensured that guiding principles were formulated and followed to maximize the probability that SPIN would be fit for purpose. We followed 3 steps: (1) we drew on themes from preparatory research (existing and primary) to identify the key behavioral issues, needs and challenges, and existing features to form the basis of SPIN design; (2) we formatted guiding principles that included articulating specific design objectives to provide a framework to identify system requirements; and (3) we selected and refined intervention features using existing literature, behavioral theory, and tools such as the "Behaviour Change Wheel." We have designed SPIN by incorporating a deep understanding of the users' needs and best available evidence to maximize engagement and positive outcomes. In this paper, we have made clear how we operationalized the PBA phases, including how existing evidence, theory, tools, and methods were leveraged to support the PBA process. In explicating our process, we have provided a blueprint to guide future researchers using this approach.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.011 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.008 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".