Design and Development of a Telerehabilitation Platform for Patients With Phantom Limb Pain: A User-Centered Approach
Notice bibliographique
Résumé
BACKGROUND: Phantom limb pain is a frequent and persistent problem following amputation. Achieving sustainable favorable effects on phantom limb pain requires therapeutic interventions such as mirror therapy that target maladaptive neuroplastic changes in the central nervous system. Unfortunately, patients' adherence to unsupervised exercises is generally poor and there is a need for effective strategies such as telerehabilitation to support long-term self-management of patients with phantom limb pain. OBJECTIVE: The main aim of this study was to describe the user-centered approach that guided the design and development of a telerehabilitation platform for patients with phantom limb pain. We addressed 3 research questions: (1) Which requirements are defined by patients and therapists for the content and functions of a telerehabilitation platform and how can these requirements be prioritized to develop a first prototype of the platform? (2) How can the user interface of the telerehabilitation platform be designed so as to match the predefined critical user requirements and how can this interface be translated into a medium-fidelity prototype of the platform? (3) How do patients with phantom limb pain and their treating therapists judge the usability of the medium-fidelity prototype of the telerehabilitation platform in routine care and how can the platform be redesigned based on their feedback to achieve a high-fidelity prototype? METHODS: The telerehabilitation platform was developed using an iterative user-centered design process. In the first phase, a questionnaire followed by a semistructured interview was used to identify the user requirements of both the patients and their physical and occupational therapists, which were then prioritized using a decision matrix. The second phase involved designing the interface of the telerehabilitation platform using design sketches, wireframes, and interface mock-ups to develop a low-fidelity prototype. Heuristic evaluation resulted in a medium-fidelity prototype whose usability was tested in routine care in the final phase, leading to the development of a high-fidelity prototype. RESULTS: A total of 7 categories of patient requirements were identified: monitoring, exercise programs, communication, settings, background information, log-in, and general requirements. One additional category emerged for therapists: patient management. Based on these requirements, patient and therapist interfaces for the telerehabilitation platform were developed and redesigned by the software development team in an iterative process, addressing the usability problems that were reported by the users during 4 weeks of field testing in routine care. CONCLUSIONS: Our findings underline the importance of involving the users and other stakeholders early and continuously in an iterative design process, as well as the need for clear criteria to identify critical user requirements. A decision matrix is presented that incorporates the views of various stakeholders in systematically rating and prioritizing user requirements. The findings and lessons learned might help health care providers, researchers, software designers, and other stakeholders in designing and evaluating new teletreatments, and hopefully increase the likelihood of user acceptance.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».