<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v6i3e13812</article-id>
      <article-id pub-id-type="pmid">31290398</article-id>
      <article-id pub-id-type="doi">10.2196/13812</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>Understanding the Situated Roles of Electronic Medical Record Systems to Enable Redesign: Mixed Methods Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Price</surname>
            <given-names>Blaine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kruse</surname>
            <given-names>Clemens</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Clarke</surname>
            <given-names>Martina</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Scherer</surname>
            <given-names>Daniel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="author" id="contrib1" corresp="yes">
          <name name-style="western">
            <surname>Helou</surname>
            <given-names>Samar</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Social Informatics</institution>
            <institution>Graduate School of Informatics</institution>
            <institution>Kyoto University</institution>
            <addr-line>Yoshida-honmachi, Sakyo-ku</addr-line>
            <addr-line>Kyoto, 606-8501</addr-line>
            <country>Japan</country>
            <phone>81 5055346505</phone>
            <email>helou.samar@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-5233-7025</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib2">
          <name name-style="western">
            <surname>Abou-Khalil</surname>
            <given-names>Victoria</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-9706-0071</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib3">
          <name name-style="western">
            <surname>Yamamoto</surname>
            <given-names>Goshiro</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-2014-7195</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib4">
          <name name-style="western">
            <surname>Kondoh</surname>
            <given-names>Eiji</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-8379-3143</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib5">
          <name name-style="western">
            <surname>Tamura</surname>
            <given-names>Hiroshi</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-7740-2732</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib6">
          <name name-style="western">
            <surname>Hiragi</surname>
            <given-names>Shusuke</given-names>
          </name>
          <degrees>MD, MBA</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-1629-6195</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib7">
          <name name-style="western">
            <surname>Sugiyama</surname>
            <given-names>Osamu</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-0190-1321</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib8">
          <name name-style="western">
            <surname>Okamoto</surname>
            <given-names>Kazuya</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-9079-2253</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib9">
          <name name-style="western">
            <surname>Nambu</surname>
            <given-names>Masayuki</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-4446-5710</ext-link>
        </contrib>
        <contrib contrib-type="author" id="contrib10">
          <name name-style="western">
            <surname>Kuroda</surname>
            <given-names>Tomohiro</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-1472-7203</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
      <label>1</label>
      <institution>Department of Social Informatics</institution>
      <institution>Graduate School of Informatics</institution>  
      <institution>Kyoto University</institution>  
      <addr-line>Kyoto</addr-line>
      <country>Japan</country></aff>
      <aff id="aff2">
      <label>2</label>
      <institution>Division of Medical Information Technology and Administration Planning</institution>
      <institution>Kyoto University Hospital</institution>  
      <addr-line>Kyoto</addr-line>
      <country>Japan</country></aff>
      <aff id="aff3">
      <label>3</label>
      <institution>Department of Gynecology and Obstetrics</institution>
      <institution>Graduate School of Medicine</institution>  
      <institution>Kyoto University</institution>  
      <addr-line>Kyoto</addr-line>
      <country>Japan</country></aff>
      <aff id="aff4">
      <label>4</label>
      <institution>Center for Innovative Research and Education in Data Science</institution>
      <institution>Kyoto University</institution>  
      <addr-line>Kyoto</addr-line>
      <country>Japan</country></aff>
      <aff id="aff5">
      <label>5</label>
      <institution>Preemptive Medicine and Lifestyle Related Diseases Research Center</institution>
      <institution>Kyoto University Hospital</institution>  
      <addr-line>Kyoto</addr-line>
      <country>Japan</country></aff>
      <author-notes>
        <corresp>Corresponding Author: Samar Helou 
        <email>helou.samar@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection"><season>Jul-Sep</season><year>2019</year></pub-date>
      <pub-date pub-type="epub">
        <day>09</day>
        <month>07</month>
        <year>2019</year>
      </pub-date>
      <volume>6</volume>
      <issue>3</issue>
      <elocation-id>e13812</elocation-id>
      <!--history from ojs - api-xml-->
      <history>
        <date date-type="received">
          <day>25</day>
          <month>2</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>18</day>
          <month>3</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>29</day>
          <month>4</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>20</day>
          <month>6</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Samar Helou, Victoria Abou-Khalil, Goshiro Yamamoto, Eiji Kondoh, Hiroshi Tamura, Shusuke Hiragi, Osamu Sugiyama, Kazuya Okamoto, Masayuki Nambu, Tomohiro Kuroda. Originally published in JMIR Human Factors (http://humanfactors.jmir.org), 09.07.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 JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on http://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://humanfactors.jmir.org/2019/3/e13812/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Redesigning electronic medical record (EMR) systems is needed to improve their usability and usefulness. Similar to other artifacts, EMR systems can evolve with time and exhibit situated roles. Situated roles refer to the ways in which a system is appropriated by its users, that is, the unintended ways the users engage with, relate to, and perceive the system in its context of use. These situated roles are usually unknown to the designers as they emerge and evolve as a response by the users to a contextual need or constraint. Understanding the system’s situated roles can expose the unarticulated needs of the users and enable redesign opportunities.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to find EMR redesign opportunities by understanding the situated roles of EMR systems in prenatal care settings.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted a field-based observational study at a Japanese prenatal care clinic. We observed 3 obstetricians and 6 midwives providing prenatal care to 37 pregnant women. We looked at how the EMR system is used during the checkups. We analyzed the observational data following a thematic analysis approach and identified the situated roles of the EMR system. Finally, we administered a survey to 5 obstetricians and 10 midwives to validate our results and understand the attitudes of the prenatal care staff regarding the situated roles of the EMR system.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>We identified 10 distinct situated roles that EMR systems play in prenatal care settings. Among them, 4 roles were regarded as favorable as most users wanted to experience them more frequently, and 4 roles were regarded as unfavorable as most users wanted to experience them less frequently; 2 ambivalent roles highlighted the providers’ reluctance to document sensitive psychosocial information in the EMR and their use of the EMR system as an accomplice to pause communication during the checkups. To improve the usability and usefulness of EMR systems, designers can amplify the favorable roles and minimize the unfavorable roles. Our results also showed that obstetricians and midwives may have different experiences, wants, and priorities regarding the use of the EMR system.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Currently, EMR systems are mainly viewed as tools that support the clinical workflow. Redesigning EMR systems is needed to amplify their roles as communication support tools. Our results provided multiple EMR redesign opportunities to improve the usability and usefulness of EMR systems in prenatal care. Designers can use the results to guide their EMR redesign activities and align them with the users’ wants and priorities. The biggest challenge is to redesign EMR systems in a way that amplifies their favorable roles for all the stakeholders concurrently.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>computerized medical record systems</kwd>
        <kwd>physicians' offices</kwd>
        <kwd>design</kwd>
        <kwd>role</kwd>
        <kwd>prenatal care</kwd>
        <kwd>Japan</kwd>
        <kwd>observational study</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Enabling Redesign by Understanding the Situated Roles of an Electronic Medical Record System</title>
        <p>The usability and usefulness of electronic medical record (EMR) systems are critical for their acceptance and effective use [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. Accordingly, multiple user and usability studies were conducted with the aim of refining the systems’ functional and nonfunctional specifications [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Previous studies used interviews, surveys, focus groups, and observations to identify the needs of EMR users and the issues they encounter when using EMR systems. However, EMR users may have needs that they are not aware of or cannot articulate. Moreover, the experts’ verbal description of their work could be inconsistent with how they perform it in the field [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
        <p>To address these limitations, we adopted a novel approach for finding EMR redesign opportunities. The approach is based on the idea of <italic>redesigning from appropriation</italic> [<xref ref-type="bibr" rid="ref17">17</xref>]. Following this approach, we analyzed the EMR system as an artifact that evolves with time and exhibits situated roles. Situated roles refer to the ways in which a system is appropriated by its users, that is, the unintended ways the users engage with, relate to, and perceive the system in its context of use. The conceptual approach is depicted in <xref ref-type="fig" rid="figure1">Figure 1</xref>. Multiple EMR situated roles can exist; for example, one could use it as an explanation support tool to communicate information to a patient during a consultation or as an excuse to take a break from the conversation. These situated roles are usually unknown to the designers as they emerge with time as a response by the users to a contextual need or constraint. Understanding the situated roles of the system and the users’ attitudes regarding them could enable user-centered redesign opportunities.</p>
        <p>We applied our approach in prenatal care settings, a unique health care setting that does not fit into the common clinician-patient scheme where EMR systems are usually studied. Prenatal care is the periodic care that a pregnant woman receives during her pregnancy. Unlike other health care settings where the aim is to address a patient’s health problems, the main goal of prenatal care is the prevention and early detection of diseases that can affect the pregnant woman and her fetus(es) [<xref ref-type="bibr" rid="ref18">18</xref>]. Therefore, prenatal care is the setting in which we collect information about the health of an individual for the first time. The effective use of EMR systems in antennal care is needed if we aim to have complete longitudinal health records.</p>
      </sec>
      <sec>
        <title>Purpose of This Study</title>
        <p>The purpose of this study was to identify EMR redesign opportunities in prenatal care settings. We achieved this purpose by answering the following research questions:</p>
        <list list-type="bullet">
          <list-item>
            <p>What are the situated roles of EMR systems in prenatal care settings?</p>
          </list-item>
          <list-item>
            <p>Do users want to experience the situated roles more, or less, frequently?</p>
          </list-item>
          <list-item>
            <p>How important are the different situated roles to the users?</p>
          </list-item>
        </list>
        <p>Using our results, designers can align their EMR redesign activities with the wants and priorities of EMR users in prenatal care.</p>
       
      </sec>
      <sec>
        <title>Prenatal Care in Japan</title>
        <p>In Japan, prenatal care is standardized by the Japan Society of Obstetrics and Gynecology and the Japan Association of Obstetricians and Gynecologists. Most of the pregnant women in Japan attend the recommended regular prenatal checkups. Women with uncomplicated pregnancies usually receive 14 checkups. The checkups start around their 8th week of pregnancy and finish 1 week after childbirth [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
         <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Approach for identifying system redesign opportunities.</p>
          </caption>
          <graphic xlink:href="humanfactors_v6i3e13812_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>During prenatal care, almost all pregnant women carry the <italic>Boshi Kenko Techo</italic>, a paper-based maternal and child health (MCH) handbook. The MCH handbook is filled and reviewed by the prenatal care providers. The MCH handbook contains information about the woman’s pregnancy and the child’s development and health [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        <p>Japanese women can receive midwife-led (MW-led) prenatal care or obstetrician-led (OB-led) prenatal care. Previous studies have found that pregnant women in the MW-led care group gave higher ratings to their care satisfaction and their perception of woman-centered care [<xref ref-type="bibr" rid="ref22">22</xref>]. These results highlight the different responsibilities of the obstetricians and the midwives. The obstetricians’ focus is mostly biomedical, whereas the midwives’ focus is to promote self-care.</p>
        <p>In Japan, the adoption of EMR systems has been steadily increasing since 2005 [<xref ref-type="bibr" rid="ref23">23</xref>]. By 2020, the EMR adoption rate is expected to reach 90% for general hospitals [<xref ref-type="bibr" rid="ref24">24</xref>]. Although EMR systems are regularly used in Japanese prenatal care, little is known about their use and about the attitudes of the prenatal care providers regarding them.</p>
      </sec>
      <sec>
        <title>Redesigning from Appropriation</title>
        <p>In a proposed model for artifact study, Fleming talked about the function of an artifact being one of its 5 basic properties [<xref ref-type="bibr" rid="ref25">25</xref>]. He proposed that the function “embraces both the uses (intended functions) and the roles (unintended functions) of the object in its culture.” He also noted that functional analysis would have to involve the discussion of the human and their artifact-associated behavior.</p>
        <p>In a similar vein, multiple studies in computer-supported cooperative work shed light on these unintended functions through the concept of appropriation. Once deployed in their contexts of use, artifacts or technologies are appropriated by their users [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Appropriation is “the way technologies are adopted, adapted and incorporated into working practice” [<xref ref-type="bibr" rid="ref28">28</xref>]. Dourish presented the concept of appropriation as a broader view of customization, one that includes users “making use of the technologies for purposes beyond those for which it was originally designed, or to serve new ends” [<xref ref-type="bibr" rid="ref28">28</xref>]. In this sense, Dourish noted that appropriation lies at the intersection of workplace studies and design and that understanding how technologies are appropriated is critical to developing them [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>It has been suggested that understanding the ways in which a technology is appropriated is important to improve its design process [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. Carroll argues that the appropriation of technologies is part of their design process. As the users appropriate a technology, they play a crucial role in completing its design [<xref ref-type="bibr" rid="ref17">17</xref>]. Carroll also proposed improving the technologies’ design by harvesting the users’ needs from their appropriation activities. By deriving requirements from the appropriated technology, the designer would “design from appropriation” and involve the users as co-designers in an evolutionary design approach [<xref ref-type="bibr" rid="ref17">17</xref>]. On a similar note, Fischer described the “impossibility of complete coverage” as one of the biggest design challenges for designing high-functionality environments. To address this challenge, he proposed “viewing the systems as open-ended and continuously adapted by the people who use them in their day-to-day work” [<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        <p>In their work on persuasive technologies, Krischkowsky et al argued that the study of the unintended uses of a technology is critical to counteract undesired consequences [<xref ref-type="bibr" rid="ref32">32</xref>]. Furthermore, we can find various works in the fields of human-computer interaction [<xref ref-type="bibr" rid="ref31">31</xref>] and design [<xref ref-type="bibr" rid="ref33">33</xref>] that aim to understand the appropriation of technologies in their contexts of use.</p>
      </sec>
      <sec>
        <title>Roles of Electronic Medical Record Systems</title>
        <p>Chase et al [<xref ref-type="bibr" rid="ref34">34</xref>] examined the roles of electronic health record (EHR) systems regarding the collaboration between care providers. They identified 4 general EHR roles:</p>
        <list list-type="bullet">
          <list-item>
            <p>Repository: the EHR allows the providers to have all the needed data in one place.</p>
          </list-item>
          <list-item>
            <p>Messenger: the EHR enables information transfer between the providers.</p>
          </list-item>
          <list-item>
            <p>Orchestrator: the EHR ensures that the right person is doing the right thing at the right time.</p>
          </list-item>
          <list-item>
            <p>Monitor: the EHR allows the identification of gaps in treatment and provides a benchmark for performance evaluation.</p>
          </list-item>
        </list>
        <p>Through these roles, they described the ways in which the EHR system supports or hinders collaboration. Unlike this study, the roles were not extracted with the aim of <italic>redesigning from appropriation</italic> and, thus, were not translated into design recommendations.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>In this study, we used mixed research methods in an exploratory sequential manner—a qualitative study followed by a quantitative study. We used the results from the qualitative method to inform the quantitative method. The sequence of the applied methods is shown in <xref ref-type="fig" rid="figure2">Figure 2</xref>.</p>
        <p>After familiarizing ourselves with the prenatal care process, we conducted a field-based observational study at a Japanese prenatal care clinic. We analyzed the data following a thematic analysis approach to identify the different situated roles that the EMR system plays. Then, we administered a survey to the prenatal care staff to understand their experiences and attitudes regarding the situated roles of the EMR system. Finally, we analyzed the survey data and categorized the situated roles of the EMR system based on the users’ experiences and attitudes. In the following sections, we describe in detail how we conducted each step of the study.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>The applied methods.</p>
          </caption>
          <graphic xlink:href="humanfactors_v6i3e13812_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Literature Review—Familiarization With the Prenatal Care Process</title>
        <p>To rapidly gather a large corpus of knowledge and gain an initial understanding of the prenatal care process, we conducted a review targeting the existing literature on the prenatal care process and guidelines for obstetrical practices in Japan [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. We validated our initial understanding of the process by discussing it with a practicing obstetrician at the prenatal care clinic.</p>
      </sec>
      <sec>
        <title>Identifying the Situated Roles of the Electronic Medical Record System</title>
        <sec>
          <title>Data Collection: Observational Field Study</title>
          <p>One researcher observed a team of obstetricians and midwives providing prenatal care services at an outpatient clinic in a Japanese university hospital. In the observed clinic, a total of 5 obstetricians and 10 midwives provide prenatal care services. After obtaining the approval of 3 obstetricians to observe checkups during their shifts, the researcher conducted the observations by visiting the prenatal care outpatient clinic twice a week over a period of 3 weeks.</p>
          <p>At the beginning of the checkups, the obstetricians explained to the pregnant women and their companions the reasons for the researcher’s presence in the clinic. The obstetricians also asked the pregnant women and their companions if they accept having the researcher observe and take notes during the checkup.</p>
          <p>After the pregnant women and their companions granted their approval, the researcher directly observed the prenatal care checkups and took notes using pen and paper. The notes contained descriptions of the interactions that took place around the EMR system, key information relating to the women’s course of pregnancy (pregnancy week, pregnancy type, and pregnancy number), sketches of the room layout and the EMR screen, and quotes and impressions from the conversations that took place around the EMR system.</p>
          <p>In the observed clinic, there were 2 desks with computer terminals, as shown in <xref ref-type="fig" rid="figure3">Figure 3</xref>. One desk was used by the obstetrician and the other by the midwife. The room layout was <italic>semi-inclusive patient controlled</italic>. The pregnant women could see the EMR screen by moving the direction of their gaze [<xref ref-type="bibr" rid="ref35">35</xref>].</p>
          <p>During the observations, the researcher did not engage in conversations with the present parties. After the pregnant women and their companions left the clinic, the researcher asked the clinical staff questions to clarify certain occurrences. The researcher asked for information about the software that the staff used in addition to the EMR software. The researcher also asked for explanations as to why certain things were done in certain ways, for example, (1) using an image snipping tool, (2) bolding and changing the color of certain text, or (3) copying information from EMR notes and pasting them in other notes. In addition, the researcher inquired about artifacts that were used during the checkups, such as reference books that the staff used and paper files that the pregnant women exchanged with the staff.</p>
          <p>In total, the researcher observed a team of 3 obstetricians and 6 midwives performing 37 prenatal care checkups for 35 different pregnant women between the eighth and 33rd week of their pregnancy.</p>
        </sec>
        <sec>
          <title>Data Analysis: Thematic Analysis</title>
          <p>After each observation, the field notes were transcribed and imported into QDA Miner, a qualitative data analysis tool made by Provalis Research [<xref ref-type="bibr" rid="ref36">36</xref>]. After the observations were completed, the data were analyzed by 3 researchers following the 6 phases of thematic analysis described by Braun et al [<xref ref-type="bibr" rid="ref37">37</xref>]:</p>
          <list list-type="bullet">
            <list-item>
              <p>Familiarization with the data: In the beginning of the analysis process, we read and discussed the data multiple times to familiarize ourselves with it.</p>
            </list-item>
            <list-item>
              <p>Coding the data: The coding process was conducted over 3 iterations in which the codes were extended and refined. The process is described below.</p>
            </list-item>
          </list>
          <p>While familiarizing ourselves with the data, we found that the interactions with the EMR system fall into 4 main categories: (1) interactions that support the communication, (2) interactions that hinder the communication, (3) interactions that support the clinical process, and (4) interactions that hinder the clinical process. These categories were mapped into 4 initial codes and were used in the first coding iteration.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>The observed prenatal care clinic.</p>
            </caption>
            <graphic xlink:href="humanfactors_v6i3e13812_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>After the first coding iteration, we noted more specifically how the EMR system supports/hinders the communication/process. These more detailed descriptions were used to code the data in the second coding iteration.</p>
          <p>After the second coding iteration, we extended the codes to reflect aspects that could not be captured in the original codes and we merged codes together when their contents overlapped. Using these extended and refined codes, we conducted our third coding iteration.</p>
          <list list-type="bullet">
            <list-item>
              <p>Searching for the themes: after the coding was completed, 2 researchers examined the codes to see which ones could fit together under one theme. A theme was considered to be any set of codes that captures a significant or interesting unintended way in which the parties interact with the EMR system.</p>
            </list-item>
            <list-item>
              <p>Reviewing the themes: in this step, we discussed which themes qualify as situated roles of the EMR system. A situated role of the EMR system would be any theme that reflects an unintended way that the users engage with, relate to, and perceive the system in its context of use. When deciding which themes to keep and which themes to discard, we answered the following questions:</p>
              <list list-type="order">
                <list-item>
                  <p>Does the theme really reflect an unintended way that the users engage with, relate to, and perceive the system?</p>
                </list-item>
                <list-item>
                  <p>Does the theme make sense?</p>
                </list-item>
                <list-item>
                  <p>Does the data that we collected support our conclusion?</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Defining and naming the themes: after reviewing the themes, we finally named and clearly defined them to reflect situated roles of the EMR system.</p>
            </list-item>
            <list-item>
              <p>Producing the report: the situated roles of the EMR system are presented in the Results section.</p>
            </list-item>
          </list>
        </sec>
      </sec>
      <sec>
        <title>Identifying the Attitudes of the Prenatal Care Providers Regarding the Situated Roles of the Electronic Medical Record System</title>
        <sec>
          <title>Survey Design</title>
          <p>After the situated roles were defined and named through the thematic analysis process, we administered a survey for all the prenatal care staff working at the observed clinic. In total, 15 surveys were sent out to 5 obstetricians and 10 midwives. The survey participants included the obstetricians and midwives that we observed in the field study.</p>
          <p>First, the purpose of the survey was to validate the situated roles through the experiences of the users. Second, we wanted to understand how frequently the users want to experience the EMR roles and how important is each role to them. Therefore, for each situated role, we asked 3 questions:</p>
          <list list-type="order">
            <list-item>
              <p>Currently, how frequently do you experience [role’s definition]?</p>
            </list-item>
            <list-item>
              <p>Optimally, how frequently would you experience [role’s definition]?</p>
            </list-item>
            <list-item>
              <p>It is important to me that the EMR system does [role’s definition] OR It is important to me that the EMR system does not [role’s definition]</p>
            </list-item>
          </list>
          <p>The purpose of the first question was to validate the situated roles through the users’ current experiences. Answers to this type of question were reported using a 6-point Likert scale ranging from very frequently (1) to not at all (6).</p>
          <p>The purpose of the second question was to understand how frequently the users wanted to experience each role. Answers to this type of question were reported using a 6-point Likert scale ranging from very frequently (1) to not at all (6).</p>
          <p>The purpose of the third question was to understand the importance of each situated role. These statements were formulated based on the roles’ nature. For favorable roles, we asked about the importance of their presence. For unfavorable roles, we asked about the importance of their absence. Answers to these statements were reported using a 4-point Likert scale ranging from strongly agree (1) to disagree (4).</p>
          <p>In addition to the questions regarding the situated roles, the respondents were asked for their job title and the number of years they had used the target EMR system.</p>
          <p>The survey was designed over several iterations. It was pretested by researchers in medical informatics and human-computer interaction who evaluated the structure, understandability, scales, and formulation of the questions. Finally, the survey was pilot tested with 2 graduate students and refined based on their experience and feedback. The final survey was administered in Japanese.</p>
        </sec>
        <sec>
          <title>Survey Participants</title>
          <p>We received a total of 15 survey responses, 5 from obstetricians and 10 from midwives. <xref ref-type="table" rid="table1">Table 1</xref> shows the experience of the participants with the EMR system.</p>
        </sec>
        <sec>
          <title>Survey Analysis</title>
          <p>The purpose of the survey was threefold: (1) validating the situated roles through the experiences of the users, (2) understanding how often the users want to experience each situated role, and (3) understanding how important each situated role is to the users.</p>
          <sec>
            <title>Validation of the Situated Roles</title>
            <p>On the basis of the survey responses, we considered that a situated role is validated if at least one respondent reports experiencing it occasionally.</p>
            <p>We also categorized the situated roles into 3 categories reflecting the extent to which they are currently experienced by the users:</p>
            <list list-type="order">
              <list-item>
                <p>Frequently: more than half of the respondents experienced the role at least frequently.</p>
              </list-item>
              <list-item>
                <p>Occasionally: more than half of the respondents experienced the role at least occasionally.</p>
              </list-item>
              <list-item>
                <p>Rarely: more than half of the respondents experienced the role rarely at most.</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Desired Frequency of the Situated Roles</title>
            <p>We categorized the situated roles into 3 categories reflecting the extent to which they are wanted to be experienced by the users:</p>
            <list list-type="order">
              <list-item>
                <p>Frequently: more than half of the respondents wanted the role to be experienced at least frequently.</p>
              </list-item>
              <list-item>
                <p>Occasionally: more than half of the respondents wanted the role to be experienced at least occasionally.</p>
              </list-item>
              <list-item>
                <p>Rarely: more than half of the respondents wanted to experience the role rarely at most.</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Importance of the Situated Roles</title>
            <p>On the basis of the survey responses, we categorized the situated roles into 4 categories reflecting their degree of importance for the users:</p>
            <list list-type="order">
              <list-item>
                <p>Very important: at least half of the respondents strongly agree that the presence or absence of the role is important.</p>
              </list-item>
              <list-item>
                <p>Important: at least half of the respondents agree that the presence or absence of the role is important.</p>
              </list-item>
              <list-item>
                <p>Somewhat important: at least half of the respondents somewhat agree that the presence or absence of the role is important.</p>
              </list-item>
              <list-item>
                <p>Not important at all: at least half of the respondents disagree that the presence or absence of the role is important.</p>
              </list-item>
            </list>
            <table-wrap position="float" id="table1">
              <label>Table 1</label>
              <caption>
                <p>The survey participants.</p>
              </caption>
              <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="36*"/>
                <col width="40*"/>
                <col width="180*"/>
                <thead>
                  <tr valign="bottom">
                    <td>Participant</td>
                    <td>Job</td>
                    <td>Experience with the EMR<sup>a</sup> system (years)</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td>O1</td>
                    <td>Obstetrician</td>
                    <td>1</td>
                  </tr>
                  <tr valign="top">
                    <td>O2</td>
                    <td>Obstetrician</td>
                    <td>1</td>
                  </tr>
                  <tr valign="top">
                    <td>O3</td>
                    <td>Obstetrician</td>
                    <td>7</td>
                  </tr>
                  <tr valign="top">
                    <td>O4</td>
                    <td>Obstetrician</td>
                    <td>4</td>
                  </tr>
                  <tr valign="top">
                    <td>O5</td>
                    <td>Obstetrician</td>
                    <td>7</td>
                  </tr>
                  <tr valign="top">
                    <td>M1</td>
                    <td>Midwife</td>
                    <td>12</td>
                  </tr>
                  <tr valign="top">
                    <td>M2</td>
                    <td>Midwife</td>
                    <td>3</td>
                  </tr>
                  <tr valign="top">
                    <td>M3</td>
                    <td>Midwife</td>
                    <td>12</td>
                  </tr>
                  <tr valign="top">
                    <td>M4</td>
                    <td>Midwife</td>
                    <td>3</td>
                  </tr>
                  <tr valign="top">
                    <td>M5</td>
                    <td>Midwife</td>
                    <td>5</td>
                  </tr>
                  <tr valign="top">
                    <td>M6</td>
                    <td>Midwife</td>
                    <td>13</td>
                  </tr>
                  <tr valign="top">
                    <td>M7</td>
                    <td>Midwife</td>
                    <td>1</td>
                  </tr>
                  <tr valign="top">
                    <td>M8</td>
                    <td>Midwife</td>
                    <td>5</td>
                  </tr>
                  <tr valign="top">
                    <td>M9</td>
                    <td>Midwife</td>
                    <td>3</td>
                  </tr>
                  <tr valign="top">
                    <td>M10</td>
                    <td>Midwife</td>
                    <td>6</td>
                  </tr>
                </tbody>
              </table>
              <table-wrap-foot>
                <fn id="table1fn1">
                  <p><sup>a</sup>EMR: electronic medical record.</p>
                </fn>
              </table-wrap-foot>
            </table-wrap>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Situated Roles of the Electronic Medical Record System</title>
        <p>In total, we were able to extract 10 distinct situated roles that the EMR system plays in prenatal care settings.</p>
        <p>We found 4 situated roles relating to the communication between the providers, the pregnant women, and their companions, namely: (1) the wingman, (2) the accomplice, (3) the third wheel, and (4) the bouncer.</p>
        <p>Regarding the clinical process, we found that the EMR system plays 6 different situated roles, namely: (1) the messenger, (2) the summarizer, (3) the assistant, (4) the gossip, (5) the alien, and (6) the bureaucrat. <xref ref-type="table" rid="table2">Table 2</xref> shows the situated roles and their definitions.</p>
        <sec>
          <title>The Wingman</title>
          <p>As a wingman, the EMR system supports the care providers in the explanation process.</p>
          <p>During the checkups, the clinical staff verbally communicated clinical information to the pregnant women and their companions. This communication helps the pregnant women and their companions understand the current state of the pregnancy and the logic behind clinical decisions. In the observations, the obstetricians used the EMR system as a support tool to provide clinical information and explanations. We observed the obstetricians pointing toward the screen while reading their EMR notes and explaining them. The obstetricians also used automatically generated charts and ultrasound images from their EMR notes to visually communicate information to the pregnant women and their companions.</p>
          <p>However, the obstetricians did not always automatically employ this strategy. In one case, while the obstetrician was explaining, the pregnant woman started leaning toward the EMR system’s screen to see the image that the obstetrician was looking at. Only after realizing that the pregnant woman was interested in seeing the image did the obstetrician rotate the monitor in her direction.</p>
        </sec>
        <sec>
          <title>The Accomplice</title>
          <p>As an accomplice, the EMR system helps pause communication with the pregnant women.</p>
          <p>We found that the obstetricians used the EMR system as a tool to pause communication with the pregnant women, a strategy which proved particularly useful when their workload was high or in highly emotional situations.</p>
          <p>One of the obstetricians expressed the need for a <italic>moment to think</italic> in which they do not have to maintain a conversation with the pregnant women. In such cases, the EMR system served as a tool to pause the conversation and provide them with the needed moment to think.</p>
          <p>Moreover, talking about pregnancies, especially complicated ones, could result in highly emotional situations. In this case, the EMR system provided the obstetricians with a <italic>bubble</italic> allowing them to distance themselves from the interaction. In one observed case, the obstetrician had to tell the pregnant woman that her pregnancy must be terminated. This woman had already experienced a pregnancy termination. After receiving the information, the pregnant woman started crying. At that moment, the obstetrician resorted to the EMR system to avoid looking at the pregnant woman and allow her to privately wipe her tears and stop herself from crying. When the obstetrician turned to the EMR system, the midwife left her desk and went toward the pregnant woman with a tissue box in hand. The midwife continued standing next to the pregnant woman while the obstetrician was working on the EMR system.</p>
        </sec>
        <sec>
          <title>The Third Wheel</title>
          <p>As a third wheel, the EMR system distracts the care providers from communicating with the pregnant women.</p>
          <p>We found that the obstetricians spent a major part of the checkup time keyboarding and facing the EMR screen. During the obstetricians’ data input time, the pregnant women waited silently in their chair, looked closely at the EMR screen to see what their obstetrician was typing, or tried to initiate a conversation with the obstetrician or their companions.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>The situated roles of electronic medical record systems in prenatal care.</p>
            </caption>
            <table width="1000" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="350"/>
              <col width="650"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Definition</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>The wingman</td>
                  <td>Supports the care providers in the explanation process.</td>
                </tr>
                <tr valign="top">
                  <td>The accomplice</td>
                  <td>Helps pause communication with the pregnant women.</td>
                </tr>
                <tr valign="top">
                  <td>The third wheel</td>
                  <td>Distracts the care providers from communicating with the pregnant women.</td>
                </tr>
                <tr valign="top">
                  <td>The bouncer</td>
                  <td>Excludes the pregnant women and their companions from the electronic medical record.</td>
                </tr>
                <tr valign="top">
                  <td>The messenger</td>
                  <td>Enables the communication of information between the care providers.</td>
                </tr>
                <tr valign="top">
                  <td>The summarizer</td>
                  <td>Provides a quick summary of the pregnancy’s current state and care course.</td>
                </tr>
                <tr valign="top">
                  <td>The assistant</td>
                  <td>Facilitates the management and preparation of the checkups.</td>
                </tr>
                <tr valign="top">
                  <td>The gossip</td>
                  <td>Is not completely trusted with sensitive information.</td>
                </tr>
                <tr valign="top">
                  <td>The alien</td>
                  <td>Has low learnability, requires recall, and does not support routine tasks.</td>
                </tr>
                <tr valign="top">
                  <td>The bureaucrat</td>
                  <td>Requires the care providers to halt the clinical process to input data.</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <p>While inputting data, the obstetricians responded to the pregnant women in various ways. Most of the time, they responded by turning their heads slightly away from the screen toward the pregnant woman. When the pregnant woman continued to ask questions or tried to engage in conversation, the obstetricians either started to alternate quickly between the screen and her or stopped inputting data and turned their chair away from the desk to face and respond to her. In some cases, they fully rotated their chair, but in most cases, they turned it halfway between their desk and the pregnant woman.</p>
        </sec>
        <sec>
          <title>The Bouncer</title>
          <p>As a bouncer, the EMR system creates an exclusive environment by physically excluding the pregnant women and their companions.</p>
          <p>On multiple occasions, we found that the pregnant women and their companions showed interest in looking at the EMR. However, the pregnant women had to actively get closer to the screen while their companions’ assigned chairs were placed too far from the screen, leading most of them to stop trying to look at the screen after a while.</p>
          <p>On one occasion, the companion of the pregnant woman stood up to get a better view of the EMR screen. After standing up and realizing that he still cannot get a clear view, he tilted his head and body forward in the direction of the screen. When he realized that, even in this position, he cannot clearly see the contents of the EMR, he went back to his seat. After some time, he got up again, tilted forward toward the screen and went back to his seat, clearly feeling disappointed. A while later, he repeated the same sequence: he stood up, tilted forward, and sat down again. After sitting down, he gazed at the floor, bored and frustrated. Finally, he stood up, moved closer to the pregnant woman and to the EMR screen and remained standing there until the end of the checkup.</p>
        </sec>
        <sec>
          <title>The Messenger</title>
          <p>As a messenger, the EMR system enables the communication of information between the care providers.</p>
          <p>In the case of the observed clinic, every pregnancy was cared for by multiple obstetricians and midwives. The rotation of the clinical staff required them to communicate the pregnant women’s health data. The EMR system was the main tool for communicating clinical information to ensure continuity of care. The EMR system, in this case, provided seamless communication between the clinical staff over time and staff rotations.</p>
          <p>Conversely, when pregnant women were transferred from other clinics, the team only had access to the paper records that they had brought with them. In this case, the team created new EMRs for the women. However, the previous notes existing in the paper records were not transferred to the newly created EMRs.</p>
          <p>Even though the pregnant women and their family members are involved in communicating health-related information to the care providers, they did not have the ability to directly add information into the EMR. During the checkups, through conversations with the pregnant women and notes from the women’s MCH handbooks, the providers gathered information and added them into EMR memos. However, what went into the EMR remained under the full control of the care providers.</p>
          <p>In one examination, a pregnant woman, with a history of high blood pressure, brought along a paper containing a list of blood pressure measurements that she self-monitored and recorded. The obstetrician reviewed the measurements and handed the paper back to the woman. Then, the obstetrician wrote a note in an EMR memo regarding the measurements. However, the full list of blood pressure measurements remained out of the woman’s EMR.</p>
        </sec>
        <sec>
          <title>The Summarizer</title>
          <p>As a summarizer, the EMR system provides the care providers with a summary of the pregnancy’s current state and care course.</p>
          <p>The EMR system allows the prenatal care providers to have all the health information in one place. On multiple occasions, before calling a pregnant woman into the clinic, the obstetricians quickly navigated through the previous EMR notes to form a mental summary of her current course of pregnancy.</p>
          <p>However, the EMR system did not allow for a quick understanding of the current state of the pregnancy. One obstetrician noted, “we would like to see the course of care in one glance. With paper records, it was easier to do that. However, with this system, it takes a lot of clicking and scrolling to get the full image.”</p>
          <p>The staff needed the EMR system to act as a summarizer. To achieve that, the obstetricians employed a workaround. To give themselves and the other providers a quick understanding of the care course, the obstetricians emphasized certain parts of their EMR notes by changing the size, boldness, and color of the text.</p>
        </sec>
        <sec>
          <title>The Assistant</title>
          <p>As an assistant, the EMR system facilitates the management and preparation of the checkups.</p>
          <p>At the beginning of their shift, using the EMR system, the obstetrician and the midwife viewed the list of scheduled checkups. Knowing the number of checkups, they could estimate the workload for the day. Based on that information, they adapted the speed of their work and the duration of checkups. Moreover, using the scheduled checkups list, the obstetrician and midwife knew who they were examining next and had access to her records before the checkup. Before calling the woman in, they reviewed the previous notes and discussed the current state of the woman’s pregnancy. Using this information, they could form a picture of what care actions they needed to perform once the pregnant woman was called in. By allowing for previous preparation, the EMR system makes the checkups run more smoothly. It eliminates the need for the staff to orient themselves and for the pregnant woman to explain the reason for her visit at the beginning of her visit.</p>
        </sec>
        <sec>
          <title>The Gossip</title>
          <p>As a gossip, the EMR system is not completely trusted with sensitive information. In our analysis, we found that the clinical staff hesitate to include highly sensitive information in the pregnant women’s records because of privacy and legal concerns. In one of our discussions with the staff, one midwife stated,</p>
          <disp-quote>
            <p>If we have concerns over some psychosocial issues such as domestic abuse, we note it indirectly in the record. We do not write it literally; we use codes to pass the message to the other clinical staff.</p>
          </disp-quote>
          <p>Employing this sort of strategy to document sensitive information implies that the EMR system is not completely trusted by the staff with information that is usually considered private or could be used for legal purposes.</p>
        </sec>
        <sec>
          <title>The Alien</title>
          <p>As an alien, the EMR system (1) has low learnability, (2) requires a high level of recall, and (3) has an interface that is not optimized for routine tasks.</p>
          <p>The difficulty of learning how to use the EMR system was one of the problems noted by the obstetricians. One obstetrician mentioned that it took them at least 1 month to get used to the system. Moreover, during a checkup, a staff member walked into the clinic and asked the obstetrician a question regarding the use of the EMR system, which the obstetrician answered by guiding them through the interface.</p>
          <p>Furthermore, the EMR system appeared to require a high level of memory recall. The obstetricians frequently paused and tried to recall in which tab a specific field, or note, was placed. The inconvenience of the manual data input was further amplified by an interface design that was not optimized for routine data input and data retrieval tasks.</p>
          <p>In addition, the EMR system suffered from performance-related issues. In certain cases, the system would temporarily stop responding or have a slow response time. These issues occurred particularly when the providers opened a new EMR. Even though 90% of the common database queries are usually cached, and the list of patients is previously compiled, opening a new EMR required more than 10 seconds in certain observed cases. This poor performance resulted in obvious frustration and time loss. To counter this issue, some midwives employed a sort of manual caching where they anticipated the need to open the records, opened the records, and let them load before they actually needed them.</p>
        </sec>
        <sec>
          <title>The Bureaucrat</title>
          <p>As a bureaucrat, the EMR system requires the care providers to halt the care process to input data.</p>
          <p>During the checkups, the providers continuously collect data from multiple sources and add it into the EMR. Those sources include conversations with the pregnant women and their family members; ultrasound imaging devices; and measuring devices such as blood pressure meters, weighing scales, and measuring tapes. The lack of integration between the medical devices and the EMR system required the providers to manually input most of the data that they collect. To do so, they had to intermittently pause their clinical flow. Below are some examples of occurrences encountered during the observations.</p>
          <p>Before entering the clinic, the pregnant women use a blood pressure meter and a weighing scale located in the waiting room. The machines print the measurements on small paper receipts. Once they enter the clinic, the women hand the paper receipts and their MCH handbooks to the midwives. During the checkup, the midwives copy the measurements into the MCH handbook and then input them into the EMR. The process of copying the data could take up to 3 min. After they copy the measurements, the midwives throw the small paper receipts in a trash bin under their desks. On 2 different occasions, during ongoing checkups, the midwives had to look in the trash bin for receipts that they had previously thrown away. In one of those occasions, a nurse had to come in, put gloves on, and help the midwife look inside the trash bin.</p>
          <p>In addition, the midwives routinely measure the belly circumference before the obstetricians start to conduct the ultrasound. Using a measurement tape, they measure the belly twice, vertically and then horizontally. After the second measurement, the midwives sometimes retake the first measurement, as that they might have forgotten the first measure. Once they finish measuring, some midwives prepare the women for the ultrasound, turn off the lights and then head back to their desks to input the measures. As this increases the risk of forgetting the measures, other midwives prefer to head fast to their desks, input the measures in the MCH handbook and the EMR, and then return to the woman to prepare her for the ultrasound.</p>
          <p>As for the obstetricians, they routinely use 2 ultrasound devices to collect data. After they finish conducting the ultrasounds, they reflect on the results and summarize them inside free-text EMR notes. Then, they add the ultrasound images to the notes. To do so, they manually copy the information from the output of the ultrasound devices into the EMR. In addition, they use an image snipping tool to take screenshots of the ultrasound images and then they paste the images inside the EMR notes.</p>
          <p>It is important to note that similarly to the <italic>third wheel</italic>, this role is manifested when the providers input data into the EMR system. However, as a <italic>third wheel</italic>, the EMR system hinders the communication between the providers and the pregnant women, whereas as a <italic>bureaucrat</italic>, the EMR system hinders the clinical workflow.</p>
        </sec>
      </sec>
      <sec>
        <title>Attitudes of the Prenatal Care Providers Regarding the Situated Roles of the Electronic Medical Record System</title>
        <p>All the prenatal care staff responded to the survey. In total, we received 15 responses, 10 responses from midwives and 5 responses from obstetricians.</p>
        <sec>
          <title>Validation of the Situated Roles</title>
          <p>To validate the situated roles, we analyzed the responses regarding the users’ current experience. We looked at the midwives’ and obstetricians’ answers separately. All the situated roles were validated as at least one respondent reported experiencing them occasionally. <xref ref-type="table" rid="table3">Tables 3</xref> and <xref ref-type="table" rid="table4">4</xref> show the responses of the obstetricians and midwives, respectively. The numbers in the table indicate the number of respondents that chose the option.</p>
          <p>To better understand the extent to which different roles are experienced, we assigned them to 3 different categories:</p>
          <list list-type="order">
            <list-item>
              <p>Frequently: more than half of the respondents experienced the role at least frequently.</p>
            </list-item>
            <list-item>
              <p>Occasionally: more than half of the respondents experienced the role at least occasionally.</p>
            </list-item>
            <list-item>
              <p>Rarely: more than half of the respondents experienced the role rarely at most.</p>
            </list-item>
          </list>
          <p>The extent to which the respondents experience the situated roles is shown in <xref ref-type="table" rid="table5">Table 5</xref>.</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>The current frequency of experiencing the situated roles as reported by the obstetricians. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="36*"/>
              <col width="44*"/>
              <col width="41*"/>
              <col width="44*"/>
              <col width="30*"/>
              <col width="31*"/>
              <col width="30*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Very frequently (n)</td>
                  <td>Frequently (n)</td>
                  <td>Occasionally (n)</td>
                  <td>Rarely (n)</td>
                  <td>Very rarely (n)</td>
                  <td>Not at all (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Wingman</td>
                  <td>0</td>
                  <td>2 (O3, O5)</td>
                  <td>2 (O1, O4)</td>
                  <td>1 (O2)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Accomplice</td>
                  <td>0</td>
                  <td>2 (O1, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (O3, O4)</td>
                  <td>1 (O2)</td>
                </tr>
                <tr valign="top">
                  <td>Third wheel</td>
                  <td>0</td>
                  <td>0</td>
                  <td>3 (O1, O2, O4)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (O3, O5)</td>
                </tr>
                <tr valign="top">
                  <td>Bouncer</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (O4)</td>
                  <td>0</td>
                  <td>2 (O1, O3)</td>
                  <td>2 (O2, O5)</td>
                </tr>
                <tr valign="top">
                  <td>Messenger</td>
                  <td>1 (O3)</td>
                  <td>3 (O2, O4, O5)</td>
                  <td>1 (O1)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Summarizer</td>
                  <td>2 (O2, O3)</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Assistant</td>
                  <td>0</td>
                  <td>3 (O1, O2, O3)</td>
                  <td>1 (O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (O4)</td>
                </tr>
                <tr valign="top">
                  <td>Gossip</td>
                  <td>0</td>
                  <td>0</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>1 (O2)</td>
                  <td>1 (O3)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Alien</td>
                  <td>0</td>
                  <td>0</td>
                  <td>4 (O1, O3, O4, O5)</td>
                  <td>1 (O2)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Bureaucrat</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (O1, O5)</td>
                  <td>2 (O2, O3)</td>
                  <td>0</td>
                  <td>1 (O4)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>The current frequency of experiencing the situated roles as reported by the midwives. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="6" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="32*"/>
              <col width="39*"/>
              <col width="44*"/>
              <col width="50*"/>
              <col width="26*"/>
              <col width="40*"/>
              <col width="26*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Very frequently (n)</td>
                  <td>Frequently (n)</td>
                  <td>Occasionally (n)</td>
                  <td>Rarely (n)</td>
                  <td>Very rarely (n)</td>
                  <td>Not at all (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Wingman</td>
                  <td>0</td>
                  <td>1 (M8)</td>
                  <td>3 (M1, M6, M7)</td>
                  <td>2 (M4, M5)</td>
                  <td>1 (M2)</td>
                  <td>3 (M3, M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Accomplice</td>
                  <td>0</td>
                  <td>0</td>
                  <td>7 (M1, M3, M4, M5, M6, M7, M8)</td>
                  <td>1 (M2)</td>
                  <td>2 (M9, M10)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Third wheel</td>
                  <td>1 (M3)</td>
                  <td>0</td>
                  <td>3 (M1, M4, M6)</td>
                  <td>2 (M2, M5)</td>
                  <td>1 (M8)</td>
                  <td>3 (M7, M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Bouncer</td>
                  <td>0</td>
                  <td>1 (M3)</td>
                  <td>6 (M1, M4, M5, M8, M9, M10)</td>
                  <td>3 (M2, M6, M7)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Messenger</td>
                  <td>4 (M2, M3, M4, M7)</td>
                  <td>6 (M1, M5, M6, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Summarizer</td>
                  <td>4 (M3, M4, M6, M7)</td>
                  <td>6 (M1, M2, M5, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Assistant</td>
                  <td>5 (M1, M3, M4, M7, M9)</td>
                  <td>4 (M2, M6, M8, M10)</td>
                  <td>1 (M5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Gossip</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (M8)</td>
                  <td>1 (M10)</td>
                  <td>7 (M1, M2, M4, M5, M6, M7, M9)</td>
                  <td>1 (M3)</td>
                </tr>
                <tr valign="top">
                  <td>Alien</td>
                  <td>0</td>
                  <td>5 (M3, M4, M5, M9, M10)</td>
                  <td>4 (M1, M2, M7, M8)</td>
                  <td>1 (M6)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Bureaucrat</td>
                  <td>1 (M3)</td>
                  <td>1 (M1)</td>
                  <td>6 (M2, M4, M5, M6, M8, M9)</td>
                  <td>1 (M7)</td>
                  <td>1 (M10)</td>
                  <td>0</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>The extent to which the respondents experience the situated roles.</p>
            </caption>
            <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="87*"/>
              <col width="87*"/>
              <col width="82*"/>
              <thead>
                <tr valign="top">
                  <td>Frequency</td>
                  <td>Obstetricians</td>
                  <td>Midwives</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Frequently</td>
                  <td>Summarizer; messenger; assistant</td>
                  <td>Summarizer; messenger; assistant; alien</td>
                </tr>
                <tr valign="top">
                  <td>Occasionally</td>
                  <td>Alien; wingman; third wheel; gossip</td>
                  <td>Accomplice; bureaucrat; bouncer</td>
                </tr>
                <tr valign="top">
                  <td>Rarely</td>
                  <td>Accomplice; bouncer; bureaucrat</td>
                  <td>Wingman; third wheel; gossip</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Desired Frequency of the Situated Roles</title>
          <p>To understand the desired frequency of each situated role, we analyzed the users’ responses for how frequently they would like to experience the roles. We looked at the midwives’ and obstetricians’ answers separately.</p>
          <p><xref ref-type="table" rid="table6">Tables 6</xref> and <xref ref-type="table" rid="table7">7</xref> show the responses of the obstetricians and midwives respectively. The numbers in the table indicate the number of respondents that chose the option.</p>
          <p>To better understand the extent to which different situated roles are wanted, we assigned them to 3 different categories:</p>
          <list list-type="order">
            <list-item>
              <p>Frequently: more than half of the respondents wanted the role to be experienced at least frequently.</p>
            </list-item>
            <list-item>
              <p>Occasionally: more than half of the respondents wanted the role to be experienced at least occasionally.</p>
            </list-item>
            <list-item>
              <p>Rarely: more than half of the respondents wanted to experience the role rarely at most.</p>
            </list-item>
          </list>
          <p>The extent to which the respondents want to experience the situated roles is shown in <xref ref-type="table" rid="table8">Table 8</xref>.</p>
          <table-wrap position="float" id="table6">
            <label>Table 6</label>
            <caption>
              <p>The desired frequency of experiencing the situated roles as reported by the obstetricians. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="33*"/>
              <col width="37*"/>
              <col width="50*"/>
              <col width="37*"/>
              <col width="27*"/>
              <col width="27*"/>
              <col width="46*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Very frequently (n)</td>
                  <td>Frequently (n)</td>
                  <td>Occasionally (n)</td>
                  <td>Rarely (n)</td>
                  <td>Very rarely (n)</td>
                  <td>Not at all (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Wingman</td>
                  <td>0</td>
                  <td>3 (O2, O3, O5)</td>
                  <td>2 (O1, O4)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Accomplice</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (O1, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>3 (O2, O3, O4)</td>
                </tr>
                <tr valign="top">
                  <td>Third wheel</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (O2)</td>
                  <td>0</td>
                  <td>4 (O1, O3, O4, O5)</td>
                </tr>
                <tr valign="top">
                  <td>Bouncer</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>5 (O1, O2, O3, O4, O5)</td>
                </tr>
                <tr valign="top">
                  <td>Messenger</td>
                  <td>2 (O2, O3)</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Summarizer</td>
                  <td>2 (O2, O3)</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Assistant</td>
                  <td>0</td>
                  <td>5 (O1, O2, O3, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Gossip</td>
                  <td>0</td>
                  <td>0</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>1 (O2)</td>
                  <td>1 (O3)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Alien</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (O4, O5)</td>
                  <td>2 (O2, O3)</td>
                  <td>1 (O1)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Bureaucrat</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (O5)</td>
                  <td>1 (O2)</td>
                  <td>1 (O1)</td>
                  <td>2 (O3, O4)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table7">
            <label>Table 7</label>
            <caption>
              <p>The desired frequency of experiencing the situated roles as reported by the midwives. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="6" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="32*"/>
              <col width="45*"/>
              <col width="38*"/>
              <col width="41*"/>
              <col width="27*"/>
              <col width="32*"/>
              <col width="42*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Very frequently (n)</td>
                  <td>Frequently (n)</td>
                  <td>Occasionally (n)</td>
                  <td>Rarely (n)</td>
                  <td>Very rarely (n)</td>
                  <td>Not at all (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Wingman</td>
                  <td>0</td>
                  <td>2 (M2, M5)</td>
                  <td>5 (M1, M3, M4, M6, M7)</td>
                  <td>1 (M8)</td>
                  <td>0</td>
                  <td>2 (M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Accomplice</td>
                  <td>0</td>
                  <td>1 (M8)</td>
                  <td>4 (M1, M3, M6, M7)</td>
                  <td>2 (M4, M5)</td>
                  <td>2 (M2, M9)</td>
                  <td>1 (M10)</td>
                </tr>
                <tr valign="top">
                  <td>Third wheel</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>1 (M5)</td>
                  <td>9 (M1, M2, M3, M4, M6, M7, M8, M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Bouncer</td>
                  <td>0</td>
                  <td>1 (M1)</td>
                  <td>1 (M8)</td>
                  <td>1 (M7)</td>
                  <td>1 (M2)</td>
                  <td>6 (M3, M4, M5, M6, M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Messenger</td>
                  <td>5 (M2, M3, M4, M5, M7)</td>
                  <td>5 (M1, M6, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Summarizer</td>
                  <td>8 (M2, M3, M4, M5, M6, M7, M8, M10)</td>
                  <td>2 (M1, M9)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Assistant</td>
                  <td>5 (M1, M2, M3, M4, M7)</td>
                  <td>4 (M6, M8, M9, M10)</td>
                  <td>1 (M5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Gossip</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                  <td>6 (M1, M6, M7, M8, M9, M10)</td>
                  <td>4 (M2, M3, M4, M5)</td>
                </tr>
                <tr valign="top">
                  <td>Alien</td>
                  <td>0</td>
                  <td>0</td>
                  <td>2 (M4, M7)</td>
                  <td>4 (M1, M2, M6, M8)</td>
                  <td>4 (M3, M5, M9, M10)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Bureaucrat</td>
                  <td>1 (M8)</td>
                  <td>0</td>
                  <td>1 (M6)</td>
                  <td>3 (M1, M4, M7)</td>
                  <td>2 (M2, M9)</td>
                  <td>3 (M3, M5, M10)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table8">
            <label>Table 8</label>
            <caption>
              <p>The extent to which the respondents want to experience the situated roles.</p>
            </caption>
            <table width="1000" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="300"/>
              <col width="350"/>
              <col width="350"/>
              <thead>
                <tr valign="top">
                  <td>Frequency</td>
                  <td>Obstetricians</td>
                  <td>Midwives</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Frequently</td>
                  <td>Summarizer; messenger; assistant; wingman</td>
                  <td>Summarizer; messenger; assistant</td>
                </tr>
                <tr valign="top">
                  <td>Occasionally</td>
                  <td>Gossip</td>
                  <td>Accomplice; wingman</td>
                </tr>
                <tr valign="top">
                  <td>Rarely</td>
                  <td>Alien; third wheel; bureaucrat; bouncer; accomplice</td>
                  <td>Alien; third wheel; bureaucrat; bouncer; gossip</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <p>We assumed that favorable roles are ones that users want to experience more frequently than they currently do. Unfavorable roles are ones that users want to experience less frequently than they currently do. Accordingly, the summarizer, the messenger, the assistant, and the wingman were regarded as favorable by both obstetricians and midwives. However, the obstetricians wanted to experience the wingman more frequently than the midwives. The alien, the third wheel, the bureaucrat, and the bouncer were regarded as unfavorable by both groups.</p>
          <p>As for the gossip and accomplice, we considered them to be ambivalent. Their ideal frequency is the same as their current frequency. The midwives considered the gossip unfavorable, but the obstetricians wanted to experience it occasionally. Conversely, the obstetricians considered the accomplice unfavorable, but the midwives wanted to experience it occasionally.</p>
        </sec>
        <sec>
          <title>Importance of the Situated Roles</title>
          <p>As mentioned in the Methods section, for favorable roles, we asked the staff about the importance of their presence. For unfavorable roles, we asked about the importance of their absence. The accomplice role was treated as favorable to the prenatal care staff as it is created by them. The gossip role was treated as unfavorable as it denotes a lack of trust in the system.</p>
          <p>To understand the importance of the situated roles, we looked at how much the respondents agreed that the roles’ presence or absence was important. We also looked at the midwives’ and obstetricians’ answers separately. <xref ref-type="table" rid="table9">Tables 9</xref> and <xref ref-type="table" rid="table10">10</xref> show the responses of the obstetricians and midwives, respectively. The numbers in the table indicate the number of respondents that chose the option.</p>
          <p>To better understand the importance of the different situated roles, we assigned them to 4 different categories:</p>
          <list list-type="order">
            <list-item>
              <p>Very important: at least half of the respondents strongly agree that the presence or absence of the role is important.</p>
            </list-item>
            <list-item>
              <p>Important: at least half of the respondents agree that the presence or absence of the role is important.</p>
            </list-item>
            <list-item>
              <p>Somewhat important: at least half of the respondents somewhat agree that the presence or absence of the role is important.</p>
            </list-item>
            <list-item>
              <p>Not important at all: at least half of the respondents disagree that the presence or absence of the role is important.</p>
            </list-item>
          </list>
          <p>The situated roles’ levels of importance are shown in <xref ref-type="table" rid="table11">Table 11</xref>.</p>
          <table-wrap position="float" id="table9">
            <label>Table 9</label>
            <caption>
              <p>The extent to which the obstetricians agree that the situated roles are important. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="61*"/>
              <col width="60*"/>
              <col width="50*"/>
              <col width="44*"/>
              <col width="41*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Strongly agree (n)</td>
                  <td>Agree (n)</td>
                  <td>Somewhat agree (n)</td>
                  <td>Disagree (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Presence of wingman</td>
                  <td>0</td>
                  <td>4 (O2, O3, O4, O5)</td>
                  <td>1 (O1)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of accomplice</td>
                  <td>1 (O1)</td>
                  <td>1 (O5)</td>
                  <td>2 (O3, O4)</td>
                  <td>1 (O2)</td>
                </tr>
                <tr valign="top">
                  <td>Absence of third wheel</td>
                  <td>1 (O3)</td>
                  <td>4 (O1, O2, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of bouncer</td>
                  <td>0</td>
                  <td>1 (O5)</td>
                  <td>1 (O3)</td>
                  <td>3 (O1, O2, O4)</td>
                </tr>
                <tr valign="top">
                  <td>Presence of messenger</td>
                  <td>4 (O1, O2, O3, O4)</td>
                  <td>1 (O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Presence of summarizer</td>
                  <td>4 (O1, O2, O3, O4)</td>
                  <td>1 (O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Presence of assistant</td>
                  <td>2 (O1, O2)</td>
                  <td>3 (O3, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of gossip</td>
                  <td>2 (O2, O3)</td>
                  <td>3 (O1, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of alien</td>
                  <td>5 (O1, O2, O3, O4, O5)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of bureaucrat</td>
                  <td>1 (O4)</td>
                  <td>4 (O1, O2, O3, O5)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table10">
            <label>Table 10</label>
            <caption>
              <p>The extent to which the midwives agree that the situated roles are important. Participant identifier listed in parentheses.</p>
            </caption>
            <table width="100%" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="46*"/>
              <col width="75*"/>
              <col width="53*"/>
              <col width="53*"/>
              <col width="30*"/>
              <thead>
                <tr valign="top">
                  <td>Situated role</td>
                  <td>Strongly agree (n)</td>
                  <td>Agree (n)</td>
                  <td>Somewhat agree (n)</td>
                  <td>Disagree (n)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Presence of wingman</td>
                  <td>1 (M5)</td>
                  <td>7 (M1, M2, M3, M4, M6, M7, M8)</td>
                  <td>2 (M9, M10)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of accomplice</td>
                  <td>0</td>
                  <td>4 (M3, M5, M6, M8)</td>
                  <td>6 (M1, M2, M4, M7, M9, M10)</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of third wheel</td>
                  <td>8 (M1, M2, M3, M4, M5, M6, M8, M10)</td>
                  <td>2 (M7, M9)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of bouncer</td>
                  <td>0</td>
                  <td>5 (M1, M2, M3, M5, M6)</td>
                  <td>3 (M4, M7, M8)</td>
                  <td>2 (M9, M10)</td>
                </tr>
                <tr valign="top">
                  <td>Presence of messenger</td>
                  <td>10 (M1, M2, M3, M4, M5, M6, M7, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Presence of summarizer</td>
                  <td>10 (M1, M2, M3, M4, M5, M6, M7, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Presence of assistant</td>
                  <td>5 (M1, M2, M3, M4, M7)</td>
                  <td>5 (M5, M6, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of gossip</td>
                  <td>6 (M1, M2, M3, M4, M5, M9)</td>
                  <td>4 (M6, M7, M8, M10)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of alien</td>
                  <td>10 (M1, M2, M3, M4, M5, M6, M7, M8, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
                <tr valign="top">
                  <td>Absence of bureaucrat</td>
                  <td>6 (M1, M3, M5, M6, M7, M8)</td>
                  <td>4 (M2, M4, M9, M10)</td>
                  <td>0</td>
                  <td>0</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <table-wrap position="float" id="table11">
            <label>Table 11</label>
            <caption>
              <p>The situated roles’ levels of importance.</p>
            </caption>
            <table width="1000" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="300"/>
              <col width="350"/>
              <col width="350"/>
              <thead>
                <tr valign="top">
                  <td>Importance</td>
                  <td>Obstetricians</td>
                  <td>Midwives</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Very important</td>
                  <td>Presence of summarizer; presence of messenger; presence of assistant; absence of alien</td>
                  <td>Presence of summarizer; presence of messenger; presence of assistant; absence of alien; absence of third wheel; absence of bureaucrat; absence of gossip</td>
                </tr>
                <tr valign="top">
                  <td>Important</td>
                  <td>Presence of wingman; absence of third wheel; absence of bureaucrat; absence of gossip</td>
                  <td>Presence of wingman</td>
                </tr>
                <tr valign="top">
                  <td>Somewhat important</td>
                  <td>Presence of accomplice</td>
                  <td>Presence of accomplice; absence of bouncer</td>
                </tr>
                <tr valign="top">
                  <td>Not important at all</td>
                  <td>Absence of bouncer</td>
                  <td>—<sup>a</sup></td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table11fn1">
                <p><sup>a</sup>Not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>We identified 10 situated roles that EMR systems play in Japanese prenatal care. On the basis of the feedback of the obstetricians and the midwives, we validated the roles and understood the users’ wants and priorities regarding them.</p>
        <p>Our results offer multiple EMR redesign opportunities in prenatal care. <xref ref-type="fig" rid="figure4">Figures 4</xref> and <xref ref-type="fig" rid="figure5">5</xref> can serve as redesign guidelines for satisfying the wants of the obstetricians and the midwives, respectively.</p>
        <p>To improve the usability and usefulness of the EMR systems, designers can amplify the favorable roles (the roles wanted to be experienced frequently) and minimize the unfavorable roles (the roles wanted to be experienced rarely). To align their design activities with the priorities of the users, designers can focus on the roles reported as important by the users. To increase the impact of their redesigns, the designers can focus on minimizing unfavorable roles that are frequently experienced, for example, the alien, or amplifying favorable roles that are less frequently experienced, for example, the wingman.</p>
        <p>The gossip and the accomplice roles seem to be ambivalent. The midwives want to clearly document sensitive psychosocial information in most cases, whereas the obstetricians seem to be more hesitant. Conversely, the midwives want to use the EMR system occasionally to have a moment to think, whereas obstetricians prefer to rarely do so.</p>
        <p>Through the gossip role, our study highlighted the challenge of documenting sensitive psychosocial information in EMR systems. A reason for not documenting such information could be that psychosocial information is viewed as <italic>subjective</italic> and sometimes <italic>not legitimate enough</italic> to be placed in a permanent medical record [<xref ref-type="bibr" rid="ref38">38</xref>]. Conversely, when such information is documented, it may be documented in vague and ambiguous ways. This behavior may be attributed to the health care providers’ distrust in the security of EMR systems or their unfamiliarity with the laws governing the access and use of health care data. It is important to note that in Japan, one in every 20 women may experience domestic violence (DV) during pregnancy [<xref ref-type="bibr" rid="ref39">39</xref>]. Furthermore, pregnant Japanese women want their psychosocial information to be documented in detail in their EMRs [<xref ref-type="bibr" rid="ref40">40</xref>]. Therefore, clearly documenting sensitive information is needed to (1) respect the preferences of the pregnant women and (2) address psychosocial issues, such as DV, that are not easily disclosed or discussed [<xref ref-type="bibr" rid="ref41">41</xref>]. Further investigations should be conducted to understand if the gossip role is a result of the EMR system’s design as it might create a feeling of distrust for the medical staff, or if it is a result of the medical staff’s uncertainty regarding the laws governing health care data.</p>
        <p>As for the accomplice role, it is created by the staff to pause the conversation with the pregnant women. In this case, the reasons behind this role should be further understood as it presents a possible conflict between the needs of health care providers and patients and raises an important question: whose needs should we consider and prioritize when designing EMR systems?</p>
        <p>Our results also suggest that the EMR system is viewed first and foremost as a tool for supporting the clinical workflow. The messenger, summarizer, assistant, and alien were very important situated roles for both user groups. These results shed light on <italic>clear</italic> redesign targets, ones that improve the EMR system’s capabilities as a tool to support the clinical process.</p>
        <p>However, the EMR system’s roles as a tool that supports the communication with the pregnant women seems secondary, as shown through the bouncer role. Both midwives and obstetricians do not think it is important that the pregnant women see the EMR screen. Conversely, they think it is important to use the EMR screen as an explanation support tool. Further research is needed to understand the attitudes of the prenatal care providers regarding the EMR system as a communication support tool.</p>
        <p>A previous study found no difference between the perceptions of physicians and nurses regarding EMR systems [<xref ref-type="bibr" rid="ref13">13</xref>]. Even though the experiences and wants of the midwives and the obstetricians overlapped for certain situated roles (the messenger, the summarizer, the assistant, and the alien), they differed for others. Our results imply that the users’ experiences with the EMR system, and their aspirations regarding it, are related to the nature and purpose of their job. Aligning with previous findings in Japanese prenatal care settings [<xref ref-type="bibr" rid="ref22">22</xref>], these results highlight the different responsibilities that obstetricians and midwives have in prenatal care, as it can be argued that the obstetricians’ focus is clinical while the midwives’ focus is more psychosocial. Moreover, in OB-led checkups, the midwife assists the obstetrician instead of being the main caretaker. Consequently, the pregnant woman’s chair faces the obstetrician’s desk. The desk placement in this case might affect the situated roles exhibited by the EMR system.</p>
        <p>Accordingly, EMR redesign efforts should take into consideration not only the prenatal care context but also the different types of EMR users in this context. One direction to explore is having 2 different EMR systems—one for the midwives and another for the obstetricians—rather than having a general prenatal care EMR system. In this case, we need to ensure that the use of different systems does not hinder collaborative care [<xref ref-type="bibr" rid="ref42">42</xref>].</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>The situated roles of the electronic medical record system for the obstetricians.</p>
          </caption>
          <graphic xlink:href="humanfactors_v6i3e13812_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>The situated roles of the electronic medical record system for the midwives.</p>
          </caption>
          <graphic xlink:href="humanfactors_v6i3e13812_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The first limitation of this study is the number of observations. In addition, the obstetricians that we observed were all males. As the communication style may differ substantially depending on the obstetrician and pregnant woman, more situated roles may be identified through additional observations that include female obstetricians.</p>
        <p>Moreover, our results may not be generalizable. The readers will have to assess the degrees to which our results can be transferred to health care or cultural settings of their interest.</p>
        <p>In other respects, it would be valuable to quantify the number of occurrences relating to a situated role. Owing to the limited number of field observations that we were able to conduct, our analysis aimed to provide a purely qualitative and nuanced description of the situated roles, without counting the frequency of occurrences. Quantifying the occurrences is particularly valuable to evaluate redesign activities. To evaluate the success of a redesign activity, designers may need to objectively quantify and compare the frequency of certain occurrences in the pre-redesign and postredesign phases. To facilitate the redesign evaluation process, our future work will look into ways to automatically and objectively quantify the occurrences without the need for manual data analysis.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>By looking at how the prenatal care providers appropriated the EMR system, we identified 10 situated roles that EMR systems play in Japanese prenatal care settings. We also identified the wants and the priorities of the users regarding the EMR system’s situated roles.</p>
        <p>We found that prenatal care providers mainly use the EMR system as a summarizer to have a quick summary of the pregnancy course, as a messenger to communicate patient information across staff rotations, and as an assistant to prepare for the checkups. They would like to use the EMR system as a tool to support their explanations to the pregnant women more frequently. We also found that the providers may use the EMR system as an accomplice to pause communication with the pregnant women. Interestingly, they do not think it is important for the pregnant women to view the EMR screen during the checkups. Our results further highlighted the lack of trust in the security of EMR systems and how it can negatively affect prenatal care provision.</p>
        <p>In other respects, we found a difference in the experiences and attitudes of the obstetricians and the midwives regarding the use of the EMR system. These findings imply the need for different EMR system designs to better fit the job descriptions and tasks of the different user groups.</p>
        <p>Our study serves as an example to show how EMR systems can be redesigned from appropriation. Our results could be used to redesign EMR systems to better fit the contextual needs of their users in prenatal care.</p>
      </sec>
    </sec>
  </body>
  <back>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">DV</term>
          <def>
            <p>domestic violence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">MCH</term>
          <def>
            <p>maternal and child health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MW-led</term>
          <def>
            <p>midwife-led</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">OB-led</term>
          <def>
            <p>obstetrician-led</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research was supported by the Leading Graduate Schools Program <italic>Collaborative Graduate Program in Design</italic>, Kyoto University, Japan. The authors would like to thank Professor Kumiyo Nakakoji for her valued input and insights. The authors would also like to thank all the participants and collaborators of this project.</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>Santiago</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>Q</given-names>
          </name>
          <name name-style="western">
            <surname>Gagliano</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Judge</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Hamann</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Middleton</surname>
            <given-names>B</given-names>
          </name>
        </person-group>
        <article-title>Improving EMR usability: a method for both discovering and prioritizing improvements in EMR workflows based on human factors engineering</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2006</year>  
        <fpage>1086</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/17238705"/>
        </comment>  
        <pub-id pub-id-type="medline">17238705</pub-id>
        <pub-id pub-id-type="pii">86055</pub-id>
        <pub-id pub-id-type="pmcid">PMC1839600</pub-id></nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Sittig</surname>
            <given-names>DF</given-names>
          </name>
          <name name-style="western">
            <surname>Wright</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Ash</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>New unintended adverse consequences of electronic health records</article-title>
        <source>Yearb Med Inform</source>  
        <year>2016</year>  
        <month>11</month>  
        <day>10</day>  
        <issue>1</issue>  
        <fpage>7</fpage>  
        <lpage>12</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.15265/IY-2016-023"/>
        </comment>  
        <pub-id pub-id-type="doi">10.15265/IY-2016-023</pub-id>
        <pub-id pub-id-type="medline">27830226</pub-id>
        <pub-id pub-id-type="pii">me2016-023</pub-id>
        <pub-id pub-id-type="pmcid">PMC5171566</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kruse</surname>
            <given-names>CS</given-names>
          </name>
          <name name-style="western">
            <surname>Kothman</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Anerobi</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Abanaka</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Adoption factors of the electronic health record: a systematic review</article-title>
        <source>JMIR Med Inform</source>  
        <year>2016</year>  
        <month>06</month>  
        <day>1</day>  
        <volume>4</volume>  
        <issue>2</issue>  
        <fpage>e19</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://medinform.jmir.org/2016/2/e19/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/medinform.5525</pub-id>
        <pub-id pub-id-type="medline">27251559</pub-id>
        <pub-id pub-id-type="pii">v4i2e19</pub-id>
        <pub-id pub-id-type="pmcid">PMC4909978</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>Aarts</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Ash</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Berg</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Extending the understanding of computerized physician order entry: implications for professional collaboration, workflow and quality of care</article-title>
        <source>Int J Med Inform</source>  
        <year>2007</year>  
        <month>06</month>  
        <volume>76</volume>  
        <issue>Suppl 1</issue>  
        <fpage>S4</fpage>  
        <lpage>13</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2006.05.009</pub-id>
        <pub-id pub-id-type="medline">16798068</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(06)00126-2</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>Ash</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Gorman</surname>
            <given-names>PN</given-names>
          </name>
          <name name-style="western">
            <surname>Lavelle</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Payne</surname>
            <given-names>TH</given-names>
          </name>
          <name name-style="western">
            <surname>Massaro</surname>
            <given-names>TA</given-names>
          </name>
          <name name-style="western">
            <surname>Frantz</surname>
            <given-names>GL</given-names>
          </name>
          <name name-style="western">
            <surname>Lyman</surname>
            <given-names>JA</given-names>
          </name>
        </person-group>
        <article-title>A cross-site qualitative study of physician order entry</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2003</year>  
        <volume>10</volume>  
        <issue>2</issue>  
        <fpage>188</fpage>  
        <lpage>200</lpage>  
        <pub-id pub-id-type="doi">10.1197/jamia.m770</pub-id>
        <pub-id pub-id-type="medline">12595408</pub-id>
        <pub-id pub-id-type="pmcid">PMC150372</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>Blijleven</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Koelemeijer</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Wetzels</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Jaspers</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Workarounds emerging from electronic health record system usage: consequences for patient safety, effectiveness of care, and efficiency of care</article-title>
        <source>JMIR Hum Factors</source>  
        <year>2017</year>  
        <month>10</month>  
        <day>5</day>  
        <volume>4</volume>  
        <issue>4</issue>  
        <fpage>e27</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/2017/4/e27/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/humanfactors.7978</pub-id>
        <pub-id pub-id-type="medline">28982645</pub-id>
        <pub-id pub-id-type="pii">v4i4e27</pub-id>
        <pub-id pub-id-type="pmcid">PMC5649044</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Carayon</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Karsh</surname>
            <given-names>BT</given-names>
          </name>
          <name name-style="western">
            <surname>Cartmill</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Hoonakker</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Hundt</surname>
            <given-names>AS</given-names>
          </name>
          <name name-style="western">
            <surname>Krueger</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Thuemling</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Wetterneck</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Brennan</surname>
            <given-names>PF</given-names>
          </name>
          <name name-style="western">
            <surname>Walker</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Alyousef</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Boddipalli</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Capista</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Donato</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Peña</surname>
            <given-names>MC</given-names>
          </name>
          <name name-style="western">
            <surname>Ollila</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <source>AHRQ Health IT</source>  
        <year>2010</year>  
        <month>07</month>  
        <access-date>2019-06-28</access-date>
        <comment>Incorporating Health IT Into Workflow Redesign: Request for Information Summary Report 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://healthit.ahrq.gov/sites/default/files/docs/citation/workflowredesignrfi.pdf">https://healthit.ahrq.gov/sites/default/files/docs/citation/workflowredesignrfi.pdf</ext-link></comment> </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>Cresswell</surname>
            <given-names>KM</given-names>
          </name>
          <name name-style="western">
            <surname>Worth</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sheikh</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Integration of a nationally procured electronic health record system into user work practices</article-title>
        <source>BMC Med Inform Decis Mak</source>  
        <year>2012</year>  
        <month>03</month>  
        <day>8</day>  
        <volume>12</volume>  
        <fpage>15</fpage>  
        <pub-id pub-id-type="doi">10.1186/1472-6947-12-15</pub-id>
        <pub-id pub-id-type="medline">22400978</pub-id>
        <pub-id pub-id-type="pii">1472-6947-12-15</pub-id>
        <pub-id pub-id-type="pmcid">PMC3313868</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Marcu</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Dey</surname>
            <given-names>AK</given-names>
          </name>
          <name name-style="western">
            <surname>Kiesler</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Designing for Collaborative Reflection</article-title>
        <source>Proceedings of the 8th International Conference on Pervasive Computing Technologies for Healthcare</source>  
        <year>2014</year>  
        <conf-name>PervasiveHealth'14</conf-name>
        <conf-date>May 20-23, 2014</conf-date>
        <conf-loc>Oldenburg, Germany</conf-loc>
        <fpage>9</fpage>  
        <lpage>16</lpage>  
        <pub-id pub-id-type="doi">10.4108/icst.pervasivehealth.2014.254987</pub-id></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Miller</surname>
            <given-names>RH</given-names>
          </name>
          <name name-style="western">
            <surname>Sim</surname>
            <given-names>I</given-names>
          </name>
        </person-group>
        <article-title>Physicians' use of electronic medical records: barriers and solutions</article-title>
        <source>Health Aff (Millwood)</source>  
        <year>2004</year>  
        <volume>23</volume>  
        <issue>2</issue>  
        <fpage>116</fpage>  
        <lpage>26</lpage>  
        <pub-id pub-id-type="doi">10.1377/hlthaff.23.2.116</pub-id>
        <pub-id pub-id-type="medline">15046136</pub-id></nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rose</surname>
            <given-names>AF</given-names>
          </name>
          <name name-style="western">
            <surname>Schnipper</surname>
            <given-names>JL</given-names>
          </name>
          <name name-style="western">
            <surname>Park</surname>
            <given-names>ER</given-names>
          </name>
          <name name-style="western">
            <surname>Poon</surname>
            <given-names>EG</given-names>
          </name>
          <name name-style="western">
            <surname>Li</surname>
            <given-names>Q</given-names>
          </name>
          <name name-style="western">
            <surname>Middleton</surname>
            <given-names>B</given-names>
          </name>
        </person-group>
        <article-title>Using qualitative studies to improve the usability of an EMR</article-title>
        <source>J Biomed Inform</source>  
        <year>2005</year>  
        <month>02</month>  
        <volume>38</volume>  
        <issue>1</issue>  
        <fpage>51</fpage>  
        <lpage>60</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(04)00152-2"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2004.11.006</pub-id>
        <pub-id pub-id-type="medline">15694885</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(04)00152-2</pub-id></nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zadvinskis</surname>
            <given-names>IM</given-names>
          </name>
          <name name-style="western">
            <surname>Garvey</surname>
            <given-names>SJ</given-names>
          </name>
          <name name-style="western">
            <surname>Yen</surname>
            <given-names>PY</given-names>
          </name>
        </person-group>
        <article-title>Nurses' experience with health information technology: longitudinal qualitative study</article-title>
        <source>JMIR Med Inform</source>  
        <year>2018</year>  
        <month>06</month>  
        <day>26</day>  
        <volume>6</volume>  
        <issue>2</issue>  
        <fpage>e38</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://medinform.jmir.org/2018/2/e38/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/medinform.8734</pub-id>
        <pub-id pub-id-type="medline">29945862</pub-id>
        <pub-id pub-id-type="pii">v6i2e38</pub-id>
        <pub-id pub-id-type="pmcid">PMC6043728</pub-id></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Clarke</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Belden</surname>
            <given-names>JL</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>MS</given-names>
          </name>
        </person-group>
        <article-title>How does learnability of primary care resident physicians increase after seven months of using an electronic health record? A longitudinal study</article-title>
        <source>JMIR Hum Factors</source>  
        <year>2016</year>  
        <month>02</month>  
        <day>15</day>  
        <volume>3</volume>  
        <issue>1</issue>  
        <fpage>e9</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://humanfactors.jmir.org/2016/1/e9/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/humanfactors.4601</pub-id>
        <pub-id pub-id-type="medline">27025237</pub-id>
        <pub-id pub-id-type="pii">v3i1e9</pub-id>
        <pub-id pub-id-type="pmcid">PMC4811662</pub-id></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rathert</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Porter</surname>
            <given-names>TH</given-names>
          </name>
          <name name-style="western">
            <surname>Mittler</surname>
            <given-names>JN</given-names>
          </name>
          <name name-style="western">
            <surname>Fleig-Palmer</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Seven years after meaningful use: physicians' and nurses' experiences with electronic health records</article-title>
        <source>Health Care Manage Rev</source>  
        <year>2019</year>  
        <volume>44</volume>  
        <issue>1</issue>  
        <fpage>30</fpage>  
        <lpage>40</lpage>  
        <pub-id pub-id-type="doi">10.1097/HMR.0000000000000168</pub-id>
        <pub-id pub-id-type="medline">28614166</pub-id></nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kruse</surname>
            <given-names>CS</given-names>
          </name>
          <name name-style="western">
            <surname>Mileski</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Vijaykumar</surname>
            <given-names>AG</given-names>
          </name>
          <name name-style="western">
            <surname>Viswanathan</surname>
            <given-names>SV</given-names>
          </name>
          <name name-style="western">
            <surname>Suskandla</surname>
            <given-names>U</given-names>
          </name>
          <name name-style="western">
            <surname>Chidambaram</surname>
            <given-names>Y</given-names>
          </name>
        </person-group>
        <article-title>Impact of electronic health records on long-term care facilities: systematic review</article-title>
        <source>JMIR Med Inform</source>  
        <year>2017</year>  
        <month>09</month>  
        <day>29</day>  
        <volume>5</volume>  
        <issue>3</issue>  
        <fpage>e35</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://medinform.jmir.org/2017/3/e35/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/medinform.7958</pub-id>
        <pub-id pub-id-type="medline">28963091</pub-id>
        <pub-id pub-id-type="pii">v5i3e35</pub-id>
        <pub-id pub-id-type="pmcid">PMC5640822</pub-id></nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Morita</surname>
            <given-names>PP</given-names>
          </name>
          <name name-style="western">
            <surname>Cafazzo</surname>
            <given-names>JA</given-names>
          </name>
        </person-group>
        <article-title>Challenges and paradoxes of human factors in health technology design</article-title>
        <source>JMIR Hum Factors</source>  
        <year>2016</year>  
        <month>03</month>  
        <day>1</day>  
        <volume>3</volume>  
        <issue>1</issue>  
        <fpage>e11</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/2016/1/e11/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/humanfactors.4653</pub-id>
        <pub-id pub-id-type="medline">27025862</pub-id>
        <pub-id pub-id-type="pii">v3i1e11</pub-id>
        <pub-id pub-id-type="pmcid">PMC4811664</pub-id></nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Carroll</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Completing Design in Use: Closing the Appropriation Cycle</article-title>
        <source>Proceedings of the 13th European Conference on Information Systems</source>  
        <year>2004</year>  
        <conf-name>ECSCW'04</conf-name>
        <conf-date>June 14-16, 2004</conf-date>
        <conf-loc>Turku, Finland</conf-loc></nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Oakley</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Enkin</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Chalmers</surname>
            <given-names>I</given-names>
          </name>
        </person-group>
        <article-title>The origins and development of antenatal care</article-title>
        <source>Effectiveness and Satisfaction in Antenatal Care</source>  
        <year>1982</year>  
        <publisher-loc>St. Bermondsey, London</publisher-loc>
        <publisher-name>Mac Keith Press</publisher-name>
        <fpage>1</fpage>  
        <lpage>21</lpage> </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kawaguchi</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Matsumoto</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Akira</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Ishitani</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Iwasaku</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Ueda</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Okagaki</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Okano</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Oki</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Koga</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Kido</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Kurabayashi</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Kuribayashi</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Sato</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Shiina</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Takai</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Tanimura</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Chaki</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Terauchi</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Todo</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Noguchi</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Nose-Ogura</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Baba</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Hirasawa</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Fujii</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Fujii</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Maruyama</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Miyagi</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Yanagida</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Yoshino</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Iwashita</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Maeda</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Minegishi</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Kobayashi</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Guidelines for office gynecology in Japan: Japan Society of Obstetrics and Gynecology (JSOG) and Japan Association of Obstetricians and Gynecologists (JAOG) 2017 edition</article-title>
        <source>J Obstet Gynaecol Res</source>  
        <year>2019</year>  
        <month>04</month>  
        <volume>45</volume>  
        <issue>4</issue>  
        <fpage>766</fpage>  
        <lpage>86</lpage>  
        <pub-id pub-id-type="doi">10.1111/jog.13831</pub-id>
        <pub-id pub-id-type="medline">30675969</pub-id></nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Unno</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>The perinatal health care in Japan</article-title>
        <source>Japan Med Assoc J</source>  
        <year>2011</year>  
        <volume>54</volume>  
        <issue>4</issue>  
        <fpage>234</fpage>  
        <lpage>40</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.med.or.jp/english/journal/pdf/2011_04/234_240.pdf"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nakamura</surname>
            <given-names>Y</given-names>
          </name>
        </person-group>
        <article-title>Maternal and child health handbook in Japan</article-title>
        <source>Japan Med Assoc J</source>  
        <year>2010</year>  
        <volume>53</volume>  
        <issue>4</issue>  
        <fpage>259</fpage>  
        <lpage>65</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.med.or.jp/english/journal/pdf/2010_04/259_265.pdf"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Iida</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Horiuchi</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Nagamori</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>A comparison of midwife-led care versus obstetrician-led care for low-risk women in Japan</article-title>
        <source>Women Birth</source>  
        <year>2014</year>  
        <month>09</month>  
        <volume>27</volume>  
        <issue>3</issue>  
        <fpage>202</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.wombi.2014.05.001</pub-id>
        <pub-id pub-id-type="medline">24906495</pub-id>
        <pub-id pub-id-type="pii">S1871-5192(14)00035-3</pub-id></nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kaneko</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Onozuka</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Shibuta</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Hagihara</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Impact of electronic medical records (EMRs) on hospital productivity in Japan</article-title>
        <source>Int J Med Inform</source>  
        <year>2018</year>  
        <month>12</month>  
        <volume>118</volume>  
        <fpage>36</fpage>  
        <lpage>43</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.07.008</pub-id>
        <pub-id pub-id-type="medline">30153919</pub-id>
        <pub-id pub-id-type="pii">S1386-5056(18)30615-4</pub-id></nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
        <source>Prime Minister of Japan and His Cabinet</source>  
        <year>2015</year>  
        <access-date>2019-02-10</access-date>
        <comment>[Promotion of ICT in the Medical Fields] 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="http://www.kantei.go.jp/jp/singi/keizaisaisei/kadaibetu/dai6/siryou1.pdf">http://www.kantei.go.jp/jp/singi/keizaisaisei/kadaibetu/dai6/siryou1.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="7667TArYi"/></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>Fleming</surname>
            <given-names>EM</given-names>
          </name>
        </person-group>
        <article-title>Artifact study: a proposed model</article-title>
        <source>Winterthur Portf</source>  
        <year>1974</year>  
        <volume>9</volume>  
        <fpage>153</fpage>  
        <lpage>73</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/1180572?seq=1#page_scan_tab_contents"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1086/495828</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>DeSanctis</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Poole</surname>
            <given-names>MS</given-names>
          </name>
        </person-group>
        <article-title>Capturing the complexity in advanced technology use: adaptive structuration theory</article-title>
        <source>Organ Sci</source>  
        <year>1994</year>  
        <month>05</month>  
        <volume>5</volume>  
        <issue>2</issue>  
        <fpage>121</fpage>  
        <lpage>47</lpage>  
        <pub-id pub-id-type="doi">10.1287/orsc.5.2.121</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Orlikowski</surname>
            <given-names>WJ</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Ackerman</surname>
            <given-names>MS</given-names>
          </name>
          <name name-style="western">
            <surname>Halverson</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Erickson</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Kellogg</surname>
            <given-names>WA</given-names>
          </name>
        </person-group>
        <article-title>Using technology and constituting structures: a practice lens for studying technology in organizations</article-title>
        <source>Resources, Co-Evolution and Artifacts</source>  
        <year>2008</year>  
        <publisher-loc>London</publisher-loc>
        <publisher-name>Springer</publisher-name>
        <fpage>254</fpage>  
        <lpage>308</lpage> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Dourish</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>The appropriation of interactive technologies: some lessons from placeless documents</article-title>
        <source>Comput Support Coop Work</source>  
        <year>2003</year>  
        <month>12</month>  
        <volume>12</volume>  
        <issue>4</issue>  
        <fpage>465</fpage>  
        <lpage>90</lpage>  
        <pub-id pub-id-type="doi">10.1023/A:1026149119426</pub-id></nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Griffith</surname>
            <given-names>TL</given-names>
          </name>
        </person-group>
        <article-title>Technology features as triggers for sensemaking</article-title>
        <source>Acad Manage Rev</source>  
        <year>1999</year>  
        <month>07</month>  
        <volume>24</volume>  
        <issue>3</issue>  
        <fpage>472</fpage>  
        <lpage>88</lpage>  
        <pub-id pub-id-type="doi">10.2307/259137</pub-id></nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Majchrzak</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rice</surname>
            <given-names>RE</given-names>
          </name>
          <name name-style="western">
            <surname>Malhotra</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>King</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Ba</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Technology adaptation: the case of a computer-supported inter-organizational virtual team</article-title>
        <source>MIS Q</source>  
        <year>2000</year>  
        <month>12</month>  
        <volume>24</volume>  
        <issue>4</issue>  
        <fpage>569</fpage>  
        <lpage>600</lpage>  
        <pub-id pub-id-type="doi">10.2307/3250948</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Fischer</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <person-group person-group-type="editor">
          <name name-style="western">
            <surname>Barbosa</surname>
            <given-names>SD</given-names>
          </name>
          <name name-style="western">
            <surname>Breitman</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Exploring richer ecologies between designers and users</article-title>
        <source>Conversations Around Semiotic Engineering</source>  
        <year>2017</year>  
        <publisher-loc>New York City</publisher-loc>
        <publisher-name>Springer</publisher-name>
        <fpage>21</fpage>  
        <lpage>9</lpage> </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Krischkowsky</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Maurer</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Tscheligi</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Captology and Technology Appropriation: Unintended Use as a Source for Designing Persuasive Technologies</article-title>
        <source>Proceedings of the 11th International Conference on Persuasive Technology</source>  
        <year>2016</year>  
        <conf-name>PERSUASIVE'16</conf-name>
        <conf-date>April 5-7, 2016</conf-date>
        <conf-loc>Salzburg, Austria</conf-loc>
        <fpage>78</fpage>  
        <lpage>83</lpage>  
        <pub-id pub-id-type="doi">10.1007/978-3-319-31510-2_7</pub-id></nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>van der Vegte</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>Kitamura</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Koji</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Mizoguchi</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>Coping With Unintended Behavior of Users and Products: Ontological Modelling of Product Functionality and Use</article-title>
        <source>Proceedings of the International Design Engineering Technical Conferences and Computers and Information in Engineering Conference</source>  
        <year>2004</year>  
        <conf-name>ASME'04</conf-name>
        <conf-date>September 28–October 2, 2004</conf-date>
        <conf-loc>Salt Lake City, Utah</conf-loc>
        <fpage>683</fpage>  
        <lpage>92</lpage>  
        <pub-id pub-id-type="doi">10.1115/DETC2004-57720</pub-id></nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chase</surname>
            <given-names>DA</given-names>
          </name>
          <name name-style="western">
            <surname>Ash</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Cohen</surname>
            <given-names>DJ</given-names>
          </name>
          <name name-style="western">
            <surname>Hall</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Olson</surname>
            <given-names>GM</given-names>
          </name>
          <name name-style="western">
            <surname>Dorr</surname>
            <given-names>DA</given-names>
          </name>
        </person-group>
        <article-title>The EHR's roles in collaboration between providers: a qualitative study</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2014</year>  
        <volume>2014</volume>  
        <fpage>1718</fpage>  
        <lpage>27</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/25954444"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2015.08.006</pub-id>
        <pub-id pub-id-type="medline">25954444</pub-id>
        <pub-id pub-id-type="pmcid">PMC4419964</pub-id></nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>de Lusignan</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Pearce</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Kumarapeli</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Stavropoulou</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Kushniruk</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Sheikh</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Shachak</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Mendis</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Reporting observational studies of the use of information technology in the clinical consultation. A position statement from the IMIA primary health care informatics working group (IMIA PCI WG)</article-title>
        <source>Yearb Med Inform</source>  
        <year>2011</year>  
        <volume>6</volume>  
        <fpage>39</fpage>  
        <lpage>47</lpage>  
        <pub-id pub-id-type="doi">10.1055/s-0038-1638735</pub-id>
        <pub-id pub-id-type="medline">21938323</pub-id>
        <pub-id pub-id-type="pii">me11010039</pub-id></nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
        <source>Provalis Research</source>  
        <year>2019</year>  
        <access-date>2019-02-10</access-date>
        <comment>Qualitative Data Analysis Software 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://provalisresearch.com/products/qualitative-data-analysis-software/">https://provalisresearch.com/products/qualitative-data-analysis-software/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="7668Iqu49"/></comment> </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Braun</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Clarke</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Hayfield</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Terry</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Thematic analysis</article-title>
        <source>Handbook of Research Methods in Health Social Sciences</source>  
        <year>2019</year>  
        <publisher-loc>United States</publisher-loc>
        <publisher-name>Springer</publisher-name>
        <fpage>843</fpage>  
        <lpage>60</lpage> </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zhou</surname>
            <given-names>X</given-names>
          </name>
          <name name-style="western">
            <surname>Ackerman</surname>
            <given-names>MS</given-names>
          </name>
          <name name-style="western">
            <surname>Zheng</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>Doctors and Psychosocial Information: Records and Reuse in Inpatient Care</article-title>
        <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>  
        <year>2010</year>  
        <conf-name>CHI'10</conf-name>
        <conf-date>April 10-15, 2010</conf-date>
        <conf-loc>Atlanta, Georgia, USA</conf-loc>
        <fpage>1767</fpage>  
        <lpage>76</lpage>  
        <pub-id pub-id-type="doi">10.1145/1753326.1753592</pub-id></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Suzuki</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Eto</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Domestic violence against women during pregnancy in Japan</article-title>
        <source>J Matern Fetal Neonatal Med</source>  
        <year>2017</year>  
        <month>02</month>  
        <volume>30</volume>  
        <issue>4</issue>  
        <fpage>497</fpage>  
        <lpage>8</lpage>  
        <pub-id pub-id-type="doi">10.1080/14767058.2016.1177505</pub-id>
        <pub-id pub-id-type="medline">27071842</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>Helou</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Abou-Khalil</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Yamamoto</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Kondoh</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Tamura</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Hiragi</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Sugiyama</surname>
            <given-names>O</given-names>
          </name>
          <name name-style="western">
            <surname>Okamoto</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Nambu</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Kuroda</surname>
            <given-names>T</given-names>
          </name>
        </person-group>
        <article-title>Understanding the EMR-related experiences of pregnant Japanese women to redesign antenatal care EMR systems</article-title>
        <source>Inform</source>  
        <year>2019</year>  
        <month>04</month>  
        <day>4</day>  
        <volume>6</volume>  
        <issue>2</issue>  
        <fpage>15</fpage>  
        <pub-id pub-id-type="doi">10.3390/informatics6020015</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>Nagae</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Dancy</surname>
            <given-names>BL</given-names>
          </name>
        </person-group>
        <article-title>Japanese women's perceptions of intimate partner violence (IPV)</article-title>
        <source>J Interpers Violence</source>  
        <year>2010</year>  
        <month>04</month>  
        <volume>25</volume>  
        <issue>4</issue>  
        <fpage>753</fpage>  
        <lpage>66</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/19465572"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1177/0886260509334413</pub-id>
        <pub-id pub-id-type="medline">19465572</pub-id>
        <pub-id pub-id-type="pii">0886260509334413</pub-id>
        <pub-id pub-id-type="pmcid">PMC3804558</pub-id></nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mercer</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Burns</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Guirguis</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Chin</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Dogba</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Dolovich</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Guénette</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Jenkins</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Légaré</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>McKinnon</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>McMurray</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Waked</surname>
            <given-names>KA</given-names>
          </name>
          <name name-style="western">
            <surname>Grindrod</surname>
            <given-names>KA</given-names>
          </name>
        </person-group>
        <article-title>Physician and pharmacist medication decision-making in the time of electronic health records: mixed-methods study</article-title>
        <source>JMIR Hum Factors</source>  
        <year>2018</year>  
        <month>09</month>  
        <day>25</day>  
        <volume>5</volume>  
        <issue>3</issue>  
        <fpage>e24</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/3/e24/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/humanfactors.9891</pub-id>
        <pub-id pub-id-type="medline">30274959</pub-id>
        <pub-id pub-id-type="pii">v5i3e24</pub-id>
        <pub-id pub-id-type="pmcid">PMC6231837</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
