<?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="letter" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v8i1e52726</article-id>
      <article-id pub-id-type="pmid">38820574</article-id>
      <article-id pub-id-type="doi">10.2196/52726</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Letter</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Research Letter</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Barriers to Postdischarge Smartphone App Use Among Patients With Traumatic Rib Fractures</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ghozali</surname>
            <given-names>Mt</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Levin</surname>
            <given-names>Leonard</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Berrigan</surname>
            <given-names>Margaret T</given-names>
          </name>
          <degrees>MS, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0009-4538-3459</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Beaulieu-Jones</surname>
            <given-names>Brendin R</given-names>
          </name>
          <degrees>MBA, MBI, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1208-8025</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Baines</surname>
            <given-names>Rachel</given-names>
          </name>
          <degrees>MSN, NP</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0002-1727-0886</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Berkowitz</surname>
            <given-names>Seth</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3515-5961</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Evans</surname>
            <given-names>Heather</given-names>
          </name>
          <degrees>MS, MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3661-0666</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Brat</surname>
            <given-names>Gabriel A</given-names>
          </name>
          <degrees>MPH, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Surgery</institution>
            <institution>Beth Israel Deaconess Medical Center</institution>
            <addr-line>110 Francis Street</addr-line>
            <addr-line>Suite 2G</addr-line>
            <addr-line>Boston, MA, 02215</addr-line>
            <country>United States</country>
            <phone>1 617 632 9922</phone>
            <email>gbrat@bidmc.harvard.edu</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3928-5931</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Surgery</institution>
        <institution>Beth Israel Deaconess Medical Center</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Biomedical Informatics</institution>
        <institution>Harvard Medical School</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department of Radiology</institution>
        <institution>Beth Israel Deaconess Medical Center</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Surgery</institution>
        <institution>Medical University of South Carolina</institution>
        <addr-line>Charleston, SC</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Gabriel A Brat <email>gbrat@bidmc.harvard.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>31</day>
        <month>5</month>
        <year>2024</year>
      </pub-date>
      <volume>8</volume>
      <elocation-id>e52726</elocation-id>
      <history>
        <date date-type="received">
          <day>13</day>
          <month>9</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>20</day>
          <month>12</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>10</day>
          <month>1</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>1</day>
          <month>2</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Margaret T Berrigan, Brendin R Beaulieu-Jones, Rachel Baines, Seth Berkowitz, Heather Evans, Gabriel A Brat. Originally published in JMIR Formative Research (https://formative.jmir.org), 31.05.2024.</copyright-statement>
      <copyright-year>2024</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 Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2024/1/e52726" xlink:type="simple"/>
      <abstract>
        <p>Rib fractures commonly result from traumatic injury and often require hospitalization for pain control and supportive pulmonary care. Although the use of mobile health technology to share patient-generated health data has increased, it remains limited in patients with traumatic injuries. We sought to assess the feasibility of mobile health tracking in patients with rib fractures by using a smartphone app to monitor postdischarge recovery. We encountered patient, institutional, and process-related obstacles that limited app use. The success of future work requires the acknowledgment of these limitations and the use of an implementation science framework to effectively integrate technological tools for personalized trauma care.</p>
      </abstract>
      <kwd-group>
        <kwd>mobile health</kwd>
        <kwd>smartphone app</kwd>
        <kwd>electronic health record</kwd>
        <kwd>postdischarge monitoring</kwd>
        <kwd>implementation science</kwd>
        <kwd>mHealth</kwd>
        <kwd>app</kwd>
        <kwd>apps</kwd>
        <kwd>application</kwd>
        <kwd>applications</kwd>
        <kwd>digital health</kwd>
        <kwd>smartphone</kwd>
        <kwd>smartphones</kwd>
        <kwd>mobile phone</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Rib fractures are common among adults and frequently result from traumatic injury. Management often requires hospitalization and focuses on pain control and supportive pulmonary care [<xref ref-type="bibr" rid="ref1">1</xref>]. Patient-generated health data sharing and mobile health technology use have increased with expanded technical ability and smartphone uptake. Most existing examples target patients enrolled in an elective outpatient setting, but some include acute inpatient enrollment [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. Understanding that electronic data exchange has historically been limited among patients with traumatic injuries, we sought to assess the feasibility of mobile health tracking in patients with rib fractures by using a smartphone app to monitor postdischarge recovery.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>All consecutive adult patients with ≥1 rib fracture admitted to the trauma service from July to August 2022 were approached. Interested and eligible patients were enrolled and had the app (pilot available only in English and for iOS devices) loaded on their phones. The app was developed by the authors for use at a single, large, urban, academic, level I trauma center. After discharge, patients actively entered data on pain severity, opioid medication use, and bowel movement frequency. Patient step count was passively collected by the app. Data were stored and accessible in the electronic health record (EHR; <xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Smartphone app and electronic health record data retrieval: (A) the patient-facing smartphone app, including data entry for pain severity, use of opioid pain medication, frequency of bowel movements, and step count, and (B) the corresponding data review interface accessible to the provider within the electronic health record. YTD: year to date.</p>
          </caption>
          <graphic xlink:href="formative_v8i1e52726_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This quality improvement effort was undertaken with the support and within the standard clinical practice of the trauma surgery service. All patients admitted with rib fractures were offered the use of the hospital-approved postdischarge smartphone app; patients could stop use or remove the app from their phones at any time. Patients were not compensated for app use. Patients were informed that their providers would be able to access data they entered into the app solely via their existing EHR and that the app was not a means for urgent communication. A review of the quality improvement project was performed; no separate institutional review board approval or consent was required, and only the clinical team had access to identifiable data.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>During the pilot period, 25 patients with rib fractures were admitted to the trauma service (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
      <p>Of the 25 patients, 2 (8%) participated in the study. The other 23 (92%) patients did not participate for the following reasons: 6 (24%) had prohibitively low functional status (delirium, dementia, or traumatic brain injury), 8 (32%) did not have an iOS device (used an Android device or feature phone or did not have a mobile phone), 2 (8%) did not speak English, 5 (20%) declined participation, and 2 (8%) could not download the app while admitted due to patient or team member unavailability and the need for in-hospital enrollment. Both patients who used the app had multiple injuries and recovered to their preinjury functional status without complication. They reported data for 2 days and 2 weeks after discharge, respectively, and disclosed no problems with app use.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Patient characteristics and results of attempted app download. The age, sex, mechanism of injury, and injury burden including the presence of rib fractures for patients approached for app download are shown. The results of attempted app download are described, including common barriers to app use.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="30"/>
          <col width="620"/>
          <col width="0"/>
          <col width="0"/>
          <col width="320"/>
          <thead>
            <tr valign="top">
              <td colspan="5">Variable</td>
              <td>Value</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="6">
                <bold>Characteristics of patients admitted with rib fractures in a 1 month period (n=25)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Age (years), median (IQR)</td>
              <td colspan="2">69 (25-91)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="5">
                <bold>Sex, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Male</td>
              <td colspan="3">17 (68)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Female</td>
              <td colspan="3">8 (32)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="5">
                <bold>Mechanisms of injury, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Falls</td>
              <td colspan="3">13 (52)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Vehicular accidents</td>
              <td colspan="3">7 (28)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="5">
                <bold>Injuries, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Rib fractures with or without associated pneumothorax</td>
              <td colspan="3">7 (28)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Rib fractures and other traumatic injury</td>
              <td colspan="3">18 (72)</td>
            </tr>
            <tr valign="top">
              <td colspan="6">
                <bold>Results of attempted app download, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Downloaded and used the app</td>
              <td colspan="2">2 (8)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Prohibitively low functional status</td>
              <td colspan="2">6 (24)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">No iPhone</td>
              <td colspan="2">8 (32)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Non-English speaker</td>
              <td colspan="2">2 (8)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Declined participation</td>
              <td colspan="2">5 (20)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">Not available at attempt to download</td>
              <td colspan="2">2 (8)</td>
            </tr>
          </tbody>
        </table>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>We developed a novel smartphone app to collect patient-reported postdischarge data within the existing EHR. However, we observed patient, institutional, and process-related obstacles that limited study participation by patients with traumatic rib fractures. These limitations appear to extend to the general trauma population, as we anecdotally encountered similar results when we engaged patients admitted to the trauma service with injuries other than rib fractures.</p>
      <p>Patients with traumatic injuries, often from vulnerable populations, present unexpectedly and urgently. It is not possible to meet them in clinic prior to presentation for planned enrollment. Further, patients with traumatic injuries may not have access to a smartphone or have the ability to use a postdischarge smartphone app. Faced with the stress of injury, patients may decline to participate and require additional incentives to use such technology. This reluctance may be amplified when it is unclear how their participation will aid recovery.</p>
      <p>We did not observe technical or user-reported issues with app use. However, the onboarding process was burdensome to team members and patients. Streamlining this within the existing clinical and technological infrastructure might improve onboarding but requires substantial institutional investment in EHR customization, as well as the allocation of already limited human resources for enrollment. To reach more patients, an Android app is being developed.</p>
      <p>Smartphone apps for the collection of patient-generated data represent a new opportunity for postdischarge management of patients who sustain traumatic injury. The success of future work requires the acknowledgment of the described limitations. Researchers should use an implementation science framework [<xref ref-type="bibr" rid="ref7">7</xref>] to better understand the requirements and motivations of key stakeholders, leverage technology to understand the postdischarge patient experience, and integrate such tools effectively for personalized trauma care.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>All shareable data are included in this paper; additional data are not publicly available given the potential for patient reidentification.</p>
      </sec>
    </notes>
    <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="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Rib fracture</article-title>
          <source>StatPearls</source>
          <year>2023</year>
          <month>8</month>
          <day>8</day>
          <publisher-loc>Treasure Island, FL</publisher-loc>
          <publisher-name>StatPearls Publishing</publisher-name>
        </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>Lavallee</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Austin</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bloch</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lawrence</surname>
              <given-names>SO</given-names>
            </name>
            <name name-style="western">
              <surname>McCall</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Munson</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Nery-Hurwit</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Amtmann</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>mHealth and patient generated health data: stakeholder perspectives on opportunities and barriers for transforming healthcare</article-title>
          <source>Mhealth</source>
          <year>2020</year>
          <month>1</month>
          <day>5</day>
          <volume>6</volume>
          <fpage>8</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32190619"/>
          </comment>
          <pub-id pub-id-type="doi">10.21037/mhealth.2019.09.17</pub-id>
          <pub-id pub-id-type="medline">32190619</pub-id>
          <pub-id pub-id-type="pii">mh-06-2019.09.17</pub-id>
          <pub-id pub-id-type="pmcid">PMC7063266</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>Nittas</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Lun</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ehrler</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Puhan</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Mütsch</surname>
              <given-names>Margot</given-names>
            </name>
          </person-group>
          <article-title>Electronic patient-generated health data to facilitate disease prevention and health promotion: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>10</month>
          <day>14</day>
          <volume>21</volume>
          <issue>10</issue>
          <fpage>e13320</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/10/e13320/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13320</pub-id>
          <pub-id pub-id-type="medline">31613225</pub-id>
          <pub-id pub-id-type="pii">v21i10e13320</pub-id>
          <pub-id pub-id-type="pmcid">PMC6914107</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>Tiase</surname>
              <given-names>VL</given-names>
            </name>
            <name name-style="western">
              <surname>Hull</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>McFarland</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Sward</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Del Fiol</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Staes</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Weir</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Cummins</surname>
              <given-names>MR</given-names>
            </name>
          </person-group>
          <article-title>Patient-generated health data and electronic health record integration: a scoping review</article-title>
          <source>JAMIA Open</source>
          <year>2020</year>
          <month>12</month>
          <volume>3</volume>
          <issue>4</issue>
          <fpage>619</fpage>
          <lpage>627</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33758798"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaa052</pub-id>
          <pub-id pub-id-type="medline">33758798</pub-id>
          <pub-id pub-id-type="pii">ooaa052</pub-id>
          <pub-id pub-id-type="pmcid">PMC7969964</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>Semple</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Armstrong</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Mobile applications for postoperative monitoring after discharge</article-title>
          <source>CMAJ</source>
          <year>2017</year>
          <month>01</month>
          <day>09</day>
          <volume>189</volume>
          <issue>1</issue>
          <fpage>E22</fpage>
          <lpage>E24</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.cmaj.ca/cgi/pmidlookup?view=long&#38;pmid=27920015"/>
          </comment>
          <pub-id pub-id-type="doi">10.1503/cmaj.160195</pub-id>
          <pub-id pub-id-type="medline">27920015</pub-id>
          <pub-id pub-id-type="pii">cmaj.160195</pub-id>
          <pub-id pub-id-type="pmcid">PMC5224949</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>Liao</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>YT</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Ooyang</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>CY</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>YP</given-names>
            </name>
            <name name-style="western">
              <surname>Hsieh</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>CC</given-names>
            </name>
          </person-group>
          <article-title>An image-based mobile health app for postdrainage monitoring: usability study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>08</month>
          <day>28</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>e17686</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/8/e17686/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17686</pub-id>
          <pub-id pub-id-type="medline">32857060</pub-id>
          <pub-id pub-id-type="pii">v22i8e17686</pub-id>
          <pub-id pub-id-type="pmcid">PMC7486677</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>Neuman</surname>
              <given-names>HB</given-names>
            </name>
            <name name-style="western">
              <surname>Kaji</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Haut</surname>
              <given-names>ER</given-names>
            </name>
          </person-group>
          <article-title>Practical guide to implementation science</article-title>
          <source>JAMA Surg</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>155</volume>
          <issue>5</issue>
          <fpage>434</fpage>
          <lpage>435</lpage>
          <pub-id pub-id-type="doi">10.1001/jamasurg.2019.5149</pub-id>
          <pub-id pub-id-type="medline">31995157</pub-id>
          <pub-id pub-id-type="pii">2759267</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
