<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
    <article-id pub-id-type="publisher-id">v6i11e10666</article-id>
    <article-id pub-id-type="pmid">30467100</article-id>
    <article-id pub-id-type="doi">10.2196/10666</article-id>
    <article-categories>
      <subj-group subj-group-type="heading">
        <subject>Original Paper</subject>
      </subj-group>
      <subj-group subj-group-type="article-type">
        <subject>Original Paper</subject>
      </subj-group>
    </article-categories>
    <title-group>
      <article-title>A Real-Time Autonomous Dashboard for the Emergency Department: 5-Year Case Study</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Dias</surname>
          <given-names>Casimiro</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Randell</surname>
          <given-names>Rebecca</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Franklin</surname>
          <given-names>Amy</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Staib</surname>
          <given-names>Andrew</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Jones</surname>
          <given-names>Josette</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1">
        <name name-style="western">
          <surname>Yoo</surname>
          <given-names>Junsang</given-names>
        </name>
        <degrees>RN</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-2331-7644</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib2">
        <name name-style="western">
          <surname>Jung</surname>
          <given-names>Kwang Yul</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-5688-2581</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib3">
        <name name-style="western">
          <surname>Kim</surname>
          <given-names>Taerim</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-8149-1205</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib4">
        <name name-style="western">
          <surname>Lee</surname>
          <given-names>Taerim</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff3" ref-type="aff">3</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-2831-7715</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib5">
        <name name-style="western">
          <surname>Hwang</surname>
          <given-names>Sung Yeon</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1352-3009</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib6">
        <name name-style="western">
          <surname>Yoon</surname>
          <given-names>Hee</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1297-9813</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib7">
        <name name-style="western">
          <surname>Shin</surname>
          <given-names>Tae Gun</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-9657-1040</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib8">
        <name name-style="western">
          <surname>Sim</surname>
          <given-names>Min Seob</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-6645-3684</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib9">
        <name name-style="western">
          <surname>Jo</surname>
          <given-names>Ik Joon</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-8098-1862</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib10">
        <name name-style="western">
          <surname>Paeng</surname>
          <given-names>Hansol</given-names>
        </name>
        <xref rid="aff4" ref-type="aff">4</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-8645-864X</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib11">
        <name name-style="western">
          <surname>Choi</surname>
          <given-names>Jong Soo</given-names>
        </name>
        <degrees>PhD</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <xref rid="aff5" ref-type="aff">5</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-3108-406X</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib12" corresp="yes">
      <name name-style="western">
        <surname>Cha</surname>
        <given-names>Won Chul</given-names>
      </name>
      <degrees>MD</degrees>
      <xref rid="aff2" ref-type="aff">2</xref>
      <address>
        <institution>Department of Emergency Medicine</institution>
        <institution>Samsung Medical Center</institution>
        <institution>Sungkyunkwan University School of Medicine</institution>
        <addr-line>81, Irwon-ro</addr-line>
        <addr-line>Gangnam-gu</addr-line>
        <addr-line>Seoul, 06351</addr-line>
        <country>Republic of Korea</country>
        <phone>82 2 3410 2053</phone>
        <fax>82 2 3410 0012</fax>
        <email>wc.cha@samsung.com</email>
      </address>  
      <xref rid="aff5" ref-type="aff">5</xref>
      <xref rid="aff6" ref-type="aff">6</xref>
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-2778-2992</ext-link></contrib>
    </contrib-group>
    <aff id="aff1">
    <label>1</label>
    <institution>SAIHST</institution>
    <institution>Department of Digital Health</institution>  
    <institution>Sungkyunkwan University</institution>  
    <addr-line>Seoul</addr-line>
    <country>Republic of Korea</country></aff>
    <aff id="aff2">
    <label>2</label>
    <institution>Department of Emergency Medicine</institution>
    <institution>Samsung Medical Center</institution>  
    <institution>Sungkyunkwan University School of Medicine</institution>  
    <addr-line>Seoul</addr-line>
    <country>Republic of Korea</country></aff>
    <aff id="aff3">
    <label>3</label>
    <institution>Department of Emergency Medicine</institution>  
    <institution>Chamjoeun Hospital</institution>
    
    <addr-line>Gwangju</addr-line>
    <country>Republic of Korea</country></aff>
    <aff id="aff4">
    <label>4</label>
     <institution>Human Understanding Design Center (HUDC)</institution>  
    <institution>Seoul Medical Center</institution>
   
    <addr-line>Seoul</addr-line>
    <country>Republic of Korea</country></aff>
    <aff id="aff5">
    <label>5</label>
    <institution>Health Information Center</institution>
    <institution>Samsung Medical Center</institution>  
    <addr-line>Seoul</addr-line>
    <country>Republic of Korea</country></aff>
    <aff id="aff6">
    <label>6</label>
    <institution>Department of Digital Health</institution>
    <institution>Samsung Advanced Institute of Health Sciences and Technology</institution>  
    <institution>Sungkyunkwan University</institution>  
    <addr-line>Seoul</addr-line>
    <country>Republic of Korea</country></aff>
    <author-notes>
      <corresp>Corresponding Author: Won Chul Cha 
      <email>wc.cha@samsung.com</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><month>11</month><year>2018</year></pub-date>
    <pub-date pub-type="epub">
      <day>22</day>
      <month>11</month>
      <year>2018</year>
    </pub-date>
    <volume>6</volume>
    <issue>11</issue>
    <elocation-id>e10666</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>2</day>
        <month>4</month>
        <year>2018</year>
      </date>
      <date date-type="rev-request">
        <day>14</day>
        <month>5</month>
        <year>2018</year>
      </date>
      <date date-type="rev-recd">
        <day>2</day>
        <month>7</month>
        <year>2018</year>
      </date>
      <date date-type="accepted">
        <day>10</day>
        <month>8</month>
        <year>2018</year>
      </date>
    </history>
    <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
    <copyright-statement>©Junsang Yoo, Kwang Yul Jung, Taerim Kim, Taerim Lee, Sung Yeon Hwang, Hee Yoon, Tae Gun Shin, Min Seob Sim, Ik Joon Jo, Hansol Paeng, Jong Soo Choi, Won Chul Cha. Originally published in JMIR Mhealth and Uhealth (http://mhealth.jmir.org), 22.11.2018.</copyright-statement>
    <copyright-year>2018</copyright-year>
    <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
      <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mhealth and uhealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://mhealth.jmir.org/2018/11/e10666/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>The task of monitoring and managing the entire emergency department (ED) is becoming more important due to increasing pressure on the ED. Recently, dashboards have received the spotlight as health information technology to support these tasks.</p>
      </sec>
      <sec sec-type="objective">
        <title>Objective</title>
        <p>This study aimed to describe the development of a real-time autonomous dashboard for the ED and to evaluate perspectives of clinical staff on its usability.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>We developed a dashboard based on three principles—“anytime, anywhere, at a glance;” “minimal interruption to workflow;” and “protect patient privacy”—and 3 design features—“geographical layout,” “patient-level alert,” and “real-time summary data.” Items to evaluate the dashboard were selected based on the throughput factor of the conceptual model of ED crowding. Moreover, ED physicians and nurses were surveyed using the system usability scale (SUS) and situation awareness index as well as a questionnaire we created on the basis of the construct of the Situation Awareness Rating Technique.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>The first version of the ED dashboard was successfully launched in 2013, and it has undergone 3 major revisions since then because of geographical changes in ED and modifications to improve usability. A total of 52 ED staff members participated in the survey. The average SUS score of the dashboard was 67.6 points, which indicates “OK-to-Good” usability. The participants also reported that the dashboard provided efficient “concentration support” (4.15 points), “complexity representation” (4.02 points), “variability representation” (3.96 points), “information quality” (3.94 points), and “familiarity” (3.94 points). However, the “division of attention” was rated at 2.25 points.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>We developed a real-time autonomous ED dashboard and successfully used it for 5 years with good evaluation from users.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>dashboard</kwd>
      <kwd>development</kwd>
      <kwd>emergency department</kwd>
      <kwd>evaluation</kwd>
      <kwd>health information technology</kwd>
      <kwd>situation awareness</kwd>
      <kwd>usability</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>An emergency department (ED) is a complex system designed to treat patients with various conditions simultaneously. Even though ED providers try to triage patients according to their clinical needs while managing scarce resources, these activities are often overwhelmed by the complexity and large volume of data. Emergency physicians are required to treat multiple patients while maintaining situational awareness of the ED surroundings [<xref ref-type="bibr" rid="ref1">1</xref>]. This task is very challenging because it requires acquisition, processing, integration, and archiving of large data at multiple levels [<xref ref-type="bibr" rid="ref2">2</xref>]. Thus, physicians frequently feel like they are losing control over the ED, which aggravates burnout and affects performance [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>].</p>
      <p>Moreover, many EDs are already overcrowded, thus increasing the complexity [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. While ED overcrowding remains a major health care issue, it significantly and adversely affects quality of care by influencing major quality factors, such as timeliness, effectiveness, efficiency, safety, and patient-centeredness, resulting in increased mortality and morbidity [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Multiple studies have suggested the use of system engineering and science to improve ED performance, streamline the process, and improve the throughput [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. However, a strategic approach to identify process delays and supply-demand mismatch using traditional hospital information systems (HISs) is not feasible. It is important to monitor and manage the ED as a whole.</p>
      <p>The dashboard is “a visual display of the most important information needed to achieve one or more objectives” [<xref ref-type="bibr" rid="ref14">14</xref>]. Because the situation in the ED affects the quality of care and patient outcomes, clinicians use different diagnostic and treatment strategies depending on the situation [<xref ref-type="bibr" rid="ref15">15</xref>]. Therefore, recognizing the correct situation is becoming increasingly important to emergency medical clinicians [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
      <p>While a quality dashboard helps decision making at the organization level, a clinical dashboard helps decision making regarding patient care [<xref ref-type="bibr" rid="ref17">17</xref>]. A dashboard that fits the changing situations in the ED in the real time must have the characteristics of both quality and clinical dashboards [<xref ref-type="bibr" rid="ref17">17</xref>]. Recent studies on the ED dashboard system have reported its potential to improve patient safety, situation awareness, and workflow [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref18">18</xref>], but such studies have not addressed long-term experiences and association between the introduction of the dashboard and mental workload of the users. In particular, ensuring real-time availability is challenging and important because nonreal–time dashboards cannot support decision making [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>This study aimed to describe the development of a real-time organizational dashboard for the ED and to evaluate its usability.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>This study was approved by the Institutional Review Board of the study site (Institutional Review Board File #SMC 2018-01-040-001).</p>
      <sec>
        <title>Study Setting</title>
        <p>The study was carried out in a metropolis: Seoul. It was undertaken at an ED with an annual visit volume of 79,000 patients in a tertiary teaching hospital. The hospital has about 2000 inpatient beds. This ED is one of the most overcrowded EDs in the country [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>The HIS was in use in this ED since 1994, supported by electronic medical records and a picture archiving and communication system. Although the history of this HIS is long and its technical quality was one of the most advanced in the country, no ED-specific dashboard system was ever used in this hospital.</p>
      </sec>
      <sec>
        <title>Development</title>
        <sec>
          <title>The Happinovation and the Happy Emergency Room Team</title>
          <p>In 2012, an institution-wide project, the “Happinovation” (Happy innovation), was initiated to enhance patient and provider happiness through process and hardware innovations. The “Happy Emergency Room Team” was formed as a satellite team for the overall project. The team focused on visualizing the ED process for providers and patients.</p>
          <p>Specifically, 2 subprojects were implemented. One was a visualization project for providers—an electronic dashboard to develop visualization of ED performance status on wall-mounted monitors and PCs. The other was a visualization project for patients and their families—a wall-mounted electronic dashboard, kiosks, and tablets.</p>
          <p>The multidisciplinary Happy Emergency Room Team included 6 physicians, 4 nurses, 1 administrator, 2 quality improvement team members, 2 consultants, and 2 designers. While hospital staff provided inputs, consultants and designers tried to see things from patients’ perspective, thus balancing the conclusion. Several rounds of discussions and debates took place before the first dashboard principle and design feature was created.</p>
        </sec>
        <sec>
          <title>Dashboard Principle</title>
          <p>The team had agreed on the following 3 dashboard principles that define the characteristics of the dashboard.</p>
          <sec>
            <title>Anytime, Anywhere, at a Glance</title>
            <p>The dashboard was designed to be like a traditional whiteboard for the ED, which means that it should be mounted on a wall and be visible to providers from about 2-5 m away. It should be in a static mode, without flipping the screen, such that providers would not waste any time to find the desired information [<xref ref-type="bibr" rid="ref20">20</xref>]. Since multiple providers should be able to access the information, interactivity was not feasible. We did not include a writing and communication function from the dashboard because it was designed to only offer providers the overall ED status at a glance [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
          </sec>
          <sec>
            <title>Minimal Interruption to Workflow</title>
            <p>The dashboard should be integrated with the clinical workflow. An unfavorable clinical workflow often changes after implementing health information technology [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>]. However, the Happy Emergency Room Team worried that the dashboard could be a source of botheration. Therefore, we designed it such that it would not require any additional inputs. This means that all data should come from the legacy system.</p>
            <fig id="figure1" position="float">
              <label>Figure 1</label>
              <caption>
                <p>Geographical layout of the emergency department.</p>
              </caption>
              <graphic xlink:href="mhealth_v6i11e10666_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
            <p>All information on the dashboard is automatically generated from previous columns of HIS. For example, the moment at which a physician’s order or barcode of a clinical sample is input by a nurse, it is linked to the dashboard system such that the whole operating process could be automatically marked and shown without additional inputting processes. This is also different from traditional dry-erase whiteboards [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          </sec>
          <sec>
            <title>Protect Patient Privacy</title>
            <p>It is important that patients’ privacy be secured [<xref ref-type="bibr" rid="ref25">25</xref>]. Because the screen is physically accessible to patients and families, most information should be deidentified and symbolized to prevent unnecessary misunderstandings and debates.</p>
          </sec>
        </sec>
        <sec>
          <title>Design Features</title>
          <p>The team adopted the following 3 design features for the dashboard:</p>
          <sec>
            <title>Geographical Layout</title>
            <p>The dashboard should indicate the ED floor plan. A geographical layout would give intuitive information to ED providers on what is going on where in the ED. It is also very common that ED providers recognize and communicate about patients with their bed locations and not with their numbers or names, which made it more intuitive and effective to use a geographical layout rather than a patient list (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p>
          </sec>
          <sec>
            <title>Patient-Level Alert</title>
            <p>All beds and chairs were symbolized to stand for a patient to provide patient-specific information to ED clinicians. Additional patient-level information was included to provide a real-time alert to providers through encoded colors and symbols, especially regarding process delays. The main objective of this concept was to provide ED staff with patient-level alerts such that a provider could immediately notice delays in catering to patients.</p>
          </sec>
          <sec>
            <title>Real-Time Summary Data</title>
            <p>The dashboard would show summary statistics regarding ED performance in the real time. While in-depth information for each patient is available in the pre-existing HIS, a real-time summary depends mostly on subjective feeling of individual providers, which varies significantly due to the lack of information on summary information over ED state. With summary data, providers would be able to reschedule clinical processes for their patients’ efficient journey. For example, a nurse could direct a patient to the X-ray if there is a long queue for a co-ordered computed tomography.</p>
          </sec>
        </sec>
        <sec>
          <title>Prototyping</title>
          <p>Initially, multiple measures were suggested for the dashboard. Measures were chosen and categorized based on a “conceptual model of ED crowding.” The model consisted of 3 factors, among which the throughput factors, which reflect the internal process of ED care, were mostly demonstrated with the dashboard [<xref ref-type="bibr" rid="ref13">13</xref>]. Among input factors, which are components that contribute to the demand for ED services, patient severity and measure of visits were included. Cautions on infection information were also included since they were well correlated with severity and patient allocation within the ED and hospital. Throughput factors were divided into 2 sections: structures and functions. Output factors, such as boarding and discharge data, were also included. Boarding pertains to the inability to admit a patient to a ward due to the lack of inpatient beds even through the patient is determined to be admitted.</p>
          <p>We used a Windows server as the ED visualization platform to support various devices in the ED, including the dashboard and kiosks for patients and mobile devices. Our entire platform was developed and deployed on 2 Windows 2008 servers, each with a 1200-GB hard drive and 20-GB memory, and 2 4-core Intel Xeon 2.4 GHz processors. The servers queried the measurements mentioned above from the electronic medical records and picture archiving and communication system servers. A Windows communication foundation was used as a visualization tool (<xref ref-type="fig" rid="figure2">Figure 2</xref>).</p>
        </sec>
        <sec>
          <title>Evolution of the Emergency Department Dashboard</title>
          <p>We developed and updated the dashboard over 5 years. During the observation, the ED had gone through a Middle East Respiratory Syndrome outbreak, followed by a major structural and functional renovation [<xref ref-type="bibr" rid="ref26">26</xref>]. The ED dashboard adopted such changes and evolved through the process.</p>
        </sec>
      </sec>
      <sec>
        <title>Evaluation</title>
        <sec>
          <title>Selection of Participants</title>
          <p>Inclusion criteria were those currently working as ED physicians and triage or charge nurses and those using the dashboard. Participants were recruited from January 1 to February 10, 2018.</p>
        </sec>
        <sec>
          <title>Intervention</title>
          <p>Participants responded to 20 questions on a 5-point Likert scale after completing a consent form. The first 10 items of the questionnaire were derived from the system usability scale (SUS) to investigate the usability of the dashboard [<xref ref-type="bibr" rid="ref27">27</xref>]. The last 10 items were derived from the situation awareness index (SAI), which we composed based on the Situation Awareness Rating Technique (SART) [<xref ref-type="bibr" rid="ref28">28</xref>]. The SAI aimed to assess whether ED physicians and nurses were using the dashboard to help them recognize the situation. The SAI includes the constructs of the SART as a whole, and small modifications were made to adjust it to fit the dashboard.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Transfer of electronic medical record (EMR) and picture archiving and communication system (PACS) data to the emergency department (ED) visual architecture platform. LAN: Local Area Network.</p>
            </caption>
            <graphic xlink:href="mhealth_v6i11e10666_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>After completing the questionnaire, the participants received about US $8 as compensation for participating in the survey.</p>
        </sec>
        <sec>
          <title>Outcome Analysis</title>
          <p>The SUS scores were interpreted using an adjective rating scale [<xref ref-type="bibr" rid="ref29">29</xref>].</p>
          <p>The SAI score was calculated using the following formula:</p>
          <disp-formula>SAI = {Q11 + Q12 + Q13 + Q14 + Q15 + Q16 + (6 - Q17) + Q18 + Q19 + Q20} / 10, where Q: question number.</disp-formula>
          <p>The SAI scores were also examined using descriptive analyses.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Design and Structure</title>
        <sec>
          <title>Introduction to the First Version of the Emergency Department Dashboard</title>
          <p>The semicircle-shaped indicator in the upper central area represents the complexity of the ED and presents the expected mean length of stay of a current patient in the ED. The semicircle borrows the scheme of the traffic light so that the user intuitively grasps the current situation of the ED.</p>
          <p>A semitransparent colored square represents each section of the ED and matches the geographical layout presented in <xref ref-type="fig" rid="figure1">Figure 1</xref>. The squares are not visible on the actual dashboard. Small icons, such as that shown in the red circle, indicate patients, and they intuitively inform the user about the patient’s journey through the color corresponding to the patient’s process on the left.</p>
          <p>The left side of the dashboard presents a summary of the patient process. This information allows the physician to set up a patient diagnosis strategy and the nurse to determine the order of various tests. The central area of the dashboard reflects the geographical layout of the ED. Here, individual patients’ specific information is displayed, such as real-time clinical processes. The right side of the dashboard presents the number of patients by zone, thereby enabling efficient distribution of medical labor (<xref ref-type="fig" rid="figure3">Figure 3</xref>).</p>
        </sec>
        <sec>
          <title>Evolution of the Emergency Department Dashboard</title>
          <p>Major difference between versions 1 and 2 of the dashboard is that the latter reflects a geographical change. In 2015, the ED of the study site underwent a Middle East Respiratory Syndrome outbreak, and a respiratory isolation area was established and operated. This structural change to the ED was reflected on the dashboard (<xref ref-type="fig" rid="figure4">Figure 4</xref>).</p>
          <p>In version 3, a revision was made to improve usability. We updated the dashboard to change the overall color coding. By doing so, we were able to reflect the users’ suggestions, such as “difficulty to identify bed status” (<xref ref-type="fig" rid="figure4">Figure 4</xref>).</p>
          <p>A major change in version 4 is the improvement of patient-specific information.</p>
          <p>The circle next to the patient indicates the mapping of the Korean Triage and Acuity Scale score from 1 to 5, presented from red to green. Additionally, the rectangle next to the patient reflects “infection caution,” such as “air caution” and “blood caution” (<xref ref-type="fig" rid="figure4">Figure 4</xref>).</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>The first version of the emergency department dashboard.</p>
            </caption>
            <graphic xlink:href="mhealth_v6i11e10666_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Evolution of the emergency department dashboard, showing the second, third, and final versions.</p>
            </caption>
            <graphic xlink:href="mhealth_v6i11e10666_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Evaluation</title>
        <sec>
          <title>Participant Characteristics</title>
          <p>A total of 52 participants were recruited; 25 were physicians and 27 were nurses. In the physician group, 17 were males and 8 were females; in the nurse group, only 2 were males and 25 were females. The participants’ years of experience also varied; 8 had worked for less than 3 years, 10 had worked for 3-5 years, 19 had worked for 5-10 years, and 15 had worked for over 10 years (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        </sec>
        <sec>
          <title>System Usability Scale</title>
          <p>The SUS score of the ED dashboard system was 67.6 points (<xref ref-type="table" rid="table2">Table 2</xref>). The SUS score showed a slight difference between the 2 groups; the physician and nurse groups had scores of 67.5 and 67.69 points, respectively. We could interpret our result as follows: acceptability of the dashboard was “marginally high,” and the adjective rating was “OK-to-Good” [<xref ref-type="bibr" rid="ref29">29</xref>]. These findings indicate that the participants used it very frequently. They also felt that this system was easy to learn and use.</p>
        </sec>
        <sec>
          <title>Situation Awareness Index</title>
          <p>The overall SAI score was 3.87 points, and the score of the physician group (3.95) was higher than that of the nurse group (3.80). The top 5 rated items were “concentration support” (4.15), “complexity representation” (4.02 points), “variability representation” (3.96 points), “information quality provided” (3.94 points), and “familiarity of dashboard” (3.94 points). However, the score for “division of attention” was 2.25 points (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Characteristics of participants.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="220"/>
              <col width="250"/>
              <col width="250"/>
              <col width="250"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Characteristic</td>
                  <td>Physician (n=25)</td>
                  <td>Nurse (n=27)</td>
                  <td>Total (N=52)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="5"><bold>Age group, n (%)</bold></td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>20s</td>
                  <td>2 (8)</td>
                  <td>6 (22)</td>
                  <td>8 (15)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>30s</td>
                  <td>19 (76)</td>
                  <td>19 (70)</td>
                  <td>38 (73)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>40s</td>
                  <td>1 (4)</td>
                  <td>2 (7)</td>
                  <td>3 (6)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>50s</td>
                  <td>3 (12)</td>
                  <td>0 (0)</td>
                  <td>3 (6)</td>
                </tr>
                <tr valign="top">
                  <td colspan="5"><bold>Sex, n (%)</bold></td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>Male</td>
                  <td>17 (68)</td>
                  <td>2 (7)</td>
                  <td>19 (37)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>Female</td>
                  <td>8 (32)</td>
                  <td>25 (93)</td>
                  <td>33 (64)</td>
                </tr>
                <tr valign="top">
                  <td colspan="5"><bold>Years of experience, n (%)</bold></td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>0-3</td>
                  <td>8 (32)</td>
                  <td>0 (0)</td>
                  <td>8 (15)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>3-5</td>
                  <td>6 (24)</td>
                  <td>4 (15)</td>
                  <td>10 (19)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>5-10</td>
                  <td>4 (16)</td>
                  <td>15 (56)</td>
                  <td>19 (37)</td>
                </tr>
                <tr valign="top">
                  <td><break/></td>
                  <td>&#62;10</td>
                  <td>7 (28)</td>
                  <td>8 (30)</td>
                  <td>15 (29)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>System usability scale scores.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="540"/>
              <col width="170"/>
              <col width="150"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td>Item</td>
                  <td>Physician, mean (SD)</td>
                  <td>Nurse, mean (SD)</td>
                  <td>Total, mean (SD)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Q1. I think that I would like to use this dashboard frequently.</td>
                  <td>4.52 (0.7)</td>
                  <td>4.15 (0.5)</td>
                  <td>4.33 (0.6)</td>
                </tr>
                <tr valign="top">
                  <td>Q2. I found the dashboard unnecessarily complex.</td>
                  <td>2.44 (0.9)</td>
                  <td>2.52 (1.0)</td>
                  <td>2.48 (0.9)</td>
                </tr>
                <tr valign="top">
                  <td>Q3. I thought the dashboard was easy to use.</td>
                  <td>3.76 (0.7)</td>
                  <td>3.85 (0.6)</td>
                  <td>3.81 (0.7)</td>
                </tr>
                <tr valign="top">
                  <td>Q4. I think that I would need the support of a technician to be able to use this dashboard.</td>
                  <td>3.08 (1.1)</td>
                  <td>2.89 (1.1)</td>
                  <td>2.98 (1.1)</td>
                </tr>
                <tr valign="top">
                  <td>Q5. I found that the various functions in this dashboard were well integrated.</td>
                  <td>3.56 (0.8)</td>
                  <td>3.78 (0.7)</td>
                  <td>3.67 (0.7)</td>
                </tr>
                <tr valign="top">
                  <td>Q6. I thought there was too much inconsistency in this dashboard.</td>
                  <td>2.24 (0.9)</td>
                  <td>2.07 (0.7)</td>
                  <td>2.15 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Q7. I would imagine that most people would learn to use this dashboard very quickly.</td>
                  <td>3.72 (0.9)</td>
                  <td>3.93 (0.6)</td>
                  <td>3.83 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Q8. I found the dashboard very cumbersome to use.</td>
                  <td>2.12 (0.7)</td>
                  <td>2.11 (0.6)</td>
                  <td>2.12 (0.7)</td>
                </tr>
                <tr valign="top">
                  <td>Q9. I felt very confident using the dashboard.</td>
                  <td>3.84 (0.9)</td>
                  <td>3.67 (0.8)</td>
                  <td>3.75 (0.9)</td>
                </tr>
                <tr valign="top">
                  <td>Q10. I needed to learn a lot of things before I could get going with this dashboard.</td>
                  <td>2.52 (1.1)</td>
                  <td>2.70 (1.1)</td>
                  <td>2.62 (1.1)</td>
                </tr>
                <tr valign="top">
                  <td>System usability scale score</td>
                  <td>67.50 (12.0)</td>
                  <td>67.69 (11.0)</td>
                  <td>67.60 (11.4)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Situation awareness and dashboard results.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="220"/>
              <col width="320"/>
              <col width="170"/>
              <col width="150"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td>Construct</td>
                  <td>Item</td>
                  <td>Physician, mean (SD)</td>
                  <td>Nurse, mean (SD)</td>
                  <td>Total, mean (SD)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Instability representation</td>
                  <td>Q11. The dashboard adequately represents the instability of the ED<sup>a</sup>.</td>
                  <td>3.96 (1.0)</td>
                  <td>3.78 (0.7)</td>
                  <td>3.87 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Complexity representation</td>
                  <td>Q12. The dashboard adequately represents the complexity of the ED.</td>
                  <td>4.12 (0.9)</td>
                  <td>3.93 (0.6)</td>
                  <td>4.02 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Variability representation</td>
                  <td>Q13. The dashboard contains key elements that are changing in the ED.</td>
                  <td>4.08 (0.6)</td>
                  <td>3.85 (0.8)</td>
                  <td>3.96 (0.7)</td>
                </tr>
                <tr valign="top">
                  <td>Arousal support</td>
                  <td>Q14. The dashboard helps me be alert and clearer.</td>
                  <td>3.92 (0.9)</td>
                  <td>3.74 (0.7)</td>
                  <td>3.83 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Concentration support</td>
                  <td>Q15. The dashboard helps me focus on the situation in the ED.</td>
                  <td>4.20 (0.6)</td>
                  <td>4.11 (0.6)</td>
                  <td>4.15 (0.6)</td>
                </tr>
                <tr valign="top">
                  <td>Spare mental capacity support</td>
                  <td>Q16. I can acquire additional mental capacity in a pressing ED situation.</td>
                  <td>3.60 (1.2)</td>
                  <td>3.48 (0.9)</td>
                  <td>3.54 (1.0)</td>
                </tr>
                <tr valign="top">
                  <td>Division of attention</td>
                  <td>Q17. The dashboard distracts attention from important tasks of the ED.</td>
                  <td>2.12 (0.7)</td>
                  <td>2.37 (0.9)</td>
                  <td>2.25 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Information quantity provided</td>
                  <td>Q18. The quantity of information provided by the dashboard is appropriate for performing ED tasks.</td>
                  <td>3.84 (0.9)</td>
                  <td>3.67 (0.8)</td>
                  <td>3.75 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Information quality provided</td>
                  <td>Q19. The quality of information provided by the dashboard is appropriate for performing ED tasks.</td>
                  <td>3.92 (1.0)</td>
                  <td>3.96 (0.6)</td>
                  <td>3.94 (0.8)</td>
                </tr>
                <tr valign="top">
                  <td>Familiarity of dashboard</td>
                  <td>Q20. I can perform ED tasks more proficiently using the dashboard.</td>
                  <td>4.00 (0.9)</td>
                  <td>3.89 (0.8)</td>
                  <td>3.94 (0.9)</td>
                </tr>
                <tr valign="top">
                  <td>Situation awareness index</td>
                  <td>—</td>
                  <td>3.95 (0.6)</td>
                  <td>3.80 (0.5)</td>
                  <td>3.87 (0.6)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>ED: emergency department.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The ED dashboard was successfully developed and implemented. The system is independent of manual input and is fully connected to the legacy HIS. The graphical and statistical concepts were determined during the developmental period, and they were upgraded gradually. Though clinical dashboards for EDs have been developed in other studies [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref32">32</xref>], this study is the first to examine its long-term use and conduct serial upgrades.</p>
        <p>We used SUS, a formal, highly validated usability test, and obtained a score of 67.6 points from physicians and nurses. This score could be interpreted as indicating “marginally high acceptability” with “OK-to-Good usability.” Additionally, the ED staff responded that the dashboard presented the situation in the ED effectively and that they could better focus on the changing situation in the ED by using it. The quality of the information provided by the dashboard was rated high; however, the quantity of information was rated relatively low. There is a need for a systematic investigation to establish the information that ED staff seek and a subsequent improvement plan to reflect the same in the system.</p>
      </sec>
      <sec>
        <title>Clinical Aspects</title>
        <p>It has been one of the major responsibilities of ED staff to keep patients’ processes on track and ensure timely results [<xref ref-type="bibr" rid="ref33">33</xref>]. To do so, ED providers had to call numerous departments and browse through multiple windows repeatedly during their duty time. As the tasks and volume of ED work-ups grew, this timekeeping function had become significantly heavy. The ED dashboard described in this study focused on providing a visual representation of this “hidden” information pertaining to the ED process, such that ED providers could plan and carry out their tasks proactively.</p>
        <p>The visualized information not only pertained to individual patients’ processes but also reported the department’s performance status. As the government and insurance companies focus on performance as a group of patients, it has become an essential job for the system administrator to be able to assess real-time statistics. ED providers’ responsibility as administrators demands tools like our dashboard during their work.</p>
        <p>Our ED dashboard affects the workflow of various medical personnel in the ED in a variety of ways, ranging from simple information delivery to clinical decision-making support. If the dashboard indicates that the ED is extremely overcrowded, the ED chief could contact the national acute care system to control the transfer of new patients. Additionally, physicians could grasp the timely information of each patient using this dashboard. The charge nurse could improve the efficacy of the ED by reassigning each nurse to more appropriate zones based on the information obtained from the dashboard. Triage nurses could also use the dashboard to allocate patients to appropriate treatment zones.</p>
      </sec>
      <sec>
        <title>Comparison With Previous Work</title>
        <p>Recent review articles have indicated that an ED dashboard could be useful for “saving time and reducing the risk of errors or delay” [<xref ref-type="bibr" rid="ref18">18</xref>]. However, the association between the introduction of an electronic dashboard and the mental workload of ED staff is controversial. Further, there is little evidence to support that it improves clinical outcomes [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>A major difference between our system and other electronic boards is that our dashboard does not allow manual or direct input of patient-specific information. We have fully synchronized our dashboard with the legacy system such that physicians’ and nurses’ additional inputs are not required to use the dashboard. By achieving this goal, our system was found to provide effective arousal support, concentration support, and spare mental capacity (3.83 points, 4.15 points, and 3.54 points, respectively) even in the busy clinical setting.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>First, this is a single-center case study with its unique HIS. Its feasibility and usability should be validated in other institutions. Considering that the implementation of this system in other institutions has been discussed, subsequent investigation on ED dashboard utilization is expected in the near future.</p>
        <p>The measures used for the dashboard are not universally agreed upon. They have mainly been used in a highly crowded EDs of a teaching hospital. When used in smaller EDs, the measures of interest would be different. Additionally, the measures were not compared with the national standard, which requires further research.</p>
        <p>The SAI has not been validated. We searched for questionnaires to investigate the association between dashboards and situation awareness, but we could not find any that suited our purpose. Therefore, we developed a questionnaire based on the SART and applied it in this study. However, this questionnaire is not validated, and therefore, its interpretation value is limited.</p>
        <p>Finally, we could not investigate the association between the effectiveness of the ED dashboard and clinical outcomes. However, it is difficult to identify this association because the ED is one of the most complex systems affected by several uncontrollable factors. Therefore, multicenter comparative studies need to be conducted to examine this association.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>We developed a real-time autonomous ED dashboard and successfully used it for 5 years. ED physicians and nurses rated the usability of the ED dashboard as “OK-to-Good.” We realize that continuous maintenance is important because the dashboard should reflect the situation of the ED.</p>
      </sec>
    </sec>
  </body>
  <back>
    <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">HIS</term>
          <def>
            <p>hospital information system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">LAN</term>
          <def>
            <p>Local Area Network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">SAI</term>
          <def>
            <p>situation awareness index</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">SART</term>
          <def>
            <p>Situation Awareness Rating Technique</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">SUS</term>
          <def>
            <p>system usability scale</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors acknowledge the members of the Department of Quality Improvement and of the Health Information Center for their contribution to the design and development of the emergency department dashboard. This research was supported by Basic Science Research Program through the National Research Foundation of Korea and funded by the Ministry of Education (Grant #2017R1D1A1B03034690).</p>
    </ack>
    <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>Endsley</surname>
            <given-names>MR</given-names>
          </name>
        </person-group>
        <article-title>Toward a Theory of Situation Awareness in Dynamic Systems</article-title>
        <source>hum factors</source>  
        <year>1995</year>  
        <month>03</month>  
        <day>01</day>  
        <volume>37</volume>  
        <issue>1</issue>  
        <fpage>32</fpage>  
        <lpage>64</lpage>  
        <pub-id pub-id-type="doi">10.1518/001872095779049543</pub-id></nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wickens</surname>
            <given-names>CD</given-names>
          </name>
        </person-group>
        <article-title>Situation Awareness and Workload in Aviation</article-title>
        <source>Curr Dir Psychol Sci</source>  
        <year>2016</year>  
        <month>06</month>  
        <day>24</day>  
        <volume>11</volume>  
        <issue>4</issue>  
        <fpage>128</fpage>  
        <lpage>133</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://journals.sagepub.com/doi/abs/10.1111/1467-8721.00184"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1111/1467-8721.00184</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
        <name name-style="western">
        <surname>De Stefano</surname>  
        <given-names>Carla</given-names></name>  
        <name name-style="western">
        <surname>Philippon</surname>  
        <given-names>A</given-names></name>  
        <name name-style="western">
        <surname>Krastinova</surname>  
        <given-names>E</given-names></name>  
        <name name-style="western">
        <surname>Hausfater</surname>  
        <given-names>P</given-names></name>  
        <name name-style="western">
        <surname>Riou</surname>  
        <given-names>B</given-names></name>  
        <name name-style="western">
        <surname>Adnet</surname>  
        <given-names>F</given-names></name>  
        <name name-style="western">
        <surname>Freund</surname>  
        <given-names>Y</given-names></name> </person-group>
        <article-title>Effect of emergency physician burnout on patient waiting times</article-title>
        <source>Intern Emerg Med</source>  
        <year>2018</year>  
        <month>12</month>  
        <volume>13</volume>  
        <issue>3</issue>  
        <fpage>421</fpage>  
        <lpage>428</lpage>  
        <pub-id pub-id-type="doi">10.1007/s11739-017-1706-9</pub-id>
        <pub-id pub-id-type="medline">28677043</pub-id>
        <pub-id pub-id-type="pii">10.1007/s11739-017-1706-9</pub-id></nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Garrouste-Orgeas</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Perrin</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Soufir</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Vesin</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Blot</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Maxime</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Beuret</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Troch&#38;eacute;</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Klouche</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Argaud</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Azoulay</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Timsit</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>The Iatroref study: medical errors are associated with symptoms of depression in ICU staff but not burnout or safety culture</article-title>
        <source>Intensive Care Med</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>41</volume>  
        <issue>2</issue>  
        <fpage>273</fpage>  
        <lpage>84</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1007/s00134-014-3601-4"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s00134-014-3601-4</pub-id>
        <pub-id pub-id-type="medline">25576157</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>Pines</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Iyer</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Disbot</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Hollander</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Shofer</surname>
            <given-names>FS</given-names>
          </name>
          <name name-style="western">
            <surname>Datner</surname>
            <given-names>EM</given-names>
          </name>
        </person-group>
        <article-title>The effect of emergency department crowding on patient satisfaction for admitted patients</article-title>
        <source>Acad Emerg Med</source>  
        <year>2008</year>  
        <month>09</month>  
        <volume>15</volume>  
        <issue>9</issue>  
        <fpage>825</fpage>  
        <lpage>31</lpage>  
        <pub-id pub-id-type="medline">19244633</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>Pines</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>McCarthy</surname>
            <given-names>ML</given-names>
          </name>
        </person-group>
        <article-title>The crowding-effectiveness link: it doesn't matter how fast we deliver care if we don't deliver it right</article-title>
        <source>Ann Emerg Med</source>  
        <year>2011</year>  
        <month>03</month>  
        <volume>57</volume>  
        <issue>3</issue>  
        <fpage>201</fpage>  
        <lpage>2</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.annemergmed.2010.12.005</pub-id>
        <pub-id pub-id-type="medline">21232815</pub-id>
        <pub-id pub-id-type="pii">S0196-0644(10)01837-8</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Warden</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Griffin</surname>
            <given-names>RB</given-names>
          </name>
          <name name-style="western">
            <surname>Erickson</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Mchugh</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Wheatley</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Dharshi</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Madhani</surname>
            <given-names>SJ</given-names>
          </name>
          <name name-style="western">
            <surname>Trenum</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <source>Hospital-based emergency care: at the breaking point</source>  
        <year>2006</year>  
        <month>06</month>  
        <publisher-loc>Washington, DC</publisher-loc>
        <publisher-name>National Academies Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bernstein</surname>
            <given-names>SL</given-names>
          </name>
          <name name-style="western">
            <surname>Aronsky</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Duseja</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Epstein</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Handel</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Hwang</surname>
            <given-names>U</given-names>
          </name>
          <name name-style="western">
            <surname>McCarthy</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>John</surname>
            <given-names>MK</given-names>
          </name>
          <name name-style="western">
            <surname>Pines</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Rathlev</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Schafermeyer</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Zwemer</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Schull</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Asplin</surname>
            <given-names>BR</given-names>
          </name>
          <name name-style="western">
            <surname>Society</surname>
            <given-names>FAEMEDCTF</given-names>
          </name>
        </person-group>
        <article-title>The effect of emergency department crowding on clinically oriented outcomes</article-title>
        <source>Acad Emerg Med</source>  
        <year>2009</year>  
        <month>01</month>  
        <volume>16</volume>  
        <issue>1</issue>  
        <fpage>1</fpage>  
        <lpage>10</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.1111/j.1553-2712.2008.00295.x"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1111/j.1553-2712.2008.00295.x</pub-id>
        <pub-id pub-id-type="medline">19007346</pub-id>
        <pub-id pub-id-type="pii">ACEM295</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Jo</surname>
            <given-names>YH</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>JH</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Hwang</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Jung</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <article-title>ED crowding and the outcomes of out-of-hospital cardiac arrest</article-title>
        <source>Am J Emerg Med</source>  
        <year>2015</year>  
        <month>11</month>  
        <volume>33</volume>  
        <issue>11</issue>  
        <fpage>1659</fpage>  
        <lpage>64</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ajem.2015.08.002</pub-id>
        <pub-id pub-id-type="medline">26324002</pub-id>
        <pub-id pub-id-type="pii">S0735-6757(15)00641-5</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>Cha</surname>
            <given-names>WC</given-names>
          </name>
          <name name-style="western">
            <surname>Cho</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Shin</surname>
            <given-names>SD</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>EJ</given-names>
          </name>
          <name name-style="western">
            <surname>Ro</surname>
            <given-names>YS</given-names>
          </name>
        </person-group>
        <article-title>The impact of prolonged boarding of successfully resuscitated out-of-hospital cardiac arrest patients on survival-to-discharge rates</article-title>
        <source>Resuscitation</source>  
        <year>2015</year>  
        <month>05</month>  
        <volume>90</volume>  
        <fpage>25</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.resuscitation.2015.02.004</pub-id>
        <pub-id pub-id-type="medline">25680821</pub-id>
        <pub-id pub-id-type="pii">S0300-9572(15)00065-9</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>Storrow</surname>
            <given-names>AB</given-names>
          </name>
          <name name-style="western">
            <surname>Zhou</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Gaddis</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Han</surname>
            <given-names>JH</given-names>
          </name>
          <name name-style="western">
            <surname>Miller</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Klubert</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Laidig</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Aronsky</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Decreasing lab turnaround time improves emergency department throughput and decreases emergency medical services diversion: a simulation model</article-title>
        <source>Acad Emerg Med</source>  
        <year>2008</year>  
        <month>11</month>  
        <volume>15</volume>  
        <issue>11</issue>  
        <fpage>1130</fpage>  
        <lpage>5</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.1111/j.1553-2712.2008.00181.x"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1111/j.1553-2712.2008.00181.x</pub-id>
        <pub-id pub-id-type="medline">18638034</pub-id>
        <pub-id pub-id-type="pii">ACEM181</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>White</surname>
            <given-names>BA</given-names>
          </name>
          <name name-style="western">
            <surname>Baron</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Dighe</surname>
            <given-names>AS</given-names>
          </name>
          <name name-style="western">
            <surname>Camargo</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>DFM</given-names>
          </name>
        </person-group>
        <article-title>Applying Lean methodologies reduces ED laboratory turnaround times</article-title>
        <source>Am J Emerg Med</source>  
        <year>2015</year>  
        <month>11</month>  
        <volume>33</volume>  
        <issue>11</issue>  
        <fpage>1572</fpage>  
        <lpage>6</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26145581"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.ajem.2015.06.013</pub-id>
        <pub-id pub-id-type="medline">26145581</pub-id>
        <pub-id pub-id-type="pii">S0735-6757(15)00485-4</pub-id>
        <pub-id pub-id-type="pmcid">PMC4628563</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>Asplin</surname>
            <given-names>BR</given-names>
          </name>
          <name name-style="western">
            <surname>Magid</surname>
            <given-names>DJ</given-names>
          </name>
          <name name-style="western">
            <surname>Rhodes</surname>
            <given-names>KV</given-names>
          </name>
          <name name-style="western">
            <surname>Solberg</surname>
            <given-names>LI</given-names>
          </name>
          <name name-style="western">
            <surname>Lurie</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Camargo</surname>
            <given-names>CA</given-names>
          </name>
        </person-group>
        <article-title>A conceptual model of emergency department crowding</article-title>
        <source>Ann Emerg Med</source>  
        <year>2003</year>  
        <month>08</month>  
        <volume>42</volume>  
        <issue>2</issue>  
        <fpage>173</fpage>  
        <lpage>80</lpage>  
        <pub-id pub-id-type="doi">10.1067/mem.2003.302</pub-id>
        <pub-id pub-id-type="medline">12883504</pub-id>
        <pub-id pub-id-type="pii">S019606440300444X</pub-id></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Few</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <source>Information Dashboard Design: The Effective Visual Communication of Data</source>  
        <year>2006</year>  
        <publisher-loc>Sebastopol, California</publisher-loc>
        <publisher-name>O'Reilly Media, Incorporated</publisher-name></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>Franklin</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Gantela</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Shifarraw</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Johnson</surname>
            <given-names>TR</given-names>
          </name>
          <name name-style="western">
            <surname>Robinson</surname>
            <given-names>DJ</given-names>
          </name>
          <name name-style="western">
            <surname>King</surname>
            <given-names>BR</given-names>
          </name>
          <name name-style="western">
            <surname>Mehta</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Maddow</surname>
            <given-names>CL</given-names>
          </name>
          <name name-style="western">
            <surname>Hoot</surname>
            <given-names>NR</given-names>
          </name>
          <name name-style="western">
            <surname>Nguyen</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Rubio</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Okafor</surname>
            <given-names>NG</given-names>
          </name>
        </person-group>
        <article-title>Dashboard visualizations: Supporting real-time throughput decision-making</article-title>
        <source>J Biomed Inform</source>  
        <year>2017</year>  
        <month>12</month>  
        <volume>71</volume>  
        <fpage>211</fpage>  
        <lpage>221</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2017.05.024</pub-id>
        <pub-id pub-id-type="medline">28579532</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(17)30123-5</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>Jarvis</surname>
            <given-names>PRE</given-names>
          </name>
        </person-group>
        <article-title>Improving emergency department patient flow</article-title>
        <source>Clin Exp Emerg Med</source>  
        <year>2016</year>  
        <month>06</month>  
        <volume>3</volume>  
        <issue>2</issue>  
        <fpage>63</fpage>  
        <lpage>68</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.15441/ceem.16.127"/>
        </comment>  
        <pub-id pub-id-type="doi">10.15441/ceem.16.127</pub-id>
        <pub-id pub-id-type="medline">27752619</pub-id>
        <pub-id pub-id-type="pii">ceem-16-127</pub-id>
        <pub-id pub-id-type="pmcid">PMC5051606</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>Dowding</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Randell</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Gardner</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Fitzpatrick</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Dykes</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Favela</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Hamer</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Whitewood-Moores</surname>
            <given-names>Z</given-names>
          </name>
          <name name-style="western">
            <surname>Hardiker</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Borycki</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Currie</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Dashboards for improving patient care: review of the literature</article-title>
        <source>Int J Med Inform</source>  
        <year>2015</year>  
        <month>02</month>  
        <volume>84</volume>  
        <issue>2</issue>  
        <fpage>87</fpage>  
        <lpage>100</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2014.10.001</pub-id>
        <pub-id pub-id-type="medline">25453274</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(14)00189-0</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>Randell</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Greenhalgh</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Wyatt</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Gardner</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Pearman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Honey</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Dowding</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Electronic whiteboards: review of the literature</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2015</year>  
        <volume>210</volume>  
        <fpage>389</fpage>  
        <lpage>93</lpage>  
        <pub-id pub-id-type="medline">25991172</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>Cha</surname>
            <given-names>WC</given-names>
          </name>
          <name name-style="western">
            <surname>Ahn</surname>
            <given-names>KO</given-names>
          </name>
          <name name-style="western">
            <surname>Shin</surname>
            <given-names>SD</given-names>
          </name>
          <name name-style="western">
            <surname>Park</surname>
            <given-names>JH</given-names>
          </name>
          <name name-style="western">
            <surname>Cho</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>Emergency Department Crowding Disparity: a Nationwide Cross-Sectional Study</article-title>
        <source>J Korean Med Sci</source>  
        <year>2016</year>  
        <month>08</month>  
        <volume>31</volume>  
        <issue>8</issue>  
        <fpage>1331</fpage>  
        <lpage>6</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://jkms.org/DOIx.php?id=10.3346/jkms.2016.31.8.1331"/>
        </comment>  
        <pub-id pub-id-type="doi">10.3346/jkms.2016.31.8.1331</pub-id>
        <pub-id pub-id-type="medline">27478347</pub-id>
        <pub-id pub-id-type="pmcid">PMC4951566</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>Bjørn</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Hertzum</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Artefactual Multiplicity: A Study of Emergency-Department Whiteboards</article-title>
        <source>Comput Supported Coop Work</source>  
        <year>2010</year>  
        <month>10</month>  
        <day>27</day>  
        <volume>20</volume>  
        <issue>1-2</issue>  
        <fpage>93</fpage>  
        <lpage>121</lpage>  
        <pub-id pub-id-type="doi">10.1007/s10606-010-9126-7</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>Miller</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Mosby</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Capan</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Kowalski</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Ratwani</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Noaiseh</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Kraft</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Schwartz</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Weintraub</surname>
            <given-names>WS</given-names>
          </name>
          <name name-style="western">
            <surname>Arnold</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Interface, information, interaction: a narrative review of design and functional requirements for clinical decision support</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2018</year>  
        <month>05</month>  
        <day>01</day>  
        <volume>25</volume>  
        <issue>5</issue>  
        <fpage>585</fpage>  
        <lpage>592</lpage>  
        <pub-id pub-id-type="doi">10.1093/jamia/ocx118</pub-id>
        <pub-id pub-id-type="medline">29126196</pub-id>
        <pub-id pub-id-type="pii">4598305</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>Ash</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Berg</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Coiera</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <article-title>Some unintended consequences of information technology in health care: the nature of patient care information system-related errors</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2004</year>  
        <month>04</month>  
        <volume>11</volume>  
        <issue>2</issue>  
        <fpage>104</fpage>  
        <lpage>12</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/lookup/pmidlookup?view=long&#38;pmid=14633936"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1197/jamia.M1471</pub-id>
        <pub-id pub-id-type="medline">14633936</pub-id>
        <pub-id pub-id-type="pii">M1471</pub-id>
        <pub-id pub-id-type="pmcid">PMC353015</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>Bloomrosen</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Starren</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Lorenzi</surname>
            <given-names>NM</given-names>
          </name>
          <name name-style="western">
            <surname>Ash</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Patel</surname>
            <given-names>VL</given-names>
          </name>
          <name name-style="western">
            <surname>Shortliffe</surname>
            <given-names>EH</given-names>
          </name>
        </person-group>
        <article-title>Anticipating and addressing the unintended consequences of health IT and policy: a report from the AMIA 2009 Health Policy Meeting</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2011</year>  
        <volume>18</volume>  
        <issue>1</issue>  
        <fpage>82</fpage>  
        <lpage>90</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21169620"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1136/jamia.2010.007567</pub-id>
        <pub-id pub-id-type="medline">21169620</pub-id>
        <pub-id pub-id-type="pii">18/1/82</pub-id>
        <pub-id pub-id-type="pmcid">PMC3005876</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>Zhang</surname>
            <given-names>A L</given-names>
          </name>
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>R X</given-names>
          </name>
          <name name-style="western">
            <surname>Kang</surname>
            <given-names>M F</given-names>
          </name>
          <name name-style="western">
            <surname>Fan</surname>
            <given-names>H L</given-names>
          </name>
          <name name-style="western">
            <surname>Wang</surname>
            <given-names>W L</given-names>
          </name>
        </person-group>
        <article-title>Study of the regulatory effect of acupuncture on rotation-induced gastric dysrhythmia in rabbits</article-title>
        <source>World J Gastroenterol</source>  
        <year>1997</year>  
        <month>03</month>  
        <day>15</day>  
        <volume>3</volume>  
        <issue>1</issue>  
        <fpage>54</fpage>  
        <lpage>5</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27006588"/>
        </comment>  
        <pub-id pub-id-type="doi">10.3748/wjg.v3.i1.54</pub-id>
        <pub-id pub-id-type="medline">27006588</pub-id>
        <pub-id pub-id-type="pmcid">PMC4796841</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>Tsou</surname>  
        <given-names>M</given-names></name>  
        <name name-style="western">
        <surname>Jung</surname>  
        <given-names>C</given-names></name>  
        <name name-style="western">
        <surname>Allen</surname>  
        <given-names>C</given-names></name>  
        <name name-style="western">
        <surname>Yang</surname>  
        <given-names>J</given-names></name>  
        <name name-style="western">
        <surname>Gawron</surname>  
        <given-names>J</given-names></name>  
        <name name-style="western">
        <surname>Spitzberg</surname>  
        <given-names>B</given-names></name>  
        <name name-style="western">
        <surname>Han</surname>  
        <given-names>S</given-names></name> </person-group>
        <article-title>Social media analytics and research test-bed (SMART dashboard)</article-title>
        <source>Proceedings of the 2015 International Conference on Social Media &#38; Society Article No. 2</source>  
        <year>2015</year>  
        <conf-name>The 2015 International Conference on Social Media &#38; Society</conf-name>
        <conf-date>July 27 - 29, 2015</conf-date>
        <conf-loc>Toronto, Canada</conf-loc>
        <pub-id pub-id-type="doi">10.1145/2789187.2789196</pub-id></nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Park</surname>
            <given-names>GE</given-names>
          </name>
          <name name-style="western">
            <surname>Ko</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Peck</surname>
            <given-names>KR</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>JY</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>JY</given-names>
          </name>
          <name name-style="western">
            <surname>Cho</surname>
            <given-names>SY</given-names>
          </name>
          <name name-style="western">
            <surname>Ha</surname>
            <given-names>YE</given-names>
          </name>
          <name name-style="western">
            <surname>Kang</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Kang</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Huh</surname>
            <given-names>HJ</given-names>
          </name>
          <name name-style="western">
            <surname>Ki</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>NY</given-names>
          </name>
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>JH</given-names>
          </name>
          <name name-style="western">
            <surname>Jo</surname>
            <given-names>IJ</given-names>
          </name>
          <name name-style="western">
            <surname>Jeong</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Suh</surname>
            <given-names>GY</given-names>
          </name>
          <name name-style="western">
            <surname>Park</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Chung</surname>
            <given-names>CR</given-names>
          </name>
          <name name-style="western">
            <surname>Song</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Chung</surname>
            <given-names>DR</given-names>
          </name>
        </person-group>
        <article-title>Control of an Outbreak of Middle East Respiratory Syndrome in a Tertiary Hospital in Korea</article-title>
        <source>Ann Intern Med</source>  
        <year>2016</year>  
        <month>07</month>  
        <day>19</day>  
        <volume>165</volume>  
        <issue>2</issue>  
        <fpage>87</fpage>  
        <lpage>93</lpage>  
        <pub-id pub-id-type="doi">10.7326/M15-2495</pub-id>
        <pub-id pub-id-type="medline">27272273</pub-id>
        <pub-id pub-id-type="pii">2526944</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Jordan</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Jordan</surname>
            <given-names>Jw</given-names>
          </name>
          <name name-style="western">
            <surname>McClelland</surname>
            <given-names>Il</given-names>
          </name>
        </person-group>
        <article-title>SUS-A quick and dirty usability scale</article-title>
        <source>Usability Evaluation in Industry</source>  
        <year>1996</year>  
        <publisher-loc>Boca Raton, Florida</publisher-loc>
        <publisher-name>Taylor &#38; Francis, Inc</publisher-name>
        <fpage>189</fpage>  
        <lpage>194</lpage> </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>Selcon</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Taylor</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Evaluation of the Situational Awareness Rating Technique(SART) as a tool for aircrew systems design</article-title>
        <source>AGARD, Situational Awareness in Aerospace Operations</source>  
        <year>1989</year>  
        <conf-name>Advisory Group For Airospace Research &#38; Development</conf-name>
        <conf-date>october 02 1989</conf-date>
        <conf-loc>Copenhagen, Denmark</conf-loc>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.dtic.mil/dtic/tr/fulltext/u2/a223939.pdf"/>
        </comment> </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>Bangor</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Kortum</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Miller</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Determining what individual SUS scores mean: Adding an adjective rating scale</article-title>
        <source>Journal of usability studies</source>  
        <year>2009</year>  
        <month>05</month>  
        <volume>4</volume>  
        <issue>3</issue>  
        <fpage>114</fpage>  
        <lpage>123</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://delivery.acm.org/10.1145/2840000/2835589/p114-bangor.pdf?ip=115.145.225.152&#38;id=2835589&#38;acc=ACTIVE%20SERVICE&#38;key=0EC22F8658578FE1%2EB50D9BE1468BDDBD%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&#38;__acm__=1538967801_ebf9fbd21db32a9c7a8e6a2539520fcd"/>
        </comment> </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>Staib</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sullivan</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Jones</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Griffin</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Bell</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Scott</surname>
            <given-names>I</given-names>
          </name>
        </person-group>
        <article-title>The ED-inpatient dashboard: Uniting emergency and inpatient clinicians to improve the efficiency and quality of care for patients requiring emergency admission to hospital</article-title>
        <source>Emerg Med Australas</source>  
        <year>2017</year>  
        <month>06</month>  
        <volume>29</volume>  
        <issue>3</issue>  
        <fpage>363</fpage>  
        <lpage>366</lpage>  
        <pub-id pub-id-type="doi">10.1111/1742-6723.12661</pub-id>
        <pub-id pub-id-type="medline">27592365</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Stone-Griffith</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Englebright</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Cheung</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Korwek</surname>
            <given-names>KM</given-names>
          </name>
          <name name-style="western">
            <surname>Perlin</surname>
            <given-names>JB</given-names>
          </name>
        </person-group>
        <article-title>Data-driven process and operational improvement in the emergency department: the ED Dashboard and Reporting Application</article-title>
        <source>J Healthc Manag</source>  
        <year>2012</year>  
        <volume>57</volume>  
        <issue>3</issue>  
        <fpage>167</fpage>  
        <lpage>80; discussion 180</lpage>  
        <pub-id pub-id-type="medline">22724375</pub-id></nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Batley</surname>
            <given-names>NJ</given-names>
          </name>
          <name name-style="western">
            <surname>Osman</surname>
            <given-names>HO</given-names>
          </name>
          <name name-style="western">
            <surname>Kazzi</surname>
            <given-names>AA</given-names>
          </name>
          <name name-style="western">
            <surname>Musallam</surname>
            <given-names>KM</given-names>
          </name>
        </person-group>
        <article-title>Implementation of an emergency department computer system: design features that users value</article-title>
        <source>J Emerg Med</source>  
        <year>2011</year>  
        <month>12</month>  
        <volume>41</volume>  
        <issue>6</issue>  
        <fpage>693</fpage>  
        <lpage>700</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jemermed.2010.05.014</pub-id>
        <pub-id pub-id-type="medline">20619572</pub-id>
        <pub-id pub-id-type="pii">S0736-4679(10)00386-0</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>Randell</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Keen</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Gates</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Ferguson</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Long</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ginn</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>McGinnis</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Whittle</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Managing Quality and Safety in Real Time? Evidence from an Interview Study</article-title>
        <source>Stud Health Technol Inform</source>  
        <year>2016</year>  
        <volume>228</volume>  
        <fpage>23</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="medline">27577334</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
