<?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">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</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">v6i10e11076</article-id>
    <article-id pub-id-type="pmid">30341047</article-id>
    <article-id pub-id-type="doi">10.2196/11076</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>Teleconsultation Using Mobile Phones for Diagnosis and Acute Care of Burn Injuries Among Emergency Physicians: Mixed-Methods Study</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Eysenbach</surname>
          <given-names>Gunther</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Mars</surname>
          <given-names>Maurice</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Pecina</surname>
          <given-names>Jennifer</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Blondon</surname>
          <given-names>Katie</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1" corresp="yes" equal-contrib="yes">
      <name name-style="western">
        <surname>Klingberg</surname>
        <given-names>Anders</given-names>
      </name>
      <degrees>BSc, MSc</degrees>
      <xref rid="aff1" ref-type="aff">1</xref>
      <address>
        <institution>Department of Public Health Sciences</institution>
        <institution>Karolinska Institutet</institution>
        <addr-line>Solnavägen 1, 171 77</addr-line>
        <addr-line>Stockholm,</addr-line>
        <country>Sweden</country>
        <phone>46 733357727</phone>
        <email>anders.klingberg@ki.se</email>
      </address>  
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-5937-753X</ext-link></contrib>
      <contrib contrib-type="author" id="contrib2" equal-contrib="yes">
        <name name-style="western">
          <surname>Wallis</surname>
          <given-names>Lee Alan</given-names>
        </name>
        <degrees>MBChB, MD, FRCS Edin (A&#38;E), FRCEM</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-2711-3139</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib3" equal-contrib="yes">
        <name name-style="western">
          <surname>Hasselberg</surname>
          <given-names>Marie</given-names>
        </name>
        <degrees>PhD</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-6522-7941</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib4" equal-contrib="yes">
        <name name-style="western">
          <surname>Yen</surname>
          <given-names>Po-Yin</given-names>
        </name>
        <degrees>RN, PhD</degrees>
        <xref rid="aff3" ref-type="aff">3</xref>
        <xref rid="aff4" ref-type="aff">4</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-7061-4185</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib5" equal-contrib="yes">
        <name name-style="western">
          <surname>Fritzell</surname>
          <given-names>Sara Caroline</given-names>
        </name>
        <degrees>MPH, PhD</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-8463-7759</ext-link>
      </contrib>
    </contrib-group>
    <aff id="aff1">
    <label>1</label>
    <institution>Department of Public Health Sciences</institution>
    <institution>Karolinska Institutet</institution>  
    <addr-line>Stockholm</addr-line>
    <country>Sweden</country></aff>
    <aff id="aff2">
    <label>2</label>
    <institution>Division of Emergency Medicine</institution>
    <institution>Faculty of Medicine and Health Sciences</institution>  
    <institution>Stellenbosch University</institution>  
    <addr-line>Cape Town</addr-line>
    <country>South Africa</country></aff>
    <aff id="aff3">
    <label>3</label>
    <institution>Institute for Informatics, Division of General Medical Sciences</institution>
    <institution>Department of Medicine</institution>  
    <institution>Washington University School of Medicine</institution>  
    <addr-line>St. Louis, MO</addr-line>
    <country>United States</country></aff>
    <aff id="aff4">
    <label>4</label>
    <institution>Goldfarb School of Nursing</institution>
    <institution>Barnes–Jewish College</institution>  
    <addr-line>St. Louis, MO</addr-line>
    <country>United States</country></aff>
    <author-notes>
      <corresp>Corresponding Author: Anders Klingberg 
      <email>anders.klingberg@ki.se</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><month>10</month><year>2018</year></pub-date>
    <pub-date pub-type="epub">
      <day>19</day>
      <month>10</month>
      <year>2018</year>
    </pub-date>
    <volume>6</volume>
    <issue>10</issue>
    <elocation-id>e11076</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>25</day>
        <month>5</month>
        <year>2018</year>
      </date>
      <date date-type="rev-request">
        <day>4</day>
        <month>7</month>
        <year>2018</year>
      </date>
      <date date-type="rev-recd">
        <day>18</day>
        <month>7</month>
        <year>2018</year>
      </date>
      <date date-type="accepted">
        <day>18</day>
        <month>7</month>
        <year>2018</year>
      </date>
    </history>
    <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
    <copyright-statement>©Anders Klingberg, Lee Alan Wallis, Marie Hasselberg, Po-Yin Yen, Sara Caroline Fritzell. Originally published in JMIR Mhealth and Uhealth (http://mhealth.jmir.org), 19.10.2018.</copyright-statement>
    <copyright-year>2018</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 mhealth and uhealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://mhealth.jmir.org/2018/10/e11076/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>The referral process in acute care remains challenging in many areas including burn care. Mobile phone apps designed explicitly for medical referrals and consultations could streamline the referral process by using structured templates and integrating features specific to different specialties. However, as these apps are competing with commercial chat services, usability becomes a crucial factor for successful uptake.</p>
      </sec>
      <sec sec-type="objective">
        <title>Objective</title>
        <p>The aim of this study was to assess the usability of a mobile phone app for remote consultations and referrals of burn injuries.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>A total of 24 emergency doctors and 4 burns consultants were recruited for the study. A mixed-methods approach was used including a usability questionnaire and a think-aloud interview. Think-aloud sessions were video-recorded, and content analysis was undertaken with predefined codes relating to the following 3 themes: ease of use, usefulness of content, and technology-induced errors.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>The users perceived the app to be easy to use and useful, but some problems were identified. Issues relating to usability were associated with navigation, such as scrolling and zooming. Users also had problems in understanding the meaning of some icons and terminologies. Sometimes, some users felt limited by predefined options, and they wanted to be able to freely express their clinical findings.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>We found that users faced problems mainly with navigation when the app did not work in the same way as the other apps that were frequently used. Our study also resonates with previous findings that when using standardized templates, the systems should also allow the user to express their clinical findings in their own words.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>mobile phone</kwd>
      <kwd>referral and consultation</kwd>
      <kwd>emergency medicine</kwd>
      <kwd>mHealth</kwd>
      <kwd>teleconsultations</kwd>
      <kwd>burns</kwd>
      <kwd>usability evaluation</kwd>
      <kwd>think-aloud</kwd>
      <kwd>video analysis</kwd>
      <kwd>South Africa</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The referral process between primary health care and specialized services remains challenging for several reasons, particularly in resource-constrained settings where specialists are in short supply. Inappropriate or delayed referrals result in inefficient use of resources, both financial and human, but more importantly, it may result in suboptimal care for patients [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
      <p>Electronic referral and consultation systems have been suggested as a promising replacement for paper-based referrals [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. Better medical decisions can be made as all relevant patient and clinical information is available to both the referring clinician and the specialist. Moreover, with electronic systems, the speed of communication and referrals is faster, and the quality of the information exchange is improved by using standardized templates compared with referral letters with illegible handwriting [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>One area where over- and under-referrals are common is within burn injury care [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. Two core components in the referral process of burn injuries are accurate diagnosis by the initial provider and the ability to effectively communicate these findings to a specialist for referral and management advice. Due to the visual nature of burn wounds, burn care has a tradition of utilizing image- and video-based telemedicine to enhance clinical practice and improve outcomes in patients [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. In the past, telemedicine systems have relied on expensive and bulky infrastructure, which makes implementation difficult in resource-limited settings [<xref ref-type="bibr" rid="ref18">18</xref>]. Furthermore, burn injuries are still a significant problem, especially in low- and middle-income countries [<xref ref-type="bibr" rid="ref19">19</xref>]. For best possible outcomes in this group of patients, the decision on management and facility destination (whether to transfer or not) must be made in a timely manner. As burns are often difficult to assess by inexperienced doctors [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref25">25</xref>], remote assistance can be crucial for further management and final disposition. Inaccurate estimation of the size and depth of the burn can lead to over or under fluid resuscitation with adverse effects [<xref ref-type="bibr" rid="ref26">26</xref>]. Therefore, effective consultation is paramount.</p>
      <p>In recent years, as an ad hoc solution to the shortcomings in the referral and consultation process, communication via instant messaging using mobile phones has increased among health care workers. This is exemplified by the increasing reports on the use of chat services such as WhatsApp (WhatsApp Inc) for clinical consultations both within and between hospitals [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref32">32</xref>]. The use of such chat services has often evolved spontaneously from a need for more straightforward and faster channels of communication [<xref ref-type="bibr" rid="ref33">33</xref>]. Benefits reported include shorter response time [<xref ref-type="bibr" rid="ref34">34</xref>], flattening of hierarchies, and the ability to break down geographical barriers [<xref ref-type="bibr" rid="ref35">35</xref>]. Areas in which the use of these chat services are particularly appealing are those with a prominent visual component [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref35">35</xref>], including diagnosis and management of acute burns [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. However, there are some issues using services such as WhatsApp in medical practice. One drawback is that the information that is sent is less structured and often without patient identifiers, making it hard to keep track of which patient is being discussed [<xref ref-type="bibr" rid="ref37">37</xref>]. In addition, the information including images will not be documented within the hospital information system [<xref ref-type="bibr" rid="ref37">37</xref>]. Furthermore, despite some authors emphasizing the security of WhatsApp due to its end-to-end encryption [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>], patient-related information including images is nonetheless stored on users’ phones, and it is ultimately up to the user to delete messages when no longer needed. Another problem is that by default, WhatsApp saves images and videos to the users’ photo gallery, and depending on the settings, images may be uploaded to other third-party cloud services. On the other hand, deleting messages makes it impossible for information to be audited in the future. There have been attempts to resolve these issues by developing apps intended explicitly for medical consultations [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref42">42</xref>]. Apps such as these can be tailored to contain a premade form to add demographic and clinical information, a chat function, and other features. This approach could allow for smoother consultations as the referring clinician will be prompted to provide the information that the consultant is requesting [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>Regardless of the app being used, besides proper implementation, it is essential to assess user needs and their perceptions [<xref ref-type="bibr" rid="ref43">43</xref>]. The most important aspect of technology acceptance and uptake among users is perceived usefulness—“the degree to which a person believes that using a particular system would enhance his/her job performance” [<xref ref-type="bibr" rid="ref44">44</xref>]. Another critical factor, especially for continuous use, is ease of use—“the degree to which a person believes that using a particular system would be free from effort” [<xref ref-type="bibr" rid="ref44">44</xref>]. The International Standards Organization (ISO 9241-11) defines usability as the “extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use” [<xref ref-type="bibr" rid="ref45">45</xref>].</p>
      <p>From our experience in implementing a mobile phone-based referral and consultation system for acute burn injuries in South Africa, uptake has been rather slow, where physicians still choose to call the burns consultant or send them a message via other general text messaging apps (primarily WhatsApp) [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. For example, in a recent report from Cape Town, South Africa, WhatsApp was the preferred method for communicating clinical findings for pediatric burn care [<xref ref-type="bibr" rid="ref36">36</xref>]. Although there are several reasons for the low uptake of new systems, usability is one important aspect to consider. Therefore, the aim of this study was to assess the usability of a mobile phone app for remote consultations and referrals of burn injuries.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>The Vula App</title>
        <p>Vula mobile is a mobile phone app for remote consultation and referrals between emergency doctors at point of care and specialists, which was developed by Vula Mobile, Mafami Pty Ltd. The app runs on both iPhone and Android operating systems, and it can be downloaded free of charge. The app was introduced to the Western Cape, South Africa, in 2014 and now allows for referrals to 15 specialties such as ophthalmology, orthopedics, dermatology, and burns. The app currently handles over 5000 referrals per month, with 62 specialist teams actively taking referrals on Vula. The ability to refer patients with burns was introduced in April 2016, and it handled around 250 referrals during 2017. The app provides a template for each specialty, including patient and clinical data (see <xref ref-type="fig" rid="figure1">Figure 1</xref>, screenshot 1). There are specific features related to each specialty, the ability to take photographs, and a chat function. The burns section of the app includes a feature to draw the burn on a depiction of a body, which will calculate burn size and fluid requirements (see <xref ref-type="fig" rid="figure1">Figure 1</xref>, screenshots 2, 3, and 4). This feature also allows the burns consultant to see the location, size, and depth of the burn. All the documented information including photos are only saved within the app and not saved elsewhere on the phone. The form and the features were established in collaboration with burns experts and emergency specialists before the development of the burns section of the app. When a referring clinician has completed the form, the information is uploaded to a secure server and shared with the burns specialist on call who will be notified. The specialist reviews the information on their mobile phone or computer and sends back treatment and referral advice either via predefined medical advice options or an instant messaging function. After the consultation is complete, the specialist can archive the referral, which will remove it from both the referring doctor’s and the specialist’s devices. Users are mandated to take the necessary precautions in accordance with the “South African Protection of Personal Information Act, 2013” and to act in accordance with national and local legislation. The user is prompted by the app to make sure that the patient has consented to data being stored electronically. As with any consultation, whether it is face-to-face or telephonic, both the referring doctor and the specialist have to make the appropriate medical documentation as mandated by the health care organization where they operate. In this study, participants assessed the app on their own device.</p>
      </sec>
      <sec>
        <title>Participants and Setting</title>
        <p>Cape Town has experienced rapid urbanization with a large part of its population living in suboptimal housing that is characterized by crowded living situations, lack of running water, lack of electricity, and houses built out of flammable materials [<xref ref-type="bibr" rid="ref46">46</xref>]. It has a high burden of burn injuries, with an estimated mortality rate of 7.9 per 100.000 person-years [<xref ref-type="bibr" rid="ref47">47</xref>]. In Cape Town, there are 2 hospitals with specialized burns units serving the Western Cape province. Depending on the burn severity and day-to-day capacity, patients can be treated at local clinics or referring hospitals. Furthermore, to improve referral of patients in the region, referral criteria have been implemented [<xref ref-type="bibr" rid="ref48">48</xref>]. However, studies indicate that inappropriate or delayed referrals are still commonplace in this region [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
        <p>This study was conducted in the emergency centers at 2 health facilities, 1 district hospital, and 1 health clinic in Cape Town. Participants were doctors sampled at the emergency center at Khayelitsha Hospital and Gugulethu Community Health Centre by convenience sampling. The primary focus of this study is on emergency doctors; however, an additional 4 of the burns consultants who were registered with the app were selected by convenience sampling and interviewed for the study to explore their view of the app. Although training is available upon request, no training is required to use the app. All participants had used the app for other specialties, and some participants used the app for burns consultations. Among the participants, 6 had never used the app for burns, 14 had used it less than 5 times, and 4 had used it more than 5 times. The burns consultants had all used the app for consultations at least 10 times before the interview.</p>
      </sec>
      <sec>
        <title>Evaluation Methods</title>
        <p>This study was a mixed-methods study including a qualitative approach using the think-aloud method and a questionnaire measuring different usability metrics. As the app is already in use, the goal of this usability study was to identify usability problems related to the Vula app to improve the existing app.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Screenshots of the user interface of the Vula app for burn injury consultations and referrals.</p>
          </caption>
          <graphic xlink:href="mhealth_v6i10e11076_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <sec>
          <title>Think-Aloud Protocol</title>
          <p>A think-aloud test was conducted with each participant to assess the usability of the app. The purpose of think-aloud protocols is to have users <italic>think aloud</italic> while performing a set of tasks. The users are asked to verbalize whatever they are looking at, thinking, doing, and feeling [<xref ref-type="bibr" rid="ref49">49</xref>]. The think-aloud method is suitable to generate data on the cognitive processes when performing a set of tasks [<xref ref-type="bibr" rid="ref49">49</xref>]. Participants were given a case description of a patient with 2 burn injuries on the right forearm, 1 on the back (posterior side), and 1 on the front (anterior side) (see <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>). Each burn was equal in size and covered about 3% of the body surface, 1 full thickness and 1 partial thickness. The interviewer who acted as the patient had drawn on the arm with a marker to indicate location, size, and depth to facilitate an examination. The participants were asked to use the app as they would in a real situation. Descriptions of tasks for emergency doctors are shown in <xref ref-type="table" rid="table1">Table 1</xref> and for burns specialist in <xref ref-type="table" rid="table2">Table 2</xref>. A camera (GoPro Hero4, GoPro, Inc, San Mateo, California) was mounted to each participant’s chest to record their hands holding the mobile phone (see <xref ref-type="fig" rid="figure2">Figure 2</xref>). The interviews took place during their working hours in either an empty examination room or a break room. Interviews lasted for 10 to 20 min. Data collection took place during December 2016 and August 2017. During the second period of data collection, we extended the interview by going through the app once again where the interviewer asked about their thoughts on the different parts and asked further questions about specific problems encountered.</p>
        </sec>
        <sec>
          <title>Questionnaire</title>
          <p>At the end of the interview, the participants completed the previously validated Health Information Technology Usability Evaluation Scale (Health-ITUES) [<xref ref-type="bibr" rid="ref50">50</xref>]. The Health-ITUES is a customizable questionnaire that subjectively measures the usability of eHealth tools. Each question can be customized to address the specific type of eHealth tool, the type of user, and the specific tasks that users are expected to perform using the system in a specified context. In this study, user=<italic>emergency staff</italic>, <italic>tool</italic>=app, <italic>task</italic>=management of burns, and <italic>context</italic>=emergency care services. The questionnaire covers 4 different domains: quality of work life, perceived usefulness, perceived ease of use, and user control. In total, the questionnaire contains 20 questions measured on a 5-point Likert-scale, ranging from strongly disagree (1) to strongly agree (5), as well as a <italic>non-applicable</italic> option.</p>
          <boxed-text id="box1" position="float">
            <title>Case description of patient.</title>
            <p>Weight: 80 kg</p>
            <p>Sex: Male</p>
            <p>Cause of burn: Spilled hot coffee (3% of the body surface, 1 full thickness and 1 partial thickness)</p>
            <p>When did the injury happen: 3 hours ago</p>
            <p>Medical history: Diabetes; Tuberculosis</p>
          </boxed-text>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Tasks associated with the Vula app for referral doctors.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="150"/>
              <col width="850"/>
              <thead>
                <tr valign="top">
                  <td>Task identification</td>
                  <td>Tasks associated with the Vula app for referring doctors</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Task 1</td>
                  <td>Launch app from home screen</td>
                </tr>
                <tr valign="top">
                  <td>Task 2</td>
                  <td>Choose new referral</td>
                </tr>
                <tr valign="top">
                  <td>Task 3</td>
                  <td>Choose “Burns” in the list of specialties</td>
                </tr>
                <tr valign="top">
                  <td>Task 4a</td>
                  <td>Choose doctor on call at the referral facility</td>
                </tr>
                <tr valign="top">
                  <td>Task 4b</td>
                  <td>For first time users: Press the button saying “Yes, I am allowed to refer”</td>
                </tr>
                <tr valign="top">
                  <td>Task 5</td>
                  <td>Fill out patient information</td>
                </tr>
                <tr valign="top">
                  <td>Task 6</td>
                  <td>Choose cause of burn from list</td>
                </tr>
                <tr valign="top">
                  <td>Task 7</td>
                  <td>Select how long ago the burn injury happened</td>
                </tr>
                <tr valign="top">
                  <td>Task 8</td>
                  <td>Click on “Calculate burn area”</td>
                </tr>
                <tr valign="top">
                  <td>Task 9</td>
                  <td>On the “Calculate burn area” page, draw the burn on the picture and click save</td>
                </tr>
                <tr valign="top">
                  <td>Task 10</td>
                  <td>A box will appear with the fluid calculation, and percentage of the burn area will be displayed as well as burn depth.</td>
                </tr>
                <tr valign="top">
                  <td>Task 11</td>
                  <td>If applicable, select any of the conditions in the list under medical history</td>
                </tr>
                <tr valign="top">
                  <td>Task 12</td>
                  <td>Take one or more photos of the burn injury</td>
                </tr>
                <tr valign="top">
                  <td>Task 13</td>
                  <td>Add comments</td>
                </tr>
                <tr valign="top">
                  <td>Task 14</td>
                  <td>“Click refer” or “Save and refer later”</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Tasks associated with the Vula app for burns specialists.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="150"/>
              <col width="850"/>
              <thead>
                <tr valign="top">
                  <td>Task identification</td>
                  <td>Tasks associated with the Vula app for the specialists</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Task 1</td>
                  <td>Launch app from home screen</td>
                </tr>
                <tr valign="top">
                  <td>Task 2</td>
                  <td>Select the new referral from the list of referrals</td>
                </tr>
                <tr valign="top">
                  <td>Task 3</td>
                  <td>Review the information about the referral</td>
                </tr>
                <tr valign="top">
                  <td>Task 4</td>
                  <td>Go into “Send advice” page</td>
                </tr>
                <tr valign="top">
                  <td>Task 5</td>
                  <td>Select where the patient should be treated from the drop-down list</td>
                </tr>
                <tr valign="top">
                  <td>Task 6</td>
                  <td>Choose fluid resuscitation protocol</td>
                </tr>
                <tr valign="top">
                  <td>Task 7</td>
                  <td>Choose drugs to be given</td>
                </tr>
                <tr valign="top">
                  <td>Task 8</td>
                  <td>Choose recommended dressings</td>
                </tr>
                <tr valign="top">
                  <td>Task 9</td>
                  <td>Write further instructions if any</td>
                </tr>
                <tr valign="top">
                  <td>Task 10</td>
                  <td>Write your assessment of the total burn surface area</td>
                </tr>
                <tr valign="top">
                  <td>Task 11</td>
                  <td>Write your assessment of the burn depth</td>
                </tr>
                <tr valign="top">
                  <td>Task 12</td>
                  <td>Click “send advice” button (the user will be taken to the chat window where the selected information has been compiled into a message.)</td>
                </tr>
                <tr valign="top">
                  <td>Task 13</td>
                  <td>If necessary, chat with the referring doctor</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>User taking a photo of burn injury (left picture), and camera mounted to user’s chest (right picture).</p>
            </caption>
            <graphic xlink:href="mhealth_v6i10e11076_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Usability themes and definitions.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="300"/>
              <col width="700"/>
              <thead>
                <tr valign="top">
                  <td>Usability themes</td>
                  <td>Definition</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Usability-related aspects</td>
                  <td>These codes are used to describe usability problems and issues identified when analyzing video usability data. The codes focus on aspects of the user interface and the user system</td>
                </tr>
                <tr valign="top">
                  <td>Usefulness of content codes</td>
                  <td>These codes are used to describe issues regarding the usefulness of the user interface or system being evaluated from analyzing the data</td>
                </tr>
                <tr valign="top">
                  <td>Safety- and technology-induced error codes</td>
                  <td>These codes are used to identify and tag errors made by users when analyzing data</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>Video recordings were analyzed with MAXQDA (Version 12, VERBI Software, Berlin, Germany), a software for analysis of qualitative data. The program allows for analysis of both video and text. First, the audio recordings from the video were transcribed verbatim. In MAXQDA, this can be done using timestamps to have easy access to each audio and video segment that correlates with the text segment in the transcript. The videos can be analyzed by coding directly into the timeline when viewing the video. Content analysis with predefined codes developed by Kushniruk and Borycki was used for coding the data [<xref ref-type="bibr" rid="ref51">51</xref>]. The codes cover 3 themes: usability, usefulness, and safety- and technology-induced errors (see <xref ref-type="table" rid="table3">Table 3</xref>). The coding scheme was adapted to suit this study, and codes were also added if findings did not fit the predefined codes. Conversely, some codes were omitted if they did not apply to the material. AK and SCF independently coded all interviews and discussed the labeling of each coded event. PYY worked in the final stage with AK to ensure the codes were accurately assigned to each scenario. The data from the questionnaire were analyzed using descriptive statistics with SPSS (Version 23, IBM Corp, Armonk, NY).</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>All participants were presented with both verbal and written information about the study before the interview, and written consent was obtained. Consent forms with participant identifiers were separated from the collected data. Data are presented on an aggregated level. The study was approved by the University of Cape Town, Faculty of Health Sciences Human Research Ethics Committee.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Characteristics of Study Participants</title>
        <p>Overall, 24 emergency doctors were included in the study, and all of them were working in the emergency department at the 2 different health facilities. Demographics of the study participants are presented in <xref ref-type="table" rid="table4">Table 4</xref>. Most participants were rotating, that is, they were on a short-term allocation to the emergency center. Experience in emergency care varied from 3 months to 7 years with a median time of 1 year. Participants rated their experience with burn care as either minimal (n=11), moderate (n=10), extensive (n=1), or none (n=2). The participants all used mobile phones for private and work purposes. The purpose of use was sending images, apps, or browsing the internet for reference on medical conditions, criteria, and drug dosage calculations. The mobile phones were also used to discuss cases with seniors using either instant messaging or voice calls.</p>
      </sec>
      <sec>
        <title>Findings From Think-Aloud Sessions</title>
        <p>All participants were able to complete all tasks with no major difficulties. However, several usability issues were identified. Usability issues were classified as either <italic>usability problems</italic>, <italic>usefulness of content</italic>, or <italic>safety- or technology-induced errors</italic>, as described in the Methods section (<xref ref-type="table" rid="table3">Table 3</xref>). Codes and frequency of problems encountered related to each domain in this analysis are presented in <xref ref-type="table" rid="table5">Table 5</xref>.</p>
        <sec>
        <title>Usability-Related Aspects</title>
        <p>The video analysis revealed 149 problems related to the usability of the app. Most of these problems were related to navigation, consistency, meaning of icons and terminology, and a lack of user instructions. The majority of the problems occurred in the section where the user is prompted to draw the burn on a depiction of a body (<xref ref-type="table" rid="table1">Table 1</xref>, Task 9). In this part of the app, the most prevalent problems were related to navigation, specifically to zooming and moving the picture.</p>  
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Demographics of study participants (N=24).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="800"/>
            <col width="170"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Characteristics</td>
                <td>Participants</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2"><bold>Gender, n (%)</bold></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Male</td>
                <td>12 (50)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Female</td>
                <td>12 (50)</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Age (in years)</bold></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Median</td>
                <td>27</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Mean</td>
                <td>27.63</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Range</td>
                <td>25-34</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Experience in emergency care (in months)</bold></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Median (SD)</td>
                <td>12 (18)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Range</td>
                <td>3-84</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Experience in burn care, n (%)</bold></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>None</td>
                <td>2 (8)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Minimal</td>
                <td>10 (41)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Moderate</td>
                <td>11 (45)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Extensive</td>
                <td>1 (4)</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Operating system</bold></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>iOS</td>
                <td>15</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Android</td>
                <td>9</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Usability codes, definitions, frequency of problems, and number of users experiencing problems.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="220"/>
            <col width="400"/>
            <col width="180"/>
            <col width="170"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Code</td>
                <td>Definition of code</td>
                <td>Times usability problem occurred, n</td>
                <td>Users experiencing problems (N=24), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3"><bold>Usability codes</bold></td>
                <td><break/></td>
                <td/>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Consistency</td>
                <td>Relates to aspects of consistency in the user interface</td>
                <td>23</td>
                <td>10 (42)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Font</td>
                <td>Relates to aspects of font size or text readability</td>
                <td>1</td>
                <td>1 (4)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Graphics</td>
                <td>Relates to aspects of graphics of the system</td>
                <td>4</td>
                <td>3 (13)</td>
              </tr>
              <tr valign="bottom">
                <td><break/></td>
                <td>Lack of user instructions<sup>a</sup></td>
                <td>Relates to aspects of lack of user instructions</td>
                <td>17</td>
                <td>10 (42)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Layout</td>
                <td>Relates to aspects of the layout of screens or information on those screens</td>
                <td>6</td>
                <td>5 (21)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Meaning of icons/terminology</td>
                <td>Relates to aspects of understanding language or labels used in the interface</td>
                <td>20</td>
                <td>12 (50)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Navigation</td>
                <td>Relates to aspects of moving through a system or user interface</td>
                <td>30</td>
                <td>14 (58)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Overall ease of use</td>
                <td>Coded when the user makes comments of the overall ease of use of the system</td>
                <td>27</td>
                <td>9 (38)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Speed/response time</td>
                <td>Relates to aspects of system speed or response time</td>
                <td>1</td>
                <td>1 (4)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Understanding instructions</td>
                <td>Relates to aspects of understanding user instructions</td>
                <td>5</td>
                <td>5 (21)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Visibility of system status</td>
                <td>Relates to aspects of understanding what the system is doing</td>
                <td>15</td>
                <td>11 (46)</td>
              </tr>
              <tr valign="top">
                <td colspan="3"><bold>Usefulness of content codes</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Accuracy/correctness</td>
                <td>Relates to aspects of the accuracy or correctness of information or advice provided by the system</td>
                <td>19</td>
                <td>14 (58)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Overall usefulness<sup>a</sup></td>
                <td>Coded when a user makes comments on the overall usefulness of the system</td>
                <td>5</td>
                <td>3 (13)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Relevance</td>
                <td>Relates to aspects of the relevance of information and features to the user carrying out their task.</td>
                <td>30</td>
                <td>13 (54)</td>
              </tr>
              <tr valign="top">
                <td colspan="3"><bold>Safety- and technology-induced error codes</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Mistake</td>
                <td>Coded when a review of the data indicates the user has made a mistake that is not corrected</td>
                <td>7</td>
                <td>4 (17)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Slip</td>
                <td>Coded when a review of the video data indicates the user has made a mistake but corrects the mistake</td>
                <td>34</td>
                <td>20 (83)</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Work-around</td>
                <td>Coded when the user is not using the approach to carrying out work that is recommended by the health care organization or computer system</td>
                <td>8</td>
                <td>8 (33)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>New code added to the original coding scheme.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The users often tried to move the picture using one finger instead of two, which resulted in accidental marks which had to be erased (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 6). The users expressed varying degrees of frustration when this happened. A few users mentioned that they did not see the textbox saying “Pinch to zoom, use two fingers to scroll” (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 2), which is related to the codes <italic>lack of user instructions</italic> and <italic>understanding of user instructions</italic>. This textbox is only visible when entering the page and disappears when the user starts drawing. Even if they said they saw it and knew they had to use two fingers to scroll, they would still use one finger out of habit:</p>
        <disp-quote>
          <p>So initially it took me a while. Just navigating was a bit hard, because I want to go there, want to move up, and then I kind of you know want to move. I know that you need to put two fingers I’m just not used to it.</p>
          <attrib>User 17</attrib>
        </disp-quote>
        <p>Other problems in this section were related to the layout and meaning of icons and terminology. Some users did not see the erase button and as a work-around, they canceled and re-entered (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 4). A few users also did not see the button for turning the body around to display the back of the patient, resulting in the user drawing both burns on the same side (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 5):</p>
        <disp-quote>
          <p>And then also didn’t initially see that there is a turn body to do the other side.</p>
          <attrib>User 17</attrib>
        </disp-quote>
        <p>Similarly, a few users did not know that it was possible to change the color to indicate different burn depths, indicating a lack of user instructions. There was also a problem with the system visibility in this part illustrated by the fact that users tried to press the buttons for burn depth even though they were already selected, which is indicated by a line right beneath the button (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 1). Some users also thought the percentage indicators at the bottom of the screen were buttons to select burn depth (<xref ref-type="fig" rid="figure3">Figure 3</xref>, point 3):</p>
        <disp-quote>
          <p>I didn’t see that you could change the color of the paint, I just used to write it in the description.</p>
          <attrib>User 22</attrib>
        </disp-quote>
        <p>Some users were also confused about the calculation of the burn surface, and some users did not agree with the calculated percentage in relation to their perception of how big the burn was:</p>
        <disp-quote>
          <p>It’s quite difficult to mark with like a finger, because I think with what I’ve drawn and what you have [on your arm] it’s quite a difference, in that it looks like you have a bigger burn on the diagram than what you have.</p>
          <attrib>User 22</attrib>
        </disp-quote>
        <p>Overall, most users found the drawing function to be a useful way to convey the information about burn surface and depth. However, a few users did not find it easy to use and suggested other ways of conveying the burn surface area:</p>
        <disp-quote>
          <p>This is too difficult in my opinion because when you try to zoom and then suddenly it draws I’m not a big fan of this I’m not going to lie, I rather just work it out by myself [laughing] than use this.</p>
          <attrib>User 21</attrib>
        </disp-quote></sec>
        <sec>
          <title>Usefulness of Content</title>
          <p>Many users had comments or experienced issues that related to the content of the app. These were either related to the relevance or accuracy or correctness. One re-occurring theme was that they often could not provide information that was asked for in the app, such as patient’s phone number, weight, or time of injury:</p>
          <disp-quote>
            <p>...time of injury is obviously very very important, which I think also gets guesstimated quite a bit here in this area.</p>
            <attrib>User 13</attrib>
          </disp-quote>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Usability problems identified in the drawing section.</p>
            </caption>
            <graphic xlink:href="mhealth_v6i10e11076_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>The users did not indicate that any information asked for in the app was redundant. Instead, they suggested more fields or options to provide information in some areas that they thought would be relevant. For example, a section to provide the overall condition of the patient, such as other trauma, or a section where they could describe what management had already been undertaken:</p>
          <disp-quote>
            <p>I would rather like this part again to rather to be, type in because this is like limited choice.</p>
            <attrib>User 16</attrib>
          </disp-quote>
          <disp-quote>
            <p>I don’t think there was a section that says what your management has been so far. I think that is quite helpful just to kind of let the other doctor know what you have done.</p>
            <attrib>User 17</attrib>
          </disp-quote>
          <p>Some issues were related to the accuracy and correctness of some of the information. For example, some users had problems selecting the cause of the burn and were debating whether hot coffee should be classified as a hot liquid or as hot water. Although most users did not seem to struggle when choosing the cause, some discrepancy remains; while 8 users chose <italic>hot water</italic>, 16 chose <italic>hot liquid</italic>:</p>
          <disp-quote>
            <p>...ok cause of burn, I would choose hot water burn, coffee is basically hot water, but I find that a bit ambiguous</p>
            <attrib>User 2</attrib>
          </disp-quote>
          <p>In addition, some users thought that the list of comorbidities was too limited. Many users suggested that there should be a free text field below each of these sections where they could provide more information.</p>
          <p>After the user has finished and saved the drawing of the burn, a box with the fluid calculation is displayed. The users thought this was a useful feature, but some users noted that this was not relevant information, as they would not give intravenous fluid to a patient with a small burn like in the test scenario:</p>
          <disp-quote>
            <p>So, the one thing it doesn’t speak about is whether you can use, so a minor burn like that I wouldn’t necessarily go with IV-fluids.</p>
            <attrib>User 12</attrib>
          </disp-quote>
          <p>Many users also talked about how the ability to send pictures was one of the most relevant parts of the app. Most users did not encounter any problems when taking the photos. However, one user thought that the app would automatically save photos to the phone library and was confused when he could not find them. Another user chose to take photos before starting the app and then import the pictures:</p>
          <disp-quote>
            <p>I’m going to add the photos from the gallery, because I have the photos already, ehm, so that’s the, where is the picture now? Ok, seems I lost the images.</p>
            <attrib>User 1</attrib>
          </disp-quote>
          <p>At the bottom of the form, there is a field for additional comments, which many users used to write a message to the consultant with information they thought would be relevant. These messages often included information that was already filled in, such as age and gender of the patient or the size of the burn. Many users also used this field to specify that the burn was the result of hot coffee.</p>
        </sec>
        <sec>
          <title>Safety- and Technology-Induced Error Codes</title>
          <p>This theme included slips, mistakes, and work-arounds. One of the most common issues was that users made a slip while using the drawing section. Although this did not cause any significant problems, the users found it frustrating. Only a few users made mistakes that they seemed unaware of making. One user selected an expert from the list that was not on call; during a real scenario, this could have resulted in no response. When using the drawing tool, one user only circled the burn without coloring it in, which resulted in a 0% calculation. The user manually typed in the percentage that the user estimated to be 9%. As some users did not know the body could be flipped around, these users drew both burns on the same side of the body, also resulting in a smaller burn area calculation. Slips, mistakes, and work-arounds were most of the time the result of an underlying usability problem such as understanding user instructions, meaning of icons or terminology, or visibility of system status.</p>
        </sec>
        <sec>
          <title>Other Insights</title>
          <p>During the think-aloud sessions, some users made comments about the app that was not specifically related to the design or functions of the app itself. For example, some users said they would not use the app on a small burn such as the one in the test scenario, that is, they did not find the app useful for smaller burns:</p>
          <disp-quote>
            <p>Since it’s not a circumferential burn, I would consider admitting this patient to our surgical team and for them to debride the patient rather than referring the patient. So, I wouldn’t refer the patient via the app.</p>
            <attrib>User 24</attrib>
          </disp-quote>
          <p>Furthermore, when talking about their previous experience using the app, some users said that the specialists were slow to respond, and sometimes they would call them if they had not heard back from them in a while.</p>
        </sec>
      </sec>
      <sec>
        <title>User Satisfaction</title>
        <p>Questions and scores relating to each construct in the Health-ITUES questionnaire are presented in <xref ref-type="table" rid="table6">Table 6</xref>. In general, the app scored high on most of the constructs, with the construct “ease of use” scoring the highest. Usefulness also scored high; however, the questions relating to the ability to receive management advice in a timely manner tended to be lower (items 5, 10, and 12). The construct “user control” scored the lowest, especially the items relating to error prevention (item 18 and 19).</p>
      </sec>
      <sec>
        <title>Interviews With Burns Consultants</title>
        <p>A total of 4 interviews were also conducted with burns consultants who used the app to give diagnostic support to emergency doctors. The first screen the consultants see displays all information about the patient sent by the referring doctor. From this page, they can either go into “Send advice,” “Chat,” or review photos. Some consultants did not use the app in the way it was intended to be used; mostly they found it easier to initiate a chat with the referring doctor. In one case, the consultant was unaware of the send advice function. One of the participants said, in general, it is good with predefined options, but in this app, the options were not very useful:</p>
        <disp-quote>
          <p>It irritates me that I need to tell them the dose. So, if I choose morphine, I have to write the dose. That’s standard protocol, the nurse or doctor should know this, or use another app, or it should be in this app.</p>
          <attrib>Consultant 1</attrib>
        </disp-quote>
        <p>They all found the pictures to be very beneficial as they could then more accurately assess the burn depth and size. However, 1 consultant expressed that many doctors will not clean the burns or remove blisters before taking the pictures, which then made it harder for the consultant to be able to assess the burn. The consultant suggested there should be instructions in the app about this before the user takes a picture. One consultant seemed unaware that the referring doctor could take pictures within the app and would usually ask them to send pictures through WhatsApp instead.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Health-Information Technology Usability Evaluation Scale (Health-ITUES).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="490"/>
            <col width="260"/>
            <col width="100"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Item</td>
                <td>Concept</td>
                <td>Score (1-5)</td>
                <td>Cronbach alpha</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2"><bold>Quality of work life</bold></td>
                <td><break/></td>
                <td>4.42</td>
                <td>.76</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>1. I think the app has improved the emergency staff’s ability to care for burns</td>
                <td>System impact – career mission</td>
                <td>4.67</td>
                <td>—<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>2. I think the app has been a positive addition to burn care at the hospital</td>
                <td>System impact – organizational level</td>
                <td>4.46</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>3. The app is an important part in the acute management of burns</td>
                <td>System impact – personal level</td>
                <td>4.13</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Perceived usefulness</bold></td>
                <td><break/></td>
                <td>4.14</td>
                <td>.92</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>4. Using the app makes it easier to receive expert advice on management of burns</td>
                <td>Productiveness</td>
                <td>4.5</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>5. Using the app enables me to receive burn management advice more quickly</td>
                <td>Productiveness</td>
                <td>3.70</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>6. Using the app makes it more likely that I have sufficient knowledge on how to manage acute burns</td>
                <td>Productiveness</td>
                <td>4.00</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>7. Using the app is useful for receiving information about burn management</td>
                <td>General usefulness</td>
                <td>4.13</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>8. I think that the app presents a more equitable process for burn management</td>
                <td>General usefulness</td>
                <td>4.38</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>9. I am satisfied with the app for receiving information on burn management</td>
                <td>General satisfaction</td>
                <td>4.13</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>10. I can receive information on burn management in a timely manner because of the app</td>
                <td>Performance speed</td>
                <td>3.88</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>11. Using the app increases receiving information about burn management</td>
                <td>Productiveness</td>
                <td>4.33</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>12. I am able to receive advice on burn management whenever I use the app</td>
                <td>Information needs</td>
                <td>3.88</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>Perceived ease of use</bold></td>
                <td><break/></td>
                <td>4.64</td>
                <td>.74</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>13. I am comfortable with my ability to use the app</td>
                <td>Competency</td>
                <td>4.71</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>14. Learning to operate the app is easy for me</td>
                <td>Learnability</td>
                <td>4.63</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>15. It is easy for me to become skillful at using the app</td>
                <td>Competency</td>
                <td>4.67</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>16. I find the app easy to use</td>
                <td>Ease of use</td>
                <td>4.54</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>17. I can always remember how to log on and use the app</td>
                <td>Memorability</td>
                <td>4.67</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td colspan="2"><bold>User control</bold></td>
                <td><break/></td>
                <td>3.73</td>
                <td>.55</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>18. The app gives me error messages that clearly tell me how to fix problems</td>
                <td>Error prevention</td>
                <td>2.67</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>19. Whenever I make a mistake using the app, I recover easily and quickly</td>
                <td>Error prevention</td>
                <td>3.87</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>20. The information (such as on-screen messages and other documentation) provided with the app is clear.</td>
                <td>Information needs</td>
                <td>4.33</td>
                <td>—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table6fn1">
              <p><sup>a</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Although the Health-ITUES questionnaire showed the usability to be satisfactory, the think-aloud evaluation revealed several important usability problems that should be considered for improvements for this particular app and for others planning to design apps for remote consultations.</p>
      </sec>
      <sec>
        <title>Usability</title>
        <p>Most issues occurred in the drawing feature, which is a central feature of the app that allows the users to describe the size, depth, and location of the burn. For the burns consultant, this information is of great importance when assessing a burn. Some users expressed frustration, and a few even said they thought this feature was too difficult to use. Conversely, many users said that this was one of the strengths of the app, suggesting it may be a central feature that is not present in other communication apps. The consultants also mentioned that being able to see the location of the burn visually is very important for them to do their assessment. This resonates with the findings by Blom et al in their study on expectations of burn specialists about image-based teleconsultation [<xref ref-type="bibr" rid="ref52">52</xref>].</p>
        <p>Given that the drawing function is one of the central features but at the same time where most users struggled, it calls for some reflection. Any extra added feature needs to be well justified, that is, increase the usefulness of the app, but at the same time, it needs to be easy to use, that is, free of effort. Rust et al argue that adding extra features may be attractive but could lead to a product that is overly complex with decreased usability, resulting in <italic>feature fatigue</italic> [<xref ref-type="bibr" rid="ref53">53</xref>]. Considering these problems that the users encountered, we suggest that any extra feature be well justified (add value to the user) and be designed to be easy to use.</p>
        <p>Other usability problems were related to the meaning of icons and their functionalities. Although design changes can improve these, it also demonstrates the importance of user testing with the intended users. Ehrler et al, who found similar issues assessing a mobile app to support nurses, suggest both design changes and also training to mitigate some of these problems [<xref ref-type="bibr" rid="ref54">54</xref>].</p>
        <p>Another finding related to the drawing feature was that some users did not agree with the calculation of the burn surface and said that they would have assessed the burn to be larger had they not used the app. It is well documented in the literature that nonburns specialists tend to overestimate burn surface area when visually assessing the burn [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. One way to at least make it more apparent in the app would be to have the percentage indicated on each body part as a reminder of the burn surface area.</p>
        <p>One critical part of usability testing of medical apps is to identify problems that could result in harm to the patient; for example, the fact that some users made mistakes that led to either a smaller or larger calculation of the percentage, which in turn could lead to adverse effects if this discrepancy is significant. This is one of the reasons why supplementing with photos is important so that the burns consultant can make their assessment of the burn.</p>
      </sec>
      <sec>
        <title>Usefulness of Content</title>
        <p>Although it is important that new technologies are easy to use, the usefulness of the content of a system is equally or even more important to end users [<xref ref-type="bibr" rid="ref55">55</xref>]. Although the participants found the content to be useful in the app, many users thought that the app lacked some information or options. First, many users felt limited by the predefined choices and often wanted to describe more about the injury. For example, the medical conditions that are asked for in the app are limited to a few that are of interest to the burn specialist. However, some users thought this list could have been extended. In a similar vein, many users were also not sure whether hot coffee should be classified as <italic>hot liquid, not water</italic> or <italic>hot water</italic>. Both these options are meant to indicate that the burn was a scald. <italic>Hot liquids, not water</italic> is meant to represent what can be referred to as a dense liquid burn that is caused by liquids such as milk and oil [<xref ref-type="bibr" rid="ref56">56</xref>]. In contrary to less dense liquids such as water, dense liquids will retain more heat and will adhere to the skin longer because of their higher viscosity. Therefore, such burn injuries may result in deeper burns. Although coffee or tea, for example, is not just water, it still has the same properties, which many users also mentioned. However, as one participant pointed out, if milk is added, this will change. In terms of the usability of the app, this relates to the meaning of icons/terminology, as well as information needs. At best, this may only cause confusion and irritation, but there could be instances where misunderstandings might have implications for the patient.</p>
        <p>Despite a field for additional comments at the bottom of the form, some users suggested that there should be a possibility to specify with free text under each subsection when the options were too limiting. We did not further explore why some participants felt like this, but one explanation could be that at this point in the user test, they were unaware of the comment box that is located at the end of the form. A study by Hysong et al of e-referral systems reported similar findings where the primary health practitioners felt constrained by the use of templates and that they were not able to communicate findings clearly [<xref ref-type="bibr" rid="ref57">57</xref>]. Similarly, in the tests with the burn consultants, some of them said they did not like the predefined options in their present form and would rather use the chat function instead.  Hysong et al, on the other hand, found that specialists thought that more rigid templates with mandatory fields would enhance the quality of the referrals [<xref ref-type="bibr" rid="ref57">57</xref>]. Other studies have found that feedback from consultants is more consistent and timely when referral templates are used [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref59">59</xref>]. One interesting finding regarding the comment box was that many participants used this to write a message to the specialist repeating much of the information already filled out. These messages would often be of a friendly nature including phrases such as “dear Dr” or “kind regards.” This highlights the fact that a consultation is not merely an exchange of information but also a collaboration that requires personal communication [<xref ref-type="bibr" rid="ref60">60</xref>].</p>
        <p>Our findings indicate that both emergency doctors and consultants wanted more flexibility within the system. Flexible systems can make it easier to transfer information about special cases, reducing the need for additional phone and text communication. However, when designing a system, the need for flexibility must be balanced with the need for its usability. Although it might be tempting to design a system for every scenario to maximize flexibility, one needs to take into account that when the flexibility of a system increases, so does its complexity and consequently its usability. This is often termed the flexibility-usability trade-off [<xref ref-type="bibr" rid="ref61">61</xref>], and when doing this trade-off, it is important to understand the users’ needs, both present and future. This is, however, not always possible, especially with newer technologies. In addition, as acute burn injuries can manifest in different ways, it is difficult to design a template that will fit the clinical presentation of every single patient. Esquivel et al outlined 10 recommendations for improving the effectiveness of electronic referrals [<xref ref-type="bibr" rid="ref3">3</xref>]. One recommendation that our findings support is to <italic>design and use standardized electronic referral templates that include both structured and free text fields</italic>. They argue that when designing electronic referral templates, there must be both structured fields to capture required information and free text fields for providers to freely expand on their clinical findings.</p>
        <p>The usability tests with the consultants revealed that the 2 more experienced users found the ”Send advice” function cumbersome and would rather just chat with the referring doctor. The 2 less experienced consultants seemed to be unaware of some of the functionalities in the app, such as the “Send advice” function or how to access the photos, suggesting that the user interface may not be clear for new users.</p>
      </sec>
      <sec>
        <title>Significance of Findings</title>
        <p>Although the participants in our study perceived the burns section of the app to be useful and easy to use, it is still not used on a regular basis. However, there are other reasons for low uptake that are not related to the usability of the app. These include, but are not limited to, awareness of the app, resistance to new technologies and attitudes among colleagues [<xref ref-type="bibr" rid="ref43">43</xref>]. Even though traditional means of discussing and referring patients with burns by telephonic consultations and paper-based referrals are still prevalent, recent reports from South Africa have described the use of WhatsApp as a mode of communication for clinical decision support [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. The fact that WhatsApp is very prevalent may be a reason why a specific app for medical referrals is not widely adopted. For the referring doctor seeking advice, the most important aspect will inevitably be to receive advice back from the consultant in a timely manner. Therefore, the consultants have an important role to play as pioneers for apps such as the Vula app. Nikolic et al note in their recent study that the widespread use of WhatsApp may impede the introduction of other communication apps designed for medical consultations [<xref ref-type="bibr" rid="ref62">62</xref>]. Future research should focus on identifying the barriers to using mobile phone-based referral and consultation systems.</p>
      </sec>
      <sec>
        <title>Methodological Considerations</title>
        <p>The methods and equipment for data collection used in this study were simple, low cost, and allowed for quick data collection. None of the participants objected or showed any signs of being uncomfortable wearing the recording equipment. The video coding scheme was useful and covered most aspects. However, we changed the original definitions to cover both positive and negative aspects of the events and not only focus on problems. By doing this, the data generated more findings concerning things that the users liked about the app. We also added some codes that we thought were not covered in the original coding scheme. For example, <italic>Lack of user instructions</italic> was added as an extension to the code <italic>Not understanding user instructions</italic>.</p>
        <p>During the think-aloud session, the interviewer tried not to interfere, except for encouraging the interviewee to keep talking. However, we found that the participants would mostly verbalize what they were doing but not what they were thinking and feeling. Consequently, during the second period of data collection, we extended the interview by going through the app once again where the interviewer asked about their thoughts on the different parts of the app.</p>
        <p>Although the users rated the app to be easy to use, the think-aloud interviews found several problems related to the ease of use. This is not surprising as the purpose of a usability questionnaire is to assess the users’ overall perception of the app and not identify specific problems. It is, however, useful for comparing different user groups, different designs of the app, or how user perceptions change over time.</p>
        <p>As this was a mixed-methods study spanning both emergency burn care and health informatics, we think it was a strength that the authors come from different disciplines, including public health, political science, sociology, emergency medicine, nursing, and health informatics. Another strength of the study was the large number of participants in the user tests. A limitation was the relatively homogenous sample, where all users were young junior doctors. Sonderegger et al found that age affects several usability measures such as speed and accuracy [<xref ref-type="bibr" rid="ref63">63</xref>]. Cillessen et al studied the user satisfaction of a clinical notes app and only differences by medical specialty but no differences by sex, age, professional experience, or training hours [<xref ref-type="bibr" rid="ref64">64</xref>]. Nevertheless, our sample does represent the typical user from our study population.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Mobile referral and communication systems are a relatively new concept that could simplify the consultation and referral process within burn care and other specialties. However, when a new system is competing with other technologies such as instant messaging apps or traditional phone calls, usefulness and ease of use become highly important. Although the Health-ITUES questionnaire showed high satisfaction with the system, the think-aloud interviews provided additional insights for further improvements. The users liked the ability to describe the burns through both the built-in drawing function as well as with photographs. For the burn consultants, the drawings and the photos were considered the most valuable information for their assessment. We also found that users had problems with navigation in the drawing section when the app did not act in the same way as other apps that were frequently used. There was also some confusion regarding terminology and the meaning of buttons and icons. Our study also resonates with previous findings that when using standardized electronic consultation and referral templates, the system should also allow the users to freely express their clinical findings in their own words.</p>
      </sec>
    </sec>
  </body>
  <back>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">Health-ITUES</term>
          <def>
            <p>Health-Information Technology Usability Evaluation Scale</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors are grateful for the doctors who gave their valuable time and feedback. They specially thank Sa’ad Lahri and Jennie Morgan for organizing the interviews at each hospital. The study was funded by the Swedish Research Council.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>AK, MH, PYY, and LAW contributed to the design of the study; AK, MH, PYY, and SCF contributed to the development of measurement tools; AK collected data and LAW assisted with logistics in the field. AK and SCF contributed to data analysis, and PYY assisted with unresolved codes. AK, SCF, and MH contributed to interpretation of the results. AK drafted the manuscript. All authors read, commented on, and approved the final 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>Mehrotra</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Forrest</surname>
            <given-names>CB</given-names>
          </name>
          <name name-style="western">
            <surname>Lin</surname>
            <given-names>CY</given-names>
          </name>
        </person-group>
        <article-title>Dropping the baton: specialty referrals in the United States</article-title>
        <source>Milbank Q</source>  
        <year>2011</year>  
        <month>03</month>  
        <volume>89</volume>  
        <issue>1</issue>  
        <fpage>39</fpage>  
        <lpage>68</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21418312"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1111/j.1468-0009.2011.00619.x</pub-id>
        <pub-id pub-id-type="medline">21418312</pub-id>
        <pub-id pub-id-type="pmcid">PMC3160594</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>Naseriasl</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Adham</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Janati</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>E-referral solutions: successful experiences, key features and challenges-a systematic review</article-title>
        <source>Mater Sociomed</source>  
        <year>2015</year>  
        <month>06</month>  
        <volume>27</volume>  
        <issue>3</issue>  
        <fpage>195</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26236167"/>
        </comment>  
        <pub-id pub-id-type="doi">10.5455/msm.2015.27.195-199</pub-id>
        <pub-id pub-id-type="medline">26236167</pub-id>
        <pub-id pub-id-type="pii">MSM-27-195</pub-id>
        <pub-id pub-id-type="pmcid">PMC4499295</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>Esquivel</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sittig</surname>
            <given-names>DF</given-names>
          </name>
          <name name-style="western">
            <surname>Murphy</surname>
            <given-names>DR</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Improving the effectiveness of electronic health record-based referral processes</article-title>
        <source>BMC Med Inform Decis Mak</source>  
        <year>2012</year>  
        <month>09</month>  
        <day>13</day>  
        <volume>12</volume>  
        <fpage>107</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://bmcmedinformdecismak.biomedcentral.com/articles/110.1186/1472-6947-12-107"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/1472-6947-12-107</pub-id>
        <pub-id pub-id-type="medline">22973874</pub-id>
        <pub-id pub-id-type="pii">1472-6947-12-107</pub-id>
        <pub-id pub-id-type="pmcid">PMC3492108</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>Chipp</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Walton</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Gorman</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Moiemen</surname>
            <given-names>NS</given-names>
          </name>
        </person-group>
        <article-title>Adherence to referral criteria for burns in the emergency department</article-title>
        <source>Eplasty</source>  
        <year>2008</year>  
        <month>05</month>  
        <day>09</day>  
        <volume>8</volume>  
        <fpage>e26</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18536778"/>
        </comment>  
        <pub-id pub-id-type="medline">18536778</pub-id>
        <pub-id pub-id-type="pmcid">PMC2380084</pub-id></nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Doud</surname>
            <given-names>AN</given-names>
          </name>
          <name name-style="western">
            <surname>Swanson</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Ladd</surname>
            <given-names>MR</given-names>
          </name>
          <name name-style="western">
            <surname>Neff</surname>
            <given-names>LP</given-names>
          </name>
          <name name-style="western">
            <surname>Carter</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Holmes</surname>
            <given-names>JH</given-names>
          </name>
        </person-group>
        <article-title>Referral patterns in pediatric burn patients</article-title>
        <source>Am Surg</source>  
        <year>2014</year>  
        <month>09</month>  
        <volume>80</volume>  
        <issue>9</issue>  
        <fpage>836</fpage>  
        <lpage>40</lpage>  
        <pub-id pub-id-type="medline">25197864</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>Klingberg</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Wallis</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Rode</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Stenberg</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Laflamme</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Hasselberg</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Assessing guidelines for burn referrals in a resource-constrained setting: demographic and clinical factors associated with inter-facility transfer</article-title>
        <source>Burns</source>  
        <year>2017</year>  
        <month>08</month>  
        <volume>43</volume>  
        <issue>5</issue>  
        <fpage>1070</fpage>  
        <lpage>77</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2017.01.035</pub-id>
        <pub-id pub-id-type="medline">28420571</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(17)30081-5</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>den Hollander</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Albert</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Strand</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Hardcastle</surname>
            <given-names>TC</given-names>
          </name>
        </person-group>
        <article-title>Epidemiology and referral patterns of burns admitted to the Burns Centre at Inkosi Albert Luthuli Central Hospital, Durban</article-title>
        <source>Burns</source>  
        <year>2014</year>  
        <month>09</month>  
        <volume>40</volume>  
        <issue>6</issue>  
        <fpage>1201</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2013.12.018</pub-id>
        <pub-id pub-id-type="medline">24439933</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(13)00443-9</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>Carter</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Neff</surname>
            <given-names>LP</given-names>
          </name>
          <name name-style="western">
            <surname>Holmes</surname>
            <given-names>JH</given-names>
          </name>
        </person-group>
        <article-title>Adherence to burn center referral criteria: are patients appropriately being referred?</article-title>
        <source>J Burn Care Res</source>  
        <year>2010</year>  
        <volume>31</volume>  
        <issue>1</issue>  
        <fpage>26</fpage>  
        <lpage>30</lpage>  
        <pub-id pub-id-type="doi">10.1097/BCR.0b013e3181cb8efb</pub-id>
        <pub-id pub-id-type="medline">20061833</pub-id>
        <pub-id pub-id-type="pii">01253092-201001000-00003</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>Reiband</surname>
            <given-names>HK</given-names>
          </name>
          <name name-style="western">
            <surname>Lundin</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Alsbjørn</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Sørensen</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Rasmussen</surname>
            <given-names>LS</given-names>
          </name>
        </person-group>
        <article-title>Optimization of burn referrals</article-title>
        <source>Burns</source>  
        <year>2014</year>  
        <month>05</month>  
        <volume>40</volume>  
        <issue>3</issue>  
        <fpage>397</fpage>  
        <lpage>401</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2013.08.001</pub-id>
        <pub-id pub-id-type="medline">24004853</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(13)00235-0</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>Wallace</surname>
            <given-names>DL</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>RW</given-names>
          </name>
          <name name-style="western">
            <surname>Pickford</surname>
            <given-names>MA</given-names>
          </name>
        </person-group>
        <article-title>A cohort study of acute plastic surgery trauma and burn referrals using telemedicine</article-title>
        <source>J Telemed Telecare</source>  
        <year>2007</year>  
        <volume>13</volume>  
        <issue>6</issue>  
        <fpage>282</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1258/135763307781644933</pub-id>
        <pub-id pub-id-type="medline">17785024</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>Atiyeh</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Masellis</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Conte</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Optimizing burn treatment in developing low- and middle-income countries with limited health care resources (part 1)</article-title>
        <source>Ann Burns Fire Disasters</source>  
        <year>2009</year>  
        <month>09</month>  
        <day>30</day>  
        <volume>22</volume>  
        <issue>3</issue>  
        <fpage>121</fpage>  
        <lpage>5</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21991167"/>
        </comment>  
        <pub-id pub-id-type="medline">21991167</pub-id>
        <pub-id pub-id-type="pmcid">PMC3188147</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>Saffle</surname>
            <given-names>JR</given-names>
          </name>
          <name name-style="western">
            <surname>Edelman</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Theurer</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Morris</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Cochran</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine evaluation of acute burns is accurate and cost-effective</article-title>
        <source>J Trauma</source>  
        <year>2009</year>  
        <month>08</month>  
        <volume>67</volume>  
        <issue>2</issue>  
        <fpage>358</fpage>  
        <lpage>65</lpage>  
        <pub-id pub-id-type="doi">10.1097/TA.0b013e3181ae9b02</pub-id>
        <pub-id pub-id-type="medline">19667890</pub-id>
        <pub-id pub-id-type="pii">00005373-200908000-00019</pub-id></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Turk</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Karagulle</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Aydogan</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Oguz</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Tarim</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Karakayali</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Haberal</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Use of telemedicine and telephone consultation in decision-making and follow-up of burn patients: Initial experience from two burn units</article-title>
        <source>Burns</source>  
        <year>2011</year>  
        <month>05</month>  
        <volume>37</volume>  
        <issue>3</issue>  
        <fpage>415</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2010.10.004</pub-id>
        <pub-id pub-id-type="medline">21146313</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(10)00275-5</pub-id></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Holt</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Faraklas</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Theurer</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Cochran</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Saffle</surname>
            <given-names>JR</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine use among burn centers in the United States: a survey</article-title>
        <source>J Burn Care Res</source>  
        <year>2012</year>  
        <volume>33</volume>  
        <issue>1</issue>  
        <fpage>157</fpage>  
        <lpage>62</lpage>  
        <pub-id pub-id-type="doi">10.1097/BCR.0b013e31823d0b68</pub-id>
        <pub-id pub-id-type="medline">22105096</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>Syed-Abdul</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Scholl</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>CC</given-names>
          </name>
          <name name-style="western">
            <surname>Santos</surname>
            <given-names>MD</given-names>
          </name>
          <name name-style="western">
            <surname>Jian</surname>
            <given-names>WS</given-names>
          </name>
          <name name-style="western">
            <surname>Liou</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>YC</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine utilization to support the management of the burns treatment involving patient pathways in both developed and developing countries: a case study</article-title>
        <source>J Burn Care Res</source>  
        <year>2012</year>  
        <volume>33</volume>  
        <issue>4</issue>  
        <fpage>e207</fpage>  
        <lpage>12</lpage>  
        <pub-id pub-id-type="doi">10.1097/BCR.0b013e318241b6b7</pub-id>
        <pub-id pub-id-type="medline">22249104</pub-id></nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Atiyeh</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Dibo</surname>
            <given-names>SA</given-names>
          </name>
          <name name-style="western">
            <surname>Janom</surname>
            <given-names>HH</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine and burns: an overview</article-title>
        <source>Ann Burns Fire Disasters</source>  
        <year>2014</year>  
        <month>06</month>  
        <day>30</day>  
        <volume>27</volume>  
        <issue>2</issue>  
        <fpage>87</fpage>  
        <lpage>93</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26170782"/>
        </comment>  
        <pub-id pub-id-type="medline">26170782</pub-id>
        <pub-id pub-id-type="pmcid">PMC4396801</pub-id></nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Boccara</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Bekara</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Soussi</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Legrand</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Chaouat</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Mimoun</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Serror</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Ongoing development and evaluation of a method of telemedicine: burn care management with a smartphone</article-title>
        <source>J Burn Care Res</source>  
        <year>2018</year>  
        <month>06</month>  
        <day>13</day>  
        <volume>39</volume>  
        <issue>4</issue>  
        <fpage>580</fpage>  
        <lpage>4</lpage>  
        <pub-id pub-id-type="doi">10.1093/jbcr/irx022</pub-id>
        <pub-id pub-id-type="medline">29789857</pub-id>
        <pub-id pub-id-type="pii">4683477</pub-id></nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Combi</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Pozzani</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Pozzi</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine for developing countries. A survey and some design issues</article-title>
        <source>Appl Clin Inform</source>  
        <year>2016</year>  
        <month>11</month>  
        <day>02</day>  
        <volume>7</volume>  
        <issue>4</issue>  
        <fpage>1025</fpage>  
        <lpage>50</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27803948"/>
        </comment>  
        <pub-id pub-id-type="doi">10.4338/ACI-2016-06-R-0089</pub-id>
        <pub-id pub-id-type="medline">27803948</pub-id>
        <pub-id pub-id-type="pii">2016-06-R-0089</pub-id>
        <pub-id pub-id-type="pmcid">PMC5228142</pub-id></nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rybarczyk</surname>
            <given-names>MM</given-names>
          </name>
          <name name-style="western">
            <surname>Schafer</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Elm</surname>
            <given-names>CM</given-names>
          </name>
          <name name-style="western">
            <surname>Sarvepalli</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Vaswani</surname>
            <given-names>PA</given-names>
          </name>
          <name name-style="western">
            <surname>Balhara</surname>
            <given-names>KS</given-names>
          </name>
          <name name-style="western">
            <surname>Carlson</surname>
            <given-names>LC</given-names>
          </name>
          <name name-style="western">
            <surname>Jacquet</surname>
            <given-names>GA</given-names>
          </name>
        </person-group>
        <article-title>A systematic review of burn injuries in low- and middle-income countries: epidemiology in the WHO-defined African Region</article-title>
        <source>Afr J Emerg Med</source>  
        <year>2017</year>  
        <month>03</month>  
        <volume>7</volume>  
        <issue>1</issue>  
        <fpage>30</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.afjem.2017.01.006</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>Harish</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Raymond</surname>
            <given-names>AP</given-names>
          </name>
          <name name-style="western">
            <surname>Issler</surname>
            <given-names>AC</given-names>
          </name>
          <name name-style="western">
            <surname>Lajevardi</surname>
            <given-names>SS</given-names>
          </name>
          <name name-style="western">
            <surname>Chang</surname>
            <given-names>LY</given-names>
          </name>
          <name name-style="western">
            <surname>Maitz</surname>
            <given-names>PK</given-names>
          </name>
          <name name-style="western">
            <surname>Kennedy</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>Accuracy of burn size estimation in patients transferred to adult Burn Units in Sydney, Australia: an audit of 698 patients</article-title>
        <source>Burns</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>41</volume>  
        <issue>1</issue>  
        <fpage>91</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2014.05.005</pub-id>
        <pub-id pub-id-type="medline">24972983</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(14)00170-3</pub-id></nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Baartmans</surname>
            <given-names>MG</given-names>
          </name>
          <name name-style="western">
            <surname>van Baar</surname>
            <given-names>ME</given-names>
          </name>
          <name name-style="western">
            <surname>Boxma</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Dokter</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Tibboel</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Nieuwenhuis</surname>
            <given-names>MK</given-names>
          </name>
        </person-group>
        <article-title>Accuracy of burn size assessment prior to arrival in Dutch burn centres and its consequences in children: a nationwide evaluation</article-title>
        <source>Injury</source>  
        <year>2012</year>  
        <month>09</month>  
        <volume>43</volume>  
        <issue>9</issue>  
        <fpage>1451</fpage>  
        <lpage>6</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.injury.2011.06.027</pub-id>
        <pub-id pub-id-type="medline">21741042</pub-id>
        <pub-id pub-id-type="pii">S0020-1383(11)00264-6</pub-id></nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Thom</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Appraising current methods for preclinical calculation of burn size - a pre-hospital perspective</article-title>
        <source>Burns</source>  
        <year>2017</year>  
        <month>02</month>  
        <volume>43</volume>  
        <issue>1</issue>  
        <fpage>127</fpage>  
        <lpage>36</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2016.07.003</pub-id>
        <pub-id pub-id-type="medline">27575669</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(16)30208-X</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>Goverman</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Bittner</surname>
            <given-names>EA</given-names>
          </name>
          <name name-style="western">
            <surname>Friedstat</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Moore</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Nozari</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ibrahim</surname>
            <given-names>AE</given-names>
          </name>
          <name name-style="western">
            <surname>Sarhane</surname>
            <given-names>KA</given-names>
          </name>
          <name name-style="western">
            <surname>Chang</surname>
            <given-names>PH</given-names>
          </name>
          <name name-style="western">
            <surname>Sheridan</surname>
            <given-names>RL</given-names>
          </name>
          <name name-style="western">
            <surname>Fagan</surname>
            <given-names>SP</given-names>
          </name>
        </person-group>
        <article-title>Discrepancy in initial pediatric burn estimates and its impact on fluid resuscitation</article-title>
        <source>J Burn Care Res</source>  
        <year>2015</year>  
        <volume>36</volume>  
        <issue>5</issue>  
        <fpage>574</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1097/BCR.0000000000000185</pub-id>
        <pub-id pub-id-type="medline">25407387</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>Chan</surname>
            <given-names>QE</given-names>
          </name>
          <name name-style="western">
            <surname>Barzi</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Cheney</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Harvey</surname>
            <given-names>JG</given-names>
          </name>
          <name name-style="western">
            <surname>Holland</surname>
            <given-names>AJ</given-names>
          </name>
        </person-group>
        <article-title>Burn size estimation in children: still a problem</article-title>
        <source>Emerg Med Australas</source>  
        <year>2012</year>  
        <month>04</month>  
        <volume>24</volume>  
        <issue>2</issue>  
        <fpage>181</fpage>  
        <lpage>6</lpage>  
        <pub-id pub-id-type="doi">10.1111/j.1742-6723.2011.01511.x</pub-id>
        <pub-id pub-id-type="medline">22487668</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>Parvizi</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Kamolz</surname>
            <given-names>LP</given-names>
          </name>
          <name name-style="western">
            <surname>Giretzlehner</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Haller</surname>
            <given-names>HL</given-names>
          </name>
          <name name-style="western">
            <surname>Trop</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Selig</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Nagele</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Lumenta</surname>
            <given-names>DB</given-names>
          </name>
        </person-group>
        <article-title>The potential impact of wrong TBSA estimations on fluid resuscitation in patients suffering from burns: things to keep in mind</article-title>
        <source>Burns</source>  
        <year>2014</year>  
        <month>03</month>  
        <volume>40</volume>  
        <issue>2</issue>  
        <fpage>241</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2013.06.019</pub-id>
        <pub-id pub-id-type="medline">24050977</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(13)00202-7</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>Dulhunty</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Boots</surname>
            <given-names>RJ</given-names>
          </name>
          <name name-style="western">
            <surname>Rudd</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Muller</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Lipman</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Increased fluid resuscitation can lead to adverse outcomes in major-burn injured patients, but low mortality is achievable</article-title>
        <source>Burns</source>  
        <year>2008</year>  
        <month>12</month>  
        <volume>34</volume>  
        <issue>8</issue>  
        <fpage>1090</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2008.01.011</pub-id>
        <pub-id pub-id-type="medline">18468802</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(08)00036-3</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>Stahl</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Katsman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Zaidman</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Keshet</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Sigal</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Eidelman</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Reliability of smartphone-based instant messaging application for diagnosis, classification, and decision-making in pediatric orthopedic trauma</article-title>
        <source>Pediatr Emerg Care</source>  
        <year>2017</year>  
        <month>07</month>  
        <day>11</day>  
        <pub-id pub-id-type="doi">10.1097/PEC.0000000000001211</pub-id>
        <pub-id pub-id-type="medline">28697157</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>Giordano</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Koch</surname>
            <given-names>HA</given-names>
          </name>
          <name name-style="western">
            <surname>Mendes</surname>
            <given-names>CH</given-names>
          </name>
          <name name-style="western">
            <surname>Bergamin</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>de Souza</surname>
            <given-names>FS</given-names>
          </name>
          <name name-style="western">
            <surname>do Amaral</surname>
            <given-names>NP</given-names>
          </name>
        </person-group>
        <article-title>WhatsApp Messenger is useful and reproducible in the assessment of tibial plateau fractures: inter- and intra-observer agreement study</article-title>
        <source>Int J Med Inform</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>84</volume>  
        <issue>2</issue>  
        <fpage>141</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2014.11.002</pub-id>
        <pub-id pub-id-type="medline">25468642</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(14)00217-2</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>Gulacti</surname>
            <given-names>U</given-names>
          </name>
          <name name-style="western">
            <surname>Lok</surname>
            <given-names>U</given-names>
          </name>
          <name name-style="western">
            <surname>Hatipoglu</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Polat</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>An analysis of WhatsApp usage for communication between consulting and emergency physicians</article-title>
        <source>J Med Syst</source>  
        <year>2016</year>  
        <month>06</month>  
        <volume>40</volume>  
        <issue>6</issue>  
        <fpage>130</fpage>  
        <pub-id pub-id-type="doi">10.1007/s10916-016-0483-8</pub-id>
        <pub-id pub-id-type="medline">27083574</pub-id>
        <pub-id pub-id-type="pii">10.1007/s10916-016-0483-8</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>Johnston</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Mobasheri</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>King</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Darzi</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>The Imperial Clarify, Design and Evaluate (CDE) approach to mHealth app development</article-title>
        <source>BMJ Innov</source>  
        <year>2015</year>  
        <month>03</month>  
        <day>31</day>  
        <volume>1</volume>  
        <issue>2</issue>  
        <fpage>39</fpage>  
        <lpage>42</lpage>  
        <pub-id pub-id-type="doi">10.1136/bmjinnov-2014-000020</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>Mars</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Scott</surname>
            <given-names>RE</given-names>
          </name>
        </person-group>
        <article-title>WhatsApp in clinical practice: a literature review</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2016</year>  
        <volume>231</volume>  
        <fpage>82</fpage>  
        <lpage>90</lpage>  
        <pub-id pub-id-type="medline">27782019</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>den Hollander</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Mars</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Smart phones make smart referrals: the use of mobile phone technology in burn care - a retrospective case series</article-title>
        <source>Burns</source>  
        <year>2017</year>  
        <month>02</month>  
        <volume>43</volume>  
        <issue>1</issue>  
        <fpage>190</fpage>  
        <lpage>4</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2016.07.015</pub-id>
        <pub-id pub-id-type="medline">27575675</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(16)30225-X</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>Mars</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Scott</surname>
            <given-names>RE</given-names>
          </name>
        </person-group>
        <article-title>Being Spontaneous: the future of telehealth implementation?</article-title>
        <source>Telemed J E Health</source>  
        <year>2017</year>  
        <month>09</month>  
        <volume>23</volume>  
        <issue>9</issue>  
        <fpage>766</fpage>  
        <lpage>72</lpage>  
        <pub-id pub-id-type="doi">10.1089/tmj.2016.0155</pub-id>
        <pub-id pub-id-type="medline">28355127</pub-id>
        <pub-id pub-id-type="pii">10.1089/tmj.2016.0155</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>Eksert</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Aşık</surname>
            <given-names>MB</given-names>
          </name>
          <name name-style="western">
            <surname>Akay</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Keklikçi</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Aydın</surname>
            <given-names>FN</given-names>
          </name>
          <name name-style="western">
            <surname>Çoban</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Kantemir</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Güngör</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Garip</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Turgut</surname>
            <given-names>MS</given-names>
          </name>
          <name name-style="western">
            <surname>Olcay</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Efficiency of instant messaging applications in coordination of emergency calls for combat injuries: a pilot study</article-title>
        <source>Ulus Travma Acil Cerrahi Derg</source>  
        <year>2017</year>  
        <month>05</month>  
        <volume>23</volume>  
        <issue>3</issue>  
        <fpage>207</fpage>  
        <lpage>11</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.journalagent.com/pubmed/linkout.asp?ISSN=1306-696X&#38;PMID=28530773"/>
        </comment>  
        <pub-id pub-id-type="medline">28530773</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>Kamel Boulos</surname>
            <given-names>MN</given-names>
          </name>
          <name name-style="western">
            <surname>Giustini</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Wheeler</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Instagram and WhatsApp in health and healthcare: an overview</article-title>
        <source>Future Internet</source>  
        <year>2016</year>  
        <month>07</month>  
        <day>26</day>  
        <volume>8</volume>  
        <issue>3</issue>  
        <fpage>1</fpage>  
        <lpage>14</lpage>  
        <pub-id pub-id-type="doi">10.3390/fi8030037</pub-id></nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Martinez</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Rogers</surname>
            <given-names>AD</given-names>
          </name>
          <name name-style="western">
            <surname>Numanoglu</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rode</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>The value of WhatsApp communication in paediatric burn care</article-title>
        <source>Burns</source>  
        <year>2018</year>  
        <month>06</month>  
        <volume>44</volume>  
        <issue>4</issue>  
        <fpage>947</fpage>  
        <lpage>55</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2017.11.005</pub-id>
        <pub-id pub-id-type="medline">29395403</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(17)30608-3</pub-id></nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Thomas</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Wanted: a WhatsApp alternative for clinicians</article-title>
        <source>BMJ</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>26</day>  
        <volume>360</volume>  
        <fpage>k928</fpage>  
        <pub-id pub-id-type="medline">29483144</pub-id></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Pecina</surname>
            <given-names>JL</given-names>
          </name>
          <name name-style="western">
            <surname>Wyatt</surname>
            <given-names>KD</given-names>
          </name>
          <name name-style="western">
            <surname>Comfere</surname>
            <given-names>NI</given-names>
          </name>
          <name name-style="western">
            <surname>Bernard</surname>
            <given-names>ME</given-names>
          </name>
          <name name-style="western">
            <surname>North</surname>
            <given-names>F</given-names>
          </name>
        </person-group>
        <article-title>Uses of mobile device digital photography of dermatologic conditions in primary care</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2017</year>  
        <month>11</month>  
        <day>08</day>  
        <volume>5</volume>  
        <issue>11</issue>  
        <fpage>e165</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2017/11/e165/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.8257</pub-id>
        <pub-id pub-id-type="medline">29117934</pub-id>
        <pub-id pub-id-type="pii">v5i11e165</pub-id>
        <pub-id pub-id-type="pmcid">PMC5700409</pub-id></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wyatt</surname>
            <given-names>KD</given-names>
          </name>
          <name name-style="western">
            <surname>Willaert</surname>
            <given-names>BN</given-names>
          </name>
          <name name-style="western">
            <surname>Pallagi</surname>
            <given-names>PJ</given-names>
          </name>
          <name name-style="western">
            <surname>Uribe</surname>
            <given-names>RA</given-names>
          </name>
          <name name-style="western">
            <surname>Yiannias</surname>
            <given-names>JA</given-names>
          </name>
          <name name-style="western">
            <surname>Hellmich</surname>
            <given-names>TR</given-names>
          </name>
        </person-group>
        <article-title>PhotoExam: adoption of an iOS-based clinical image capture application at Mayo Clinic</article-title>
        <source>Int J Dermatol</source>  
        <year>2017</year>  
        <month>05</month>  
        <day>11</day>  
        <volume>56</volume>  
        <issue>12</issue>  
        <fpage>1359</fpage>  
        <lpage>65</lpage>  
        <pub-id pub-id-type="doi">10.1111/ijd.13648</pub-id>
        <pub-id pub-id-type="medline">28497467</pub-id></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>Börve</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Dahlén Gyllencreutz</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Terstappen</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Johansson Backman</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Aldenbratt</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Danielsson</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Gillstedt</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Sandberg</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Paoli</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Smartphone teledermoscopy referrals: a novel process for improved triage of skin cancer patients</article-title>
        <source>Acta Derm Venereol</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>95</volume>  
        <issue>2</issue>  
        <fpage>186</fpage>  
        <lpage>90</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.medicaljournals.se/acta/content/?doi=10.2340/00015555-1906"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2340/00015555-1906</pub-id>
        <pub-id pub-id-type="medline">24923283</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>Paik</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Granick</surname>
            <given-names>MS</given-names>
          </name>
          <name name-style="western">
            <surname>Scott</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Plastic surgery telehealth consultation expedites Emergency Department treatment</article-title>
        <source>J Telemed Telecare</source>  
        <year>2017</year>  
        <month>02</month>  
        <volume>23</volume>  
        <issue>2</issue>  
        <fpage>321</fpage>  
        <lpage>27</lpage>  
        <pub-id pub-id-type="doi">10.1177/1357633X16639459</pub-id>
        <pub-id pub-id-type="medline">27056907</pub-id>
        <pub-id pub-id-type="pii">1357633X16639459</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>Cinaglia</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Tradigo</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Guzzi</surname>
            <given-names>PH</given-names>
          </name>
          <name name-style="western">
            <surname>Veltri</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>Design and implementation of a telecardiology system for mobile devices</article-title>
        <source>Interdiscip Sci</source>  
        <year>2015</year>  
        <month>09</month>  
        <volume>7</volume>  
        <issue>3</issue>  
        <fpage>266</fpage>  
        <lpage>74</lpage>  
        <pub-id pub-id-type="doi">10.1007/s12539-015-0267-8</pub-id>
        <pub-id pub-id-type="medline">26223546</pub-id>
        <pub-id pub-id-type="pii">10.1007/s12539-015-0267-8</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>Gagnon</surname>
            <given-names>MP</given-names>
          </name>
          <name name-style="western">
            <surname>Ngangue</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Payne-Gagnon</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Desmartis</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>m-Health adoption by healthcare professionals: a systematic review</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2016</year>  
        <month>01</month>  
        <volume>23</volume>  
        <issue>1</issue>  
        <fpage>212</fpage>  
        <lpage>20</lpage>  
        <pub-id pub-id-type="doi">10.1093/jamia/ocv052</pub-id>
        <pub-id pub-id-type="medline">26078410</pub-id>
        <pub-id pub-id-type="pii">ocv052</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>Davis</surname>
            <given-names>FD</given-names>
          </name>
        </person-group>
        <article-title>Perceived usefulness, perceived ease of use, and user acceptance of information technology</article-title>
        <source>MIS Q</source>  
        <year>1989</year>  
        <month>09</month>  
        <volume>13</volume>  
        <issue>3</issue>  
        <fpage>319</fpage>  
        <pub-id pub-id-type="doi">10.2307/249008</pub-id></nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
        <source>Iso.org</source>  
        <access-date>2018-09-17</access-date>
        <comment>Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/obp/ui/#iso:std:iso:9241:-11:ed-2:v1:en">https://www.iso.org/obp/ui/#iso:std:iso:9241:-11:ed-2:v1:en</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="72Upaov7y"/></comment> </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Maritz</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Wallis</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Van Der Merwe</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Nel</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>The aetiology of adult burns in the Western Cape, South Africa</article-title>
        <source>Burns</source>  
        <year>2012</year>  
        <month>02</month>  
        <volume>38</volume>  
        <issue>1</issue>  
        <fpage>120</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.burns.2010.12.007</pub-id>
        <pub-id pub-id-type="medline">22113101</pub-id>
        <pub-id pub-id-type="pii">S0305-4179(10)00326-8</pub-id></nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Van Niekerk</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Laubscher</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Laflamme</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Demographic and circumstantial accounts of burn mortality in Cape Town, South Africa, 2001-2004: an observational register based study</article-title>
        <source>BMC Public Health</source>  
        <year>2009</year>  
        <month>10</month>  
        <day>06</day>  
        <volume>9</volume>  
        <fpage>374</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpublichealth.biomedcentral.com/articles/10.1186/1471-2458-9-374"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/1471-2458-9-374</pub-id>
        <pub-id pub-id-type="medline">19804652</pub-id>
        <pub-id pub-id-type="pii">1471-2458-9-374</pub-id>
        <pub-id pub-id-type="pmcid">PMC2765964</pub-id></nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Stander</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Wallis</surname>
            <given-names>LA</given-names>
          </name>
        </person-group>
        <article-title>The emergency management and treatment of severe burns</article-title>
        <source>Emerg Med Int</source>  
        <year>2011</year>  
        <volume>2011</volume>  
        <fpage>161375</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.doi.org/10.1155/2011/161375"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1155/2011/161375</pub-id>
        <pub-id pub-id-type="medline">22046536</pub-id>
        <pub-id pub-id-type="pmcid">PMC3195355</pub-id></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>Jaspers</surname>
            <given-names>MW</given-names>
          </name>
          <name name-style="western">
            <surname>Steen</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>van den Bos</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Geenen</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>The think aloud method: a guide to user interface design</article-title>
        <source>Int J Med Inform</source>  
        <year>2004</year>  
        <month>11</month>  
        <volume>73</volume>  
        <issue>11-12</issue>  
        <fpage>781</fpage>  
        <lpage>95</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2004.08.003</pub-id>
        <pub-id pub-id-type="medline">15491929</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(04)00182-0</pub-id></nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Yen</surname>
            <given-names>PY</given-names>
          </name>
          <name name-style="western">
            <surname>Wantland</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Bakken</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Development of a customizable health IT usability evaluation scale</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2010</year>  
        <volume>2010</volume>  
        <fpage>917</fpage>  
        <lpage>21</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21347112"/>
        </comment>  
        <pub-id pub-id-type="medline">21347112</pub-id>
        <pub-id pub-id-type="pmcid">PMC3041285</pub-id></nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</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>
        </person-group>
        <article-title>Development of a video coding scheme for analyzing the usability and usefulness of health information systems</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2015</year>  
        <volume>218</volume>  
        <fpage>40599</fpage>  
        <pub-id pub-id-type="medline">26262529</pub-id></nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Blom</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Laflamme</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Mölsted Alvesson</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Expectations of medical specialists about image-based teleconsultation - a qualitative study on acute burns in South Africa</article-title>
        <source>PLoS One</source>  
        <year>2018</year>  
        <volume>13</volume>  
        <issue>3</issue>  
        <fpage>e0194278</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0194278"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1371/journal.pone.0194278</pub-id>
        <pub-id pub-id-type="medline">29543847</pub-id>
        <pub-id pub-id-type="pii">PONE-D-17-04911</pub-id>
        <pub-id pub-id-type="pmcid">PMC5854403</pub-id></nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rust</surname>
            <given-names>RT</given-names>
          </name>
          <name name-style="western">
            <surname>Thompson</surname>
            <given-names>DV</given-names>
          </name>
          <name name-style="western">
            <surname>Hamilton</surname>
            <given-names>RW</given-names>
          </name>
        </person-group>
        <article-title>Defeating feature fatigue</article-title>
        <source>Harv Bus Rev</source>  
        <year>2006</year>  
        <month>02</month>  
        <volume>84</volume>  
        <issue>2</issue>  
        <fpage>98</fpage>  
        <lpage>107, 165</lpage>  
        <pub-id pub-id-type="medline">16485808</pub-id></nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ehrler</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Weinhold</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Joe</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Lovis</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Blondon</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>A mobile app (BEDSide Mobility) to support nurses' tasks at the patient's bedside: usability study</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2018</year>  
        <month>03</month>  
        <day>21</day>  
        <volume>6</volume>  
        <issue>3</issue>  
        <fpage>e57</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/3/e57/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.9079</pub-id>
        <pub-id pub-id-type="medline">29563074</pub-id>
        <pub-id pub-id-type="pii">v6i3e57</pub-id>
        <pub-id pub-id-type="pmcid">PMC5885064</pub-id></nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Keil</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Beranek</surname>
            <given-names>PM</given-names>
          </name>
          <name name-style="western">
            <surname>Konsynski</surname>
            <given-names>BR</given-names>
          </name>
        </person-group>
        <article-title>Usefulness and ease of use: field study evidence regarding task considerations</article-title>
        <source>Decis Support Syst</source>  
        <year>1995</year>  
        <month>1</month>  
        <volume>13</volume>  
        <issue>1</issue>  
        <fpage>75</fpage>  
        <lpage>91</lpage>  
        <pub-id pub-id-type="doi">10.1016/0167-9236(94)E0032-M</pub-id></nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bayramoglu</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sener</surname>
            <given-names>MT</given-names>
          </name>
          <name name-style="western">
            <surname>Cakir</surname>
            <given-names>Z</given-names>
          </name>
          <name name-style="western">
            <surname>Aslan</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Emet</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Akoz</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Characteristics of patients who admitted to the emergency department because of burns due to dens liquids such as hot milk/oil</article-title>
        <source>Eurasian J Med</source>  
        <year>2016</year>  
        <month>02</month>  
        <volume>48</volume>  
        <issue>1</issue>  
        <fpage>20</fpage>  
        <lpage>3</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27026759"/>
        </comment>  
        <pub-id pub-id-type="doi">10.5152/eurasianjmed.2015.34</pub-id>
        <pub-id pub-id-type="medline">27026759</pub-id>
        <pub-id pub-id-type="pii">eajm-48-1-20</pub-id>
        <pub-id pub-id-type="pmcid">PMC4792491</pub-id></nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hysong</surname>
            <given-names>SJ</given-names>
          </name>
          <name name-style="western">
            <surname>Esquivel</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sittig</surname>
            <given-names>DF</given-names>
          </name>
          <name name-style="western">
            <surname>Paul</surname>
            <given-names>LA</given-names>
          </name>
          <name name-style="western">
            <surname>Espadas</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Towards successful coordination of electronic health record based-referrals: a qualitative analysis</article-title>
        <source>Implement Sci</source>  
        <year>2011</year>  
        <month>07</month>  
        <day>27</day>  
        <volume>6</volume>  
        <fpage>84</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-6-84"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/1748-5908-6-84</pub-id>
        <pub-id pub-id-type="medline">21794109</pub-id>
        <pub-id pub-id-type="pii">1748-5908-6-84</pub-id>
        <pub-id pub-id-type="pmcid">PMC3199858</pub-id></nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Jenkins</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Arroll</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Hawken</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Nicholson</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Referral letters: are form letters better?</article-title>
        <source>Br J Gen Pract</source>  
        <year>1997</year>  
        <month>02</month>  
        <volume>47</volume>  
        <issue>415</issue>  
        <fpage>107</fpage>  
        <lpage>8</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://bjgp.org/cgi/pmidlookup?view=long&#38;pmid=9101670"/>
        </comment>  
        <pub-id pub-id-type="medline">9101670</pub-id>
        <pub-id pub-id-type="pmcid">PMC1312891</pub-id></nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>GB</given-names>
          </name>
          <name name-style="western">
            <surname>Cohen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Taylor</surname>
            <given-names>FC</given-names>
          </name>
          <name name-style="western">
            <surname>Gabbay</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Referral of patients to an anticoagulant clinic: implications for better management</article-title>
        <source>Qual Health Care</source>  
        <year>1993</year>  
        <month>06</month>  
        <volume>2</volume>  
        <issue>2</issue>  
        <fpage>96</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://qhc.bmj.com/cgi/pmidlookup?view=long&#38;pmid=10131640"/>
        </comment>  
        <pub-id pub-id-type="medline">10131640</pub-id>
        <pub-id pub-id-type="pmcid">PMC1055092</pub-id></nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zuchowski</surname>
            <given-names>JL</given-names>
          </name>
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>DE</given-names>
          </name>
          <name name-style="western">
            <surname>Hamilton</surname>
            <given-names>AB</given-names>
          </name>
          <name name-style="western">
            <surname>Stockdale</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Meredith</surname>
            <given-names>LS</given-names>
          </name>
          <name name-style="western">
            <surname>Yano</surname>
            <given-names>EM</given-names>
          </name>
          <name name-style="western">
            <surname>Rubenstein</surname>
            <given-names>LV</given-names>
          </name>
          <name name-style="western">
            <surname>Cordasco</surname>
            <given-names>KM</given-names>
          </name>
        </person-group>
        <article-title>Challenges in referral communication between VHA primary care and specialty care</article-title>
        <source>J Gen Intern Med</source>  
        <year>2015</year>  
        <month>03</month>  
        <volume>30</volume>  
        <issue>3</issue>  
        <fpage>305</fpage>  
        <lpage>11</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25410884"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s11606-014-3100-x</pub-id>
        <pub-id pub-id-type="medline">25410884</pub-id>
        <pub-id pub-id-type="pmcid">PMC4351287</pub-id></nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Dvořák</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Pergl</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Kroha</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Rocha</surname>
            <given-names>Á</given-names>
          </name>
          <name name-style="western">
            <surname>Correia</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Adeli</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Luis Paulo</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Costanzo</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Tackling the flexibility-usability trade-off in component-based software development</article-title>
        <source>Recent Advances in Information Systems and Technologies</source>  
        <year>2017</year>  
        <publisher-loc>New York City</publisher-loc>
        <publisher-name>Springer International Publishing</publisher-name>
        <fpage>861</fpage>  
        <lpage>71</lpage> </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nikolic</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Wickramasinghe</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Claydon-Platt</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Balakrishnan</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Smart</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>The use of communication apps by medical staff in the Australian health care system: survey study on prevalence and use</article-title>
        <source>JMIR Med Inform</source>  
        <year>2018</year>  
        <month>02</month>  
        <day>09</day>  
        <volume>6</volume>  
        <issue>1</issue>  
        <fpage>e9</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://medinform.jmir.org/2018/1/e9/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/medinform.9526</pub-id>
        <pub-id pub-id-type="medline">29426813</pub-id>
        <pub-id pub-id-type="pii">v6i1e9</pub-id>
        <pub-id pub-id-type="pmcid">PMC5889814</pub-id></nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Sonderegger</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Schmutz</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Sauer</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>The influence of age in usability testing</article-title>
        <source>Appl Ergon</source>  
        <year>2016</year>  
        <month>01</month>  
        <volume>52</volume>  
        <fpage>291</fpage>  
        <lpage>300</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.apergo.2015.06.012</pub-id>
        <pub-id pub-id-type="medline">26360221</pub-id>
        <pub-id pub-id-type="pii">S0003-6870(15)30014-4</pub-id></nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Cillessen</surname>
            <given-names>FH</given-names>
          </name>
          <name name-style="western">
            <surname>de Vries Robbé</surname>
            <given-names>PF</given-names>
          </name>
          <name name-style="western">
            <surname>Biermans</surname>
            <given-names>MC</given-names>
          </name>
        </person-group>
        <article-title>A hospital-wide transition from paper to digital problem-oriented clinical notes. A descriptive history and cross-sectional survey of use, usability, and satisfaction</article-title>
        <source>Appl Clin Inform</source>  
        <year>2017</year>  
        <month>12</month>  
        <day>17</day>  
        <volume>8</volume>  
        <issue>2</issue>  
        <fpage>502</fpage>  
        <lpage>14</lpage>  
        <pub-id pub-id-type="doi">10.4338/ACI-2016-08-RA-0137</pub-id>
        <pub-id pub-id-type="medline">28512662</pub-id>
        <pub-id pub-id-type="pii">2016-08-RA-0137</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
