<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v21i5e12875</article-id>
      <article-id pub-id-type="pmid">31099336</article-id>
      <article-id pub-id-type="doi">10.2196/12875</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>Developing the National Usability-Focused Health Information System Scale for Physicians: Validation Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Roa</surname>
            <given-names>Laura</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mircheva</surname>
            <given-names>Iskra</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="author" id="contrib1" equal-contrib="yes">
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>Hannele</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-3914-5640</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib2">
          <name name-style="western">
            <surname>Kaipio</surname>
            <given-names>Johanna</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-6659-5022</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib3" corresp="yes">
          <name name-style="western">
            <surname>Heponiemi</surname>
            <given-names>Tarja</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>National Institute for Health and Welfare</institution>
            <addr-line>PO Box 30</addr-line>
            <addr-line>Helsinki, 00271</addr-line>
            <country>Finland</country>
            <phone>358 295247434</phone>
            <email>tarja.heponiemi@thl.fi</email>
          </address>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-8540-049X</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib4">
          <name name-style="western">
            <surname>Lääveri</surname>
            <given-names>Tinja</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-4124-6667</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib5">
          <name name-style="western">
            <surname>Aalto</surname>
            <given-names>Anna-Mari</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1287-1431</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib6">
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>Jukka</given-names>
          </name>
          <degrees>MSocSci</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-2621-3245</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib7">
          <name name-style="western">
            <surname>Elovainio</surname>
            <given-names>Marko</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1401-1910</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>National Institute for Health and Welfare</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Aalto University</institution>
        <addr-line>Espoo</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Helsinki University Hospital</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>University of Helsinki</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Finnish Medical Association</institution>
        <addr-line>Helsinki</addr-line>
        <country>Finland</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Tarja Heponiemi 
        <email>tarja.heponiemi@thl.fi</email></corresp>
      </author-notes>
      <pub-date pub-type="collection"><month>05</month><year>2019</year></pub-date>
      <pub-date pub-type="epub">
        <day>16</day>
        <month>05</month>
        <year>2019</year>
      </pub-date>
      <volume>21</volume>
      <issue>5</issue>
      <elocation-id>e12875</elocation-id>
      <!--history from ojs - api-xml-->
      <history>
        <date date-type="received">
          <day>27</day>
          <month>11</month>
          <year>2018</year>
        </date>
        <date date-type="rev-request">
          <day>30</day>
          <month>1</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>18</day>
          <month>2</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Hannele Hyppönen, Johanna Kaipio, Tarja Heponiemi, Tinja Lääveri, Anna-Mari Aalto, Jukka Vänskä, Marko Elovainio. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 16.05.2019.</copyright-statement>
      <copyright-year>2019</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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2019/5/e12875/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Problems in the usability of health information systems (HISs) are well acknowledged, but research still lacks a validated questionnaire for measuring and monitoring different dimensions of usability of HISs. Such questionnaires are needed not only for research but also for developing usability of HISs from the viewpoint of end-user experiences.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to develop and test the validity of the questionnaire measuring the National Usability-Focused HIS-Scale (NuHISS) among a nationally representative sample of Finnish physicians.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We utilized 2 cross-sectional data collected from a random sample of Finnish physicians in 2014 (N=3781; of which 2340 [61.9%] were women) and 2017 (N=4018; of which 2604 [64.8%] were women). Exploratory and confirmatory factor analyses (structural equation modeling [SEM]) were applied to test the structural validity of the NuHISS. As the concurrent validity measure, we used the self-reported overall quality of the electronic health record system (<italic>school grade</italic>) provided by the participants using marginal structural models.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The exploratory factor analyses with Varimax rotation suggested that the 7-factor solution did offer a good fit to the data in both samples (C<sup>2</sup>=2136.14 in 2014 and C<sup>2</sup>=2109.83 in 2017, both <italic>P</italic>&lt;.001). Moreover, structural equation modelling analyses, using comparative fit index (CFI), Tucker-Lewis Index (TLI), Normed Fit Index (NFI), root mean squared error of approximation (RMSEA), and Standardized Root Mean square Residual (SRMR), showed that the 7-factor solution provided an acceptable fit in both samples (CFI=0.92/0.91, TLI=0.92/0.91, NFI=0.92/0.91, RMSEA=0.048/0.049, and SRMR=0.040/0.039). In addition, concurrent validity of this solution was shown to be acceptable. <italic>Ease of use</italic>, but also all other dimensions, was especially associated with overall quality reports independent of measured confounders. The 7-factor solution included dimensions of <italic>technical quality</italic>, <italic>information quality</italic>, <italic>feedback</italic>, <italic>ease of use</italic>, <italic>benefits</italic>, <italic>internal collaboration</italic>, and <italic>cross-organizational collaboration</italic>.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>NuHISS provides a useful tool for measuring usability of HISs among physicians and offers a valid measure for monitoring the long-term development of HISs on a large scale. The relative importance of items needs to be assessed against national electronic health policy goals and complemented with items that have remained outside the NuHISS from the questionnaire when appropriate.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>physicians</kwd>
        <kwd>health information systems</kwd>
        <kwd>questionnaire</kwd>
        <kwd>validation studies</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Problems in usability of health information systems (HISs) are well acknowledged in research [<xref ref-type="bibr" rid="ref1">1</xref>]. The vast investments in the adoption of HISs in the United States as well as in Europe have been driven by expectations reflecting key usability goals, particularly increased effectiveness and efficiency in health care [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. The clinician community has, while considering electronic health record (EHR) systems as an improvement over the paper-based system, expressed frustration with the level of usability of available systems as well as their support for information exchange [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Moreover, several studies suggest that HISs may cause stress and frustration to clinicians and this appears to have increased recently [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. If clinicians cannot achieve their goals with efficiency, effectiveness, and satisfaction by using the implemented information systems (ISs), they seek alternative solutions to reach their goals, that is, by using paper to document and transfer health information [<xref ref-type="bibr" rid="ref8">8</xref>]. Declining to use is one important indication that the anticipated benefits are not being realized.</p>
      <p>Research has shown that with high-quality management and high perceived usability, HISs could yield significant quality and productivity gains [<xref ref-type="bibr" rid="ref4">4</xref>]. To show evidence of these gains arising from HISs use, appropriate measures need to be used. However, usability is qualitative and multidimensional by nature, thereby challenging the measuring [<xref ref-type="bibr" rid="ref9">9</xref>] and thereby accumulation of results [<xref ref-type="bibr" rid="ref10">10</xref>] on a larger scale. Depending on the definition used, the attributes and metrics of measurement have varied [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. The widely known definition for usability is defined by the International Organization for Standardization (ISO) standard as follows: “usability refers to an extent to which a system, product or service can be used by specified users to achieve specific goals with effectiveness, efficiency and satisfaction in a specified context of use” [<xref ref-type="bibr" rid="ref13">13</xref>]. The possible measures for each of these 3 aspects of usability are many. On the basis of a review of practices in measuring usability by Hornbæk [<xref ref-type="bibr" rid="ref9">9</xref>], the challenges include, for example, distinguishing and empirically comparing subjective and objective measures of usability, studying long-term use and usability, extending measures of satisfaction beyond postuse questionnaire, validating and standardizing the host of subjective satisfaction questionnaires used, and studying correlations between usability measures as a means for validation. Alongside with usability, user experience (UX) as a concept has gained interest and is described as a person’s perceptions and responses resulting from the use or anticipated use of a product, system, or service [<xref ref-type="bibr" rid="ref13">13</xref>]. According to the ISO standard [<xref ref-type="bibr" rid="ref13">13</xref>], usability criteria can be used to assess aspects of UX as well.</p>
      <p>Although governments have pushed the adoption of electronic Health (eHealth) systems and services, they have often lacked knowledge of longer term and larger scale eHealth usability and UX in health care contexts. Both the Organisation for Economic Co-operation and Development (OECD) and European Union (EU) have included information and communication technology (ICT) benchmarking as one of the issues on their policy agendas [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]; however, current HIS monitoring on a national level focuses on availability and usage rate of key functionalities of EHRs, personal health record (PHR) systems, health information exchange (HIE), and telemedicine [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Some HIS-related health care output or efficiency indicators (eg, number of visits saved, impact on length of stay, time saved by system use, and cost saved by system use) have also been defined [<xref ref-type="bibr" rid="ref20">20</xref>] but rarely used in systematic, large-scale eHealth monitoring.</p>
      <p>Validated usability questionnaires (eg, Software Usability Measurement Inventory (SUMI) [<xref ref-type="bibr" rid="ref21">21</xref>], System Usability Scale (SUS) [<xref ref-type="bibr" rid="ref22">22</xref>], and Questionnaire for User Interaction Satisfaction (QUIS) [<xref ref-type="bibr" rid="ref23">23</xref>]) are context and domain independent and focus on evaluating the usability of user interfaces typically after usability testing. Our aim was to study and monitor longer-term experiences on usability and experienced outcomes of complex HISs from the viewpoint of physicians and their clinical tasks in specific contexts of clinical work. In addition, we aimed at addressing the development of the EHR systems. SUMI, SUS, or QUIS questions were therefore not as such regarded suitable as repeated measures of perceived usability of HISs on a national level.</p>
      <p>The large-scale eHealth monitoring tools developed by the EU and OECD [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] include indicators for availability of key HIS functionalities and information contents, for example, documentation and retrieval of patient data, availability of patient summary data, and medication list. They do not cover end-users’ experiences on usability or experienced benefits of these functionalities or information contents.</p>
      <p>The DeLone and McLean ISs success model that was developed in 1992 and revised in 2003 [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] is based on vast theoretical and empirical IS research with validation and updates. It has been used in over 30 scientific publications and, more importantly, also applied on a national level in the health care context in the Canada Health Infoway evaluation framework for HISs [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. The original model and its application in the eHealth evaluation framework in Canada offer 6 interrelated dimensions on IS success: (1) System quality, (2) Information quality, (3) Service quality, (4) Use, (5) User satisfaction, and (6) Benefits. The framework does not list specific items or measures. The subareas are not specific to key functionalities and information contents needed in clinical work.</p>
      <p>The Finnish eHealth strategy from 2015 listed a national-level eHealth usability survey as one strategic means to reach the strategy objectives [<xref ref-type="bibr" rid="ref30">30</xref>]. In 2012, Nordic eHealth research network was established under the Nordic Council of Ministers to develop common Nordic eHealth indicators. The Finnish HIS usability-focused questionnaire for physicians was adopted in Iceland and Denmark in 2018. The OECD is also following work by the Nordic countries on common eHealth indicators for countries with advanced national ICT infrastructures [<xref ref-type="bibr" rid="ref30">30</xref>].</p>
      <p>The need to collect national-level evidence on usability and UXs of HISs in health care contexts to steer national eHealth policies and implementation coupled with the lack of suitable measures led to development of the Finnish <italic>EHR systems as tools for physicians</italic> questionnaire and within it, the National Usability-Focused HIS Scale (NuHISS) for physicians in 2009. The development team consisted of 2 physician-researchers, 1 usability researcher, and 2 researchers with experience in sociology of technology and national benchmarking studies. The first questionnaire for physicians with NuHISS was conducted in 2010, before implementation of the first national eHealth service—ePrescription. The second data collection round in 2014 was timed so that the national ePrescription service was in full use in the public sector and implementation of the national patient data repository (Kanta) was to begin. In 2017, the data collection was repeated for physicians for the third time and also extended to cover the nurses. The data collection was timed so that the Kanta system was in full use in Finland. The Ministry of Social Affairs and Health has agreed to fund the next data collection round in 2020, extending it further to social workers and asking for a plan beyond 2020.</p>
      <p>Establishing the Finnish questionnaire containing the NuHISS as a regular source of evidence for steering national eHealth policies as well as increased international attention about the Finnish questionnaire has added pressure for validation of the key measures used for usability. Thus, the objective of this study was to develop a valid and reliable measure of NuHISS for physicians. The research questions were as follows:</p>
      <list list-type="order">
        <list-item>
          <p>What are the most important dimensions of usability and UXs of HISs that the NuHISS for physicians should measure?</p>
        </list-item>
        <list-item>
          <p>Does the developed NuHISS show acceptable construct validity (do the selected survey items measure their corresponding dimension and can the dimensions be separated from each other) and concurrent validity (do the dimensions have associations to other factors, such as quality ratings, that they theoretically should) of the scale?</p>
        </list-item>
      </list>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>The Survey and Data Used to Validate the Usability-Focused HIS Scale</title>
        <sec>
          <title>The Survey Population</title>
          <p>This report is based on the data collected from a random sample of Finnish physicians at 2 data collection points (2 cross-sectional samples) in 2014 (N=18,257) and 2017 (N=18,326). The response rates were 21% in 2014 and 22% in 2017 providing analytic samples of 3781 in 2014 and 4018 in 2017 [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Owing to missing values in a part of the variables, we imputed both datasets (missing pattern of both the samples is reported in the <xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>). We used the multiple imputation method with chained equations using Mice R-package. We generated 5 separate imputed datasets for analyses purposes. The study has been approved by the Finnish National Institute for Health and Welfare Ethics Board.</p>
        </sec>
        <sec>
          <title>The Survey Questionnaire</title>
          <p>Key EHR, HIE, and PHR functionalities and information needed by physicians in everyday clinical work (eg, documentation, viewing and retrieval of patient data, medication list, decision support, HIE, and patient-provided data) were used as a starting point of the questionnaire; see the OECD model survey <italic>The OECD Guide for Measuring ICTs in the Health Sector</italic> [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]). The questions were grounded in physicians’ key HIS use tasks to increase face validity of the questions and to increase comparability with HIS availability monitoring (including the OECD model survey). The usability-focused questions (including aspects of stability, reaction speed, ease-of-use, recovery from errors, learnability, availability, information quality, and utility of information as well as effects) were modified based on the Finnish Medical Association’s information technology (IT)-physicians’ listing of key strengths and weaknesses of their HIS, as well as a comprehensive analysis of existing usability constructs [eg, <xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. The full questionnaire included 17 background questions, 41 usability-focused items, a list of 17 most urgent EHR development needs to select from, a list of 15 best functioning EHR features to select from, and a 9-item module measuring HIS-related well-being. For manager-level physicians, there was an additional 11-item module measuring HIS support for management.</p>
        </sec>
        <sec>
          <title>The Usability-Focused HIS-Scale Items Used</title>
          <p>Of the 41 usability-focused items, 32 items that were identical in the 2014 and 2017 questionnaires were selected for the NuHISS to measure physicians’ experiences on usability and benefits of HISs. The scale items are depicted in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        </sec>
        <sec>
          <title>Items Used for Concurrent Validity Evaluation</title>
          <p>As the concurrent validity measure of the dimensions of our construct, we selected the self-reported overall quality of the EHR system (<italic>school grade</italic>) provided by the participants. The overall quality was rated by a continuous scale from 4=<italic>very poor</italic> to 10=<italic>excellent</italic>. The scale was dichotomized into low (7 or less) and high (more than 7) quality estimates. In 2014, 1095 of 3781 respondents (29%) and in 2017 altogether 1323 of 4018 respondents (33%) rated the system they used as a high-quality system.</p>
          <p>In the concurrent validity analyses, gender, the year of birth, work tenure (in years), and whether the respondent was specialized (yes/no) were used as time independent covariates and overall system quality (measured by school grade given to the system) as the outcome variable (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Measured items in the National Usability-Focused HIS-Scale scale.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="200"/>
              <col width="800"/>
              <thead>
                <tr valign="top">
                  <td>Short name</td>
                  <td>Questionnaire item (with 5-point Likert scale: 1=fully disagree, 5=fully agree)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Logic</td>
                  <td>The arrangement of fields and functions is logical on computer screen</td>
                </tr>
                <tr valign="top">
                  <td>Terminology</td>
                  <td>Terminology on the screen is clear and understandable (eg, titles and labels)</td>
                </tr>
                <tr valign="top">
                  <td>Documenting</td>
                  <td>Entering and documenting patient data is quick, easy, and smooth</td>
                </tr>
                <tr valign="top">
                  <td>Operating info</td>
                  <td>The systems keep me clearly informed about what it is doing (eg, saving data)</td>
                </tr>
                <tr valign="top">
                  <td>Straightforward tasks</td>
                  <td>Routine tasks can be performed in a straight forward manner without the need for extra steps using the system</td>
                </tr>
                <tr valign="top">
                  <td>Needed patient data</td>
                  <td>It is easy to obtain necessary patient information using the EHR<sup>a</sup> system</td>
                </tr>
                <tr valign="top">
                  <td>Nursing record</td>
                  <td>The information on the nursing record is in easily readable format</td>
                </tr>
                <tr valign="top">
                  <td>Stability</td>
                  <td>The systems are stable in terms of technical functionality (does not crash and no downtime)</td>
                </tr>
                <tr valign="top">
                  <td>System errors</td>
                  <td>Faulty system function has caused or has nearly caused a serious adverse event for the patient</td>
                </tr>
                <tr valign="top">
                  <td>Reaction speed</td>
                  <td>The system responds quickly to inputs</td>
                </tr>
                <tr valign="top">
                  <td>Unexpected actions</td>
                  <td>In my view, the system frequently behaves in unexpected or strange ways</td>
                </tr>
                <tr valign="top">
                  <td>Missing info</td>
                  <td>Information entered/documented occasionally disappears from the IS<sup>b</sup></td>
                </tr>
                <tr valign="top">
                  <td>Medic list quality</td>
                  <td>The patient’s current medication list is presented in a clear format</td>
                </tr>
                <tr valign="top">
                  <td>Summary view</td>
                  <td>The EHR system generates a summary view (eg, on a timeline) that helps to develop an overall picture of the patients’ health status</td>
                </tr>
                <tr valign="top">
                  <td>Order completion</td>
                  <td>The system monitors and notifies when the orders given to nurses have been completed</td>
                </tr>
                <tr valign="top">
                  <td>Patient-provided info</td>
                  <td>Measurement results provided electronically by the patient (eg, via patient portal) help to improve the quality of care</td>
                </tr>
                <tr valign="top">
                  <td>Collaboration</td>
                  <td>EHR systems support cooperation and communication between physicians and patients</td>
                </tr>
                <tr valign="top">
                  <td>Suggestion implementation</td>
                  <td>The system supplier implements suggested corrections and amendments as wished</td>
                </tr>
                <tr valign="top">
                  <td>Vendor interest</td>
                  <td>The system supplier is interested in feedback from users</td>
                </tr>
                <tr valign="top">
                  <td>Implementation speed</td>
                  <td>Suggestions for corrections and amendments are implemented sufficiently quickly</td>
                </tr>
                <tr valign="top">
                  <td>Care quality</td>
                  <td>ISs help to improve quality of care</td>
                </tr>
                <tr valign="top">
                  <td>Care continuity</td>
                  <td>ISs help to ensure continuity of care</td>
                </tr>
                <tr valign="top">
                  <td>Guideline adherence</td>
                  <td>ISs support compliance and adherence with the treatment recommendations</td>
                </tr>
                <tr valign="top">
                  <td>Medication errors</td>
                  <td>ISs help in preventing errors and mistakes associated with medications</td>
                </tr>
                <tr valign="top">
                  <td>Duplicate tests</td>
                  <td>ISs help to avoid duplicate tests and examinations</td>
                </tr>
                <tr valign="top">
                  <td>Care needs and impacts</td>
                  <td>The EHR system provides me with information about the need for and effectiveness of treatment of my patients</td>
                </tr>
                <tr valign="top">
                  <td>HIE<sup>c</sup> medication</td>
                  <td>Information on medications ordered in other organizations is easily available</td>
                </tr>
                <tr valign="top">
                  <td>HIE speed</td>
                  <td>Obtaining patient information from another organization often takes too much time</td>
                </tr>
                <tr valign="top">
                  <td>HIE data quality</td>
                  <td>Patient data (also from other organizations) are comprehensive, up-to-date, and reliable</td>
                </tr>
                <tr valign="top">
                  <td>HIE collaboration</td>
                  <td>EHR systems support cooperation and communication between physicians working in different organizations</td>
                </tr>
                <tr valign="top">
                  <td>Professionals collaboration</td>
                  <td>EHR systems support cooperation and communication between physicians and nurses</td>
                </tr>
                <tr valign="top">
                  <td>Physician collaboration</td>
                  <td>EHR systems support cooperation and communication between physicians in your own organization</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table1fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
              <fn id="table1fn2">
                <p><sup>b</sup>IS: information system.</p>
              </fn>
              <fn id="table1fn3">
                <p><sup>c</sup>HIE: health information exchange.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Demographics, including means and SDs of overall system quality (school grade) covariates in the 2014 and 2017 data.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="470"/>
              <col width="250"/>
              <col width="250"/>
              <thead>
                <tr valign="top">
                  <td rowspan="2" colspan="2">Variable</td>
                  <td colspan="2">Year of data collection</td>
                </tr>
                <tr valign="top">
                  <td>2014</td>
                  <td>2017</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="2">Target population, n</td>
                  <td>16,350</td>
                  <td>17,210</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">Questionnaire sent (target population), %</td>
                  <td>91</td>
                  <td>93</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">Respondents</td>
                  <td>3781</td>
                  <td>4018</td>
                </tr>
                <tr valign="top">
                  <td colspan="4"><bold>Gender</bold></td>
                </tr>
                <tr valign="top">
                  <td rowspan="3"><break/></td>
                  <td>Male, %</td>
                  <td>38.1</td>
                  <td>35.1</td>
                </tr>
                <tr valign="top">
                  <td>Female, %</td>
                  <td>61.9</td>
                  <td>64.8</td>
                </tr>
                <tr valign="top">
                  <td>Mean (SD)</td>
                  <td>1.62 (0.49)</td>
                  <td>1.65 (0.48)</td>
                </tr>
                <tr valign="top">
                  <td colspan="4"><bold>Age (years), %</bold></td>
                </tr>
                <tr valign="top">
                  <td rowspan="4"><break/></td>
                  <td>&lt;34</td>
                  <td>16.9</td>
                  <td>16.7 </td>
                </tr>
                <tr valign="top">
                  <td>35-44</td>
                  <td>21.2</td>
                  <td> 21.9</td>
                </tr>
                <tr valign="top">
                  <td>45-54</td>
                  <td>28.4</td>
                  <td> 26.7</td>
                </tr>
                <tr valign="top">
                  <td>55&gt;</td>
                  <td>33.6 </td>
                  <td> 34.7</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">Year of birth, mean</td>
                  <td>1966</td>
                  <td>1969</td>
                </tr>
                <tr valign="top">
                  <td colspan="4"><bold>Specialization</bold></td>
                </tr>
                <tr valign="top">
                  <td rowspan="3"><break/></td>
                  <td>Not specialized (1), %</td>
                  <td>33.1</td>
                  <td>32.6</td>
                </tr>
                <tr valign="top">
                  <td>Specialized (2), %</td>
                  <td>66.9</td>
                  <td>67.4</td>
                </tr>
                <tr valign="top">
                  <td>Mean (SD)</td>
                  <td>1.33 (0.47)</td>
                  <td>1.33 (0.47)</td>
                </tr>
                <tr valign="top">
                  <td colspan="4"><bold>Work tenure (experience, years)</bold></td>
                </tr>
                <tr valign="top">
                  <td rowspan="5"><break/></td>
                  <td>&lt;10, %</td>
                  <td>25.7</td>
                  <td>25.1</td>
                </tr>
                <tr valign="top">
                  <td>&gt;10&lt;20, %</td>
                  <td>22.0</td>
                  <td>22.1</td>
                </tr>
                <tr valign="top">
                  <td>&gt;20&lt;30, %</td>
                  <td>27.1</td>
                  <td>27.0</td>
                </tr>
                <tr valign="top">
                  <td>30+, %</td>
                  <td>25.2</td>
                  <td>25.7</td>
                </tr>
                <tr valign="top">
                  <td>Mean (SD)</td>
                  <td>19.63 (11.42)</td>
                  <td>19.71 (11.48)</td>
                </tr>
                <tr valign="top">
                  <td colspan="4"><bold>School grade given to the primary</bold> <bold>electronic health record</bold> <bold>system</bold></td>
                </tr>
                <tr valign="top">
                  <td rowspan="8"><break/></td>
                  <td>10 (excellent)</td>
                  <td>0.5</td>
                  <td>0.6</td>
                </tr>
                <tr valign="top">
                  <td>9</td>
                  <td>5.2</td>
                  <td>6.3</td>
                </tr>
                <tr valign="top">
                  <td>8</td>
                  <td>20.9</td>
                  <td>23.5</td>
                </tr>
                <tr valign="top">
                  <td>7</td>
                  <td>29.6</td>
                  <td>32.7</td>
                </tr>
                <tr valign="top">
                  <td>6</td>
                  <td>24.2</td>
                  <td>21.9</td>
                </tr>
                <tr valign="top">
                  <td>5</td>
                  <td>14.7</td>
                  <td>11.2</td>
                </tr>
                <tr valign="top">
                  <td>4 (fail)</td>
                  <td>4.9</td>
                  <td>3.8</td>
                </tr>
                <tr valign="top">
                  <td>Mean (SD)</td>
                  <td>6.64 (1.27)</td>
                  <td>6.82 (1.23)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Statistical Analyses Assessing Sample Differences</title>
          <p>Means and SDs of the NuHISS items for the 2 time points (2014 and 2017) were calculated and Welch 2-sample <italic>t</italic> test was used to analyze the differences in the mean profile of the responses from the 2 time points. Following the research questions and established psychometric testing procedures we tested the validity of the NuHISS in 2 steps: (1) structural validity test (do the intended dimensions or latent variables explain the covariance of the corresponding items) showing whether the scale measures the defined dimensions and (2) concurrent validity test (are the dimensions associated with the factors they should be associated with).</p>
        </sec>
        <sec>
          <title>Assessing Construct Validity of the NuHISS Scale Dimensions</title>
          <p>The preliminary structural analyses were conducted by calculating bivariate correlations between the 32 study variables in the 2014 and then in the 2017 data. For grouping the NuHISS scale items into dimensions, we then tested the factor structure and number of dimensions using exploratory factor analyses with eigenvalue 1 and loading structure as a criterion for the appropriate number of factors. The factorial validity of the original scales was tested separately among the 2 samples (time points 2014 and 2017) with exploratory factor analyses (Varimax rotation; [<xref ref-type="bibr" rid="ref32">32</xref>]) and then structural equation modeling (SEM; confirmatory factor analyses).</p>
          <p>Second, we tested the structure using SEM [<xref ref-type="bibr" rid="ref33">33</xref>] that offers more stringent testing and allowing items to be loaded only to their corresponding latent variables (factors). SEM is a multivariate statistical analysis technique. This technique is a combination of factor analysis and multiple regression analysis, and it is used to analyze the structural relationship between measured variables and latent constructs. Goodness-of-fit of the SEM models was evaluated based on the chi-square test (X<sup>2</sup>), RMSEA, CFI, TLI, and Akaike’s information criterion (AIC). A nonsignificant chi-square value indicates that the model is a good fit to the data. RMSEA values of less than .05 and .08 suggest a good and reasonable fit, respectively. For CFI and TLI, values above .90 and .95 represent an acceptable and a good fit, respectively. AIC is a measure used to compare any models that have the same set of variables. In such cases, the model with the smaller value of AIC will be preferred [<xref ref-type="bibr" rid="ref34">34</xref>]. Testing the final structure was done in 3 steps. First, a 1-factor model was estimated where all remaining items were loaded on the same underlying dimension (null model). In the second step, a model representing the original theoretical model was estimated, and, in the final step, the structural invariance (test showing whether the structure can be considered as similar between 2 measurement points) was tested between 2 samples as strong/scalar invariance with factor loadings and intercepts constrained to be similar. Again the same fit indexes were used as in the overall SEM test.</p>
          <p>As a final step for structural validation, we assessed internal consistency of each dimension using Cronbach alpha reliability coefficient. The closer Cronbach alpha coefficient is to 1.0, the greater the internal consistency of the items in the dimension.</p>
        </sec>
        <sec>
          <title>Assessing Concurrent Validity of the Scale Dimensions</title>
          <p>Concurrent validity is the extent to which one measurement is backed up by a related measurement obtained at about the same point in time. In testing, the validity of results obtained from one test (in this case <italic>ease of use</italic>) can often be assessed by comparison with a separate but related measurement (in this case, school grade given to the system) collected at the same point in time [<xref ref-type="bibr" rid="ref35">35</xref>]. Concurrent validity was tested separately for each dimension of the EHR system with the overall quality (measured by school grade given to the system) evaluation as the criteria. The associations between overall quality evaluation and each dimension were tested using the marginal structural model (MSM) approach proposed by Robins et al [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>], with inverse probability weights taking into account the effects of potential covariates. The approach produces a pseudopopulation with balance in all included covariates.</p>
          <p>Statistical programming language R (version 3.5.1)/R-studio and multiple statistical R-packages (psych, psycho, missForest, mice, miceadds, ggplot2, resahpe2, lavaan, semPlot, semTools, ipw, sandwich, and survey) were used for the statistical analyses.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Differences of Samples From the 2 Time Points</title>
        <p>Means and SDs of the measured items in 2014 and 2017 are presented in <xref ref-type="fig" rid="figure1">Figure 1</xref>. There were some differences between time points especially in HIE medication (<italic>information on medication prescribed in other organizations is easily accessible</italic>), duplicate tests (<italic>ISs help prevent overlapping examinations</italic>), care needs and impacts (<italic>IS provides me information on the need and efficiency of care</italic>), and B2C collaboration (<italic>ISs support collaboration between physicians and patients</italic>). The mean profiles were, however, relatively similar: Overall correlations between samples were 0.97, suggesting that the means were very similar between time points. The Welch 2-Sample <italic>t</italic> test suggested that the difference of the overall means between samples (in 2014, mean 3.28; in 2017, mean 3.27; difference=0.016) was not significant (<italic>t</italic><sub>(7757.06)</sub>=1.14; 95% CI [–0.012 to 0.044]; <italic>P</italic>&gt;.10).</p>
      </sec>
      <sec>
        <title>Construct Validity of the NuHISS Scale</title>
        <sec>
          <title>Item-to-Item Correlations</title>
          <p>Correlation matrixes in both samples are presented in <xref ref-type="fig" rid="figure2">Figures 2</xref> and <xref ref-type="fig" rid="figure3">3</xref>. In 2014 data, items around dimension that we named <italic>technical quality</italic> show strong mutual correlations in both years, also correlating especially with most of the relatively strongly mutually correlating items in dimension that we named <italic>ease of use</italic>. <italic>Ease of use</italic> items also correlate with the dimension named <italic>benefit</italic>. Items in the dimension that we named <italic>cross-organization collaboration</italic> also cluster together, but with less significant correlations (lighter color) and correlations also with <italic>internal collaboration</italic>, <italic>ease of use</italic>, and <italic>benefits</italic> items. Items in the <italic>feedback</italic> dimension show strongest between-item correlation, represented by the darkest color, without strong external correlations. Items in the <italic>info quality</italic> dimension do not cluster together so clearly. <italic>Benefit</italic> dimension items correlate clearly with each other. The 2 <italic>internal collaboration</italic> items correlate with each other and also with some of <italic>ease of use</italic> and <italic>cross-organization collaboration</italic> items.</p>
          <p>In the 2017 data, the clearest item-to-item correlations are within the <italic>feedback</italic> dimension items. In addition, <italic>ease of use</italic> items, <italic>technical quality</italic> items, <italic>internal collaboration</italic> items, and most of <italic>benefits</italic> dimension items show clear item-to-item correlations. <italic>Cross-organizational collaboration</italic> items show clearer within-item correlations in 2017 than in 2014 data.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Means and standard deviations of the measured items in 2014 and 2017. HIE: health information exchange.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Correlation matrixes among items in 2014.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Correlation matrixes among items in 2017.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Scale Structure and Reliability Testing</title>
          <p>The exploratory factor analyses with Varimax rotation suggested that the 7-factor solution did offer a good fit to the data in both samples (test of the hypothesis that 7 factors are sufficient, X<sup>2</sup><sub>293</sub>=2136.14 in 2014 and X<sup>2</sup><sub>293</sub>=2109.83 in 2017, both <italic>P</italic>&lt;.001, see also <xref ref-type="fig" rid="figure4">Figures 4</xref> and <xref ref-type="fig" rid="figure5">5</xref>). However, in both samples the choice of 6 factor was supported by 2 (out of 9; 22.22%) methods (Optimal Coordinates and Parallel Analysis) and the choice of 8 factor was supported by 2 (out of 9; 22.22%) methods (Bayesian information criterion [BIC] and Sample Size Adjusted BIC).</p>
          <p>In SEM analyses, the null model (without predicted structure) did not provide an acceptable fit to the data in 2014 (CFI=0.64, TLI=0.62, NFI=0.64, RMSEA=0.100, and SRMR=0.081) or in 2017 (CFI=0.66, TLI=0.64, NFI=0.66, RMSEA=0.094, and SRMR=0.074). The original 7-factor solution, however, provided an acceptable fit in both samples (CFI=0.92/0.91, TLI=0.92/0.91, NFI=0.92/0.91, RMSEA=0.048/0.049, and SRMR=0.040/0.039). The final solutions are presented in <xref ref-type="fig" rid="figure6">Figures 6</xref> and <xref ref-type="fig" rid="figure7">7</xref>.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Eigenvalues and explained variance by the number of factors (exploratory factor analyses) in 2014 sample.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Eigenvalues and explained variance by the number of factors (exploratory factor analyses) in 2017 sample.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Confirmatory factor analysis in 2014 data.</p>
            </caption>
            <graphic xlink:href="jmir_v21i5e12875_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        <fig id="figure7" position="float">
          <label>Figure 7</label>
          <caption>
            <p>Confirmatory factor analysis in 2017 data.</p>
          </caption>
          <graphic xlink:href="jmir_v21i5e12875_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
          <p>The strongest 2 factors (measured by the loadings of items) were <italic>feedback</italic> and <italic>internal collaboration</italic>—in both years all the item loadings were over 0.7. All items in <italic>ease of use</italic>, <italic>technical quality</italic>, and <italic>benefits</italic>—factors had factor loadings over 0.5 both years. The weakest factor loadings in 2017 were in <italic>information quality</italic> factor (0.38 in 2014 for Patient-provided information item, 0.45/0.49 for Medication list quality item, and 0.47/0.56 for Order completion item in 2014/2017). In addition, <italic>cross-organizational collaboration</italic> factor loading for 1 item remained under 0.5 in 2017 (0.44 for HIE speed item). In addition, the internal reliability of the final factors (assessed with alpha coefficients) in the 2014/2017 data shows that the first 4 factors were the strongest:</p>
          <list list-type="order">
            <list-item>
              <p>Factor 1 <italic>ease of use</italic> (alpha=.87/.86).</p>
            </list-item>
            <list-item>
              <p>Factor 2 <italic>technical quality</italic> (alpha=.82/.80).</p>
            </list-item>
            <list-item>
              <p>Factor 3 <italic>benefits</italic> (alpha=.85/.81).</p>
            </list-item>
            <list-item>
              <p>Factor 4 <italic>feedback</italic> (alpha=.88/.88).</p>
            </list-item>
            <list-item>
              <p>Factor 5 <italic>cross-organizational collaboration</italic> (alpha=.69/.64).</p>
            </list-item>
            <list-item>
              <p>Factor 6 <italic>information quality</italic> (alpha=.61/.62).</p>
            </list-item>
            <list-item>
              <p>Factor 7 <italic>internal collaboration</italic> (alpha=.70/.69).</p>
            </list-item>
          </list>
          <p>As the test of structural consistency, we performed the measurement invariance test that assesses the psychometric equivalence of a construct across groups or across time [<xref ref-type="bibr" rid="ref38">38</xref>]. Results suggest that the final measure provided only minimal invariance between samples. The sequential tests are reported in <xref ref-type="table" rid="table3">Table 3</xref>. This was expected, because the fit of the final 7-factor solution was relatively modest.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Changes of the fit indexes according to the sequential invariance tests.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="60"/>
            <col width="150"/>
            <col width="150"/>
            <col width="100"/>
            <col width="150"/>
            <col width="110"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td>Invariance tests steps</td>
                <td><italic>Df</italic></td>
                <td>Akaike’s information criterion</td>
                <td>Bayesian information criterion</td>
                <td>Chi-square</td>
                <td>Chi-square difference</td>
                <td><italic>Df</italic> difference</td>
                <td><italic>P</italic>-difference (&gt;chi-square)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>fit.configural</td>
                <td>886</td>
                <td>660,523</td>
                <td>662,145</td>
                <td>8613.6</td>
                <td>—<sup>a</sup></td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>fit.loadings</td>
                <td>911</td>
                <td>660,626</td>
                <td>662,075</td>
                <td>8766.9</td>
                <td>153.29</td>
                <td>25</td>
                <td>&lt;2.2e-16<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td>fit.intercepts</td>
                <td>936</td>
                <td>661,458</td>
                <td>662,733</td>
                <td>9648.7</td>
                <td>881.78</td>
                <td>25</td>
                <td>&lt;2.2e-16<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td>fit.residuals</td>
                <td>968</td>
                <td>661,693</td>
                <td>662,747</td>
                <td>9947.7</td>
                <td>299.00</td>
                <td>32</td>
                <td>&lt;2.2e-16<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td>fit.means</td>
                <td>975</td>
                <td>661,848</td>
                <td>662,853</td>
                <td>10,116.5</td>
                <td>168.86</td>
                <td>7</td>
                <td>&lt;2.2e-16<sup>b</sup></td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>Not applicable.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup><italic>P</italic>&lt;.001.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        </sec>
      </sec>
      <sec>
        <title>Concurrent Validity of the Scale Items</title>
        <p>In the weighted sample, the covariates had a balanced distribution between those who evaluated the overall quality of the system (<italic>school grade</italic>) low and high in both measurement years (<xref ref-type="table" rid="table4">Tables 4</xref> and <xref ref-type="table" rid="table5">5</xref>). The distribution suggests that the MSM fits relatively well and is effective in balancing covariates across <italic>Overall system quality</italic> (school grade) evaluation sequences (<xref ref-type="table" rid="table6">Table 6</xref>).</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Distribution of covariates between those who evaluated the overall quality of the electronic health record system (<italic>school grade</italic>) low and high in both measurement years from inverse probability weighting in 2014.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td>Variable</td>
                <td>0 (school grade low; n=3780.96<sup>a</sup>), mean (SD)</td>
                <td>1 (school grade high; n=3781.33<sup>a</sup>), mean (SD)</td>
                <td>Standardized mean difference</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Gender</td>
                <td>1.62 (0.49)</td>
                <td>1.62 (0.49)</td>
                <td>0.007</td>
              </tr>
              <tr valign="top">
                <td>Year of birth</td>
                <td>1966.24 (10.93)</td>
                <td>1966.22 (10.84)</td>
                <td>0.002</td>
              </tr>
              <tr valign="top">
                <td>Tenure</td>
                <td>19.85 (11.46)</td>
                <td>19.86 (11.33)</td>
                <td>0.001</td>
              </tr>
              <tr valign="top">
                <td>Specialized</td>
                <td>1.33 (0.47)</td>
                <td>1.33 (0.47)</td>
                <td>0.003</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>n refers to pseudopopulation samples from inverse probability weighting.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Distribution of covariates between those who evaluated the overall quality of the electronic health record system (<italic>school grade</italic>) low and high in both measurement years from inverse probability weighting in 2017.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td>Variable</td>
                <td>0 (school grade low); n=4018.24<sup>a</sup>)</td>
                <td>1 (school grade high; n=4017.07)</td>
                <td>Standardized mean difference</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Gender, mean (SD)</td>
                <td>1.65 (0.48)</td>
                <td>1.65 (0.48)</td>
                <td>0.001</td>
              </tr>
              <tr valign="top">
                <td>Year of birth, mean (SD)</td>
                <td>1969.24 (11.16)</td>
                <td>1969.21 (10.83)</td>
                <td>0.003</td>
              </tr>
              <tr valign="top">
                <td>Tenure, mean (SD)</td>
                <td>19.74 (11.60)</td>
                <td>19.77 (11.26)</td>
                <td>0.003</td>
              </tr>
              <tr valign="top">
                <td>Specialized, mean (SD)</td>
                <td>1.33 (0.47)</td>
                <td>1.32 (0.47)</td>
                <td>0.002</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>n refers to pseudopopulation samples from inverse probability weighting.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Controlled direct effect of overall quality evaluation (<italic>school grade</italic>) estimated from the marginal structural model.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="470"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Factor</td>
                <td>Odds ratio</td>
                <td>95% CI</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4"><bold>2014</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Ease-of-use</td>
                <td>0.29</td>
                <td>0.28 to 0.31</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Technical quality</td>
                <td>0.36</td>
                <td>0.34 to 0.38</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Benefits</td>
                <td>0.49</td>
                <td>0.46 to 0.52</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Feedback</td>
                <td>0.44</td>
                <td>0.42 to 0.48</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Cross-organizational collaboration</td>
                <td>0.59</td>
                <td>0.56 to 0.62</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Information quality</td>
                <td>0.58</td>
                <td>0.55 to 0.60</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Internal collaboration</td>
                <td>0.49</td>
                <td>0.46 to 0.52</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>2017</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Ease-of-use</td>
                <td>0.34</td>
                <td>0.32 to 0.36</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Technical quality</td>
                <td>0.39</td>
                <td>0.37 to 0.41</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Benefits</td>
                <td>0.55</td>
                <td>0.52 to 0.58</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Feedback</td>
                <td>0.48</td>
                <td>0.45 to 0.51</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Cross-organizational collaboration</td>
                <td>0.60</td>
                <td>0.57 to 0.63</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Information quality</td>
                <td>0.58</td>
                <td>0.55 to 0.60</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Internal collaboration</td>
                <td>0.54</td>
                <td>0.51 to 0.57</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>The Validated NuHISS Scale</title>
        <p>The study resulted in a validated scale including 7 dimensions: the <italic>technical quality</italic> dimension measures reliability and safety aspects of the EHR system, including 5 items. The 5 items in the <italic>information quality</italic> dimension reflect availability and format of key information types of the EHR system. Information quality measures for the HIE functionality are included in the <italic>cross-organizational collaboration</italic> dimension. The <italic>feedback</italic> dimension measures responsiveness of the EHR system vendor to improvement suggestions including 3 items. The <italic>ease of use</italic> dimension consists of 7 items related to the key functionalities of the EHR system (including reading, documenting, and patient data retrieval). The <italic>benefit</italic> dimension covers 6 items measuring UX on overall benefits of HISs. The <italic>internal collaboration</italic> dimension with its 2 measures is actually a specific benefit that measures how well the EHR system supports cooperation and communication between professionals within their own organization. <italic>Cross-organizational collaboration</italic> dimension is another specific benefit dimension with 4 measures on systems support cooperation and communication among professionals in different organizations (focusing on HIE functionalities). Loadings of each of the measures show the strongest and weakest measures within each dimension (<xref ref-type="table" rid="table7">Table 7</xref>).</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>The validated National Usability-Focused HIS-Scale with dimension reliability and item loadings.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="280"/>
            <col width="560"/>
            <col width="130"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Dimension (reliability 2014/2017) and short name</td>
                <td>Item on the questionnaire (with 5-point Likert scale: 1=fully disagree, 5=fully agree)</td>
                <td>Factor loading 2014/2017</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4"><bold>Technical quality (alpha=.82/.80)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Stability</td>
                <td>The systems are stable in terms of technical functionality (does not crash, no downtime)</td>
                <td>0.76/0.76</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>System errors</td>
                <td>Faulty system function has caused or has nearly caused a serious adverse event for the patient</td>
                <td>0.65/0.63</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Reaction speed</td>
                <td>The system responds quickly to inputs</td>
                <td>0.77/0.76</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Unexpected actions</td>
                <td>In my view, the system frequently behaves in unexpected or strange ways</td>
                <td>0.69/0.65</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Missing info</td>
                <td>Information entered/documented occasionally disappears from the IS</td>
                <td>0.56/0.55</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Information quality (alpha=.61/.62)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Medic list quality</td>
                <td>The patient’s current medication list is presented in a clear format</td>
                <td>0.45/0.49</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Summary view</td>
                <td>The EHR system generates a summary view (eg, on a timeline) that helps to develop an overall picture of the patient’s health status</td>
                <td>0.56/0.5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Order completion</td>
                <td>The system monitors and notifies when the orders given to nurses have been completed</td>
                <td>0.47/0.56</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Patient-provided info</td>
                <td>Measurement results provided electronically by the patient (eg, via patient portal) help to improve the quality of care</td>
                <td>0.40/0.38</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>B2C collaboration</td>
                <td>EHR systems support co-operation and communication between physicians and patients</td>
                <td>0.54/0.53</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Feedback (alpha=.88/.88)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Suggestion implementation</td>
                <td>The system supplier implements suggested corrections and amendments as wished</td>
                <td>0.93/0.93</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Vendor interest</td>
                <td>The system supplier is interested in feedback from users</td>
                <td>0.78/0.78</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Implementation speed</td>
                <td>Suggestions for corrections and amendments are implemented sufficiently quickly</td>
                <td>0.83/0.84</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Ease of use (alpha=.87/.86)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Logic</td>
                <td>The arrangement of fields and functions is logical on computer screen</td>
                <td>0.75/0.72</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Terminology</td>
                <td>Terminology on the screen is clear and understandable (eg, titles and labels)</td>
                <td>0.71/0.68</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Documenting</td>
                <td>Entering and documenting patient data is quick, easy and smooth</td>
                <td>0.77/0.75</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Operating info</td>
                <td>The systems keep me clearly informed about what it is doing (eg, saving data)</td>
                <td>0.69/0.66</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Straightforward tasks</td>
                <td>Routine tasks can be performed in a straight forward manner without the need for extra steps using the system</td>
                <td>0.75/0.72</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Needed patient data</td>
                <td>It is easy to obtain necessary patient information using the EHR system</td>
                <td>0.68/0.7</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Nursing record</td>
                <td>The information on the nursing record is in easily readable format</td>
                <td>0.59/0.6</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Benefits (alpha=.85/.81)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Care quality</td>
                <td>ISs help to improve quality of care</td>
                <td>0.83/0.79</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Care continuity</td>
                <td>ISs help to ensure continuity of care</td>
                <td>0.74/0.73</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Guideline adherence</td>
                <td>ISs support compliance and adherence with the treatment recommendations</td>
                <td>0.7/0.66</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Medication errors</td>
                <td>ISs help in preventing errors and mistakes associated with medications</td>
                <td>0.6/0.58</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Duplicate tests</td>
                <td>ISs help to avoid duplicate tests and examinations</td>
                <td>0.62/0.59</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Care needs and impacts</td>
                <td>The EHR system provides me with information about the need for and effectiveness of treatment of my patients</td>
                <td>0.72/0.51</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Cross-organizational collaboration (alpha=</bold><bold>.69/.64)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>HIE medication</td>
                <td>Information on medications ordered in other organizations is easily available</td>
                <td>0.6/0.51</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>HIE speed</td>
                <td>Obtaining patient information from another organization often takes too much time</td>
                <td>0.48/0.44</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>HIE data quality</td>
                <td>Patient data (also from other organizations) are comprehensive, up-to-date and reliable</td>
                <td>0.63/0.63</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>HIE collaboration</td>
                <td>EHR systems support co-operation and communication between physicians working in different organizations</td>
                <td>0.66/0.63</td>
              </tr>
              <tr valign="top">
                <td colspan="4"><bold>Internal collaboration (alpha=.70/.69)</bold></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Professionals collaboration</td>
                <td>EHR systems support co-operation and communication Between physicians and nurses</td>
                <td>0.71/0.73</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Physician collaboration</td>
                <td>EHR systems support co-operation and communication Between physicians in your own organization</td>
                <td>0.75/0.72</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>The main aim of this study was to develop and test the validity of the questionnaire measuring NuHISS among a nationally representative sample of Finnish physicians. The exploratory factor analyses showed that the 7-factor solution did offer a good fit to the data and SEM analyses showed that it provided an acceptable fit. Moreover, concurrent validity of this solution was shown to be acceptable. The 7-factor solution included <italic>technical quality</italic>, <italic>information quality</italic>, <italic>feedback</italic>, <italic>ease of use</italic>, <italic>benefits</italic>, <italic>internal collaboration</italic>, and <italic>cross-organizational collaboration</italic> dimensions. Our results show that NuHISS provides a useful tool for measuring the usability of HISs among physicians and offers a valid measure for monitoring the long-term development of HISs on a large scale.</p>
      <sec>
        <title>Differences of Samples</title>
        <p>Overall correlations between the 2 samples suggested that the means were very similar between time points. The Welch 2-Sample <italic>t</italic> test verified that the difference was not significant. This generated a good basis for validation of the scale.</p>
      </sec>
      <sec>
        <title>Validity and Reliability of the Scale</title>
        <p>Construct validity—the degree to which a test measures what it claims to be measuring—was supported by correlation analysis, which revealed the items clustering together, although correlations for some clusters were stronger and for some others weaker and more dispersed. The underlying components were analyzed using factor analysis—principal components analysis (PCA) for data collected with the same scale in 2 time points. PCA led to a 32-item 7-component solution with 65% of the total variance explained in 2014 and 63% in 2017. In confirmatory factor analyses, the original 7-factor solution provided an acceptable, although modest, fit in both samples. Component or factor loadings revealed that the highest loadings were for all items in the <italic>feedback</italic> factor and many items in the <italic>technical quality</italic>, <italic>ease of use</italic>, <italic>benefits</italic>, and <italic>internal collaboration</italic> factors. The <italic>information quality</italic> factor had overall the lowest loadings.</p>
        <p>Internal consistency of factors was assessed by reliability (Cronbach alpha). Reliability of all factors exceeded .60, with the highest alphas in <italic>feedback</italic> (over .80), <italic>ease of use,</italic> and <italic>benefit</italic> factors. The <italic>information quality</italic> factor was the weakest in both years (.61/.62). <italic>Cross-organizational collaboration</italic> reliability was also below .70 in both years.</p>
        <p>Concurrent validity measures the extent to which results correspond to those of a previously established measurement of the construct. The covariates had a balanced distribution between those who evaluated the overall quality of the system (school grade) low and high in both measurement years, suggesting that the MSM fits relatively well and is effective in balancing covariates across quality evaluation sequences.</p>
      </sec>
      <sec>
        <title>Comparison of NuHISS and IS Success Model</title>
        <p>The final 7-factor solution was compared with IS success model dimensions and items (Canada Infoway 2012 version, <xref ref-type="app" rid="app2">Multimedia Appendix 2</xref>). NuHISS covered all but one of the IS success model dimensions (Use) and most of the key subareas. The IS success model dimension of <italic>Use</italic> was out of the scope of our survey (Availability and Usage rate are assessed in Finland with a separate survey to health care providers). In addition, the items were grouped in a slightly different manner. <xref ref-type="app" rid="app2">Multimedia Appendix 2</xref> compares the 2 scales, where black font shows the actual items for each factor or dimension and gray font location of the item, if different in the scales.</p>
        <p>The comparison shows that overall, the NuHISS-scale items are more grounded to the physician work and more detailed than the IS success model items. The NuHISS scale has a more focused <italic>technical quality</italic> factor than the IS success model <italic>System Quality</italic> dimension. In addition to similar items, the latter includes items that fell into NuHISS <italic>ease of use</italic> and <italic>benefits</italic> factors. NuHISS has a dedicated item for <italic>ease of use</italic>, whereas in the IS success model, corresponding items are listed under <italic>system quality</italic> and <italic>information quality</italic> dimensions. NuHISS <italic>benefits</italic> factor and <italic>collaboration</italic> factors correspond to IS success model <italic>user satisfaction</italic> and <italic>information quality</italic> dimensions. NuHISS has specific factors for <italic>cross-organizational</italic> and <italic>internal collaboration</italic>, unlike the IS success model. NuHISS does not include a Service quality factor, although the full questionnaire contains these items.</p>
        <p>On the basis of this comparison, <italic>service quality</italic> factor is a potential new factor to be added in the scale in future. In addition, <italic>information quality</italic> factor has the clearest improvement needs based on the weakest reliability and factor loadings.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The face validity of our questionnaire is good: experts (physicians using the different HISs in their everyday work) have participated in generating the questionnaire and questions were grounded to the core IT functionalities and information contents needed by physicians. The physicians have evaluated the importance of questions from the viewpoint of actual end-users and long-term use of the systems in clinical environments. The surveys have also been pilot tested on both occasions (before sending out the 2014 and 2017 surveys) on a subset of the intended population. The scale offers a valid tool for measuring usability of HISs among professionals and adds substantially to previous scales such as those focusing on measuring usability, acceptability, and user satisfaction of mobile apps among clients [<xref ref-type="bibr" rid="ref39">39</xref>-<xref ref-type="bibr" rid="ref41">41</xref>].</p>
        <p>However, the questionnaire may have shortcomings typical to questionnaire-based surveys: it may include questions that are understood differently by different respondents, depending on the experience they have had with different systems and other individual factors. Although trying to use the language familiar to practicing physicians, we have also been obliged to use terminology from user interface and interaction design fields, such as <italic>label</italic>, <italic>input</italic>, or <italic>screen</italic>. In addition, we used the term <italic>EHR</italic> in instances where questions were particularly focused on the respondents’ main EHR system, and <italic>ISs</italic> in instances where questions focused not only on EHRs but also related specialty-specific regional or national <italic>ISs</italic> or patient-provided data (either via the EHR or via standalone systems). The wording aimed at relieving respondents from knowing the particulars of system integration, but may have also confused some respondents. As the clinical ICT system environments often include several systems, which are used simultaneously, it is not always clear for the physicians which functionalities and features are related to EHR systems and which to other IT systems.</p>
        <p>The total number of respondents in both surveys was about 4000. Response rates remained relatively low (21% to 22%). A small proportion of this is due to the sampling method: We targeted the survey to all physicians in clinical work. The Finnish Medical association’s membership register did not allow us to select only physicians in clinical work into the target population. Therefore, the questionnaires were sent to all working aged physicians (ie, to a larger target population, with a cover letter calling for responses from physicians in clinical work). Calculation of the response rate was carried out from the sent questionnaires, which included physicians not in clinical work. Comparison of the respondents with the target population in 2014 [<xref ref-type="bibr" rid="ref5">5</xref>] and 2017 [<xref ref-type="bibr" rid="ref31">31</xref>] showed good representativeness of samples in both years.</p>
        <p>The questionnaire length is another possible reason for the relatively low response rate. Although the core <italic>NuHISS</italic> for physicians had only 32 items, the full questionnaire had 17 background questions, 41 usability-focused items, a list of 17 most urgent EHR development needs to select from, a list of 15 best functioning EHR features to select from, and a 9-item module measuring HIS-related well-being. For manager-level physicians, there was an additional 11-item module measuring HIS support for management.</p>
        <p>All the questionnaire items related to IS success were not included in the validated scale. Our questions on system integration and proficiency of use were not included because of a different scale. In the exploratory factor analysis (<xref ref-type="app" rid="app3">Multimedia Appendix 3</xref>), our items measuring learnability (<italic>Learning to use the EHR system does not require a lot of training</italic>), recovery from errors (<italic>It is easy to correct mistakes [such as entry errors, ending up in the wrong screen, changing incorrect selections, etc]</italic>), and decision support quality (<italic>The reminders, alerts and warnings provided by the system are useful and are adequate</italic>) loaded on the <italic>ease of use</italic> factor but did not qualify there in the validation. In the exploratory factor analysis, our items <italic>Diagnostic imaging results are easily available on a regional level</italic> and <italic>Laboratory results are easily available and are logically presented on a regional level</italic> loaded on <italic>cross-organizational collaboration</italic> factor but did not qualify for the validated scale. In the exploratory factor analysis, our questions <italic>If I have problems with the system I can easily get help</italic> and <italic>Use of EHR systems frequently takes my attention away from the patient</italic> loaded on <italic>technical quality</italic> factor but did not qualify into the validated scale. In the exploratory factor analysis, our item <italic>I know to whom and how I can send feedback on the system, if I so wish</italic> loaded on the <italic>feedback</italic> factor but did not qualify into the validated scale. All these questions reflect aspects of usability that may still be important to keep in the full questionnaire.</p>
        <p>Although the functionalities and information needed by doctors in daily patient care remain relatively constant, development of technologies may enhance some functionalities (ie, artificial intelligence-assisted decision support and improved personalization possibilities). These developments should also be considered in the full questionnaire for physicians in future. In addition, further development of some of the measures in the <italic>information quality</italic> factor may be called for. In the exploratory factor analysis, there was an eighth factor, which we named <italic>Business to Client collaboration</italic>. This did not qualify as an individual factor in the validation, but combining the items with the <italic>information quality</italic> factor provided a satisfactory result. The eighth factor may become valid, if some items are added or rephrased.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>To our knowledge, Finland is the first country to have administered regular national monitoring of usability of HISs from the viewpoint of end-user experiences. The introduced tool—NuHISS for physicians—offers a valid measure for monitoring the long-term development of HISs on a large scale. The scale is highly adoptable in other countries—it has already been used in Iceland, Denmark, and Germany in 2018. The relative importance of items needs to be assessed against national eHealth policy goals and complemented with items that have remained outside the NuHISS from the questionnaire when appropriate. Development of HIS functionalities calls for further development of the scale, especially within the <italic>information quality</italic> domain. Similar national-level scales have been developed in Finland for nurses and social workers, based on the physician scale. First data collections were conducted from 2017 to 2018. Validation of these in due course will show generalizability of the physician scale across professional groups.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>Number of missing values in each item and missing patterns.</p>
        <media xlink:href="jmir_v21i5e12875_app1.pdf" xlink:title="PDF File (Adobe PDF File), 456KB"/>
      </app>
      <app id="app2">
        <title>Multimedia Appendix 2</title>
        <p>Comparison of National Usability-Focused HIS-Scale and Information System Success model dimensions and items.</p>
        <media xlink:href="jmir_v21i5e12875_app2.pdf" xlink:title="PDF File (Adobe PDF File), 34KB"/>
      </app>
      <app id="app3">
        <title>Multimedia Appendix 3</title>
        <p>Exploratory factor analysis factor matrix with factor loadings.</p>
        <media xlink:href="jmir_v21i5e12875_app3.pdf" xlink:title="PDF File (Adobe PDF File), 64KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AIC</term>
          <def>
            <p>Akaike’s information criterion</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">BIC</term>
          <def>
            <p>Bayesian information criterion</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CFI</term>
          <def>
            <p>comparative fit index</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">eHealth</term>
          <def>
            <p>electronic health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">HIE</term>
          <def>
            <p>health information exchange</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">HIS</term>
          <def>
            <p>health information system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">ICT</term>
          <def>
            <p>information and communication technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">IS</term>
          <def>
            <p>information system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">ISO</term>
          <def>
            <p>International Organization for Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">IT</term>
          <def>
            <p>information technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">MSM</term>
          <def>
            <p>marginal structural model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">NFI</term>
          <def>
            <p>Normed Fit Index</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">NuHISS</term>
          <def>
            <p>National Usability-Focused HIS-Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">OECD</term>
          <def>
            <p>Organisation for Economic Co-operation and Development</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">PCA</term>
          <def>
            <p>principal components analysis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">QUIS</term>
          <def>
            <p>Questionnaire for User Interaction Satisfaction</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb20">RMSEA</term>
          <def>
            <p>root mean squared error of approximation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb21">SEM</term>
          <def>
            <p>structural equation modeling</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb22">SRMR</term>
          <def>
            <p>Standardized Root Mean square Residual</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb23">SUMI</term>
          <def>
            <p>Software Usability Measurement Inventory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb24">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb25">TLI</term>
          <def>
            <p>Tucker-Lewis Index</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb26">UX</term>
          <def>
            <p>user experience</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was funded by the Finnish Work Environment Fund (project 116104), the Strategic Research Council at the Academy of Finland (project 303607), and the Ministry of Social Affairs and Health (project 112241).</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>Roman</surname>
            <given-names>LC</given-names>
          </name>
          <name name-style="western">
            <surname>Ancker</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Johnson</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Senathirajah</surname>
            <given-names>Y</given-names>
          </name>
        </person-group>
        <article-title>Navigation in the electronic health record: a review of the safety and usability literature</article-title>
        <source>J Biomed Inform</source>  
        <year>2017</year>  
        <month>12</month>  
        <volume>67</volume>  
        <fpage>69</fpage>  
        <lpage>79</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30005-9"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2017.01.005</pub-id>
        <pub-id pub-id-type="medline">28088527</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(17)30005-9</pub-id></nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
        <source>European Commission</source>  
        <year>2012</year>  
        <access-date>2019-03-08</access-date>
        <comment>eHealth Action Plan 2012-2020 - Innovative healthcare for the 21st century 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/digital-single-market/en/news/ehealth-action-plan-2012-2020-innovative-healthcare-21st-century">https://ec.europa.eu/digital-single-market/en/news/ehealth-action-plan-2012-2020-innovative-healthcare-21st-century</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iP86cl0"/></comment> </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>Sheikh</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sood</surname>
            <given-names>HS</given-names>
          </name>
          <name name-style="western">
            <surname>Bates</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Leveraging health information technology to achieve the "triple aim" of healthcare reform</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2015</year>  
        <month>07</month>  
        <volume>22</volume>  
        <issue>4</issue>  
        <fpage>849</fpage>  
        <lpage>56</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/25882032"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1093/jamia/ocv022</pub-id>
        <pub-id pub-id-type="medline">25882032</pub-id>
        <pub-id pub-id-type="pii">ocv022</pub-id>
        <pub-id pub-id-type="pmcid">PMC5009900</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>Jones</surname>
            <given-names>SS</given-names>
          </name>
          <name name-style="western">
            <surname>Heaton</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Rudin</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Schneider</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <article-title>Unraveling the IT productivity paradox--lessons for health care</article-title>
        <source>N Engl J Med</source>  
        <year>2012</year>  
        <month>06</month>  
        <day>14</day>  
        <volume>366</volume>  
        <issue>24</issue>  
        <fpage>2243</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="doi">10.1056/NEJMp1204980</pub-id>
        <pub-id pub-id-type="medline">22693996</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>Kaipio</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Lääveri</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Vainiomäki</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Reponen</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Kushniruk</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Borycki</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Usability problems do not heal by themselves: national survey on physicians' experiences with EHRs in Finland</article-title>
        <source>Int J Med Inform</source>  
        <year>2017</year>  
        <month>12</month>  
        <volume>97</volume>  
        <fpage>266</fpage>  
        <lpage>81</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(16)30225-8"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2016.10.010</pub-id>
        <pub-id pub-id-type="medline">27919385</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(16)30225-8</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>Heponiemi</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Vehko</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Kujala</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Aalto</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Elovainio</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Finnish physicians' stress related to information systems keeps increasing: a longitudinal three-wave survey study</article-title>
        <source>BMC Med Inform Decis Mak</source>  
        <year>2017</year>  
        <month>10</month>  
        <day>17</day>  
        <volume>17</volume>  
        <issue>1</issue>  
        <fpage>147</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-017-0545-y"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12911-017-0545-y</pub-id>
        <pub-id pub-id-type="medline">29041971</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12911-017-0545-y</pub-id>
        <pub-id pub-id-type="pmcid">PMC5646125</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Heponiemi</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Kujala</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Aalto</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Vehko</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Elovainio</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Predictors of physicians' stress related to information systems: a nine-year follow-up survey study</article-title>
        <source>BMC Health Serv Res</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>13</day>  
        <volume>18</volume>  
        <issue>1</issue>  
        <fpage>284</fpage>  
        <pub-id pub-id-type="doi">10.1186/s12913-018-3094-x</pub-id>
        <pub-id pub-id-type="medline">29653530</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12913-018-3094-x</pub-id>
        <pub-id pub-id-type="pmcid">PMC5899365</pub-id></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>Hannele</given-names>
          </name>
          <name name-style="western">
            <surname>Lumme</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Reponen</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Kaipio</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Heponiemi</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Lääveri</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Health information exchange in Finland: Usage of different access types and predictors of paper use</article-title>
        <source>Int J Med Inform</source>  
        <year>2019</year>  
        <month>02</month>  
        <volume>122</volume>  
        <fpage>1</fpage>  
        <lpage>6</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.11.005</pub-id>
        <pub-id pub-id-type="medline">30623778</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(18)31310-8</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>Hornbaek</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Current practice in measuring usability: challenges to usability studies and research</article-title>
        <source>Int J Hum Comp Stud</source>  
        <year>2006</year>  
        <volume>64</volume>  
        <fpage>102</fpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijhcs.2005.06.002</pub-id></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Scott</surname>
            <given-names>RE</given-names>
          </name>
          <name name-style="western">
            <surname>Saeed</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <source>ResearchGate</source>  
        <year>2008</year>  
        <access-date>2019-03-12</access-date>
        <comment>Global eHealth - Measuring Outcomes: Why, What, and How: A Report Commissioned by the World Health Organization's Global Observatory for eHealth 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/237279666_Global_eHealth_-_Measuring_Outcomes_Why_What_and_How_A_Report_Commissioned_by_the_World_Health_Organization's_Global_Observatory_for_eHealth">https://www.researchgate.net/publication/237279666_Global_eHealth_-_Measuring_Outcomes_Why_What_and_How_A_Report_Commissioned_by_the _World_Health_Organization's_Global_Observatory_for_eHealth</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76pj8AVbG"/></comment> </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>Usability Engineering</source>  
        <year>1993</year>  
        <publisher-loc>Boston</publisher-loc>
        <publisher-name>Academic Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kurosu</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <source>Revised: What Have We Learnt About Usability Since 1998? Human-Computer Interaction: Design and Evaluation Cham</source>  
        <year>2015</year>  
        <publisher-loc>London</publisher-loc>
        <publisher-name>Academic Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
        <source>International Organization for Standardization</source>  
        <year>2015</year>  
        <access-date>2019-03-08</access-date>
        <comment>ISO 9241-210:2010: Ergonomics of human-system interaction -- Part 210: Human-centred design for interactive systems 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/52075.html">https://www.iso.org/standard/52075.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iRTHG6L"/></comment> </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bevan</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>Usability is quality of use</article-title>
        <source>Adv Hum Fact Ergon</source>  
        <year>1995</year>  
        <volume>20</volume>  
        <fpage>349</fpage>  
        <lpage>54</lpage>  
        <pub-id pub-id-type="doi">10.1016/S0921-2647(06)80241-8</pub-id></nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
        <source>Organisation for Economic Co-operation and Development</source>  
        <year>2015</year>  
        <access-date>2019-03-08</access-date>
        <comment>OECD Recommendation on Health Data Governance 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.oecd.org/els/health-systems/health-data-governance.htm">http://www.oecd.org/els/health-systems/health-data-governance.htm</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iS4HXdH"/></comment> </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
        <source>European Commission</source>  
        <year>2017</year>  
        <access-date>2019-03-08</access-date>
        <comment>Multi annual work programme (MWP) 2018-2021 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/health/sites/health/files/ehealth/docs/ev_20170509_co01_en.pdf">https://ec.europa.eu/health/sites/health/files/ehealth/docs/ev_20170509_co01_en.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iSGlPYO"/></comment> </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
        <source>Organisation for Economic Co-operation and Development</source>  
        <year>2015</year>  
        <access-date>2019-03-08</access-date>
        <comment>Draft OECD Guide for Measuring ICTs in the Health Sector 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.oecd.org/health/health-systems/Draft-oecd-guide-to-measuring-icts-in-the-health-sector.pdf">http://www.oecd.org/health/health-systems/Draft-oecd-guide-to-measuring-icts-in-the-health-sector.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76iSSUVpd"/></comment> </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>Adler-Milstein</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Ronchi</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Cohen</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Winn</surname>
            <given-names>LA</given-names>
          </name>
          <name name-style="western">
            <surname>Jha</surname>
            <given-names>AK</given-names>
          </name>
        </person-group>
        <article-title>Benchmarking health IT among OECD countries: better data for better policy</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2014</year>  
        <volume>21</volume>  
        <issue>1</issue>  
        <fpage>111</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/23721983"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1136/amiajnl-2013-001710</pub-id>
        <pub-id pub-id-type="medline">23721983</pub-id>
        <pub-id pub-id-type="pii">amiajnl-2013-001710</pub-id>
        <pub-id pub-id-type="pmcid">PMC3912720</pub-id></nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
        <source>European Commission</source>  
        <year>2014</year>  
        <access-date>2019-03-13</access-date>
        <comment>European Hospital Survey: Benchmarking Deployment of e-Health Services (2012-2013) 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/digital-single-market/en/news/european-hospital-survey-benchmarking-deployment-ehealth-services-2012-2013">https://ec.europa.eu/digital-single-market/en/news/european-hospital-survey-benchmarking-deployment-ehealth-services-2012-2013</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ppEQiyD"/></comment> </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
        <source>Canada Health Infoway</source>  
        <year>2006</year>  
        <access-date>2019-03-13</access-date>
        <comment>Canada Health Infoway Benefits Evaluation Indicators Technical Report 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.infoway-inforoute.ca/en/">https://www.infoway-inforoute.ca/en/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76ppkMaqi"/></comment> </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kirakowski</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>SUMI Questionnaire</source>  
        <year>2019</year>  
        <comment>The use of questionnaire methods for usability assessment, Background Notes on the SUMI Questionnaire 1994 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://sumi.uxp.ie/about/sumipapp.html">http://sumi.uxp.ie/about/sumipapp.html</ext-link></comment> </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Brooke</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Jordan</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Thomas</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Weerdmeester</surname>
            <given-names>A</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>London</publisher-loc>
        <publisher-name>Taylor and Francis</publisher-name></nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chin</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Diehl</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Norman</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Development of an instrument measuring user satisfaction of the human–computer interface</article-title>
        <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>  
        <year>1988</year>  
        <conf-name>CHI'88</conf-name>
        <conf-date>May 15-19, 1988</conf-date>
        <conf-loc>Washington, DC, USA</conf-loc>
        <fpage>213</fpage>  
        <lpage>8</lpage> </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Codagnone</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Lupiañez-Villanueva</surname>
            <given-names>F</given-names>
          </name>
        </person-group>
        <source>European Commission</source>  
        <year>2014</year>  
        <access-date>2019-03-13</access-date>
        <comment>Benchmarking Deployment of eHealth among General Practitioners (2013) 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/digital-single-market/en/news/benchmarking-deployment-ehealth-among-general-practitioners-2013-smart-20110033">https://ec.europa.eu/digital-single-market/en/news/benchmarking-deployment-ehealth-among-general-practitioners-2013-smart-20110033</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76pqWX0o7"/></comment> </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>DeLone</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>McLean</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <article-title>Information Systems Success: The Quest for the Dependent Variable</article-title>
        <source>Inf Syst Res</source>  
        <year>1992</year>  
        <volume>3</volume>  
        <issue>1</issue>  
        <fpage>60</fpage>  
        <lpage>95</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://pdfs.semanticscholar.org/a041/45f1ca06c61f5985ab22a2346b788f343392.pdf"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1287/isre.3.1.60</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>DeLone</surname>
            <given-names>WH</given-names>
          </name>
          <name name-style="western">
            <surname>McLean</surname>
            <given-names>ER</given-names>
          </name>
        </person-group>
        <article-title>The DeLone and McLean Model of Information Systems Success: a ten-year update</article-title>
        <source>J Man Inf Syst</source>  
        <year>2003</year>  
        <volume>19</volume>  
        <fpage>9</fpage>  
        <lpage>30</lpage>  
        <pub-id pub-id-type="doi">10.1080/07421222.2003.11045748</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Decima</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <source>Canada Health Infoway</source>  
        <year>2012</year>  
        <access-date>2019-03-11</access-date>
        <comment>Canadian Views on Electronic Health Records 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.infoway-inforoute.ca/en/component/edocman/1687-harris-decima-survey-on-electronic-health-records/view-document?Itemid=0">https://www.infoway-inforoute.ca/en/component/edocman/1687-harris-decima-survey-on-electronic-health-records/view-document?Itemid=0</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76mxVSugw"/></comment> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
        <source>Canada Health Infoway</source>  
        <year>2012</year>  
        <access-date>2019-03-13</access-date>
        <comment>Canada Health Infoway Benefits Evaluation Indicators Technical Report Version 2.0 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.infoway-inforoute.ca/en/component/edocman/resources/reports/450-benefits-evaluation-indicators-technical-report-version-2-0">https://www.infoway-inforoute.ca/en/component/edocman/resources/reports/450-benefits-evaluation-indicators-technical-report-version-2-0</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="76prFDNej"/></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>Lau</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Hagens</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Muttitt</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>A proposed benefits evaluation framework for health information systems in Canada</article-title>
        <source>Healthc Q</source>  
        <year>2007</year>  
        <volume>10</volume>  
        <issue>1</issue>  
        <fpage>112-6</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="medline">17326376</pub-id></nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
        <source>Ministry of Social Affairs and Health</source>  
        <year>2016</year>  
        <comment>Information to Support Well-Being And Service Renewal 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://julkaisut.valtioneuvosto.fi/bitstream/handle/10024/74459/URN_ISBN_978-952-00-3575-4.pdf?sequence=1&amp;isAllowed=y">http://julkaisut.valtioneuvosto.fi/bitstream/handle/10024/74459/URN_ISBN_978-952-00-3575-4.pdf?sequence=1&amp;isAllowed=y</ext-link></comment> </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>Saastamoinen</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Vänskä</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Kaipio</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Hyppönen</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Reponen</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Lääveri</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>[Doctors' estimates of patient information systems improved slightly]</article-title>
        <source>Finn Med J</source>  
        <year>2018</year>  
        <volume>34</volume>  
        <fpage>1814</fpage>  
        <lpage>9</lpage> </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Maharee-Lawler</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Rodwell</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Noblet</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>A step toward a common measure of organizational justice</article-title>
        <source>Psychol Rep</source>  
        <year>2010</year>  
        <month>04</month>  
        <volume>106</volume>  
        <issue>2</issue>  
        <fpage>407</fpage>  
        <lpage>18</lpage>  
        <pub-id pub-id-type="doi">10.2466/PR0.106.2.407-418</pub-id>
        <pub-id pub-id-type="medline">20524541</pub-id></nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Jöreskog</surname>
            <given-names>KG</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Bollen</surname>
            <given-names>KA</given-names>
          </name>
          <name name-style="western">
            <surname>Long</surname>
            <given-names>JS</given-names>
          </name>
        </person-group>
        <article-title>Testing structural equation models</article-title>
        <source>Testing Structural Equation Models</source>  
        <year>1993</year>  
        <publisher-loc>Thousand Oaks, CA</publisher-loc>
        <publisher-name>Sage Publications</publisher-name>
        <fpage>294</fpage>  
        <lpage>316</lpage> </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kelloway</surname>
            <given-names>EK</given-names>
          </name>
        </person-group>
        <source>Using LISREL for Structural Equation Modeling: A Researcher's Guide</source>  
        <year>1998</year>  
        <publisher-loc>Thousand Oaks, CA</publisher-loc>
        <publisher-name>Sage Publications</publisher-name></nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nunnally</surname>
            <given-names>JC</given-names>
          </name>
        </person-group>
        <source>McGraw-Hill series in psychology. Psychometric theory</source>  
        <year>1967</year>  
        <publisher-loc>New York</publisher-loc>
        <publisher-name>McGraw-Hill</publisher-name></nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Robins</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Hernan</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Brumback</surname>
            <given-names>B</given-names>
          </name>
        </person-group>
        <article-title>Marginal structural models and causal inference in epidemiology</article-title>
        <source>Epidemiology</source>  
        <year>2000</year>  
        <month>09</month>
        <volume>11</volume>
        <issue>5</issue>  
        <fpage>550</fpage>  
        <lpage>60</lpage> </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>VanderWeele</surname>
            <given-names>TJ</given-names>
          </name>
        </person-group>
        <article-title>Marginal structural models for the estimation of direct and indirect effects</article-title>
        <source>Epidemiology</source>  
        <year>2000</year>  
        <month>01</month>
        <volume>20</volume>
        <issue>1</issue>  
        <fpage>18</fpage>  
        <lpage>26</lpage> </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Putnick</surname>
            <given-names>DL</given-names>
          </name>
          <name name-style="western">
            <surname>Bornstein</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Measurement invariance conventions and reporting: the state of the art and future directions for psychological research</article-title>
        <source>Devel Rev</source>  
        <year>2016</year>  
        <volume>41</volume>  
        <fpage>71</fpage>  
        <lpage>90</lpage> </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Torbjørnsen</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Småstuen</surname>
            <given-names>MC</given-names>
          </name>
          <name name-style="western">
            <surname>Jenum</surname>
            <given-names>AK</given-names>
          </name>
          <name name-style="western">
            <surname>Årsand</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Ribu</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>The Service User Technology Acceptability Questionnaire: psychometric evaluation of the Norwegian Version</article-title>
        <source>JMIR Hum Factors</source>  
        <year>2018</year>  
        <month>12</month>  
        <day>21</day>  
        <volume>5</volume>  
        <issue>4</issue>  
        <fpage>e10255</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://humanfactors.jmir.org/2018/4/e10255/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/10255</pub-id>
        <pub-id pub-id-type="medline">30578191</pub-id>
        <pub-id pub-id-type="pii">v5i4e10255</pub-id>
        <pub-id pub-id-type="pmcid">PMC6324518</pub-id></nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Boß</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Lehr</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Reis</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Vis</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Riper</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Berking</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ebert</surname>
            <given-names>DD</given-names>
          </name>
        </person-group>
        <article-title>Reliability and validity of assessing user satisfaction with web-based health interventions</article-title>
        <source>J Med Internet Res</source>  
        <year>2016</year>  
        <month>08</month>  
        <day>31</day>  
        <volume>18</volume>  
        <issue>8</issue>  
        <fpage>e234</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jmir.org/2016/8/e234/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/jmir.5952</pub-id>
        <pub-id pub-id-type="medline">27582341</pub-id>
        <pub-id pub-id-type="pii">v18i8e234</pub-id>
        <pub-id pub-id-type="pmcid">PMC5023944</pub-id></nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Schnall</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Cho</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Health Information Technology Usability Evaluation Scale (Health-ITUES) for usability assessment of mobile health technology: validation study</article-title>
        <source>JMIR Mhealth Uhealth</source>  
        <year>2018</year>  
        <month>01</month>  
        <day>5</day>  
        <volume>6</volume>  
        <issue>1</issue>  
        <fpage>e4</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://mhealth.jmir.org/2018/1/e4/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/mhealth.8851</pub-id>
        <pub-id pub-id-type="medline">29305343</pub-id>
        <pub-id pub-id-type="pii">v6i1e4</pub-id>
        <pub-id pub-id-type="pmcid">PMC5775483</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
