<?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</journal-id>
            <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
            <journal-title>Journal of Medical Internet Research</journal-title>
            <issn pub-type="epub">1438-8871</issn>
            <publisher>
                <publisher-name>Gunther Eysenbach</publisher-name>
                <publisher-loc>Centre for Global eHealth Innovation, Toronto, Canada</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="publisher-id">v11i4e47</article-id>
            <article-id pub-id-type="pmid">19897458</article-id>
            <article-id pub-id-type="doi">10.2196/jmir.1244</article-id>
            <article-categories>
                <subj-group subj-group-type="article-type">
                    <subject>Tutorial</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Usability of a Patient Education and Motivation Tool Using Heuristic Evaluation</article-title>
            </title-group>
            <!--contrib-group from ojs / api-xml-->
            <contrib-group>
                <contrib contrib-type="editor">
                    <name>
                        <surname>Eysenbach</surname>
                        <given-names>Gunther</given-names>
                    </name>
                </contrib>
            </contrib-group>
            <contrib-group>
                <contrib contrib-type="reviewer">
                    <name>
                        <surname>Mackert</surname>
                        <given-names>Michael</given-names>
                    </name>
                </contrib>
                <contrib contrib-type="reviewer">
                    <name>
                        <surname>Witteman</surname>
                        <given-names>Holly</given-names>
                    </name>
                </contrib>
            </contrib-group>
            <!--contrib-group from ojs ends-->
            <contrib-group>
                <contrib contrib-type="author" id="contrib1" corresp="yes">
                    <name name-style="western">
                        <surname>Joshi</surname>
                        <given-names>Ashish</given-names>
                    </name>
                    <degrees>MD</degrees>
                    <degrees>MPH</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                    <address>

                        <institution>Department of Information Systems</institution>
                        <institution>University of Maryland, Baltimore County</institution>
                        <addr-line>1000 Hilltop Circle, ITE 437</addr-line>
                        <addr-line>Baltimore, MD 21250</addr-line>
                        <country>USA</country>
                        <phone>+1 410 455 8837</phone>
                        <fax>+1 410 455 1217</fax>
                        <email>asjoshi@umbc.edu</email>
                    </address>
                </contrib>
                <contrib contrib-type="author" id="contrib2">
                    <name name-style="western">
                        <surname>Arora</surname>
                        <given-names>Mohit</given-names>
                    </name>
                    <degrees>MS</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib3">
                    <name name-style="western">
                        <surname>Dai</surname>
                        <given-names>Liwei</given-names>
                    </name>
                    <degrees>PhD</degrees>
                    <xref ref-type="aff" rid="aff2">2</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib4">
                    <name name-style="western">
                        <surname>Price</surname>
                        <given-names>Kathleen</given-names>
                    </name>
                    <degrees>MS</degrees>
                    <degrees>RN</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib5">
                    <name name-style="western">
                        <surname>Vizer</surname>
                        <given-names>Lisa</given-names>
                    </name>
                    <degrees>MS</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib6">
                    <name name-style="western">
                        <surname>Sears</surname>
                        <given-names>Andrew</given-names>
                    </name>
                    <degrees>PhD</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
            </contrib-group>
            <aff id="aff2" rid="aff2">
                <sup>2</sup>
                <addr-line>Usability Engineering Group</addr-line>
                <addr-line>Xerox Corporation</addr-line>
                <addr-line>Baltimore</addr-line>
                <addr-line>MD</addr-line>
                <country>USA</country>
            </aff>
            <aff id="aff1" rid="aff1">
                <sup>1</sup>
                <institution>Department of Information Systems</institution>
                <institution>University of Maryland</institution>
                <addr-line>Baltimore County</addr-line>
                <addr-line>Baltimore</addr-line>
                <addr-line>MD</addr-line>
                <country>USA</country>
            </aff>
            <pub-date pub-type="collection">
                <season>Oct-Dec</season>
                <year>2009</year>
            </pub-date>
            <pub-date pub-type="epub">
                <day>6</day>
                <month>11</month>
                <year>2009</year>
            </pub-date>
            <volume>11</volume>
            <issue>4</issue>
            <elocation-id>e47</elocation-id>
            <!--history from ojs - api-xml-->
            <history>
                <date date-type="received">
                    <day>06</day>
                    <month>04</month>
                    <year>2009</year>
                </date>
                <date date-type="rev-request">
                    <day>28</day>
                    <month>04</month>
                    <year>2009</year>
                </date>
                <date date-type="rev-recd">
                    <day>17</day>
                    <month>09</month>
                    <year>2009</year>
                </date>
                <date date-type="accepted">
                    <day>09</day>
                    <month>10</month>
                    <year>2009</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>&#169; Ashish Joshi, Mohit Arora, Liwei Dai, Kathleen Price, Lisa Vizer, Andrew Sears.  Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 06.11.2009.  &#160;
	</copyright-statement>
            <copyright-year>2009</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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
            </license>
            <!--<related-article related-article-type="commentary&#124;commentary-article&#124;corrected-article" 
						xlink:title="Commentary in:&#124;Commentary to:&#124;Correction of:" xlink:href="http://dx.doi.org/10.2196/jmir.1000" 
						vol="##" page="e##"> </related-article>-->
            <self-uri xlink:href="http://www.jmir.org/2009/4/e47/" xlink:type="simple" />
            <abstract>
                <sec sec-type="background">
                    <title>Background</title>
                    <p>Computer-mediated educational applications can provide a self-paced, interactive environment to deliver educational content to individuals about their health condition. These programs have been used to deliver health-related information about a variety of topics, including breast cancer screening, asthma management, and injury prevention. We have designed the Patient Education and Motivation Tool (PEMT), an interactive computer-based educational program based on behavioral, cognitive, and humanistic learning theories. The tool is designed to educate users and has three key components: screening, learning, and evaluation.</p>
                </sec>
                <sec sec-type="objective">
                    <title>Objective</title>
                    <p>The objective of this tutorial is to illustrate a heuristic evaluation using a computer-based patient education program (PEMT) as a case study. The aims were to improve the usability of PEMT through heuristic evaluation of the interface; to report the results of these usability evaluations; to make changes based on the findings of the usability experts; and to describe the benefits and limitations of applying usability evaluations to PEMT.</p>
                </sec>
                <sec sec-type="methods">
                    <title>Methods</title>
                    <p>PEMT was evaluated by three usability experts using Nielsen&#8217;s usability heuristics while reviewing the interface to produce a list of heuristic violations with severity ratings. The violations were sorted by heuristic and ordered from most to least severe within each heuristic.</p>
                </sec>
                <sec sec-type="results">
                    <title>Results</title>
                    <p>A total of 127 violations were identified with a median severity of 3 (range 0 to 4 with 0 = no problem to 4 = catastrophic problem). Results showed 13 violations for visibility (median severity = 2), 38 violations for match between system and real world (median severity = 2), 6 violations for user control and freedom (median severity = 3), 34 violations for consistency and standards (median severity = 2), 11 violations for error severity (median severity = 3), 1 violation for recognition and control (median severity = 3), 7 violations for flexibility and efficiency (median severity = 2), 9 violations for aesthetic and minimalist design (median severity = 2), 4 violations for help users recognize, diagnose, and recover from errors (median severity = 3), and 4 violations for help and documentation (median severity = 4).</p>
                </sec>
                <sec sec-type="conclusion">
                    <title>Conclusion</title>
                    <p>We describe the heuristic evaluation method employed to assess the usability of PEMT, a method which uncovers heuristic violations in the interface design in a quick and efficient manner. Bringing together usability experts and health professionals to evaluate a computer-mediated patient education program can help to identify problems in a timely manner. This makes this method particularly well suited to the iterative design process when developing other computer-mediated health education programs. Heuristic evaluations provided a means to assess the user interface of PEMT.</p>
                </sec>
            </abstract>
            <kwd-group>
                <kwd>Computers</kwd>
                <kwd>health</kwd>
                <kwd>education</kwd>
                <kwd>usability</kwd>
                <kwd>heuristic</kwd>
            </kwd-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="introduction">
            <title>Introduction</title>
            <p>Computer technology has been widely used for education of both patients and health care professionals. Patient receptivity to computerized education is reported to be high across diverse medical settings and age groups. Computerized patient education has also been shown to increase patient knowledge, but little is reported about the results of findings of usability assessments of computerized patient education programs.</p>
            <p>The objective of this case study was to describe the usability of the Patient Education and Motivation Tool (PEMT) through heuristic evaluation of the interface. We report the results of the usability evaluation, make changes based on the findings of the usability experts, and describe the benefits and limitations of applying usability evaluations to PEMT. We used Nielson&#8217;s 10 usability heuristics [<xref ref-type="bibr" rid="ref6">6</xref>] to identify potential usability problems, describe severity ratings for each heuristic violation, and use the results to improve the overall usability of PEMT. This paper presents the results of the heuristic evaluation of PEMT, system changes performed based on the evaluation, and planned future research.</p>
            <sec>
                <title>Human-Computer Interaction Evaluation</title>
                <p>Human factor or usability engineering is a discipline that investigates human/machine interface issues, using a wide array of methodologies [<xref ref-type="bibr" rid="ref7">7</xref>]. These methodologies vary in terms of research design, complexity, cost, duration, and relevance to operational programs [<xref ref-type="bibr" rid="ref7">7</xref>]. The two approaches for evaluating the human-computer interaction (HCI) characteristics of a system include inspection methods or user evaluations [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Inspection methods are based on reviews of a system, often by experts, which can be guided by usability heuristics, user tasks, or other information [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. User evaluations measure user task performance in a lab setting [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Using these methods in system development has been recognized as an important way to ensure the usability of the end product [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>].</p>
                <p>Nielson defines heuristic evaluation as a measurement that utilizes heuristics in order to find usability problems [<xref ref-type="bibr" rid="ref4">4</xref>]. Nielson&#8217;s method uses a small set of principles, guidelines, or heuristics that are systematically assessed against a target system in order to identify problems and their severity, as well consequences for the user [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Heuristic evaluation is an effective usability inspection method for discovering the most serious problems with a low investment of resources, while representing a high cost-benefit ratio [<xref ref-type="bibr" rid="ref10">10</xref>]. During the heuristic evaluation, a group of usability experts examine the user interface design according to a set of usability guidelines [<xref ref-type="bibr" rid="ref11">11</xref>]. A list of heuristic violations found in the interface design and an assessment of the severity of these problems is generated [<xref ref-type="bibr" rid="ref11">11</xref>]. The results can be utilized as suggestions for interface refinements. This method requires less time and resources than many other usability engineering methods. Nielsen identified 10 usability heuristics as the basic characteristics of usable interfaces [<xref ref-type="bibr" rid="ref4">4</xref>]. Research in the past has shown that usability inspection through heuristic evaluation is an effective way to uncover user interface design problems in a broad range of clinical contexts [<xref ref-type="bibr" rid="ref12">12</xref>]. In a previous study, heuristic evaluation combined with small-scale expert assessment was examined in the context of the design and development of a Web-based telemedicine system [<xref ref-type="bibr" rid="ref12">12</xref>]. The study found usage difficulties related to HCI problems primarily characterized by a mismatch of the designer model and the content expert model [<xref ref-type="bibr" rid="ref12">12</xref>]. The heuristic/usage methodology provided an incremental benefit in a variety of design activities [<xref ref-type="bibr" rid="ref12">12</xref>]. They examined a software user interface with heuristic evaluation, software guidelines, cognitive walkthrough, and usability testing and found that heuristic evaluation by several user interface specialists yielded the highest number of serious problems with the least amount of effort [<xref ref-type="bibr" rid="ref12">12</xref>]. A single general usability expert familiar with the kind of interface being evaluated can identify about 60% of the problems [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. This method was applied to support the clinical information system during a standard Call for Tender and was found to be an efficient and cost-effective approach to choose an appropriate and useful clinical information system [<xref ref-type="bibr" rid="ref14">14</xref>]. In another study, Zhang and colleagues applied this method to evaluate patient safety with regard to the use of medical devices [<xref ref-type="bibr" rid="ref15">15</xref>]. Heuristic evaluation through the identification of usability problems and their severities was found to be a useful, efficient, and low-cost method to evaluate patient safety features of medical devices [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
            </sec>
            <sec>
                <title>Overview of the Patient Education and Motivation Tool (PEMT)</title>
                <p>PEMT is an interactive computer-based program that is being designed according to three sets of learning theories [<xref ref-type="bibr" rid="ref16">16</xref>]: behavioral, cognitive, and humanistic. Two key ideas of behavioral theory are that learning is manifested by a change in behavior and that technology-based instructional materials should be introduced in increments. Cognitive learning theory focuses on providing structured education to individuals along with reinforcement. Humanistic theory predominantly emphasizes the participants&#8217; willingness to learn and their ability to be evaluated. The outcome of learning depends upon how the information is presented and how the learner processes that information.</p>
                <p>A computer-based educational program provides individuals with a self-paced learning environment and presents educational modules as a series of short messages. The information is provided in various representations, including audio, images, text, and animation with the resulting program being interactive. The system accounts for a variety of literacy levels and learning styles amongst users. Visual learners prefer seeing what they are learning, so pictures and images help them understand ideas and information better than text-based explanations [<xref ref-type="bibr" rid="ref17">17</xref>]. Auditory learners learn best by hearing things and remember verbal instructions well, preferring someone else read the directions to them while they do the physical work or task [<xref ref-type="bibr" rid="ref18">18</xref>]. PEMT allows users to toggle the audio on or off based on their preferences. The tool provides users with the opportunity and flexibility to navigate modules relevant to their condition by allowing them to move forward and backward at their own pace. PEMT also provides users with access to extensive information and empowers patients to obtain pertinent information about their condition. We employed usability principles when designing the user interface [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
                <p>PEMT has three key components [<xref ref-type="bibr" rid="ref20">20</xref>]:</p>
                <list list-type="order">
                    <list-item>
                        <p>
                            <bold>Screening</bold>: PEMT allows users to enter information about their socio-demographics at their own pace, including age, gender, education, disease severity, and prior disease knowledge through a series of multiple-choice questions. No feedback is given to the individuals during this component.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <bold>Learning</bold>: The learning material is broken down into a series of educational messages with relevant audio, images, and animations as appropriate. Individuals can move forward and backward through the messages by clicking next and back buttons. The information on each screen varies in terms of the number of paragraphs, sentences, words, bulleted items, highlights, and animations.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <bold>Evaluation</bold>: The evaluation component is a post-learning questionnaire similar to that used during the screening component. Feedback is provided to the users based on their responses. Users giving correct responses receive positive prompts and encouragement while individuals giving incorrect responses are given corrective feedback and reinforcement. The goal of the evaluation component is to track the progress of individual behavior, knowledge, and disease progression over a period of time.</p>
                    </list-item>
                </list>
                <p>These three key components of PEMT make it a multifaceted tool that can be utilized to screen individuals&#8217; demographics, health literacy, prior knowledge, attitudes, behavior, and prior use of technology. The tool has been successfully employed in different clinical settings (including emergency departments and outpatient clinics), for different conditions, including asthma [<xref ref-type="bibr" rid="ref20">20</xref>] and influenza [<xref ref-type="bibr" rid="ref21">21</xref>], and across different populations (including children, parents, and caregivers). In our prior study, we implemented PEMT on a touch-screen computer in a pediatric emergency department (ED). Children with asthma and their parents used the asthma education program in the ED. The results showed significant improvement in their knowledge and found PEMT to be highly acceptable [<xref ref-type="bibr" rid="ref20">20</xref>]. In another study, we implemented PEMT in an ED and in an inner city outpatient pediatric ambulatory center (PAC) to assess and describe changes in the knowledge, attitudes, and practice regarding the influenza vaccine in participants whose children were between 6 months to 5 years of age [<xref ref-type="bibr" rid="ref21">21</xref>]. The results of the study showed high acceptance of PEMT, and users found PEMT easy to use with no difficulties in navigating from one screen to another [<xref ref-type="bibr" rid="ref21">21</xref>]. Users could interact with the tool on a desktop, laptop, or tablet PC using a touch screen, keyboard, and/or mouse. The system is available as a local or Web-based application.</p>
            </sec>
            <sec>
                <title>PEMT Hardware and Software</title>
                <p>PEMT is implemented in an n-tier architecture, using Adobe Flash CS3 for the presentation layer, XML for content management, Microsoft.Net Framework version 2.0 with Visual Basic.Net for program logic and data flow control, and Microsoft SQL Server 2005 for data storage. Educational content elements&#8212;including text, images, thumbnails, animations, and audio&#8212;and accessibility features&#8212;including textual descriptors and closed captions&#8212;are organized using multiple XML files. The Adobe Flash layer is used to render educational content and user interface controls dynamically. User interactions with the Adobe Flash layer&#8212;including responses to questions and navigational interactions&#8212;are captured by the .Net layer and recorded in a relational structure, linked with timestamps and a unique session identifier in the MS SQL Server database. For heuristic evaluations, the software experts used the software on desktop and laptop computers running Windows XP with a minimum configuration of a Pentium 4 processor and 512MB RAM.</p>
            </sec>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <p> Heuristic evaluation is better if several people conduct the evaluation independent of each other [<xref ref-type="bibr" rid="ref6">6</xref>]. Jacob Nielsen's heuristics are probably the most used usability heuristics for user interface design [<xref ref-type="bibr" rid="ref6">6</xref>]. The evaluation is structured in terms of recognized usability principles.</p>
            <p>The severity of a usability problem is a combination of three factors:</p>
            <list list-type="bullet">
                <list-item>
                    <p>The <bold>frequency</bold> with which the problem occurs: Is it common or rare?</p>
                </list-item>
                <list-item>
                    <p>The <bold>impact</bold> of the problem if it occurs: Will it be easy or difficult for the users to overcome?</p>
                </list-item>
                <list-item>
                    <p>The <bold>persistence</bold> of the problem: Is it a one-time problem that users can overcome once they know about it, or will users repeatedly be bothered by the problem?</p>
                </list-item>
            </list>
            <p>Three usability experts (LD, KP, and LV) used Nielsen&#8217;s usability heuristics (<xref ref-type="table" rid="table1">Table 1</xref>) while reviewing the PEMT user interface and generated a list of heuristic violations. One of the usability experts was a registered nurse with 15 years of clinical and HCI experience and had conducted numerous heuristic evaluation studies (KP). One of the other experts had 12 years of professional experience in usability design and heuristic evaluation (LV), and the third expert was a PhD student in HCI with experience in doing heuristic evaluations for several studies (LD). During the evaluation, the usability experts first reviewed the user interface of PEMT independently and generated a list of heuristic violations. The usability experts then independently rated the severity of each usability violation on the following scale [<xref ref-type="bibr" rid="ref6">6</xref>]:</p>
            <p>0 - I don&#8217;t agree that this is a usability problem at all</p>
            <p>1 - Cosmetic problem only: need not be fixed unless extra time is available on the project</p>
            <p>2 - Minor usability problem: fixing this should be given low priority</p>
            <p>3 - Major usability problem: important to fix, so should be given high priority</p>
            <p>4 - Usability catastrophe: imperative to fix this before product can be released</p>
            <p>In rating the problems, persistent issues with major impact on most users received the highest severity rating. The mean severity for each violation was calculated from the individual ratings. The three independent lists were combined together to generate a single list of heuristics violations, their severity ratings, and suggestions for the correction of these violations. The three usability experts (LD, KP, and LV) discussed their individual lists together, and any disagreements in assigning the severity ratings were resolved after mutual discussions. The combined list of heuristic violations was then reviewed and changes were made.</p>
            <table-wrap id="table1" position="float">
                <label>Table 1</label>
                <caption>
                    <p> Nielsen&#8217;s usability heuristics</p>
                </caption>
                <table width="632" border="1" cellpadding="7" cellspacing="0" rules="groups">
                    <col width="196" />
                    <col width="406" />
                    <thead>
                        <tr>
                            <td>Usability Heuristic</td>
                            <td>Description</td>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td valign="top">1. Visibility of system status</td>
                            <td>The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.</td>
                        </tr>
                        <tr>
                            <td valign="top">2. Match between system and real world</td>
                            <td>The system should speak the users' language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.</td>
                        </tr>
                        <tr>
                            <td valign="top">3. User control and freedom</td>
                            <td>Users often choose system functions by mistake and will need a clearly marked &#34;emergency exit&#34; to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.</td>
                        </tr>
                        <tr>
                            <td valign="top">4. 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>
                            <td valign="top">5. 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>
                            <td valign="top">6. 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 dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.</td>
                        </tr>
                        <tr>
                            <td valign="top">7. Flexibility and efficiency of use</td>
                            <td>Accelerators&#8212;unseen by the novice user&#8212;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>
                            <td valign="top">8. Aesthetic and minimalist design</td>
                            <td>Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.</td>
                        </tr>
                        <tr>
                            <td valign="top">9. Help users recognize, diagnose, and recover from errors</td>
                            <td valign="top">Express error messages in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.</td>
                        </tr>
                        <tr>
                            <td valign="top">10. 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, be focused on the user's task, list concrete steps to be carried out, and not be too large.</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
        </sec>
        <sec sec-type="results">
            <title>Results</title>
            <p>The result of the heuristic evaluation was a combined list of violations with severity ratings. The violations were sorted by heuristic and ordered from most to least severe within each heuristic category. A total of 127 violations were identified with a mean severity of 3 (range 0 - 4). The usability problems pertaining to the system function were organized by individual screens. An excerpt of the evaluation results for the user interface prototype has been presented (<xref ref-type="table" rid="table2">Table 2</xref>). Sample heuristic violations included a &#8220;lack of feedback to the user if they didn&#8217;t answer a question and tried to proceed to the next screen&#8221;, and the &#8220;inability to exit or obtain help throughout the entire program&#8221;.</p>
 <p>The results of the heuristic evaluation were given to the software development team so that the interface could be revised. The domain expert and the software development team discussed these changes and, based on the severity ratings, changes were prioritized and implemented (<xref ref-type="fig" rid="figure1">Figure 1</xref>, <xref ref-type="fig" rid="figure2">Figure 2</xref>, <xref ref-type="fig" rid="figure3">Figure 3</xref>). In <xref ref-type="fig" rid="figure1">Figure 1</xref>, if an option is not selected and the user clicks next to go forward, no feedback is given to the user. No help is provided to assist users during their use of the program, and no exit button is available to leave the program at any time.</p>
            <p>In <xref ref-type="fig" rid="figure2">Figure 2</xref>, feedback is provided if no option is selected, and the user is able to exit anytime during the use of the program.</p>
            <table-wrap id="table2" position="float">
                <label>Table 2</label>
                <caption>
                    <p> Sample heuristic evaluation results</p>
                </caption>
                <table width="632" border="1" cellpadding="7" cellspacing="0" rules="groups">
                    <col width="124" />
                    <col width="226" />
                    <col width="142" />
                    <col width="82" />
                    <thead>
                        <tr>
                            <td>Heuristic violated</td>
                            <td>Problem Description</td>
                            <td>Program Section</td>
                            <td>Severity Rating</td>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td valign="top">Visibility</td>
                            <td>If you don't answer a question and then try to advance, the system will not let you, but it gives you no feedback on how to proceed.</td>
                            <td valign="top">Screening section</td>
                            <td>3</td>
                        </tr>
                        <tr>
                            <td>User control and freedom</td>
                            <td valign="top">No Exit or Quit present.</td>
                            <td valign="top">Entire program</td>
                            <td>3</td>
                        </tr>
                        <tr>
                            <td>Help and documentation</td>
                            <td valign="top">No Help present.</td>
                            <td valign="top">Entire program</td>
                            <td>4</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
            <p />
           
            <p>
                <fig id="figure1" position="float">
                    <label>Figure 1</label>
                    <caption>
                        <p>PEMT Version before heuristic evaluation</p>
                    </caption>
                    <!--Original graphic name: 1244-6535-1-LE_html_m5fd9e937.jpg-->
                    <graphic xlink:href="jmir_v11i4e47_fig1.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
            </p>
            <p>
                <fig id="figure2" position="float">
                    <label>Figure 2</label>
                    <caption>
                        <p>Revised PEMT version after changes were made based on heuristic evaluations</p>
                    </caption>
                    <!--Original graphic name: 1244-6535-1-LE_html_60102f6f.jpg-->
                    <graphic xlink:href="jmir_v11i4e47_fig2.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
            </p>
            <p>
                <fig id="figure3" position="float">
                    <label>Figure 3</label>
                    <caption>
                        <p>Help section is provided during the use of the program in the modified version of PEMT</p>
                    </caption>
                    <!--Original graphic name: 1244-6535-1-LE_html_374674d9.jpg-->
                    <graphic xlink:href="jmir_v11i4e47_fig3.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
            </p>
            <p>
                <xref ref-type="table" rid="table3">Table 3</xref> shows the average number of violations for visibility, the match between system and real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency, aesthetic and minimalist design, help users recognize, diagnose, and recover from errors, and help and documentation. Results showed that among the 10 usability heuristics, the match between system and real world (n = 38) and consistency and standards (n = 34) were the two heuristics most frequently violated. These two heuristics accounted for more than half (57%) of all the violations. Two examples of heuristic violations related to the match between system and real world included: 1) lack of clarity in the presentation of the buttons and their functions and 2) a mismatch between the audio and written content. Consistency and standards heuristic violations included: 1) differences in function performed by similar buttons, including the &#8220;next&#8221; button that was used to display additional content on the same screen instead of to advance screens and 2) inconsistent typesizes and styles used on the same screen.</p>
            <p>We found severity ratings predominantly higher for violations of the usability heuristics &#8220;Help users recognize, diagnose, and recover from errors&#8221; (median rating = 3) and &#8220;Help and documentation&#8221; (median rating = 4) (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
            <p>For four heuristics, more than 50% of the violations were major violations: &#8220;User control and freedom&#8221; (n = 4/6; 66.67%), &#8220;Error prevention&#8221; (n = 6/10; 54.54%), &#8220;Recognition rather than recall&#8221; (n = 1/1; 100%), and &#8220;Help users recognize, diagnose, and recover from errors&#8221; (n = 4/4; 100%) (<xref ref-type="table" rid="table3">Table 3</xref>). The median severity rating per usability heuristic has also been reported (<xref ref-type="table" rid="table3">Table 3</xref>). This information was used to evaluate the severity of the violations in each category of the usability heuristics and was used as a medium to describe not only the average number of severe violations in each category but also to prioritize changes that can be made to the violations.</p>
            <table-wrap id="table3" position="float">
                <label>Table 3</label>
                <caption>
                    <p> Number of violations, average severity rating, and severity category per usability heuristic</p>
                </caption>
                <table width="632" border="1" cellpadding="7" cellspacing="0" rules="groups">
                    <col width="150" />
                    <col width="74" />
                    <col width="66" />
                    <col width="60" />
                    <col width="60" />
                    <col width="76" />
                    <thead>
                        <tr valign="top">
                            <td>Usability heuristic</td>
                            <td>Median severity<break /> rating</td>
                            <td>Cosmetic</td>
                            <td>Minor</td>
                            <td>Major</td>
                            <td>Catastrophic</td>
                        </tr>
                    </thead>
                    <tbody>
                        <tr valign="top">
                            <td>Visibility of system status (n = 13)</td>
                            <td>2</td>
                            <td />
                            <td>7</td>
                            <td>6</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Match between system and real world<break /> (n = 38)</td>
                            <td>2</td>
                            <td>15</td>
                            <td>17</td>
                            <td>6</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>User control and freedom (n = 6)</td>
                            <td>3</td>
                            <td />
                            <td>2</td>
                            <td>4</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Consistency and standards (n = 34)</td>
                            <td>2</td>
                            <td>4</td>
                            <td>24</td>
                            <td>6</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Error prevention<break /> (n = 11)</td>
                            <td>3</td>
                            <td />
                            <td>4</td>
                            <td>6</td>
                            <td>1</td>
                        </tr>
                        <tr valign="top">
                            <td>Recognition rather than recall (n = 1)</td>
                            <td>3</td>
                            <td />
                            <td />
                            <td>1</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Flexibility and efficiency of use<break /> (n = 7)</td>
                            <td>2</td>
                            <td />
                            <td>4</td>
                            <td>3</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Aesthetic and minimalist design<break /> (n = 9)</td>
                            <td>2</td>
                            <td>3</td>
                            <td>6</td>
                            <td />
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Help users recognize, diagnose, and<break /> recover from errors<break /> (n = 4)</td>
                            <td>3</td>
                            <td />
                            <td />
                            <td>4</td>
                            <td />
                        </tr>
                        <tr valign="top">
                            <td>Help and documentation<break />(n = 4)</td>
                            <td>4</td>
                            <td />
                            <td />
                            <td>1</td>
                            <td>3</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
            <p>Based on the feedback from the heuristic evaluations, the user interface of PEMT underwent considerable changes. The majority of the changes that required urgent attention were fixed; however, certain changes were particular to the environment in which the system was to be used which, in this case, was an emergency department setting. The changes immediately made to the system included giving users feedback in the form of a text message when they tried to navigate to the next screen without making a choice. Some of the changes that were recommended by the usability experts were not completely adopted in the revised prototype due to specific user roles and the study protocol. Designers and users are faced with different requirements and tend to focus on different sets of issues. A prior study supports the view that it is not surprising to find experts and end users faced with different requirements focusing on different sets of issues [<xref ref-type="bibr" rid="ref7">7</xref>]. Heuristic evaluation focuses on the interface characteristics mediating between functionality and performance [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
        </sec>
        <sec sec-type="discussion">
            <title>Discussion</title>
            <p> This tutorial illustrates a heuristic evaluation using a computer-based patient education program (PEMT) as a case study. The motivation to conduct this heuristic evaluation was to uncover usability violations in the user interface prototypes of PEMT in an efficient yet effective manner. Our case study illustrates the relevance of the heuristic evaluation for identifying usability problems with computer-based health education programs. We evaluated acceptance of PEMT in the emergency department and the pediatric ambulatory clinic using an attitudinal survey. The results showed that 95% of the users found the program easy to use, 91% found it easy to navigate the program&#8217;s different screens, 94% found the text easy to read, and 93% liked the colors used on the screen [<xref ref-type="bibr" rid="ref21">21</xref>]. Overall, the results of this study suggested high acceptance of PEMT [<xref ref-type="bibr" rid="ref21">21</xref>]. One major weakness in our assessment of heuristic evaluation as a method is that we have no baseline against which to measure our results. Earlier studies suggest that heuristic evaluations detect 40 - 60% of the usability problems an empirical user test would find, and also claim that the types of problems found are roughly comparable [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
            <p>A substantial benefit of heuristic evaluation is that it represents significant savings in time over the duration of a complete empirical user test, both in terms of execution and generation of interface changes for implementation. It has been reported that heuristic evaluations employing 3 - 5 evaluators can identify 60 - 70% of the usability problems in an interface, including many of the major problems, even though it requires less time than other evaluation techniques [<xref ref-type="bibr" rid="ref21">21</xref>]. The current case study demonstrates the significance and relevance of human factors in designing computer-mediated health education programs, especially with respect to improving the acceptance of these systems.</p>
            <p>Heuristic evaluation is a usability inspection method and differs from empirical approaches that rely heavily on user performance data, such as user testing. The study shows the practicality of heuristic evaluation. The results suggest that the application of human-computer interaction design principles to technology-based health education programs can be a quick, relatively efficient way to gather feedback and guidance to improve the interface of a system. The heuristic evaluation results were also a guide during the iterative software development process. The results were presented to the development team, and the recommended changes were implemented. The changes made to the interface were prioritized based on the severity ratings, from catastrophic to cosmetic. The immediate changes made to the program included adding a help mechanism, providing feedback to the users based on their actions, and allowing users to exit the system. Therefore, the sorted list of heuristic violations with severity ratings was very helpful for prioritizing the revisions to PEMT. The recommended changes were easily understood, not only by the software development team, but also by domain experts, since the rationale used to make changes to the system was well justified by the heuristics. The benefits of the recommended changes became evident after the revised software demonstrated higher ease of use and greater ease of navigation, while minimizing errors. Thus, providing software designers with practical feedback in a timely fashion represents a distinct advantage that heuristic evaluation possesses which many other usability engineering methods do not.</p>
            <p>Over the long term, perhaps the most lasting result of the heuristic evaluation concerns more than the specific system tested, since heuristic evaluation also relates to internal organizational development. Heuristic evaluation was another step in this educational process. The experimenters and evaluators learned to use the method and to incorporate the results into subsequent development. A large number of usability problems were identified with a reasonable expenditure of effort. To ensure the success of education programs, information must be delivered in a way that is accessible to and meaningful to users.</p>
            <p>However, there are several limitations of using heuristic evaluation compared to other usability engineering methods. This method relies heavily on the expertise of the usability professionals who conduct the evaluation [<xref ref-type="bibr" rid="ref5">5</xref>]. These experts may lack domain knowledge and could therefore overlook domain-related usability problems [<xref ref-type="bibr" rid="ref5">5</xref>]. One way to overcome this obstacle is to employ evaluators, known as double experts, who possess both usability and domain knowledge [<xref ref-type="bibr" rid="ref5">5</xref>]. In our case study, usability experts, designers, and domain experts worked together on the design and evaluation of the PEMT. It is highly important to have a combination of these experts while evaluating computer-mediated patient education programs in the health care environment, or else there is a risk of producing a mismatch between the system and the real world. Involving professionals with expertise in both computer-mediated education and the health care environment allows for the adjustment of several variables while evaluating the system.</p>
            <p>The PEMT user interface was more consistent with Nielsen&#8217;s usability heuristics after the expert-recommended changes were completed. In our study, we examined the value of heuristic evaluation for improving the usability of PEMT by uncovering heuristic violations in the interface design in a quick, efficient, and cost-effective manner. The ability to identify problems in a timely manner makes this method particularly well suited to the iterative design process. In addition, it is very important that the focus is on users when evaluating the interface design because this can influence the problems identified by the usability experts, as well as how these problems are described and prioritized. The system should speak the user&#8217;s language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms and information, and these words, phrases, and concepts should appear in a natural and logical order. The &#8220;match between system and real world&#8221; means that the system should follow real-world conventions as closely as possible, in order to allow the user to understand how to operate the program.</p>
            <p>We are currently conducting multiple studies to evaluate the usability of PEMT by combining heuristic evaluation and user testing for other patient education programs.</p>
        </sec>
    </body>
    <back>
        <fn-group>
            <fn fn-type="conflict">
                <p>None declared.</p>
                <p />
                <p />
            </fn>
        </fn-group>
        <ref-list>
            <ref id="ref1">
                <label>1</label>
                <!--1. Diefenbach MA, Butz BP. A multimedia interactive education system for prostate cancer patients: development and preliminary evaluation. J Med Internet Res 2004;6(1):e3. PMID: 15111269.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Diefenbach</surname>
                            <given-names>Michael A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Butz</surname>
                            <given-names>Brian P</given-names>
                        </name>
                    </person-group>
                    <article-title>A multimedia interactive education system for prostate cancer patients: development and preliminary evaluation</article-title>
                    <source>J Med Internet Res</source>
                    <year>2004</year>
                    <month>1</month>
                    <day>21</day>
                    <volume>6</volume>
                    <issue>1</issue>
                    <fpage>e3</fpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.jmir.org/2004/1/e3/" ext-link-type="uri" />
                    </comment>
                    <pub-id pub-id-type="medline">15111269</pub-id>
                    <pub-id pub-id-type="doi">10.2196/jmir.6.1.e3</pub-id>
                    <pub-id pub-id-type="pmcid">PMC1550590</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <!-- 2. Hofstetter FT. Multimedia Literacy with Student CD-ROM. 3rd edition. New York, NY: Irwin/McGraw-Hill; 2000.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Hofstetter</surname>
                            <given-names>FT</given-names>
                        </name>
                    </person-group>
                    <source>Multimedia Literacy with Student CD-ROM. 3rd edition</source>
                    <year>2000</year>
                    <publisher-loc>New York, NY</publisher-loc>
                    <publisher-name>Irwin/McGraw-Hill</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <!--3. O&#8217;Grady LA. Consumer e-health education in HIV/AIDS: a pilot study of a Web-based video workshop. BMC Med Inform Decis Mak 2006;Feb 27;6:10. PMID: 16504148.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>O'Grady</surname>
                            <given-names>Laura A</given-names>
                        </name>
                    </person-group>
                    <article-title>Consumer e-health education in HIV/AIDS: a pilot study of a web-based video workshop</article-title>
                    <source>BMC Med Inform Decis Mak</source>
                    <year>2006</year>
                    <volume>6</volume>
                    <issue>1</issue>
                    <fpage>10</fpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.biomedcentral.com/1472-6947/6/10" ext-link-type="uri" />
                    </comment>
                    <pub-id pub-id-type="medline">16504148</pub-id>
                    <pub-id pub-id-type="pii">1472-6947-6-10</pub-id>
                    <pub-id pub-id-type="doi">10.1186/1472-6947-6-10</pub-id>
                    <pub-id pub-id-type="pmcid">PMC1409770</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <!--4. Nielson J. Usability Engineering. San Diego, CA: Academic Press; 1993.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Nielson</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <source>Usability Engineering</source>
                    <year>1993</year>
                    <publisher-loc>San Diego, CA</publisher-loc>
                    <publisher-name>Academic Press</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <!--5. Tang Z, Johnson TR, Tindall RD, Zhang J. Applying heuristic evaluation to improve the usability of a telemedicine system. Telemed J E Health. 2006;Feb;12(1):24-34. PMID: 16478410.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Tang</surname>
                            <given-names>Zhihua</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>Todd R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Tindall</surname>
                            <given-names>R Douglas</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Jiajie</given-names>
                        </name>
                    </person-group>
                    <article-title>Applying heuristic evaluation to improve the usability of a telemedicine system</article-title>
                    <source>Telemed J E Health</source>
                    <year>2006</year>
                    <month>2</month>
                    <volume>12</volume>
                    <issue>1</issue>
                    <fpage>24</fpage>
                    <lpage>34</lpage>
                    <pub-id pub-id-type="medline">16478410</pub-id>
                    <pub-id pub-id-type="doi">10.1089/tmj.2006.12.24</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <!--6. Nielsen J. Heuristic evaluation. In: Nielsen J, Mack RL, editors. Usability Inspection Methods. New York, NY: John Wiley &#38; Sons; 1994.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Nielsen</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <article-title>Heuristic evaluation</article-title>
                    <source>Nielsen J, Mack RL, editors. Usability Inspection Methods</source>
                    <year>1994</year>
                    <publisher-loc>New York, NY</publisher-loc>
                    <publisher-name>John Wiley &#38; Sons</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <!--7. Lathan C, Sebrechts MM, Newman DJ, Doarn CR. Heuristic evaluation of a Web-based interface for Internet telemedicine. Telemed J 1999;5(2);177-185. PMID: 10908430.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Lathan</surname>
                            <given-names>C E</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Sebrechts</surname>
                            <given-names>M M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Newman</surname>
                            <given-names>D J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Doarn</surname>
                            <given-names>C R</given-names>
                        </name>
                    </person-group>
                    <article-title>Heuristic evaluation of a web-based interface for internet telemedicine</article-title>
                    <source>Telemed J</source>
                    <year>1999</year>
                    <volume>5</volume>
                    <issue>2</issue>
                    <fpage>177</fpage>
                    <lpage>85</lpage>
                    <pub-id pub-id-type="medline">10908430</pub-id>
                    <pub-id pub-id-type="doi">10.1089/107830299312140</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <!--8. Kushniruk AW, Patel VL. Cognitive and usability methods for the evaluation of clinical information systems. J Biomed Inform 2004;37:56-76. PMID: 15016386.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Kushniruk</surname>
                            <given-names>Andre W</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Patel</surname>
                            <given-names>Vimla L</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>2</month>
                    <volume>37</volume>
                    <issue>1</issue>
                    <fpage>56</fpage>
                    <lpage>76</lpage>
                    <pub-id pub-id-type="medline">15016386</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.jbi.2004.01.003</pub-id>
                    <pub-id pub-id-type="pii">S1532046404000206</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <!--9. Jeffries R, Miller JR, Wharton C, Uyeda KM. User interface evaluation in the real world: a comparison of four techniques. In: Robertson S, Oslon GM, Oslon JS, editors. Human Factors in Computing Systems CHI&#8217;91 Conference Proceedings. New York, NY: ADM Press; 1991.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Jeffries</surname>
                            <given-names>R</given-names>
                        </name>
                        <name>
                            <surname>Miller</surname>
                            <given-names>JR</given-names>
                        </name>
                        <name>
                            <surname>Wharton</surname>
                            <given-names>C</given-names>
                        </name>
                        <name>
                            <surname>Uyeda</surname>
                            <given-names>KM</given-names>
                        </name>
                    </person-group>
                    <article-title>User interface evaluation in the real world: a comparison of four techniques</article-title>
                    <source>Robertson S, Oslon GM, Oslon JS, editors. Human Factors in Computing Systems CHI&#8217;91 Conference Proceedings</source>
                    <year>1991</year>
                    <publisher-loc>New York, NY</publisher-loc>
                    <publisher-name>ADM Press</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <!--10. Nielson J. Guerilla HCI: using discount usability engineering to penetrate intimidation barrier. In: Bias RG, Mayhew DJ, editors. Cost-Justifying Usability. San Diego, CA: Academic Press; 1994.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Nielson</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <article-title>Guerilla HCI: using discount usability engineering to penetrate intimidation barrier</article-title>
                    <source>Bias RG, Mayhew DJ, editors. Cost-Justifying Usability</source>
                    <year>1994</year>
                    <publisher-loc>San Diego, CA</publisher-loc>
                    <publisher-name>Academic Press</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <!--11. Jaspers MW. A comparison of usability methods for testing interactive health technologies: methodological aspects and empirical evidence. Int J Med Inform 2009;78(5):340-53. PMID: 19046928.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Jaspers</surname>
                            <given-names>Monique W M</given-names>
                        </name>
                    </person-group>
                    <article-title>A comparison of usability methods for testing interactive health technologies: methodological aspects and empirical evidence</article-title>
                    <source>Int J Med Inform</source>
                    <year>2009</year>
                    <month>5</month>
                    <volume>78</volume>
                    <issue>5</issue>
                    <fpage>340</fpage>
                    <lpage>53</lpage>
                    <pub-id pub-id-type="medline">19046928</pub-id>
                    <pub-id pub-id-type="pii">S1386-5056(08)00180-9</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2008.10.002</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <!--12. Tang Z, Johnson TR, Tindall RD, Zhang J. Applying heuristic evaluation to improve the usability of a telemedicine system. Telemed J E Health 2006;12(1):24-34. PMID: 16478410.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Tang</surname>
                            <given-names>Zhihua</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>Todd R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Tindall</surname>
                            <given-names>R Douglas</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Jiajie</given-names>
                        </name>
                    </person-group>
                    <article-title>Applying heuristic evaluation to improve the usability of a telemedicine system</article-title>
                    <source>Telemed J E Health</source>
                    <year>2006</year>
                    <month>2</month>
                    <volume>12</volume>
                    <issue>1</issue>
                    <fpage>24</fpage>
                    <lpage>34</lpage>
                    <pub-id pub-id-type="medline">16478410</pub-id>
                    <pub-id pub-id-type="doi">10.1089/tmj.2006.12.24</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <!--13. Nielson J. Usability evaluation and inspection methods. In: Ashlund S, Mullet K, Henderson A, Hollnagel E, White T, editors. Bridges Between Worlds, INTERCHI&#8217;93 Tutorial Notes 22. Reading, MA: Addison-Wesley; 1993.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Nielson</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <article-title>Usability evaluation and inspection methods</article-title>
                    <source>Ashlund S, Mullet K, Henderson A, Hollnagel E, White T, editors. Bridges Between Worlds, INTERCHI&#8217;93 Tutorial Notes 22</source>
                    <year>1993</year>
                    <publisher-loc>Reading, MA</publisher-loc>
                    <publisher-name>Addison-Wesley</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <!--14. Beuscart-Zephir MC, Watbled L, Carpentier AM, Degroisse M, Alao O. A rapid usability assessment methodology to support the choice of clinical information systems: a case study. Proc AMIA Symp 2002:46-50. PMID: 12463784.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Beuscart-Z&#233;phir</surname>
                            <given-names>M C</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Watbled</surname>
                            <given-names>L</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Carpentier</surname>
                            <given-names>A M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Degroisse</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Alao</surname>
                            <given-names>O</given-names>
                        </name>
                    </person-group>
                    <article-title>A rapid usability assessment methodology to support the choice of clinical information systems: a case study</article-title>
                    <source>Proc AMIA Symp</source>
                    <year>2002</year>
                    <fpage>46</fpage>
                    <lpage>50</lpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&#38;pubmedid=12463784" ext-link-type="uri" />
                    </comment>
                    <pub-id pub-id-type="medline">12463784</pub-id>
                    <pub-id pub-id-type="pii">D020002529</pub-id>
                    <pub-id pub-id-type="pmcid">PMC2244284</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <!--15. Zhang J, Johnson TR, Patel VL, Paige DL, Kubose T. Using usability heuristics to evaluate patient safety of medical devices. J Biomed Inform 2003;36:23-30. PMID: 14552844.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Jiajie</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>Todd R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Patel</surname>
                            <given-names>Vimla L</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Paige</surname>
                            <given-names>Danielle L</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Kubose</surname>
                            <given-names>Tate</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>
                    <pub-id pub-id-type="medline">14552844</pub-id>
                    <pub-id pub-id-type="pii">S1532046403000601</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S1532-0464(03)00060-1</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <!--16. Smith MK. Learning Theory. Source:The Encyclopedia of Informal Education#2003. [Accessed 2009 Oct 26]. <ext-link ext-link-type="uri" xlink:href="http://www.infed.org/biblio/b-learn.htm" xlink:type="simple">http://www.infed.org/biblio/b-learn.htm</ext-link><ext-link ext-link-type="uri" xlink:href="http://www.webcitation.org/5fOKSfZtW" xlink:type="simple">http://www.webcitation.org/5fOKSfZtW</ext-link>-->
                <nlm-citation citation-type="web">
					<person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Smith</surname>
                            <given-names>MK</given-names>
                        </name>
                    </person-group>
                    <source>The Encyclopedia of Informal Education</source>
                    <year>2003</year>
                    <access-date>2009 Oct 26</access-date>
                    <comment>Learning Theory.<ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.infed.org/biblio/b-learn.htm" ext-link-type="uri">http://www.infed.org/biblio/b-learn.htm</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5fOKSfZtW</pub-id>
                </nlm-citation>
                <!-- CORRECTION: Check comment field-->
            </ref>
            <ref id="ref17">
                <label>17</label>
                <!--17. Jezierski J. Learning Styles. Source:Learnativity.com#2003. [Accessed 2009 Oct 30]. <ext-link ext-link-type="uri" xlink:href="http://www.learnativity.com/learningstyles.html" xlink:type="simple">http://www.learnativity.com/learningstyles.html</ext-link><ext-link ext-link-type="uri" xlink:href="http://www.webcitation.org/5kwoTBbNC" xlink:type="simple">http://www.webcitation.org/5kwoTBbNC</ext-link>-->
                <nlm-citation citation-type="web">
					<person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Jezierski</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <source>Learnativity.com</source>
					<year>2003</year>
                    <access-date>2009 Oct 30</access-date>
                    <comment>Learning Styles.<ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.learnativity.com/learningstyles.html" ext-link-type="uri">http://www.learnativity.com/learningstyles.html</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5kwoTBbNC</pub-id>
                </nlm-citation>
                <!-- CORRECTION: Check comment field-->
            </ref>
            <ref id="ref18">
                <label>18</label>
                <!--18. Russell SS. An overview of adult learning processes. Urol Nurs 2006;26(5):349-352, 370. PMID: 17078322.-->
                <nlm-citation citation-type="journal">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Russell</surname>
                            <given-names>SS</given-names>
                        </name>
                    </person-group>
                    <article-title>An overview of adult learning processes</article-title>
                    <source>Urol Nurs</source>
                    <year>2006</year>
                    <volume>26</volume>
                    <issue>5</issue>
                    <fpage>349</fpage>
                    <lpage>352, 370</lpage>
                    <pub-id pub-id-type="medline">17078322</pub-id>
                </nlm-citation>
                <!-- CORRECTION: Check comment field-->
            </ref>
            <ref id="ref19">
                <label>19</label>
                <!--19. Shneiderman B. Designing the User Interface: Strategies for Effective Human-Computer Interaction. Reading, MA: Addison-Wesley; 1998.-->
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Shneiderman</surname>
                            <given-names>B</given-names>
                        </name>
                    </person-group>
                    <source>Designing the User Interface: Strategies for Effective Human-Computer Interaction</source>
                    <year>1998</year>
                    <publisher-loc>Reading, MA</publisher-loc>
                    <publisher-name>Addison-Wesley</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <!--20. Joshi A, Lichenstein R, Rafei K, Bakar A, Arora M. A pilot study to evaluate self-initiated computer patient education in children with acute asthma in pediatric emergency department. Technol Health Care 2007;15(6):433-44. PMID: 18057566.-->
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Joshi</surname>
                            <given-names>Ashish</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Lichenstein</surname>
                            <given-names>Richard</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rafei</surname>
                            <given-names>Keyvan</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bakar</surname>
                            <given-names>Adnan</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Arora</surname>
                            <given-names>Mohit</given-names>
                        </name>
                    </person-group>
                    <article-title>A pilot study to evaluate self initiated computer patient education in children with acute asthma in pediatric emergency department</article-title>
                    <source>Technol Health Care</source>
                    <year>2007</year>
                    <volume>15</volume>
                    <issue>6</issue>
                    <fpage>433</fpage>
                    <lpage>44</lpage>
                    <pub-id pub-id-type="medline">18057566</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <!--21. Joshi A, Lichenstein R, King J, Arora M, Khan S. Evaluation of a Computer-Based Patient Education and Motivation Tool on Knowledge, Attitudes, and Practice Towards Influenza Vaccination. IEJHE 2009;12:1-15.-->
                <nlm-citation citation-type="journal">
                    <person-group person-group-type="author">
                        <name>
                            <surname>Joshi</surname>
                            <given-names>A</given-names>
                        </name>
                        <name>
                            <surname>Lichenstein</surname>
                            <given-names>R</given-names>
                        </name>
                        <name>
                            <surname>King</surname>
                            <given-names>J</given-names>
                        </name>
                        <name>
                            <surname>Arora</surname>
                            <given-names>M</given-names>
                        </name>
                        <name>
                            <surname>Khan</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <article-title>Evaluation of a Computer-Based Patient Education and Motivation Tool on Knowledge, Attitudes, and Practice Towards Influenza Vaccination</article-title>
                    <source>IEJHE</source>
                    <year>2009</year>
                    <volume>12</volume>
                    <fpage>1</fpage>
                    <lpage>15</lpage>
                </nlm-citation>
            </ref>
        </ref-list>
        <glossary>
            <title>Abbreviations</title>
            <def-list>
                <def-item>
                    <term id="abb1">ED</term>
                    <def>
                        <p>emergency department</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb2">HCI</term>
                    <def>
                        <p>human computer interaction</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb3">PAC</term>
                    <def>
                        <p>pediatric ambulatory center</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb4">PEMT</term>
                    <def>
                        <p>Patient Education and Motivation Tool</p>
                    </def>
                </def-item>
            </def-list>
        </glossary>
    </back>
</article>
