<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v8i4e30767</article-id>
      <article-id pub-id-type="pmid">34951599</article-id>
      <article-id pub-id-type="doi">10.2196/30767</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Perceptions of Older Men Using a Mobile Health App to Monitor Lower Urinary Tract Symptoms and Tamsulosin Side Effects: Mixed Methods Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Johnson II</surname>
            <given-names>Theodore</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Cavadas</surname>
            <given-names>Vitor</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hidki</surname>
            <given-names>Asmaa</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Wang</surname>
            <given-names>Elizabeth Y</given-names>
          </name>
          <degrees>MD, MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5226-7258</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Breyer</surname>
            <given-names>Benjamin N</given-names>
          </name>
          <degrees>MD, MAS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0532-048X</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Austin W</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2811-7385</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Rios</surname>
            <given-names>Natalie</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2583-1241</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Oni-Orisan</surname>
            <given-names>Akinyemi</given-names>
          </name>
          <degrees>PharmD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5897-5543</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Steinman</surname>
            <given-names>Michael A</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9564-9480</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Sim</surname>
            <given-names>Ida</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1045-8459</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Kenfield</surname>
            <given-names>Stacey A</given-names>
          </name>
          <degrees>ScD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1585-7352</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Bauer</surname>
            <given-names>Scott R</given-names>
          </name>
          <degrees>MD, MS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <address>
            <institution>University of California San Francisco</institution>
            <addr-line>550 16th St, 6th floor</addr-line>
            <addr-line>Box 1695</addr-line>
            <addr-line>San Francisco, CA, 94121</addr-line>
            <country>United States</country>
            <phone>1 4152214810 ext 24322</phone>
            <email>Scott.Bauer@ucsf.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4908-1924</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Columbia Vagelos College of Physicians and Surgeons</institution>
        <addr-line>New York, NY</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>University of California San Francisco</institution>
        <addr-line>San Francisco, CA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Scott R Bauer <email>Scott.Bauer@ucsf.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Oct-Dec</season>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>24</day>
        <month>12</month>
        <year>2021</year>
      </pub-date>
      <volume>8</volume>
      <issue>4</issue>
      <elocation-id>e30767</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>5</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>4</day>
          <month>7</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>28</day>
          <month>8</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>31</day>
          <month>8</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Elizabeth Y Wang, Benjamin N Breyer, Austin W Lee, Natalie Rios, Akinyemi Oni-Orisan, Michael A Steinman, Ida Sim, Stacey A Kenfield, Scott R Bauer. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 24.12.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2021/4/e30767" xlink:type="simple"/>
      <related-article related-article-type="companion" id="v5i12e30762" ext-link-type="doi" xlink:href="10.2196/30762" vol="5" page="e30762" xlink:title="See also the companion paper from the same research project:" xlink:type="simple">https://formative.jmir.org/2021/12/e30762</related-article>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Mobile health (mHealth) apps may provide an efficient way for patients with lower urinary tract symptoms (LUTS) to log and communicate symptoms and medication side effects with their clinicians.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The aim of this study was to explore the perceptions of older men with LUTS after using an mHealth app to track their symptoms and tamsulosin side effects.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Structured phone interviews were conducted after a 2-week study piloting the daily use of a mobile app to track the severity of patient-selected LUTS and tamsulosin side effects. Quantitative and qualitative data were considered.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>All 19 (100%) pilot study participants completed the poststudy interviews. Most of the men (n=13, 68%) reported that the daily questionnaires were the right length, with 32% (n=6) reporting that the questionnaires were too short. Men with more severe symptoms were less likely to report changes in perception of health or changes in self-management; 47% (n=9) of the men reported improved awareness of symptoms and 5% (n=1) adjusted fluid intake based on the questionnaire. All of the men were willing to share app data with their clinicians. Thematic analysis of qualitative data yielded eight themes: (1) orientation (setting up app, format, symptom selection, and side-effect selection), (2) triggers (routine or habit and symptom timing), (3) daily questionnaire (reporting symptoms, reporting side effects, and tailoring), (4) technology literacy, (5) perceptions (awareness, causation or relevance, data quality, convenience, usefulness, and other apps), (6) self-management, (7) clinician engagement (communication and efficiency), and (8) improvement (reference materials, flexibility, language, management recommendations, and optimize clinician engagement).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>We assessed the perceptions of men using an mHealth app to monitor and improve management of LUTS and medication side effects. LUTS management may be further optimized by tailoring the mobile app experience to meet patients’ individual needs, such as tracking a greater number of symptoms and integrating the app with clinicians’ visits. mHealth apps are likely a scalable modality to monitor symptoms and improve care of older men with LUTS. Further study is required to determine the best ways to tailor the mobile app and to communicate data to clinicians or incorporate data into the electronical medical record meaningfully.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>BPH</kwd>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>telehealth</kwd>
        <kwd>telemedicine</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Lower urinary tract symptoms (LUTS) comprise a complex and heterogenous syndrome, including urinary urgency, urinary frequency, weak urinary stream, hesitancy, straining, incomplete bladder emptying, nocturia, and urinary incontinence [<xref ref-type="bibr" rid="ref1">1</xref>]. LUTS are chronic and progressive [<xref ref-type="bibr" rid="ref2">2</xref>], and they affect as many as 72% of men over the age of 40 years [<xref ref-type="bibr" rid="ref3">3</xref>]. First-line treatment for LUTS due to benign prostatic hyperplasia (BPH) includes medical management with alpha-1-andrenergic receptor blockers, such as tamsulosin. Although some men achieve symptomatic relief with this regimen, many do not, and placebo effects make it difficult for patients and their providers to determine true clinical response [<xref ref-type="bibr" rid="ref4">4</xref>]. More than 10% of men taking tamsulosin will also suffer from undesirable side effects, such as dizziness, orthostatic hypotension, headache, sexual dysfunction, and rhinitis. In addition to contributing to unnecessary polypharmacy, these potential side effects can be debilitating and a major concern for patients with LUTS, especially in older men or men who achieve minimal or no symptomatic relief from tamsulosin [<xref ref-type="bibr" rid="ref5">5</xref>]. Thus, successful management of LUTS requires a balance of both benefits and harms from interventions, including tamsulosin, which are highly variable between individuals and may not be accurately communicated or recorded during routine medical encounters. Lowering barriers to improve communication of symptoms and medication side effects may improve understanding and adherence in a significant proportion of men who are incorrectly labeled as refractory to medical LUTS management. In addition, mobile apps may increase patients’ awareness of variability in symptom severity, identify triggers of symptoms or side effects, assist clinicians by quantifying the efficacy and adverse effects of LUTS interventions, and ultimately facilitate shared decision making based on whether a medication is continuing to provide net benefit to the patient.</p>
      <p>Mobile apps are increasingly used to monitor symptoms and side effects in a wide range of urologic conditions. For men with LUTS, mobile apps have been successfully used to administer questionnaires [<xref ref-type="bibr" rid="ref6">6</xref>], increase peak flow rate (ie, with the sound of running water) [<xref ref-type="bibr" rid="ref7">7</xref>], and guide clinical decision making [<xref ref-type="bibr" rid="ref8">8</xref>]. Given these findings, a well-designed and thoughtfully implemented mobile app could streamline the way that patients report symptoms and improve characterization of LUTS severity and variability. In addition, mobile health (mHealth) apps may provide an efficient mechanism to generate a repository of patient data that could be used to identify new LUTS phenotypes, define treatment response or harms, and ultimately help clinicians tailor medical management.</p>
      <p>To our knowledge, the use of mobile apps to track symptoms and side effects in men with LUTS has not been studied using qualitative methodology. Qualitative studies are uniquely equipped to explore the patient perspective and help ensure that future intervention designs are grounded in the patient experience. Thus, we designed the Placebo-Controlled, Randomized, Patient-Selected Outcomes, N-of-1 Trials (PERSONAL) pilot study, a 2-week intervention to determine the feasibility and acceptability of daily LUTS severity and tamsulosin side-effect assessment through a mobile app among older men with LUTS receiving chronic tamsulosin therapy. Following this study period, we aimed to explore the men’s insights about using an mHealth app to track their symptoms and medication side effects via interviews. Here, we present the findings and implications of the first mixed methods study exploring the experience of men with LUTS after using an mHealth app to track their symptoms and medication side effects.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>A convenience sample of 19 men was recruited from an academic urology clinic for the PERSONAL pilot study. Recruitment was targeted at men with LUTS who may be unsure if the benefits of tamsulosin outweighed the harms, specifically older men who were both receiving chronic tamsulosin therapy and interested in tracking their daily urinary symptoms and tamsulosin side effects outside of regular clinic visits. Men were eligible if they were taking tamsulosin for LUTS for at least 12 months, received care from a urologist at our institution, and had previously consented to being contacted for research purposes via the electronic medical record. The sample size was based on feasibility of recruitment. Additional inclusion and exclusion criteria are outlined in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. First, the participants completed a baseline survey describing their LUTS severity and medication side effects; in the same survey, they selected up to three individual symptoms and three tamsulosin side effects to track daily for 2 weeks. Then, the participants underwent an orientation phone call to set up the PERSONAL mobile app; they were guided on how to use the app and had the opportunity to ask questions. The participants received daily questionnaires through the mobile app at a prespecified time of their choice, and the questionnaire data from all participants were then collected in a secure cloud-based database made accessible to the research team; participants could review their own results throughout the study period. Additional study design details were previously published [<xref ref-type="bibr" rid="ref9">9</xref>], and results pertaining to the PERSONAL pilot study itself will be published in a separate manuscript.</p>
      </sec>
      <sec>
        <title>Interviews</title>
        <p>To gain a more nuanced understanding of participants’ experiences using the PERSONAL mobile app following the 2-week data collection period, semistructured feasibility interviews were administered by telephone, ranging from 10 to 30 minutes. The interviewer (EYW) was a medical trainee and research associate with formal qualitative research training, who had no interactions with the participants prior to the interviews. The interview guide is available in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. Responses were recorded in REDCap (Research Electronic Data Capture) and field notes were made afterward. Due to the relatively structured nature of interview questions, qualitative responses were comprehensively transcribed in REDCap during the phone interviews, but were not audio-recorded. EYW manually coded these open-ended responses using a data-driven approach; codes were iteratively refined into themes. EYW reviewed codes and themes intermittently with coauthors SAK and SRB.</p>
      </sec>
      <sec>
        <title>Statistical Approach</title>
        <p>Continuous variables were reported using median and IQR, and categorical data were summarized using frequencies. Thematic analysis of open-ended questions yielded 22 codes, which were refined into eight themes. EYW completed initial coding; codes and themes were finalized in discussion with coauthors SRB and SAK. Qualitative data were integrated relative to quantitative responses [<xref ref-type="bibr" rid="ref10">10</xref>]. The study is reported in concordance with the Consolidated Criteria for Reporting Qualitative Research (COREQ) checklist [<xref ref-type="bibr" rid="ref11">11</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>All 19 participants who participated in the 2-week PERSONAL pilot study completed poststudy interviews; their demographics and self-selected symptoms and side effects are reported in <xref ref-type="table" rid="table1">Table 1</xref>. All participants found the setup process easy via phone orientation; the majority of participants (n=15, 79%) reported no issues at all, and 4 participants (21%) mentioned minor initial issues, which were easy to resolve (device incompatibility, asked partner to help download app, etc). Some participants suggested an online video or a written document in addition to the phone orientation. Stated reasons for wanting a written document included lower English proficiency and to have materials for future reference.</p>
      <p>About two-thirds of participants felt that the questionnaires were just the right length, and about one-third felt that they were too short; the latter participants reported concerns about adequate detail or the appropriate gradations used in the questions and answer choices, commenting that those with milder symptoms might prefer additional gradations on the lower end of the spectrum. Some participants reported frustration about the side-effects questions, as they had difficulty parsing out which side effects to specifically attribute to tamsulosin. A few men were willing to log answers for seven to eight symptoms and side effects rather than the recommended limit of three. About two-thirds of participants set app notifications for mornings, which they found particularly useful for reporting nocturnal symptoms, such as nocturia.</p>
      <p>Some participants reported that they did not receive daily notifications via the mobile app due to technical difficulties, but the large majority of participants completed the questionnaire by “habit” at the same time every day—no participants logged responses purely as an immediate response to bothersome symptoms. Out of 19 participants, 9 (47%) felt that this app changed their perception of their health or LUTS management; 8 of these 9 patients (89%) reported increased awareness of symptoms and 1 participant (11%) was able to adjust his fluid intake to improve LUTS. All participants would be willing to share data with their clinician to complement their usual care.</p>
      <p>Almost half (8/19, 42%) of the participants reported prior use of other health apps or devices. When prompted to compare those experiences with the study app, most agreed that this app had a simpler interface than others they had encountered, though 1 participant (5%) noted that the app may still be inaccessible in populations with lower English proficiency.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Participant demographics and responses to structured interviews.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="770"/>
          <col width="200"/>
          <thead>
            <tr valign="top">
              <td colspan="2">Characteristic</td>
              <td>Value (N=19)</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="2">Age (years), median (IQR)</td>
              <td>70 (62-75)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Race, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>White</td>
              <td>13 (68)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Black</td>
              <td>0 (0)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Asian</td>
              <td>3 (16)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Other</td>
              <td>3 (16)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Ethnicity, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Not Hispanic, Latino, or Spanish</td>
              <td>16 (84)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Mexican, Mexican American, or Chicano</td>
              <td>1 (5)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Puerto Rican</td>
              <td>1 (5)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Another Hispanic, Latino, or Spanish origin</td>
              <td>1(5)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Preferred orientation format, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Online video</td>
              <td>10 (53)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>On-demand phone support</td>
              <td>6 (32)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>In-person demonstration</td>
              <td>4 (21)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Phone orientation</td>
              <td>3 (16)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Length of daily questionnaire, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Took more time than it should</td>
              <td>0 (0)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>About right</td>
              <td>13 (68)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Took less time than it should</td>
              <td>6 (32)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Time of day questionnaire usually completed, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Morning</td>
              <td>13 (68)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Afternoon</td>
              <td>1 (5)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Evening</td>
              <td>4 (21)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Sporadic</td>
              <td>1 (5)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Frequency of app usage without alert or notification, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Never</td>
              <td>6 (32)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>A few times per week</td>
              <td>11(58)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>More than half of the days per week</td>
              <td>1 (5)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Once per day</td>
              <td>2 (11)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>2-3 times per day</td>
              <td>0 (0)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>More than 3 times per day</td>
              <td>0 (0)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">Usefulness of urinary symptom assessment<sup>a</sup>, median (IQR)</td>
              <td>4 (4-4)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">Usefulness of medication side-effect assessment<sup>a</sup>, median (IQR)</td>
              <td>4 (2-5)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">Reported change in urinary symptom management due to the use of the PERSONAL<sup>b</sup> app (during the 2-week study), n (%)</td>
              <td>9 (47)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">Would allow clinician to see PERSONAL app data, n (%)</td>
              <td>19 (100)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">Reported use of other health apps or devices, n (%)</td>
              <td>8 (42)</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Other health apps or devices, n (%)</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Fitbit</td>
              <td>4 (21)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Other<sup>c</sup></td>
              <td>6 (32)</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>On a scale of 1 to 5, where 1 is “not at all useful” and 5 is “very useful.”</p>
          </fn>
          <fn id="table1fn2">
            <p><sup>b</sup>PERSONAL: Placebo-Controlled, Randomized, Patient-Selected Outcomes, N-of-1 Trials.</p>
          </fn>
          <fn id="table1fn3">
            <p><sup>c</sup>Other health apps or devices include Fitbit-like device, Apple Watch, MyFitnessPal, Brainscape, and the iPhone heart rate monitor.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>The qualitative analysis generated eight themes (ie, orientation, triggers, daily questionnaire, technology literacy, perceptions, self-management, clinician engagement, and improvement) and 22 codes organized into three categories (ie, mHealth app, clinical use, and next steps) whose relationships are illustrated in <xref rid="figure1" ref-type="fig">Figure 1</xref>. Definitions for themes and select quotations organized by code are included in <xref ref-type="table" rid="table2">Table 2</xref>. For example, under the theme “perceptions” and code “usefulness,” one participant said, “I learned some things that I didn’t know about my condition before; I was surprised about what I learned about my symptoms—'cause then I can talk to my doctor about it.” Under the theme “clinician engagement” and code “efficiency,” another participant said, “I think it would help that we would be looking at this issue a little more closely as opposed to a casual conversation during the visit. I think the doctor would be able to monitor the frequency of symptoms I’m having either throughout the night or the day and we can decide if the dosage needs to be changed.” Additional quotations are presented in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Codes and themes generated from the qualitative analysis. Orange boxes represent themes and blue boxes represent codes.</p>
        </caption>
        <graphic xlink:href="humanfactors_v8i4e30767_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Selected participant quotations organized by themes and codes.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="30"/>
          <col width="240"/>
          <col width="700"/>
          <thead>
            <tr valign="top">
              <td colspan="3">Themes and codes</td>
              <td>Quotations</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="4">
                <bold>Mobile health app</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Orientation</bold>
                <bold>: participants discussed the orientation process, from the assistance they received while setting up the app to the symptom and side-effect selection</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Setting up app</td>
              <td>“Fairly easy. Good to have someone on the other line to take me through it step by step.”<break/>“Instructions were very straightforward, and the graphics were easy to read.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Format</td>
              <td>“The way it was done in the study was good: email and phone orientation.”<break/>“Would prefer written documentation in case there were issues.”<break/>“Send link by email and I can follow instructions—I don’t need any human contact.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Symptom selection</td>
              <td>“Disappointed that it was limited to three, would have done up to seven to eight.”<break/>“I have more symptoms than the survey asked about—the top three weren’t enough for me.”<break/>“The more items I was keeping track of, the more I was attuned to my symptoms, so more questions would be good.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Side-effect selection</td>
              <td>“Would have preferred to track more side effects. Initially thought some of these were just symptoms, not side effects, like runny nose. I also have allergies, but definitely could have been tamsulosin.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Triggers: participants discussed their experiences and preferences regarding reminders and notifications from the mobile app</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Routine or habit</td>
              <td>“Never received notifications, I went in and answered by habit.”<break/>“Just did the questions before bed, whether I got the notification or not yet that day. I was getting daily notifications.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Symptom timing</td>
              <td>“Sometimes I would remember to answer questions in the morning before the notification—my symptoms were mostly during the night, so I remembered to log in the morning.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Daily questionnaire</bold>
                <bold>: participants discussed their experiences completing daily questionnaires within the mobile app</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Reporting symptoms</td>
              <td>“Asked about symptoms that weren’t applicable and did not ask about leakage.”<break/>“Maybe some questions seemed like they would be too simple for others but were good for me.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Reporting side effects</td>
              <td>“Impossible to answer—whatever side effects could be caused by other things. All of that was kind of irrelevant—couldn’t relate anything to Flomax.”<break/>“Hard to distinguish which symptoms are from what.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Tailoring</td>
              <td>“Frustrated because some issues were not questioned in the survey. Not sure if I’m having them because of meds or not. The survey was simplistic, basic. Would have preferred more depth—and to be able to note the thoughts before this interview.”<break/>“Some questions didn’t apply.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Technology literacy: participants discussed their ability to engage with technology</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>N/A<sup>a</sup></td>
              <td>“It’s very easy for everybody, even people like me, old and not very good with technology.”</td>
            </tr>
            <tr valign="top">
              <td colspan="4">
                <bold>Clinical use</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Perceptions</bold>
                <bold>: participants discussed their perceptions as a result of using the mobile app</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Awareness</td>
              <td>“Brought more awareness to the issue; and now I think about it more than before. I kind of wonder how much it affects my sleep and it brings the awareness to the forefront.”<break/>“Became more attuned to your symptoms, more attentive—had never previously paid attention.”<break/>“Made me more aware of the topic.”<break/>“Made me more conscious of [symptoms]. Haven’t seen a doctor in a while, keeps the issues fresh on my mind so I can track them.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Causation or relevance</td>
              <td>“No relationship between what Flomax does. The app tells you what you’re feeling but doesn’t say why you feel that way.”<break/>“I didn’t know if I was getting side effects, and I didn’t know if they were related to the meds or just overall bladder problems; no baseline to compare to.”<sup>b</sup><break/>“What if you take eight meds? This is just one medication. Lots of meds have the same side effects, ie, headaches, dizziness.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Data quality</td>
              <td>“The questions were limiting. The number of options for getting up at night were recorded as a range of numbers rather than a precise number. Trying to track things means you want to be more specific.”<break/>“[Would prefer] having more longitudinal data—duration of symptoms.”<break/>“Do you have this problem 0 times, 1-2, et cetera, well geez I’m more like 0-1, but there’s no way to put 0-1. Having a selection process that takes in the range of options, I would suspect most people the frequency is variable from day to day. So, if you have 0-2, that certainly includes 0-1 and 1-2, and I would think that frequency question should be taken into account, maybe the lower levels more inclusively, rather than feeling like there’s a gap or uncertainty in the choice.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Convenience</td>
              <td>“Would have loved to continue this study, if possible, I could always record on paper but it’s not as convenient. With the app, it’s just clicking buttons.”<break/>“It was short enough to stick to every day.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Usefulness</td>
              <td>“I learned some things that I didn’t know about my condition before; I was surprised about what I learned about my symptoms—'cause then I can talk to my doctor about it.”<break/>“Same answers every day. It’s a one-way survey, not a dialogue—not sure if the answers are good enough to change management.”<break/>“Nice to have a tool to help with aging issues.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Other apps</td>
              <td>“The PERSONAL<sup>c</sup> app is more user friendly, and you only have to provide simple responses.”<break/>“This app was very basic, not even an app, just a questionnaire. An app tries to change behavior—there was nothing in the app that seems to have any influence on behavior.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Self-management:</bold>
                <bold>participants discuss using the questionnaires to guide self-management</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>N/A</td>
              <td>“More awareness of symptoms—the morning timing is very appropriate for answering the questions. So maybe that day based on my doctor’s recommendations I will change my diet, for example, citrus/salt changes. I analyze why certain nights are worse than others.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>N/A</td>
              <td>“I’m going to talk to my doctor and tell him that I did this and tell him what I learned.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Clinician engagement: participants discuss their preferences for clinician engagement</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Communication</td>
              <td>“I would like my doctor to have every scintilla of data they can have.”<break/>“It made me more aware of leakage, because of incomplete emptying, and I want to share this with her.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Efficiency</td>
              <td>“It would help: the more that you can do electronically to help your doctor, the less time they have to spend on the office visits, especially given how busy they are. That would be helpful in monitoring.”<break/>“I think it would help that we would be looking at this issue a little more closely as opposed to a casual conversation during the visit. I think the doctor would be able to monitor the frequency of symptoms I’m having either throughout the night or the day and we can decide if the dosage needs to be changed.”</td>
            </tr>
            <tr valign="top">
              <td colspan="4">
                <bold>Next steps</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Improvement:</bold>
                <bold>participants discuss potential areas of improvement for the mobile app and its integration into clinical care</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Reference materials</td>
              <td>“Maybe save [the symptom list] for participants so they can reference which were symptoms versus side effects.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Flexibility</td>
              <td>“More open ended, the questions from the app were overly simple.”<break/>“Wanted afternoon/evening reminders, but was getting them in the morning, but I was reflecting on the day before rather than for the next 24 hours and that based on the person who set it up and I thought we could change it from AM to PM.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Language</td>
              <td>“Based on experience as a nurse in Oakland where 90% of patients were Spanish speaking, many underserved patients over the age of 60 would not be able to benefit from this app as it currently stands.”<break/>“Because English isn’t first my language, something to read would be best so I can look it up on Google Translate.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Management recommendations</td>
              <td>“There were no directions on how to manage one’s symptoms based on the answers.”<break/>“Maybe add questions in the app about how many cups of water to better help with management; could have scores/goals incorporated in the app to keep you on track, like Fitbit.”</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Optimize clinician engagement</td>
              <td>“Yes—of note, I had a video appointment with my urologist during the 2 weeks, and told him about the study. My urologist’s reaction was ‘zero’ because the urologist didn’t know what it was.”</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table2fn1">
            <p><sup>a</sup>N/A: not applicable; there were no codes under this theme.</p>
          </fn>
          <fn id="table2fn2">
            <p><sup>b</sup>N-of-1 is supposed to help establish a baseline to help reduce this type of confusion.</p>
          </fn>
          <fn id="table2fn3">
            <p><sup>c</sup>PERSONAL: Placebo-Controlled, Randomized, Patient-Selected Outcomes, N-of-1 Trials.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>In sum, mHealth apps may play an important role in the chronic management of LUTS. In this study, the key themes that emerged from our qualitative data were (1) orientation, (2) triggers, (3) daily questionnaire, (4) technological literacy, (5) perceptions, (6) self-management, (7) clinician engagement, and (8) improvement. Consistent with prior literature [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>], our participants had adequate technology literacy to use this app on a daily basis. The questionnaires were short enough for daily adherence, though a subset of participants with more severe or poorly controlled symptoms believed the questionnaires were not encompassing enough. These participants either felt that the app’s closed-ended question format impeded accurate reporting, that they wanted to track symptoms that were not selected, or they wanted to track symptoms in addition to the ones selected. Given the desire for increased flexibility in communication, certain patients may benefit from a free-text or messaging option. Some patients taking multiple medications expressed frustration at not being able to differentiate which side effects were attributable to tamsulosin, further supporting the need for individualized tracking and potentially individual crossover trials (eg, N-of-1 studies). Patients with prior experience logging health information on a daily basis mentioned that mobile apps are a great way to store data and communicate important information with their clinicians, especially compared with recording on paper. Participants with more severe symptoms seemed less empowered to use their daily logs to change management, potentially because even their clinic visits with their clinicians failed to yield symptomatic improvement, among other reasons.</p>
      <p>Most American men and adults over the age of 65 years own a smartphone [<xref ref-type="bibr" rid="ref14">14</xref>]. Mobile apps are widely used by the general public, and the number of urology-related mobile apps has multiplied in recent decades [<xref ref-type="bibr" rid="ref15">15</xref>]. These apps support patients with a wide range of urologic conditions, but their usage is unstandardized and unregulated [<xref ref-type="bibr" rid="ref16">16</xref>]; in addition, mobile app usage remains inconsistently integrated with routine clinical care [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
      <p>Studies support the need for expert involvement in mobile app development, dissemination, and regulation [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. In our study, patients were unanimously willing to share this health data with their clinicians with the goal of optimizing their urologic care. Likewise, in a British study, urologists reported considerable interest in incorporating various mobile apps into their urologic practices [<xref ref-type="bibr" rid="ref20">20</xref>]. Leveraging the doctor-patient relationship in the early phases of using the PERSONAL app would likely mitigate both patient confusion regarding which symptoms are medication side effects versus isolated symptoms, as well as clinician confusion when their patients ask to discuss data from a mobile app they are using to track their symptoms. Becoming more aware of symptoms via a mobile app may also help patients hone their questions when visiting their physician. Ultimately, mobile apps may become an important part of LUTS management, such as motivating patients and providers to stop chronic tamsulosin therapy if it is no longer helpful or causing nonspecific yet bothersome side effects. Tracking symptoms regularly using an mHealth app could also potentially help identify low-frequency, but serious, events associated with tamsulosin use, such as falls [<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      <p>This study offers insights into the benefits and patient concerns associated with tracking symptoms via a mobile app among older men with benign urologic conditions, but there are some limitations. Traditionally, qualitative interviews are audio-recorded unstructured or semistructured interviews. Given the focus of the study, the homogeneous population, and the strong convergence of responses around a few common themes, we likely reached data saturation among 19 participants [<xref ref-type="bibr" rid="ref22">22</xref>]. We solicited a wide range of responses, but less structured interviews in more diverse patient populations are warranted in future studies; additional qualitative studies involving clinical providers could inform the best ways to incorporate the use of mobile apps into clinical care. While qualitative interviews allow study participants to discuss their experiences in more depth, some participants may have felt less candid than they would answering an online form.</p>
      <p>Despite the limitations, this is the first mixed methods study to examine the use of a mobile app to track symptoms in older men with LUTS. Importantly, these results suggest that mobile apps designed to improve symptom awareness and management may be adapted to benefit older men with LUTS due to BPH. As the use of mobile apps becomes increasingly popular, their usage in the health care setting will require further optimization. Tailoring to individual patients’ health and technology literacy levels, language proficiency, and symptom severity will be critical to maximizing the efficacy of these digital interventions. Incorporating the use of apps into clinical practice may play another important role, pending future study.</p>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Study inclusion and exclusion criteria.</p>
        <media xlink:href="humanfactors_v8i4e30767_app1.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Interview guide.</p>
        <media xlink:href="humanfactors_v8i4e30767_app2.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Participant feedback.</p>
        <media xlink:href="humanfactors_v8i4e30767_app3.docx" xlink:title="DOCX File , 26 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BPH</term>
          <def>
            <p>benign prostatic hyperplasia</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">COREQ</term>
          <def>
            <p>Consolidated Criteria for Reporting Qualitative Research</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">LUTS</term>
          <def>
            <p>lower urinary tract symptoms</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">PERSONAL</term>
          <def>
            <p>Placebo-Controlled, Randomized, Patient-Selected Outcomes, N-of-1 Trials</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">REDCap</term>
          <def>
            <p>Research Electronic Data Capture</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We would like to acknowledge our study participants.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>D'Ancona</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Haylen</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Oelke</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abranches-Monteiro</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Arnold</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Goldman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hamid</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Homma</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Marcelissen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rademakers</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Schizas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Singla</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Soto</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Tse</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>de Wachter</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Herschorn</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The International Continence Society (ICS) report on the terminology for adult male lower urinary tract and pelvic floor symptoms and dysfunction</article-title>
          <source>Neurourol Urodyn</source>
          <year>2019</year>
          <month>02</month>
          <volume>38</volume>
          <issue>2</issue>
          <fpage>433</fpage>
          <lpage>477</lpage>
          <pub-id pub-id-type="doi">10.1002/nau.23897</pub-id>
          <pub-id pub-id-type="medline">30681183</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Washington III</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Shinohara</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>McAninch</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Lue</surname>
              <given-names>TF</given-names>
            </name>
          </person-group>
          <article-title>Disorders of the bladder, prostate, and seminal vesicles</article-title>
          <source>Smith &#38; Tanagho's General Urology. 19th edition</source>
          <year>2020</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>McGraw Hill</publisher-name>
          <fpage>585</fpage>
        </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>Coyne</surname>
              <given-names>KS</given-names>
            </name>
            <name name-style="western">
              <surname>Sexton</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Milsom</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Irwin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kopp</surname>
              <given-names>ZS</given-names>
            </name>
            <name name-style="western">
              <surname>Chapple</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Kaplan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tubaro</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aiyer</surname>
              <given-names>LP</given-names>
            </name>
            <name name-style="western">
              <surname>Wein</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>The prevalence of lower urinary tract symptoms (LUTS) in the USA, the UK and Sweden: Results from the Epidemiology of LUTS (EpiLUTS) study</article-title>
          <source>BJU Int</source>
          <year>2009</year>
          <month>08</month>
          <volume>104</volume>
          <issue>3</issue>
          <fpage>352</fpage>
          <lpage>360</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1464-410X.2009.08427.x</pub-id>
          <pub-id pub-id-type="medline">19281467</pub-id>
          <pub-id pub-id-type="pii">BJU8427</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>van Leeuwen</surname>
              <given-names>JHS</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Busse</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bemelmans</surname>
              <given-names>BL</given-names>
            </name>
          </person-group>
          <article-title>The placebo effect in the pharmacologic treatment of patients with lower urinary tract symptoms</article-title>
          <source>Eur Urol</source>
          <year>2006</year>
          <month>09</month>
          <volume>50</volume>
          <issue>3</issue>
          <fpage>440</fpage>
          <lpage>452; discussion 453</lpage>
          <pub-id pub-id-type="doi">10.1016/j.eururo.2006.05.014</pub-id>
          <pub-id pub-id-type="medline">16753253</pub-id>
          <pub-id pub-id-type="pii">S0302-2838(06)00605-1</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>Malde</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Umbach</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wheeler</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Lytvyn</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cornu</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Gacci</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gratzke</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Herrmann</surname>
              <given-names>TRW</given-names>
            </name>
            <name name-style="western">
              <surname>Mamoulakis</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Rieken</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Speakman</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gravas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Drake</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Guyatt</surname>
              <given-names>GH</given-names>
            </name>
            <name name-style="western">
              <surname>Tikkinen</surname>
              <given-names>KAO</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of patients' values, preferences, and expectations for the diagnosis and treatment of male lower urinary tract symptoms</article-title>
          <source>Eur Urol</source>
          <year>2021</year>
          <month>06</month>
          <volume>79</volume>
          <issue>6</issue>
          <fpage>796</fpage>
          <lpage>809</lpage>
          <pub-id pub-id-type="doi">10.1016/j.eururo.2020.12.019</pub-id>
          <pub-id pub-id-type="medline">33461781</pub-id>
          <pub-id pub-id-type="pii">S0302-2838(20)30967-2</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>Kim</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Kwon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shim</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>HY</given-names>
            </name>
            <name name-style="western">
              <surname>Ko</surname>
              <given-names>YM</given-names>
            </name>
            <name name-style="western">
              <surname>Chun</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>YS</given-names>
            </name>
          </person-group>
          <article-title>Validation and reliability of a smartphone application for the International Prostate Symptom Score questionnaire: A randomized repeated measures crossover study</article-title>
          <source>J Med Internet Res</source>
          <year>2014</year>
          <month>02</month>
          <day>10</day>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>e38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2014/2/e38/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.3042</pub-id>
          <pub-id pub-id-type="medline">24513507</pub-id>
          <pub-id pub-id-type="pii">v16i2e38</pub-id>
          <pub-id pub-id-type="pmcid">PMC3936272</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>Kwon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Joung</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Seo</surname>
              <given-names>HK</given-names>
            </name>
          </person-group>
          <article-title>Changes in urination according to the sound of running water using a mobile phone application</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>e0126798</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0126798"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0126798</pub-id>
          <pub-id pub-id-type="medline">25978378</pub-id>
          <pub-id pub-id-type="pii">PONE-D-15-00648</pub-id>
          <pub-id pub-id-type="pmcid">PMC4433320</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>Choo</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Ku</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Oh</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Development of decision support formulas for the prediction of bladder outlet obstruction and prostatic surgery in patients with lower urinary tract symptom/benign prostatic hyperplasia: Part II, External validation and usability testing of a smartphone app</article-title>
          <source>Int Neurourol J</source>
          <year>2017</year>
          <month>04</month>
          <volume>21</volume>
          <issue>Suppl 1</issue>
          <fpage>S66</fpage>
          <lpage>S75</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.doi.org/10.5213/inj.1734854.427"/>
          </comment>
          <pub-id pub-id-type="doi">10.5213/inj.1734854.427</pub-id>
          <pub-id pub-id-type="medline">28446011</pub-id>
          <pub-id pub-id-type="pii">inj-1734854-427</pub-id>
          <pub-id pub-id-type="pmcid">PMC5426430</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>Bauer</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Breyer</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Oni-Orisan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Steinman</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sim</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>McCulloch</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Kenfield</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>PERSONAL: Feasibility study protocol for placebo-controlled, randomized n-of-1 trials of tamsulosin for lower urinary tract symptoms</article-title>
          <source>Front Digit Health</source>
          <year>2020</year>
          <volume>2</volume>
          <fpage>7</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/34713020"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2020.00007</pub-id>
          <pub-id pub-id-type="medline">34713020</pub-id>
          <pub-id pub-id-type="pmcid">PMC8521798</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>Creswell</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Fetters</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Ivankova</surname>
              <given-names>NV</given-names>
            </name>
          </person-group>
          <article-title>Designing a mixed methods study in primary care</article-title>
          <source>Ann Fam Med</source>
          <year>2004</year>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.annfammed.org/cgi/pmidlookup?view=long&#38;pmid=15053277"/>
          </comment>
          <pub-id pub-id-type="doi">10.1370/afm.104</pub-id>
          <pub-id pub-id-type="medline">15053277</pub-id>
          <pub-id pub-id-type="pmcid">PMC1466635</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>Tong</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sainsbury</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Craig</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Consolidated Criteria for Reporting Qualitative Research (COREQ): A 32-item checklist for interviews and focus groups</article-title>
          <source>Int J Qual Health Care</source>
          <year>2007</year>
          <month>12</month>
          <volume>19</volume>
          <issue>6</issue>
          <fpage>349</fpage>
          <lpage>357</lpage>
          <pub-id pub-id-type="doi">10.1093/intqhc/mzm042</pub-id>
          <pub-id pub-id-type="medline">17872937</pub-id>
          <pub-id pub-id-type="pii">mzm042</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>Morselli</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liaci</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nicoletti</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pecoraro</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gemma</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Polverino</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zaccaro</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sebastianelli</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Serni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Laguna</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>De La Rosette</surname>
              <given-names>JJMC</given-names>
            </name>
            <name name-style="western">
              <surname>Gravas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gacci</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The use of a novel smartphone app for monitoring male LUTS treatment during the COVID-19 outbreak</article-title>
          <source>Prostate Cancer Prostatic Dis</source>
          <year>2020</year>
          <month>12</month>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>724</fpage>
          <lpage>726</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32665609"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41391-020-0253-z</pub-id>
          <pub-id pub-id-type="medline">32665609</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41391-020-0253-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7359441</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>Anthony Berauk</surname>
              <given-names>VL</given-names>
            </name>
            <name name-style="western">
              <surname>Murugiah</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Soh</surname>
              <given-names>YC</given-names>
            </name>
            <name name-style="western">
              <surname>Chuan Sheng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>TW</given-names>
            </name>
            <name name-style="western">
              <surname>Ming</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Mobile health applications for caring of older people: Review and comparison</article-title>
          <source>Ther Innov Regul Sci</source>
          <year>2018</year>
          <month>05</month>
          <volume>52</volume>
          <issue>3</issue>
          <fpage>374</fpage>
          <lpage>382</lpage>
          <pub-id pub-id-type="doi">10.1177/2168479017725556</pub-id>
          <pub-id pub-id-type="medline">29714532</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <article-title>Mobile fact sheet</article-title>
          <source>Pew Research Center</source>
          <year>2019</year>
          <month>06</month>
          <day>12</day>
          <access-date>2021-12-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/internet/fact-sheet/mobile/">https://www.pewresearch.org/internet/fact-sheet/mobile/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mantica</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Malinaric</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dotta</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Paraboschi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Guano</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rebuffo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Garriboli</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Suardi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Van der Merwe</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Terrone</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Urology apps: Overview of current types and use</article-title>
          <source>Cent European J Urol</source>
          <year>2020</year>
          <volume>73</volume>
          <issue>3</issue>
          <fpage>369</fpage>
          <lpage>372</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/33133667"/>
          </comment>
          <pub-id pub-id-type="doi">10.5173/ceju.2020.0090</pub-id>
          <pub-id pub-id-type="medline">33133667</pub-id>
          <pub-id pub-id-type="pii">0090</pub-id>
          <pub-id pub-id-type="pmcid">PMC7587494</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Akbar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Magrabi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Safety concerns with consumer-facing mobile health applications and their consequences: A scoping review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>02</month>
          <day>01</day>
          <volume>27</volume>
          <issue>2</issue>
          <fpage>330</fpage>
          <lpage>340</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31599936"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz175</pub-id>
          <pub-id pub-id-type="medline">31599936</pub-id>
          <pub-id pub-id-type="pii">5585394</pub-id>
          <pub-id pub-id-type="pmcid">PMC7025360</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tapiero</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jefferson</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sung</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Limfueco</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cottone</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Landman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Clayman</surname>
              <given-names>RV</given-names>
            </name>
          </person-group>
          <article-title>Smartphone technology and its applications in urology: A review of the literature</article-title>
          <source>World J Urol</source>
          <year>2020</year>
          <month>10</month>
          <volume>38</volume>
          <issue>10</issue>
          <fpage>2393</fpage>
          <lpage>2410</lpage>
          <pub-id pub-id-type="doi">10.1007/s00345-019-02960-y</pub-id>
          <pub-id pub-id-type="medline">31598754</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00345-019-02960-y</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pereira-Azevedo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Carrasquinho</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Cardoso de Oliveira</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Cavadas</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Osório</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fraga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Castelo-Branco</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Roobol</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>mHealth in urology: A review of experts' involvement in app development</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>e0125547</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0125547"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0125547</pub-id>
          <pub-id pub-id-type="medline">25984916</pub-id>
          <pub-id pub-id-type="pii">PONE-D-15-06113</pub-id>
          <pub-id pub-id-type="pmcid">PMC4436179</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pereira-Azevedo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Osório</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cavadas</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Fraga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Carrasquinho</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Cardoso de Oliveira</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Castelo-Branco</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Roobol</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Expert involvement predicts mHealth app downloads: Multivariate regression analysis of urology apps</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2016</year>
          <month>07</month>
          <day>15</day>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>e86</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2016/3/e86/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.5738</pub-id>
          <pub-id pub-id-type="medline">27421338</pub-id>
          <pub-id pub-id-type="pii">v4i3e86</pub-id>
          <pub-id pub-id-type="pmcid">PMC4967182</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dempster</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Risk</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Meddings</surname>
              <given-names>RN</given-names>
            </name>
          </person-group>
          <article-title>Urologists' usage and perceptions of urological apps</article-title>
          <source>J Telemed Telecare</source>
          <year>2014</year>
          <month>12</month>
          <volume>20</volume>
          <issue>8</issue>
          <fpage>450</fpage>
          <lpage>453</lpage>
          <pub-id pub-id-type="doi">10.1177/1357633X14555622</pub-id>
          <pub-id pub-id-type="medline">25316043</pub-id>
          <pub-id pub-id-type="pii">1357633X14555622</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Welk</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>McArthur</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fraser</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hayward</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dixon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>YJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ordon</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The risk of fall and fracture with the initiation of a prostate-selective α antagonist: A population based cohort study</article-title>
          <source>BMJ</source>
          <year>2015</year>
          <month>10</month>
          <day>26</day>
          <volume>351</volume>
          <fpage>h5398</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=26502947"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.h5398</pub-id>
          <pub-id pub-id-type="medline">26502947</pub-id>
          <pub-id pub-id-type="pmcid">PMC4620650</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vasileiou</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Barnett</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thorpe</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Characterising and justifying sample size sufficiency in interview-based studies: Systematic analysis of qualitative health research over a 15-year period</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2018</year>
          <month>11</month>
          <day>21</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>148</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-018-0594-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12874-018-0594-7</pub-id>
          <pub-id pub-id-type="medline">30463515</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12874-018-0594-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6249736</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
