<?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">ResProt</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Res Protoc</journal-id>
      <journal-title>JMIR Research Protocols</journal-title>
      <issn pub-type="epub">1929-0748</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">v5i2e136</article-id>
    <article-id pub-id-type="pmid">27350013</article-id>
    <article-id pub-id-type="doi">10.2196/resprot.5400</article-id>
    <article-categories>
      <subj-group subj-group-type="heading">
        <subject>Protocol</subject>
      </subj-group>
      <subj-group subj-group-type="article-type">
        <subject>Protocol</subject>
      </subj-group>
    </article-categories>
    <title-group>
      <article-title>Supporting Tablet Configuration, Tracking, and Infection Control Practices in Digital Health Interventions: Study Protocol</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Eysenbach</surname>
          <given-names>Gunther</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Shaw</surname>
          <given-names>Ryan</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Green</surname>
          <given-names>Beverly</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1">
        <name name-style="western">
          <surname>Furberg</surname>
          <given-names>Robert D</given-names>
        </name>
        <degrees>PhD, MBA</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-3803-1879</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib2" corresp="yes">
      <name name-style="western">
        <surname>Ortiz</surname>
        <given-names>Alexa M</given-names>
      </name>
      <degrees>MSN</degrees>
      <xref rid="aff1" ref-type="aff">1</xref>
      <address>
        <institution>RTI International</institution>
        <addr-line>3040 E. Cornwallis Road</addr-line>
        <addr-line>Research Triangle Park, NC,</addr-line>
        <country>United States</country>
        <phone>1 919 316 3344</phone>
        <fax>1 919 541 6621</fax>
        <email>amortiz@rti.org</email>
      </address>  
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-8121-1250</ext-link></contrib>
      <contrib contrib-type="author" id="contrib3">
        <name name-style="western">
          <surname>Zulkiewicz</surname>
          <given-names>Brittany A</given-names>
        </name>
        <degrees>BS</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-9018-2068</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib4">
        <name name-style="western">
          <surname>Hudson</surname>
          <given-names>Jordan P</given-names>
        </name>
        <degrees>BA</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-2421-3759</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib5">
        <name name-style="western">
          <surname>Taylor</surname>
          <given-names>Olivia M</given-names>
        </name>
        <degrees>MPH</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-0233-3488</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib6">
        <name name-style="western">
          <surname>Lewis</surname>
          <given-names>Megan A</given-names>
        </name>
        <degrees>PhD</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-1670-9298</ext-link>
      </contrib>
    </contrib-group>
    <aff id="aff1">
      <sup>1</sup>
      <institution>RTI International</institution>
      <addr-line>Research Triangle Park, NC</addr-line>
      <country>United States</country>
    </aff>
    <author-notes>
      <corresp>Corresponding Author: Alexa M Ortiz 
      <email>amortiz@rti.org</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><season>Apr-Jun</season><year>2016</year></pub-date>
    <pub-date pub-type="epub">
      <day>27</day>
      <month>06</month>
      <year>2016</year>
    </pub-date>
    <volume>5</volume>
    <issue>2</issue>
    <elocation-id>e136</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>1</day>
        <month>12</month>
        <year>2015</year>
      </date>
      <date date-type="rev-request">
        <day>30</day>
        <month>1</month>
        <year>2016</year>
      </date>
      <date date-type="rev-recd">
        <day>26</day>
        <month>2</month>
        <year>2016</year>
      </date>
      <date date-type="accepted">
        <day>31</day>
        <month>3</month>
        <year>2016</year>
      </date>
    </history>
    <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
    <copyright-statement>©Robert D Furberg, Alexa M Ortiz, Brittany A Zulkiewicz, Jordan P Hudson, Olivia M Taylor, Megan A Lewis. Originally published in JMIR Research Protocols (http://www.researchprotocols.org), 27.06.2016.</copyright-statement>
    <copyright-year>2016</copyright-year>
    <license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/2.0/">
      <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on http://www.researchprotocols.org, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://www.researchprotocols.org/2016/2/e136/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>Tablet-based health care interventions have the potential to encourage patient care in a timelier manner, allow physicians convenient access to patient records, and provide an improved method for patient education. However, along with the continued adoption of tablet technologies, there is a concomitant need to develop protocols focusing on the configuration, management, and maintenance of these devices within the health care setting to support the conduct of clinical research.</p>
      </sec>
      <sec sec-type="objective">
        <title>Objective</title>
        <p>Develop three protocols to support tablet configuration, tablet management, and tablet maintenance.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>The Configurator software, Tile technology, and current infection control recommendations were employed to develop three distinct protocols for tablet-based digital health interventions. Configurator is a mobile device management software specifically for iPhone operating system (iOS) devices. The capabilities and current applications of Configurator were reviewed and used to develop the protocol to support device configuration. Tile is a tracking tag associated with a free mobile app available for iOS and Android devices. The features associated with Tile were evaluated and used to develop the Tile protocol to support tablet management. Furthermore, current recommendations on preventing health care–related infections were reviewed to develop the infection control protocol to support tablet maintenance.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>This article provides three protocols: the Configurator protocol, the Tile protocol, and the infection control protocol.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>These protocols can help to ensure consistent implementation of tablet-based interventions, enhance fidelity when employing tablets for research purposes, and serve as a guide for tablet deployments within clinical settings.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>tablet computers</kwd>
      <kwd>mHealth</kwd>
      <kwd>infection control</kwd>
      <kwd>clinical research protocol</kwd>
      <kwd>mobile device management</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The proliferation of tablet technologies has ushered in a new realm of connected health care and research-based interventions in the clinical setting. According to the Pew Research Center, 64% of American adults own a smartphone, and of those, 53% also own a tablet [<xref ref-type="bibr" rid="ref1">1</xref>]. Advancements in policy, health information technology adoption by providers, mobile/social technology adoption by consumers, and development of health-focused mobile apps have created ideal conditions to enable the expansion of tablet-based interventions. According to the <italic>2015 Healthcare Information and Management Systems Society Mobile Technology Survey</italic>, 47% of responding organizations labeled mobile service implementation to access information as a top priority, and 57% indicated already having a mobile technology policy [<xref ref-type="bibr" rid="ref2">2</xref>]. Further, as noted by the IMS Institute for Healthcare Informatics, more than 165,000 mobile health (mHealth) apps are currently available for consumer download through Google Play and the Mac App Store [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>The use of electronic tools and services has created new opportunities for individuals to actively participate in monitoring and directing their health care through digital health interventions. The body of evidence that supports the use of such strategies to improve health outcomes continues to expand [<xref ref-type="bibr" rid="ref4">4</xref>]. However, insufficient guidance exists on deployment methods that could be used to support replication or subsequent scaling. To address this gap, we describe protocols relevant to three major phases of digital health intervention activities using tablets: initial device configuration, remote management of deployed technologies, and the ongoing maintenance of tablets deployed within clinical environments. The protocols are intended for use by three major audiences: (1) public health investigators responsible for the design of a digital health intervention, (2) research technologists seeking guidance on deployment methods, and (3) clinical staff responsible for monitoring tablets and carrying out infection control procedures in a health care setting.</p>
      <p>There is scant literature describing the implementation of tablet-based public health interventions and the management of tablets. Tablet use takes place across multiple populations and settings including urban ambulatory care practices, grocery stores, pediatric practices, and primary care practices [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Several interventions describe the use of Web-based material optimized for delivery via tablets, whereas others used operating system–specific tablet-based interventions [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. Irrespective of the mode of content delivery (eg, native app, hybrid app, or responsive Web application), proper configuration, management, and maintenance of the tablet computer is essential to ensure technical fidelity and control of participant exposure to intervention materials. To the best of our knowledge, no studies describe these procedures, and there are no predeveloped protocols surrounding the use of tablets in digital health interventions. We describe protocols to address the gap within the literature that can serve as a basic guide for configuration, management, and maintenance of tablet-based interventions.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Tablet Configuration</title>
        <sec>
          <title>Characteristics of Configurator</title>
          <p>The mobile device management software, known as Configurator, is a resource that may improve the reliability and enhance the reproducibility of digital health interventions. Configurator is a free utility available from the Mac App Store. It is designed to configure and deploy multiple iPhones, iPod Touches, iPads, or Apple TV devices [<xref ref-type="bibr" rid="ref14">14</xref>]. Configurator users have the ability to push images, settings, apps, and security profiles across groups of iPhone operating system (iOS) devices [<xref ref-type="bibr" rid="ref15">15</xref>]. These devices can be configured using an XML configuration file or by using the backup of a master iPad [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>], which is configured by hand. The configuration can include all network and security settings as well as installs for the selected free or in-house apps. Once set, the master iPad is imaged using Configurator’s backup function [<xref ref-type="bibr" rid="ref16">16</xref>]. Remaining iPads are connected to the Mac OS device via universal serial bus (USB), and the image of the master iPad is restored to the remaining iPads. This can be done with up to 30 iPads [<xref ref-type="bibr" rid="ref15">15</xref>]. Using Configurator to set up and maintain iOS devices gives administrative control over every aspect of the device, including wallpaper and lock screen settings, virtual private network and Wi-Fi (wireless local area network) settings, mail and calendar accounts, iOS version and upgrades, documents, and application access [<xref ref-type="bibr" rid="ref16">16</xref>]. The end result is a number of identical, incrementally identified iOS devices. Subsequent alterations, including software updates, can only be made using Configurator by connecting the devices via USB to a Mac OS computer.</p>
        </sec>
        <sec>
          <title>Applying Configurator to Tablet Deployment</title>
          <p>Presently there is limited guidance available regarding tablet configuration for digital health interventions. However, with reported sales of more than 4.5 million iPads to educational institutions within the United States and almost twice that worldwide, Configurator is extensively used within the field of education [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Recommendations from Configurator’s application in education can be applied to digital health interventions deployed for research or clinical purposes.</p>
          <p>The Configurator application is widely used in education for configuring multiple iOS-based devices at scale, whether it be for a single classroom, school, or district. Consequently, a considerable amount of guidance is available about Configurator’s setup and use in schools. Additionally, the Configurator education deployment model provides institutions with flexibility to manage multiple deployment scenarios, such as one-to-one, shared-use, and student-owned devices. Schools may choose to deploy iPads in one specific scenario or all three scenarios. However, Configurator is ideally used to set up one-to-one or shared-use devices, which gives educational IT staff the ability to customize and be flexible in addressing the school’s specific needs.</p>
          <p>The iOS education Configurator deployment model can easily be transposed to other domains, such as deployment within clinical settings or health research studies. The example provided in <xref ref-type="fig" rid="figure1">Figure 1</xref> outlines how the educational infrastructure is similar to the health care infrastructure, as can be seen by changing the nomenclature from schools to clinics, teachers to clinicians, and students to patients.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Education and healthcare comparative configurator infrastructure.</p>
            </caption>
            <graphic xlink:href="resprot_v5i2e136_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Configurator Protocol</title>
          <p>As the use of tablets continues to expand within clinical settings and tablets become more commonplace components in digital health interventions, a consistent method for configuring devices will become increasingly necessary. The protocol, as shown in <xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>, provides a generic outline for iPad deployment using Configurator within research or clinical settings. The protocol reviews the requirements associated with Configurator’s use and provides the steps for setting up an iPad using Configurator.</p>
        </sec>
      </sec>
      <sec>
        <title>Tablet Management</title>
        <sec>
          <title>Characteristics of Tile</title>
          <p>The ability to track tablets (or other mobile devices) is an investment in the retention of the digital health intervention. Tile is a small tracking tag (see <xref ref-type="fig" rid="figure2">Figure 2</xref> for dimensions) associated with a free app compatible with iOS and the Android operating system [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref23">23</xref>]. The primary purpose of Tile is to assist users in locating lost items. While Tile was not designed for mobile device management, its capabilities and small size offer a unique method of tracking mobile devices in clinical settings to augment native management features, such as Find My iPhone, where a Global Positioning System (GPS) signal may not be available.</p>
          <p>The Tile app is free and the cost of Tile’s hardware is relatively low—usually less than $25 per device [<xref ref-type="bibr" rid="ref24">24</xref>]. Tile locates items by using Bluetooth low energy (BLE) 4.0 [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. BLE works optimally at a range of 30 feet but can extend to a maximum range of 100 feet [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. If an item is lost but is in the range of the BLE, Tile can be triggered to play a short tune by selecting the <italic>Find</italic> option within the app to assist the user in locating the lost device [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. If Tile is unable to track an item via BLE, the user can select the app’s <italic>Mark as Lost</italic> option to report a missing Tile [<xref ref-type="bibr" rid="ref23">23</xref>]. The app can also inform users about the last place their lost device was seen. As noted in the Tile informational material [<xref ref-type="bibr" rid="ref23">23</xref>], “Tile maps the last place you had it.”</p>
          <p>Additionally, multiple Tiles can work together. While an individual Tile is only visible to its registered user, each Tile can be used in a <italic>Community Find</italic>, which allows any Tile to assist in communicating the location of a lost item to its registered owner [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Separate from the <italic>Community Find</italic> feature, the Tile app can share a Tile’s location with another Tile app user [<xref ref-type="bibr" rid="ref27">27</xref>]. The <italic>Share</italic> feature allows two different app users access to the same Tile [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Entity relationship diagram: option 1 and tile dimensions.</p>
            </caption>
            <graphic xlink:href="resprot_v5i2e136_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Applying Tile to Tablet Deployment</title>
          <p>There are two approaches to applying Tile technology to tablet deployments. The first option, as outlined in <xref ref-type="fig" rid="figure2">Figure 2</xref>, displays three devices that each track one other device within the diagram. Since each Tile’s BLE can only connect to one device at a time [<xref ref-type="bibr" rid="ref27">27</xref>], each tablet is limited to tracking only one other tablet. That is, tablet 1 is used to track the location of tile 2 (attached to tablet 2); tablet 2 is used to track the location of tile 3 (attached to tablet 3); tablet 3 is used to track the location of tile 1 (attached to tablet 1).</p>
          <p>The second option for applying Tile technology to tablet deployments is outlined in <xref ref-type="fig" rid="figure3">Figure 3</xref>, which displays four devices, three with Tiles attached and one device that is solely used for tracking the deployed Tiles. Because one Tile app can simultaneously track multiple individual Tiles, a single tablet can track the three deployed Tiles via BLE; that is, tablet 1 can track tablets 2, 3, and 4.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Entity relationship diagram: option 2.</p>
            </caption>
            <graphic xlink:href="resprot_v5i2e136_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Tile Protocol</title>
          <p>Considering the compact nature of many tablets, the risk of theft, misplaced devices, or loss is a concern. Consequently, enhanced use of tablet technology in digital health interventions must be accompanied by innovative methods of device management. <xref ref-type="app" rid="app2">Multimedia Appendix 2</xref> provides a protocol outlining the requirements for deployment as well as how to set up and use the various features offered by the Tile tracking device.</p>
        </sec>
      </sec>
      <sec>
        <title>Tablet Maintenance</title>
        <sec>
          <title>Characteristics of Infection Control</title>
          <p>As tablets continue to proliferate the health care setting, the risk of device-based pathogen transmission increases [<xref ref-type="bibr" rid="ref29">29</xref>]. In a 2009 study, the mobile phones of 200 intensive care and operating room health care workers were tested, and 94.5% showed some form of bacterial contamination [<xref ref-type="bibr" rid="ref30">30</xref>]. Although the study does not discuss tablets, the same concerns of bacterial contamination and infection surrounding mobile phones are applicable to tablets.</p>
          <p>Presently, Apple recommends using a soft, lint-free cloth for cleaning mobile devices, avoiding liquids, solvents, or spraying cleaners directly onto the device [<xref ref-type="bibr" rid="ref31">31</xref>]. However, a plain cloth will not remove contagious pathogens such as methicillin-resistant <italic>Staphylococcus aureus</italic> (MRSA) or vancomycin-resistant enterococcus (VRE) from a mobile device [<xref ref-type="bibr" rid="ref29">29</xref>]. A study by Howell and colleagues [<xref ref-type="bibr" rid="ref29">29</xref>] compared six different wipes (Sani-Cloth CHG 2%, Trigene, Clorox, Tristel, soap and water, and a plain cloth) and found that the Sani-Cloth CHG (chlorhexidine gluconate 2%/alcohol 70%) wipes were the most effective cleaning agent for tablets, with very low risk to the tablet’s functional capabilities or accessories.</p>
        </sec>
        <sec>
          <title>Infection Control Protocol</title>
          <p>Proper disinfection is an important component to consider as tablets are increasingly integrated into both research studies and patient care. The infection control protocol is reviewed in <xref ref-type="app" rid="app3">Multimedia Appendix 3</xref> and provides a list of the required supplies as well as an outline of the steps needed to disinfect tablet devices using CHG 2% wipes.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>This article provides three protocols within the multimedia appendices that can be applied to support the configuration, the management, and the maintenance of mobile devices employed in digital health interventions: the Configurator protocol, the Tile protocol, and the infection control protocol.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>This article addresses the literature gap on tablet protocols used in digital health interventions and describes three protocols supporting tablet configuration, management, and maintenance. The protocols discussed are furnished as generalized instructions or as a foundation for further enhancements, allowing for customization to further optimize tablet adoption. While these protocols can be used to support a single intervention, the resources may be used individually or bundled, at the discretion of investigators or clinicians, depending on the methodological requirements and deployment environment.</p>
      <p>The availability and utilization of tablets is advancing the way researchers work, clinicians provide health care, and patients receive health care. However, along with the proliferation of tablets comes the need to advance tablet-focused protocols. The goal of this paper was not to test the effectiveness of Configurator, Tile, or the proposed infection protocol. Rather, we sought to review various options available to augment consistent tablet configuration, management, and maintenance. Further research is necessary to evaluate the feasibility and efficacy of the developed tablet-focused protocols.</p>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>Configurator Protocol.</p>
        <media xlink:href="resprot_v5i2e136_app1.pdf" xlink:title="PDF File (Adobe PDF File), 62KB"/>
      </app>
      <app id="app2">
        <title>Multimedia Appendix 2</title>
        <p>Tile Protocol.</p>
        <media xlink:href="resprot_v5i2e136_app2.pdf" xlink:title="PDF File (Adobe PDF File), 29KB"/>
      </app>
      <app id="app3">
        <title>Multimedia Appendix 3</title>
        <p>Infection Control Protocol.</p>
        <media xlink:href="resprot_v5i2e136_app3.pdf" xlink:title="PDF File (Adobe PDF File), 30KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BLE</term>
          <def>
            <p>Bluetooth low energy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDC</term>
          <def>
            <p>Centers for Disease Control and Prevention</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CHG</term>
          <def>
            <p>chlorhexidine gluconate</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">GPS</term>
          <def>
            <p>Global Positioning System</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">iOS</term>
          <def>
            <p>iPhone operating system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">MRSA</term>
          <def>
            <p>methicillin-resistant <italic>Staphylococcus aureus</italic></p>
          </def>
        </def-item>
        <def-item>
        <term id="abb8">OS</term>
        <def>
          <p>operating system</p>
        </def> </def-item>
        <def-item>
          <term id="abb9">PPE</term>
          <def>
            <p>personal protective equipment</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">USB</term>
          <def>
            <p>universal serial bus</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">VRE</term>
          <def>
            <p>vancomycin-resistant enterococcus</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">Wi-Fi</term>
          <def>
            <p>wireless local area network technology</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>Funding for this work was provided by the Centers for Disease Control and Prevention (CDC). The authors would like to acknowledge the contributions of Dr. Camilla Harshbarger and Carla Galindo, MPH. The content of this article is solely the responsibility of the authors and does not necessarily reflect the views of the CDC, the companies responsible for the production and distribution of Tile and Configurator, or the authors’ employer, RTI International.</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="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <source>U.S. smartphone use in 2015. Chapter one: a portrait of smartphone ownership</source>  
        <year>2015</year>  
        <month>04</month>  
        <day>01</day>  
        <access-date>2016-06-12</access-date>
        <publisher-loc>Washington, DC</publisher-loc>
        <publisher-name>Pew Internet and American Life Project</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.pewinternet.org/files/2015/03/PI_Smartphones_0401151.pdf">http://www.pewinternet.org/files/2015/03/PI_Smartphones_0401151.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d8l18Ykz"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
        <source>2015 HIMSS mobile technology survey: executive summary</source>  
        <year>2015</year>  
        <month>04</month>  
        <access-date>2015-11-18</access-date>
        <publisher-loc>Chicago, IL</publisher-loc>
        <publisher-name>Healthcare Information and Management Systems Society</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://s3.amazonaws.com/rdcms-himss/files/production/public/FileDownloads/2015%20Mobile%20Technology%20Survey%20EXECUTIVE%20SUMMARY%20FINAL%20040215.pdf">http://s3.amazonaws.com/rdcms-himss/files/production/public/FileDownloads/2015%20Mobile%20Technology%20Survey%20EXECUTIVE%20SUMMARY%20FINAL%20040215.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d8mbggUs"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
        <source>Patient Adoption of mHealth</source>  
        <year>2015</year>  
        <month>09</month>  
        <access-date>2016-06-12</access-date>
        <publisher-loc>Danbury, CT</publisher-loc>
        <publisher-name>IMS Institute for Healthcare Informatics</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.imshealth.com/da_DK/thought-leadership/ims-institute/reports/patient-adoption-of-mhealth">http://www.imshealth.com/da_DK/thought-leadership/ims-institute/reports/patient-adoption-of-mhealth</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6iCgJZtLc"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Claborn</surname>
            <given-names>KR</given-names>
          </name>
          <name name-style="western">
            <surname>Fernandez</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Wray</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Ramsey</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Computer-based HIV adherence promotion interventions: A systematic review</article-title>
        <source>Transl Behav Med</source>  
        <year>2015</year>  
        <month>09</month>  
        <volume>5</volume>  
        <issue>3</issue>  
        <fpage>294</fpage>  
        <lpage>306</lpage>  
        <pub-id pub-id-type="doi">10.1007/s13142-015-0317-0</pub-id>
        <pub-id pub-id-type="medline">26327935</pub-id>
        <pub-id pub-id-type="pmcid">PMC4537461</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>Bickmore</surname>
            <given-names>TW</given-names>
          </name>
          <name name-style="western">
            <surname>Silliman</surname>
            <given-names>RA</given-names>
          </name>
          <name name-style="western">
            <surname>Nelson</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Cheng</surname>
            <given-names>DM</given-names>
          </name>
          <name name-style="western">
            <surname>Winter</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Henault</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Paasche-Orlow</surname>
            <given-names>MK</given-names>
          </name>
        </person-group>
        <article-title>A randomized controlled trial of an automated exercise coach for older adults</article-title>
        <source>J Am Geriatr Soc</source>  
        <year>2013</year>  
        <month>10</month>  
        <volume>61</volume>  
        <issue>10</issue>  
        <fpage>1676</fpage>  
        <lpage>1683</lpage>  
        <pub-id pub-id-type="doi">10.1111/jgs.12449</pub-id>
        <pub-id pub-id-type="medline">24001030</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>Kaplan</surname>
            <given-names>CP</given-names>
          </name>
          <name name-style="western">
            <surname>Livaudais-Toman</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Tice</surname>
            <given-names>JA</given-names>
          </name>
          <name name-style="western">
            <surname>Kerlikowske</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Gregorich</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Pérez-Stable</surname>
            <given-names>EJ</given-names>
          </name>
          <name name-style="western">
            <surname>Pasick</surname>
            <given-names>RJ</given-names>
          </name>
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Quinn</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Karliner</surname>
            <given-names>LS</given-names>
          </name>
        </person-group>
        <article-title>A randomized, controlled trial to increase discussion of breast cancer in primary care</article-title>
        <source>Cancer Epidemiol Biomarkers Prev</source>  
        <year>2014</year>  
        <month>07</month>  
        <volume>23</volume>  
        <issue>7</issue>  
        <fpage>1245</fpage>  
        <lpage>1253</lpage>  
        <pub-id pub-id-type="doi">10.1158/1055-9965.EPI-13-1380</pub-id>
        <pub-id pub-id-type="medline">24762560</pub-id>
        <pub-id pub-id-type="pmcid">PMC4167008</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Burckley</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Tincani</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Guld Fisher</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>An iPad-based picture and video activity schedule increases community shopping skills of a young adult with autism spectrum disorder and intellectual disability</article-title>
        <source>Dev Neurorehabil</source>  
        <year>2015</year>  
        <month>04</month>  
        <volume>18</volume>  
        <issue>2</issue>  
        <fpage>131</fpage>  
        <lpage>136</lpage>  
        <pub-id pub-id-type="doi">10.3109/17518423.2014.945045</pub-id>
        <pub-id pub-id-type="medline">25084013</pub-id></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Dempsey</surname>
            <given-names>AF</given-names>
          </name>
          <name name-style="western">
            <surname>Maertens</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Beaty</surname>
            <given-names>BL</given-names>
          </name>
          <name name-style="western">
            <surname>O'Leary</surname>
            <given-names>ST</given-names>
          </name>
        </person-group>
        <article-title>Understanding how different recruitment strategies impact parent engagement with an iPad-based intervention to provide personalized information about adolescent vaccines</article-title>
        <source>J Adolesc Health</source>  
        <year>2015</year>  
        <month>05</month>  
        <volume>56</volume>  
        <issue>5 Suppl</issue>  
        <fpage>S7</fpage>  
        <lpage>S13</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jadohealth.2014.11.022</pub-id>
        <pub-id pub-id-type="medline">25863557</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Levine</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Wolf</surname>
            <given-names>RL</given-names>
          </name>
          <name name-style="western">
            <surname>Chinn</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Edelstein</surname>
            <given-names>BL</given-names>
          </name>
        </person-group>
        <article-title>MySmileBuddy: an iPad-based interactive program to assess dietary risk for early childhood caries</article-title>
        <source>J Acad Nutr Diet</source>  
        <year>2012</year>  
        <month>10</month>  
        <volume>112</volume>  
        <issue>10</issue>  
        <fpage>1539</fpage>  
        <lpage>1542</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jand.2012.06.010</pub-id>
        <pub-id pub-id-type="medline">23017564</pub-id>
        <pub-id pub-id-type="pmcid">PMC3556790</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>Webster</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Gerressu</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Michie</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Estcourt</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Anderson</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Ang</surname>
            <given-names>CS</given-names>
          </name>
          <name name-style="western">
            <surname>Murray</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Rait</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Stephenson</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Bailey</surname>
            <given-names>JV</given-names>
          </name>
          <collab>MenSS Trial Group</collab>
        </person-group>
        <article-title>Defining the content of an online sexual health intervention: The menSS website</article-title>
        <source>JMIR Res Protoc</source>  
        <year>2015</year>  
        <month>07</month>  
        <volume>4</volume>  
        <issue>3</issue>  
        <fpage>e82</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.researchprotocols.org/2015/3/e82/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/resprot.4316</pub-id>
        <pub-id pub-id-type="medline">26142304</pub-id>
        <pub-id pub-id-type="pmcid">PMC4526976</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>Breitenstein</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Gross</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Web-based delivery of a preventive parent training intervention: A feasibility study</article-title>
        <source>J Child Adolesc Psychiatr Nurs</source>  
        <year>2013</year>  
        <month>05</month>  
        <volume>26</volume>  
        <issue>2</issue>  
        <fpage>149</fpage>  
        <lpage>157</lpage>  
        <pub-id pub-id-type="doi">10.1111/jcap.12031</pub-id>
        <pub-id pub-id-type="medline">23607827</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>Farmer</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Toms</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Hardinge</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Williams</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Rutter</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Tarassenko</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Self-management support using an Internet-linked tablet computer (the EDGE platform)-based intervention in chronic obstructive pulmonary disease: Protocol for the EDGE-COPD randomised controlled trial</article-title>
        <source>BMJ Open</source>  
        <year>2014</year>  
        <month>01</month>  
        <volume>4</volume>  
        <issue>1</issue>  
        <fpage>e004437</fpage>  
        <pub-id pub-id-type="doi">10.1136/bmjopen-2013-004437</pub-id>
        <pub-id pub-id-type="medline">24401729</pub-id>
        <pub-id pub-id-type="pmcid">PMC3902407</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>Cook</surname>
            <given-names>DJ</given-names>
          </name>
          <name name-style="western">
            <surname>Moradkhani</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Douglas</surname>
            <given-names>KS</given-names>
          </name>
          <name name-style="western">
            <surname>Prinsen</surname>
            <given-names>SK</given-names>
          </name>
          <name name-style="western">
            <surname>Fischer</surname>
            <given-names>EN</given-names>
          </name>
          <name name-style="western">
            <surname>Schroeder</surname>
            <given-names>DR</given-names>
          </name>
        </person-group>
        <article-title>Patient education self-management during surgical recovery: Combining mobile (iPad) and a content management system</article-title>
        <source>Telemed J E Health</source>  
        <year>2014</year>  
        <month>04</month>  
        <volume>20</volume>  
        <issue>4</issue>  
        <fpage>312</fpage>  
        <lpage>317</lpage>  
        <pub-id pub-id-type="doi">10.1089/tmj.2013.0219</pub-id>
        <pub-id pub-id-type="medline">24443928</pub-id>
        <pub-id pub-id-type="pmcid">PMC3968874</pub-id></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
        <source>Apple Configurator 2</source>  
        <access-date>2015-11-19</access-date>
        <publisher-name>Mac App Store</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://itunes.apple.com/us/app/apple-configurator-2/id1037126344?mt=12">https://itunes.apple.com/us/app/apple-configurator-2/id1037126344?mt=12</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9myVgh0"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rivers</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <source>ClassThink</source>  
        <year>2013</year>  
        <month>05</month>  
        <day>27</day>  
        <access-date>2015-11-23</access-date>
        <comment>What is Apple Configurator? 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.classthink.com/2013/05/27/apple-configurator-or-mdm/">http://www.classthink.com/2013/05/27/apple-configurator-or-mdm/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6dGN6T4bi"/></comment> </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
        <source>iOS Deployment Reference</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>Cupertino, CA</publisher-loc>
        <publisher-name>Apple Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://manuals.info.apple.com/MANUALS/1000/MA1685/en_US/ios_deployment_reference.pdf">https://manuals.info.apple.com/MANUALS/1000/MA1685/en_US/ios_deployment_reference.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9n1Rufm"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
        <source>iOS Education Deployment Overview</source>  
        <year>2014</year>  
        <month>09</month>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>Cupertino, CA</publisher-loc>
        <publisher-name>Apple Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.apple.com/education/docs/EDU_deployment_overview_en_sept14.pdf">http://www.apple.com/education/docs/EDU_deployment_overview_en_sept14.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9n407Vz"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Paczkowski</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <source>All Things D</source>  
        <year>2013</year>  
        <month>02</month>  
        <day>28</day>  
        <access-date>2015-11-19</access-date>
        <comment>Apple’s iTunes U hits one billion downloads 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://allthingsd.com/20130228/apples-itunes-u-hits-1-billion-downloads/">http://allthingsd.com/20130228/apples-itunes-u-hits-1-billion-downloads/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6d9nAr4rf"/></comment> </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Etherington</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <source>TechCrunch</source>  
        <year>2013</year>  
        <month>02</month>  
        <day>28</day>  
        <access-date>2015-11-19</access-date>
        <comment>Apple has sold over 8M iPads direct to education worldwide, with more than 1B iTunes U downloads 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://techcrunch.com/2013/02/28/apple-has-sold-over-8m-ipads-direct-to-education-worldwide-with-more-than-1b-itunes-u-downloads/">http://techcrunch.com/2013/02/28/apple-has-sold-over-8m-ipads-direct-to-education-worldwide-with-more-than-1b-itunes-u-downloads/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6d9opZ2Yy"/></comment> </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
        <source>Tile: Dimensions</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://support.thetileapp.com/hc/en-us/articles/200591648-Dimensions">https://support.thetileapp.com/hc/en-us/articles/200591648-Dimensions</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9qad1O7"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
        <source>Tile: device compatability</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/compatibility">https://www.thetileapp.com/compatibility</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9qnV3e6"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
        <source>Tile: Welcome to Tile</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/got-my-tile">https://www.thetileapp.com/got-my-tile</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9r5CBEN"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
        <source>Tile: Frequently Asked Questions</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/faq">https://www.thetileapp.com/faq</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9r802ki"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
        <source>The Tile App</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/">https://www.thetileapp.com/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9rAtaxi"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
        <source>Tile: How it Works</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/how-it-works">https://www.thetileapp.com/how-it-works</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9rDPrVc"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
        <source>Tile: Community Find. We're All Looking Out for Each Other</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/community-find">https://www.thetileapp.com/community-find</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9rG3pb2"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
        <source>Tile: Introducing Shared Tiles</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.thetileapp.com/blog/shared-tiles-feature">https://www.thetileapp.com/blog/shared-tiles-feature</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9rmSdaP"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
        <source>Tile: Sharing a Tile</source>  
        <year>2015</year>  
        <access-date>2015-11-19</access-date>
        <publisher-loc>San Mateo, CA</publisher-loc>
        <publisher-name>Tile Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://support.thetileapp.com/hc/en-us/articles/205332837-Sharing-a-Tile">https://support.thetileapp.com/hc/en-us/articles/205332837-Sharing-a-Tile</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d9rdM6HQ"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Howell</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Thoppil</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Mariyaselvam</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Jones</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Young</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Sharma</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Blunt</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Young</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>Disinfecting the ipad: evaluating effective methods</article-title>
        <source>J Hosp Infect</source>  
        <year>2014</year>  
        <month>06</month>  
        <volume>87</volume>  
        <issue>2</issue>  
        <fpage>77</fpage>  
        <lpage>83</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jhin.2014.01.012</pub-id>
        <pub-id pub-id-type="medline">24746231</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>Ulger</surname>
            <given-names>F</given-names>
          </name>
          <name name-style="western">
            <surname>Esen</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Dilek</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Yanik</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Gunaydin</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Leblebicioglu</surname>
            <given-names>H</given-names>
          </name>
        </person-group>
        <article-title>Are we aware how contaminated our mobile phones with nosocomial pathogens?</article-title>
        <source>Ann Clin Microbiol Antimicrob</source>  
        <year>2009</year>  
        <month>03</month>  
        <volume>8</volume>  
        <issue>7</issue>  
        <pub-id pub-id-type="doi">10.1186/1476-0711-8-7</pub-id>
        <pub-id pub-id-type="medline">19267892</pub-id>
        <pub-id pub-id-type="pmcid">PMC2655280</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
        <source>Apple Support: How to Clean Apple Products</source>  
        <year>2015</year>  
        <access-date>2015-11-18</access-date>
        <publisher-loc>Cupertino, CA</publisher-loc>
        <publisher-name>Apple Inc</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://support.apple.com/en-us/ht204172">https://support.apple.com/en-us/ht204172</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6d8ibEtNd"/>
        </comment> </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
