<?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">v12i1e48221</article-id>
      <article-id pub-id-type="pmid">40101207</article-id>
      <article-id pub-id-type="doi">10.2196/48221</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>Illustrating User Needs for eHealth With Experience Map: Interview Study With Chronic Kidney Disease Patients</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>Koizumi</surname>
            <given-names>Naoru</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Eriksen</surname>
            <given-names>Jeppe</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Valkonen</surname>
            <given-names>Paula</given-names>
          </name>
          <degrees>MA (Art and Des)</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Computer Science</institution>
            <institution>Aalto University</institution>
            <addr-line>P.O. Box 15400</addr-line>
            <addr-line>Espoo, 00076</addr-line>
            <country>Finland</country>
            <phone>358 947001</phone>
            <email>paula.valkonen@aalto.fi</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4954-9585</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Hölsä</surname>
            <given-names>Sini</given-names>
          </name>
          <degrees>MSc (Tech)</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1655-7650</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Viitanen</surname>
            <given-names>Johanna</given-names>
          </name>
          <degrees>MSc (Tech), LicSc (Tech), DSc (Tech)</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6659-5022</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Leinonen</surname>
            <given-names>Sini</given-names>
          </name>
          <degrees>MSc (Tech)</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0000-0744-3398</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Karisalmi</surname>
            <given-names>Nina</given-names>
          </name>
          <degrees>MSc (Tech)</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3020-1589</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Rauta</surname>
            <given-names>Virpi</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0239-2661</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Computer Science</institution>
        <institution>Aalto University</institution>
        <addr-line>Espoo</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Nephrology</institution>
        <institution>University of Helsinki</institution>
        <institution>Helsinki University Central Hospital</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Helsinki University Hospital</institution>
        <institution>Abdominal Center</institution>
        <institution>Nephrology</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Paula Valkonen <email>paula.valkonen@aalto.fi</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>3</month>
        <year>2025</year>
      </pub-date>
      <volume>12</volume>
      <elocation-id>e48221</elocation-id>
      <history>
        <date date-type="received">
          <day>16</day>
          <month>4</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>18</day>
          <month>9</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>12</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>15</day>
          <month>1</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Paula Valkonen, Sini Hölsä, Johanna Viitanen, Sini Leinonen, Nina Karisalmi, Virpi Rauta. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 18.03.2025.</copyright-statement>
      <copyright-year>2025</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/2025/1/e48221" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Chronic kidney disease (CKD) is a common condition worldwide and home dialysis (HD) provides economic, quality of life, and clinical advantages compared to other dialysis modalities. Human-centered design aims to support the development of eHealth solutions with high usability and user experience. However, research on the eHealth needs of patients using HD is scarce.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to support the design of eHealth for patients with CKD, particularly for patients using HD, by developing a kidney disease experience map that illustrates user needs, concerns, and barriers. The research questions were (1) what experiences do patients, particularly older adults, have in their everyday lives with CKD? (2) what user needs do patients with CKD have for HD eHealth? (3) how can these needs be illustrated using the experience map technique? The study focused on patients aged &#62;60 years, as they are at a higher risk of chronic conditions. The study was conducted as part of the eHealth in HD project, coordinated by Hospital District of Helsinki and Uusimaa, Finland.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>In total, 18 patients in different care modalities participated in retrospective interviews conducted between October 2020 and April 2021. The interviews included a preliminary task with patient journey illustrations and questions about their experiences and everyday lives with CKD. The data analysis was conducted using a thematic analysis approach and the process included several phases.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>On the basis of the thematic analysis, 5 categories were identified: healthy habits, concerns about and barriers to eHealth use, digital communication, patients’ emotions, and everyday life with CKD. These were illustrated in the first version of the kidney disease experience map. The patients had different healthy habits regarding social life, sports, and other activities. They had challenges with poorly functioning eHealth software and experienced other factors, such as a lack of interest and lack of skills for eHealth use. Technical devices do not always meet the emotional or physical needs of their users. This caused feelings of frustration, worry, and fear in patients, yet also fostered situational awareness and hope.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The experience map is a promising method for illustrating user needs and communicating the patient’s voice for eHealth development. eHealth offers possibilities to support patient’s everyday life with chronic disease. The patient’s situation and capacity to use eHealth solutions vary with their everyday challenges, opportunities, and their current stage of treatment. The kidney disease experience map will be used and further developed in the ongoing research project “Better Health at Home—Optimized Human-Centered Care of Predialysis and Home Dialysis Patients” (2022 to 2026).</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>user need</kwd>
        <kwd>chronic illness</kwd>
        <kwd>kidney disease</kwd>
        <kwd>older adult</kwd>
        <kwd>eHealth</kwd>
        <kwd>experience map</kwd>
        <kwd>human-centered design</kwd>
        <kwd>home dialysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Chronic kidney disease (CKD) is a common condition worldwide. It has been estimated that 11% to 13% of the population in high-income countries have CKD. The number of patients with advanced kidney disease is growing 5% to 7% per year [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. The prevalence of CKD is highest among older adults, ranging from 38% to 44% in patients aged &#62;65 years [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. In total 2.05 million people were treated with dialysis worldwide in 2010 [<xref ref-type="bibr" rid="ref2">2</xref>]. In 2017, 1.2 million people died globally because of CKD [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>Patients with end-stage CKD need kidney transplants or dialysis to survive. Dialysis can be performed in a dialysis unit in a hospital (ie, in-center dialysis), in a satellite dialysis unit, or at home using peritoneal dialysis or hemodialysis. The dialysis modality may vary depending on the patient’s current health and life situation. Both in-center and satellite dialysis can be laborious for patients [<xref ref-type="bibr" rid="ref6">6</xref>] and impose a heavy financial burden on medical care [<xref ref-type="bibr" rid="ref7">7</xref>]. Therefore, home dialysis (HD) provides better quality of life and clinical advantages and empowers patients by providing them with more flexibility in their everyday lives [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
        <p>Even though bringing dialysis treatment to a patient’s home might be burdensome and complicated for both the patient and the health care unit [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], there is a common understanding that HD prevalence needs to increase [<xref ref-type="bibr" rid="ref1">1</xref>]. HD creates opportunities to improve the patient’s safety and quality of life, as well as to support self-management of health [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. HD has also proven to be feasible for older adults, even though challenges such as fear of needles or doubts about handling them, or other physical limitations have been recognized [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>Research advises a holistic eHealth design that integrates technologies, end users, and use contexts [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Using human-centered design (HCD) approach [<xref ref-type="bibr" rid="ref16">16</xref>], our study aimed to support the design of eHealth for patients with CKD, especially those on HD care, by investigating user needs, concerns, and digital service barriers, and illustrating those in the format of a kidney disease experience map. Due to the high prevalence of CKD among older adults [<xref ref-type="bibr" rid="ref8">8</xref>], both in Finland and worldwide [<xref ref-type="bibr" rid="ref17">17</xref>], the focus of the study was set on the perspective of older adults. The research questions were as follows:</p>
        <list list-type="order">
          <list-item>
            <p>What experiences do patients, particularly older adults, have in their everyday lives with CKD?</p>
          </list-item>
          <list-item>
            <p>What user needs do patients with CKD have for HD eHealth?</p>
          </list-item>
          <list-item>
            <p>How can these needs be illustrated using the experience map technique?</p>
          </list-item>
        </list>
        <p>The study was part of the eHealth in HD project (“device research”) [<xref ref-type="bibr" rid="ref18">18</xref>] coordinated by the Hospital District of Helsinki and Uusimaa in Finland from 2020 to 2022. The project aimed to create a novel eHealth solution for patients with CKD undergoing HD (named “Home dialysis eHealth solution”) and research devices that support patients both before and throughout dialysis therapy by gathering monitoring data, managing HD supply orders, and facilitating communication between the patient and the health care team (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>eHealth solution and research devices for home dialysis. BP: blood pressure; HUS: Helsinki University Hospital; IoT: Internet of Things; PROM: patient-reported outcome measure; UI: user interface.</p>
          </caption>
          <graphic xlink:href="humanfactors_v12i1e48221_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>HCD of eHealth Solutions</title>
        <p>HCD is an approach to interactive system development that aims to develop solutions with high usability and user experience [<xref ref-type="bibr" rid="ref16">16</xref>]. The principles of HCD highlight the importance of involving end users in an iterative design process [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>] and understanding their needs at the beginning of the development process [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>When exploring user needs, researchers collect information, for example, about what features digital services should contain and how they should function from the perspectives of end users. The user needs exploration is important as it helps service designers to understand the role and meaning of the solutions for end users, in our case, patients using HD. eHealth is used to refer to digital health services, and health information offered through the internet or other technology solutions improving health care [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. By designing in a human-centric way and involving end users in the development, eHealth can offer more value and new ways to provide health care and well-being services for patients and all citizens [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. For patients with chronic illnesses, eHealth solutions can offer new communication possibilities between the patient and the health care team, as well as support empowerment and improve quality of life [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Patient Journey Maps and Experience Maps as Illustrations of User Needs</title>
        <p>A patient journey map and an experience map are tools for 2 different purposes. In this study, patient journey maps were used as a part of patient interviews [<xref ref-type="bibr" rid="ref23">23</xref>], and an experience map was used to communicate the results of the study holistically.</p>
        <p>Patient journey maps as tools for visualizing patient journeys can be used to support the design of eHealth in several ways. The maps can help researchers and designers to identify how health care processes can be improved, for example, identify gaps and improve the processes by integrating eHealth solutions as part of those processes [<xref ref-type="bibr" rid="ref24">24</xref>]. The patient journey maps sum up patients’ experiences and care activities in a single, chronological, timeline-type visualization [<xref ref-type="bibr" rid="ref24">24</xref>]. As the maps can help to explain what patients go through with their disease [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>], they can help designers promote empathy, which is important in HCD [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>]. Furthermore, they can help the sharing of knowledge between stakeholders as well as activate creative thinking [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>Patient journey maps can be applied in various specialties regardless of the medical condition. For example, patient journey maps have been used to illustrate home isolation experiences of people with mild COVID-19 [<xref ref-type="bibr" rid="ref29">29</xref>], hypertensive disorders in pregnancy [<xref ref-type="bibr" rid="ref30">30</xref>], cancer [<xref ref-type="bibr" rid="ref24">24</xref>], cervical dystonia [<xref ref-type="bibr" rid="ref31">31</xref>], and kidney diseases [<xref ref-type="bibr" rid="ref32">32</xref>]. In literature, the focus of patient journey maps varies from communicating patients’ emotions and identifying process gaps to the importance of shared decision-making [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
        <p>Experience maps are tools to combine situations, functions, emotions, and contacts in the same visualization [<xref ref-type="bibr" rid="ref34">34</xref>]. Experience maps are valuable in the development of various eHealth, mobile health, and other apps, helping to communicate, for example, how cancer affects a patient’s life and capturing patients’ voices [<xref ref-type="bibr" rid="ref35">35</xref>]. However, similar to patient journey maps, there is no standardized way to visualize and use them in an eHealth development context [<xref ref-type="bibr" rid="ref33">33</xref>]. To our knowledge, no experience maps have been produced to represent the everyday life of patients with CKD using HD. Even though working with experience maps helps to identify users’ needs [<xref ref-type="bibr" rid="ref34">34</xref>], based on our literature review, few patient journey maps or experience maps focus on illustrating and communicating the needs as a basis for eHealth design and requirements specification.</p>
      </sec>
      <sec>
        <title>Older Adults as eHealth Users</title>
        <p>The European population is aging [<xref ref-type="bibr" rid="ref36">36</xref>]. In Finland, &#62;2 million citizens (ie, 36% of the population) are ≥55 years old [<xref ref-type="bibr" rid="ref37">37</xref>]. Finnish older adults have good self-confidence in using digital services. In the 55 to 64 age group, &#62;80% of Finns felt that their digital skills were at least on par with those of other Finns, and in the 65 to 74 age group, &#62;60% of Finns felt the same [<xref ref-type="bibr" rid="ref38">38</xref>]. At the same time, the number of patients in Finland who undergo dialysis, is expected to increase by &#62;36% before 2040 [<xref ref-type="bibr" rid="ref39">39</xref>]. Therefore, Finnish older adults seem to have both a need for and self-confidence in using CKD eHealth.</p>
        <p>Older adults, due to an increase in diseases and complex health issues, could benefit substantially from eHealth [<xref ref-type="bibr" rid="ref40">40</xref>]. Still, they experience several barriers to using eHealth, such as privacy concerns, lack of motivation to use digital solutions [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], and challenges to finding, accessing and understanding health-related information [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. In addition, they have concerns about eHealth reducing the time with the physicians during appointments [<xref ref-type="bibr" rid="ref42">42</xref>]. Although they can benefit from eHealth, they still face several challenges that could be solved with careful design.</p>
        <p>The health situation also affects the use of the eHealth and user needs. Many eHealth tools are intended for the treatment of a specific disease. One or more chronic health conditions can lead to several regular self-management tasks [<xref ref-type="bibr" rid="ref40">40</xref>], which can potentially affect a patient’s everyday life and the use context of eHealth. Therefore, eHealth should be adapted to each user’s special situation [<xref ref-type="bibr" rid="ref44">44</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>Combining different context-specific strategies is important when developing services in a complex environment, such as health care [<xref ref-type="bibr" rid="ref15">15</xref>]. Our study on user needs of patients with CKD for eHealth used a qualitative research approach and semistructured interviews [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref45">45</xref>] as the primary method for data gathering. The interviews were supported with preliminary tasks, which included visualizing patient’s journey in the form of a timeline drawing [<xref ref-type="bibr" rid="ref23">23</xref>]. The procedure of the study included several phases starting from the recruitment and ending with the creation of the kidney disease experience map illustration (<xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Procedure of the study.</p>
          </caption>
          <graphic xlink:href="humanfactors_v12i1e48221_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>The empirical study was conducted as part of the eHealth in HD project, which received permission from the ethical committee of the Hospital District of Helsinki and Uusimaa (HUS/1649/2020, Jarkko Ihalainen). All participants gave their voluntary, informed, and written consent. The patients’ capabilities to participate in the study were ensured. While analyzing the data, the information of the patients participating in the study was pseudonymized and coded with the identification numbers. Only the researchers assigned to the study had access to the data. No compensation was paid to the participants for their participation.</p>
      </sec>
      <sec>
        <title>Participants</title>
        <p>In total, 18 patients aged ≥60 years participated in the study: 5 patients in predialysis phase, 4 patients in satellite dialysis, 5 patients in home peritoneal dialysis care, and 4 patients in home hemodialysis care (<xref ref-type="table" rid="table1">Table 1</xref>). Most of the participants were retired. The sample excluded in-center patients with dialysis, but included patients with dialysis in satellite units. The participants were recruited from the group of patients who were participating in the larger research project of HD eHealth solution development.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Demographics of study participants (N=18).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="500"/>
            <col width="0"/>
            <col width="470"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Demographics</td>
                <td>Frequency, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Dialysis</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Predialysis</td>
                <td colspan="2">5 (28)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Satellite dialysis</td>
                <td colspan="2">4 (22)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Home peritoneal dialysis</td>
                <td colspan="2">5 (28)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Home hemodialysis</td>
                <td colspan="2">4 (22)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Gender</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Woman</td>
                <td colspan="2">4 (22)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Man</td>
                <td colspan="2">14 (78)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Education</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Basic education</td>
                <td colspan="2">4 (22)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Upper secondary level</td>
                <td colspan="2">4 (22)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bachelor’s degree</td>
                <td colspan="2">5 (28)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Master’s degree</td>
                <td colspan="2">3 (17)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Other</td>
                <td colspan="2">2 (11)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Technology skills (self-assessed)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Good</td>
                <td colspan="2">6 (33)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Basic</td>
                <td colspan="2">11 (61)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Weak</td>
                <td colspan="2">1 (6)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The health care team recruited the patients by distributing materials about the study and asking about their interest in participation. Participation was voluntary and they did not get any compensation. The study participants were already familiar with the novel HD eHealth solution under development and had tested the first version of the solution. The research nurse contacted the potential participants first and informed them about the study. If the participants wanted to participate in the study, they signed the consent form, and the research nurse provided their contact information to the researchers. Then, the research material package, prepared by the researchers, consisting of a cover letter, a preliminary interview task, background information forms, and the responsible researcher’s contact details were sent to the participants. After sending the package to the participants, the researcher called them to provide more detailed instructions, answer any questions, and schedule a time for the remote interview.</p>
      </sec>
      <sec>
        <title>Preliminary Tasks and Retrospective Interviews</title>
        <p>Interviews are useful in the phases of any development process related to eHealth [<xref ref-type="bibr" rid="ref15">15</xref>]. In our study, retrospective interviews included questions about the patient’s journey, treatments experiences, cooperation with the health care team, technology experiences, and visions for the future. The themes broadly covered patients’ everyday experiences with the illness, practical questions, and the comprehensive timeline with CKD.</p>
        <p>The idea of the visual timeline drawing as the preliminary task for the interview was to (1) help the interviewee to process and structure their multistage patient path even before the interview, and (2) help with communication between the interviewee and researcher during the remote interview [<xref ref-type="bibr" rid="ref23">23</xref>]. The preliminary task was sent to the interviewees 2 weeks before each interview. In this task, patients were asked to identify and illustrate significant milestones, events, and experiences with their illness to a timeline. The patients returned the task to the researchers before the remote interview.</p>
        <p>The interviews were conducted between October 2020 and April 2021 when the second wave of COVID-19 was underway in Finland. For safety reasons, the interviews were arranged remotely via Microsoft Teams. Two researchers were present in the interview session with the participating patient: one researcher being the interviewer and the other note-taker. Interviews were audio-recorded using recording functionality of Microsoft Teams. Data gathering was conducted in collaboration with 5 researchers (SL, NK, JV, SH, and PV): 2 doctoral researchers, 2 students, and a professor from the human-computer interaction field.</p>
      </sec>
      <sec>
        <title>Data and Analysis</title>
        <sec>
          <title>Overview</title>
          <p>The data included recordings and notes from the interviews, as well as illustrations of patient journeys. The interview notes were finalized according to audio recordings and the transcriptions were pseudonymized. In total, the data consisted of 155 pages (ie, 58,429 words) of written notes and 18 paper-based patient journey visualizations (ie, visual timeline drawings). A total of 5 researchers (SL, NK, JV, SH, and PV) participated in the data analysis.</p>
          <p>The data were analyzed in 4 phases (<xref rid="figure3" ref-type="fig">Figure 3</xref>): (1) grounded theory analysis, (2) thematic analysis, (3) user needs exploration and thematic categorization, and (4) comprehensive affinity diagram creation. The data included many different perspectives to understand the different nuances and ensure reliability, and the analysis was done in collaboration with several researchers in many phases.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Four phases of data analysis.</p>
            </caption>
            <graphic xlink:href="humanfactors_v12i1e48221_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Phase 1: Grounded Theory Analysis</title>
          <p>In the first phase [<xref ref-type="bibr" rid="ref46">46</xref>], the pseudonymized interview transcripts were analyzed following the main structure of grounded theory [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>] using ATLAS.ti software version 9.1.5.0 (ATLAS.ti Scientific Software Development GmbH, “ATLAS.ti”) [<xref ref-type="bibr" rid="ref46">46</xref>]. During the analysis, the interview data was coded using researcher-denoted concepts and open coding influenced by the grounded theory [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. The first round of interview data analysis following grounded theory was conducted by SL.</p>
        </sec>
        <sec>
          <title>Phase 2: Thematic Analysis</title>
          <p>In the second phase, the principles of the thematic analysis method [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>] were followed to analyze the interview data from 18 participants from an existentialist perspective, including references to death, well-being, and atmosphere in life (eg, emotions) [<xref ref-type="bibr" rid="ref50">50</xref>-<xref ref-type="bibr" rid="ref52">52</xref>]. In addition, the analysis used the holistic framework [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>] of exploring the context of use, technology, and people.</p>
          <p>On the basis of the analysis, 3 thematic categories were identified: healthy habits, concerns and barriers for eHealth use, and everyday life with CKD. Observations based on interview transcripts were written on post-it notes and thematically categorized following the phases of the affinity diagram method [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]. The data gathered using preliminary task of patient journeys were mapped in line with the interview transcripts. In addition to the initial 3 themes, 2 categories were formed based on thematic analysis: digital communication and patients’ emotions. Concerns and use barriers for eHealth were investigated from the data by two researchers (PV and SH). The digital communication affinity diagram was done by three researchers (PV, SH, and JV).</p>
          <p>The thematic analysis categories include several aspects as presented in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>.</p>
          <boxed-text id="box1" position="float">
            <title>Categories of thematic analysis.</title>
            <list list-type="bullet">
              <list-item>
                <p>Healthy habits: health-promoting activities and hobbies that were mentioned by interviewees, including the whole scale of activities from sports to eating habits.</p>
              </list-item>
              <list-item>
                <p>Concerns and use barriers for eHealth: observations related to everyday life challenges with the disease, use challenges and barriers of digital services, negative emotions, such as worries or dissatisfactions, and patient path challenges.</p>
              </list-item>
              <list-item>
                <p>Digital communication: observations concerning health care-related digital communication habits, channels, and experiences.</p>
              </list-item>
              <list-item>
                <p>Patients’ emotions: observations of emotions and experiences interviewees mentioned in the interviews and patient journey visualizations. The emotions included the whole scale of emotions, from fear and confusion to happiness.</p>
              </list-item>
              <list-item>
                <p>Everyday life with chronic kidney disease: observations related to interviewees’ thoughts, stories, and experiences of their everyday lives, including references to death. Death made the participants reflect from different perspectives: their own (forthcoming) death was compared to other deaths, the actions to avoid death were listed, and the inevitable nature of death was considered.</p>
              </list-item>
            </list>
          </boxed-text>
          <p>Finally, the frequency of observations per theme was calculated (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Most of the observations were related to concerns and barriers to technology use. Emotions and healthy habits were also common topics in all the interviews.</p>
        </sec>
        <sec>
          <title>Phase 3: The User Needs Exploration and Thematic Categorization</title>
          <p>The third phase focused on analyzing user needs. All the gathered data were explored from the viewpoint of user needs from 2 perspectives: exploring digital communication needs and exploring overall user needs for interactive solution development. In the analysis, 2 researchers (PV and SH) explored the data labeled “digital communication,” “user needs,” and “to eHealth solution concept” in ATLAS.ti and formulated the observations as user needs. The second round resulted in 165 needs.</p>
          <p>After this, the digital communication affinity diagram was created in collaboration with 3 researchers (SH, JV, and PV). The user needs were written on post-it-notes by PV, and analyzed, and regrouped to the affinity diagram in collaboration with SH, JV, and PV. In the affinity diagram, the identified needs (n=165, 100%) were thematically grouped under 5 categories: overall interaction and communication (n=77, 47% of all identified needs), patients’ digital activities (n=28, 17%), instruments (n=27, 16%), inventory and ordering dialysis supplies (n=19, 12%), and digital communication with the health care team (n=14, 8%). While creating the affinity diagram of digital communication needs, doubles were removed.</p>
          <p>When exploring overall user needs, the data transcriptions of 18 interviews were analyzed using ATLAS.ti. During this analysis, the data labeled with the following codes—“user needs,” “healthy habits and hobbies,” “suggestion,” “communication,” “digital services,” “tasks,” “care team,” “communication,” “social relationships,” “equipment,” “challenges,” “positive experiences,” and “device research”—were explored and formulated as user needs. In total, 287 user needs were identified and written on post-it notes as preparation for the comprehensive affinity diagram work.</p>
        </sec>
        <sec>
          <title>Phase 4: Comprehensive Affinity Diagram</title>
          <p>In the fourth phase, the affinity diagrams created in the previous analysis phase were merged to form a comprehensive affinity diagram. Three researchers recategorized the post-it notes to create a comprehensive affinity diagram of user needs. The main themes of the diagram were “eHealth user interfaces,” “Inventory and ordering dialysis supplies,” “Overall interaction and communication,” “Process,” “HD eHealth solution,” “Family/peer-support,” “Patients’ digital activities,” and “Needs for improving the quality of life” (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). These 5 were used as the leading themes to guide the design of the first version of the kidney disease experience map. Data analysis results were discussed between PV, SH, VR, and JV.</p>
        </sec>
      </sec>
      <sec>
        <title>Creation of the First Version of the Kidney Disease Experience Map</title>
        <p>An experience map is a tool that strings the perspectives of the context of use, people, and technology, together in a holistic manner [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. The maps can be used to support the communication between stakeholders and to capture a patient’s voice in eHealth design [<xref ref-type="bibr" rid="ref35">35</xref>]. The first version of the kidney disease patient experience map (<xref rid="figure4" ref-type="fig">Figure 4</xref>) was made by combining remarks from existing example models particularly the cancer experience map [<xref ref-type="bibr" rid="ref35">35</xref>]. In the first paper-based template of our map, the preliminary phases from the preliminary tasks (ie, patient journey maps) were illustrated: “before diagnosis,” “diagnosis and passive treatment,” “treatment method selection,” “beginning of treatment/training,” and “home dialysis.” Post-it notes from the comprehensive affinity diagram were added under those phases. The first draft of the patient experience map was created in collaboration with 3 researchers.</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Overview of the data analysis process leading to the creation of the first version of the kidney disease experience map.</p>
          </caption>
          <graphic xlink:href="humanfactors_v12i1e48221_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Next, the structure of the experience map was refined based on the number of post-it notes in each phase. The duplicate post-it notes were removed and the content of the map was reorganized (PV, SH, and JV). To validate the contents of the draft map further, 2 researchers (PV and SH) reexamined the post-it notes after which 4 other researchers (JV, NK, SL, and VR) gave feedback on the next version of the map. After all, in total of 6 researchers (PV, SH, JV, NK, SL, and VR) participated at least somehow in the experience map visualization process. The published version of the first version of the kidney disease experience map was finalized by PV. An overview of the multiphase analysis process which led to the creation of this first version of the kidney disease experience map is illustrated in <xref rid="figure4" ref-type="fig">Figure 4</xref>.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>As the outcome of the study, the first version of the kidney disease experience map, which illustrates the user needs, concerns, and barriers of patients with CKD for eHealth, was created. This section explores the patients (ie, people), technology, and context of use perspectives [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. First, patients’ healthy habits are investigated and their concerns and barriers to technology are addressed. Then, the technology is examined, concentrating on digital communication. Finally, the context of use from the perspective of patients’ everyday lives is explored. Due to sensitive personal issues, research results and citations are presented without identification information to ensure complete anonymity of the participants.</p>
      </sec>
      <sec>
        <title>Exploring the People: Healthy Habits</title>
        <p>The patients had different needs for healthy habits regarding social life, sports, and other activities (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). Patients mentioned that social life and taking care of close relatives, such as grandchildren, were important to them. Incidental exercises, including gardening or shoveling snow, were popular. Being in nature, picking mushrooms or berries, fishing, and hiking, along with other everyday life activities, such as club and society activities or studying, brought well-being to the participants. Animals, for example, dogs, cats, and summer chickens, also supported the participants’ well-being. Handcrafting, art, and culture were also seen as important, but COVID-19 restricted those activities. The importance of many remote social contacts was mentioned in the data, and patients had to learn new eating habits, such as losing weight or cutting down on alcohol consumption.</p>
      </sec>
      <sec>
        <title>Exploring the People: Concerns and Barriers for eHealth Use</title>
        <p>Patients were challenged with poorly functioning available eHealth solutions and also experienced other negative factors, such as lack of interest or lack of skills (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>). Technical devices did not always meet the emotional or physical needs of their users. This caused emotions like frustration, worry, and fear from patients. The patients’ responses covered their available eHealth solutions, not focusing especially on the HD eHealth solution.</p>
        <p>The solution or software used by patients for their CKD care was found to function poorly in many ways. For example, the devices as a part of the HD eHealth solution did not work as expected, or they worked differently than they expected:</p>
        <disp-quote>
          <p>I have no control over the information. If I measure my blood pressure, I press the BT button and then it should be delivered, but I don’t know if it did. The same goes for the scale, *beep*, and maybe it synchronized.</p>
          <attrib>P18</attrib>
        </disp-quote>
        <p>Alongside poorly functioning devices, in some cases, the HD eHealth app also did not work well. The software content (eg, one’s results or visualizations of one’s health situations) was challenging to understand or find. The HD eHealth app was challenging to use with small mobile phone screens and its user interface terminology caused problems for patients:</p>
        <disp-quote>
          <p>There have been a few problems with the phone. There will be updates and then it will freeze somehow. I don’t understand much; the basic things are in Finnish, but then they are English words so... This was at least the third time that the nurse had visited us.</p>
          <attrib>P17</attrib>
        </disp-quote>
        <disp-quote>
          <p>Others have also worked well. Even the mobile phone. You can monitor your health from it, even though it has those [health status] curves that you don’t understand much about.</p>
          <attrib>P13</attrib>
        </disp-quote>
        <p>The participants doubted the functionality of the HD eHealth solution, both devices and the app. With the dialysis monitor, they were worried that something would go wrong:</p>
        <disp-quote>
          <p>I haven’t used (ie, the devices and instruments) much, I’ve just tried. I’m a bit lazy. I doubt whether the instrument is still in good condition. There was an error message about a month ago. There was a notification that there was still something wrong. I thought I’d let it be and fix the instrument before I started.</p>
          <attrib>P24</attrib>
        </disp-quote>
        <disp-quote>
          <p>When the first treatments started, it was so exciting. But after a month had passed, it had become routine and was no longer exciting. Then, when I moved home from hospital, I started to get excited again.</p>
          <attrib>P22</attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>Exploring the Technology: Digital Communication</title>
        <sec>
          <title>Overview</title>
          <p>Patients commented on digital devices and the app from many different aspects in terms of the technical functionality and the emotion they cause. The contents of the solution’s user interface (<xref rid="figure1" ref-type="fig">Figure 1</xref>), as well as other user interfaces, were also commented on. Patients linked and communicated with the health care team through digital channels and used technology independently as a part of their HD treatment during the research.</p>
        </sec>
        <sec>
          <title>Many Groups Communicate With the Patient</title>
          <p>Communication within the health care team is important, but also nurses, physicians, and patients share information (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). To get the supplies and instruments needed for HD care, the patient also needs to be in regular contact with the pharmacy or the health care team. Relatives must not be forgotten either, as patients may want to share information with them:</p>
          <disp-quote>
            <p>To be able to get in touch with the on-call nephrologist or the other way around, perhaps you could organize a little more frequent meeting. I think that many patients could have questions for the doctor that the nurses cannot or are not allowed to answer. Nephrologist on-call from the computer.</p>
            <attrib>P24</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Examples of Current Communication Channels</title>
          <p>Depending on the patients’ devices and patients’ capabilities to use them, HD patients use different communication channels for following their health records and CKD-specific operations. They order HD supplies once per month. Some patients have created their digital tools (eg, Excel sheets), which calculate the number of needed supplies automatically. After that, the order will be sent via email to the nurse. Still, Excel sheets or other tools for ordering dialysis supplies are not an option for everybody. Therefore, an easy-to-use solution for ordering supplies and managing inventory is needed for HD patients:</p>
          <disp-quote>
            <p>Orders must be sent once a month. I have an Excel sheet that automatically keeps the balances. Then, there is a page where you can automatically see what needs to be ordered. I have made Excel sheets myself. It’s quite a job when there are more than 30 different supplies. Syringes... you must know their numbers. Sometimes, I also check some information. If one item is true, then so are all the others. It’s automatic. I then make a .pdf list from the Excel sheet, one A4, and then it goes [by e-mail to the nurse].</p>
            <attrib>P30</attrib>
          </disp-quote>
          <p>In Finland, patients follow their health records via national or local patient portals (eg, “My Kanta Pages” [<xref ref-type="bibr" rid="ref53">53</xref>] or “MyChart” [<xref ref-type="bibr" rid="ref54">54</xref>]). Patients with chronic illness have many laboratory tests taken. They appreciate that all their health records are found in one place, but each record is shown in detail separately, too. Therefore, easy-to-read visualizations of test results and current health situations are needed:</p>
          <disp-quote>
            <p>MyChart is as hopeless as My Kanta, both of which break down the lab results separately, even if they want to see them as a whole. Applying for your results is difficult.</p>
            <attrib>P37</attrib>
          </disp-quote>
          <disp-quote>
            <p>I look at the results on ‘My Kanta,’ all diagnoses come there, as well as laboratory test results. From there, I can see them all. The information is readable and remains stored. I think ‘My Kanta’ is really good. There you can also see laboratory visits from a certain period if you want to follow a limited period.</p>
            <attrib>P21</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Positive Attitude Toward Digital Communication</title>
          <p>All patients participating in the study seemed to have a positive attitude toward digital communication tools. For example, paper-based dialysis supply orderings may be forgotten and instead, digital tools can step in and help patients with their everyday lives. Patients felt that digital solutions enabled information-seeking and offered more flexibility in meetings with the health care team and other contacts:</p>
          <disp-quote>
            <p>Their version is that they hand out an A4 paper. You should fill it in; it’s difficult manually. The risk is that you forget.</p>
            <attrib>P30</attrib>
          </disp-quote>
          <disp-quote>
            <p>We have internet and e-mail. My wife uses them more; I just read. The wife handles banking and other things remotely. I kind of stopped using the computer when I don’t need to. You could probably handle things digitally. I haven’t come across anything like that. I have had to deal with a lot of paper. I have not been approached digitally. Yes, it would be even easier. You could reach the staff at any time.</p>
            <attrib>P24</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>Exploring the Context of Use: Everyday Life and Emotions</title>
        <sec>
          <title>Overview</title>
          <p>The main themes related to everyday life were thinking of death, the importance of care, changes in well-being after treatment started, and emotions (<xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>).</p>
        </sec>
        <sec>
          <title>The Presence of Death</title>
          <p>With kidney disease, death is present in life. It is known that without dialysis or receiving a transplant, one dies. The logic of the disease is unequivocal: when dialysis no longer helps, the person knows they are going to die:</p>
          <disp-quote>
            <p>I think that the disease is deadly and must be treated.</p>
            <attrib>P21</attrib>
          </disp-quote>
          <disp-quote>
            <p>Everyone knows that life ends eventually, but I’m not afraid of it in any way.</p>
            <attrib>P1</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>The General Well-Being of the Participants Varied</title>
          <p>The patients understood the essentiality of treatment and often felt better after the treatment started. They wished to be able to continue life as normally as possible. One patient (P9) described experiencing leg cramps at night, which had caused them to sleep poorly. After the dialysis treatment started, the cramps stopped. They managed better than before and could even go for walks:</p>
          <disp-quote>
            <p>I hope I don’t end up on dialysis. Of course, it is ahead, but hopefully as far as possible. It is a wish.</p>
            <attrib>P20</attrib>
          </disp-quote>
          <disp-quote>
            <p>It’s just that now I feel like I’m getting older. I recently turned 70, so all kinds of unnecessary aches and pains will increase.</p>
            <attrib>P25</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Everyday Life Is Characterized by Waiting</title>
          <p>The health situation of a patient can be improved either with dialysis or a transplant. Having to wait for transplant can have major setbacks; one patient (P24) had to be removed from the transplantation waiting list due to amputation and sepsis, which is why they now focus on keeping themselves in the best possible physical condition through physical activities. Patients were waiting to travel.</p>
        </sec>
        <sec>
          <title>A Wide Range of Emotions in Everyday Life</title>
          <p>A wide range of emotions appeared in the interview data about the patient’s everyday life. Despite the challenges of the disease, most of the patients described their lives with the disease in somewhat positive terms. Everyday life with the disease seemed to go somewhat smoothly.</p>
          <p>In addition to positive feelings, patients also expressed negative emotions, such as confusion, fear, irritation, anger, and frustration. Feelings of confusion were caused by changes in health status and events in the patient’s journey, uncertainty of the future steps in the journey, or technology that worked unexpectedly. After receiving the diagnosis, one patient was confused because they did not fully understand what kind of disease the diagnosis was about. Several patients brought up fear in the interviews. Things related to the treatments were especially scary. Most of the patients also described irritation or anger at least sometimes during the patient journey. In addition, half of the patients reported frustration. Health challenges, the difficulty or even failure of a treatment, and the commitment to dialysis treatment were irritating. The most frustrating thing was when HD treatment did not go as well as planned. Another source of frustration was digital systems, equipment, and devices:</p>
          <disp-quote>
            <p>And a little fear. I am quite hopeful that I will get there on the transplantation waiting list and that it will be successful at some point. I hope that I can make it there (ie, from a health perspective), and if this continues, then there is nothing to worry about.</p>
            <attrib>P11</attrib>
          </disp-quote>
          <disp-quote>
            <p>Actigraphy, a part of HD eHealth solution, is inconvenient, but there is nothing wrong with the other devices, everything is fine. I have a strong belief that information will go forward. It’s enough for me to see on the scale and blood pressure monitor that my weight and blood pressure are okay.</p>
            <attrib>P18</attrib>
          </disp-quote>
          <disp-quote>
            <p>This home dialysis takes up a lot of space. Do you see these boxes? A huge package comes once a month. The dialysis monitor also takes up quite a lot of space. And then the cabinets, where you put all the treatment consumables. And there is a bottle like this: hand sanitizer comes once a month. Quite a lot of supplies come from the hospital once a month. This room is completely reserved for dialysis.</p>
            <attrib>P30</attrib>
          </disp-quote>
          <p>HD taking up too much space or other resources was both irritating and frustrating. HD requires much space at home, so some patients had to renovate their homes. However, almost half of the patients felt that their living conditions did not require changes due to HD. The patients felt it was important that the dialysis treatment could also be done at the summer cottage.</p>
          <p>Positive emotions included joy, optimism, hope, and satisfaction. A third of the patients mentioned joy in the interviews and most patients expressed hope and optimism. They were satisfied with the professional staff and the stability of the current situation. The supportive and successful dialysis made them happy. Keeping their health situation stable was their biggest wish. Patients also mentioned their willingness to continue their hobbies.</p>
          <p>The patients were satisfied with both their health condition and the information related to it. Half of them were satisfied with the treatment. The patients were pleased with the eHealth solution in use during the study and the HD treatment was experienced as proceeding smoothly. The nursing staff was considered friendly and knowledgeable:</p>
          <disp-quote>
            <p>I have been very satisfied. They, the care team, have guided me, and when I have challenged them, they have accepted challenges and promised to sort things out.</p>
            <attrib>P37</attrib>
          </disp-quote>
          <disp-quote>
            <p>Home dialysis has gone surprisingly well—no major problems.</p>
            <attrib>P34</attrib>
          </disp-quote>
          <disp-quote>
            <p>At least now, this present moment looks bright.</p>
            <attrib>P13</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>The First Version of the Kidney Disease Experience Map</title>
        <p>The first version of the kidney disease experience map (<xref rid="figure5" ref-type="fig">Figure 5</xref> [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]) was developed from the perspective of user needs of eHealth. It includes their needs for everyday life with CKD (ie, “Common needs”), needs relating to 4 phases of the journey of patients with CKD, and needs in all journey phases of patient with CKD from diagnosis to kidney transplant or death. The patient journey phases, which are inspired by the experience timeline of cancer experience map [<xref ref-type="bibr" rid="ref35">35</xref>], are “Diagnosis and passive treatment,” “Predialysis,” “HD,” and “Preparing for kidney transplant or death.” In the top corner of our map kidney disease statistics and patients’ everyday life experiences with CKD are illustrated.</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>The first version of the kidney disease experience map from a user needs perspective. A higher resolution image is available in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref>. CKD: chronic kidney disease. KD: kidney disease.</p>
          </caption>
          <graphic xlink:href="humanfactors_v12i1e48221_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The first version of the kidney disease experience map (<xref rid="figure5" ref-type="fig">Figure 5</xref>) includes aspects from all three perspectives [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]:</p>
        <list list-type="order">
          <list-item>
            <p>Context of use: the context of use perspective can be found especially in the patient journey phases and the “everyday life with CKD” part of the map.</p>
          </list-item>
          <list-item>
            <p>People: information about people is available in the “statistics and everyday life with CKD” parts of the map.</p>
          </list-item>
          <list-item>
            <p>Technology: technology aspects are mainly covered in the form of user needs.</p>
          </list-item>
        </list>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>On the basis of our study, eHealth as a part of the daily lives of the patients with CKD was perceived as being useful, but the patients also had challenges with devices and apps. Acknowledging that CKD is a long-lasting journey, it is essential to consider long-term user experiences. Finally, several user needs in different phases of the journey of patients with CKD were identified and illustrated with the first version of the kidney disease experience map.</p>
      </sec>
      <sec>
        <title>Answers to Research Questions</title>
        <sec>
          <title>Overview</title>
          <p>This study had three research questions: (1) what experiences do patients, particularly older adults, have in their everyday lives with CKD; (2) what user needs do patients with CKD have for HD eHealth; and (3) how can these needs be illustrated using the experience map technique?</p>
        </sec>
        <sec>
          <title>What Experiences Do Patients, Particularly Older Adults, Have in Their Lives With CKD?</title>
          <p>Three key experiences related to daily life of patients with CKD were identified as depicted in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref></p>
          <boxed-text id="box2" position="float">
            <title>Key experiences related to daily life of patients with chronic kidney disease (CKD).</title>
            <list list-type="bullet">
              <list-item>
                <p>Patients’ healthy habits: patients with CKD must adapt to the changes in their everyday lives resulting from dialysis care. For example, patients must learn new routines for their treatment at home. Patients felt that CKD limited their lives, but they dealt with it in different ways: some were frustrated and others continued to live as normally as possible. However, they understood the necessity of the treatment and continued the treatment as usual. Similar findings were reported from a study involving cancer patients [<xref ref-type="bibr" rid="ref35">35</xref>], who expressed concerns with unknown, life-threatening, and life-changing experiences.</p>
              </list-item>
              <list-item>
                <p>Patients’ concerns and barriers to use for eHealth: patients had challenges with user interface and technical devices, including dialysis monitors and research devices of HD eHealth solution (<xref rid="figure1" ref-type="fig">Figure 1</xref>), that did not always meet the users’ needs.</p>
              </list-item>
              <list-item>
                <p>Digital communication: digital communication opportunities via the eHealth solution play an important role for patients. Digital solutions made information-seeking possible and offered more flexibility when meeting the health care team and other contacts. Information gaps did not accumulate as easily as for cancer [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>What User Needs Do Patients With CKD Have for HD eHealth?</title>
          <p>In our study, both general needs and needs related to different patient journey phases were identified and illustrated in the first version of the kidney disease experience map (<xref rid="figure5" ref-type="fig">Figure 5</xref>). We found that CKD was different from day to day, and thus the use context of eHealth varied. Poor usability burdens the everyday life of a person with disease even more. Similar observations were reported in the case of digital independent living supporting systems of older adults [<xref ref-type="bibr" rid="ref34">34</xref>]: designers were important to understand the treatment stage, the transition from health to illness, and statuses between them. Furthermore, the needs and experiences of patients with cancer were found to vary during the care process [<xref ref-type="bibr" rid="ref35">35</xref>].</p>
          <p>The HD eHealth solution is targeted to all patients with CKD, as well as individuals with disabilities, such as low vision or even amputated limbs. The solution is to be used during the entire patient journey, which may last for years. Considering this, the HD eHealth solution is observed to play a remarkable role in the patient’s life and highlights the need for research on long-term user experience.</p>
        </sec>
        <sec>
          <title>How Can the User Needs Be Illustrated Using the Experience Map Technique?</title>
          <p>Typically, user needs are illustrated with use cases or user needs tables, and they can be processed further to requirements format [<xref ref-type="bibr" rid="ref55">55</xref>]. Findings from user research can also be presented as user profile illustrations, such as personas [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref34">34</xref>], stakeholder maps [<xref ref-type="bibr" rid="ref15">15</xref>], experience maps [<xref ref-type="bibr" rid="ref34">34</xref>], and visualizations of stakeholders [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
          <p>In our study, we used the experience map method to illustrate user needs. As with the cancer experience map [<xref ref-type="bibr" rid="ref35">35</xref>], we identified the phases of care and relevant themes for grouping the findings. We considered the experience map technique applicable for illustrating not only the phases but also the eHealth related needs of the patients. We found a group of general needs, which are common for all phases of care, but also needs that arise from specific phases of care. Understanding the care process and how user needs evolve is important for the designers and also for the health care team, who are responsible for introducing the services to patients and training them. Experience maps help to ensure the care continuum in service development [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
          <p>In this study, the created experience map represents a common higher-level experience map, which can illustrate a specific persona, or the timeline could be narrower (ie, 1 month or 1 day). In the first version of the kidney disease experience map, the HD eHealth solution covers different wearable solutions and the software (ie, including the wearable solutions and software connected to the dialysis monitors); however, different physical dimensions (ie, dialysis monitors, packing materials of supplies ordered) are not covered.</p>
          <p>Experience mapping can be seen as a promising but laborious method for illustrating user needs and communicating a patient’s voice holistically to eHealth development, especially in a case where the experience map is based on extensive qualitative data. Following the example of cancer experience map [<xref ref-type="bibr" rid="ref35">35</xref>], we captured patient’s voices with their quotes. Similarly, we also focused on reporting patient quotes in the paper instead of the experience map. Therefore, the first version of the kidney disease experience map can be used both separately and with the paper. Our interpretation is that similar to the integrated patient journey map for hypertensive disorders in pregnancy [<xref ref-type="bibr" rid="ref30">30</xref>] and the cancer experience map [<xref ref-type="bibr" rid="ref35">35</xref>], the kidney disease experience map can help developers build effective eHealth solutions and promote empathy and shared understanding between the developing team members. It can also help empower patients and help with shared decision-making [<xref ref-type="bibr" rid="ref33">33</xref>]. Like the patient journey map [<xref ref-type="bibr" rid="ref24">24</xref>], the first version of the kidney disease experience map has the potential to help simplify and optimize processes for better health outcomes. In addition to that, similar to the cervical dystonia patient journey map [<xref ref-type="bibr" rid="ref31">31</xref>], it can help to communicate the different phases of the care to the patients and help them to understand their needs at each phase.</p>
        </sec>
      </sec>
      <sec>
        <title>Relevance of the Research</title>
        <p>In the study, the experience map describing the patient’s experience was formed based on the qualitative data from retrospective interviews and preliminary tasks. This first version of the kidney disease experience map can be used as a basis for other experience maps related to kidney diseases in the future. In addition, it can also bring perspective to the experience maps of other chronic diseases.</p>
        <p>The presented results can be used to support the further development of HD eHealth. The results have already been used in HD eHealth solution development project in Finland (eg, to inform the redesign of the solution user interfaces).</p>
        <p>Experience maps, such as the map created in the study, can help researchers, designers, and developers to empathize with the patients with chronic illnesses, and to understand their needs and use contexts for future eHealth innovations. We see our kidney disease experience map and other similar maps having the potential to help design the solutions from a more holistic perspective compared to currently prevailing practices [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref21">21</xref>], as well as to create a base for the new ecosystems and new ways to offer health care in the future [<xref ref-type="bibr" rid="ref21">21</xref>]. We continue the work in the ongoing research project “Better Health at Home—Optimized Human-Centered Care of Predialysis and Home Dialysis Patients” (2022 to 2026).</p>
      </sec>
      <sec>
        <title>Evaluation of the Study</title>
        <p>Our study had some limitations. First, exploring the context of use was not allowed at patients’ homes due to COVID-19 restrictions. Therefore, we needed to collect data remotely. This was partly problematic because the patient’s home is the main context of using HD eHealth. In contrast, due to the patient journey preliminary task and participants’ open-minded attitude during the interviews, we were able to gather rich data about user needs and the context of eHealth use. In our study, the possible impact of the COVID-19 period was considered.</p>
        <p>Our sample size is quite small, however, typical for a qualitative interview study. The representativeness of our sample can be questioned as it is divided from a larger patient group based on age and treatment methods. To find as comprehensive a sample as possible, while ensuring the safety of the participants with their ongoing treatment, the health care team helped researchers in recruiting participants for the research study.</p>
        <p>Due to the personal nature of health information and privacy, we could not release the participants’ background information, such as specific ages or treatments in this paper. In addition, the indirect identifiers have been removed from the paper. The relative satisfaction of the patients in their lives despite CKD could have been influenced by various factors, besides the HD eHealth solution. First, the target group in this study included only active patients with relatively good physical conditions for research ethics reasons. Second, many of them were waiting for a kidney transplant, which brought them hope with the disease. Overall, there was a lot of variation in emotions, but deep gloom appeared in the data only rarely.</p>
        <p>The first version of the kidney disease experience map was created based on a reasonable amount of qualitative data of the everyday lives on patients aged ≥60 years in Finland. Before participating in this study, the patients already knew that the study covered new eHealth solution testing. Therefore, perspectives from patients whose condition is very weak and those whose attitude is not open to new technology are missing in this study. In contrast, research shows that HD is optimal for those who live in areas with long distances to travel to an in-center dialysis unit [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. In part, this can also be seen in the first version of the kidney disease experience map: the study did not include patient experiences during the kidney transplant phase—meaning that the user needs related to this essential phase of the patient journey are missing from our map. In future, the introduced version of the kidney disease experience map can be updated by including motivational issues for HD.</p>
        <p>The study was conducted as an integrated part of the patient’s normal CKD treatment, so the research setup was organized in line with the patients’ typical daily conditions and treatments. The study included participants who started using the HD eHealth solution shortly before the interviews but also those who had already been using the solution for several months. Thus, the study covered both novice users and more experienced users. Patients’ reported technology skills varied from weak to good.</p>
      </sec>
      <sec>
        <title>Further Research</title>
        <p>This study provided initial experiences of creating an experience map to illustrate patients’ needs for eHealth. In addition, the patients’ experiences from the HD eHealth solution development can offer important perspectives to other development projects regarding patients with CKD. Further research is needed to gather more experience about the applicability of the method. We aim to continue the research with patients with CKD and HD eHealth designs. We will use the illustrated first version of the kidney disease experience map and the listed user needs in further analysis, which will aim to describe design principles and guidelines for HCD of eHealth for patients using HD and other patients with chronic illnesses.</p>
        <p>The outcome of the first version of the kidney disease experience map offers insights to the different phases of the patient journey for patients with kidney disease at the HD care. Due to the diverse experiences of patients in different phases of the care process, different types of kidney diseases could also be studied and visualized with experience maps. In addition, the next versions of the kidney disease experience maps could focus on specific days and months. The next versions of the kidney disease experience maps could also be created from the health care team’s perspective.</p>
        <p>The content of the first version of the kidney disease experience map was collected with qualitative research methods, which made the consideration of the many different nuances possible. Due to the qualitative nature of the data collection for the first version of the kidney disease experience map, we did not prioritize the available content, for example, based on the amount of the post-it notes. However, without careful prioritization, there is always a risk that the map is too challenging to use as a part of the practical software development work. Therefore, we will involve the patients, as well as the health care team, designers, and software developers, in prioritizing the content of the map in the future.</p>
        <p>The perspectives of patients using in-center dialysis are missing from that data, which was the base of the first version of the kidney disease experience map. However, we believe the creation of experience maps for the eHealth needs of patients using in-center dialysis is important for the future as the dialysis modalities might change depending on the patient’s health and life situation.</p>
        <p>Our study pointed out the need for further research on the existentialism perspectives of the patients with chronic illnesses using eHealth. Deeper understanding is required on user needs and the role of eHealth as a part of patients’ everyday lives, even when life is nearing its end [<xref ref-type="bibr" rid="ref50">50</xref>-<xref ref-type="bibr" rid="ref52">52</xref>].</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>eHealth offers possibilities to support the key needs of patients with chronic diseases, such as CKD; however, digital services need to adapt to a wide variety of situations and user needs because kidney diseases are unique to each patient. Patient experiences vary both between and within the stages of treatment. In addition, the patient’s situation, needs, and capacity to use eHealth vary with everyday challenges and opportunities. Furthermore, with older adult patients, the problems that come with age increase the spectrum of barriers to use eHealth and associated challenges.</p>
        <p>eHealth should enable proactive communication between the patient and the health care team. Furthermore, awareness of the status should be formed for both parties in real time, as much as possible. In this way, the patients feel safe, are more motivated in their treatment, and take responsibility for themselves.</p>
        <p>The experience map is a promising method for illustrating user needs for eHealth, communicating a patient’s voice and describing the longitudinal patient journey to support eHealth development. Our first version of the kidney disease experience map combines people, context of use, and technology perspectives holistically and illustrates the eHealth needs of patients with CKD for the future.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Theme analysis: themes from the second phase of the analysis. CKD: chronic kidney disease.</p>
        <media xlink:href="humanfactors_v12i1e48221_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 82 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Main themes of the comprehensive affinity diagram (n=287). Some post-it notes included content for many themes.</p>
        <media xlink:href="humanfactors_v12i1e48221_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 106 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Healthy habits and hobbies, and their frequency (n=105, 18 participants).</p>
        <media xlink:href="humanfactors_v12i1e48221_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 83 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Barriers to eHealth use (n=288, 18 participants).</p>
        <media xlink:href="humanfactors_v12i1e48221_app4.pdf" xlink:title="PDF File  (Adobe PDF File), 104 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Aspects of everyday life with chronic kidney disease, N=18 (aspects N&#62;3 are excluded from the table)</p>
        <media xlink:href="humanfactors_v12i1e48221_app5.pdf" xlink:title="PDF File  (Adobe PDF File), 134 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>The first version of the kidney disease experience map from a user needs perspective. KD: kidney disease. CKD: chronic kidney disease.</p>
        <media xlink:href="humanfactors_v12i1e48221_app6.png" xlink:title="PNG File , 479 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CKD</term>
          <def>
            <p>chronic kidney disease</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">HCD</term>
          <def>
            <p>human-centered design</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">HD</term>
          <def>
            <p>home dialysis</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The project eHealth in Home Dialysis was part of the CleverHealth Network ecosystem and the project (eCare for Me Homedialysis) was funded by participating companies, the Hospital District of Helsinki and Uusimaa, and Business Finland. We thank our project partners Tiina Puurtinen and Pirgit Silvast-Äikäs from Helsinki University Hospital and Malin Ekholm from Helsinki University, and the patients who participated in this study.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The datasets generated or analyzed during this study are not publicly available due to the ethical reasons as stated in the research permit application.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>The study was conceptualized by PV, SL, SH, NK, VR, and JV. Data were collected by five researchers (PV, SH, SL, NK, and JV). PV, SL, and SH were involved in the methodology, investigation, project administration, data curation, visualizations, and formal analysis of the study. PV finalized the experience map. JV contributed to the resources, validation, supervision, project administration, and funding acquisition of the study. VR contributed to funding acquisition, project administration, resource collection, supervision, and results’ validation. All authors were involved in writing, reviewing, and editing the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</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>Mendu</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Divino-Filho</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Vanholder</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Davies</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Damron</surname>
              <given-names>KC</given-names>
            </name>
            <name name-style="western">
              <surname>Gallego</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Seger</surname>
              <given-names>M</given-names>
            </name>
            <collab>International Home Dialysis Roundtable Steering Committee</collab>
          </person-group>
          <article-title>Expanding utilization of home dialysis: an action agenda from the first international home dialysis roundtable</article-title>
          <source>Kidney Med</source>
          <year>2021</year>
          <volume>3</volume>
          <issue>4</issue>
          <fpage>635</fpage>
          <lpage>43</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2590-0595(21)00100-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.xkme.2021.04.004</pub-id>
          <pub-id pub-id-type="medline">34401729</pub-id>
          <pub-id pub-id-type="pii">S2590-0595(21)00100-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8350829</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liyanage</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ninomiya</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Neal</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Patrice</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Okpechi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lv</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Garg</surname>
              <given-names>AX</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rodgers</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gallagher</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kotwal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cass</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Perkovic</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Worldwide access to treatment for end-stage kidney disease: a systematic review</article-title>
          <source>Lancet</source>
          <year>2015</year>
          <month>05</month>
          <day>16</day>
          <volume>385</volume>
          <issue>9981</issue>
          <fpage>1975</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(14)61601-9</pub-id>
          <pub-id pub-id-type="medline">25777665</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(14)61601-9</pub-id>
        </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>Vanholder</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Annemans</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bello</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Bikbov</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Gallego</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gansevoort</surname>
              <given-names>RT</given-names>
            </name>
            <name name-style="western">
              <surname>Lameire</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Luyckx</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Noruisiene</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Oostrom</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wanner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wieringa</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Fighting the unbearable lightness of neglecting kidney health: the decade of the kidney</article-title>
          <source>Clin Kidney J</source>
          <year>2021</year>
          <month>07</month>
          <volume>14</volume>
          <issue>7</issue>
          <fpage>1719</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34221379"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/ckj/sfab070</pub-id>
          <pub-id pub-id-type="medline">34221379</pub-id>
          <pub-id pub-id-type="pii">sfab070</pub-id>
          <pub-id pub-id-type="pmcid">PMC8243275</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>Brück</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Stel</surname>
              <given-names>VS</given-names>
            </name>
            <name name-style="western">
              <surname>Gambaro</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hallan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Völzke</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ärnlöv</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kastarinen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Guessous</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Vinhas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stengel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Brenner</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chudek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Romundstad</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tomson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>AO</given-names>
            </name>
            <name name-style="western">
              <surname>Bello</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Ferrieres</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Palmieri</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Browne</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Capuano</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Van Biesen</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Zoccali</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gansevoort</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Navis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rothenbacher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ferraro</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Nitsch</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wanner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jager</surname>
              <given-names>KJ</given-names>
            </name>
            <collab>European CKD Burden Consortium</collab>
          </person-group>
          <article-title>CKD prevalence varies across the European general population</article-title>
          <source>J Am Soc Nephrol</source>
          <year>2016</year>
          <month>07</month>
          <volume>27</volume>
          <issue>7</issue>
          <fpage>2135</fpage>
          <lpage>47</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26701975"/>
          </comment>
          <pub-id pub-id-type="doi">10.1681/ASN.2015050542</pub-id>
          <pub-id pub-id-type="medline">26701975</pub-id>
          <pub-id pub-id-type="pii">ASN.2015050542</pub-id>
          <pub-id pub-id-type="pmcid">PMC4926978</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>GBD Chronic Kidney Disease Collaboration</collab>
          </person-group>
          <article-title>Global, regional, and national burden of chronic kidney disease, 1990-2017: a systematic analysis for the Global Burden of Disease Study 2017</article-title>
          <source>Lancet</source>
          <year>2020</year>
          <month>02</month>
          <day>29</day>
          <volume>395</volume>
          <issue>10225</issue>
          <fpage>709</fpage>
          <lpage>33</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0140-6736(20)30045-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(20)30045-3</pub-id>
          <pub-id pub-id-type="medline">32061315</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(20)30045-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7049905</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>Rygh</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Arild</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Johnsen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rumpsfeld</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Choosing to live with home dialysis-patients' experiences and potential for telemedicine support: a qualitative study</article-title>
          <source>BMC Nephrol</source>
          <year>2012</year>
          <month>03</month>
          <day>19</day>
          <volume>13</volume>
          <fpage>13</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcnephrol.biomedcentral.com/articles/10.1186/1471-2369-13-13"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2369-13-13</pub-id>
          <pub-id pub-id-type="medline">22429705</pub-id>
          <pub-id pub-id-type="pii">1471-2369-13-13</pub-id>
          <pub-id pub-id-type="pmcid">PMC3355039</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>Malmström</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Roine</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Heikkilä</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Räsänen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sintonen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Muroma-Karttunen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Honkanen</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Cost analysis and health-related quality of life of home and self-care satellite haemodialysis</article-title>
          <source>Nephrol Dial Transplant</source>
          <year>2008</year>
          <month>06</month>
          <volume>23</volume>
          <issue>6</issue>
          <fpage>1990</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1093/ndt/gfm910</pub-id>
          <pub-id pub-id-type="medline">18223263</pub-id>
          <pub-id pub-id-type="pii">gfm910</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>Wu</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Dhaygude</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tennankore</surname>
              <given-names>KK</given-names>
            </name>
          </person-group>
          <article-title>Home dialysis in older adults: challenges and solutions</article-title>
          <source>Clin Kidney J</source>
          <year>2023</year>
          <month>03</month>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>422</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36865019"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/ckj/sfac220</pub-id>
          <pub-id pub-id-type="medline">36865019</pub-id>
          <pub-id pub-id-type="pii">sfac220</pub-id>
          <pub-id pub-id-type="pmcid">PMC9972827</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>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ku</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>eHealth in kidney care</article-title>
          <source>Nat Rev Nephrol</source>
          <year>2020</year>
          <month>07</month>
          <volume>16</volume>
          <issue>7</issue>
          <fpage>368</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32238923"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41581-020-0271-z</pub-id>
          <pub-id pub-id-type="medline">32238923</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41581-020-0271-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7110432</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>Hölsä</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Valkonen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Viitanen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rauta</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Kohti käyttäjälähtöisiä kotidialyysin sähköisiä terveyspalveluita: Potilaskokemus ja ammattilaisten tarpeet suunnittelun lähtökohtana</article-title>
          <source>FinJeHeW</source>
          <year>2022</year>
          <month>05</month>
          <day>09</day>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>55</fpage>
          <pub-id pub-id-type="doi">10.23996/fjhw.114929</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>Cornelis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tennankore</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Goffin</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rauta</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Honkanen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Őzyilmaz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thanaraj</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Jayanti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mitra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van der Sande</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Kooman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>An international feasibility study of home haemodialysis in older patients</article-title>
          <source>Nephrol Dial Transplant</source>
          <year>2014</year>
          <month>12</month>
          <volume>29</volume>
          <issue>12</issue>
          <fpage>2327</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1093/ndt/gfu260</pub-id>
          <pub-id pub-id-type="medline">25085237</pub-id>
          <pub-id pub-id-type="pii">gfu260</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>Muroma-Karttunen</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Almost anyone can have home therapy but can we overcome the barriers?</article-title>
          <source>J Ren Care</source>
          <year>2013</year>
          <month>01</month>
          <volume>39 Suppl 1</volume>
          <fpage>22</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1755-6686.2013.00331.x</pub-id>
          <pub-id pub-id-type="medline">23464910</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Beerlage-de Jong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Holistic development of eHealth technology</article-title>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>131</fpage>
          <lpage>66</lpage>
        </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>van Gemert-Pijnen</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Nijland</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>van Limburg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ossebaard</surname>
              <given-names>HC</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Eysenbach</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Seydel</surname>
              <given-names>ER</given-names>
            </name>
          </person-group>
          <article-title>A holistic framework to improve the uptake and impact of eHealth technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2011</year>
          <month>12</month>
          <day>05</day>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>e111</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2011/4/e111/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1672</pub-id>
          <pub-id pub-id-type="medline">22155738</pub-id>
          <pub-id pub-id-type="pii">v13i4e111</pub-id>
          <pub-id pub-id-type="pmcid">PMC3278097</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>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Keizer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Beerlage-de Jong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Köhle</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Methods for human-centered eHealth development: narrative scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>01</month>
          <day>27</day>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>e31858</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/1/e31858/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/31858</pub-id>
          <pub-id pub-id-type="medline">35084359</pub-id>
          <pub-id pub-id-type="pii">v24i1e31858</pub-id>
          <pub-id pub-id-type="pmcid">PMC8832261</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <article-title>ISO 9241-210:2019 Ergonomics of human-system interaction - part 210: Human-centred design for interactive systems</article-title>
          <source>International Organization for Standardization (ISO)</source>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/77520.html">https://www.iso.org/standard/77520.html</ext-link>
          </comment>
        </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>Webster</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Nagler</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Morton</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Masson</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Chronic kidney disease</article-title>
          <source>Lancet</source>
          <year>2017</year>
          <month>03</month>
          <day>25</day>
          <volume>389</volume>
          <issue>10075</issue>
          <fpage>1238</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(16)32064-5</pub-id>
          <pub-id pub-id-type="medline">27887750</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(16)32064-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Development of home dialysis</article-title>
          <source>CleverHealth Network</source>
          <access-date>2023-01-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cleverhealth.fi/en/development-of-home-dialysis/">https://www.cleverhealth.fi/en/development-of-home-dialysis/</ext-link>
          </comment>
        </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>Gould</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Designing for usability: key principles and what designers think</article-title>
          <source>Commun ACM</source>
          <year>1985</year>
          <month>03</month>
          <volume>28</volume>
          <issue>3</issue>
          <fpage>300</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/pdf/10.1145/3166.3170"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3166.3170</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>Eysenbach</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>What is e-health?</article-title>
          <source>J Med Internet Res</source>
          <year>2001</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>E20</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2001/2/e20/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3.2.e20</pub-id>
          <pub-id pub-id-type="medline">11720962</pub-id>
          <pub-id pub-id-type="pmcid">PMC1761894</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Kip</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Jong</surname>
              <given-names>NB</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kelders</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Introducing eHealth</article-title>
          <source>eHealth Research, Theory and Development: A Multi-Disciplinary Approach</source>
          <year>2018</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
          <fpage>3</fpage>
          <lpage>26</lpage>
        </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>Brands</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Gouw</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Beestrum</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cronin</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Fijnvandraat</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Badawy</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Patient-centered digital health records and their effects on health outcomes: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>12</month>
          <day>22</day>
          <volume>24</volume>
          <issue>12</issue>
          <fpage>e43086</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/12/e43086/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/43086</pub-id>
          <pub-id pub-id-type="medline">36548034</pub-id>
          <pub-id pub-id-type="pii">v24i12e43086</pub-id>
          <pub-id pub-id-type="pmcid">PMC9816956</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Valkonen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Karisalmi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kaipio</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kujala</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Remote interviews and visual timelines with patients: lessons learned</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>05</month>
          <day>27</day>
          <volume>281</volume>
          <fpage>845</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210298</pub-id>
          <pub-id pub-id-type="medline">34042793</pub-id>
          <pub-id pub-id-type="pii">SHTI210298</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Borycki</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Parush</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A case study of patient journey mapping to identify gaps in healthcare: learning from experience with cancer diagnosis and treatment</article-title>
          <source>Knowl Manag E-Learn</source>
          <year>2020</year>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>405</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.34105/j.kmel.2020.12.022"/>
          </comment>
          <pub-id pub-id-type="doi">10.34105/j.kmel.2020.12.022</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ilen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ahola</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Niinimäki</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Empathy in a technology-driven design process: designing for users without a voice of their own</article-title>
          <source>Nordes</source>
          <year>2019</year>
          <month>05</month>
          <day>10</day>
          <volume>8</volume>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.designresearchsociety.org/cgi/viewcontent.cgi?article=1526&#38;context=nordes"/>
          </comment>
          <pub-id pub-id-type="doi">10.21606/nordes.2019.021</pub-id>
        </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>Ector</surname>
              <given-names>GI</given-names>
            </name>
            <name name-style="western">
              <surname>Westerweel</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Braspenning</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Heeren</surname>
              <given-names>BC</given-names>
            </name>
            <name name-style="western">
              <surname>Vinck</surname>
              <given-names>OM</given-names>
            </name>
            <name name-style="western">
              <surname>de Jong</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Janssen</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Blijlevens</surname>
              <given-names>NM</given-names>
            </name>
          </person-group>
          <article-title>The development of a web-based, patient-centered intervention for patients with chronic myeloid leukemia (CMyLife): design thinking development approach</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>05</month>
          <day>15</day>
          <volume>22</volume>
          <issue>5</issue>
          <fpage>e15895</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/5/e15895/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15895</pub-id>
          <pub-id pub-id-type="medline">32412424</pub-id>
          <pub-id pub-id-type="pii">v22i5e15895</pub-id>
          <pub-id pub-id-type="pmcid">PMC7260663</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leary</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cacchione</surname>
              <given-names>PZ</given-names>
            </name>
            <name name-style="western">
              <surname>Demiris</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Carthon</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Bauermeister</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>An integrative review of human-centered design and design thinking for the creation of health interventions</article-title>
          <source>Nurs Forum</source>
          <year>2022</year>
          <month>11</month>
          <volume>57</volume>
          <issue>6</issue>
          <fpage>1137</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1111/nuf.12805</pub-id>
          <pub-id pub-id-type="medline">36255150</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McCarthy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O’Raghallaigh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Woodworth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>YL</given-names>
            </name>
            <name name-style="western">
              <surname>Kenny</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Adam</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>An integrated patient journey mapping tool for embedding quality in healthcare service reform</article-title>
          <source>J Decis Syst</source>
          <year>2016</year>
          <month>06</month>
          <day>16</day>
          <volume>25</volume>
          <issue>sup1</issue>
          <fpage>354</fpage>
          <lpage>68</lpage>
          <pub-id pub-id-type="doi">10.1080/12460125.2016.1187394</pub-id>
        </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>He</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Simonse</surname>
              <given-names>LW</given-names>
            </name>
          </person-group>
          <article-title>A Patient journey map to improve the home isolation experience of persons with mild COVID-19: design research for service touchpoints of artificial intelligence in eHealth</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>04</month>
          <day>12</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>e23238</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/4/e23238/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23238</pub-id>
          <pub-id pub-id-type="medline">33444156</pub-id>
          <pub-id pub-id-type="pii">v9i4e23238</pub-id>
          <pub-id pub-id-type="pmcid">PMC8043148</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McCarthy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O'Raghallaigh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Woodworth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>YY</given-names>
            </name>
            <name name-style="western">
              <surname>Kenny</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Adam</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Embedding the pillars of quality in health information technology solutions using "integrated patient journey mapping" (IPJM): case study</article-title>
          <source>JMIR Hum Factors</source>
          <year>2020</year>
          <month>09</month>
          <day>17</day>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>e17416</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2020/3/e17416/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17416</pub-id>
          <pub-id pub-id-type="medline">32940610</pub-id>
          <pub-id pub-id-type="pii">v7i3e17416</pub-id>
          <pub-id pub-id-type="pmcid">PMC7530692</pub-id>
        </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>Benson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Albanese</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatia</surname>
              <given-names>KP</given-names>
            </name>
            <name name-style="western">
              <surname>Cavillon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cuffe</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>König</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Reinhard</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Graessner</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Development of a patient journey map for people living with cervical dystonia</article-title>
          <source>Orphanet J Rare Dis</source>
          <year>2022</year>
          <month>03</month>
          <day>21</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>130</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ojrd.biomedcentral.com/articles/10.1186/s13023-022-02270-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13023-022-02270-4</pub-id>
          <pub-id pub-id-type="medline">35313909</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13023-022-02270-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC8935780</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wilden</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Herman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Botling knowledge and sharing it - using patient journey mapping to build evidence and improve aboriginal renal patent care</article-title>
          <source>Ren Soc Australas J</source>
          <year>2016</year>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>48</fpage>
          <lpage>55</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://search.informit.org/doi/10.3316/informit.182564296613440"/>
          </comment>
          <pub-id pub-id-type="doi">10.3316/informit.182564296613440</pub-id>
        </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>Joseph</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Borycki</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>Patient journey mapping: current practices, challenges and future opportunities in healthcare</article-title>
          <source>Knowl Manag E-Learn</source>
          <year>2020</year>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>387</fpage>
          <lpage>404</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.34105/j.kmel.2020.12.021"/>
          </comment>
          <pub-id pub-id-type="doi">10.34105/j.kmel.2020.12.021</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>Schäpers</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Krewer</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Yasuoka</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Becker</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Heller</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Koenig</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Determining design requirements for active aging: personas, experience maps, and stakeholders</article-title>
          <source>Gerontechnology</source>
          <year>2017</year>
          <month>10</month>
          <day>31</day>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>139</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/320897079_Determining_design_requirements_for_active_aging_Personas_experience_maps_and_stakeholders"/>
          </comment>
          <pub-id pub-id-type="doi">10.4017/gt.2017.16.3.003.00</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>Hall</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Kunz</surname>
              <given-names>BF</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Dawson</surname>
              <given-names>RI</given-names>
            </name>
            <name name-style="western">
              <surname>Powers</surname>
              <given-names>RS</given-names>
            </name>
          </person-group>
          <article-title>The cancer experience map: an approach to including the patient voice in supportive care solutions</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>05</month>
          <day>28</day>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>e132</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/5/e132/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3652</pub-id>
          <pub-id pub-id-type="medline">26022846</pub-id>
          <pub-id pub-id-type="pii">v17i5e132</pub-id>
          <pub-id pub-id-type="pmcid">PMC4468569</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <article-title>Ageing Europe — looking at the lives of older people in the EU — 2020 edition</article-title>
          <source>Eurostat</source>
          <year>2020</year>
          <access-date>2023-01-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/eurostat/documents/3217494/11478057/KS-02-20-655-EN-N.pdf/9b09606c-d4e8-4c33-63d2-3b20d5c19c91?t=1604055531000">https://ec.europa.eu/eurostat/documents/3217494/11478057/KS-02-20-655-EN-N.pdf/9b09606c-d4e8-4c33-63d2-3b20d5c19c91?t=1604055531000</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>11rc population according to age (5-year) and sex, 1865-2022</article-title>
          <source>Statistics Finland</source>
          <access-date>2023-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pxdata.stat.fi/PxWeb/pxweb/en/StatFin/StatFin__vaerak/statfin_vaerak_pxt_11rc.px/">https://pxdata.stat.fi/PxWeb/pxweb/en/StatFin/StatFin__vaerak/statfin_vaerak_pxt_11rc.px/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <article-title>Digital Skills Report 2023</article-title>
          <source>Digital and Population Data Services Agency</source>
          <access-date>2023-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dvv.fi/documents/16079645/0/Digitaitoraportti_2023_saavutettava.pdf/4d2f74b1-0baf-a06a-f28e-954bb8df491d/Digitaitoraportti_2023_saavutettava.pdf?t=1702556379736">https://dvv.fi/documents/16079645/0/Digitaitoraportti_2023_saavutettava.pdf/4d2f74b1-0baf-a06a-f28e-954bb8df491d/Digitaitoraportti_2023_saavutettava.pdf?t=1702556379736</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>Finnish registry for kidney diseases 2017</article-title>
          <source>Munuais- ja maksaliitto</source>
          <access-date>2023-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://muma.fi/wp-content/uploads/2024/02/Suomen-munuaistautirekisteri-vuosiraportti-2017.pdf">https://muma.fi/wp-content/uploads/2024/02/Suomen-munuaistautirekisteri-vuosiraportti-2017.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ware</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bartlett</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Paré</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Symeonidis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Tannenbaum</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bartlett</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Poissant</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Using eHealth technologies: interests, preferences, and concerns of older adults</article-title>
          <source>Interact J Med Res</source>
          <year>2017</year>
          <month>03</month>
          <day>23</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>e3</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.i-jmr.org/2017/1/e3/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/ijmr.4447</pub-id>
          <pub-id pub-id-type="medline">28336506</pub-id>
          <pub-id pub-id-type="pii">v6i1e3</pub-id>
          <pub-id pub-id-type="pmcid">PMC5383803</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Backonja</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Thielke</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Older adults' current and potential uses of information technologies in a changing world: a theoretical perspective</article-title>
          <source>Int J Aging Hum Dev</source>
          <year>2014</year>
          <month>12</month>
          <volume>80</volume>
          <issue>1</issue>
          <fpage>41</fpage>
          <lpage>63</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26215298"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/0091415015591109</pub-id>
          <pub-id pub-id-type="medline">26215298</pub-id>
          <pub-id pub-id-type="pii">80/1/41</pub-id>
          <pub-id pub-id-type="pmcid">PMC4522707</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Latulipe</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gatto</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>HT</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Quandt</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Bertoni</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Arcury</surname>
              <given-names>TA</given-names>
            </name>
          </person-group>
          <article-title>Design considerations for patient portal adoption by low-income, older adults</article-title>
          <source>Proc SIGCHI Conf Hum Factor Comput Syst</source>
          <year>2015</year>
          <month>04</month>
          <volume>2015</volume>
          <fpage>3859</fpage>
          <lpage>68</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27077140"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/2702123.2702392</pub-id>
          <pub-id pub-id-type="medline">27077140</pub-id>
          <pub-id pub-id-type="pmcid">PMC4827765</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reiners</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sturm</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bouw</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wouters</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Sociodemographic factors influencing the use of eHealth in people with chronic diseases</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2019</year>
          <month>02</month>
          <day>21</day>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>645</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph16040645"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph16040645</pub-id>
          <pub-id pub-id-type="medline">30795623</pub-id>
          <pub-id pub-id-type="pii">ijerph16040645</pub-id>
          <pub-id pub-id-type="pmcid">PMC6406337</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheibe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reichelt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bellmann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kirch</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Acceptance factors of mobile apps for diabetes by patients aged 50 or older: a qualitative study</article-title>
          <source>Med 2 0</source>
          <year>2015</year>
          <month>03</month>
          <day>02</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>e1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medicine20.com/2015/1/e1/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/med20.3912</pub-id>
          <pub-id pub-id-type="medline">25733033</pub-id>
          <pub-id pub-id-type="pii">v4i1e1</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376102</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Blandford</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Furniss</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Makri</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Qualitative HCI Research: Going Behind the Scenes</source>
          <year>2016</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leinonen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Design principles of eHealth services for chronically ill patients</article-title>
          <source>Master of Science Thesis, Tampere University</source>
          <year>2021</year>
          <access-date>2023-01-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://trepo.tuni.fi/handle/10024/130761">https://trepo.tuni.fi/handle/10024/130761</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Corbin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Strauss</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory</source>
          <year>2014</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Boyatzis</surname>
              <given-names>RE</given-names>
            </name>
          </person-group>
          <source>Transforming Qualitative Information: Thematic Analysis and Code Development</source>
          <year>1998</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using thematic analysis in psychology</article-title>
          <source>Qual Res Psychol</source>
          <year>2006</year>
          <month>01</month>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaptelinin</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Making the case for an existential perspective in HCI research on mortality and death</article-title>
          <source>Proceedings of the 2016 CHI Conference Extended Abstracts on Human Factors in Computing Systems</source>
          <year>2016</year>
          <conf-name>CHI EA '16</conf-name>
          <conf-date>May 7-12, 2016</conf-date>
          <conf-loc>San Jose, CA</conf-loc>
          <fpage>352</fpage>
          <lpage>64</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.1145/2851581.2892585#:~:text=The%20paper%20discusses%20some%20of,and%20evaluation%20%2D%2D%20is%20not"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/2851581.2892585</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaptelinin</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Technology and the givens of existence: toward an existential inquiry framework in HCI research</article-title>
          <source>Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems</source>
          <year>2018</year>
          <conf-name>CHI '18</conf-name>
          <conf-date>April 21-26, 2018</conf-date>
          <conf-loc>Montreal, QC</conf-loc>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.1145/3173574.3173844"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3173574.3173844</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sadeghian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Laschke</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hassenzahl</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Dying, death, and the afterlife in human-computer interaction. a scoping review</article-title>
          <source>Proceedings of the 2023 CHI Conference on Human Factors in Computing Systems</source>
          <year>2023</year>
          <conf-name>CHI '23</conf-name>
          <conf-date>April 23-28, 2023</conf-date>
          <conf-loc>Hamburg, Germany</conf-loc>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.1145/3544548.3581199"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3544548.3581199</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>My Kanta pages - citizens</article-title>
          <source>Kanta Services</source>
          <access-date>2023-01-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.kanta.fi/en/my-kanta-pages">https://www.kanta.fi/en/my-kanta-pages</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <article-title>Maisa makes life easier</article-title>
          <source>Client Portal Maisa</source>
          <access-date>2023-01-13</access-date>
          <publisher-name>Apotti</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.apotti.fi/en/client-portal-maisa/">https://www.apotti.fi/en/client-portal-maisa/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kujala</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kauppinen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rekola</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Bridging the gap between user needs and user requirements</article-title>
          <source>Proceedings of the 2021 Panhellenic Conference with International Participation in Human-Computer Interaction</source>
          <year>2021</year>
          <conf-name>PC-HCI '21</conf-name>
          <conf-date>July 24-29, 2021</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <fpage>45</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://citeseerx.ist.psu.edu/document?repid=rep1&#38;type=pdf&#38;doi=62823e8ccba3c33fa89ddb74b45c1d4c49ac878d"/>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
