<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id><journal-id journal-id-type="publisher-id">mhealth</journal-id><journal-id journal-id-type="index">13</journal-id><journal-title>JMIR mHealth and uHealth</journal-title><abbrev-journal-title>JMIR Mhealth Uhealth</abbrev-journal-title><issn pub-type="epub">2291-5222</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">v14i1e48828</article-id><article-id pub-id-type="doi">10.2196/48828</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Mobile App Rating Scale for Health Care Professionals to Assess the Quality of mHealth Apps: Questionnaire Development and Psychometric Analysis</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Sharpe</surname><given-names>Albie</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Chan</surname><given-names>Yiong Huak</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Saparamadu</surname><given-names>Amarasinghe Arachchige Don Nalin Samandika</given-names></name><degrees>MBBS, MPH</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib></contrib-group><aff id="aff1"><institution>Discipline of Public Health, School of Human Performance, Rehabilitation and Population Health, University of Technology Sydney</institution><addr-line>Sydney</addr-line><addr-line>NSW</addr-line><country>Australia</country></aff><aff id="aff2"><institution>Biostatistics Unit, Yong Loo Lin School of Medicine, National University of Singapore</institution><addr-line>Kent Ridge</addr-line><addr-line>Singapore</addr-line><country>Singapore</country></aff><aff id="aff3"><institution>Department of International Health, Johns Hopkins Bloomberg School of Public Health, Johns Hopkins University</institution><addr-line>615 N Wolfe St</addr-line><addr-line>Baltimore</addr-line><addr-line>MD</addr-line><country>United States</country></aff><aff id="aff4"><institution>Department of Nutrition and Food Studies, College of Public Health, George Mason University</institution><addr-line>Fairfax</addr-line><addr-line>VA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Buis</surname><given-names>Lorraine</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Watcharaporn</surname><given-names>Fonthip</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Fernando</surname><given-names>Nimasha</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Amarasinghe Arachchige Don Nalin Samandika Saparamadu, MBBS, MPH, Department of International Health, Johns Hopkins Bloomberg School of Public Health, Johns Hopkins University, 615 N Wolfe St, Baltimore, MD, 21205, United States, 1 4109553543, 1 4105029809; <email>samandika@icloud.com</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>31</day><month>7</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e48828</elocation-id><history><date date-type="received"><day>05</day><month>09</month><year>2024</year></date><date date-type="rev-recd"><day>09</day><month>02</month><year>2026</year></date><date date-type="accepted"><day>10</day><month>02</month><year>2026</year></date></history><copyright-statement>&#x00A9; Albie Sharpe, Yiong Huak Chan, Amarasinghe Arachchige Don Nalin Samandika Saparamadu. Originally published in JMIR mHealth and uHealth (<ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org">https://mhealth.jmir.org</ext-link>), 31.7.2026. </copyright-statement><copyright-year>2026</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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org/">https://mhealth.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://mhealth.jmir.org/2026/1/e48828"/><abstract><sec><title>Background</title><p>Many frameworks and tools are available to evaluate the quality of mobile health apps (MHAs), which are increasingly used by health care professionals (HCPs) for accessing medical information, clinical decision support, and communication. However, existing tools are not well equipped to assess the quality of apps designed for HCPs from their perspectives.</p></sec><sec><title>Objective</title><p>We aimed to develop a new tool based on the Mobile App Rating Scale (MARS) to capture the unique perspectives of HCPs on MHAs. We then conducted a psychometric analysis of this new questionnaire to determine its effectiveness in assessing the quality of MHAs designed specifically for HCPs from their perspectives.</p></sec><sec sec-type="methods"><title>Methods</title><p>This study was conducted in 2 phases. In phase 1, the original MARS tool was adapted for HCPs through expert panel review and subsequent qualitative interviews, resulting in the development of the pMARS (MARS for health care professionals) tool. This phase focused on establishing face and content validity. Qualitative interviews were conducted with HCPs from a tertiary hospital in Singapore to gather their perspectives on the tool&#x2019;s structure, clarity, applicability, and usability. In phase 2, we invited HCP participants to complete pMARS based on their experience with the LabMed app, an mHealth tool designed to provide medical laboratory&#x2013;related information to HCPs. We established the construct validity of pMARS through multiple psychometric techniques. Internal consistency reliability was measured using the Cronbach &#x03B1;, while structural equation modeling was used to examine the interrelationships among latent constructs. Additionally, we used item response theory (IRT) to evaluate each item&#x2019;s impact on latent constructs of interest, that is, discriminative performance of individual items within each domain.</p></sec><sec sec-type="results"><title>Results</title><p>Based on the results from phase 1, the pMARS comprised 26 items across 5 domains: engagement, functionality, aesthetics, information, and subjective quality, refined through interviews with 10 HCPs. In phase 2 (n=218), pMARS demonstrated good internal consistency reliability across all domains (Cronbach &#x03B1;=0.855-0.931). Structural equation modeling demonstrated that functionality had the strongest influence on end-user willingness to use, recommend, and purchase the MHA (<italic>P</italic>&#x003C;.001). IRT identified that customization and interactivity of the engagement domain had a weak impact on latent constructs, whereas entertainment had a higher impact. Ease of use and gestural design had a weak impact on the functionality domain, whereas arrangement and size of content and quantity and quality had a strong impact on the aesthetics and information domains, respectively.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>This study reports the development and psychometric analysis of pMARS. Our findings demonstrate strong internal consistency reliability and construct validity, supporting its potential use in health care. Further research should validate pMARS across diverse MHAs and contexts and apply IRT to further refine its precision and efficiency.</p></sec></abstract><kwd-group><kwd>Mobile App Rating Scale for health care professionals</kwd><kwd>MARS for health care professionals</kwd><kwd>pMARS</kwd><kwd>psychometric analysis</kwd><kwd>structural equation modeling</kwd><kwd>item response theory</kwd><kwd>scale development</kwd><kwd>internal consistency reliability</kwd><kwd>eHealth</kwd><kwd>mobile health</kwd><kwd>mHealth</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Mobile health (mHealth) apps (MHAs) offer the potential to deliver accessible, efficient, and cost-effective health care [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. These apps are used not only by patients for health education and self-care but also by health care professionals (HCPs) [<xref ref-type="bibr" rid="ref3">3</xref>]. HCPs rely on MHAs for many purposes, including consultations between HCPs, intersectoral communication, and access to information for HCPs at the point of health care delivery [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. However, the quality of MHAs designed specifically for HCPs can vary significantly in terms of the accuracy of the information provided, functionality, data visualization effectiveness, credibility, and other key factors. Poor-quality or misleading content can pose serious risks to patient health and safety, underscoring the need for reliable quality assessment measures [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Although several frameworks and tools have been developed to evaluate the quality of MHAs, the Mobile Application Rating Scale (MARS) remains one of the most widely used and recognized tools for this purpose [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>].</p><p>MARS is a multidimensional tool designed for experts to assess the quality of MHAs [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. It consists of 23 questions or items, with 19 of these organized into 4 objective dimensions: engagement (5 items), functionality (4 items), aesthetics (3 items), and information (7 items) [<xref ref-type="bibr" rid="ref10">10</xref>]. MARS has been widely applied in the evaluation of apps related to health, well-being, health care, and medicine [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. Researchers have validated MARS across multiple languages, demonstrating that its psychometric properties are consistent with those of the original English version [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref20">20</xref>].</p><p>Given the expertise and training required to administer MARS, a simplified version, known as uMARS (user version of the MARS), has been developed for end users [<xref ref-type="bibr" rid="ref21">21</xref>]. Items requiring expertise and complex terminology have been removed from uMARS. While uMARS has gained wide acceptance for its utility in assessing the quality of various MHAs [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref25">25</xref>] and has been translated into other languages [<xref ref-type="bibr" rid="ref26">26</xref>], it has also faced criticism. Specifically, it has been noted that uMARS may inadequately capture end user perspectives on quality, and some have suggested that it should include emerging mHealth technologies to enhance its comprehensiveness [<xref ref-type="bibr" rid="ref27">27</xref>].</p><p>Despite the widespread use of tools for assessing the quality of MHAs, there have been only a few attempts to evaluate these tools from the perspective of HCPs as end users. This evaluation is crucial for several reasons. First, HCPs are reported to have unique requirements when assessing quality, including access to patient data, data security, and evidence-based clinical content [<xref ref-type="bibr" rid="ref28">28</xref>]. Second, MHAs designed for HCPs must cater to clinical needs and other professional decision-making processes. Unlike MHAs for general users, these apps are also subject to professional and organizational policies that mandate specific security features. Third, HCPs often face demanding schedules, with limited time to thoroughly assess digital tools due to their primary responsibilities in patient care and clinical decision-making [<xref ref-type="bibr" rid="ref29">29</xref>]. Finally, current assessment tools, such as MARS and uMARS, may not fully meet these specific functional requirements or accommodate the time constraints experienced by HCPs. Consequently, developing a new, specifically designed, and simplified questionnaire that can be administered quickly would effectively address these gaps and provide a more relevant evaluation tool for HCPs as end users.</p><p>Moreover, involving HCPs in the development of MHAs is widely recognized as a key factor in creating safe and effective apps [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. A tailored assessment tool would enable MHA developers to address the unique priorities of HCPs. In addition, by capturing the distinct perspectives of HCPs using a dedicated tool, service providers can obtain more accurate and practical insights, ensuring that MHAs are suitable for professional use and health care delivery. Therefore, we aimed to (1) develop a new MHA rating scale tailored for HCPs based on the widely validated MARS framework and (2) conduct a psychometric analysis of this new questionnaire to determine its effectiveness in assessing the quality of MHAs designed specifically for HCPs.</p><p>This paper describes the development of the new rating scale and evaluates its initial application using the LabMed app, an mHealth tool designed to provide medical laboratory&#x2013;related information to HCPs [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. We present our Methods, Results, and Discussion sections in accordance with the &#x201C;recommendations for instrument and scale development and testing&#x201D; [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><p>In this section, we discuss the specific methods and materials used in the study: (1) the process of adapting MARS for use by HCPs with the goal of establishing judgment validity and the qualitative methods used in this process (phase 1) and (2) the assessment of reliability and construct validity of the new tool, pMARS (MARS for health care professionals), through Cronbach &#x03B1; and structural equation modeling (SEM), respectively, followed by the utility of item response theory (IRT) in identifying weakly impacting or performing items (phase 2).</p><sec id="s2-1"><title>Phase 1: Development of the New Rating Scale (pMARS) and Establishment of Judgment Validity</title><sec id="s2-1-1"><title>Overview</title><p>Judgment validity was based on face and content validity [<xref ref-type="bibr" rid="ref35">35</xref>]. Face validity is the degree to which respondents judge the questionnaire items to be valid. Content validity is the extent to which the observed variables in a questionnaire are representative of the theoretical constructs or latent variables (eg, entertainment, interest, customization, and interactivity) and latent constructs (eg, engagement, functionality, and aesthetics). A study outline is shown in <xref ref-type="fig" rid="figure1">Figure 1</xref>.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Study outline. HCP: health care professional; MARS: Mobile App Rating Scale. pMARS: Mobile App Rating Scale for health care professionals.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e48828_fig01.png"/></fig></sec><sec id="s2-1-2"><title>Expert Evaluation</title><p>Judgment validity as a whole was approached using the following steps: establishing an expert committee, identifying dimensionality of constructs, determining the questionnaire and item formats, adding items, determining length, reviewing results, and revising [<xref ref-type="bibr" rid="ref35">35</xref>]. This step was guided by the anticipated clinical, informational, and workflow-related needs of HCPs when evaluating MHAs for professional use.</p></sec><sec id="s2-1-3"><title>Data Collection</title><p>Data collection focused on systematically eliciting expert judgments on the relevance, suitability, clarity, and completeness of MARS items when assessing MHAs intended for HCP use. We assessed content validity with the following criteria: (1) questions were clear and easy to understand, (2) questions covered all the important aspects of each domain, (3) the questionnaire did not omit important questions regarding quality of MHAs, (4) the questionnaire was suitable for replication studies, and (5) there were no violations of privacy. A 3-member panel of multidisciplinary experts comprising a physician, a public health expert, and a human-computer interactions specialist evaluated the relevance and suitability of the original MARS domains and identified items for adaptation to HCP end users.</p></sec><sec id="s2-1-4"><title>Data Analysis</title><p>The aim of this analysis was to identify key domains and constructs from HCP perspectives, eliminate multiconstruct items, ensure appropriate language for HCPs, and review questionnaire length. Feedback was synthesized through iterative review and consensus among the experts to determine item retention, modification, and/or removal. A draft tool with 23 items across 5 conceptually defined domains was developed. Items were not reverse scored. Domains were treated as conceptual groupings rather than independent subscales. Scoring of the tool was carried out by averaging the item scores within domains and across the full pMARS tool.</p></sec><sec id="s2-1-5"><title>Interviews</title><p>To further establish face and content validity from an end-user perspective, qualitative interviews were conducted with HCPs.</p><sec id="s2-1-5-1"><title>Data Collection</title><p>To assess pMARS&#x2019;s ability to capture quality and other key characteristics, we recruited a sample of HCPs (n=10) through both convenience and purposive sampling for face-to-face interviews using a semistructured interview guide provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. A convenience sampling method was used to recruit HCPs who had recent contact with the clinical laboratory. A purposive sampling method was used to ensure that both physicians and nurses were represented in the sample. One researcher (AADNSS) was present for a week at the clinical laboratory to recruit participants.</p><p>Demographic details, excluding personal identifiers, were collected during the interview. Participants first completed version 1 of the pMARS tool, then were interviewed about their experiences and asked for suggestions for improvement. On average, the entire interview process lasted 25 to 30 minutes and was conducted in a private, quiet space within the hospital.</p></sec></sec></sec><sec id="s2-2"><title>Interview Analysis</title><p>Audio recordings from the interviews were transcribed verbatim and handwritten notes were compiled without participant identifiers. Anonymized transcripts were analyzed using a deductive coding process [<xref ref-type="bibr" rid="ref36">36</xref>]. One researcher (AS) conducted the initial coding, categorizing participant feedback based on the role pMARS played in assessing the app. Preliminary codes and emerging themes were discussed by the researcher and a collaborator until consensus was reached. The final coding scheme was subsequently reviewed and validated by a second researcher (AADNSS). Findings from this phase were used to refine item wording and enhance the content validity of the pMARS tool.</p></sec><sec id="s2-3"><title>Phase 2: Evaluation of Reliability and Construct Validity of pMARS</title><sec id="s2-3-1"><title>Overview</title><p>To evaluate the pMARS questionnaire, a cross-sectional analysis was conducted with the users of the LabMed app between March and August 2019 at a tertiary care general hospital in Singapore.</p></sec><sec id="s2-3-2"><title>Data Collection</title><p>The physicians, residents, nurse clinicians, and registered nurses in the hospital who used the clinical laboratory services and had experience using the LabMed app were eligible to take part in the study.</p><p>We used a simple sequential sampling approach to recruit participants. The questionnaire was administered using 2 parallel approaches. First, a researcher (AADNSS) systematically visited all hospital wards in person and distributed printed questionnaires, which were collected periodically during the data collection period. Second, the questionnaire was made available through the hospital intranet via the REDCap (Research Electronic Data Capture [<xref ref-type="bibr" rid="ref37">37</xref>]) electronic data capture platform. The HCPs were informed of the online option through a single mass email campaign conducted by the hospital&#x2019;s marketing department. Response was voluntary.</p><p>REDCap is a secure, web-based software platform designed to support data capture for research studies. We aimed for a participant-to-questionnaire-item ratio of 8:1 to 10:1, resulting in an estimated sample size of 184 to 230 [<xref ref-type="bibr" rid="ref35">35</xref>].</p></sec><sec id="s2-3-3"><title>Data Analysis</title><p>All forms of questionnaires were transcribed into a Microsoft Excel file by 2 researchers working together to minimize transcription errors. STATA (version 17.0; StataCorp) was used for analysis [<xref ref-type="bibr" rid="ref38">38</xref>]. The Cronbach &#x03B1; was used to show the internal consistency reliability of pMARS: 0.80 to 0.89 was considered good, and &#x003E;0.90 was considered excellent [<xref ref-type="bibr" rid="ref39">39</xref>]. A high &#x03B1; may indicate redundancy; however, it is not the sole determinant of item appropriateness [<xref ref-type="bibr" rid="ref40">40</xref>]. Face and content validity, along with factor structure, were essential in determining the questionnaire&#x2019;s ability to accurately measure the intended construct.</p><p>SEM was used to evaluate the interrelationships between the latent constructs after adjusting for age, sex, and HCPs&#x2019; role in the hospital [<xref ref-type="bibr" rid="ref1">1</xref>]. SEM assumed a latent construct for the observed items of each subscale, and a higher order factor&#x2014;subjective quality&#x2014;accounted for correlations between the factors (<xref ref-type="fig" rid="figure2">Figure 2</xref>).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>The model used in structural equation modeling.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e48828_fig02.png"/></fig><p>Lastly, we used IRT to identify each question&#x2019;s impact on the latent constructs, that is, engagement, functionality, information, aesthetics, and subjective quality. Unlike classical test theory, which assumes all items contribute equally to the overall score, IRT allows for identifying items with varying discrimination, making it ideal for optimizing and shortening measurement tools without compromising validity and reliability. The primary purpose of using IRT was to refine the questionnaire, resulting in a precise, valid, and relatively brief pMARS that minimized the completion time and response burden [<xref ref-type="bibr" rid="ref41">41</xref>].</p></sec></sec><sec id="s2-4"><title>Ethical Considerations</title><p>This research project received an ethics review exemption from the Projects Committee of the Department of Laboratory Medicine at Ng Teng Fong General Hospital, Singapore. The exemption was granted in accordance with the department&#x2019;s policy for minimal-risk research involving health care staff and was reviewed and approved by the head of the department. All participants were provided with an information sheet describing the study objectives, the voluntary nature of participation, and the commitment to data confidentiality. Informed consent was obtained before participation in each study phase. Participants who completed the qualitative interviews (phase 1) or paper-based questionnaires (phase 2) provided written consent, while those who completed the online survey via REDCap on the hospital intranet platform provided electronic consent.</p><p>Basic demographic data, including age, biological sex, and professional role, were collected. No personally identifiable data were collected. All files were stored on password-protected institutional drives accessible only to study investigators. In phase 2, participants were offered a Singapore $10 (S$1=US $0.78 as of June 17, 2026) voucher for a local coffee chain as compensation for their time spent completing the questionnaire. No other payments or incentives were provided.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><p>Phase 1, the qualitative study, included 10 participants. Phase 2 included 218 participants who responded and returned completed questionnaires. Selected sociodemographic characteristics of the participants are presented in <xref ref-type="table" rid="table1">Table 1</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Demographic characteristics of the participants in phase 1 and phase 2.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Values</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Phase 1</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age (years), mean (SD)</td><td align="left" valign="top">28.4 (8.81)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Sex, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Male</td><td align="left" valign="top">3 (30)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Female</td><td align="left" valign="top">7 (70)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Role in hospital, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Nurse</td><td align="left" valign="top">8 (80)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Doctor</td><td align="left" valign="top">2 (20)</td></tr><tr><td align="left" valign="top" colspan="2">Phase 2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age (years), mean (SD)</td><td align="left" valign="top">30.4 (7.2)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Sex, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Male</td><td align="left" valign="top">39 (17.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Female</td><td align="left" valign="top">176 (80.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Missing data</td><td align="left" valign="top">3 (0)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Role in hospital, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Nurse</td><td align="left" valign="top">154 (70.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Doctor</td><td align="left" valign="top">47 (21.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Missing data</td><td align="left" valign="top">17 (7.8)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Specialty, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Surgical specialties</td><td align="left" valign="top">26 (11.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Medical specialties (inpatient or acute care)</td><td align="left" valign="top">91 (41.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Community hospital</td><td align="left" valign="top">9 (4.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unspecified</td><td align="left" valign="top">92 (42.2)</td></tr></tbody></table></table-wrap><sec id="s3-1"><title>Phase 1: Development of pMARS and Assessment of Its Judgment Validity</title><p>The first version of the questionnaire consisted of a demographic data section and 5 domains. Certain question stems were reworded and/or split into 2 separate stems to ensure that there were no double-barreled questions, for example, item 1 of section A of MARS reads, &#x201C;Is the app fun/entertaining to use? Does it use any strategies to increase engagement through entertainment?&#x201D; This was broken into two separate question stems: (1) &#x201C;Is the app fun/entertaining to use?&#x201D; and (2) &#x201C;Does the app use strategies to increase engagement through entertainment (e.g., strategies such as interactivity/gamification)?&#x201D; This version of the questionnaire consisted of question stems presented in question form and shortened but descriptive answer stems presented as a Likert scale. Moreover, almost all the question stems had examples or descriptive statements to further elaborate or clarify the ideas.</p><p>Insights from the qualitative assessment, categorized into 4 key areas, guided the multidisciplinary panel in developing the second version of pMARS at the end of phase 1 (<xref ref-type="table" rid="table2">Table 2</xref>).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Quotes from the qualitative interview participants (n=10) in relation to specific functionalities of the Mobile App Rating Scale for health care professionals.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Function</td><td align="left" valign="top">Quotes from participants</td><td align="left" valign="top">Action taken</td></tr></thead><tbody><tr><td align="left" valign="top">Structure</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Some questions are truncated in the paper.&#x201D;</p></list-item><list-item><p>&#x201C;Takes a long time to read.&#x201D;</p></list-item><list-item><p>&#x201C;Print all the stems on the same page.&#x201D;</p></list-item><list-item><p>&#x201C;Shorten the questionnaire by reducing the length of the items.&#x201D;</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Shorten the questionnaire by reducing the length of the items.</p></list-item><list-item><p>Limit examples and descriptive statements in question stems.</p></list-item><list-item><p>Switch to landscape format to reduce the length of the survey to three pages.</p></list-item></list></td></tr><tr><td align="left" valign="top">Clarity</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;RCT, what does it mean? Only the abbreviation is given.&#x201D;</p></list-item><list-item><p>&#x201C;Should have presented the answer stems in tables or using numbers instead of bullet points.&#x201D;</p></list-item><list-item><p>&#x201C;I think only the options are quite long.&#x201D;</p></list-item><list-item><p>&#x201C;Not sure or uncertain is the answer that I was looking for.&#x201D;</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Simplify the language and minimize jargon.</p></list-item><list-item><p>Revise question stems to statements to reduce length and increase clarity.</p></list-item></list></td></tr><tr><td align="left" valign="top">Applicability</td><td align="left" valign="bottom"><list list-type="bullet"><list-item><p>&#x201C;The questionnaire is different to the context of this app.&#x201D;</p></list-item><list-item><p>&#x201C;We usually use it when we need it, but the question is about entertainment. Not relevant.&#x201D;</p></list-item><list-item><p>&#x201C;It is not about entertainment, it&#x2019;s whether I want it or not.&#x201D;</p></list-item><list-item><p>&#x201C;Credibility is granted by hospital. Should not doubt it.&#x201D;</p></list-item><list-item><p>&#x201C;App store description is not usually read by anyone. Therefore it is probably not important to assess.&#x201D;</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Reword item stems to better highlight app functionality and relevance.</p></list-item><list-item><p>Reduce descriptive statements to minimize assumptions about app use.</p></list-item><list-item><p>Remove irrelevant items such as app store description.</p></list-item><list-item><p>Reduce items on entertainment and gamification.</p></list-item></list></td></tr><tr><td align="left" valign="top">Usability</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Likert scale should be reversed, as in 5 should be extremely satisfied.&#x201D;</p></list-item><list-item><p>&#x201C;Should have presented the answer stems in tables or using numbers instead of bullet points.&#x201D;</p></list-item><list-item><p>&#x201C;Introduce an additional option for those who do not know the answer.&#x201D;</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Change the answer stems to a simple 5-point Likert scale.</p></list-item><list-item><p>Add a new answer stem for &#x201C;don&#x2019;t know.&#x201D;</p></list-item><list-item><p>Simplify design and remove Likert descriptors.</p></list-item></list></td></tr></tbody></table></table-wrap><p>Findings from the qualitative assessment of the questionnaire (ie, interviews with HCPs) shed light on several areas of the questionnaire for focused improvement: (1) shorten the questionnaire by reducing the length of the answers, (2) further simplify the language and minimize jargon, and (3) introduce an additional option for those who do not know the answer to a specific question. It is noteworthy that no new items were proposed by the HCPs. Based on the findings, we changed the question stems from question forms to statements, for example, (1) &#x201C;arrangement and size of buttons, icons, and menus on the screen is appropriate&#x201D; and (2) &#x201C;it uses strategies to increase engagement through entertainment (e.g., strategies such as interactivity/gamification).&#x201D; Moreover, we limited examples and/or descriptive statements in question stems to a minimum. Simultaneously, we changed the answer stems to a simple 5-point Likert scale without embedded descriptive statements: strongly agree, agree, neutral, disagree, and strongly disagree. Finally, we added a new answer stem: &#x201C;don&#x2019;t know.&#x201D;</p><p>In addition, we redesigned the questionnaire by changing its orientation from portrait to landscape. The reasons for this change were to limit the length of the questionnaire to 3 pages despite including additional questions and to provide an easy-to-complete format. The final version of the questionnaire at the end of phase 1 consisted of 26 questions spread across 5 domains: engagement (6 items), functionality (5 items), aesthetics (4 items), information (7 items), and subjective quality (4 items). The length of the questionnaire was deemed appropriate by the committee (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p></sec><sec id="s3-2"><title>Phase 2: Reliability and Construct Validity of pMARS</title><p>We distributed 197 printed questionnaires among HCPs in person, and 189 participated, resulting in a 95.9% response rate. Additionally, 29 HCPs accessed the survey through the hospital intranet, bringing the total number of responses to 218. A further 15 REDCap surveys were incomplete, resulting in a REDCap complete response rate of 65.9%. We were unable to calculate an overall response rate for REDCap as we could not track the reach through the hospital intranet. Among the in-person and intranet-administered questionnaires returned, the proportion of nonresponses per question item ranged from 0% to 13.3%, with the item &#x201C;Would you pay for this app?&#x201D; showing the highest nonresponse rate (n=29). Most items (29/30; 96.7%) had less than 5.1% missing responses. Detailed item-level missing data, including counts of &#x201C;don&#x2019;t know&#x201D; responses, are provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p><p>The Cronbach &#x03B1; (ranging from 0.855 to 0.931) showed that the internal consistency reliability of pMARS was good to excellent for all the domains (<xref ref-type="table" rid="table3">Table 3</xref>). SEM analysis demonstrated that functionality (<italic>P</italic>&#x003C;.001) had the strongest influence on end-user willingness to use or recommend and purchase the MHA, after adjusting for age, sex, and the HCPs&#x2019; role in the hospital (<xref ref-type="fig" rid="figure3">Figure 3</xref>).</p><p>For domains with Cronbach &#x03B1; values &#x003E;0.90, we conducted a manual item review to assess potential redundancy. We examined item wording and conceptual distinctness within each domain. The review confirmed that, although some items were related, they measured complementary aspects of the construct and contributed meaningfully to the overall scale. All such items were therefore retained in the current version of pMARS.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Cronbach &#x03B1; results for the Mobile App Rating Scale for health care professionals.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain and item</td><td align="left" valign="bottom">Scale mean if item deleted</td><td align="left" valign="bottom">Scale variance if item deleted</td><td align="left" valign="bottom">Corrected item&#x2013;total correlation</td><td align="left" valign="bottom">Cronbach &#x03B1; if item deleted</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="5">Engagement: Cronbach &#x03B1;=0.855, number of items=6</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 1</td><td align="left" valign="top">17.936</td><td align="left" valign="top">8.080</td><td align="left" valign="top">0.671</td><td align="left" valign="top">0.825</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 2</td><td align="left" valign="top">18.005</td><td align="left" valign="top">8.163</td><td align="left" valign="top">0.554</td><td align="left" valign="top">0.849</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 3</td><td align="left" valign="top">17.675</td><td align="left" valign="top">7.597</td><td align="left" valign="top">0.721</td><td align="left" valign="top">0.815</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 4</td><td align="left" valign="top">17.700</td><td align="left" valign="top">8.152</td><td align="left" valign="top">0.698</td><td align="left" valign="top">0.821</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 5</td><td align="left" valign="top">17.778</td><td align="left" valign="top">8.292</td><td align="left" valign="top">0.597</td><td align="left" valign="top">0.839</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 6</td><td align="left" valign="top">17.409</td><td align="left" valign="top">8.382</td><td align="left" valign="top">0.626</td><td align="left" valign="top">0.833</td></tr><tr><td align="left" valign="top" colspan="5">Functionality: Cronbach &#x03B1;=0.931, number of items=5</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 7</td><td align="left" valign="top">15.212</td><td align="left" valign="top">6.296</td><td align="left" valign="top">0.785</td><td align="left" valign="top">0.922</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 8</td><td align="left" valign="top">15.212</td><td align="left" valign="top">6.059</td><td align="left" valign="top">0.864</td><td align="left" valign="top">0.906</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 9</td><td align="left" valign="top">15.232</td><td align="left" valign="top">6.535</td><td align="left" valign="top">0.784</td><td align="left" valign="top">0.921</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 10</td><td align="left" valign="top">15.227</td><td align="left" valign="top">6.493</td><td align="left" valign="top">0.847</td><td align="left" valign="top">0.910</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 11</td><td align="left" valign="top">15.217</td><td align="left" valign="top">6.636</td><td align="left" valign="top">0.816</td><td align="left" valign="top">0.916</td></tr><tr><td align="left" valign="top" colspan="5">aesthetics: Cronbach &#x03B1;=0.928, number of items=4</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 12</td><td align="left" valign="top">11.296</td><td align="left" valign="top">3.576</td><td align="left" valign="top">0.813</td><td align="left" valign="top">0.912</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 13</td><td align="left" valign="top">11.379</td><td align="left" valign="top">3.415</td><td align="left" valign="top">0.835</td><td align="left" valign="top">0.905</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 14</td><td align="left" valign="top">11.271</td><td align="left" valign="top">3.406</td><td align="left" valign="top">0.892</td><td align="left" valign="top">0.886</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 15</td><td align="left" valign="top">11.232</td><td align="left" valign="top">3.694</td><td align="left" valign="top">0.789</td><td align="left" valign="top">0.920</td></tr><tr><td align="left" valign="top" colspan="5">Information: Cronbach &#x03B1;=0.905, number of items=7</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 16</td><td align="left" valign="top">22.688</td><td align="left" valign="top">12.056</td><td align="left" valign="top">0.740</td><td align="left" valign="top">0.889</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 17</td><td align="left" valign="top">22.752</td><td align="left" valign="top">12.048</td><td align="left" valign="top">0.663</td><td align="left" valign="top">0.897</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 18</td><td align="left" valign="top">22.673</td><td align="left" valign="top">11.594</td><td align="left" valign="top">0.825</td><td align="left" valign="top">0.879</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 19</td><td align="left" valign="top">22.713</td><td align="left" valign="top">11.569</td><td align="left" valign="top">0.811</td><td align="left" valign="top">0.881</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 20</td><td align="left" valign="top">22.757</td><td align="left" valign="top">11.568</td><td align="left" valign="top">0.720</td><td align="left" valign="top">0.891</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 21</td><td align="left" valign="top">22.748</td><td align="left" valign="top">11.672</td><td align="left" valign="top">0.783</td><td align="left" valign="top">0.884</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 22</td><td align="left" valign="top">22.965</td><td align="left" valign="top">12.302</td><td align="left" valign="top">0.523</td><td align="left" valign="top">0.915</td></tr></tbody></table></table-wrap><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Results of the structural equation modeling.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e48828_fig03.png"/></fig><p>IRT (<xref ref-type="table" rid="table4">Table 4</xref>) identified that for the engagement domain, items 4 (customization) and 5 (interactivity) had a weak impact on latent constructs, whereas items 1 and 2 (both entertainment) had a higher impact on the domain. Similarly, items 9 (ease of use) and 11 (gestural design) had a weak impact on functionality, item 13 (arrangement and size of content) had a strong impact on aesthetics, and items 18 (quantity) and 19 (quality) had a strong impact on information. The engagement domain demonstrated the lowest reliability, and IRT highlighted weakly impacting items within the domain, enabling the researchers to shorten the questionnaire if required.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Results of the item response theory analysis.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain and item</td><td align="left" valign="bottom">Impact<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Engagement</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 1</td><td align="left" valign="top">12.8</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 2</td><td align="left" valign="top">5.4</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 3</td><td align="left" valign="top">5.5</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 4</td><td align="left" valign="top">2.9</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 5</td><td align="left" valign="top">2.4</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 6</td><td align="left" valign="top">5.3</td></tr><tr><td align="left" valign="top" colspan="2">Functionality</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 7</td><td align="char" char="." valign="top">11.0</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 8</td><td align="char" char="." valign="top">41.6</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 9</td><td align="char" char="." valign="top">4.1</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 10</td><td align="char" char="." valign="top">10.8</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 11</td><td align="char" char="." valign="top">4.9</td></tr><tr><td align="left" valign="top" colspan="2">Aesthetics</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 12</td><td align="char" char="." valign="top">12.3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 13</td><td align="char" char="." valign="top">63.0</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 14</td><td align="char" char="." valign="top">16.6</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 15</td><td align="char" char="." valign="top">10.7</td></tr><tr><td align="left" valign="top" colspan="2">Information</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 16</td><td align="char" char="." valign="top">3.3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 17</td><td align="char" char="." valign="top">3.0</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 18</td><td align="char" char="." valign="top">6.8</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 19</td><td align="char" char="." valign="top">8.6</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 20</td><td align="char" char="." valign="top">3.2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 21</td><td align="char" char="." valign="top">4.1</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Item 22</td><td align="char" char="." valign="top">4.2</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>Overall: engagement=4.0, functionality=11.3, aesthetics=24.5, and information=4.0.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>Our study shows that the newly developed pMARS tool has strong internal consistency reliability (Cronbach ɑ) across all domains, indicating its potential utility in assessing the quality of MHAs designed for HCPs from their perspective. Although most items performed well, item 22 of the information domain (&#x201C;the app has been trialled/tested; verified by evidence&#x201D;) demonstrated weak correlations (<xref ref-type="table" rid="table2">Table 3</xref>). The item was retained in the final version of pMARS as it reflects a critical aspect of evidence-based practice in clinical settings and warrants further examination in future validation studies. Furthermore, SEM generated valuable insights into interrelationships between the latent constructs. Not all items were equally good indicators for the dimensions. The strongest influence was observed between subjective quality and functionality. Similarly, items 1 to 3 of the engagement domain, items 16 to 22 of the information domain, and items 23 and 26 of the subjective quality domain demonstrated relatively strong influence.</p><p>On the other hand, IRT revealed weakly impacting items such as items 4 and 5 of the engagement domain; items 9 and 11 of the functionality domain; and items 16, 17, and 20 of the information domain. These items provide an opportunity to further shorten the questionnaire. However, it should be evaluated within the theoretical factor model of the scale, and therefore, this is an area for future research. Overall, our findings suggest that pMARS is an MHA quality assessment tool of good metric quality considering the reliability and construct validity results.</p></sec><sec id="s4-2"><title>Clinical Utility and Developmental Limitations</title><p>In the busy health care settings of Singapore, engaging HCPs in discussions unrelated to direct patient care can be challenging. With its brevity and standardized format, pMARS enables rapid assessment of MHA quality from the perspective of HCPs as clinical end users. Unlike MARS, which was designed for expert evaluators to classify and assess general MHA quality, and uMARS, which targets general end users, pMARS fills a critical gap by capturing HCP-specific clinical usability and professional decision-making considerations that are not specifically addressed by existing tools [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. The use of simplified language in pMARS ensures accessibility for HCPs without requiring specific training, including those who may be unfamiliar with MHA-related terminology. Consequently, pMARS provides a practical, contextually relevant, and adaptable tool for service providers and HCPs to evaluate the quality of MHAs within real-world clinical settings. Notably, pMARS is designed as a flexible framework that can be iteratively refined to incorporate emerging clinical-, workflow-, and patient safety&#x2013;related quality considerations as digital health technologies evolve.</p><p>The direct use of MARS in developing pMARS, as described by Baptista et al [<xref ref-type="bibr" rid="ref27">27</xref>], may eliminate certain aspects of MHAs that are important to end users. To overcome this limitation, we introduced a qualitative approach using interviews with HCPs; however, the inputs generated by this procedure were limited to a few aspects of the questionnaire, as discussed in the Results section. The qualitative component introduced changes to question stems by rewording, shortening, and simplifying them without adding or removing any items from the questionnaire. According to our observations during the interviews, the interview answers were brief and the discussions were limited, possibly as a result of time pressures.</p></sec><sec id="s4-3"><title>Regulatory Challenges</title><p>Legislative frameworks such as the Health Insurance Portability and Accountability Act (HIPAA) in the United States and the Personal Data Protection Act (PDPA) in Singapore address crucial concerns for HCPs regarding MHAs, including data privacy, security, and patient confidentiality [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. These regulations set important standards for protecting patient information and ensuring the reliability of MHAs. However, the adoption of such regulations varies globally, with many countries still developing or implementing their standards. As regulatory frameworks continue to evolve, the availability of a robust tool to evaluate the quality of MHAs from the perspective of HCPs remains essential to ensure these apps meet the necessary standards. Furthermore, health care organizations can use pMARS to evaluate and select suitable MHAs that comply with professional standards.</p></sec><sec id="s4-4"><title>Considerations for the Future</title><p>As mHealth technology continues to evolve, several areas for potential improvement in future versions of the pMARS tool have emerged. First, interoperability between MHAs, health systems, and electronic health records is crucial for HCPs and health care organizations when integrating these technologies [<xref ref-type="bibr" rid="ref44">44</xref>]. Second, evaluating the effectiveness and security of communications among HCPs, including end-to-end encryption, is important for ensuring coordinated care and protecting sensitive information [<xref ref-type="bibr" rid="ref45">45</xref>]. Third, understanding potential patient safety concerns associated with MHAs is vital for maintaining high standards of care. Lastly, language barriers among HCPs should be addressed to enhance the app&#x2019;s quality, ethical considerations, and utility. Future versions of pMARS should take these evolving quality requirements into account. Additionally, with the growing integration of AI and large language models into mHealth apps, future versions of pMARS should also account for quality requirements specific to AI and AI-generated content [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>].</p></sec><sec id="s4-5"><title>Limitations</title><p>Our study has several methodological and participant-related limitations. There were 2 methodological limitations. First, the psychometric evaluation of pMARS was based on data from only 1 MHA. This focus may affect certain aspects of statistical analysis, particularly if the MHA had quality deficiencies in specific domains. To address this limitation, future validation studies should involve a broader range of MHAs across different medical fields. Second, the IRT depends on the accuracy of the underlying model. The utility of the IRT is contingent upon how well the model reflects the data, making further validation studies essential to evaluate the appropriateness of pMARS items.</p><p>Participant-related limitations include the potential influence of the questionnaire&#x2019;s ease of administration on construct validity. The simplicity and repetitive nature of the pMARS may lead to patterned responses, highlighting the need for negatively worded questions in future studies to counteract response biases. Second, the expert panel in phase 1, comprising a physician, public health expert, and human-computer interactions specialist, did not fully represent the demographics of the study participants or potential users, potentially limiting the generalizability of the pMARS tool. Further studies are necessary to assess and validate the pMARS tool across multiple MHAs. Finally, the disproportionate number of female participants should be noted as a limitation, as it may reduce the generalizability of findings to male HCPs. However, to some degree, this distribution reflects the gender composition of the hospital workforce rather than sampling bias.</p></sec><sec id="s4-6"><title>Conclusions</title><p>To our knowledge, this study is the first to develop a tool to evaluate MHAs designed for HCPs from their perspective. Additionally, it is the first study to apply IRT to assess and identify the impact of each question on the latent constructs within MARS and its derivatives. Our findings demonstrate that pMARS is a robust and metrically sound tool for evaluating MHAs intended for HCPs. It has the potential to enable HCPs to assess and recommend high-quality MHAs. We recommend that future research on pMARS incorporate IRT to refine the questionnaire by identifying and removing less-effective items, thereby enhancing its utility and precision in assessing MHA quality.</p></sec></sec></body><back><ack><p>The authors are grateful to all the staff who contributed to the project by taking part in the interviews and completing questionnaires despite their busy schedules in the hospital. This study would not have been possible without their tremendous support. We also thank Dr Leslie Lam, Ms Zeng Peizi, and Mr Andrew Goh for facilitating this study within the Department of Laboratory Medicine of Ng Teng Fong General Hospital.</p></ack><notes><sec><title>Funding</title><p>This study was supported by the JurongHealth Internal Research &#x0026; Development Grant Awards for fiscal years 2016 and 2017 (project code 16-55).</p></sec></notes><fn-group><fn fn-type="con"><p>AADNSS conceptualized and designed the study, co-designed the quantitative and qualitative methodologies, acquired the data, contributed to quantitative data analysis and interpretation of findings, drafted and critically revised the manuscript, and approved the final version for publication. YHC co-designed the quantitative methodology, performed the statistical analysis, critically reviewed the manuscript, and approved the final version for publication. AS co-designed the qualitative methodology, conducted the qualitative data analysis, critically reviewed the manuscript, and approved the final version for publication.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">HCP</term><def><p>health care professional</p></def></def-item><def-item><term id="abb2">HIPAA</term><def><p>Health Insurance Portability and Accountability Act</p></def></def-item><def-item><term id="abb3">IRT</term><def><p>item response theory</p></def></def-item><def-item><term id="abb4">MARS</term><def><p>Mobile App Rating Scale</p></def></def-item><def-item><term id="abb5">MHA</term><def><p>mobile health app</p></def></def-item><def-item><term id="abb6">mHealth</term><def><p>mobile health</p></def></def-item><def-item><term id="abb7">PDPA</term><def><p>Personal Data Protection Act</p></def></def-item><def-item><term id="abb8">pMARS</term><def><p>Mobile App Rating Scale for health care professionals</p></def></def-item><def-item><term id="abb9">SEM</term><def><p>structural equation modeling</p></def></def-item><def-item><term id="abb10">uMARS</term><def><p>user version of the Mobile App Rating Scale</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Terhorst</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Philippi</surname><given-names>P</given-names> </name><name name-style="western"><surname>Sander</surname><given-names>LB</given-names> </name><etal/></person-group><article-title>Validation of the Mobile Application Rating Scale (MARS)</article-title><source>PLoS One</source><year>2020</year><volume>15</volume><issue>11</issue><fpage>e0241480</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0241480</pub-id><pub-id pub-id-type="medline">33137123</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Donker</surname><given-names>T</given-names> </name><name name-style="western"><surname>Petrie</surname><given-names>K</given-names> </name><name name-style="western"><surname>Proudfoot</surname><given-names>J</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>J</given-names> </name><name name-style="western"><surname>Birch</surname><given-names>MR</given-names> </name><name name-style="western"><surname>Christensen</surname><given-names>H</given-names> </name></person-group><article-title>Smartphones for smarter delivery of mental health programs: a systematic review</article-title><source>J Med Internet Res</source><year>2013</year><month>11</month><day>15</day><volume>15</volume><issue>11</issue><fpage>e247</fpage><pub-id pub-id-type="doi">10.2196/jmir.2791</pub-id><pub-id pub-id-type="medline">24240579</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wattanapisit</surname><given-names>A</given-names> </name><name name-style="western"><surname>Teo</surname><given-names>CH</given-names> </name><name name-style="western"><surname>Wattanapisit</surname><given-names>S</given-names> </name><name name-style="western"><surname>Teoh</surname><given-names>E</given-names> </name><name name-style="western"><surname>Woo</surname><given-names>WJ</given-names> </name><name name-style="western"><surname>Ng</surname><given-names>CJ</given-names> </name></person-group><article-title>Can mobile health apps replace GPs? A scoping review of comparisons between mobile apps and GP tasks</article-title><source>BMC Med Inform Decis Mak</source><year>2020</year><month>01</month><day>6</day><volume>20</volume><issue>1</issue><fpage>5</fpage><pub-id pub-id-type="doi">10.1186/s12911-019-1016-4</pub-id><pub-id pub-id-type="medline">31906985</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="report"><article-title>mHealth: New Horizons for Health Through Mobile Technologies</article-title><year>2011</year><access-date>2026-06-18</access-date><publisher-name>World Health Organization</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.afro.who.int/publications/mhealth-new-horizons-health-through-mobile-technologie">https://www.afro.who.int/publications/mhealth-new-horizons-health-through-mobile-technologie</ext-link></comment></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>Lewis</surname><given-names>TL</given-names> </name><name name-style="western"><surname>Wyatt</surname><given-names>JC</given-names> </name></person-group><article-title>mHealth and mobile medical apps: a framework to assess risk and promote safer use</article-title><source>J Med Internet Res</source><year>2014</year><month>09</month><day>15</day><volume>16</volume><issue>9</issue><fpage>e210</fpage><pub-id pub-id-type="doi">10.2196/jmir.3133</pub-id><pub-id pub-id-type="medline">25223398</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>Schoenfeld</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Sehgal</surname><given-names>NJ</given-names> </name><name name-style="western"><surname>Auerbach</surname><given-names>A</given-names> </name></person-group><article-title>The challenges of mobile health regulation</article-title><source>JAMA Intern Med</source><year>2016</year><month>05</month><day>1</day><volume>176</volume><issue>5</issue><fpage>704</fpage><lpage>705</lpage><pub-id pub-id-type="doi">10.1001/jamainternmed.2016.0326</pub-id><pub-id pub-id-type="medline">26999551</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>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>1</day><volume>27</volume><issue>2</issue><fpage>330</fpage><lpage>340</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocz175</pub-id><pub-id pub-id-type="medline">31599936</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>Boudreaux</surname><given-names>ED</given-names> </name><name name-style="western"><surname>Waring</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Hayes</surname><given-names>RB</given-names> </name><name name-style="western"><surname>Sadasivam</surname><given-names>RS</given-names> </name><name name-style="western"><surname>Mullen</surname><given-names>S</given-names> </name><name name-style="western"><surname>Pagoto</surname><given-names>S</given-names> </name></person-group><article-title>Evaluating and selecting mobile health apps: strategies for healthcare providers and healthcare organizations</article-title><source>Transl Behav Med</source><year>2014</year><month>12</month><volume>4</volume><issue>4</issue><fpage>363</fpage><lpage>371</lpage><pub-id pub-id-type="doi">10.1007/s13142-014-0293-9</pub-id><pub-id pub-id-type="medline">25584085</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>Baumel</surname><given-names>A</given-names> </name><name name-style="western"><surname>Faber</surname><given-names>K</given-names> </name><name name-style="western"><surname>Mathur</surname><given-names>N</given-names> </name><name name-style="western"><surname>Kane</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Muench</surname><given-names>F</given-names> </name></person-group><article-title>Enlight: a comprehensive quality and therapeutic potential evaluation tool for mobile and web-based eHealth interventions</article-title><source>J Med Internet Res</source><year>2017</year><month>03</month><day>21</day><volume>19</volume><issue>3</issue><fpage>e82</fpage><pub-id pub-id-type="doi">10.2196/jmir.7270</pub-id><pub-id pub-id-type="medline">28325712</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>Stoyanov</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Hides</surname><given-names>L</given-names> </name><name name-style="western"><surname>Kavanagh</surname><given-names>DJ</given-names> </name><name name-style="western"><surname>Zelenko</surname><given-names>O</given-names> </name><name name-style="western"><surname>Tjondronegoro</surname><given-names>D</given-names> </name><name name-style="western"><surname>Mani</surname><given-names>M</given-names> </name></person-group><article-title>Mobile App Rating Scale: a new tool for assessing the quality of health mobile apps</article-title><source>JMIR Mhealth Uhealth</source><year>2015</year><month>03</month><day>11</day><volume>3</volume><issue>1</issue><fpage>e27</fpage><pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id><pub-id pub-id-type="medline">25760773</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>Bardus</surname><given-names>M</given-names> </name><name name-style="western"><surname>Awada</surname><given-names>N</given-names> </name><name name-style="western"><surname>Ghandour</surname><given-names>LA</given-names> </name><etal/></person-group><article-title>The Arabic version of the Mobile App Rating Scale: development and validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>03</month><day>3</day><volume>8</volume><issue>3</issue><fpage>e16956</fpage><pub-id pub-id-type="doi">10.2196/16956</pub-id><pub-id pub-id-type="medline">32130183</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>Knitza</surname><given-names>J</given-names> </name><name name-style="western"><surname>Tascilar</surname><given-names>K</given-names> </name><name name-style="western"><surname>Messner</surname><given-names>EM</given-names> </name><etal/></person-group><article-title>German mobile apps in rheumatology: review and analysis using the Mobile Application Rating Scale (MARS)</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>08</month><day>5</day><volume>7</volume><issue>8</issue><fpage>e14991</fpage><pub-id pub-id-type="doi">10.2196/14991</pub-id><pub-id pub-id-type="medline">31381501</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>Jannati</surname><given-names>N</given-names> </name><name name-style="western"><surname>Salehinejad</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kuenzig</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Pe&#x00F1;a-S&#x00E1;nchez</surname><given-names>JN</given-names> </name></person-group><article-title>Review and content analysis of mobile apps for inflammatory bowel disease management using the Mobile Application Rating Scale (MARS): systematic search in app stores</article-title><source>Int J Med Inform</source><year>2023</year><month>12</month><volume>180</volume><fpage>105249</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2023.105249</pub-id><pub-id pub-id-type="medline">37857167</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Masterson Creber</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Maurer</surname><given-names>MS</given-names> </name><name name-style="western"><surname>Reading</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hiraldo</surname><given-names>G</given-names> </name><name name-style="western"><surname>Hickey</surname><given-names>KT</given-names> </name><name name-style="western"><surname>Iribarren</surname><given-names>S</given-names> </name></person-group><article-title>Review and analysis of existing mobile phone apps to support heart failure symptom monitoring and self-care management using the Mobile Application Rating Scale (MARS)</article-title><source>JMIR Mhealth Uhealth</source><year>2016</year><month>06</month><day>14</day><volume>4</volume><issue>2</issue><fpage>e74</fpage><pub-id pub-id-type="doi">10.2196/mhealth.5882</pub-id><pub-id pub-id-type="medline">27302310</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bardus</surname><given-names>M</given-names> </name><name name-style="western"><surname>van Beurden</surname><given-names>SB</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Abraham</surname><given-names>C</given-names> </name></person-group><article-title>A review and content analysis of engagement, functionality, aesthetics, information quality, and change techniques in the most popular commercial apps for weight management</article-title><source>Int J Behav Nutr Phys Act</source><year>2016</year><month>03</month><day>10</day><volume>13</volume><fpage>35</fpage><pub-id pub-id-type="doi">10.1186/s12966-016-0359-9</pub-id><pub-id pub-id-type="medline">26964880</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>Mandracchia</surname><given-names>F</given-names> </name><name name-style="western"><surname>Llaurad&#x00F3;</surname><given-names>E</given-names> </name><name name-style="western"><surname>Tarro</surname><given-names>L</given-names> </name><name name-style="western"><surname>Valls</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Sol&#x00E0;</surname><given-names>R</given-names> </name></person-group><article-title>Mobile phone apps for food allergies or intolerances in app stores: systematic search and quality assessment using the Mobile App Rating Scale (MARS)</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>09</month><day>16</day><volume>8</volume><issue>9</issue><fpage>e18339</fpage><pub-id pub-id-type="doi">10.2196/18339</pub-id><pub-id pub-id-type="medline">32936078</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>Mendi</surname><given-names>O</given-names> </name><name name-style="western"><surname>Kiymac Sari</surname><given-names>M</given-names> </name><name name-style="western"><surname>Stoyanov</surname><given-names>S</given-names> </name><name name-style="western"><surname>Mendi</surname><given-names>B</given-names> </name></person-group><article-title>Development and validation of the Turkish version of the Mobile App Rating Scale - MARS-TR</article-title><source>Int J Med Inform</source><year>2022</year><month>10</month><volume>166</volume><fpage>104843</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2022.104843</pub-id><pub-id pub-id-type="medline">35964383</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>Messner</surname><given-names>EM</given-names> </name><name name-style="western"><surname>Terhorst</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Barke</surname><given-names>A</given-names> </name><etal/></person-group><article-title>The German version of the Mobile App Rating Scale (MARS-G): development and validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>03</month><day>27</day><volume>8</volume><issue>3</issue><fpage>e14479</fpage><pub-id pub-id-type="doi">10.2196/14479</pub-id><pub-id pub-id-type="medline">32217504</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>Domnich</surname><given-names>A</given-names> </name><name name-style="western"><surname>Arata</surname><given-names>L</given-names> </name><name name-style="western"><surname>Amicizia</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Development and validation of the Italian version of the Mobile Application Rating Scale and its generalisability to apps targeting primary prevention</article-title><source>BMC Med Inform Decis Mak</source><year>2016</year><month>07</month><day>7</day><volume>16</volume><fpage>83</fpage><pub-id pub-id-type="doi">10.1186/s12911-016-0323-2</pub-id><pub-id pub-id-type="medline">27387434</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>Martin Payo</surname><given-names>R</given-names> </name><name name-style="western"><surname>Fernandez &#x00C1;lvarez</surname><given-names>MM</given-names> </name><name name-style="western"><surname>Blanco D&#x00ED;az</surname><given-names>M</given-names> </name><name name-style="western"><surname>Cuesta Izquierdo</surname><given-names>M</given-names> </name><name name-style="western"><surname>Stoyanov</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Llaneza Su&#x00E1;rez</surname><given-names>E</given-names> </name></person-group><article-title>Spanish adaptation and validation of the Mobile Application Rating Scale questionnaire</article-title><source>Int J Med Inform</source><year>2019</year><month>09</month><volume>129</volume><fpage>95</fpage><lpage>99</lpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.06.005</pub-id><pub-id pub-id-type="medline">31445295</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>Stoyanov</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Hides</surname><given-names>L</given-names> </name><name name-style="western"><surname>Kavanagh</surname><given-names>DJ</given-names> </name><name name-style="western"><surname>Wilson</surname><given-names>H</given-names> </name></person-group><article-title>Development and validation of the user version of the Mobile Application Rating Scale (uMARS)</article-title><source>JMIR Mhealth Uhealth</source><year>2016</year><month>06</month><day>10</day><volume>4</volume><issue>2</issue><fpage>e72</fpage><pub-id pub-id-type="doi">10.2196/mhealth.5849</pub-id><pub-id pub-id-type="medline">27287964</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>LeBeau</surname><given-names>K</given-names> </name><name name-style="western"><surname>Huey</surname><given-names>LG</given-names> </name><name name-style="western"><surname>Hart</surname><given-names>M</given-names> </name></person-group><article-title>Assessing the quality of mobile apps used by occupational therapists: evaluation using the user version of the Mobile Application Rating Scale</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>05</month><day>1</day><volume>7</volume><issue>5</issue><fpage>e13019</fpage><pub-id pub-id-type="doi">10.2196/13019</pub-id><pub-id pub-id-type="medline">31066712</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Adam</surname><given-names>A</given-names> </name><name name-style="western"><surname>Hellig</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Perera</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bolton</surname><given-names>D</given-names> </name><name name-style="western"><surname>Lawrentschuk</surname><given-names>N</given-names> </name></person-group><article-title>&#x201C;Prostate cancer risk calculator&#x201D; mobile applications (apps): a systematic review and scoring using the validated user version of the Mobile Application Rating Scale (uMARS)</article-title><source>World J Urol</source><year>2018</year><month>04</month><volume>36</volume><issue>4</issue><fpage>565</fpage><lpage>573</lpage><pub-id pub-id-type="doi">10.1007/s00345-017-2150-1</pub-id><pub-id pub-id-type="medline">29222595</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bardus</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ali</surname><given-names>A</given-names> </name><name name-style="western"><surname>Demachkieh</surname><given-names>F</given-names> </name><name name-style="western"><surname>Hamadeh</surname><given-names>G</given-names> </name></person-group><article-title>Assessing the quality of mobile phone apps for weight management: user-centered study with employees from a Lebanese university</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>01</month><day>23</day><volume>7</volume><issue>1</issue><fpage>e9836</fpage><pub-id pub-id-type="doi">10.2196/mhealth.9836</pub-id><pub-id pub-id-type="medline">30672742</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ko</surname><given-names>S</given-names> </name><name name-style="western"><surname>Woo</surname><given-names>H</given-names> </name></person-group><article-title>Users&#x2019; needs for mental health apps: quality evaluation using the User Version of the Mobile Application Rating Scale</article-title><source>JMIR Mhealth Uhealth</source><year>2025</year><month>07</month><day>4</day><volume>13</volume><fpage>e64622</fpage><pub-id pub-id-type="doi">10.2196/64622</pub-id><pub-id pub-id-type="medline">40614100</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Morselli</surname><given-names>S</given-names> </name><name name-style="western"><surname>Sebastianelli</surname><given-names>A</given-names> </name><name name-style="western"><surname>Domnich</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Translation and validation of the Italian version of the user version of the Mobile Application Rating Scale (uMARS)</article-title><source>J Prev Med Hyg</source><year>2021</year><month>03</month><volume>62</volume><issue>1</issue><fpage>E243</fpage><lpage>E248</lpage><pub-id pub-id-type="doi">10.15167/2421-4248/jpmh2021.62.1.1894</pub-id><pub-id pub-id-type="medline">34322643</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Baptista</surname><given-names>S</given-names> </name><name name-style="western"><surname>Oldenburg</surname><given-names>B</given-names> </name><name name-style="western"><surname>O&#x2019;Neil</surname><given-names>A</given-names> </name></person-group><article-title>Response to &#x201C;development and validation of the user version of the Mobile Application Rating Scale (uMARS)&#x201D;</article-title><source>JMIR Mhealth Uhealth</source><year>2017</year><month>06</month><day>9</day><volume>5</volume><issue>6</issue><fpage>e16</fpage><pub-id pub-id-type="doi">10.2196/mhealth.6419</pub-id><pub-id pub-id-type="medline">28600277</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Backes</surname><given-names>C</given-names> </name><name name-style="western"><surname>Moyano</surname><given-names>C</given-names> </name><name name-style="western"><surname>Rimaud</surname><given-names>C</given-names> </name><name name-style="western"><surname>Bienvenu</surname><given-names>C</given-names> </name><name name-style="western"><surname>Schneider</surname><given-names>MP</given-names> </name></person-group><article-title>Digital medication adherence support: could healthcare providers recommend mobile health apps?</article-title><source>Front Med Technol</source><year>2020</year><volume>2</volume><fpage>616242</fpage><pub-id pub-id-type="doi">10.3389/fmedt.2020.616242</pub-id><pub-id pub-id-type="medline">35047896</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Saparamadu</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Fernando</surname><given-names>P</given-names> </name><name name-style="western"><surname>Zeng</surname><given-names>P</given-names> </name><etal/></person-group><article-title>User-centered design process of an mHealth app for health professionals: case study</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>03</month><day>26</day><volume>9</volume><issue>3</issue><fpage>e18079</fpage><pub-id pub-id-type="doi">10.2196/18079</pub-id><pub-id pub-id-type="medline">33769297</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Leigh</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ashall-Payne</surname><given-names>L</given-names> </name></person-group><article-title>The role of health-care providers in mHealth adoption</article-title><source>Lancet Digit Health</source><year>2019</year><month>06</month><volume>1</volume><issue>2</issue><fpage>e58</fpage><lpage>e59</lpage><pub-id pub-id-type="doi">10.1016/S2589-7500(19)30025-1</pub-id><pub-id pub-id-type="medline">33323231</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jacob</surname><given-names>C</given-names> </name><name name-style="western"><surname>Sanchez-Vazquez</surname><given-names>A</given-names> </name><name name-style="western"><surname>Ivory</surname><given-names>C</given-names> </name></person-group><article-title>Clinicians&#x2019; role in the adoption of an oncology decision support app in Europe and its implications for organizational practices: qualitative case study</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>05</month><day>3</day><volume>7</volume><issue>5</issue><fpage>e13555</fpage><pub-id pub-id-type="doi">10.2196/13555</pub-id><pub-id pub-id-type="medline">31066710</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="web"><person-group person-group-type="author"><collab>NTFGH LabMed</collab></person-group><source>Medical Laboratory Mobile App (102) [Mobile application software]</source><year>2019</year><access-date>2026-06-18</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://apps.apple.com/sg/app/ntfgh-labmed/id1440006973">https://apps.apple.com/sg/app/ntfgh-labmed/id1440006973</ext-link></comment></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Streiner</surname><given-names>DL</given-names> </name><name name-style="western"><surname>Kottner</surname><given-names>J</given-names> </name></person-group><article-title>Recommendations for reporting the results of studies of instrument and scale development and testing</article-title><source>J Adv Nurs</source><year>2014</year><month>09</month><volume>70</volume><issue>9</issue><fpage>1970</fpage><lpage>1979</lpage><pub-id pub-id-type="doi">10.1111/jan.12402</pub-id><pub-id pub-id-type="medline">24684713</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="web"><source>EQUATOR Network</source><access-date>2025-01-31</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.equator-network.org/">https://www.equator-network.org/</ext-link></comment></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tsang</surname><given-names>S</given-names> </name><name name-style="western"><surname>Royse</surname><given-names>CF</given-names> </name><name name-style="western"><surname>Terkawi</surname><given-names>AS</given-names> </name></person-group><article-title>Guidelines for developing, translating, and validating a questionnaire in perioperative and pain medicine</article-title><source>Saudi J Anaesth</source><year>2017</year><month>05</month><volume>11</volume><issue>Suppl 1</issue><fpage>S80</fpage><lpage>S89</lpage><pub-id pub-id-type="doi">10.4103/sja.SJA_203_17</pub-id><pub-id pub-id-type="medline">28616007</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Salda&#x00F1;a</surname><given-names>J</given-names> </name></person-group><source>The Coding Manual for Qualitative Researchers</source><year>2021</year><edition>4</edition><publisher-name>SAGE Publications</publisher-name></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Harris</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>R</given-names> </name><name name-style="western"><surname>Thielke</surname><given-names>R</given-names> </name><name name-style="western"><surname>Payne</surname><given-names>J</given-names> </name><name name-style="western"><surname>Gonzalez</surname><given-names>N</given-names> </name><name name-style="western"><surname>Conde</surname><given-names>JG</given-names> </name></person-group><article-title>Research Electronic Data Capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title><source>J Biomed Inform</source><year>2009</year><month>04</month><volume>42</volume><issue>2</issue><fpage>377</fpage><lpage>381</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id><pub-id pub-id-type="medline">18929686</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="web"><article-title>Stata index: release 17</article-title><source>StataCorp</source><access-date>2026-07-27</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.stata.com/manuals17/i.pdf">https://www.stata.com/manuals17/i.pdf</ext-link></comment></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Taber</surname><given-names>KS</given-names> </name></person-group><article-title>The use of Cronbach&#x2019;s alpha when developing and reporting research instruments in science education</article-title><source>Res Sci Educ</source><year>2018</year><month>12</month><volume>48</volume><issue>6</issue><fpage>1273</fpage><lpage>1296</lpage><pub-id pub-id-type="doi">10.1007/s11165-016-9602-2</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tavakol</surname><given-names>M</given-names> </name><name name-style="western"><surname>Dennick</surname><given-names>R</given-names> </name></person-group><article-title>Making sense of Cronbach&#x2019;s alpha</article-title><source>Int J Med Educ</source><year>2011</year><month>06</month><day>27</day><volume>2</volume><fpage>53</fpage><lpage>55</lpage><pub-id pub-id-type="doi">10.5116/ijme.4dfb.8dfd</pub-id><pub-id pub-id-type="medline">28029643</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Edelen</surname><given-names>MO</given-names> </name><name name-style="western"><surname>Reeve</surname><given-names>BB</given-names> </name></person-group><article-title>Applying item response theory (IRT) modeling to questionnaire development, evaluation, and refinement</article-title><source>Qual Life Res</source><year>2007</year><volume>16 Suppl 1</volume><fpage>5</fpage><lpage>18</lpage><pub-id pub-id-type="doi">10.1007/s11136-007-9198-0</pub-id><pub-id pub-id-type="medline">17375372</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="web"><article-title>Personal Data Protection Act 2012</article-title><source>Singapore Statutes Online</source><access-date>2026-06-18</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://sso.agc.gov.sg/Act/PDPA2012#:~:text=The%20purpose%20of%20this%20Act,consider%20appropriate%20in%20the%20circumstances">https://sso.agc.gov.sg/Act/PDPA2012#:~:text=The%20purpose%20of%20this%20Act,consider%20appropriate%20in%20the%20circumstances</ext-link></comment></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="web"><article-title>Health Insurance Portability and Accountability Act of 1996</article-title><source>US Government Publishing Office (GPO)</source><year>1996</year><access-date>2026-06-18</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.govinfo.gov/content/pkg/PLAW-104publ191/pdf/PLAW-104publ191.pdf">https://www.govinfo.gov/content/pkg/PLAW-104publ191/pdf/PLAW-104publ191.pdf</ext-link></comment></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ndlovu</surname><given-names>K</given-names> </name><name name-style="western"><surname>Mars</surname><given-names>M</given-names> </name><name name-style="western"><surname>Scott</surname><given-names>RE</given-names> </name></person-group><article-title>Interoperability frameworks linking mHealth applications to electronic record systems</article-title><source>BMC Health Serv Res</source><year>2021</year><month>05</month><day>13</day><volume>21</volume><issue>1</issue><fpage>459</fpage><pub-id pub-id-type="doi">10.1186/s12913-021-06473-6</pub-id><pub-id pub-id-type="medline">33985495</pub-id></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Galetsi</surname><given-names>P</given-names> </name><name name-style="western"><surname>Katsaliaki</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kumar</surname><given-names>S</given-names> </name></person-group><article-title>Exploring benefits and ethical challenges in the rise of mHealth (mobile healthcare) technology for the common good: an analysis of mobile applications for health specialists</article-title><source>Technovation</source><year>2023</year><month>03</month><volume>121</volume><fpage>102598</fpage><pub-id pub-id-type="doi">10.1016/j.technovation.2022.102598</pub-id></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Herpertz</surname><given-names>J</given-names> </name><name name-style="western"><surname>Dwyer</surname><given-names>B</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>J</given-names> </name><name name-style="western"><surname>Opel</surname><given-names>N</given-names> </name><name name-style="western"><surname>Torous</surname><given-names>J</given-names> </name></person-group><article-title>Developing a standardized framework for evaluating health apps using natural language processing</article-title><source>Sci Rep</source><year>2025</year><month>04</month><day>6</day><volume>15</volume><issue>1</issue><fpage>11775</fpage><pub-id pub-id-type="doi">10.1038/s41598-025-96369-w</pub-id><pub-id pub-id-type="medline">40189623</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hua</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Xia</surname><given-names>W</given-names> </name><name name-style="western"><surname>Bates</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Standardizing and scaffolding health care AI-chatbot evaluation: systematic review</article-title><source>JMIR AI</source><year>2025</year><month>11</month><day>7</day><volume>4</volume><fpage>e69006</fpage><pub-id pub-id-type="doi">10.2196/69006</pub-id><pub-id pub-id-type="medline">41202290</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Semistructured interview guide used in phase 1.</p><media xlink:href="mhealth_v14i1e48828_app1.pdf" xlink:title="PDF File, 141 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Final version of the Mobile App Rating Scale for health care professionals questionnaire.</p><media xlink:href="mhealth_v14i1e48828_app2.pdf" xlink:title="PDF File, 168 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Item-level missing data and &#x201C;don&#x2019;t know&#x201D; response summary for the Mobile App Rating Scale for health care professionals questionnaire (phase 2).</p><media xlink:href="mhealth_v14i1e48828_app3.pdf" xlink:title="PDF File, 146 KB"/></supplementary-material></app-group></back></article>