<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
    <article-id pub-id-type="publisher-id">v4i2e11</article-id>
    <article-id pub-id-type="pmid">28438724</article-id>
    <article-id pub-id-type="doi">10.2196/humanfactors.7293</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>Toward a More Usable Home-Based Video Telemedicine System: A Heuristic Evaluation of the Clinician User Interfaces of Home-Based Video Telemedicine Systems</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Santana-Mancilla</surname>
          <given-names>Pedro</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Alhuwail</surname>
          <given-names>Dari</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Chaudry</surname>
          <given-names>Beenish</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1" equal-contrib="yes">
        <name name-style="western">
          <surname>Agnisarman</surname>
          <given-names>Sruthy</given-names>
        </name>
        <degrees>BS, MS</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-7836-673X</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib2" equal-contrib="yes">
        <name name-style="western">
          <surname>Narasimha</surname>
          <given-names>Shraddhaa</given-names>
        </name>
        <degrees>BS, MS</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-3014-3005</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib3" corresp="yes">
      <name name-style="western">
        <surname>Chalil Madathil</surname>
        <given-names>Kapil</given-names>
      </name>
      <degrees>PhD</degrees>
      <xref rid="aff1" ref-type="aff">1</xref>
      <address>
        <institution>Department of Civil Engineering</institution>
        <institution>Clemson University</institution>
        <addr-line>116 Lowry Hall</addr-line>
        <addr-line>Clemson, SC, 29634</addr-line>
        <country>United States</country>
        <phone>1 7132946499</phone>
        <fax>1 8646560856</fax>
        <email>kmadath@clemson.edu</email>
      </address>  
      <xref rid="aff2" ref-type="aff">2</xref>
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-8938-9793</ext-link></contrib>
      <contrib contrib-type="author" id="contrib4">
        <name name-style="western">
          <surname>Welch</surname>
          <given-names>Brandon</given-names>
        </name>
        <degrees>PhD</degrees>
        <xref rid="aff3" ref-type="aff">3</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-2214-9282</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib5">
        <name name-style="western">
          <surname>Brinda</surname>
          <given-names>FNU</given-names>
        </name>
        <degrees>MS</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-0415-7067</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib6" equal-contrib="yes">
        <name name-style="western">
          <surname>Ashok</surname>
          <given-names>Aparna</given-names>
        </name>
        <degrees>MDS</degrees>
        <xref rid="aff4" ref-type="aff">4</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-4008-1293</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib7" equal-contrib="yes">
        <name name-style="western">
          <surname>McElligott</surname>
          <given-names>James</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff3" ref-type="aff">3</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-9577-9138</ext-link>
      </contrib>
    </contrib-group>
    <aff id="aff1">
    <sup>1</sup>
    <institution>Department of Civil Engineering</institution>
    <institution>Clemson University</institution>  
    <addr-line>Clemson, SC</addr-line>
    <country>United States</country></aff>
    <aff id="aff2">
    <sup>2</sup>
    <institution>Department of Industrial Engineering</institution>
    <institution>Clemson University</institution>  
    <addr-line>Clemson, SC</addr-line>
    <country>United States</country></aff>
    <aff id="aff3">
    <sup>3</sup>
    <institution>MUSC Center for Telehealth</institution>
    <institution>Department of Public Health Sciences</institution>  
    <institution>Medical University of South Carolina</institution>  
    <addr-line>Charleston, SC</addr-line>
    <country>United States</country></aff>
    <aff id="aff4">
    <sup>4</sup>
    <institution>School of Dental Medicine</institution>
    <institution>Southern Illinois University at Edwardsville</institution>  
    <addr-line>Edwardsville, IL</addr-line>
    <country>United States</country></aff>
    <author-notes>
      <corresp>Corresponding Author: Kapil Chalil Madathil 
      <email>kmadath@clemson.edu</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><season>Apr-Jun</season><year>2017</year></pub-date>
    <pub-date pub-type="epub">
      <day>24</day>
      <month>04</month>
      <year>2017</year>
    </pub-date>
    <volume>4</volume>
    <issue>2</issue>
    <elocation-id>e11</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>10</day>
        <month>1</month>
        <year>2017</year>
      </date>
      <date date-type="rev-request">
        <day>3</day>
        <month>2</month>
        <year>2017</year>
      </date>
      <date date-type="rev-recd">
        <day>22</day>
        <month>2</month>
        <year>2017</year>
      </date>
      <date date-type="accepted">
        <day>23</day>
        <month>2</month>
        <year>2017</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>©Sruthy Agnisarman, Shraddhaa Narasimha, Kapil Chalil Madathil, Brandon Welch, FNU Brinda, Aparna Ashok, James McElligott. Originally published in JMIR Human Factors (http://humanfactors.jmir.org), 24.04.2017.</copyright-statement>
    <copyright-year>2017</copyright-year>
    <license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/2.0/">
      <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on http://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://humanfactors.jmir.org/2017/2/e11/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>Telemedicine is the use of technology to provide and support health care when distance separates the clinical service and the patient. Home-based telemedicine systems involve the use of such technology for medical support and care connecting the patient from the comfort of their homes with the clinician. In order for such a system to be used extensively, it is necessary to understand not only the issues faced by the patients in using them but also the clinician.</p>
      </sec>
      <sec sec-type="objectives">
        <title>Objectives</title>
        <p>The aim of this study was to conduct a heuristic evaluation of 4 telemedicine software platforms—Doxy.me, Polycom, Vidyo, and VSee—to assess possible problems and limitations that could affect the usability of the system from the clinician’s perspective.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>It was found that 5 experts individually evaluated all four systems using Nielsen’s list of heuristics, classifying the issues based on a severity rating scale.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>A total of 46 unique problems were identified by the experts. The heuristics most frequently violated were <italic>visibility of system status</italic> and <italic>Error prevention</italic> amounting to 24% (11/46 issues) each. <italic>Esthetic and minimalist design</italic> was second contributing to 13% (6/46 issues) of the total errors.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>Heuristic evaluation coupled with a severity rating scale was found to be an effective method for identifying problems with the systems. Prioritization of these problems based on the rating provides a good starting point for resolving the issues affecting these platforms. There is a need for better transparency and a more streamlined approach for how physicians use telemedicine systems. Visibility of the system status and speaking the users’ language are keys for achieving this.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>telemedicine</kwd>
      <kwd>heuristics, Internet, user-computer interface, cognition</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Health Care System</title>
        <p>The health care system in the United States is currently undergoing extensive changes. Possible causes for such challenges faced by its delivery system are increased demand for health care due to an increased number and changing lifestyle leading to an increase in chronic diseases, the demand for increased accessibility of care outside hospitals, moving health services into the patient’s own homes, the need for increased efficiency, individualization and equity of quality-oriented health care with limited financial resources, the difficulties of recruiting and retaining personnel in health care services in general, and in home and elderly care in particular [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. Telehealth, the use of electronic information and telecommunication technologies to support long-distance clinical health care, patient and professional health-related education, public health and health administration [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>], has the potential to address these issues. One subsection, telemedicine, the use of technology to provide and support health care when distance separates the clinical service and the patient, appears to be particularly attractive [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
        <p>Although playing an important role in addressing the health issues of patients living in underserved and rural areas, telemedicine is now attracting attention beyond these limited regions. It offers mechanisms for centralizing specialists, reducing costs for specialty care, and supporting primary care clinician needs in the urban and suburban areas these typically serve [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. The possible benefits of using these systems have resulted in an increased interest in telemedicine. For example, they help patients with chronic illness and those with limited mobility to connect with a health care facility from the comfort of their homes [<xref ref-type="bibr" rid="ref1">1</xref>], and it is important because it reduces the stress for patients who otherwise would have to travel long distances for their appointments [<xref ref-type="bibr" rid="ref10">10</xref>]. Currently, this remote care is extensively used for clinical visits that do not require physical presence such as behavioral health [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], counseling [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>], follow-up [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref16">16</xref>], and patient education [<xref ref-type="bibr" rid="ref17">17</xref>], with studies finding telemedicine an appealing solution for the real-time remote monitoring of patients. It has also shown promise for improving patient knowledge of health care, thus helping them better manage their diseases or illnesses. With the expanding technical capabilities and the decreasing costs of telemedicine software solutions, home-based telemedicine is becoming more widely used, evidenced by a recent workshop conducted by the National Academies that discussed the potential of scaling such delivery of care for a growing number of patients [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref18">18</xref>].</p>
      </sec>
      <sec>
        <title>Telemedicine System</title>
        <p>Unlike face-to-face encounters, in which clinicians and patients are both located in the same setting, telemedicine participants usually use the teleconferencing systems at their respective locations. Thus, for a telemedicine system to become widely accepted, it should not only be functional but also user-friendly [<xref ref-type="bibr" rid="ref19">19</xref>-<xref ref-type="bibr" rid="ref23">23</xref>]. The Institute of Medicine (IOM) recently emphasized the role of usability in telemedicine systems, given its potential to replace regular clinical visits which are both time-consuming and resource-demanding [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref23">23</xref>].</p>
        <p>However, limited research has been conducted evaluating the perceived usefulness and usability of such tools from a home-based video telemedicine system perspective [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. The evaluation of a user interface can be carried out by 4 ways; <italic>formally</italic> using analytical tools, <italic>automatically</italic> using computer technology, <italic>empirically</italic>, that is, testing with users, and <italic>heuristically</italic> [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>]. Heuristic evaluation is the process of usability testing wherein evaluators are provided with an interface and asked to comment on it based on a set of heuristics [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. The efficiency of this system of evaluation allows for an iterative design process of user interfaces [<xref ref-type="bibr" rid="ref18">18</xref>]. Studies have found that this type of evaluation can reveal both major and minor usability issues, including problems that lead to errors and user dissatisfaction content [<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. Furthermore, it has been extensively used to ascertain usability issues in the medical field ranging from websites to medical devices [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>] to health information technology applications [<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref40">40</xref>]. In light of these advantages of a heuristic evaluation, this study aimed to understand the issues of the clinician’s interfaces of 4 telemedicine platforms. The issues uncovered through this heuristic evaluation could serve as a basis to improve the clinician’s interface in telemedicine platforms.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Telemedicine Systems</title>
        <p>The criteria for a telemedicine system to be included in this heuristic evaluation were as follows: (1) the system is primarily used to deliver video-based telemedicine at home; (2) the system does not require specialized or proprietary equipment for home use; (3) the system runs on an Internet-connected computer with audio and video capabilities; and (4) the system is Health Insurance Portability and Accountability Act (HIPAA) compliant, which aims at protecting the health rights and privacy of patiens [<xref ref-type="bibr" rid="ref41">41</xref>]. Initially, the telemedicine systems used by the medical staff at the Medical University of South Carolina (MUSC) Center for Telehealth and South Carolina (SC) Telehealth Alliance were reviewed. Subsequently, 8 software applications, Adobe Connect, Cisco WebEx, Cisco Jabber, Doxy.me, Polycom, Skype, Vidyo, and VSee, were identified as potential candidates based on this preliminary review. Next, a detailed analysis of the features of each and its primary use were conducted. A total of 5 key stakeholders including the physicians and directors associated with MUSC Center for Telehealth and SC Telehealth Alliance were consulted. It was understood that Adobe Connect, Skype, Cisco WebEx, and Cisco Jabber could be used to deliver video-based telemedicine, but they were not currently used extensively for doing so. On the basis of this feedback, the telemedicine tools selected for this research were (1) Doxy.me, (2) Vidyo, (3) VSee, and (4) Polycom.</p>
        <sec>
          <title>Doxy.me</title>
          <p>Doxy.me is a free Web-based system (as opposed to downloaded desktop application) specifically designed for telemedicine purposes. Clinicians create an account and a personalized waiting room where they communicate with their patients, either copying and emailing or directly emailing the address of their waiting room. By clicking on this link, patient is directed to the clinician’s waiting room. There is a self-view box at the top right and a chat box at the bottom right of the screen. Volume and video control buttons are located below the patient’s video. In addition to these features, the clinician can edit the waiting room and change the account settings. <xref ref-type="fig" rid="figure1">Figure 1</xref> below shows the Doxy.me log-in screen, waiting room, and clinician’s view.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Doxy.me log-in screen, waiting room, and clinician’s view.</p>
            </caption>
            <graphic xlink:href="humanfactors_v4i2e11_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Vidyo</title>
          <p>Vidyo is one of the leading telemedicine videoconferencing desktop-based application solutions. After creating an account, the clinician receives an email with log-in credentials and a Vidyo portal. The Vidyo desktop application is downloaded by clicking the portal. The clinician sends a Vidyo meeting invitation after logging into this application. He or she can change the video quality and other settings by clicking on the configuration button. In addition, this task bar includes the volume and video control buttons, group chat option, self-view option, screen layout option, and end call option. <xref ref-type="fig" rid="figure2">Figure 2</xref> shows the Vidyo desktop application from the clinician’s perspective.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Vidyo log-in screen, contact list, and clinician’s view.</p>
            </caption>
            <graphic xlink:href="humanfactors_v4i2e11_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>VSee</title>
          <p>VSee is a telemedicine system which requires the clinician to create an account and install a desktop application. After logging into the account, the clinician invites patients by entering their email ids or copying and emailing them an invitation link. This system includes an option for text chatting with the patient as well as separate windows for self-view, clinician’s video, chat box, and contacts, with the microphone and camera settings being found on the self-view window. <xref ref-type="fig" rid="figure3">Figure 3</xref> shows the VSee log-in screen, application screen, and clinician’s view.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>VSee log-in screen, application screen, and clinician’s view.</p>
            </caption>
            <graphic xlink:href="humanfactors_v4i2e11_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Polycom</title>
          <p>Polycom, a licensed Web-based application that can be purchased from the Polycom website, provides telemedicine and video services for remote conferencing and collaboration. Although this company provides a hardware-based telemedicine solution, this study used a lightweight product for home-based care. The clinician receives an email with log-in credentials and a link for accessing the account. After logging into the account, the clinician selects the devices or system, which includes an option for adding participants and managing meetings. The clinician invites patients by emailing them the address of his or her chat room; after clicking this link, the patient is then directed to the meeting. There is a self-view option on the left side of the screen, the participant list on the right, and the patient’s video in the middle. The control buttons are located below the patient’s video. <xref ref-type="fig" rid="figure4">Figure 4</xref> shows the Polycom log-in screen, welcome room, and clinician’s view.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Polycom log-in screen, welcome screen, and clinician’s view.</p>
            </caption>
            <graphic xlink:href="humanfactors_v4i2e11_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Study Personnel</title>
        <p>The investigation reported here was based on the experts’ heuristic evaluations and the severity of the problems based on a severity rating scale. A heuristic evaluation is a discounted usability method in which the evaluation of an interface is done based on established usability principles. Five human factors engineers—three PhD students, one assistant professor, and one master’s degree student, all with prior training in conducting heuristic evaluations—were recruited to serve as the subject matter experts for this study. All received verbal information about the purpose and the goal of the study, and a detailed written task flow to guide the evaluation of the 4 telemedicine platforms using a modified heuristic evaluation procedure. They were compensated with a US $20 Amazon gift card for their time.</p>
      </sec>
      <sec>
        <title>Study Design and Procedure</title>
        <p>The method of evaluation used in the study was a heuristic evaluation, a discounted usability evaluation method, combined with a severity rating scale [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Specifically, Nielsen’s heuristics were used because of their widespread use and acceptability [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref43">43</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]. The heuristics, which are listed in <xref ref-type="table" rid="table1">Table 1</xref>, were used to highlight possible usability issues.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Usability heuristics used for evaluating the telemedicine interfaces (adapted from Nielsen’s heuristics [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]).</p>
          </caption>
          <table width="733" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="172"/>
            <col width="532"/>
            <thead>
              <tr valign="top">
                <td>Heuristic</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Visibility of system status</td>
                <td>The system should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.</td>
              </tr>
              <tr valign="top">
                <td>Match between system and the real world</td>
                <td>The system should speak the users’ language, using familiar words, phrases, and concepts rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.</td>
              </tr>
              <tr valign="top">
                <td>User control and freedom</td>
                <td>Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialog. Support undo and redo.</td>
              </tr>
              <tr valign="top">
                <td>Consistency and standards</td>
                <td>Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.</td>
              </tr>
              <tr valign="top">
                <td>Error prevention</td>
                <td>Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.</td>
              </tr>
              <tr valign="top">
                <td>Recognition rather than recall</td>
                <td>Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialog to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.</td>
              </tr>
              <tr valign="top">
                <td>Flexibility and efficiency of use</td>
                <td>Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.</td>
              </tr>
              <tr valign="top">
                <td>Esthetic and minimalist design</td>
                <td>Dialogs should not contain information that is irrelevant or rarely needed. Every extra unit of information in a dialog competes with the relevant units of information and diminishes their relative visibility.</td>
              </tr>
              <tr valign="top">
                <td>Help users recognize, diagnose, and recover from errors</td>
                <td>Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.</td>
              </tr>
              <tr valign="top">
                <td>Help and documentation</td>
                <td>Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>A heuristic evaluation, typically conducted with 5 experts, detects up to 80% of the problems [<xref ref-type="bibr" rid="ref18">18</xref>]. For this study, the experts individually conducted the assessment in a closed lab setting to avoid bystander bias. A 5-point severity scale was applied to each of the usability issues to indicate the level of concern [<xref ref-type="bibr" rid="ref27">27</xref>]. The scale ranged from issues which may not impact the usability of the system to issues that could potentially lead to its failure. The 5-point scale is as follows [<xref ref-type="bibr" rid="ref46">46</xref>]:</p>
        <p>0—May not be a problem: other observers do not agree that this is a usability problem</p>
        <p>1—Cosmetic problem only: it need not be fixed unless extra time is available</p>
        <p>2—Minor usability problem: fixing it should be given low priority</p>
        <p>3—Major usability problem: it is important to fix it, should be given high priority</p>
        <p>4—Usability catastrophe: imperative that it is fixed before product can be released</p>
        <p>Understanding the source of errors in a task begins with an in-depth understanding of the task flow [<xref ref-type="bibr" rid="ref33">33</xref>]. This study, thus, began with a detailed task analysis for each of the 4 telemedicine systems to help understand the feedback they provide and the potential problems the user could face. This task analysis also included determining the knowledge the user must have in order to perform the task successfully. Before actual evaluation, the researcher discussed the detailed task analysis, heuristics, and severity ranking scale with the experts. As the experts were from the field of human factors and familiar with heuristic evaluation studies, only context-specific instructions were provided to evaluate the telemedicine platforms. A separate sheet containing the list of the heuristics and the severity rating chart was also given to the experts for their reference. The experts then evaluated the systems from the clinician’s perspective with the help of a hypothetical patient with whom no communication was carried out. After which, they listed the heuristic violations individually. The tasks to be completed by the evaluators were as follows:</p>
        <p>Initiation: Create an account, log into the portal or desktop application, send an email invitation for the telemedicine session, call the patient.</p>
        <p>Consultation: Toggle microphone and video, enter full screen mode, enter data into a chat box (where applicable), and end video call.</p>
        <p>On completing individual evaluations, experts discussed their findings with others in a postevaluation debriefing session. In the case of extreme inconsistencies, the evaluators discussed and came to a consensus about the appropriate rating. Individual lists were subsequently compiled for data analysis. <xref ref-type="fig" rid="figure5">Figure 5</xref> outlines the experimental procedure followed in this study which lasted approximately 1 h.</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Experimental procedure followed.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>For the evaluation, each expert recorded the heuristic violations for the respective tasks, including grading the severity of the issues. The individual ratings from the evaluators were averaged to obtain a single value of the severity. These data were then compiled to understand which heuristics were most violated and the severity was analyzed to prioritize the problems. The number of heuristics violated was graphed for the telemedicine session initiation and consultation.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Heuristic Violations</title>
        <p>The heuristic evaluations of the experts for the clinician’s interface revealed a total of 46 unique issues: 11 for Doxy.me, 10 for Vidyo, 12 for VSee, and 13 for Polycom. Of these, 22% (10/46) concerns were recognized by all the experts. <xref ref-type="table" rid="table2">Tables 2</xref>-<xref ref-type="table" rid="table4">4</xref> list the important usability issues and the heuristics they violated for initiating, conducting, and concluding a telemedicine session, respectively. <xref ref-type="fig" rid="figure6">Figures 6</xref>-<xref ref-type="fig" rid="figure8">8</xref> are graphical representations of heuristic violations for initiating, conducting, and concluding a telemedicine session, respectively. As these figures show, 60.9% (28 issues) of the issues was identified in the initiation phase, 33% (15/46 issues) in the telemedicine session phase, and 7% (3/46 issues) in the conclusion phase. Sharing or setting up microphone and camera was one of the specific issues observed in the initiation phase (<xref ref-type="fig" rid="figure9">Figure 9</xref>). Using default email client (Microsoft Outlook) to invite patients was one of the issues identified during the telemedicine session. During conclusion, difficulty to find the log-out button was pointed out as an important issue (<xref ref-type="fig" rid="figure10">Figure 10</xref>).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Heuristic violations identified in the telemedicine initiation session.</p>
          </caption>
          <table width="733" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="124"/>
            <col width="185"/>
            <col width="170"/>
            <col width="133"/>
            <col width="50"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Problem description</td>
                <td>Solution recommendation</td>
                <td>Heuristic violated</td>
                <td>Severity rating</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5"><bold>Doxy.me</bold></td>
              </tr>
              <tr valign="top">
                <td>Entering room name (Doxy.me)</td>
                <td>User may not comprehend the meaning of “room name” in a Web-based system setting</td>
                <td>Provide explanation or rename as “clinician’s name”</td>
                <td>Match between system and the real world</td>
                <td>2.5</td>
              </tr>
              <tr valign="top">
                <td>Select check boxes</td>
                <td>The check boxes are not noticeable</td>
                <td>Make the check box more noticeable</td>
                <td>Error prevention</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Sharing camera and microphone</td>
                <td>Instruction says “allow” camera and microphone, but popup says “share”</td>
                <td>Keep the instruction consistent with the website features</td>
                <td>Consistency and standards</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>An email verification is sent to the user</td>
                <td>Email is very lengthy and has too many links</td>
                <td>Email could consist of a body with just the essential links</td>
                <td>Esthetic and minimalistic design</td>
                <td>3.5</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Vidyo</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on the link in the welcome email sent by the company</td>
                <td>Clicking on the link does not lead to log-in page. Instead, it downloads the application</td>
                <td>Reword the link description or the link must lead to the log-in page</td>
                <td>Consistency and standards</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>Click on email icon on top right corner of the application</td>
                <td>Not all users may recognize the icon of an envelope as symbolizing email</td>
                <td>There could be a label below the icon</td>
                <td>Error prevention</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Click log-in</td>
                <td>Log-in button remains inactive if the portal is entered after entering username and password</td>
                <td>Application should show an error message</td>
                <td>Help users recognize, diagnose, and recover from errors</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>VSee</bold></td>
              </tr>
              <tr valign="top">
                <td>Downloading .exe file</td>
                <td>Does not prompt to confirm if download should be initiated. <break/>Download starts automatically</td>
                <td>Notify user before downloading. <break/>Provide a prompt asking the users if they want to download the application at that moment or later</td>
                <td>Visibility of system status</td>
                <td>3.5</td>
              </tr>
              <tr valign="top">
                <td>Enter email address in “Enter your email” tab</td>
                <td>Email id is mandatory and cannot proceed to free video sign up option</td>
                <td>Email entry could be on top with the sign-up for free tab below it instead of beside it</td>
                <td>Error prevention</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Polycom</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on the your account URL in the welcome email</td>
                <td>Email contains a link for online account and another link for downloading. User might get confused and download application</td>
                <td>Provide sufficient information about each link</td>
                <td>Error prevention. <break/>Help and documentation</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Selecting check in devices and software</td>
                <td>There is multiple check in options which may confuse users</td>
                <td>Provide sufficient information about each device and software</td>
                <td>Error prevention. <break/>Help and documentation</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Set camera, microphone, and speaker</td>
                <td>There is no option to go back and redo these actions if they are missed</td>
                <td>Provide an option to do these checks when necessary</td>
                <td>Help users recognize, diagnose, and recover from errors</td>
                <td>2</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Heuristic violations identified during the telemedicine session.</p>
          </caption>
          <table width="733" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="118"/>
            <col width="189"/>
            <col width="191"/>
            <col width="103"/>
            <col width="61"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Problem description</td>
                <td>Solution recommendation</td>
                <td>Heuristic violated</td>
                <td>Severity rating</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5"><bold>Doxy.me</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on email tab on the right side of the link</td>
                <td>Not enough information provided about copy and email tabs. Directly going to default mail client</td>
                <td>Popup boxes explaining meaning or function. Users need to choose the email client</td>
                <td>User control and freedom</td>
                <td>3.3</td>
              </tr>
              <tr valign="top">
                <td>Enter data in chat box provided at the bottom right corner of the screen</td>
                <td>The notification for an incoming message is not salient. Only the chat box symbol turns red</td>
                <td>Make the chat box header turn another color</td>
                <td>Visibility of system status</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Vidyo</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on email icon on top right corner of the application</td>
                <td>Clicking on the icon directly leads to default mail client</td>
                <td>Application needs to allow user to choose preferred email client</td>
                <td>User control and freedom</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Click on your name</td>
                <td>Room owner’s name is shown under “my contacts.” Tab or option to the chat room is not obvious</td>
                <td>Popup with “connect your room” button needs to pop up when the user hovers the mouse over the name</td>
                <td>Visibility of system status</td>
                <td>3.3</td>
              </tr>
              <tr valign="top">
                <td>Patient comes online</td>
                <td>No popup when the patient comes online</td>
                <td>Popup and audio notification to indicate that the patient is online</td>
                <td>Visibility of system status</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>VSee</bold></td>
              </tr>
              <tr valign="top">
                <td>Inviting patient</td>
                <td>Direct email invitation and copy option are next to each other. This may confuse the user about whether both actions must be completed or only one</td>
                <td>A simple “or” in between the two tabs</td>
                <td>Esthetic and minimalist design</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Disabling video and audio</td>
                <td>Video and audio toggling icons are not salient</td>
                <td>Icon could be presented in a brighter color</td>
                <td>Recognition rather than recall</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Enlarging the screen</td>
                <td>Application does not have a full screen button. User has to drag to enlarge the screen</td>
                <td>Provide a full screen button</td>
                <td>Consistency and standards</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Polycom</bold></td>
              </tr>
              <tr valign="top">
                <td>Compose email in default email client</td>
                <td>The invitation to the patient has to be sent from the default email client</td>
                <td>Application must provide the option to the user regarding preferred email client</td>
                <td>User control and freedom</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Compose invitation email to patient</td>
                <td>Application always redirects to default mailer</td>
                <td>An option to enter patient’s email id could be provided with an example invitation email</td>
                <td>User control and freedom</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Compose email in default email client</td>
                <td>Directly goes to default mail client</td>
                <td>Allow user to choose preferred email client</td>
                <td>User control and freedom</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Enter full screen by clicking on full screen icon at the bottom of the page</td>
                <td>System says “my rpcloud.vc” is full screen when the view is changed to full screen mode</td>
                <td>Use terms which user can easily understand</td>
                <td>Match between system and the real world</td>
                <td>1</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The heuristics most frequently seen violated were <italic>visibility of system status</italic> and <italic>error prevention,</italic> each with 11 violations (24%, 11/46), with <italic>esthetic and minimalist design</italic> being second with 6 out of 46 violations (13%, 6/46). Violations were not observed for the heuristics <italic>user control and freedom</italic> and <italic>flexibility and efficiency of use</italic>. It was found that (1) 4 out of 46 (9%, 4/46) violations were recorded for each of <italic>consistency and standards, recognition rather than recall, help users recognize, diagnose, and recover from errors</italic> and <italic>help and documentation</italic> heuristics, and (2) 2 out of 46 (4%, 2/46) violations were observed for <italic>match between system and real world</italic> heuristic. Specific issues related to <italic>visibility of system status</italic> included lack of feedback while downloading setup (.exe), lack of saliency of notifications on receiving a message or when a patient enters a Web-based waiting room, and the absence of salient call end and log-out icons. Inconspicuous check boxes, inadequate labeling of icons, and failure to exit full screen on completion of a session were identified under <italic>error prevention</italic>.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Heuristic violations identified while concluding the telemedicine session.</p>
          </caption>
          <table width="733" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="154"/>
            <col width="137"/>
            <col width="214"/>
            <col width="91"/>
            <col width="66"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Problem description</td>
                <td>Solution recommendation</td>
                <td>Heuristic violated</td>
                <td>Severity rating</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5"><bold>Doxy.me</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on red phone icon at the bottom of the page to end session</td>
                <td>Remains in full screen even after ending the call</td>
                <td>A dialog box saying press escape or automatically escape from full screen</td>
                <td>Error prevention</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Vidyo</bold></td>
              </tr>
              <tr valign="top">
                <td>Log-out of the application</td>
                <td>No obvious log-out button</td>
                <td>Provide conspicuous log-out button</td>
                <td>Visibility of system status</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>VSee</bold></td>
              </tr>
              <tr valign="top">
                <td>Click on log-out</td>
                <td>Log-out button is not easily seen</td>
                <td>Provide conspicuous log-out button</td>
                <td>Visibility of system status</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td colspan="5"><bold>Polycom</bold></td>
              </tr>
              <tr valign="top">
                <td colspan="5">No issues were identified</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure6" position="float">
          <label>Figure 6</label>
          <caption>
            <p>Heuristics violated during the telemedicine initiation session.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure7" position="float">
          <label>Figure 7</label>
          <caption>
            <p>Heuristics violated during the telemedicine consultation.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure8" position="float">
          <label>Figure 8</label>
          <caption>
            <p>Heuristics violated during the telemedicine session conclusion.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure9" position="float">
          <label>Figure 9</label>
          <caption>
            <p>Microphone and camera sharing option.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig9.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure10" position="float">
          <label>Figure 10</label>
          <caption>
            <p>Absence of log-out option.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig10.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Issues Requiring Immediate Attention</title>
        <p>The experts rated two issues as requiring immediate action. The multiple check-in options available in the welcome screen of Polycom was one, with the experts finding that the availability of multiple options confused the user, and that the welcome screen did not contain sufficient information to choose the appropriate device (<xref ref-type="fig" rid="figure11">Figure 11</xref>). The second problem highlighted by the experts was the use of a default email client to email invitations to the patients. Three (Doxy.me, Vidyo, and Polycom) of the four conditions redirect the user to the default email client to send email invitations to the patients. It may be more effective to give the user the choice of using the email client of his or her choice.</p>
        <p>During the debriefing, experts discussed their most and least favorite aspects of each of the platforms. Experts indicated that they preferred interfaces that were not cluttered with too many options, language that they could relate to that in the real world, and systems that provided adequate and timely feedback for their actions. The least enjoyable aspects were welcome emails from the telemedicine platforms with multiple links, the use of a default email client to invite patients, and the failure of many options to respond the way expected.</p>
        <fig id="figure11" position="float">
          <label>Figure 11</label>
          <caption>
            <p>Multiple log-in options in Polycom.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig11.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The heuristic evaluation was conducted using a structured table containing the task flow and a column for experts to input the problems they found for each task, the respective heuristic violated, the severity of the violation, and possible solutions. Several issues were identified during the course of this evaluation. Visibility, error prevention, and minimalistic design issues were frequently violated. The effect of such issues on the ability of a user to process information can be explained using the information processing model [<xref ref-type="bibr" rid="ref47">47</xref>]. A detailed description of the different aspects of the information processing model that are affected due to these issues would result in developing better solutions.</p>
        <p>The information processing model [<xref ref-type="bibr" rid="ref47">47</xref>] can be used to understand the impact of these issues on the user’s ability to understand and make decisions (<xref ref-type="fig" rid="figure12">Figure 12</xref>). This model illustrates the procedure of the human cognition process. The sensory register includes our sense organs that help a person take cues from our surroundings, which then leads to understanding or perceiving these cues. The working memory refers to the understanding and retention of information only for the span of completing a task. However, the long-term memory involves the retention of information for longer period of time such as a few weeks, months, or years. Using the information in the working memory and the long-term memory, the process of thinking and decision-making occurs to make a decision about the cues obtained from the environment. Once thoughts about the cues have been formed, an appropriate response to the cue is developed and based on this, an action is executed in response to the cue obtained. The execution of the response is again taken in by the sensory register and stored in the long-term memory for future situations. Throughout this process, there is also a constant requirement of attentional resources which help the user to focus on the necessary information and eliminate the rest.</p>
        <p>On the basis of the issues specified, the lack of feedback would have a direct effect on the perception of the process. As a result, the user would have difficulty in deciding the subsequent process to be carried out in the procedure. It was also indicated that the popup for the chat box was not salient. This would directly affect the sensory register as the popup would not be visible and hence the user would fail to understand (perception) that a message has been received. The icon size and design would again affect sensory register and perception. The content of the email invitation, which was reported to require immediate attention, will prove to be an important issue affecting the working memory. The working memory, responsible for understanding and retaining information until the completion of a task, would be affected due to the large amount of information or the lack of information in the email invitation. Another problem reported as requiring immediate attention was the use of default email client to send email invitations to patients. This could potentially require the retrieval of passwords to log into the system which affects the long-term memory.</p>
        <p>Although of lesser importance, there exist some other issues which must be studied with respect to their impact on a user’s decision-making. One such issue is the need to enter large amount of data for registration. This could affect the working memory limits of a person as they would be required to read and retain multiple data to enter. In three of the four platforms analyzed—Doxy.me, Polycom, and Vidyo—it was seen that the clinician was required to send an email invitation for every meeting. This would add to the working memory limits to process immediately available information and the long-term memory to remember patient name and email address to send the emails. The popups used to share the microphone and camera was indicated to be inconspicuous resulting in additional load on the sensory register due to lack of visibility.</p>
        <p>On the basis of the understanding of the different areas of the information processing model affected by the issues and the issues highlighted by the experts, certain design recommendations were developed for telemedicine systems. Some of the key findings for improving the interaction of physician with the interface to enhance the usability of telemedicine platforms are given in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>.</p>
        <boxed-text id="box1" position="float">
          <title>Key findings for improving the physician-interface interaction.</title>
          <p>Telemedicine initiation</p>
          <list list-type="bullet">
            <list-item>
              <p>Provide browser-based applications rather than desktop applications. VSee and Vidyo require their respective applications to be installed on the user’s device. A browser-based application avoids the installation process</p>
            </list-item>
            <list-item>
              <p>Highlight required field in the registration process and provide clear error message when the users fail to fill it</p>
            </list-item>
            <list-item>
              <p>Ask for only limited information for creating an account and provide an option to update user profile later</p>
            </list-item>
            <list-item>
              <p>Send an easy-to-comprehend and simple welcome email to the users upon account creation. The link which connects to the telemedicine platform needs to be highlighted as a hyperlink or a button</p>
            </list-item>
            <list-item>
              <p>Include an introductory tutorial to help users understand the different options the platform offers. Only VSee provides a tutorial tour upon logging into the application for the first time. Most of the tutorial tours do not appear as soon as the users log into the platform for the first time. They need to find the option (hidden in most cases) to watch the tour</p>
            </list-item>
            <list-item>
              <p>Give users the freedom to choose their email client without connecting it to the system’s default. Vidyo directly links to the default email client. If the clinician does not have an account with it, he/ or she cannot send an invitation. Polycom and Doxy.me allow users to choose among a number of email clients. Doxy.me and VSee allow users to log in to their email externally and send an invitation to a patient by copying and pasting the URL</p>
            </list-item>
            <list-item>
              <p>Have an option to save added contacts so that the user can contact patients again without having to go through the process of inviting them. Currently, only 1 of the 4 telemedicine platforms, VSee, has this feature</p>
            </list-item>
          </list>
          <p>Telemedicine consultation</p>
          <list list-type="bullet">
            <list-item>
              <p>Provide options for users to check their microphone and speaker connectivity before every conversation. Polycom has a foolproof system that allows users to join the conversation only if the connections are working. VSee allows the user to set up audio and video during the first log-in attempt. For the other two platforms, the clinician does not realize issues with the connectivity until he begins the conversation. Doxy.me instructs the user to click “allow” to share devices. However, the popup that appears does not have an allow button</p>
            </list-item>
            <list-item>
              <p>Provide adequate and clear feedback when major tasks like adding a patient, accepting a patient, and ending call are performed. When patients accept the invitation on Vidyo, it gives auditory notification; however, there is no popup notification of their status. For Polycom, only the number 1 appears on the side of screen; however, that number does not signify anything to the clinician. Doxy.me sounds a chime, and the patient’s name appear on the side; however, it is hard to notice because it usually blends into the page</p>
            </list-item>
            <list-item>
              <p>Provide conspicuous icons with popup feedback. VSee and Vidyo do not have salient log-out buttons, making the log-out process difficult</p>
            </list-item>
            <list-item>
              <p>Make the interface simple. Most frequently used icons can be made static, labeled, and grouped together. Cluttered interface with multiple windows and scattered icons may confuse users</p>
            </list-item>
          </list>
        </boxed-text>
        <p>or Apart from providing recommendations for improvement based on the information processing model, this study also demonstrates the practicality and ease of applying heuristic evaluation in usability studies. The entire process of conducting the study and analyzing the results took a week’s time and did not involve the use of any software applications. The efficiency of this method makes it well-suited for use during the early development stages [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <fig id="figure12" position="float">
          <label>Figure 12</label>
          <caption>
            <p>Information processing model.</p>
          </caption>
          <graphic xlink:href="humanfactors_v4i2e11_fig12.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study is not without its limitations. In this study, we evaluated the telemedicine systems on a Windows 7 computer with Mozilla Firefox browser only. These systems need to be tested on multiple operating systems and Web browsers. Also, the evaluators for this study were not medically trained professionals. Future studies have to be conducted with actual clinicians to find usability issues from their perspective. Furthermore, as indicated by Nielsen and Molich [<xref ref-type="bibr" rid="ref27">27</xref>], this heuristic evaluation like all others, only helps to identify the usability issues without providing solutions to address them.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Multiple studies have been carried out explaining the effectiveness of telemedicine in providing medical care with little research focusing on the ease and usability of these systems [<xref ref-type="bibr" rid="ref24">24</xref>]. In this study, we used a heuristic evaluation and severity rating method to assess the usability of 4 telemedicine software platforms with a focus on understanding the interface issues faced by the clinician. Furthermore, the information processing model was used as the baseline to explain the impact of these issues on the user’s capability in making decisions. The heuristic evaluation and severity rating method was found to be effective in uncovering issues in the interface as 46 unique issues were uncovered across 4 different platforms. Prominent issues among these, whose impact was explained using the information processing model, is an indication of the need for further human factors concept-based studies of the interfaces of telemedicine systems.</p>
        <p>With a focus on the clinician’s interface design, this heuristic evaluation was found to be an effective method for uncovering violations. This heuristic evaluation identified only potential usability problems in an existing interface; usability studies involving physicians could further indicate aspects of the system that work well and identify the most appropriate functionalities. However, with limited resources available, heuristic evaluation is a practical, affordable, and efficient method for revealing usability problems. Experts liked systems that had a straightforward and simple interface and that did not require installation. In addition, they preferred systems that sent simple welcome emails. From a telemedicine point of view, this is important as clinicians and technicians do not have the time to spend navigating and comprehending complex platforms.</p>
        <p>Heuristic evaluation is a discounted usability evaluation method with limited generalizability. Future studies need to focus on detailed usability evaluation with actual clinicians and patients. Conducting retrospective interviews with the users help the designers understand their needs and in turn design or modify the system appropriately.</p>
      </sec>
    </sec>
  </body>
  <back>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">IOM</term>
          <def>
            <p>Institute of Medicine</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">MUSC</term>
          <def>
            <p>Medical University of South Carolina</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">SC</term>
          <def>
            <p>South Carolina</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <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>Koch</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Home telehealth--current state and future trends</article-title>
        <source>Int J Med Inform</source>  
        <year>2006</year>  
        <month>08</month>  
        <volume>75</volume>  
        <issue>8</issue>  
        <fpage>565</fpage>  
        <lpage>76</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2005.09.002</pub-id>
        <pub-id pub-id-type="medline">16298545</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(05)00188-7</pub-id></nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Services</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Medicine</surname>
            <given-names>IO</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Lustig</surname>
            <given-names>TA</given-names>
          </name>
        </person-group>
        <source>The Role of Telehealth in an Evolving Health Care Environment: Workshop Summary</source>  
        <year>2012</year>  
        <publisher-loc>Washington, DC</publisher-loc>
        <publisher-name>National Academies Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
        <collab>American Telemedicine Association</collab> </person-group>
        <comment>What is telemedicine 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href=""/>
        <ext-link ext-link-type="webcite" xlink:href="6p13EgWj5"/></comment> </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>Perednia</surname>
            <given-names>DA</given-names>
          </name>
        </person-group>
        <article-title>Telemedicine technology and clinical applications</article-title>
        <source>JAMA</source>  
        <year>1995</year>  
        <month>02</month>  
        <day>08</day>  
        <volume>273</volume>  
        <issue>6</issue>  
        <fpage>483</fpage>  
        <pub-id pub-id-type="doi">10.1001/jama.1995.03520300057037</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>Doolittle</surname>
            <given-names>GC</given-names>
          </name>
          <name name-style="western">
            <surname>Spaulding</surname>
            <given-names>AO</given-names>
          </name>
        </person-group>
        <article-title>Providing access to oncology care for rural patients via telemedicine</article-title>
        <source>JOP</source>  
        <year>2006</year>  
        <month>09</month>  
        <volume>2</volume>  
        <issue>5</issue>  
        <fpage>228</fpage>  
        <lpage>30</lpage>  
        <pub-id pub-id-type="doi">10.1200/jop.2006.2.5.228</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>Coelho</surname>
            <given-names>KR</given-names>
          </name>
        </person-group>
        <article-title>Identifying telemedicine services to improve access to specialty care for the underserved in the san francisco safety net</article-title>
        <source>Int J Telemed Appl</source>  
        <year>2011</year>  
        <volume>2011</volume>  
        <fpage>523161</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://dx.doi.org/10.1155/2011/523161"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1155/2011/523161</pub-id>
        <pub-id pub-id-type="medline">22187550</pub-id>
        <pub-id pub-id-type="pmcid">PMC3236479</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>Levine</surname>
            <given-names>SR</given-names>
          </name>
          <name name-style="western">
            <surname>Gorman</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>“Telestroke” : the application of telemedicine for stroke</article-title>
        <source>Stroke</source>  
        <year>1999</year>  
        <month>02</month>  
        <day>01</day>  
        <volume>30</volume>  
        <issue>2</issue>  
        <fpage>464</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1161/01.STR.30.2.464</pub-id></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Field</surname>
            <given-names>MJ</given-names>
          </name>
        </person-group>
        <source>Telemedicine: a guide to assessing telecommunications in health care</source>  
        <year>1996</year>  
        <publisher-loc>Washington, DC</publisher-loc>
        <publisher-name>National Academy Press</publisher-name></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>Chen</surname>  
        <given-names>L</given-names></name>  
        <name name-style="western">
        <surname>Ho</surname>  
        <given-names>T</given-names></name>  
        <name name-style="western">
        <surname>Shih</surname>  
        <given-names>C</given-names></name>  
        <name name-style="western">
        <surname>Lin</surname>  
        <given-names>F</given-names></name>  
        <name name-style="western">
        <surname>Lai</surname>  
        <given-names>F</given-names></name>  
        <name name-style="western">
        <surname>Guo</surname>  
        <given-names>J</given-names></name>  
        <name name-style="western">
        <surname>Zhuang</surname>  
        <given-names>M</given-names></name> </person-group>
        <article-title>Urban-rural difference in patients utilizing the service of telehealthcare</article-title>
        <source>JHA</source>  
        <year>2015</year>  
        <month>09</month>  
        <day>01</day>  
        <volume>4</volume>  
        <issue>6</issue>  
        <fpage>9</fpage>  
        <pub-id pub-id-type="doi">10.5430/jha.v4n6p56</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>Miller</surname>
            <given-names>EA</given-names>
          </name>
        </person-group>
        <article-title>The technical and interpersonal aspects of telemedicine: effects on doctor-patient communication</article-title>
        <source>J Telemed Telecare</source>  
        <year>2003</year>  
        <volume>9</volume>  
        <issue>1</issue>  
        <fpage>1</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1258/135763303321159611</pub-id>
        <pub-id pub-id-type="medline">12641885</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>Glascock</surname>
            <given-names>AP</given-names>
          </name>
          <name name-style="western">
            <surname>Kutzik</surname>
            <given-names>DM</given-names>
          </name>
        </person-group>
        <article-title>Behavioral telemedicine: a new approach to the continuous nonintrusive monitoring of activities of daily living</article-title>
        <source>Telemed J</source>  
        <year>2000</year>  
        <month>05</month>  
        <volume>6</volume>  
        <issue>1</issue>  
        <fpage>33</fpage>  
        <lpage>44</lpage>  
        <pub-id pub-id-type="doi">10.1089/107830200311833</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>Shaw</surname>
            <given-names>RJ</given-names>
          </name>
          <name name-style="western">
            <surname>Kaufman</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Bosworth</surname>
            <given-names>HB</given-names>
          </name>
          <name name-style="western">
            <surname>Weiner</surname>
            <given-names>BJ</given-names>
          </name>
          <name name-style="western">
            <surname>Zullig</surname>
            <given-names>LL</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>SY</given-names>
          </name>
          <name name-style="western">
            <surname>Kravetz</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Rakley</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Roumie</surname>
            <given-names>CL</given-names>
          </name>
          <name name-style="western">
            <surname>Bowen</surname>
            <given-names>ME</given-names>
          </name>
          <name name-style="western">
            <surname>Del Monte</surname>
            <given-names>PS</given-names>
          </name>
          <name name-style="western">
            <surname>Oddone</surname>
            <given-names>EZ</given-names>
          </name>
          <name name-style="western">
            <surname>Jackson</surname>
            <given-names>GL</given-names>
          </name>
        </person-group>
        <article-title>Organizational factors associated with readiness to implement and translate a primary care based telemedicine behavioral program to improve blood pressure control: the HTN-IMPROVE study</article-title>
        <source>Implement Sci</source>  
        <year>2013</year>  
        <month>09</month>  
        <day>08</day>  
        <volume>8</volume>  
        <fpage>106</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-8-106"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/1748-5908-8-106</pub-id>
        <pub-id pub-id-type="medline">24010683</pub-id>
        <pub-id pub-id-type="pii">1748-5908-8-106</pub-id>
        <pub-id pub-id-type="pmcid">PMC3847033</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>Frank</surname>
            <given-names>AP</given-names>
          </name>
          <name name-style="western">
            <surname>Wandell</surname>
            <given-names>MG</given-names>
          </name>
          <name name-style="western">
            <surname>Headings</surname>
            <given-names>MD</given-names>
          </name>
          <name name-style="western">
            <surname>Conant</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Woody</surname>
            <given-names>GE</given-names>
          </name>
          <name name-style="western">
            <surname>Michel</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Anonymous HIV testing using home collection and telemedicine counseling. a multicenter evaluation</article-title>
        <source>Arch Intern Med</source>  
        <year>1997</year>  
        <month>02</month>  
        <day>10</day>  
        <volume>157</volume>  
        <issue>3</issue>  
        <pub-id pub-id-type="medline">9040298</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>Riemer-Reiss</surname>  
        <given-names>ML</given-names></name> </person-group>
        <article-title>Utilizing distance technology for mental health counseling</article-title>
        <source>J Ment Health Couns</source>  
        <year>2000</year>  
        <month>07</month>  
        <volume>22</volume>  
        <issue>3</issue>  
        <fpage>189</fpage> </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>Ertelt</surname>
            <given-names>TW</given-names>
          </name>
          <name name-style="western">
            <surname>Crosby</surname>
            <given-names>RD</given-names>
          </name>
          <name name-style="western">
            <surname>Marino</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Mitchell</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Lancaster</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Crow</surname>
            <given-names>SJ</given-names>
          </name>
        </person-group>
        <article-title>Therapeutic factors affecting the cognitive behavioral treatment of bulimia nervosa via telemedicine versus face-to-face delivery</article-title>
        <source>Int J Eat Disord</source>  
        <year>2010</year>  
        <month>11</month>  
        <day>15</day>  
        <volume>44</volume>  
        <issue>8</issue>  
        <fpage>687</fpage>  
        <lpage>91</lpage>  
        <pub-id pub-id-type="doi">10.1002/eat.20874</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>Welch</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Balder</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Zagarins</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Telehealth program for type 2 diabetes: usability, satisfaction, and clinical usefulness in an urban community health center</article-title>
        <source>Telemed J E Health</source>  
        <year>2015</year>  
        <month>05</month>  
        <day>08</day>  
        <volume>21</volume>  
        <issue>5</issue>  
        <fpage>395</fpage>  
        <lpage>403</lpage>  
        <pub-id pub-id-type="doi">10.1089/tmj.2014.0069</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>Izquierdo</surname>
            <given-names>RE</given-names>
          </name>
          <name name-style="western">
            <surname>Knudson</surname>
            <given-names>PE</given-names>
          </name>
          <name name-style="western">
            <surname>Meyer</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Kearns</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Ploutz-Snyder</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Weinstock</surname>
            <given-names>RS</given-names>
          </name>
        </person-group>
        <article-title>A comparison of diabetes education administered through telemedicine versus in person</article-title>
        <source>Diabetes Care</source>  
        <year>2003</year>  
        <month>04</month>  
        <day>01</day>  
        <volume>26</volume>  
        <issue>4</issue>  
        <fpage>1002</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.2337/diacare.26.4.1002</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>Lilholt</surname>
            <given-names>PH</given-names>
          </name>
          <name name-style="western">
            <surname>Jensen</surname>
            <given-names>MH</given-names>
          </name>
          <name name-style="western">
            <surname>Hejlesen</surname>
            <given-names>OK</given-names>
          </name>
        </person-group>
        <article-title>Heuristic evaluation of a telehealth system from the Danish TeleCare North Trial</article-title>
        <source>Int J Med Inform</source>  
        <year>2015</year>  
        <month>05</month>  
        <volume>84</volume>  
        <issue>5</issue>  
        <fpage>319</fpage>  
        <lpage>26</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.01.012</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>Yellowlees</surname>  
        <given-names>PM</given-names></name> </person-group>
        <article-title>Successfully developing a telemedicine system</article-title>
        <source>J Telemed Telecare</source>  
        <year>2005</year>  
        <volume>11</volume>  
        <issue>7</issue>  
        <fpage>331</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="medline">16238833</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>Klaassen</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>van Beijnum</surname>
            <given-names>BJF</given-names>
          </name>
          <name name-style="western">
            <surname>Hermens</surname>
            <given-names>HJ</given-names>
          </name>
        </person-group>
        <article-title>Usability in telemedicine systems—a literature survey</article-title>
        <source>Int J Med Inform</source>  
        <year>2016</year>  
        <month>09</month>  
        <volume>93</volume>  
        <fpage>57</fpage>  
        <lpage>69</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2016.06.004</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>Evans</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Papadopoulos</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Silvers</surname>
            <given-names>CT</given-names>
          </name>
          <name name-style="western">
            <surname>Charness</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Boot</surname>
            <given-names>WR</given-names>
          </name>
          <name name-style="western">
            <surname>Schlachta-Fairchild</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Crump</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Martinez</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ent</surname>
            <given-names>CB</given-names>
          </name>
        </person-group>
        <article-title>Remote health monitoring for older adults and those with heart failure: adherence and system usability</article-title>
        <source>Telemed J E Health</source>  
        <year>2016</year>  
        <month>05</month>  
        <day>25</day>  
        <volume>22</volume>  
        <issue>6</issue>  
        <fpage>480</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="doi">10.1089/tmj.2015.0140</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>Rogers</surname>  
        <given-names>H</given-names></name>  
        <name name-style="western">
        <surname>Chalil Madathil</surname>  
        <given-names>K</given-names></name>  
        <name name-style="western">
        <surname>Agnisarman</surname>  
        <given-names>S</given-names></name>  
        <name name-style="western">
        <surname>Narasimha</surname>  
        <given-names>S</given-names></name>  
        <name name-style="western">
        <surname>Ashok</surname>  
        <given-names>A</given-names></name>  
        <name name-style="western">
        <surname>Nair</surname>  
        <given-names>A</given-names></name>  
        <name name-style="western">
        <surname>Welch</surname>  
        <given-names>Bm</given-names></name>  
        <name name-style="western">
        <surname>McElligott</surname>  
        <given-names>Jt</given-names></name> </person-group>
        <article-title>A Systematic Review of the Implementation Challenges of Telemedicine Systems in Ambulances</article-title>
        <source>Telemedicine and e-Health</source>  
        <year>2017</year>  
        <month>03</month>  
        <day>15</day>  
        <comment>Epub ahead of print</comment>  
        <pub-id pub-id-type="doi">10.1089/tmj.2016.0248</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>Agnisarman</surname>
            <given-names>SO</given-names>
          </name>
          <name name-style="western">
            <surname>Chalil</surname>
            <given-names>MK</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Ashok</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Welch</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>McElligott</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Lessons learned from the usability assessment of home-based telemedicine systems</article-title>
        <source>Appl Ergon</source>  
        <year>2017</year>  
        <month>01</month>  
        <volume>58</volume>  
        <fpage>424</fpage>  
        <lpage>34</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.apergo.2016.08.003</pub-id>
        <pub-id pub-id-type="medline">27633239</pub-id>
        <pub-id pub-id-type="pii">S0003-6870(16)30155-7</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>Narasimha</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Chalil</surname>
            <given-names>MK</given-names>
          </name>
          <name name-style="western">
            <surname>Agnisarman</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Rogers</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Welch</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Ashok</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Nair</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>McElligott</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Designing telemedicine systems for geriatric patients: a review of the usability studies</article-title>
        <source>Telemed J E Health</source>  
        <year>2016</year>  
        <month>11</month>  
        <day>22</day>  
        <comment>Epub ahead of print</comment>  
        <pub-id pub-id-type="doi">10.1089/tmj.2016.0178</pub-id>
        <pub-id pub-id-type="medline">27875667</pub-id></nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Narasimha</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Agnisarman</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Gramopadhye</surname>
            <given-names>AK</given-names>
          </name>
          <name name-style="western">
            <surname>Welch</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Mcelligott</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>An investigation of the usability issues of home-based video telemedicine systems with geriatric patients</article-title>
        <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>  
        <year>2016</year>  
        <conf-name>Human Factors and Ergonomics Society Annual Meeting, 2016</conf-name>
        <conf-date>September 19–23, 2016</conf-date>
        <conf-loc>Washington, DC</conf-loc>
        <fpage>1804</fpage> </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>Chalil</surname>
            <given-names>MK</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>An investigation of the efficacy of collaborative virtual reality systems for moderated remote usability testing</article-title>
        <source>Appl Ergon</source>  
        <year>2017</year>  
        <month>02</month>  
        <day>27</day>  
        <comment>Epub ahead of print</comment>  
        <pub-id pub-id-type="doi">10.1016/j.apergo.2017.02.011</pub-id>
        <pub-id pub-id-type="medline">28256209</pub-id>
        <pub-id pub-id-type="pii">S0003-6870(17)30037-6</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Molich</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Heuristic evaluation of user interfaces</article-title>
        <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>  
        <year>1990</year>  
        <conf-name>SIGCHI Conference on Human Factors in Computing Systems</conf-name>
        <conf-date>April 01 - 05, 1990</conf-date>
        <conf-loc>Seattle, Washington, DC</conf-loc>
        <publisher-loc>New York, NY</publisher-loc>
        <publisher-name>ACM</publisher-name>
        <fpage>249</fpage>  
        <lpage>56</lpage>  
        <pub-id pub-id-type="doi">10.1145/97243.97281</pub-id></nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Usability inspection methods</article-title>
        <source>CHI '94 Conference Companion on Human Factors in Computing Systems</source>  
        <year>1994</year>  
        <conf-name>Conference Companion on Human Factors in Computing Systems</conf-name>
        <conf-date>April 24 - 28, 1994</conf-date>
        <conf-loc>Boston, MA</conf-loc>
        <publisher-loc>New York, NY</publisher-loc>
        <publisher-name>ACM</publisher-name></nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Bishu</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Web evaluation: Heuristic evaluation vs. user testing</article-title>
        <source>Int J Ind Ergonom</source>  
        <year>2009</year>  
        <volume>39</volume>  
        <issue>4</issue>  
        <fpage>621</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ergon.2008.02.012</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>Hvannberg</surname>
            <given-names>ET</given-names>
          </name>
          <name name-style="western">
            <surname>Law</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Lárusdóttir</surname>
            <given-names>MK</given-names>
          </name>
        </person-group>
        <article-title>Heuristic evaluation: comparing ways of finding and reporting usability problems</article-title>
        <source>Interact Comput</source>  
        <year>2007</year>  
        <month>3</month>  
        <volume>19</volume>  
        <issue>2</issue>  
        <fpage>225</fpage>  
        <lpage>40</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.intcom.2006.10.001</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Synchronous remote usability testing: a new approach facilitated by virtual worlds</article-title>
        <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>  
        <year>2011</year>  
        <conf-name>SIGCHI Conference on Human Factors in Computing Systems</conf-name>
        <conf-date>May 07 - 12, 2011</conf-date>
        <conf-loc>Vancouver, British Columbia, Canada</conf-loc>
        <publisher-loc>New York, NY</publisher-loc>
        <publisher-name>ACM</publisher-name>
        <fpage>2225</fpage>  
        <lpage>34</lpage> </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>Graham</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Kubose</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Jordan</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Johnson</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>V</given-names>
          </name>
        </person-group>
        <article-title>Heuristic evaluation of infusion pumps: implications for patient safety in Intensive Care Units</article-title>
        <source>Int J Med Inform</source>  
        <year>2004</year>  
        <month>11</month>  
        <volume>73</volume>  
        <issue>11-12</issue>  
        <fpage>771</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2004.08.002</pub-id>
        <pub-id pub-id-type="medline">15491928</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(04)00181-9</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>Rogers</surname>
            <given-names>WA</given-names>
          </name>
          <name name-style="western">
            <surname>Mykityshyn</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Campbell</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Fisk</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Analysis of a “Simple” Medical Device</article-title>
        <source>Ergon Des</source>  
        <year>2001</year>  
        <month>01</month>  
        <day>01</day>  
        <volume>9</volume>  
        <issue>1</issue>  
        <fpage>6</fpage>  
        <lpage>14</lpage>  
        <pub-id pub-id-type="doi">10.1177/106480460100900103</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>Zhang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Johnson</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Paige</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Kubose</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Using usability heuristics to evaluate patient safety of medical devices</article-title>
        <source>J Biomed Inform</source>  
        <year>2003</year>  
        <volume>36</volume>  
        <issue>1-2</issue>  
        <fpage>23</fpage>  
        <lpage>30</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532046403000601"/>
        </comment>  
        <pub-id pub-id-type="medline">14552844</pub-id>
        <pub-id pub-id-type="pii">S1532046403000601</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>Kushniruk</surname>
            <given-names>AW</given-names>
          </name>
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>V</given-names>
          </name>
        </person-group>
        <article-title>Cognitive and usability engineering methods for the evaluation of clinical information systems</article-title>
        <source>J Biomed Inform</source>  
        <year>2004</year>  
        <month>02</month>  
        <volume>37</volume>  
        <issue>1</issue>  
        <fpage>56</fpage>  
        <lpage>76</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532046404000206"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2004.01.003</pub-id>
        <pub-id pub-id-type="medline">15016386</pub-id>
        <pub-id pub-id-type="pii">S1532046404000206</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>Stellefson</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Chaney</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Chaney</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Heuristic evaluation of online COPD respiratory therapy and education video resource center</article-title>
        <source>Telemed J E Health</source>  
        <year>2014</year>  
        <month>10</month>  
        <volume>20</volume>  
        <issue>10</issue>  
        <fpage>972</fpage>  
        <lpage>6</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24650318"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1089/tmj.2014.0009</pub-id>
        <pub-id pub-id-type="medline">24650318</pub-id>
        <pub-id pub-id-type="pmcid">PMC4188380</pub-id></nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Alapatt</surname>
            <given-names>GF</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>An investigation of the usability of image-based CAPTCHAs</article-title>
        <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>  
        <year>2010</year>  
        <conf-name>Human Factors and Ergonomics Society Annual Meeting, 2010</conf-name>
        <conf-date>September 27-October 1, 2010</conf-date>
        <conf-loc>San Francisco, CA</conf-loc></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Koikkara</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Dorlette-Paul</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ranganayakulu</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Gramopadhye</surname>
            <given-names>AK</given-names>
          </name>
        </person-group>
        <article-title>An investigation of format modifications on the comprehension of information in consent form when presented on mobile devices</article-title>
        <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>  
        <year>2012</year>  
        <conf-name>Human Factors and Ergonomics Society Annual Meeting, 2012</conf-name>
        <conf-date>October 22-26, 2012</conf-date>
        <conf-loc>Boston, MA</conf-loc></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Koikkara</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Gramopadhye</surname>
            <given-names>AK</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>An empirical study of the usability of consenting systems iPad, touchscreen and paper-based systems</article-title>
        <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>  
        <year>2011</year>  
        <conf-name>Human Factors and Ergonomics Society Annual Meeting, 2011</conf-name>
        <conf-date>September 19-23, 2011</conf-date>
        <conf-loc>Las Vegas, NV</conf-loc></nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wismer</surname>
            <given-names>AJ</given-names>
          </name>
          <name name-style="western">
            <surname>Chalil Madathil</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Koikkara</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Juang</surname>
            <given-names>KA</given-names>
          </name>
          <name name-style="western">
            <surname>Greenstein</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>Evaluating the usability of CAPTCHAs on a mobile device with voice and touch input</article-title>
        <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>  
        <year>2016</year>  
        <conf-name>Human Factors and Ergonomics Society Annual Meeting, 2012</conf-name>
        <conf-date>October 22-26, 2012</conf-date>
        <conf-loc>Boston, MA</conf-loc></nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
        <source>U.S. Department of Health &#38; Human Services</source>  
        <year>2015</year>  
        <month>08</month>  
        <day>26</day>  
        <access-date>2017-03-17</access-date>
        <comment>Health Information Privacy 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/index.html">https://www.hhs.gov/hipaa/index.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6p24OF223"/></comment> </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Nielsen Norman Group</source>  
        <year>1995</year>  
        <access-date>2017-03-17</access-date>
        <publisher-name>Nielsen Norman Group</publisher-name>
        <comment>Severity ratings for usability problems 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/">https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6p26jI3Jk"/></comment> </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Custódio</surname>
            <given-names>RAR</given-names>
          </name>
          <name name-style="western">
            <surname>Almeida</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Correa</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Almeida</surname>
            <given-names>RMA</given-names>
          </name>
          <name name-style="western">
            <surname>Mello</surname>
            <given-names>CHP</given-names>
          </name>
          <name name-style="western">
            <surname>Muller Júnior</surname>
            <given-names>EL</given-names>
          </name>
        </person-group>
        <article-title>Using heuristic analysis to support usability evaluation of a low risk medical device under development process</article-title>
        <source>IFMBE Proceedings</source>  
        <year>2015</year>  
        <conf-name>World Congress on Medical Physics and Biomedical Engineering</conf-name>
        <conf-date>2015</conf-date>
        <conf-loc>Toronto, Ontario</conf-loc>
        <publisher-loc>Switzerland</publisher-loc>
        <publisher-name>Springer International Publishing</publisher-name>
        <pub-id pub-id-type="doi">10.1007/978-3-319-19387-8_366</pub-id></nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Horberry</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Teng</surname>
            <given-names>YC</given-names>
          </name>
          <name name-style="western">
            <surname>Ward</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Clarkson</surname>
            <given-names>PJ</given-names>
          </name>
        </person-group>
        <article-title>Safe design of medical equipment: employing usability heuristics to examine the issue of guidewire retention after surgery</article-title>
        <source>HFESA 2013</source>  
        <year>2013</year>  
        <conf-name>49th Annual Human Factors and Ergonomics Society of Australia Conference 2013</conf-name>
        <conf-date>December 2-4, 2013</conf-date>
        <conf-loc>Perth, Australia</conf-loc></nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Horberry</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Teng</surname>
            <given-names>YC</given-names>
          </name>
          <name name-style="western">
            <surname>Ward</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Clarkson</surname>
            <given-names>PJ</given-names>
          </name>
        </person-group>
        <article-title>Employing usability heuristics to examine the issue of guidewire retention after surgery</article-title>
        <source>Ergonomics Australia</source>  
        <year>2014</year>  
        <month>02</month>  
        <day>10</day>  
        <volume>1</volume>  
        <issue>1</issue>  
        <fpage>1</fpage>  
        <lpage>5</lpage> </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Finding usability problems through heuristic evaluation</article-title>
        <source>CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>  
        <year>1992</year>  
        <conf-name>SIGCHI Conference on Human Factors in Computing Systems</conf-name>
        <conf-date>May 03-07, 1992</conf-date>
        <conf-loc>Monterey, CA</conf-loc>
        <publisher-loc>New York, NY</publisher-loc>
        <publisher-name>ACM</publisher-name>
        <fpage>373</fpage>  
        <lpage>380</lpage> </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wickens</surname>
            <given-names>CD</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>JP</given-names>
          </name>
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Gordon-Becker</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Gordon</surname>
            <given-names>SE</given-names>
          </name>
        </person-group>
        <source>An introduction to human factors engineering</source>  
        <year>2004</year>  
        <publisher-loc>Upper Saddle River, NJ</publisher-loc>
        <publisher-name>Pearson Prentice Hall</publisher-name></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
