Table 3.
A summary of the requirements identified during the semistructured interviews.
| ID | Requirement description | Participant ID |
| 1 | Text used to convey symptoms should be developed in conjunction with the views of target stakeholders. Medical jargon should primarily be avoided but some phrases (such as brand names) may be crucial to user comprehension. | 2, 3, 8, 10 |
| 2 | A variety of communication modalities should be targeted. As a result, symptoms should be represented by text, speech, and images where appropriate. | 1, 3-5, 7-10 |
| 3 | Images should be immediately identifiable to the user and subsequently developed in conjunction with the views of target stakeholders. | 5, 8 |
| 4 | The user should have the option to have text played back to them. The pace, style, and volume in which the text is played back should be customizable to suit an individual’s needs. | 2-5, 8 |
| 5 | The design of the app should be consistent throughout. An example may be embedding a help button at the top left-hand corner of all pages. | 4, 9, 10 |
| 6 | Questions presented to the user should be concise, straightforward, and focus on solitary ideas. All potential options should focus on a single subject. | 1, 2, 4 |
| 7 | The number of clicks used throughout the aid should be reduced to a minimum to aid users who have limited attention spans, etc. | 10 |
| 8 | A dynamic questionnaire should be implemented. Future questions should be shaped by the information previously supplied by the user. | 7, 9 |
| 9 | The number of potential options displayed on screen should be limited to a maximum of 4. | 3, 4, 9, 10 |
| 10 | The aid should port easily across various operating systems and screen sizes. | 8, 10 |
| 11 | The aesthetics of the aid should be made customizable to address the complex needs of stakeholders. The content should remain unchanged. | 4, 5, 8, 10 |
| 12 | The symptoms presented to stakeholders should be informed by the specific health needs of adults with learning disabilities, rather than that of the general population. | 1, 2, 10 |
| 13 | Questions should aim to extract the symptoms experienced by patients, the duration and history of these symptoms, and the overall health of patients. | 6, 7 |
| 14 | Questions should be presented one at a time. | 3, 4, 9, 10 |
| 15 | A minimum font size of 14 should be used throughout. Text should be made as large as possible. | 3-5, 8, 9 |
| 16 | Contrasting colors should be used to ensure information stands out and can be processed easily. The user should be able to select the color scheme that addresses their needs best. | 3-5, 8, 10 |
| 17 | The aid should provide symptoms experienced by patients in advance of consultations. | 2, 4, 5, 7 |
| 18 | Significant symptoms identified by the app should be stored for future retrieval by general practitioners. This will require the personal details of patients to be captured to act as keys within a database. | 6-7 |
| 19 | All feedback provided should be simple and constructive with a consistent help feature available to increase autonomy. | 9 |
| 20 | The overall consultation process should be broken down into manageable chunks. | 1,2, 4 |