Starting from the needs: what are the appropriate sources to co-create innovative solutions for persons with disabilities?
Notice bibliographique
Résumé
PURPOSE: Technical solutions could facilitate activities and participation in individuals with disabilities. For the development of solutions, hackathons are a method of interdisciplinary collaboration. For hackathon, the definition of pain points that require solutions is crucial. We aimed to determine engineers' preferences and expectations regarding pain point qualities. METHODS: We used a collaborative approach involving individuals with disability, families, and healthcare professionals to determine pain points for use by engineering students during a disability Hackathon. A pain point bank was built using 3 upstream sources: a survey (350 responses, 20 pain points selected), interviews (8 children, 13 pain points), and a multidisciplinary workshop based on design thinking methods (45 people, 32 pain points). A fourth source was 20 adults with disabilities present during the Hackathon. Engineering students rated pain point qualities from each source in a questionnaire that included closed questions relating to predefined criteria: achievability, specificity, relevance and attractiveness and open questions to collect non-predefined quality criteria. RESULTS: Pain points from the workshop were most frequently used (48%); followed by on-site discussions with mentors (43%), the survey (38%), and interviews (31%). On-site discussions received the highest quality ratings followed by the workshop, survey, and interviews. Three quality criteria emerged from the responses to open questions: "representative", "empathy", and "real-need". CONCLUSIONS: To be actionable by engineers, pain points must relate to real needs, be achievable, specific, relevant and attractive but also representative and arouse empathy. We devised a checklist of qualities along with a toolbox of methods to achieve each. Implications For RehabilitationThe first step of the development of technical solutions for children and individuals with disabilities is the identification of their needs and their adequate formulation to be submitted to technical solutions providers.Daily life needs of individuals with disability were gathered for an engineering hackathon and proposed as pain points to 400 engineering students.To facilitate the development of solutions by engineers, pain points must relate to real needs, be specific, relevant, achievable and attractive; be representative and arouse empathy; a toolbox of needs collection methods is proposed to achieve each of those qualities.Discussions with individuals with disability and health professionals should be provided.
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,001 | 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,001 |
| Études des sciences et des technologies | 0,001 | 0,001 |
| 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 ».