TY - JOUR
T1 - Aphasia therapy software
T2 - an investigation of the research literature and the challenges of software development
AU - Cuperus, Pauline
AU - de Kok, Dörte
AU - de Aguiar, Vânia
AU - Nickels, Lyndsey
N1 - Publisher Copyright:
© 2024 The Author(s). Published by Informa UK Limited, trading as Taylor & Francis Group.
PY - 2024/9/13
Y1 - 2024/9/13
N2 - Aphasia therapy software: aninvestigation of the research literature and the challenges of software development Background: Digital aphasia therapy has become increasingly popular over the past years. However, not all software described in the literature appears to reach clinical practice. It is currently unclear why this is the case. Aim: We had two aims. First, we aimed to create an overview of the digital aphasia therapy described and its clinical availability bysystematically searching and reviewing the research literature. Second, we aimed to investigate the experiences of researchers/developers of aphasia therapy software. Method & Procedures: We conducted a systematic search and review, screening references against our inclusion criteria. Clinical availability of the software was established through reading literature, conducting internet searches, and by contacting the researchers/developers who were associated with the software. Researchers/developers of the reported software were surveyed about their experiences with software development. Responses were the matically analysed into themes and subthemes. Outcomes & Results: We identified a total of 63 unique pieces of software across 125 references. The software was mainly developed for English speakers and mainly focused on word retrieval or a combination of language skills. We established clinical availability with certainty for 35 pieces of software, with the remaining software (likely) currently clinically unavailable. From the survey data, we identified five recurring themes: 1) software development can be expensive and insufficient funding hinders their clinical availability; 2) commercialisation of software is often new and daunting to researchers but essential for making software available; 3) clinicians and people with aphasia are valuable sources of feedback; 4) working with software developers can be difficult; and 5) aphasia therapy software should combine both the evidence base and current clinical need. Conclusions: Aminority of aphasia therapy software described in the literature reaches clinical practice. It is clear that the development and subsequent dissemination of aphasia therapy software requires large amounts of time, energy, and funds but we conclude that this is essential for successful clinical implementation.
AB - Aphasia therapy software: aninvestigation of the research literature and the challenges of software development Background: Digital aphasia therapy has become increasingly popular over the past years. However, not all software described in the literature appears to reach clinical practice. It is currently unclear why this is the case. Aim: We had two aims. First, we aimed to create an overview of the digital aphasia therapy described and its clinical availability bysystematically searching and reviewing the research literature. Second, we aimed to investigate the experiences of researchers/developers of aphasia therapy software. Method & Procedures: We conducted a systematic search and review, screening references against our inclusion criteria. Clinical availability of the software was established through reading literature, conducting internet searches, and by contacting the researchers/developers who were associated with the software. Researchers/developers of the reported software were surveyed about their experiences with software development. Responses were the matically analysed into themes and subthemes. Outcomes & Results: We identified a total of 63 unique pieces of software across 125 references. The software was mainly developed for English speakers and mainly focused on word retrieval or a combination of language skills. We established clinical availability with certainty for 35 pieces of software, with the remaining software (likely) currently clinically unavailable. From the survey data, we identified five recurring themes: 1) software development can be expensive and insufficient funding hinders their clinical availability; 2) commercialisation of software is often new and daunting to researchers but essential for making software available; 3) clinicians and people with aphasia are valuable sources of feedback; 4) working with software developers can be difficult; and 5) aphasia therapy software should combine both the evidence base and current clinical need. Conclusions: Aminority of aphasia therapy software described in the literature reaches clinical practice. It is clear that the development and subsequent dissemination of aphasia therapy software requires large amounts of time, energy, and funds but we conclude that this is essential for successful clinical implementation.
KW - aphasia
KW - clinical implementation
KW - Digital therapy
KW - software development
KW - speech and language therapy
UR - http://www.scopus.com/inward/record.url?scp=85203962352&partnerID=8YFLogxK
U2 - 10.1080/02687038.2024.2384542
DO - 10.1080/02687038.2024.2384542
M3 - Article
AN - SCOPUS:85203962352
SN - 0268-7038
JO - Aphasiology
JF - Aphasiology
ER -