<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v9i2e34626</article-id>
      <article-id pub-id-type="pmid">35442206</article-id>
      <article-id pub-id-type="doi">10.2196/34626</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Mobile App for Advance Care Planning and Advance Directives (Accordons-nous): Development and Usability Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Dupont</surname>
            <given-names>Charlèss</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Marshall</surname>
            <given-names>Robert</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Schöpfer</surname>
            <given-names>Céline</given-names>
          </name>
          <degrees>MPhil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Institute for Ethics, History, and the Humanities</institution>
            <institution>University Medical Center</institution>
            <institution>University of Geneva</institution>
            <addr-line>CMU/1 rue Michel Servet</addr-line>
            <addr-line>Geneva, 1211</addr-line>
            <country>Switzerland</country>
            <phone>41 22 379 46 00</phone>
            <email>celine.schopfer@etu.unige.ch</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5111-9245</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Ehrler</surname>
            <given-names>Frederic</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9734-3242</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Berger</surname>
            <given-names>Antoine</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8447-0645</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Bollondi Pauly</surname>
            <given-names>Catherine</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4857-1956</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Buytaert</surname>
            <given-names>Laurence</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6967-2372</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>De La Serna</surname>
            <given-names>Camille</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6361-5289</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Hartheiser</surname>
            <given-names>Florence</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8377-9328</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Fassier</surname>
            <given-names>Thomas</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5853-8450</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Clavien</surname>
            <given-names>Christine</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0968-144X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Institute for Ethics, History, and the Humanities</institution>
        <institution>University Medical Center</institution>
        <institution>University of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Medical Information Sciences</institution>
        <institution>University Hospitals of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Direction of Care</institution>
        <institution>University Hospitals of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>University Medical Center</institution>
        <institution>University of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Division of Internal Medicine for the Aged</institution>
        <institution>University Hospitals of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>Interprofessional Simulation Center</institution>
        <institution>Faculty of Medicine</institution>
        <institution>University of Geneva</institution>
        <addr-line>Geneva</addr-line>
        <country>Switzerland</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Céline Schöpfer <email>celine.schopfer@etu.unige.ch</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Apr-Jun</season>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>20</day>
        <month>4</month>
        <year>2022</year>
      </pub-date>
      <volume>9</volume>
      <issue>2</issue>
      <elocation-id>e34626</elocation-id>
      <history>
        <date date-type="received">
          <day>1</day>
          <month>11</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>5</day>
          <month>12</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>11</day>
          <month>1</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>20</day>
          <month>1</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Céline Schöpfer, Frederic Ehrler, Antoine Berger, Catherine Bollondi Pauly, Laurence Buytaert, Camille De La Serna, Florence Hartheiser, Thomas Fassier, Christine Clavien. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 20.04.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2022/2/e34626" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>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 <italic>Accordons-nous</italic>, 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.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The first objective of this study is to conduct a usability test of this app. The second objective is to collect users’ critical opinions on the usability and relevance of the tool.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted a usability test by means of a think-aloud method, asking 10 representative patients to complete 7 browsing tasks. We double coded the filmed sessions to obtain descriptive data on task completion (with or without help), time spent, number of clicks, and the types of problems encountered. We assessed the severity of the problems encountered and identified the modifications needed to address these problems. We evaluated the readability of the app using Scolarius, a French equivalent of the Flesch Reading Ease test. By means of a posttest questionnaire, we asked participants to assess the app’s usability (System Usability Scale), relevance (Mobile App Rating Scale, section F), and whether they would recommend the app to the target groups: patients, health professionals, and patients’ caring relatives.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Participants completed the 7 think-aloud tasks in 80% (56/70) of the cases without any help from the experimenter, in 16% (11/70) of the cases with some help, and failed in 4% (3/70) of the cases. The analysis of failures and difficulties encountered revealed a series of major usability problems that could be addressed with minor modifications to the app. <italic>Accordons-nous</italic> obtained high scores on readability (overall score of 87.4 on Scolarius test, corresponding to elementary school level), usability (85.3/100 on System Usability Scale test), relevance (4.3/5 on the Mobile App Rating Scale, section F), and overall subjective endorsement on 3 <italic>I would recommend</italic> questions (4.7/5).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This usability test helped us make the final changes to our app before its official launch.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>usability</kwd>
        <kwd>mobile apps</kwd>
        <kwd>advance directives</kwd>
        <kwd>advance care planning</kwd>
        <kwd>mHealth</kwd>
        <kwd>mobile health</kwd>
        <kwd>palliative care</kwd>
        <kwd>mobile phone</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Medical progress increases the availability of treatment options and life-sustaining possibilities. Consequently, it also increases the necessity to make choices between medical options that have different impacts on patients’ future lives. When patients are not capable of making those decisions, health care professionals and surrogates are requested to choose, even if they have no clue about the patient’s values and priorities. To avoid such distressful and suboptimal situations, early advance care planning (ACP) is increasingly being recognized as an important condition for adequate treatment [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. ACP is “the ability to enable individuals to define goals and preferences for future medical treatment and care, to discuss these goals and preferences with family and health care providers, and to record and review these preferences if appropriate” [<xref ref-type="bibr" rid="ref3">3</xref>]. An ACP procedure may result in written advance directives (AD); however, for such document to be of any use, it remains important that it is precise and that patients discuss its content with their surrogate decision-maker and update it regularly [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
        <p>Despite the acknowledged importance of ACP, few patients discuss their fears, priorities, and the type of care they would like to receive with their families and professional caregivers [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. This is partly because of a lack of knowledge about ACP, a lack of recognition that ACP is relevant for them, and a lack of assistance in this psychologically heavy process [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Studies also indicate that even health care professionals find it difficult to initiate such discussions [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>].</p>
        <p>ACP can be seen as a process of behavior change involving steps, including awareness and knowledge acquisition, thinking and commitment to act (eg, talking to someone and writing AD), action, and regular updates [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. It has been suggested that patient-centered, computer-based infographics could enhance interest, understanding, recalling, contemplation, and actual sharing of decisions related to ACP [<xref ref-type="bibr" rid="ref14">14</xref>]. They may assist in the ACP process and save clinicians’ time, as patients may be able to obtain relevant information and input to start the ACP process in a family context. Free web-based ACP tools have been developed, with promising preliminary results [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref20">20</xref>]. Mobile apps for ACP are available in some countries. Their potential is recognized; however, existing products have limited features and operate mostly in English only [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. We did not find comparable tools available in French. A recent review concluded that overall, mobile apps provide insufficient content and features: they are helpful to users who are ready to complete AD rather than those seeking to learn about the ACP process. Moreover, they are poor in terms of design quality, layout, and functionality. Only one app (in English) was assessed as “fairly easy to read” [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      </sec>
      <sec>
        <title>Accordons-nous</title>
        <p>To support the ACP process for French-speaking Swiss residents, our interprofessional research team comprising ethicists, physicians, nurses, patients as partners, information technology professionals developed a free and easy-to-use solution, an app called <italic>Accordons-nous</italic> (<italic>Let’s agree</italic>).</p>
        <p>We developed the content and structure of the app between January 2019 and July 2021 using mixed methods—a Delphi procedure and multiple user tests involving laypeople and patients as partners. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> [<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>] provides the details about the process of making the app.</p>
        <p><italic>Accordons-nous</italic> aims to address known barriers to ACP: lack of awareness; insufficient health literacy; difficulty in starting the discussion; identifying one’s own preferences, values, and goals of care; and writing personalized and comprehensive AD and updating them regularly within a smooth process.</p>
        <p>The app is adapted to the local context of French-speaking Switzerland, designed to be used by patients and their family caregivers independently at home or to support ACP discussions with health professionals. Its content is adapted to the health literacy of ordinary patients. It includes (1) content to make users aware of the importance of anticipating health-related decisions and motivate them to engage in their ACP; (2) essential information on the ACP procedure, legal issues, definitions of technical terms in a format, and vocabulary accessible to common users; (3) discussion prompts to help users engage in ACP discussions with their family, friends, and professional care providers; (4) a card game to help patients clarify their values and priorities in life and reflect on the conditions that would make life not worth living; and (5) a detailed and comprehensive advance directive form that can be tailored to individual life and health situations.</p>
        <p>The app, developed in Angular 11 [<xref ref-type="bibr" rid="ref26">26</xref>], is structured in 3 main sections (<xref rid="figure1" ref-type="fig">Figures 1</xref>-<xref rid="figure3" ref-type="fig">3</xref>)—<italic>Je m’informe</italic> (I get informed), <italic>J’en parle</italic> (I talk about it), and <italic>J’écris</italic> (I write)—accessible by clicking on a menu at the bottom of the screen. Each section contains several pages accessible via a drop-down menu.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Structure of the section I get information containing subpages accessible through a drop-down menu. ACP: advance care planning; AD: advance directives.</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i2e34626_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Structure of the section I talk about it with the different pages accessible through a drop-down menu. ACP: advance care planning.</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i2e34626_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Structure of the section I write. ACP: advance care planning; AD: advance directives.</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i2e34626_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Objectives</title>
        <p>The primary objective of this study is to measure whether <italic>Accordons-nous</italic> is easy to use and understand by common users. The secondary objectives are to identify the usability problems encountered by common users and to collect their critical opinions on the relevance of the tool—do they think that the app helps to engage in ACP procedures, and would they recommend the app to its target populations?</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Participants</title>
        <p>Nielsen and Landauer [<xref ref-type="bibr" rid="ref27">27</xref>] reported that 98% of usability problems could be detected through feedback from 10 users. On the basis of this, we aimed to obtain at least 10 complete responses. We asked the <italic>Patients as Partners Project</italic> at the Geneva University Hospitals (Hopitaux Universitaires de Genève [HUG]) to recruit patients fulfilling our criteria. Participation was free and voluntary. The patients received and signed informed consent forms before the study.</p>
        <p>We used the following inclusion criteria:</p>
        <list list-type="order">
          <list-item>
            <p>Fluency in written and oral French (the app is available only in French)</p>
          </list-item>
          <list-item>
            <p>Comfortable with using a mobile phone or tablet</p>
          </list-item>
          <list-item>
            <p>Demonstrates a minimal understanding of the concept of AD (to avoid a heavy cognitive load; ordinary users will have more time than our test participants to explore the app and be acquainted with the topic)</p>
          </list-item>
          <list-item>
            <p>Did not participate in the development of <italic>Accordons-nous</italic> (to obtain unbiased responses)</p>
          </list-item>
        </list>
        <p>Being incapable of understanding the meaning of the questions and tasks required for the study after 3 iterations of the task instructions was the only exclusion criterion.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>We submitted our research protocol to the Geneva Commission Cantonale d’Ethique de la Recherche (Req-ID 2020-01397), who decided that the project does not fall within the scope of the Human Research Ordinance and therefore alleviated the need for ethical approval (decision date 12.1.2020). This study was conducted in accordance with the Declaration of Helsinki. Willing participants were informed of the study aims and procedures and signed an informed consent form. During the data collection and analysis phase, only three authors (CS, FE, and CC) had access to the recorded interviews. The recordings were destroyed after analysis. No identifying information was kept in the remaining work files.</p>
      </sec>
      <sec>
        <title>Study Intervention</title>
        <p>We conducted a usability test [<xref ref-type="bibr" rid="ref28">28</xref>] using a think-aloud method [<xref ref-type="bibr" rid="ref29">29</xref>] comprising 7 tasks. Moreover, we collected quantitative descriptive data using a questionnaire to obtain information about participants’ endorsement of the app and their evaluation of the app’s usability and relevance for ACP.</p>
        <p>We conducted the usability test sessions on the web using the Zoom video conferencing platform. Ahead of the test day, participants received the information and consent sheet and the instructions on how to log on to Zoom by email. Once connected, the experimenter (CS) recalled the procedure as described in the information and consent sheet, answered the participants’ questions, and asked for verbal (recorded on Zoom) or written (to be sent after the test) consent. The experimenter also expressed her commitment to respect the study protocol. Verbal consent was recorded separately to protect participants’ anonymity during the analysis stage.</p>
        <p>Next, the experimenter instructed participants to install the test version of the <italic>Concerto HUG</italic> app that contains the module <italic>Accordons-nous</italic> on their personal smartphone or tablet. The experimenter then instructed the participants to connect their phone or tablet to the same Zoom conversation and share their phone or tablet screen. In this way, while discussing with the experimenter in front of their computer, participants could simultaneously navigate the app via their smartphone or tablet, and the experimenter could see how participants did so (owing to the screen sharing function). Precautions were taken beforehand to avoid personal notifications appearing during the screen sharing.</p>
        <p>The experimenter then started the actual test. To ensure that participants fulfilled the inclusion criteria, she began by asking some demographic and technical questions (age, gender, and type of phone or tablet used), as well as participants’ understanding of the topic of AD (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>; general questions).</p>
        <p>Next, to ensure that participants did not need to express their personal choices and preferences regarding ACP, the experimenter asked the participants to put themselves in the following fictional scenario:</p>
        <disp-quote>
          <p>You are a 75-year-old man/woman; you have always been in good health, but you recently started experiencing a heart problem that required hospitalization. Fortunately, you recovered fully, but this experience made you think a lot. Now you are asking yourself, “What if another major health accident occurs, during which I lose my capacity to make decisions? How would health professionals know about what matters to me?” You know that it is possible to express your preferences in a document called “advance directives,” but you do not know how to do this. You share your concerns with a friend, who tells you about the application Accordons-nous and you decide to use it to write your directives. You have just downloaded the application and explore it for the first time.</p>
        </disp-quote>
        <p>Participants were then successively given 7 tasks to complete in the <italic>Accordons-nous</italic> module (<xref ref-type="table" rid="table1">Table 1</xref>). The tasks were designed to test users’ ease while completing the main tasks that a common user of the app is meant to handle and identify the strengths and weaknesses of the app.</p>
        <p>While completing the tasks, participants were asked to express all their thoughts verbally (<italic>think-aloud</italic>), as if they were speaking to themselves. If participants forgot to share their reasoning aloud, the examiner reminded them to share their thoughts with her after 15 seconds. Otherwise, the examiner would not intervene. If the task was too complex and the participant felt lost for more than a minute or decided to give up, the examiner offered assistance by providing hints to help the participant move forward in solving the task. When required, the experimenter could provide four types of help: (1) information (eg, explanation of how the participant arrived where they are or why the module includes certain content), (2) motivating question (eg, “Right, and where would you go now?”), (3) answer (if the participant asked a question related to the exploration), and (4) guidance (eg, if the participant lingered too long on an irrelevant page, tell him or her what the next step would help find the answer).</p>
        <p>At the end of each task, we asked participants, “Does the path to fulfil the task seems logical to you?” and “Do you have any suggestions for improvement?” to receive their qualitative feedback. Once the 7 tasks were completed, participants could easily browse the app at their ease if they wished to discover other functions or pages. To conclude, the experimenter asked a series of sociodemographic questions and questions that included items from two validated scales (System Usability Scale [SUS] [<xref ref-type="bibr" rid="ref30">30</xref>] and Mobile App Rating Scale [MARS] [<xref ref-type="bibr" rid="ref31">31</xref>]; <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>List and description of the tasks used during the think-aloud test procedure.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="120"/>
            <col width="280"/>
            <col width="310"/>
            <col width="290"/>
            <thead>
              <tr valign="top">
                <td>Task name</td>
                <td>Expected achievement</td>
                <td>Exact wording of the question</td>
                <td>Task considered as completed when</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Definition</td>
                <td>The participant discovers how to find definitions in the app.</td>
                <td>“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?”</td>
                <td>On the main page of the app, the participant clicks on the term <italic>surrogates</italic> (highlighted in green because it is a technical term) to pop up the definition; the participant finds the term on the <italic>definitions</italic> page of the app.</td>
              </tr>
              <tr valign="top">
                <td>Legal obligations</td>
                <td>The participant understands the logic of the green drop-down menu that allows accessing different pages within a section and finding specific legal information.</td>
                <td>“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?”</td>
                <td>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.</td>
              </tr>
              <tr valign="top">
                <td>Conversation starters</td>
                <td>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.</td>
                <td>“You want to find ways to start a conversation with your son about your advance directives. Where would you go in this application?”</td>
                <td>The participant discovered (1) the page <italic>It’s in the art</italic> or (2) the page <italic>discussion starters</italic> and verbalized that this could be used as a good conversation starter.</td>
              </tr>
              <tr valign="top">
                <td>Data confidentiality</td>
                <td>The participant finds the <italic>How it works</italic> pop up window that contains key elements for the process of writing advance directives and information on data confidentiality.</td>
                <td>“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?”</td>
                <td>The participant clicks on the button in the <italic>I write</italic> section and finds the relevant information.</td>
              </tr>
              <tr valign="top">
                <td>Filter function</td>
                <td>The participant discovers the filter function.</td>
                <td>“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?”</td>
                <td>The participant opens the filter function.</td>
              </tr>
              <tr valign="top">
                <td>Values and preferences</td>
                <td>The patient understands that the questionnaire is divided into several subsections and can make sense of their content by reading their title.</td>
                <td>“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?”</td>
                <td>The participant finds question 15 “A few words about my spirituality” situated in the subsection “My values and preferences” of the questionnaire.</td>
              </tr>
              <tr valign="top">
                <td>Finalize the questionnaire</td>
                <td>The participant understands how to export from the app his or her answers to the questionnaire.</td>
                <td>“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?”</td>
                <td>The participant clicks on the “Finalize and receive my questionnaire” button situated at the bottom of the questionnaire in the <italic>I write</italic> section.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Measures Used and Data Analysis</title>
        <sec>
          <title>Content Readability</title>
          <p>On the basis of a document containing the full content (in text format) of the app, we evaluated its readability, page by page, with the help of Scolarius [<xref ref-type="bibr" rid="ref32">32</xref>]. Influence Communication, a Canadian media analysis organization, developed this test. The test score is calculated in the same way as the Flesch Reading Ease score (often used for evaluating English material). It calculates the length of words and paragraphs. It provides a score ranging between 50 and 250 to be interpreted as follows: a score between 50 and 89 corresponds to an elementary school level of education, between 90 and 119 indicates a high school level, between 120 and 149 indicates a college level, and between 150 and 189 indicates a university level.</p>
        </sec>
        <sec>
          <title>Tasks Evaluation</title>
          <sec>
            <title>Overview</title>
            <p>All the video recordings were double coded. CS ensured the first coding of all videos. CC and FE shared the task of the second coding. The recording of one participant was evaluated by 3 authors (CC, CS, and FE) to confirm unanimously that he met an exclusion criterion. Double codes were compared systematically. Whenever coders diverged in their evaluation, we applied the rules listed in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
            <table-wrap position="float" id="table2">
              <label>Table 2</label>
              <caption>
                <p>Rules used to arbitrate diverging evaluations in double coding.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="30"/>
                <col width="470"/>
                <col width="500"/>
                <thead>
                  <tr valign="top">
                    <td colspan="2">Object of comparison and type of divergence</td>
                    <td>Rule applied</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Task success</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>1-point difference between evaluations</td>
                    <td>Select the lowest score (to avoid desirability bias)</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>&#62;1 point difference between evaluations</td>
                    <td>Double check the recording and discuss the evaluation (CS, FE, and CC) until an agreement is reached</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Number of clicks</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>≥1 point differences between evaluations</td>
                    <td>CS watches the video again to find the correct number</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Time spent on task</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Difference between the 2 evaluations &#60;10%</td>
                    <td>Use the average time between the 2 evaluators</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Difference between the 2 evaluations &#62;10%</td>
                    <td>CS watches the video again and decides</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Type of errors and problems</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Evaluators did not record the same errors and problems encountered by participants</td>
                    <td>Discuss the evaluation (CS, FE, and CC) until an agreement is reached</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Categorization</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Different categorizations for 1 error or problem</td>
                    <td>Discuss the evaluation (CS, FE, and CC) until an agreement is reached</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="3">
                      <bold>Severity rate</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Differences between evaluations of the severity rate of an error or problem</td>
                    <td>Discuss the evaluation (CS, FE, and CC) until an agreement is reached</td>
                  </tr>
                </tbody>
              </table>
            </table-wrap>
          </sec>
          <sec>
            <title>Task Success</title>
            <p>We calculated the number of participants who succeeded or failed to complete the tasks, with or without input from the experimenter. For this, we used the following scoring logic: 0=participant failed because the experimenter eventually gave the answer, 1=succeeded but did not use the shortest path and received some help from the experimenter, 2=succeeded without help but did not use the shortest path, and 3=succeeded without help and easily found the shortest path.</p>
          </sec>
          <sec>
            <title>Clicks to Complete the Task</title>
            <p>For each task, we reported the number of clicks needed to complete the task. Note that some tasks required more clicks than others; participants did not always start from the same page to complete the task; and for tasks 1 and 3, two answer paths were possible.</p>
          </sec>
          <sec>
            <title>Time Spent on Task</title>
            <p>For each task, we calculated the number of seconds required by the participants to complete it. Counting started when the experimenter finished formulating the question for the first time and ended when the participant successfully completed the required task (detailed in <xref ref-type="table" rid="table1">Table 1</xref>, right column). Whenever participants started to digress during task completion (eg, made critical comments on the design of the app or expressed a personal memory), this <italic>digression time</italic> was calculated and subtracted.</p>
          </sec>
          <sec>
            <title>Errors and Problems Encountered</title>
            <p>We recorded the errors and problems that the participants encountered while completing the 7 tasks. Each problem encountered was described in a Microsoft Excel file, categorized according to the heuristics of Bastien and Scapin [<xref ref-type="bibr" rid="ref33">33</xref>] (information density, consistency, and significance of codes), and given a severity rate following the Nielsen Norman Group recommendations [<xref ref-type="bibr" rid="ref27">27</xref>]: 0=disagreement that this is a usability problem at all, 1=cosmetic problem only—need not be fixed unless extra time is available, 2=minor usability problem: fixing this should be given low priority, 3=major usability problem: important to fix and should be given high priority, and 4=usability catastrophe—imperative to fix this before the product can be released.</p>
          </sec>
          <sec>
            <title>Participants’ Feedback</title>
            <p>Participants’ feedback after completing each task was coded as follows: 0=no, the path to complete the task makes no sense to me; 1=yes, it is more or less logical; and 2=yes, it is very logical. We took note of further comments made by the participants during the think-aloud tasks. We only reported comments that (1) were relevant to the objectives of the app and (2) contained proposals or ideas for improvements that could be realistically developed. We categorized comments as <italic>useful for improving the app in the short term</italic> or <italic>useful for future developments</italic>.</p>
          </sec>
        </sec>
        <sec>
          <title>Questionnaire</title>
          <sec>
            <title>Usability Assessment</title>
            <p>To assess the app’s usability, we used the 10-item SUS questionnaire [<xref ref-type="bibr" rid="ref30">30</xref>] suited for evaluating digital products. The SUS contains ten 5-point Likert score questions, allowing the calculation of a total score ranging between 0 and 100 (each question has a 10-point value). This indicates the effectiveness, efficiency, and overall ease of use of this app. A score of approximately 85 is considered excellent, approximately 72 is good, approximately 53 is acceptable, and approximately 38 is poor. Note that the first SUS question (“I think that I would like to use this system frequently”) is not relevant for the evaluation of <italic>Accordons-nous</italic>, as discussing end-of-life issues and writing AD is not an everyday activity. To address this issue, we added a slightly different first question to the 10 original SUS items (1bis), as follows: “I think that if I need to learn about advance care planning and want to write my advance directives, I would give priority to using this application.” This allowed the calculation of two SUS score: one with the standard scale; the other with question 1bis instead of question 1.</p>
          </sec>
          <sec>
            <title>Relevance Assessment</title>
            <p>To obtain participants’ evaluation of the impact of the app on the user’s awareness, knowledge, attitudes, intentions to change, and the likelihood of actual change in ACP behavior, we used the 6 <italic>perceived impact</italic> items (section F) of the validated MARS questionnaire [<xref ref-type="bibr" rid="ref31">31</xref>]. The MARS questionnaire is particularly interesting as it was developed on the basis of the transtheoretical model of behavior change by Prochaska [<xref ref-type="bibr" rid="ref13">13</xref>], which is commonly used in ACP literature to evaluate participants’ change in ACP engagement [<xref ref-type="bibr" rid="ref34">34</xref>]. It allows calculating the overall mean 5-point Likert scores, to be interpreted as follows: 1=inadequate, 2=poor, 3=acceptable, 4=good, and 5=excellent.</p>
          </sec>
          <sec>
            <title>Subjective Endorsement</title>
            <p>To observe whether participants endorsed the app, we adapted the first 5-point Likert items of the MARS <italic>subjective quality</italic> (section E) questionnaire. We asked participants whether they would recommend this app to the following three target groups: patients, health professionals, and patients’ caring relatives.</p>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Participants</title>
        <p>We obtained responses from 10 participants for all tasks and questions. During the study, we had to exclude 2 more participants: one because of technical problems (the sound recording did not work, making it impossible to analyze the results) and a second as he failed to understand 5 out of the 7 tasks that they were asked to perform, despite 3 iterations of the instructions.</p>
        <p>Our data set included 60% (6/10) women and 40% (4/10) men of various ages (youngest: 31 years, oldest: 68 years; mean 50.8, SD 14.6 years). Of the 10 participants, 9 (90%) used devices running on iOS, and 1 (10%) used a device running on Android. All participants used these devices daily and showed minimal understanding of the notion of AD, thereby fulfilling our inclusion criteria.</p>
      </sec>
      <sec>
        <title>Content Readability</title>
        <p>The overall Scolarius score of the app was 87.43/250, meaning that the app was readable for people with an elementary school level of education. However, some pages of the app require high school–level education. <xref ref-type="table" rid="table3">Table 3</xref> provides the details of the score.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Scolarius scores of the app Accordons-nous, per page.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="570"/>
            <col width="150"/>
            <col width="80"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>Page of the app</td>
                <td>Number of words</td>
                <td>Score</td>
                <td>Level of education</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td><italic>L’essentiel</italic> (key information)</td>
                <td>254</td>
                <td>100</td>
                <td>High school</td>
              </tr>
              <tr valign="top">
                <td><italic>Histoires de vie</italic> (short life stories)</td>
                <td>893</td>
                <td>94</td>
                <td>High school</td>
              </tr>
              <tr valign="top">
                <td><italic>Que dit la loi?</italic> (Swiss legal information)</td>
                <td>876</td>
                <td>89</td>
                <td>Elementary school</td>
              </tr>
              <tr valign="top">
                <td><italic>Définitions</italic> (definitions)</td>
                <td>1661</td>
                <td>99</td>
                <td>High school</td>
              </tr>
              <tr valign="top">
                <td><italic>Amorces de discussion</italic> (discussion starters)</td>
                <td>312</td>
                <td>60</td>
                <td>Elementary school</td>
              </tr>
              <tr valign="top">
                <td><italic>C’est dans l’art</italic> (works of art)</td>
                <td>3665</td>
                <td>70</td>
                <td>Elementary school</td>
              </tr>
              <tr valign="top">
                <td><italic>I write</italic> (filters and questionnaires)</td>
                <td>3105</td>
                <td>100</td>
                <td>High school</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Tasks Evaluation</title>
        <sec>
          <title>Task Success</title>
          <p>In 66% (46/70) of the cases, participants succeeded in completing a task without any help and easily found the shortest path (<xref rid="figure4" ref-type="fig">Figure 4</xref>). In 14% (10/70) of the cases, they succeeded without help; however, they did not take the shortest path. In 16% (11/70) of the cases, they succeeded without using the shortest route and needed some help from the experimenter. In 4% (3/70) of the cases, the experimenter eventually gave the answer. This 4% corresponds to 3 cases of failure, involving 30% (3/10) different participants. One failure on the task <italic>definition</italic> was obviously because this participant experienced a temporary state of panic at the beginning of the test and failed to grasp what the experimenter asked them to do (they struggled to find the right definition without looking at the app). In the case of the second failure, on the <italic>legal obligations</italic> task, the participant understood the logic of the drop-down menu within a section and therefore kept switching between the 3 main sections by using the bottom menu. The third failure was on the <italic>conversation starters</italic> task and seemed to be because of participants’ misunderstanding of the meaning of the three main sections: they reported having assumed that sections <italic>I talk about it</italic> and <italic>I write</italic> contained contact forms and therefore thought that this was not the place to find the conversation starters. Furthermore, once they discovered the section <italic>I talk about it</italic> (following guidance from the experimenter), they did not click on the green drop-down menu (a function that they had correctly discovered in task 1).</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Proportion 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.</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Clicks to Complete the Task</title>
          <p>Participants’ actual number of clicks needed is illustrated in <xref rid="figure5" ref-type="fig">Figure 5</xref>. During the test, we noticed that the participants struggled to find a direct path toward data confidentiality information (task 4). We wondered whether this difficulty was affected by the order in which the questions were presented. To check this, in the last 2 interviews of the think-aloud procedure, we changed the order of the questions as follows: 1, 2, 3, 6, 4, 5, and 7. The change in order did not help to complete task 4 faster.</p>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Distribution of the number of clicks needed for participants to complete each of the 7 tasks.</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Time Spent on Task</title>
          <p>Participants’ actual time spent on the tasks is shown in <xref rid="figure6" ref-type="fig">Figure 6</xref>. Overall, these results indicate that participants encountered more difficulties in completing the tasks <italic>legal obligations,</italic> <italic>conversation starters</italic>, and <italic>data confidentiality</italic>. They encountered little difficulty in completing the last 3 tasks.</p>
          <p><xref rid="figure7" ref-type="fig">Figure 7</xref> shows that there are important differences between participants: some participants navigated without difficulties, whereas others struggled on several tasks. Some participants needed much more time than others to complete their tasks; for instance, participant 10 used twice more time than participant 7 to successfully complete the tasks. Obviously, participants who needed help from the experimenter took much more time; for instance, participant 3 spent three-fourths of the whole test time on 1 task, for which they needed help.</p>
          <p>The participants who succeeded in all tasks (4/10, 40%) were aged 31, 42, 56, and 66 years, indicating that the app is also understandable for older users.</p>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Distribution of time (in seconds) spent by participants completing each of the 7 tasks.</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure7" position="float">
            <label>Figure 7</label>
            <caption>
              <p>Total 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.</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Errors and Problems Encountered</title>
          <p>In total, we recorded 44 problems encountered by the participants while completing the 7 tasks. Following the Bastien and Scapin [<xref ref-type="bibr" rid="ref33">33</xref>] grouping method, we clustered them into 17 types of problems (<xref ref-type="table" rid="table4">Table 4</xref>). Of these problems, none were considered as a <italic>usability catastrophe</italic>, 50% (22/44) were considered as <italic>major usability problems</italic>, 48% (21/44) as <italic>minor usability problems</italic>, and the last 2% (1/44) as <italic>not a usability problem at all</italic>.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>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.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="40"/>
              <col width="180"/>
              <col width="530"/>
              <col width="220"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Item and problem</td>
                  <td>Category (numbered according to Bastien and Scapin [<xref ref-type="bibr" rid="ref33">33</xref>])</td>
                  <td>Description of the problem</td>
                  <td>Task in which it occurred (frequency of occurrence)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Major usability problems (according to Nielsen Norman Group recommendations [<xref ref-type="bibr" rid="ref27">27</xref>])</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>1</td>
                  <td>1.2. Grouping or distinction of items</td>
                  <td>Users did not click on the green drop-down menu and therefore missed much of the content of the module.</td>
                  <td>Legal obligations (3); Conversation starters (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>2</td>
                  <td>7. Significance of codes</td>
                  <td>Users did not search for the information about the confidentiality of their AD<sup>a</sup> in the right place: they felt that this information should have been located elsewhere in the app (for instance, in <italic>I get information</italic>, <italic>What does the law say</italic>, instead of <italic>I write</italic>, <italic>How it works</italic>, page).</td>
                  <td>Data confidentiality (5)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>3</td>
                  <td>1.3. Immediate feedback</td>
                  <td>Users expected feedback linked to the filter function in the <italic>I write</italic> section: the module did not provide feedback when a filter was selected. Therefore, users did not know whether their choice was taken into account.</td>
                  <td>Filter function (4)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>4</td>
                  <td>8. Compatibility</td>
                  <td>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 <italic>Concerto</italic>.</td>
                  <td>Conversation starters (1); Data confidentiality (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>5</td>
                  <td>2.2 Information density</td>
                  <td>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 <italic>It’s in the art</italic> page, some users got <italic>stuck</italic> to discovering the different works of art.</td>
                  <td>Legal obligations (1); Conversation starters (2)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>6</td>
                  <td>1.4 Legibility</td>
                  <td>One user found that the bottom menu is too small and that the font does not offer sufficient contrast.</td>
                  <td>Conversation starters (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>7</td>
                  <td>7. Significance of codes</td>
                  <td>One user did not find the filter function explicit enough.</td>
                  <td>Filter function (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>8</td>
                  <td>8. Compatibility</td>
                  <td>One user was confused by the fact that on the first page, the title of the section <italic>I get information</italic> is larger than the title of the module.</td>
                  <td>Definition (1)</td>
                </tr>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Minor usability problems</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>9</td>
                  <td>7. Significance of codes</td>
                  <td>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 <italic>Accordons-nous</italic> but to the host app, <italic>Concerto</italic>.</td>
                  <td>Definition (1); Legal obligations (2); Conversation starters (3)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>10</td>
                  <td>7. Significance of codes and 8. Compatibility</td>
                  <td>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 <italic>Accordons-nous</italic>. However, this menu brought the user to the main menu of the host app, <italic>Concerto</italic>. Users were confused by this response and did not always understand where they had quit <italic>Accordons-nous</italic>.</td>
                  <td>Legal obligations (1); Conversation starters (2); Data confidentiality (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>11</td>
                  <td>8. Compatibility</td>
                  <td>Some users were looking for a main <italic>home page</italic> of the module; however, this page does not exist.</td>
                  <td>Definition (1); Data confidentiality (1); Values and preferences (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>12</td>
                  <td>7. Significance of codes and 8. Compatibility</td>
                  <td>Two users expected that the <italic>I talk about it</italic> and <italic>I write</italic> sections would work as a <italic>contact us</italic> page, which was not the case.</td>
                  <td>Conversation starters (2)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>13</td>
                  <td>1.4 Legibility</td>
                  <td>One user assessed the font size of the text as too small and the font contrast as insufficient.</td>
                  <td>Definition (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>14</td>
                  <td>1.2 Grouping or distinction of items</td>
                  <td>One user did not see the <italic>How does it work?</italic> button (section <italic>I write</italic>).</td>
                  <td>Data confidentiality (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>15</td>
                  <td>7. Significance of codes</td>
                  <td>One user did not see the <italic>Filter function</italic> button (section <italic>I write</italic>).</td>
                  <td>Filter function (1)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>16</td>
                  <td>8. Compatibility</td>
                  <td>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.</td>
                  <td>Finalize questionnaire (1)</td>
                </tr>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Problem that we did not consider to be a usability issue</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>17</td>
                  <td>8. Compatibility</td>
                  <td>One user complained that the app does not contain a search function.</td>
                  <td>Definition (1)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>AD: advance directives.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Participants’ Feedback</title>
          <p>After completing a task, 64% (45/70) of the time, participants reported that the path to complete the task was <italic>very logical</italic>. In 31% (22/70) of the cases, they reported that it was more or less logical (the remaining 5% did not provide an answer). None of the participants found that the path to complete the task made no sense (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>).</p>
          <boxed-text id="box1" position="float">
            <title>List of comments made by participants that are useful in the short and long term for improving the app.</title>
            <p>
              <bold>Useful comments for short-term improvements</bold>
            </p>
            <list list-type="order">
              <list-item>
                <p>Overall, 40% (4/10) of the oldest participants mentioned that “you have to look everywhere” to understand how to navigate.</p>
              </list-item>
              <list-item>
                <p>Data privacy was a recurrent concern.</p>
              </list-item>
              <list-item>
                <p>In total, 30% (3/10) of participants pointed out that the font was very small, which may be problematic for elderly users.</p>
              </list-item>
              <list-item>
                <p>Many participants found that there might be too much to read in the app, especially given the fact that people tend to skip lengthy paragraphs.</p>
              </list-item>
              <list-item>
                <p>Many participants said that they liked the example responses provided in the questionnaire (for illustration, see <xref rid="figure8" ref-type="fig">Figure 8</xref>). However, to avoid overloading the module with text, we included these texts in a lighter gray within the response box. The text disappears once the user clicks on the text box to add his or her own response. Some participants would have preferred these examples to remain visible (be placed above the box) to “not forget anything.”</p>
              </list-item>
            </list>
            <p>
              <bold>Useful comments for long-term improvements</bold>
            </p>
            <list list-type="order">
              <list-item>
                <p>Some participants would have appreciated a search function.</p>
              </list-item>
              <list-item>
                <p>With this app, a participant expected to be able to make calls or contact people around him or health professionals at the Hopitaux Universitaires de Genève.</p>
              </list-item>
              <list-item>
                <p>A participant wished to have the function of electronic signature for signing the advance directives on the app.</p>
              </list-item>
              <list-item>
                <p>A participant wished for more options for disabled patients, such as a dictation function for people who cannot write.</p>
              </list-item>
            </list>
          </boxed-text>
          <fig id="figure8" position="float">
            <label>Figure 8</label>
            <caption>
              <p>Two 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.</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Questionnaire</title>
        <sec>
          <title>Usability Score</title>
          <p>As illustrated in <xref rid="figure9" ref-type="fig">Figure 9</xref> [<xref ref-type="bibr" rid="ref35">35</xref>], the app <italic>Accordons-nous</italic> scores very high on the SUS usability scale (85.25/100). When question 1 of the SUS was replaced with question 1bis, the total score increased to 90.5.</p>
          <fig id="figure9" position="float">
            <label>Figure 9</label>
            <caption>
              <p>Score of Accordons-nous on the SUS. SUS: System Usability Scale [<xref ref-type="bibr" rid="ref35">35</xref>].</p>
            </caption>
            <graphic xlink:href="humanfactors_v9i2e34626_fig9.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Relevance Score</title>
          <p>Participants’ evaluation of the relevance of the app for supporting the process of ACP and AD is reported in <xref ref-type="table" rid="table5">Table 5</xref>. Most notably, 90% (9/10) to 100% (10/10) of the participants agree or strongly agree that <italic>Accordons-nous</italic> is likely to increase knowledge about the topic and the motivation to address the topic and induce related behavior changes. These responses lead to a high adherence rate, with an overall score of 4.27/5.</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Participants’ evaluation of the relevance of Accordons-nous for improving ACP<sup>a</sup> and AD<sup>b</sup> (N=10).</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="120"/>
              <col width="320"/>
              <col width="120"/>
              <col width="100"/>
              <col width="100"/>
              <col width="100"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td>Measure</td>
                  <td>Question item</td>
                  <td colspan="5">Responses, n (%)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Strongly agree</td>
                  <td>Agree</td>
                  <td>No opinion</td>
                  <td>Disagree</td>
                  <td>Strongly disagree</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Awareness</td>
                  <td>This app is likely to increase awareness of the importance of (ACP and AD)</td>
                  <td>5 (50)</td>
                  <td>4 (40)</td>
                  <td>0 (0)</td>
                  <td>1 (10)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>Knowledge</td>
                  <td>This app is likely to increase knowledge or understanding of (ACP and AD)</td>
                  <td>9 (90)</td>
                  <td>1 (10)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>Attitude</td>
                  <td>This app is likely to change attitudes toward improving (ACP and AD)</td>
                  <td>3 (30)</td>
                  <td>4 (40)</td>
                  <td>3 (30)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>Intention to change</td>
                  <td>This app is likely to increase intentions or motivation to address (ACP and AD)</td>
                  <td>4 (40)</td>
                  <td>5 (50)</td>
                  <td>1 (10)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>Help seeking</td>
                  <td>Using this app is likely to encourage further help seeking for (ACP and AD)</td>
                  <td>1 (10)</td>
                  <td>5 (50)</td>
                  <td>3 (30)</td>
                  <td>1 (10)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>Behavior change</td>
                  <td>Using this app is likely to increase behavior change (ACP and AD)</td>
                  <td>4 (40)</td>
                  <td>6 (60)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>ACP: advance care planning.</p>
              </fn>
              <fn id="table5fn2">
                <p><sup>b</sup>AD: advance directives.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Subjective Endorsement</title>
          <p>Overall, participants endorsed <italic>Accordons-nous</italic>. Of the 10 participants, 9 (90%) recommended the app (2 times 4/5 and 7 times 5/5 on the Likert scale) for patients. Only 10% (1/10) of participants <italic>strongly disagreed</italic> (1/5, lowest score) to recommend the app to patients, arguing that a smartphone app is not suitable for an older audience, whom they found as not being at ease with such technology. However, 90% (9/10) participants <italic>strongly recommended</italic> (5/5) the app to health professionals. Only 10% (1/10) disagreed (2/5), arguing that the tool was primarily designed for patients, and therefore, a professional would not find it relevant to their practice. Finally, all participants recommended (1 time 4/5 and 9 times 5/5) the app to family caregivers. The mean endorsement over the 3 questions was 4.7/5.</p>
        </sec>
      </sec>
      <sec>
        <title>Modifications Made Based on Results</title>
        <p>The usability test revealed a series of issues that were addressed, as described in <xref ref-type="table" rid="table6">Table 6</xref>. <italic>Accordons-nous</italic> is an app in an app; that is, a module inserted in the larger host app <italic>Concerto</italic>. For this reason, some navigability issues could only be addressed by the <italic>Concerto</italic> team. <xref ref-type="table" rid="table7">Table 7</xref> describes the issues that we reported to <italic>Concerto</italic> and how they have been addressed.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>List of changes made to the app in response to the major issues identified.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="80"/>
            <col width="520"/>
            <col width="400"/>
            <thead>
              <tr valign="bottom">
                <td>Item<break/>(<xref ref-type="table" rid="table4">Table 4</xref>)</td>
                <td>Description of the issue</td>
                <td>Changes made</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1 and 6</td>
                <td>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.</td>
                <td>To overcome navigation difficulties, we created a motion design video [<xref ref-type="bibr" rid="ref36">36</xref>] (inserted on the first page of the app) containing navigation tutorial elements.</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>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 <italic>I get information</italic>, <italic>What does the law say</italic>, instead of the <italic>I write</italic>, <italic>How it works,</italic> page).</td>
                <td>We duplicated the information on “How is your privacy managed?” on the first page of the module.</td>
              </tr>
              <tr valign="top">
                <td>3 and 7</td>
                <td>Users expected feedback linked to the filter function in the <italic>I write</italic> section: the module did not provide feedback when a filter was selected; therefore, users did not know whether their choice was taken into account. One user did not find the filter function explicit enough.</td>
                <td>First, we changed the color and location of the <italic>How it works</italic> button to make it more visible and added a video tutorial to explain how to write and store advance directives [<xref ref-type="bibr" rid="ref23">23</xref>]. Second, we redesigned the filter page: we renamed and relocated the drop-down filter button to make it more explicit that it is a filter menu. Third, we added an automatic notification after the user has made a choice of filter.</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>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 <italic>It’s in the art</italic> page, some users got <italic>stuck</italic> on discovering the different works of art.</td>
                <td>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 <italic>I talk about it</italic> section, we preselected the entry page that contains less text to avoid a feeling of overload while navigating across sections.</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>One user was confused by the fact that on the first page, the title of the section <italic>I get information</italic> is larger than the title of the module.</td>
                <td>We removed the title of the app on all pages.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>List of problems that were notified to the Concerto team and changes made.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="80"/>
            <col width="540"/>
            <col width="380"/>
            <thead>
              <tr valign="bottom">
                <td>Item<break/>(<xref ref-type="table" rid="table4">Table 4</xref>)</td>
                <td>Reported problem</td>
                <td>Change made</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>9</td>
                <td>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 <italic>Accordons-nous</italic>. However, this button is linked to the host app <italic>Concerto</italic> and provides only log-in information, which is confusing for the user.</td>
                <td>The <italic>Concerto</italic> team removed the hamburger menu in <italic>Accordons-nous</italic> except when users are logged</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>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 <italic>Accordons-nous</italic>. However, this button brings the user to the front page of <italic>Concerto</italic>. This action involved quitting <italic>Accordons-nous</italic>, which also confused some of the users.</td>
                <td>The <italic>Concerto</italic> team changed the design of the button: instead of a house, it is now the pictogram of the <italic>Concerto</italic> home page</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>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 <italic>Concerto</italic>.</td>
                <td>None to this date</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>The <italic>Concerto</italic> text font (imposed to all modules, including <italic>Accordons-nous</italic>) was judged as too small and not dark enough (most text is in a shade of gray).</td>
                <td>None to this date</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p><italic>Accordons-nous</italic> is the first French-language mobile app for supporting the ACP process. In contrast to existing apps worldwide, which are limited in many respects [<xref ref-type="bibr" rid="ref21">21</xref>], it includes materials and functions that facilitate each stage of the ACP process. It provides all the relevant information in an accessible language. It includes tools and prompts to facilitate contemplation and discussions about the goals of care and end-of-life issues. It provides guidance on writing or updating comprehensive and personalized AD in a simple process. In line with professional recommendations [<xref ref-type="bibr" rid="ref22">22</xref>], it can be used as an icebreaker for starting discussions within families and as a follow-up to direct conversations with health professionals.</p>
        <p>In our usability test, participants succeeded in the 7 think-aloud tasks in 80% (56/70) of the cases without help from the experimenter. However, in 16% (11/70) of the cases, help was needed, indicating that the app needed some improvement. An analysis of the navigational errors and difficulties encountered revealed no usability catastrophe but a series of major usability problems. These can be addressed with minor modifications (<xref ref-type="table" rid="table6">Table 6</xref>).</p>
        <p>Our graphs indicate that participants performed better at completing the tasks over the course of the test, although the latter tasks were not necessarily easier to complete. We think that participants gradually became familiar and at ease with the logic of the app, which indicates that a few minutes of use are enough to grasp our tool. The easy-to-use character of the tool is particularly important [<xref ref-type="bibr" rid="ref15">15</xref>] as ACP is mainly relevant for older patients [<xref ref-type="bibr" rid="ref3">3</xref>] who are less used to digital devices. Our oldest participants (aged 66 and 68 years) fulfilled the think-aloud tasks well, indicating that age was not necessarily a limiting factor for using our tool. This is in line with previous results indicating that older patients are likely to use a platform for ADs with adequate design and support [<xref ref-type="bibr" rid="ref15">15</xref>]. Moreover, as we designed <italic>Accordons-nous</italic> as a tool to help engage in discussions with family and health care providers, even patients who are not accustomed to digital devices may obtain support from surrounding care providers.</p>
        <p>The app <italic>Accordons-nous</italic> obtained high scores on readability (overall score of 87.4 on the Scolarius test, corresponding to elementary school level). This is one of the best scores compared with other similar apps internationally [<xref ref-type="bibr" rid="ref21">21</xref>]. However, the language difficulty varies across different pages of the app. Owing to the inherent complexity of the ACP topic, this difficulty can only be partially addressed; we ensured that all technical terms in the app were clickable to pop up the definition and added 2 introductory motion design videos summarizing the main information in simple terms and with illustrations.</p>
        <p>Overall, our users provided very positive feedback on <italic>Accordons-nous.</italic> They assessed the app as likely to raise awareness of the importance of ACP and AD, increase knowledge of such topics, change attitudes and behaviors intention toward improving their own ACP, and encourage seeking further help to fulfill one’s ACP. Moreover, participants expressed a clear willingness to recommend the tool to relevant stakeholders, including patients, health professionals, and patients’ caring relatives. These are exciting results indicating that <italic>Accordons-nous</italic> is relevant and contains easily understandable content.</p>
        <p>However, among the few critical views expressed, it is worth noting that 10% (1/10) of patients disagreed that <italic>Accordons-nous</italic> may encourage further help seeking in engaging in ACP, and 30% (3/10) had no opinion on that question. This result may indicate that patients expect the tool to offer the possibility of sending direct calls for help (eg, sending a message to a task force of professional ACP facilitators). Indeed, during the test, 20% (2/10) of participants erroneously thought at first glance that the section <italic>I talk about it</italic> would provide such direct support service. For practical and organizational reasons, we were not able to provide direct access to private counseling with <italic>Accordons-nous</italic>, which is a limitation of the app.</p>
        <p>Our analysis of the main problems encountered by participants while completing the 7 think-aloud tasks indicates that some participants struggled with cognitive load: they failed a task or needed help to complete it as their attention was caught by the high density of information contained in some pages of the app. For instance, some participants got distracted by the long list of works of art that they discovered on the page <italic>works of art</italic>.</p>
        <p>Other difficulties were because some participants did not spontaneously grasp the logic of navigating the app. In particular, some participants did not immediately see that the app contained 3 sections accessible via the navigation bar at the bottom of the screen (this was needed to complete the task <italic>conversation starters</italic>), whereas other participants encountered difficulties with the logic of the drop-down menu that allows navigating different pages (this was needed to complete tasks <italic>legal obligation</italic> and <italic>conversation starters</italic>). These difficulties indicate that some improvements needed to be made to the tool, especially for users who are not familiar with smartphone apps.</p>
        <p>To address the main navigation difficulties and cognitive load because of the high information content, we included 2 introductory motion design videos in the app. In the first video [<xref ref-type="bibr" rid="ref36">36</xref>], we explained the aim of the app, why ACP is useful, how the app is structured (3 sections), and the main navigation functions (menu to navigate the 3 main sections and drop-down menu buttons). In the second video [<xref ref-type="bibr" rid="ref23">23</xref>], we explained how confidentiality issues are managed and how to write and store ADs with or without the help of the app.</p>
        <p>Regarding task <italic>data confidentiality</italic>, several participants struggled to find the information as they searched it in the <italic>I get informed</italic> section rather than in the <italic>I write</italic> section. For this task, half of the participants reported that the path to complete it was <italic>more or less logical</italic> (rather than <italic>very logical</italic>). This indicates that data about confidentiality should be duplicated in both sections to be more easily found. This is particularly important as previous studies indicate that users are concerned about privacy issues [<xref ref-type="bibr" rid="ref37">37</xref>]. We adapted the content of the app accordingly (<xref ref-type="table" rid="table6">Table 6</xref>).</p>
        <p>Our results must be interpreted while considering the limitations listed in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>. Some limitations are common to usability studies, whereas others are minor issues related to small deviations from the original study protocol.</p>
        <boxed-text id="box2" position="float">
          <title>List of identified limitations to our study.</title>
          <p>
            <bold>Choice of method</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>As our test includes a small number of participants, no statistical conclusion can be drawn from this study.</p>
            </list-item>
          </list>
          <p>
            <bold>Sampling method</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Owing to our sampling method (a small convenience selection of participants from the <italic>Patients as Partners Project</italic> at Hopitaux Universitaires de Genève), a courtesy bias [<xref ref-type="bibr" rid="ref38">38</xref>] may have inflated positive results. Therefore, it is important to pay particular attention to the critical feedback provided.</p>
            </list-item>
            <list-item>
              <p>It may be that participants were more trained in medical matters than ordinary users, and this may have affected our results. On the other hand, ordinary patients would have much more time to browse and discover the app than our participants.</p>
            </list-item>
          </list>
          <p>
            <bold>Test conditions</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Some failures or difficulties that we recorded may be because of the lack of time and stress induced by the test.</p>
            </list-item>
          </list>
          <p>
            <bold>Deviation from the study protocol</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>While writing the original protocol, we did not specify the exclusion criterion “Incapable of understanding the meaning of the questions and tasks required for the study.” However, we decided to exclude one participant on this criterion as he obviously did not grasp most of the tasks that we asked him to complete.</p>
            </list-item>
            <list-item>
              <p>During the test, we changed the order of the questions from 1-2-3-4-5-6-7 to 1-2-3-6-4-5-7 (see explanation in section <italic>Results</italic>, subsection <italic>Clicks to Complete the Task</italic>) The change of order did not help to complete task 4 faster. This change of order may have influenced the number of clicks to complete the tasks.</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The tool we developed is a novel solution for promoting ACP and AD. <italic>Accordons-nous</italic> is the first French-language mobile app developed by an interdisciplinary team of professionals in collaboration with target users. It includes a variety of content for prompting discussions related to medical emergency situations and end-of-life issues. It provides support for writing and easily updating AD on a smartphone or tablet. Considering the complexity and sensitivity of the process of ACP and given that we expect most users to be older people, we put special emphasis on producing easy-to-understand information, discussion prompts, and simple navigation principles. The results of our usability test with patients were very satisfying and helped us make the necessary final adjustments to our tool before making it available to the public. Further usability and efficacy tests involving health care professionals would help define whether the tool is also suitable for this population.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>The history of the development of Accordons-nous and the list of questions submitted to the participants.</p>
        <media xlink:href="humanfactors_v9i2e34626_app1.docx" xlink:title="DOCX File , 44 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">ACP</term>
          <def>
            <p>advance care planning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AD</term>
          <def>
            <p>advance directives</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">HUG</term>
          <def>
            <p>Hopitaux Universitaires de Genève</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">MARS</term>
          <def>
            <p>Mobile App Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank everyone who contributed to this project. In particular, The authors thank Inès Serre and Pierre Sutter (members of the Hopitaux Universitaires de Genève [HUG] <italic>Patients as Partners Project</italic>) for their availability and helpful critical feedback throughout the project; François Pierre Robert and Vincent Clavien (information technology professionals) for helping us to develop the first prototype; Antoine Geissbühler and Helena Bornet Dit Vorgeat (HUG Innovation Center), Marianne Rubio and Simon Schmitt (HUG Communication Department), André Koller and Catherine Chenaud (HUG patient and family information group) for their regular support and counseling throughout the project; the many professionals who provided critical feedback at different stages of content development, notably Samia Hurst, Bara Ricou, Thierry Fumeaux, Louise Penzenstadler, Ralf Jox, Sophie Pautex, Monika Escher, Marinette Ummel, Francesca Bosisio, Johanna Sommer, Katherine Blondon, Véronique Dauve, Gora Da Rocha, Sophie Courvoisier, Laurence Sechaud, Tanja Krones, Julia Sader, Beat Sottas, Catherine Hoeneger, Alex Mauron; and our 11 anonymous study participants.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>Our project benefited from the financial support of the Fondation Privée des Hopitaux Universitaires de Genève [<xref ref-type="bibr" rid="ref39">39</xref>], which is a nonprofit organization that was not involved in any step of this study. <italic>Accordons-nous</italic> is not a saleable product. It is included in the host app Concerto Hopitaux Universitaires de Genève, which can be downloaded for free. The authors have no financial interests to declare.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Tellez</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Deconstructing the complexities of advance care planning outcomes: what do we know and where do we go? A scoping review</article-title>
          <source>J Am Geriatr Soc</source>
          <year>2021</year>
          <month>01</month>
          <day>07</day>
          <volume>69</volume>
          <issue>1</issue>
          <fpage>234</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32894787"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/jgs.16801</pub-id>
          <pub-id pub-id-type="medline">32894787</pub-id>
          <pub-id pub-id-type="pmcid">PMC7856112</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>La planification anticipée concernant la santé, en particulier en cas d’incapacité de discernement (« Advance Care Planning »). Cadre général pour la Suisse</article-title>
          <source>Département fédéral de l'intérieur DFI</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.plateforme-soinspalliatifs.ch/sites/default/files/work/files/Rahmenkonzept_Gesundheitl_Vorausplanung_FR_rev.pdf">https://www.plateforme-soinspalliatifs.ch/sites/default/files/work/files/Rahmenkonzept_Gesundheitl_Vorausplanung_FR_rev.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rietjens</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Connolly</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Delden</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Drickamer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Droger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van der Heide</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Heyland</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Houttekier</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Janssen</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Orsi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Seymour</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jox</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Korfage</surname>
              <given-names>IJ</given-names>
            </name>
          </person-group>
          <article-title>Definition and recommendations for advance care planning: an international consensus supported by the European Association for Palliative Care</article-title>
          <source>Lancet Oncol</source>
          <year>2017</year>
          <month>09</month>
          <volume>18</volume>
          <issue>9</issue>
          <fpage>e543</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1016/S1470-2045(17)30582-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Walsh</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Cognitive transformation, dementia, and the moral weight of advance directives</article-title>
          <source>Am J Bioeth</source>
          <year>2020</year>
          <month>08</month>
          <day>06</day>
          <volume>20</volume>
          <issue>8</issue>
          <fpage>54</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1080/15265161.2020.1781955</pub-id>
          <pub-id pub-id-type="medline">32757910</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bosisio</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jox</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rubli Truchard</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Planning ahead with dementia: what role can advance care planning play? A review on opportunities and challenges</article-title>
          <source>Swiss Med Wkly</source>
          <year>2018</year>
          <month>12</month>
          <day>17</day>
          <volume>148</volume>
          <fpage>w14706</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.emh.ch/10.4414/smw.2018.14706"/>
          </comment>
          <pub-id pub-id-type="doi">10.4414/smw.2018.14706</pub-id>
          <pub-id pub-id-type="medline">30594990</pub-id>
          <pub-id pub-id-type="pii">Swiss Med Wkly. 2018;148:w14706</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vilpert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Borrat-Besson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Maurer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Borasio</surname>
              <given-names>GD</given-names>
            </name>
          </person-group>
          <article-title>Awareness, approval and completion of advance directives in older adults in Switzerland</article-title>
          <source>Swiss Med Wkly</source>
          <year>2018</year>
          <month>07</month>
          <day>16</day>
          <volume>148</volume>
          <fpage>w14642</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.emh.ch/10.4414/smw.2018.14642"/>
          </comment>
          <pub-id pub-id-type="doi">10.4414/smw.2018.14642</pub-id>
          <pub-id pub-id-type="medline">30141525</pub-id>
          <pub-id pub-id-type="pii">Swiss Med Wkly. 2018;148:w14642</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cattagni Kleiner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Santos-Eggimann</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Fustinoni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dürst</surname>
              <given-names>A-V</given-names>
            </name>
            <name name-style="western">
              <surname>Haunreiter</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rubli-Truchard</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Seematter-Bagnoud</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Advance care planning dispositions: the relationship between knowledge and perception</article-title>
          <source>BMC Geriatr</source>
          <year>2019</year>
          <month>04</month>
          <day>24</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>118</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcgeriatr.biomedcentral.com/articles/10.1186/s12877-019-1113-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12877-019-1113-3</pub-id>
          <pub-id pub-id-type="medline">31014271</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12877-019-1113-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC6480869</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schickedanz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schillinger</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Landefeld</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A clinical framework for improving the advance care planning process: start with patients' self-identified barriers</article-title>
          <source>J Am Geriatr Soc</source>
          <year>2009</year>
          <month>01</month>
          <volume>57</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/19170789"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.1532-5415.2008.02093.x</pub-id>
          <pub-id pub-id-type="medline">19170789</pub-id>
          <pub-id pub-id-type="pii">JGS2093</pub-id>
          <pub-id pub-id-type="pmcid">PMC2788611</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pautex</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Herrmann</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Zulian</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Role of advance directives in palliative care units: a prospective study</article-title>
          <source>Palliat Med</source>
          <year>2008</year>
          <month>10</month>
          <day>28</day>
          <volume>22</volume>
          <issue>7</issue>
          <fpage>835</fpage>
          <lpage>41</lpage>
          <pub-id pub-id-type="doi">10.1177/0269216308094336</pub-id>
          <pub-id pub-id-type="medline">18718993</pub-id>
          <pub-id pub-id-type="pii">0269216308094336</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Periyakoil</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Neri</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kraemer</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>No easy task: a mixed methods study of barriers to conducting effective end-of-life conversations reported by multi-specialty doctors (S776)</article-title>
          <source>J Pain Symptom Manag</source>
          <year>2015</year>
          <month>02</month>
          <volume>49</volume>
          <issue>2</issue>
          <fpage>446</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jpainsymman.2014.11.255</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Glickman</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Physician reluctance to discuss advance directives. An empiric investigation of potential barriers</article-title>
          <source>Arch Intern Med</source>
          <year>1994</year>
          <month>10</month>
          <day>24</day>
          <volume>154</volume>
          <issue>20</issue>
          <fpage>2311</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">7944853</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fried</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Redding</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Robbins</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Paiva</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>O'Leary</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Iannone</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Promoting advance care planning as health behavior change: development of scales to assess Decisional Balance, Medical and Religious Beliefs, and Processes of Change</article-title>
          <source>Patient Educ Couns</source>
          <year>2012</year>
          <month>01</month>
          <volume>86</volume>
          <issue>1</issue>
          <fpage>25</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21741194"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.pec.2011.04.035</pub-id>
          <pub-id pub-id-type="medline">21741194</pub-id>
          <pub-id pub-id-type="pii">S0738-3991(11)00223-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC3192927</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Prochaska</surname>
              <given-names>JO</given-names>
            </name>
            <name name-style="western">
              <surname>Velicer</surname>
              <given-names>WF</given-names>
            </name>
          </person-group>
          <article-title>The transtheoretical model of health behavior change</article-title>
          <source>Am J Health Promot</source>
          <year>1997</year>
          <month>09</month>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>38</fpage>
          <lpage>48</lpage>
          <pub-id pub-id-type="doi">10.4278/0890-1171-12.1.38</pub-id>
          <pub-id pub-id-type="medline">10170434</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woolfolk</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Doris</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Darley</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Identification, situational constraint, and social cognition: studies in the attribution of moral responsibility</article-title>
          <source>Cognition</source>
          <year>2006</year>
          <month>06</month>
          <volume>100</volume>
          <issue>2</issue>
          <fpage>283</fpage>
          <lpage>301</lpage>
          <pub-id pub-id-type="doi">10.1016/j.cognition.2005.05.002</pub-id>
          <pub-id pub-id-type="medline">16087171</pub-id>
          <pub-id pub-id-type="pii">S0010-0277(05)00091-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Portz</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Lum</surname>
              <given-names>HD</given-names>
            </name>
            <name name-style="western">
              <surname>Bull</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Boxer</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Bekelman</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Ford</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Gleason</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Casillas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bayliss</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Perceptions of patient portal use for advance directive documentation among older adults with multiple chronic conditions</article-title>
          <source>J Soc Work End Life Palliat Care</source>
          <year>2020</year>
          <month>06</month>
          <day>01</day>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>238</fpage>
          <lpage>49</lpage>
          <pub-id pub-id-type="doi">10.1080/15524256.2020.1771806</pub-id>
          <pub-id pub-id-type="medline">32482160</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fine</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Spivey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Boardman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Courtney</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Early experience with digital advance care planning and directives, a novel consumer-driven program</article-title>
          <source>Proc (Bayl Univ Med Cent)</source>
          <year>2016</year>
          <month>07</month>
          <day>11</day>
          <volume>29</volume>
          <issue>3</issue>
          <fpage>263</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27365867"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/08998280.2016.11929430</pub-id>
          <pub-id pub-id-type="medline">27365867</pub-id>
          <pub-id pub-id-type="pmcid">PMC4900765</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van der Smissen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Overbeek</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Dulmen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>van der Heide</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rietjens</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Korfage</surname>
              <given-names>IJ</given-names>
            </name>
          </person-group>
          <article-title>The feasibility and effectiveness of web-based advance care planning programs: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>03</month>
          <day>17</day>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>e15578</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/3/e15578/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15578</pub-id>
          <pub-id pub-id-type="medline">32181750</pub-id>
          <pub-id pub-id-type="pii">v22i3e15578</pub-id>
          <pub-id pub-id-type="pmcid">PMC7109619</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Boscardin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Feuz</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Katen</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>DE</given-names>
            </name>
          </person-group>
          <article-title>Effect of the PREPARE website vs an easy-to-read advance directive on advance care planning documentation and engagement among veterans: a randomized clinical trial</article-title>
          <source>JAMA Intern Med</source>
          <year>2017</year>
          <month>08</month>
          <day>01</day>
          <volume>177</volume>
          <issue>8</issue>
          <fpage>1102</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28520838"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2017.1607</pub-id>
          <pub-id pub-id-type="medline">28520838</pub-id>
          <pub-id pub-id-type="pii">2627902</pub-id>
          <pub-id pub-id-type="pmcid">PMC5710440</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Howard</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fyles</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Barwich</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bernard</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Elston</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Heyland</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>McFee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mroz</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Slaven</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Heyland</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Effect of an interactive website to engage patients in advance care planning in outpatient settings</article-title>
          <source>Ann Fam Med</source>
          <year>2020</year>
          <month>03</month>
          <day>09</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>110</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.annfammed.org/cgi/pmidlookup?view=long&#38;pmid=32152014"/>
          </comment>
          <pub-id pub-id-type="doi">10.1370/afm.2471</pub-id>
          <pub-id pub-id-type="medline">32152014</pub-id>
          <pub-id pub-id-type="pii">18/2/110</pub-id>
          <pub-id pub-id-type="pmcid">PMC7062494</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Feuz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Farrell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>DE</given-names>
            </name>
          </person-group>
          <article-title>A novel website to prepare diverse older adults for decision making and advance care planning: a pilot study</article-title>
          <source>J Pain Symptom Manag</source>
          <year>2014</year>
          <month>04</month>
          <volume>47</volume>
          <issue>4</issue>
          <fpage>674</fpage>
          <lpage>86</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0885-3924(13)00386-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jpainsymman.2013.05.023</pub-id>
          <pub-id pub-id-type="medline">23972574</pub-id>
          <pub-id pub-id-type="pii">S0885-3924(13)00386-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC4111443</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McDarby</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Llaneza</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>George</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kozlov</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Mobile applications for advance care planning: a comprehensive review of features, quality, content, and readability</article-title>
          <source>Am J Hosp Palliat Care</source>
          <year>2021</year>
          <month>08</month>
          <day>17</day>
          <volume>38</volume>
          <issue>8</issue>
          <fpage>983</fpage>
          <lpage>94</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32938207"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1049909120959057</pub-id>
          <pub-id pub-id-type="medline">32938207</pub-id>
          <pub-id pub-id-type="pmcid">PMC7965780</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>MacKenzie Greenle</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sayani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Meghani</surname>
              <given-names>SH</given-names>
            </name>
          </person-group>
          <article-title>Identifying mobile apps targeting palliative care patients and family members</article-title>
          <source>J Palliat Med</source>
          <year>2018</year>
          <month>10</month>
          <volume>21</volume>
          <issue>10</issue>
          <fpage>1380</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1089/jpm.2018.0157</pub-id>
          <pub-id pub-id-type="medline">30312126</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>HUG Anticipation 02</article-title>
          <source>YouTube</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=j4FF56f0XuY">https://www.youtube.com/watch?v=j4FF56f0XuY</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>Hackathons des HUG</article-title>
          <source>HUG - Hôpitaux Universitaires Genève</source>
          <access-date>2022-04-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hug.ch/centre-innovation/hackathon">https://www.hug.ch/centre-innovation/hackathon</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <article-title>What is Patients as Partners?</article-title>
          <source>HUG - Hôpitaux Universitaires Genève</source>
          <access-date>2022-04-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hug.ch/en/patients-partenaires/what-patients-partners">https://www.hug.ch/en/patients-partenaires/what-patients-partners</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mangal</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>AngularJS: a modern MVC framework in JavaScript</article-title>
          <source>J Global Res Comput Sci</source>
          <year>2014</year>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>17</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rroij.com/open-access/angularjs-a-modern-mvc-framework-in-javascript.php?aid=52578"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nielson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Landauer</surname>
              <given-names>TK</given-names>
            </name>
          </person-group>
          <article-title>A mathematical model of the finding of usability problems</article-title>
          <source>Proceedings of the INTERACT '93 and CHI '93 Conference on Human Factors in Computing Systems</source>
          <year>1993</year>
          <conf-name>INTERCHI93: Conference on Human Factors in Computing</conf-name>
          <conf-date>Apr 24 - 29, 1993</conf-date>
          <conf-loc>Amsterdam, The Netherlands</conf-loc>
          <pub-id pub-id-type="doi">10.1145/169059.169166</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albert</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tullis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Albert</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <source>Measuring the User Experience Collecting, Analyzing, and Presenting Usability Metrics</source>
          <year>2010</year>
          <publisher-loc>Amsterdam, Netherlands</publisher-loc>
          <publisher-name>Elsevier Science</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Steen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>van den Bos</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Geenen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The think aloud method: a guide to user interface design</article-title>
          <source>Int J Med Inform</source>
          <year>2004</year>
          <month>11</month>
          <volume>73</volume>
          <issue>11-12</issue>
          <fpage>781</fpage>
          <lpage>95</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2004.08.003</pub-id>
          <pub-id pub-id-type="medline">15491929</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(04)00182-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brooke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>SUS: a 'quick and dirty' usability scale</article-title>
          <source>Usability Evaluation In Industry</source>
          <year>1996</year>
          <publisher-loc>Boca Raton, Florida</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stoyanov</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Hides</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kavanagh</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Zelenko</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Tjondronegoro</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mani</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile app rating scale: a new tool for assessing the quality of health mobile apps</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2015</year>
          <month>03</month>
          <day>11</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e27</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/1/e27/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id>
          <pub-id pub-id-type="medline">25760773</pub-id>
          <pub-id pub-id-type="pii">v3i1e27</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376132</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>Scolarius homepage</article-title>
          <source>Scolarius</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scolarius.com/">https://www.scolarius.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bastien</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Scapin</surname>
              <given-names>DL</given-names>
            </name>
          </person-group>
          <article-title>A validation of ergonomic criteria for the evaluation of human‐computer interfaces</article-title>
          <source>Int J Human Comput Interact</source>
          <year>1992</year>
          <month>04</month>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>183</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.1080/10447319209526035</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van Scoy</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Reading</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Chuang</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Levi</surname>
              <given-names>BH</given-names>
            </name>
          </person-group>
          <article-title>Can playing an end-of-life conversation game motivate people to engage in advance care planning?</article-title>
          <source>Am J Hosp Palliat Care</source>
          <year>2017</year>
          <month>09</month>
          <day>12</day>
          <volume>34</volume>
          <issue>8</issue>
          <fpage>754</fpage>
          <lpage>61</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27406696"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1049909116656353</pub-id>
          <pub-id pub-id-type="medline">27406696</pub-id>
          <pub-id pub-id-type="pii">1049909116656353</pub-id>
          <pub-id pub-id-type="pmcid">PMC6055477</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bangor</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kortum</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Determining what individual SUS scores mean: adding an adjective rating scale</article-title>
          <source>J Usab Stud</source>
          <year>2009</year>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>114</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.5555/2835587.2835589</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <article-title>HUG Anticipation 01</article-title>
          <source>YouTube</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=KTKYsOPyNMQ">https://www.youtube.com/watch?v=KTKYsOPyNMQ</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sakaguchi-Tang</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Bosold</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>YK</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Patient portal use and experience among older adults: systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2017</year>
          <month>10</month>
          <day>16</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2017/4/e38/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.8092</pub-id>
          <pub-id pub-id-type="medline">29038093</pub-id>
          <pub-id pub-id-type="pii">v5i4e38</pub-id>
          <pub-id pub-id-type="pmcid">PMC5662789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Evan</surname>
              <given-names>WM</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>Differential effects on response bias of computer vs. conventional administration of a social science questionnaire: an exploratory methodological experiment</article-title>
          <source>Syst Res</source>
          <year>1969</year>
          <month>05</month>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>216</fpage>
          <lpage>27</lpage>
          <pub-id pub-id-type="doi">10.1002/bs.3830140306</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <source>Fondation privée des HUG</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fondationhug.org/">https://www.fondationhug.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
