| Literature DB >> 35442206 |
Céline Schöpfer1, Frederic Ehrler2, Antoine Berger2, Catherine Bollondi Pauly3, Laurence Buytaert4, Camille De La Serna4, Florence Hartheiser1, Thomas Fassier5,6, Christine Clavien1.
Abstract
BACKGROUND: Advance care planning, including advance directives, is an important tool that allows patients to express their preferences for care if they are no longer able to express themselves. We developed Accordons-nous, a smartphone app that informs patients about advance care planning and advance directives, facilitates communication on these sensitive topics, and helps patients express their values and preferences for care.Entities:
Keywords: advance care planning; advance directives; mHealth; mobile apps; mobile health; mobile phone; palliative care; usability
Year: 2022 PMID: 35442206 PMCID: PMC9069299 DOI: 10.2196/34626
Source DB: PubMed Journal: JMIR Hum Factors ISSN: 2292-9495
Figure 1Structure of the section I get information containing subpages accessible through a drop-down menu. ACP: advance care planning; AD: advance directives.
Figure 3Structure of the section I write. ACP: advance care planning; AD: advance directives.
List and description of the tasks used during the think-aloud test procedure.
| Task name | Expected achievement | Exact wording of the question | Task considered as completed when |
| Definition | The participant discovers how to find definitions in the app. | “While researching advance directives, you heard the term ‘surrogate’ and want to know what it means exactly. Where would you look in the application to clarify its meaning?” | On the main page of the app, the participant clicks on the term |
| Legal obligations | The participant understands the logic of the green drop-down menu that allows accessing different pages within a section and finding specific legal information. | “You want to know what legal obligation doctors have toward patients who have written advance directives. Where would you go, in this application, to find this information?” | The participant finds the heading “Are doctors required to follow advance directives?” that is included in the page “What does the law say?” situated in the “I get information” section. |
| Conversation starters | The participant understands that the app is composed of 3 sections accessible via the menu at the bottom of the screen and finds specific content. | “You want to find ways to start a conversation with your son about your advance directives. Where would you go in this application?” | The participant discovered (1) the page |
| Data confidentiality | The participant finds the | “After browsing the application for some time, you feel that you have enough information and decide to start writing your advance directives. However, before you complete the questionnaire, you want to know who will have access to the answers you write in the application. Where would you go in the module to get this information?” | The participant clicks on the button in the |
| Filter function | The participant discovers the filter function. | “You find that there are too many questions in the questionnaire, and you want to answer in a more targeted way the questions that are important to you. You would like to answer only the questions that concern healthy patients. How would you do this?” | The participant opens the filter function. |
| Values and preferences | The patient understands that the questionnaire is divided into several subsections and can make sense of their content by reading their title. | “Your faith in God is something central to your life. Therefore, it is really important for you to give details of your religious beliefs. Where would you go in the application to provide details on this matter?” | The participant finds question 15 “A few words about my spirituality” situated in the subsection “My values and preferences” of the questionnaire. |
| Finalize the questionnaire | The participant understands how to export from the app his or her answers to the questionnaire. | “You have answered all questions that are important to you and now you want to send your form by email. How would you do this?” | The participant clicks on the “Finalize and receive my questionnaire” button situated at the bottom of the questionnaire in the |
Rules used to arbitrate diverging evaluations in double coding.
| Object of comparison and type of divergence | Rule applied | |
|
| ||
|
| 1-point difference between evaluations | Select the lowest score (to avoid desirability bias) |
|
| >1 point difference between evaluations | Double check the recording and discuss the evaluation (CS, FE, and CC) until an agreement is reached |
|
| ||
|
| ≥1 point differences between evaluations | CS watches the video again to find the correct number |
|
| ||
|
| Difference between the 2 evaluations <10% | Use the average time between the 2 evaluators |
|
| Difference between the 2 evaluations >10% | CS watches the video again and decides |
|
| ||
|
| Evaluators did not record the same errors and problems encountered by participants | Discuss the evaluation (CS, FE, and CC) until an agreement is reached |
|
| ||
|
| Different categorizations for 1 error or problem | Discuss the evaluation (CS, FE, and CC) until an agreement is reached |
|
| ||
|
| Differences between evaluations of the severity rate of an error or problem | Discuss the evaluation (CS, FE, and CC) until an agreement is reached |
Scolarius scores of the app Accordons-nous, per page.
| Page of the app | Number of words | Score | Level of education |
| 254 | 100 | High school | |
| 893 | 94 | High school | |
| 876 | 89 | Elementary school | |
| 1661 | 99 | High school | |
| 312 | 60 | Elementary school | |
| 3665 | 70 | Elementary school | |
| 3105 | 100 | High school |
Figure 4Proportion of participants who succeeded or failed to complete study tasks with or without input from the experimenter and with or without using the shortest route.
Figure 5Distribution of the number of clicks needed for participants to complete each of the 7 tasks.
Figure 6Distribution of time (in seconds) spent by participants completing each of the 7 tasks.
Figure 7Total time (in seconds) spent by each participant on the 7 tasks of the think-aloud test. In green, time spent on tasks that have been completed successfully and without help (by using the shortest path or not). In red, time spent on tasks failed or completed with the help of the experimenter.
List of problems encountered by participants during the 7 think-aloud tasks, classified in 3 severity categories (major usability problem, minor problem, and not a usability issue). Description, categorization, and frequency of occurrence of these problems during task completion.
| Item and problem | Category (numbered according to Bastien and Scapin [ | Description of the problem | Task in which it occurred (frequency of occurrence) | |
|
| ||||
|
| 1 | 1.2. Grouping or distinction of items | Users did not click on the green drop-down menu and therefore missed much of the content of the module. | Legal obligations (3); Conversation starters (1) |
|
| 2 | 7. Significance of codes | Users did not search for the information about the confidentiality of their ADa in the right place: they felt that this information should have been located elsewhere in the app (for instance, in | Data confidentiality (5) |
|
| 3 | 1.3. Immediate feedback | Users expected feedback linked to the filter function in the | Filter function (4) |
|
| 4 | 8. Compatibility | Participants tried to use functions they usually used in other apps; however, these were not active: one iOS user tried swiping left to return to the previous page, and an Android user used the back arrow to achieve the same goal; however, these functions were not active in | Conversation starters (1); Data confidentiality (1) |
|
| 5 | 2.2 Information density | As the pages contained large sections of written content, some users took time to read the content of the pages, and this delayed their navigation or distracted them from the task. For instance, when they discovered the | Legal obligations (1); Conversation starters (2) |
|
| 6 | 1.4 Legibility | One user found that the bottom menu is too small and that the font does not offer sufficient contrast. | Conversation starters (1) |
|
| 7 | 7. Significance of codes | One user did not find the filter function explicit enough. | Filter function (1) |
|
| 8 | 8. Compatibility | One user was confused by the fact that on the first page, the title of the section | Definition (1) |
|
| ||||
|
| 9 | 7. Significance of codes | Many users complained that they did not find the expected content by clicking on the hamburger menu at the top right of the screen: they thought that this would allow them to see the architecture of the module. However, this menu is not linked to the module | Definition (1); Legal obligations (2); Conversation starters (3) |
|
| 10 | 7. Significance of codes and 8. Compatibility | Many users clicked on the home menu at the top left of the screen, thinking that this would bring them back to the front page of the module | Legal obligations (1); Conversation starters (2); Data confidentiality (1) |
|
| 11 | 8. Compatibility | Some users were looking for a main | Definition (1); Data confidentiality (1); Values and preferences (1) |
|
| 12 | 7. Significance of codes and 8. Compatibility | Two users expected that the | Conversation starters (2) |
|
| 13 | 1.4 Legibility | One user assessed the font size of the text as too small and the font contrast as insufficient. | Definition (1) |
|
| 14 | 1.2 Grouping or distinction of items | One user did not see the | Data confidentiality (1) |
|
| 15 | 7. Significance of codes | One user did not see the | Filter function (1) |
|
| 16 | 8. Compatibility | One ordinary question in the AD form was confused with a function: a user thought that the question, “Where will you save your advance directives?” (multiple options are suggested as an incentive to store AD in several locations) would allow them to save the AD directly in different places. | Finalize questionnaire (1) |
|
| ||||
|
| 17 | 8. Compatibility | One user complained that the app does not contain a search function. | Definition (1) |
aAD: advance directives.
Figure 8Two questions included in the advance directives (AD) form, with example responses in gray. The text disappears once the user clicks on the text box to add his or her own response.
Figure 9Score of Accordons-nous on the SUS. SUS: System Usability Scale [35].
Participants’ evaluation of the relevance of Accordons-nous for improving ACPa and ADb (N=10).
| Measure | Question item | Responses, n (%) | ||||
|
|
| Strongly agree | Agree | No opinion | Disagree | Strongly disagree |
| Awareness | This app is likely to increase awareness of the importance of (ACP and AD) | 5 (50) | 4 (40) | 0 (0) | 1 (10) | 0 (0) |
| Knowledge | This app is likely to increase knowledge or understanding of (ACP and AD) | 9 (90) | 1 (10) | 0 (0) | 0 (0) | 0 (0) |
| Attitude | This app is likely to change attitudes toward improving (ACP and AD) | 3 (30) | 4 (40) | 3 (30) | 0 (0) | 0 (0) |
| Intention to change | This app is likely to increase intentions or motivation to address (ACP and AD) | 4 (40) | 5 (50) | 1 (10) | 0 (0) | 0 (0) |
| Help seeking | Using this app is likely to encourage further help seeking for (ACP and AD) | 1 (10) | 5 (50) | 3 (30) | 1 (10) | 0 (0) |
| Behavior change | Using this app is likely to increase behavior change (ACP and AD) | 4 (40) | 6 (60) | 0 (0) | 0 (0) | 0 (0) |
aACP: advance care planning.
bAD: advance directives.
List of changes made to the app in response to the major issues identified.
| Item | Description of the issue | Changes made |
| 1 and 6 | Users did not click on the green drop-down menu and therefore missed much of the content of the module. One user found that the bottom menu is too small and that the font does not offer sufficient contrast. | To overcome navigation difficulties, we created a motion design video [ |
| 2 | Users did not search for the information about the confidentiality of their advance directives in the right place: they felt that this information should have been located elsewhere in the app (for instance, in the | We duplicated the information on “How is your privacy managed?” on the first page of the module. |
| 3 and 7 | Users expected feedback linked to the filter function in the | First, we changed the color and location of the |
| 5 | As pages contained large sections of written content, some users took time to read the content of the pages, and this delayed their navigation or distracted them from the task. For instance, when they discovered the | First, we integrated 2 motion design videos containing illustrated summaries of the most important information. Second, we used the accordion visual presentation in sections containing large amounts of texts to help users to find the searched information without having to scroll through long texts. Third, in the |
| 8 | One user was confused by the fact that on the first page, the title of the section | We removed the title of the app on all pages. |
List of problems that were notified to the Concerto team and changes made.
| Item | Reported problem | Change made |
| 9 | Several users clicked on the hamburger menu at the top right of the screen, thinking that this would allow them to see the architecture of | The |
| 10 | Several users clicked on the home button at the top left of the screen, thinking that this would allow them to go back to the front page of | The |
| 4 | Participants tried to use functions they usually used in other apps; however, these were not active: an iOS user tried swiping left to return to the previous page, and an Android user used the back arrow to achieve the same goal; however, these functions were not active in | None to this date |
| 13 | The | None to this date |