<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</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">v8i7e18015</article-id>
      <article-id pub-id-type="pmid">32735228</article-id>
      <article-id pub-id-type="doi">10.2196/18015</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Tool for Rating the Value of Health Education Mobile Apps to Enhance Student Learning (MARuL): Development and Usability Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Farič</surname>
            <given-names>Nuša</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Grad</surname>
            <given-names>Roland</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Gladman</surname>
            <given-names>Tehmina</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Education Unit</institution>
            <institution>University of Otago Wellington</institution>
            <addr-line>PO Box 7343</addr-line>
            <addr-line>Newtown</addr-line>
            <addr-line>Wellington, 6242</addr-line>
            <country>New Zealand</country>
            <phone>64 04 918 6749</phone>
            <email>tehmina.gladman@otago.ac.nz</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5112-3460</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Tylee</surname>
            <given-names>Grace</given-names>
          </name>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1964-6958</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Gallagher</surname>
            <given-names>Steve</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1108-4388</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Mair</surname>
            <given-names>Jonathan</given-names>
          </name>
          <degrees>MBChB</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2512-2421</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Rennie</surname>
            <given-names>Sarah C</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8638-8955</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Grainger</surname>
            <given-names>Rebecca</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9201-8678</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Education Unit</institution>
        <institution>University of Otago Wellington</institution>
        <addr-line>Wellington</addr-line>
        <country>New Zealand</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>University of Otago Wellington</institution>
        <addr-line>Wellington</addr-line>
        <country>New Zealand</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Education Unit</institution>
        <institution>Dunedin School of Medicine</institution>
        <institution>University of Otago</institution>
        <addr-line>Dunedin</addr-line>
        <country>New Zealand</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Hutt Valley District Health Board</institution>
        <addr-line>Lower Hutt</addr-line>
        <country>New Zealand</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Tehmina Gladman <email>tehmina.gladman@otago.ac.nz</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>31</day>
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <volume>8</volume>
      <issue>7</issue>
      <elocation-id>e18015</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>1</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>25</day>
          <month>3</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>29</day>
          <month>4</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>30</day>
          <month>4</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Tehmina Gladman, Grace Tylee, Steve Gallagher, Jonathan Mair, Sarah C Rennie, Rebecca Grainger. Originally published in JMIR mHealth and uHealth (http://mhealth.jmir.org), 31.07.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://mhealth.jmir.org/2020/7/e18015" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>To realize the potential for mobile learning in clinical skills acquisition, medical students and their teachers should be able to evaluate the value of an app to support student learning of clinical skills. To our knowledge, there is currently no rubric for evaluation of quality or value that is specific for apps to support medical student learning. Such a rubric might assist students to be more confident in using apps to support their learning.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The objective of this study was to develop an instrument that can be used by health professional educators to rate the value of a mobile app to support health professional student learning.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Using the literature, we developed a list of potential criteria for the evaluation of educational app value, which were then refined with a student group using a modified nominal group technique. The refined list was organized into themes, and the initial rubric, Mobile App Rubric for Learning (MARuL, version 1), was developed. iOS and Android app stores were searched for clinical skills apps that met our inclusion criteria. After the 2 reviewers were trained and the item descriptions were refined (version 2), a random sample of 10 included apps, 5 for each mobile operating system, was reviewed. Interitem and interrater analyses and discussions with the reviewers resulted in refinement of MARuL to version 3. The reviewers completed a review of 41 clinical skills mobile apps, and a second round of interitem and interrater reliability testing was performed, leading to version 4 of the MARuL.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Students identified 28 items (from an initial set of 144 possible items) during the nominal group phase, and these were then grouped into 4 themes: teaching and learning, user centered, professional, and usability. Testing and refinement with reviewers reduced the list to 26 items. Internal consistency for MARuL was excellent (α=.96), and the interrater reliability as measured by the intraclass correlation coefficient (ICC) was good (ICC=0.66).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>MARuL offers a fast and user-friendly method for teachers to select valuable apps to enhance student learning.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>questionnaire design</kwd>
        <kwd>medical education</kwd>
        <kwd>health occupations students</kwd>
        <kwd>just-in-time learning</kwd>
        <kwd>self-directed learning</kwd>
        <kwd>mobile phone</kwd>
        <kwd>rubric</kwd>
        <kwd>mobile learning</kwd>
        <kwd>mobile apps</kwd>
        <kwd>mhealth</kwd>
        <kwd>digital learning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Smartphones and tablets have made mobile learning an important component of education, enabling learning anywhere, at any time, using mobile apps [<xref ref-type="bibr" rid="ref1">1</xref>]. Most education apps have specific functions or aims, such as providing resources for reference while learning or in practice, learning activities and games, or organizing activities related to learning. Apps can be found by keyword search in the app stores (eg, Google Play Store, iOS App Store), through recommendations, or within app store–determined categories [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
        <p>In medical education, the use of apps for reference and learning on the go (<italic>just in time</italic>) for ongoing professional development is widespread [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. However, previous work suggests that medical students may still prefer textbooks and lectures as a learning resource [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>] and predominantly use apps for reference and revision [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. Although the determinants of preference for textbooks have not been explored, there may be barriers to finding apps that are both relevant and valuable for student learning [<xref ref-type="bibr" rid="ref5">5</xref>]. Within app stores, star ratings and reviews are the main indicators of app quality or value; however, these can be subjective and only relevant if the reviewer has needs and expectations similar to the potential app user [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Furthermore, a search of medical apps reveals a very large number of potential apps to choose from and many that have not received enough reviews to get a rating. Owing to the number of options to choose from, and the lack of good quality guidance to inform their choices, students may not be accessing and using apps that could support their learning. Providing a standard way of evaluating apps for medical education may improve students’ ability to find or identify apps to support their learning.</p>
      </sec>
      <sec>
        <title>Evaluating Apps</title>
        <p>To avoid the app overload caused by the increasing number of apps in the app stores, potential app users are recommended to use the literature to identify valuable apps [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. There is evolving literature aiming to identify apps for health conditions; to support self-management, education, or behavior change [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]; and to evaluate app quality [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. To date, similar literature in education has focused on apps for use by teachers working with students with learning disabilities [<xref ref-type="bibr" rid="ref14">14</xref>] or preschool student learning [<xref ref-type="bibr" rid="ref15">15</xref>]. In addition to providing curated lists of apps, this literature often evaluates app quality with instruments that include some generic aspects of proposed quality; for example, a component to evaluate the suitability of design and aesthetics. However, these rubrics also have components or domains specific to the type or main function of an app. For instance, the evaluation rubric for health care smartphone apps by Jin and Kim [<xref ref-type="bibr" rid="ref11">11</xref>] emphasizes the input of medical experts and the developers’ citing of authoritative sources. In comparison, the rubric by Lee and Kim [<xref ref-type="bibr" rid="ref12">12</xref>] for evaluating educational apps emphasizes the <italic>teaching and learning</italic> component of an app. When developing a rubric to evaluate apps, a balance between general and specific criteria is needed to ensure that the rubric is both reliable and objective [<xref ref-type="bibr" rid="ref10">10</xref>]. To our knowledge, there is currently no rubric for evaluation of quality or value that is specific for apps to support medical student learning. Such a rubric might assist students to be more confident in using apps to support their learning.</p>
      </sec>
      <sec>
        <title>App Evaluation Rubrics</title>
        <p>Most multidimensional app evaluation rubrics include both user-centered features (eg, engagement) and technology-centered features (eg, functionality) [<xref ref-type="bibr" rid="ref10">10</xref>]. Although the model for education app evaluation by Lee and Kim [<xref ref-type="bibr" rid="ref12">12</xref>] emphasizes teaching and learning, it also recognized the need for a technologically stable app, with “quick interactions (fast loading times) and error-free stability” [<xref ref-type="bibr" rid="ref12">12</xref>]. It was concluded that factors must be considered together because they are interdependent in nature rather than independent. Stoyanov et al [<xref ref-type="bibr" rid="ref10">10</xref>] also emphasized the importance of considering multiple features of an app to increase the objectivity and reliability of an app evaluation scale.</p>
        <p>An additional factor that is relevant for health-related mobile apps is the credibility of the app content. Having apps with evidence-based approaches to health should minimize the risk of harm and promote safe application of knowledge by app users [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. In the medical education setting, for example, when learning clinical skills, it is critical to learn skills that are relevant and accurate in the local health care environment. Apps that focus on clinical skills—that is, apps supporting learning of history taking, examination, communication, or procedures—provide opportunities for just-in-time learning in clinical settings where textbooks are not available, making apps supporting acquisition of clinical skills a good test case for the development of an app evaluation rubric.</p>
      </sec>
      <sec>
        <title>Purpose and Research Question</title>
        <p>To realize the potential for mobile learning in clinical skills acquisition, medical students and their teachers should be able to evaluate the value of an app for supporting the learning of clinical skills. Our aim was to develop a rubric that can be used by staff to evaluate the value of apps for learning the clinical skills of history taking, examination, communication, or procedures so that recommendations can be made to students. The initial research question was as follows: “What key domains of value need to be included in a reliable measure that teachers can use to rate mobile apps for just-in-time learning?”</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The development of evaluative rubrics for apps uses some or all of the following steps. A literature search is completed to identify previous literature with quality evaluation criteria, followed by a discussion among topic experts to group criteria and develop scale items [<xref ref-type="bibr" rid="ref10">10</xref>]. A survey or focus group is conducted to gain expert opinion on the relevance of items generated from the literature search [<xref ref-type="bibr" rid="ref12">12</xref>]. Users and experts evaluate apps with the draft rubric to test its reliability and validity [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], with items in the rubric refined accordingly. Many rubrics are structured using overarching factors with relevant subterms to clarify and give examples [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>We undertook a literature review to identify potential rubric items, which were evaluated by a group of medical students using a modified nominal group technique. The performance of the preliminary rubric was then evaluated by clinical and education experts for use with clinical skills apps, which were identified using a comprehensive search strategy in Google Play and iTunes app stores. The rubric was then refined through expert feedback and statistical analysis using the classical test theory (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Process for developing the Mobile App Rubric for Learning. MARuL: Mobile App Rubric for Learning.</p>
          </caption>
          <graphic xlink:href="mhealth_v8i7e18015_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Definitions</title>
        <p>We defined <italic>value</italic> as referring to an object that is perceived to have utility in meeting short- or long-term goals [<xref ref-type="bibr" rid="ref20">20</xref>]. <italic>Just-in-time learning</italic> is defined as a method of learning that is driven by the learner, when and where they require it [<xref ref-type="bibr" rid="ref21">21</xref>]. With this definition, the learner anticipates learning and performance requirements rather than responding to them [<xref ref-type="bibr" rid="ref21">21</xref>]. Just-in-time learning occurs temporally close to a clinical learning encounter, for example, with a mobile device [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. <italic>Clinical skills</italic> apps are those that include opportunities to learn and improve history taking, examination, communication, or procedures [<xref ref-type="bibr" rid="ref24">24</xref>]. A <italic>rubric</italic> is a scoring method that uses evaluative criteria with quality definitions and a clear scoring strategy to determine the quality of the global concept being scored [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
      </sec>
      <sec>
        <title>Development of Potential Rubric Items</title>
        <p>A literature review was undertaken to identify criteria previously used to evaluate the quality of mobile apps for education. An expert librarian conducted a literature search on Scopus, MEDLINE, and Google Scholar (between August 14 and 21, 2018) using search terms related to the evaluation of educational mobile apps using evidence-based methods (<xref ref-type="boxed-text" rid="box1">Textboxes 1</xref>-<xref ref-type="boxed-text" rid="box4">4</xref>). After duplicates were removed, the records were exported into Rayyan QCRI (Qatar Computing Research Institute), a cloud-based method for completing systematic reviews of the literature [<xref ref-type="bibr" rid="ref26">26</xref>], and 4 educational experts (TG, SR, SG, and RG) independently reviewed the titles and abstracts of the records to identify articles that potentially met the inclusion criteria. The inclusion criteria used were as follows: clear descriptions of the concepts, list, or rubric for the evaluation of app quality; reliability or validity testing of the method of evaluation; and the evaluation was for educational mobile apps, which we defined as apps whose primary purpose was to support the education of any population. Articles were excluded if they were literature reviews or they described a framework for evaluation without describing a specific measure. Articles were included if 3 or more reviewers agreed on their relevance.</p>
        <boxed-text id="box1" position="float">
          <title>Device related literature search terms.</title>
          <list list-type="bullet">
            <list-item>
              <p>app</p>
            </list-item>
            <list-item>
              <p>smart*</p>
            </list-item>
            <list-item>
              <p>phone*</p>
            </list-item>
            <list-item>
              <p>cellular</p>
            </list-item>
            <list-item>
              <p>smartphone</p>
            </list-item>
            <list-item>
              <p>smart phone</p>
            </list-item>
            <list-item>
              <p>mobile</p>
            </list-item>
            <list-item>
              <p>tablet</p>
            </list-item>
          </list>
        </boxed-text>
        <boxed-text id="box2" position="float">
          <title>Action related literature search terms.</title>
          <list list-type="bullet">
            <list-item>
              <p>evaluat*</p>
            </list-item>
            <list-item>
              <p>assess*</p>
            </list-item>
            <list-item>
              <p>apprais*</p>
            </list-item>
            <list-item>
              <p>measure*</p>
            </list-item>
            <list-item>
              <p>validat*</p>
            </list-item>
            <list-item>
              <p>test*</p>
            </list-item>
            <list-item>
              <p>determine*</p>
            </list-item>
            <list-item>
              <p>measur*</p>
            </list-item>
          </list>
        </boxed-text>
        <boxed-text id="box3" position="float">
          <title>Measure related literature search terms.</title>
          <list list-type="bullet">
            <list-item>
              <p>criteria</p>
            </list-item>
            <list-item>
              <p>checklist*</p>
            </list-item>
            <list-item>
              <p>rubric*</p>
            </list-item>
            <list-item>
              <p>framework*</p>
            </list-item>
            <list-item>
              <p>quality</p>
            </list-item>
            <list-item>
              <p>useful*</p>
            </list-item>
          </list>
        </boxed-text>
        <boxed-text id="box4" position="float">
          <title>Teaching and learning related literature search terms.</title>
          <list list-type="bullet">
            <list-item>
              <p>educat*</p>
            </list-item>
            <list-item>
              <p>learn*</p>
            </list-item>
            <list-item>
              <p>teach*</p>
            </list-item>
            <list-item>
              <p>student*</p>
            </list-item>
            <list-item>
              <p>education*</p>
            </list-item>
            <list-item>
              <p>learning*</p>
            </list-item>
            <list-item>
              <p>educate</p>
            </list-item>
          </list>
        </boxed-text>
        <p>The full texts of all identified relevant articles were reviewed in detail by a reviewer (GT), and the concepts or terms that measure or assess app quality were extracted along with definitions. The extracted terms and definitions were then grouped and organized by GT, a medical student representing the end user for the rubric, and TG, an academic with expertise in electronic learning (e-learning) and educational psychology. Overarching concepts (called <italic>categories</italic>) were identified and related terms were grouped together within the concepts. For instance, <italic>use without an internet connection</italic> was grouped with <italic>platform</italic>, <italic>syncing</italic>, <italic>updates</italic>, and <italic>compatibility</italic> under the concept of <italic>technical specifications</italic>. Similar terms were merged.</p>
      </sec>
      <sec>
        <title>Nominal Group Technique</title>
        <p>A convenience sample of 10 medical students, recruited using targeted invitations, participated in a nominal group held at the University of Otago Wellington, School of Medicine, on December 6, 2018. Ethical approval was obtained from the Otago Human Ethics Committee, reference number D18/337, and written consent was obtained from the students.</p>
        <p>In the nominal group technique, group interaction is facilitated by the leader and verbal interaction is restricted to a discussion between the leader and participants with no discussion between participants [<xref ref-type="bibr" rid="ref27">27</xref>]. The technique is particularly useful in ensuring that all members of a group are heard. This makes it an ideal method in a group where there are varied levels of experience with the topic under discussion. Ranking of ideas occurs using votes or a Likert-type scale [<xref ref-type="bibr" rid="ref27">27</xref>]. A voting system with a predetermined maximum of 3 rounds of voting was used after the initial ranking of terms. Limited voting was chosen to reduce the possibility of participant fatigue [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>Students were asked to review the refined list of terms/concepts for app evaluation (with definitions) and indicate their top 20 terms on a ranking sheet without discussion. They were also asked to add any important missing terms or concepts. Each student then in turn stated a term on their list not previously offered by a student, which was recorded by the leader. This continued until all terms from each student’s top 20 had been recorded.</p>
        <p>Students were then given an opportunity for discussion before the first round of voting. Students voted on item inclusion in the final list using the options <italic>keep</italic>, <italic>unsure</italic>, and <italic>discard</italic>. Overall, 7 or more votes for the same option were considered a majority. Items that did not receive a majority vote were recorded and discussed before the next voting round. In the second round, students were encouraged to vote <italic>keep</italic> or <italic>discard</italic> but still had the option of <italic>unsure</italic>. In the second and third rounds, having 6 or more votes was considered a majority. In the third round, only options <italic>keep</italic> and <italic>discard</italic> were allowed. Results from each round were recorded by a group facilitator, whereas the leader facilitated group discussions and answered questions.</p>
      </sec>
      <sec>
        <title>Development of Rubric</title>
        <p>The terms chosen by the nominal group made up the preliminary rubric, which we named <italic>Mobile App Rubric for Learning</italic> (MARuL). Two authors (TG and GT) grouped the terms into themes separately, and then came together to discuss final category names and grouping of terms, with subterms used to develop descriptors for the scale.</p>
      </sec>
      <sec>
        <title>App Search</title>
        <p>The search of the iOS and Google Play stores for clinical skills apps was undertaken from January 15 to February 1, 2019. The search was conducted based on the Preferred Reporting Items for Systematic Reviews and Meta-analyses guidelines for systematic reviews, with search terms confirmed by discussion (GT, TG, and RG) after preliminary searches (<xref ref-type="boxed-text" rid="box5">Textbox 5</xref>) [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. The inclusion criteria were as follows: available in English; includes at least one of the keywords in the title or description; includes an interactive element requiring some form of user input; target audience includes medical students; and support for iOS 10 or later/Android version 7 or later. The exclusion criteria were as follows: priced over NZ $10.00 (US $6.30) for a one-off price or monthly subscription (based on expected student willingness to pay); reference-only apps (passive with no student input); designed for staff-only use in formative or summative assessment contexts; were a complement to other software (not standalone; requires a log-in/sign up).</p>
        <boxed-text id="box5" position="float">
          <title>App search terms.</title>
          <list list-type="bullet">
            <list-item>
              <p>clinical skills</p>
            </list-item>
            <list-item>
              <p>OSCE</p>
            </list-item>
            <list-item>
              <p>objective structured clinical examination</p>
            </list-item>
            <list-item>
              <p>medical history taking</p>
            </list-item>
            <list-item>
              <p>clinical history taking</p>
            </list-item>
            <list-item>
              <p>patient history</p>
            </list-item>
            <list-item>
              <p>medical examination</p>
            </list-item>
            <list-item>
              <p>physical examination</p>
            </list-item>
            <list-item>
              <p>clinical examination</p>
            </list-item>
            <list-item>
              <p>clinical exam</p>
            </list-item>
            <list-item>
              <p>physical exam</p>
            </list-item>
            <list-item>
              <p>medical exam</p>
            </list-item>
            <list-item>
              <p>planning and explaining</p>
            </list-item>
            <list-item>
              <p>patient education</p>
            </list-item>
          </list>
        </boxed-text>
        <p>A data screening and extraction spreadsheet was developed and refined by 2 authors (GT and TG) using Airtable [<xref ref-type="bibr" rid="ref31">31</xref>]. The app search of the iOS and Google Play Store was conducted independently by 2 authors (GT and TG). Apps were screened based on their title and the description in the app store. App name, developer, operating system, reviewer, and inclusion decision were recorded for all screened apps. For the excluded apps, the first identified exclusion criterion was recorded. GT and TG then reviewed all the apps with discrepant decisions and reached a consensus through discussion.</p>
      </sec>
      <sec>
        <title>Testing and Refinement of the Rubric</title>
        <p>To initially test the reliability of the MARuL, we developed a protocol based on previous research [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref30">30</xref>] and trialed this with a randomly chosen subset of 10 apps included from the search. The 10 randomly selected apps, 5 Android apps and 5 iOS apps, were downloaded between May 20 and 22, 2019. The iPhones used were iPhone 6 and 6 plus running iOS 12.3.1. The Android phones were Samsung Galaxy J1Ace running Android 5.1.1. Following the initial testing, we refined the rubric and completed reliability testing with the remaining included apps identified in our search of the app stores. Trialing of the rubric with clinical skills apps was completed independently by 2 authors: (1) a hospital-based junior doctor (3 years postgraduate) training in internal medicine (JM) and (2) the e-learning facilitator for the clinical years at a different campus of our medical school (SG). The first reviewer was able to review the apps from the point of view of a near-peer teacher of medical students, whereas the second reviewer reviewed from the point of view of a learning expert with over 10 years of experience in medical education.</p>
        <p>For training, the reviewers first used the MARuL to evaluate a previously excluded app, Clinical Skills by George Sim on iOS. The app was excluded because of a lack of interactive elements. The 2 reviewers each downloaded the app on an iPhone running iOS 12.2, tested the app features for 10 min and then independently evaluated the app using the MARuL. Following their review, they met with TG via videoconferencing to discuss their scoring of the app and ensure their understanding of the rubric items and process.</p>
        <p>Once the reviewers (JM and SG) had a clear understanding of the items and process for reviewing the apps, they each downloaded the same 5 randomly selected apps for both mobile operating systems. They independently spent a minimum of 10 min using each app before evaluating the app with the MARuL. MARuL ratings for each app and time taken to complete MARuL rating were collected using Qualtrics (Qualtrics, Provo, UT) [<xref ref-type="bibr" rid="ref32">32</xref>,], downloaded to an Excel spreadsheet, and analyzed using RStudio and appropriate packages [<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        <p>Internal consistency and interrater reliability were calculated, and then a discussion was held via videoconferencing to review discrepancies in scoring on the rubric and identify any refinements required to the items of the MARuL. The MARuL was then revised to rewrite some of the descriptors and remove an item that was considered redundant by the reviewers. The remaining apps were then independently trialed and evaluated using the revised MARuL.</p>
        <p>We calculated the internal consistency of the categories and the overall value measure using Cronbach alpha. Cronbach alpha measures how interrelated a set of items in a scale are, with scores ranging from 0 to 1, and higher scores indicating a stronger interitem relationship [<xref ref-type="bibr" rid="ref37">37</xref>]. Interrater reliability of the categories and overall value measure was calculated using the intraclass correlation coefficient (ICC). The ICC measures how much of the difference between sets of scores is because of measurement error, and it ranges from 0 to 1, with higher scores indicating stronger interrater reliability [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Rubric Items</title>
        <p>The literature search yielded 193 unique articles. After reviewing the titles and abstracts, 134 articles were eliminated. Furthermore, 8 articles were removed following full-text review. From the remaining 51 articles, 144 quality criteria were extracted, including main and descriptive subterms, 69 of which were main terms. After the consensus discussion and deletion of overlapping items and organization, a list of 36 main terms from 46 articles remained. (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> has the full list of terms and references).</p>
      </sec>
      <sec>
        <title>Nominal Group</title>
        <p>The nominal group had 10 students (6 female and 4 male) who had completed 2 years (n=2), 3 years (n=1), or 4 years (n=7) of medical school. Among them, 6 students identified as New Zealand European/Pākehā, 3 as Māori, and 1 as Sri Lankan. The nominal group ranking produced a list of 35 of the 36 terms; the only term excluded from voting was “product description.” Following the first vote, 18 items were kept and 17 were to be voted on again. The second vote on the 17 terms resulted in 10 being kept, 3 discarded, and 4 to be voted on again. After the third vote, 1 term was discarded and 3 received an equal number of keep and discard votes. These terms were “sharing,” “motivation,” and “self-directedness.” The final list of terms voted on by medical students included 28 items. <xref ref-type="table" rid="table1">Table 1</xref> shows the initial set of items and the outcome of the initial ranking and 3 voting rounds.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Outcome of nominal group votes.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="300"/>
            <col width="140"/>
            <col width="170"/>
            <col width="200"/>
            <col width="190"/>
            <thead>
              <tr valign="top">
                <td>Term</td>
                <td>Initial ranking</td>
                <td>First round of vote</td>
                <td>Second round of voting</td>
                <td>Third round of voting</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Satisfaction</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—<sup>a</sup></td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Ease of use</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Perceived usefulness</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Information quality</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Functionality</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Engagement</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>In line with professional standards</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Relevance to course</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Credibility of developers</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Privacy of information</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Discard</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Cost</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Advantage of using app</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Efficiency</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Instructional features</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Capacity to generate learning</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Aesthetics</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Quantity of information</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>User ratings</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Discard</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Intention to reuse</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Technical specifications</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Feedback</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Pedagogy</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Perceived enjoyment</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>No decision</td>
                <td>Discard</td>
              </tr>
              <tr valign="top">
                <td>Perceived importance</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Subjective quality</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Sharing</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>No decision</td>
                <td>No decision-Discard</td>
              </tr>
              <tr valign="top">
                <td>Motivation</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>No decision</td>
                <td>No decision-Discard</td>
              </tr>
              <tr valign="top">
                <td>Transparent</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>User experience</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Purpose</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Self-directedness</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>No decision</td>
                <td>No decision-Discard</td>
              </tr>
              <tr valign="top">
                <td>Playfulness</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Discard</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Lack of ads</td>
                <td>Yes</td>
                <td>Keep</td>
                <td>—</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Differentiation</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>User interactivity</td>
                <td>Yes</td>
                <td>No decision</td>
                <td>Keep</td>
                <td>—</td>
              </tr>
              <tr valign="top">
                <td>Product description</td>
                <td>No</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>The decision taken at each round of voting is shown. The voting round where a Keep or Discard decision is made ends the decision making for that item.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Development of Rubric</title>
        <p>The 28 items on the list determined by the student nominal group were grouped by 2 authors (GT and TG) into 4 themes based on their similar definitions and the aspects of value they appeared to measure. The categories formed were user-centered measures (n=7), teaching and learning measures (n=9), professional measures (n=4), and usability measures (n=8).</p>
        <p>Each category consists of a set of items that are described by posing questions for the user to consider. The questions were developed using definitions for the terms (written by GT) and the authors’ perspective on what was most important with regard to that measure. After consulting the literature, a 5-point Likert-type scale was chosen as the rating tool (0=does not fulfill the item requirements, 1=poorly fulfills requirements, 2=somewhat fulfills requirements, 3=mostly fulfills requirements, and 4=fully meets requirements) with the descriptors for each point on the scale written to answer the item questions. The rubric scale descriptors were developed by 2 authors (TG and GT) with reference to the literature. Some items were adapted from other rating scales such as the Mobile App Rating Scale (MARS) [<xref ref-type="bibr" rid="ref10">10</xref>], and these are clearly acknowledged on the final rubric (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). Scores for each item on the initial rubric are added to give a total score out of 112. Scores are used to classify apps as not at all valuable (&#60;50), potentially valuable (51-69), and probably valuable (&#62;69).</p>
      </sec>
      <sec>
        <title>App Search</title>
        <p>A total of 1291 iOS apps and 4190 Android apps were screened by title and description in the Apple and Google Play Stores, respectively. In iOS, 81 apps from 14 search terms (<xref ref-type="boxed-text" rid="box5">Textbox 5</xref>) were identified before removal of duplicates. After removal of duplicates, 35 unique apps were included for evaluation. For Android apps, the search terms identified 106 apps, of which 29 were unique. Apps found by only 1 researcher were not included because of concerns about the consistency of access to the app using typical search criteria. This gave a total of 64 apps with which to test the MARuL rubric.</p>
      </sec>
      <sec>
        <title>Reliability Analysis</title>
        <p>Initial testing and review of the rubric using the 10 selected apps occurred between June 18 and 22, 2019. One of the Android apps was unable to be tested by one of the reviewers as it did not run after installation on the device provided for testing and was excluded from further analysis.</p>
        <p>Cronbach alpha for the overall value was excellent (α=.95), and for each of the categories was acceptable to excellent (α=.78-.96). The ICC for overall value was good (ICC=0.81) and moderate to good for each of the categories (ICC=0.71-0.85). Pearson correlations showed moderate-to-strong correlations between the categories (r=0.49-0.91; <xref ref-type="table" rid="table2">Table 2</xref>). Through analysis and discussion with the reviewers, a further refinement of the descriptors of 5 of the items was completed and 1 item (transparency) was removed from the professional category. In addition, 2 further items (cost and advertisements) in the usability category were considered for removal because of poor statistical performance, but the reviewers felt they should remain as they were likely to be of more immediate concern both to students and to those individuals considering the value of apps for learning. <xref rid="figure2" ref-type="fig">Figure 2</xref> shows the process of development of the MARuL rubric from the initial rubric to the final version.</p>
        <p>Version 3 of the MARuL rubric, tested with the remaining 54 apps, consisted of 27 items across 4 categories: user-centered measures (n=7), teaching and learning measures (n=9), professional measures (n=3), and usability measures (n=8). The 54 remaining apps were downloaded and tested between July 29 and October 8, 2019. Of the 54 apps for which testing was attempted, only 46 (25 iOS and 21 Android) could be tested completely for review. As the search took place, 7 apps were removed from their respective app stores and 1 app had updated to require sign up, one of the exclusion criteria, to be used. However, as 41 apps was the minimum sample size needed to determine interrater reliability with 90% assurance, analysis was continued [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        <p>The mean time to complete the MARuL rubric for each app was 8 min (SD 0.69). The 2 reviewers showed completion times ranging from 1 to 25 min (JM) and 1 to 33 min (SG). The median review time for each reviewer was 6.6 min (JM) and 4.1 min (SG). The discussion with the 2 reviewers indicated that in a small number of cases, there were challenges in evaluating the app, including difficulties with installation or using the app, which accounted for the longer evaluation times.</p>
        <p>Cronbach alpha for the overall value was excellent at .96. The categories showed good-to-excellent internal consistency (α=.70-.96). Pearson correlations between the categories were moderate to strong (r range 0.58-0.90). Interrater reliability was also fair to good, with an overall value ICC (2-way) of 0.66 and categories with ICC ranging from 0.45 to 0.75.</p>
        <p>From the internal consistency results, it was determined that the item for <italic>cost</italic> was performing in the reverse of its expected direction and did not add useful information to the usability category. It was removed from the rubric, leaving the usability category with 7 items, and the analyses were rerun. With cost removed, the alpha for the usability category improved from .70 to .82 (see <xref ref-type="table" rid="table3">Table 3</xref> for full details of all categories).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Reliability statistics for the initial version of the Mobile App Rubric for Learning after review of 10 apps.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="270"/>
            <col width="120"/>
            <col width="160"/>
            <col width="110"/>
            <col width="100"/>
            <col width="80"/>
            <thead>
              <tr valign="top">
                <td>Rubric categories</td>
                <td>Intraclass correlation coefficient score<sup>a</sup></td>
                <td>Cronbach α<sup>b</sup></td>
                <td colspan="4">Pearson r<sup>c</sup></td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Teaching and learning</td>
                <td>User centered</td>
                <td>Professional</td>
                <td>Usability</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Teaching and learning</td>
                <td>0.85</td>
                <td>.89</td>
                <td>1.00</td>
                <td>0.91</td>
                <td>0.83</td>
                <td>0.72</td>
              </tr>
              <tr valign="top">
                <td>User centered</td>
                <td>0.78</td>
                <td>.96</td>
                <td>N/A<sup>d</sup></td>
                <td>1.00</td>
                <td>0.72</td>
                <td>0.71</td>
              </tr>
              <tr valign="top">
                <td>Professional</td>
                <td>0.71</td>
                <td>.87</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>1.00</td>
                <td>0.49</td>
              </tr>
              <tr valign="top">
                <td>Usability</td>
                <td>0.71</td>
                <td>.78</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>N/A</td>
                <td>1.00</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>Column 1 presents the interrater reliability scores for each category.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>Column 2 presents the interitem consistency for each category.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>Columns 3 to 6 present the correlations between categories presented in the top right half of the table only.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>N/A: not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Rubric development process. MARuL: Mobile App Rubric for Learning.</p>
          </caption>
          <graphic xlink:href="mhealth_v8i7e18015_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Item statistics by category for final version of the Mobile App Rubric for Learning.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="420"/>
            <col width="220"/>
            <col width="330"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Category and item</td>
                <td>Cronbach α</td>
                <td>Values, mean (SD)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Teaching and learning</bold>
                </td>
                <td>
                  <bold>.91</bold>
                </td>
                <td>
                  <bold>12.82 (6.93)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Purpose</td>
                <td>.75</td>
                <td>2.33 (1.35)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Pedagogy</td>
                <td>.83</td>
                <td>1.97 (1.27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Generates learning</td>
                <td>.90</td>
                <td>1.61 (1.05)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Quantity of information</td>
                <td>.85</td>
                <td>1.80 (1.39)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Relevance to study</td>
                <td>.88</td>
                <td>1.90 (1.04)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Instructional features</td>
                <td>.76</td>
                <td>1.15 (1.21)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>User interactivity</td>
                <td>.57</td>
                <td>1.29 (0.95)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Feedback</td>
                <td>.40</td>
                <td>0.76 (0.88)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Efficiency</td>
                <td>.93</td>
                <td>1.42 (1.16)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>User centered</bold>
                </td>
                <td>
                  <bold>.96</bold>
                </td>
                <td>
                  <bold>10.89 (7.17)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Subjective quality</td>
                <td>.93</td>
                <td>1.24 (1.13)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Satisfaction</td>
                <td>.95</td>
                <td>1.51 (1.23)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Perceived usefulness</td>
                <td>.92</td>
                <td>1.65 (1.15)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Perceived importance</td>
                <td>.90</td>
                <td>1.47 (1.03)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>User Experience</td>
                <td>.81</td>
                <td>2.18 (1.00)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Intention to reuse</td>
                <td>.94</td>
                <td>1.33 (1.22)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Engagement</td>
                <td>.91</td>
                <td>1.52 (1.12)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Professional</bold>
                </td>
                <td>
                  <bold>.74</bold>
                </td>
                <td>
                  <bold>5.94 (3.40)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>In line with standards</td>
                <td>.79</td>
                <td>2.46 (1.02)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Credibility</td>
                <td>.82</td>
                <td>2.94 (1.60)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Information quality</td>
                <td>.83</td>
                <td>1.43 (1.54)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Usability</bold>
                </td>
                <td>
                  <bold>.82</bold>
                </td>
                <td>
                  <bold>16.47 (4.49)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Aesthetics</td>
                <td>.83</td>
                <td>2.47 (0.93)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Functionality</td>
                <td>.70</td>
                <td>3.01 (0.94)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Differentiation</td>
                <td>.76</td>
                <td>1.40 (0.87)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ease of use</td>
                <td>.70</td>
                <td>2.92 (0.80)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Advertisements</td>
                <td>.36</td>
                <td>3.73 (0.86)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Technical specifications</td>
                <td>.61</td>
                <td>1.23 (0.99)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Advantage of app</td>
                <td>.87</td>
                <td>1.71 (1.07)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The final version of the MARuL rubric (version 4) is provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The rigorous development of the MARuL has provided a robust and reliable instrument that can be used by medical students and their teachers to evaluate the value of apps to support just-in-time medical student learning. Potential rubric items were identified from a literature search; and medical students, the end users, identified relevant items via a structured nominal group technique. The preliminary instrument was refined, directed by analysis of internal consistency and interrater reliability, and the final MARuL instrument showed acceptable reliability and usability. Although rubrics for the evaluation of education and health apps are common, they tend to be generic [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. We have developed a specific instrument for evaluating the value of medical education apps for learning.</p>
        <p>We took a multidimensional approach to developing the MARuL in line with guidance from the literature to date [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Where appropriate, we adapted items, with acknowledgment, from extant instruments like the MARS. The MARS is a literature-informed, rigorously developed instrument that is widely used in the evaluation of health apps [<xref ref-type="bibr" rid="ref10">10</xref>]. Our rubric measures the overall value of an app and represents the overall and category scores. This allows evaluation of how the app performs in different domains of value. To our knowledge, the use of multiple items to assess <italic>professional measures</italic> is unique to this rubric; medicine emphasizes the importance of a credible and reliable source of information when informing student learning or patient education. The other 3 categories—<italic>teaching and learning</italic>, <italic>user centered</italic>, and <italic>usability</italic>—are common among evaluative measures [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. These were included in the rubric because students agreed that they address aspects of apps that contribute to valuable student learning. During testing for the internal consistency of each category of the MARuL, cost was observed to be negatively related to the other items in the usability category. That is, apps with a high cost received a low score for the item, as students were less likely to pay for more expensive apps, but a high cost was related to high scores for other usability items. Cost remains an important consideration when choosing an app for student learning, as a lower cost is desirable, for individual students or institutional purchase, but a balance must be maintained between cost and other aspects of usability. Therefore, cost is captured in the basic information about each app (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>), which is also the approach taken in the MARS [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>The strength of this design is our focus on the end users, medical students, as the main source of input in the development of this rubric. This contrasts with most measures that rely on experts in education and technology to develop rubrics for evaluating apps [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Although special expertise is important when developing an accurate and reliable rubric, we believe the user voice is as important, if not more so, to ensure that the rubric is fit for purpose. Using a modified nominal group technique and student participants, we were able to confirm that the current literature surrounding evaluation of apps corresponded to student ideas about what made apps valuable to them in their learning. It also gives the user ownership of the means to evaluate the value of the technology they will be accessing.</p>
        <p>Just-in-time learning is a common practice used by medical students in both the clinical environment and study situations [<xref ref-type="bibr" rid="ref39">39</xref>]. Just-in-time learning especially relates to clinical skills, as medical students are constantly refining their history taking and physical examination skills with peers, in simulated clinical encounters, and with real patients. At an average of 8 min to complete after trialing an app, the MARuL rubric is easy to use and provides a fast evaluation of apps for learning.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>Although care was taken in the development and implementation of this project, there were some potential limitations. One researcher (GT) reviewed the final set of articles generated from the literature search to develop the list of potential evaluation criteria. As many articles were included, this was a large task, and it is possible that potential evaluation terms were overlooked and not extracted. Having two researchers consult the literature would have minimized this possibility; however, the number of terms extracted and their overlap, plus the nominal group’s lack of additions during the initial ranking of terms, gives us confidence that the evaluation terms extracted from the literature search was comprehensive.</p>
        <p>The recruitment of students to the nominal group was by convenience sampling. Research team members asked students to participate in the group. Every effort was made to recruit a variety of students, but the timing of the nominal group in the summer holidays limited the number of students available to take part. A related potential limitation is that students in the nominal group may not have felt confident in rejecting many of the criteria found during the literature review because of concerns around power and hierarchy. However, this was mitigated by having a medical student researcher facilitate the nominal group with another research team member, with no direct effect on student assessment, acting in a support role.</p>
        <p>Finally, there are potential limitations because of the smaller than anticipated number of apps reviewed to complete the reliability testing. However, although eight apps identified in the original search were no longer available at the time of rubric testing, the total number reviewed was still acceptable for reliability analysis.</p>
      </sec>
      <sec>
        <title>Next Steps</title>
        <p>Our next steps for this research include further refinement of the rubric and construct validity testing to compare the MARuL with measures that evaluate health-related apps and education-oriented apps to measure convergent and discriminant validity. We have also adapted the language to create a student version of the rubric and plan to use it to look at the relationship between student evaluation of app value and teacher evaluation of app value. Finally, we believe that with minor changes to the language of some of the items, the rubric can be used with other types of health professional learning apps, for example, apps that focus on student learning of orthopedic skills.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The MARuL is a quick and user-friendly method that teachers can use to evaluate the value of an app for just-in-time learning. Through the inclusion of both experts and student stakeholders in the development process, it should be a robust method for teachers to use when deciding whether to download an app to recommend to students for just-in-time clinical skills learning.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Terms used to evaluate the value of apps and/or mobile technology.</p>
        <media xlink:href="mhealth_v8i7e18015_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 95 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Final version of the Mobile App Rubric for Learning (MARuL).</p>
        <media xlink:href="mhealth_v8i7e18015_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 122 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">e-learning</term>
          <def>
            <p>electronic learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">ICC</term>
          <def>
            <p>intraclass correlation coefficient</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">MARS</term>
          <def>
            <p>Mobile App Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">MARuL</term>
          <def>
            <p>Mobile App Rubric for Learning</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research was supported by a grant from the Otago Medical School Medical Education Research Fund. The authors would like to thank Michael Fouchelle, University of Otago Wellington Medical and Health Sciences Library, for his assistance with the initial literature search. They would like to thank Dr Hemakumar Devan, University of Otago Department of Physiotherapy, for acting as an internal reviewer during the preparation of this manuscript. Aspects of this research were presented at the 2019 Association for Medical Educators in Europe conference.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>TG developed the initial research question and methodology, designed the rubric, completed the app store searches, analyzed the data, and wrote the drafts of the manuscript. GT assisted with the development of the methodology, reviewed the literature, facilitated the nominal group, designed the rubric, completed the app store searches, and edited the manuscript. SG assisted with the development of the methodology, reviewed the apps using the MARuL, assisted in refinement of the MARuL, and edited the manuscript. JM reviewed the apps using the MARuL and assisted in refinement of the MARuL. SR and RG assisted with the development of the methodology and edited the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>KF</given-names>
            </name>
            <name name-style="western">
              <surname>Wharrad</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Watts</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Smartphone and medical related app use among medical students and junior doctors in the United Kingdom (UK): a regional survey</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2012</year>
          <month>10</month>
          <day>30</day>
          <volume>12</volume>
          <fpage>121</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-12-121"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-12-121</pub-id>
          <pub-id pub-id-type="medline">23110712</pub-id>
          <pub-id pub-id-type="pii">1472-6947-12-121</pub-id>
          <pub-id pub-id-type="pmcid">PMC3504572</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>Aungst</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Clauson</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Misra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Husain</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>How to identify, assess and utilise mobile medical applications in clinical practice</article-title>
          <source>Int J Clin Pract</source>
          <year>2014</year>
          <month>02</month>
          <volume>68</volume>
          <issue>2</issue>
          <fpage>155</fpage>
          <lpage>62</lpage>
          <pub-id pub-id-type="doi">10.1111/ijcp.12375</pub-id>
          <pub-id pub-id-type="medline">24460614</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>Wallace</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>'It's on my iPhone': attitudes to the use of mobile computing devices in medical education, a mixed-methods study</article-title>
          <source>BMJ Open</source>
          <year>2012</year>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>-</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://bmjopen.bmj.com/cgi/pmidlookup?view=long&#38;pmid=22923627"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2012-001099</pub-id>
          <pub-id pub-id-type="medline">22923627</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2012-001099</pub-id>
          <pub-id pub-id-type="pmcid">PMC3432838</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wynter</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Burgess</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kalman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Heron</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Bleasel</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Medical students: what educational resources are they using?</article-title>
          <source>BMC Med Educ</source>
          <year>2019</year>
          <month>01</month>
          <day>25</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>36</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmededuc.biomedcentral.com/articles/10.1186/s12909-019-1462-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12909-019-1462-9</pub-id>
          <pub-id pub-id-type="medline">30683084</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12909-019-1462-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC6347772</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Koehler</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Vujovic</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>McMenamin</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Medical students’ use of and attitudes towards medical applications</article-title>
          <source>J Mob Technol Med</source>
          <year>2012</year>
          <month>12</month>
          <day>22</day>
          <volume>1</volume>
          <issue>4</issue>
          <fpage>16</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.7309/jmtm.73</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>Boruff</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Storie</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Mobile devices in medicine: a survey of how medical students, residents, and faculty use smartphones and other mobile devices to find information</article-title>
          <source>J Med Libr Assoc</source>
          <year>2014</year>
          <month>01</month>
          <volume>102</volume>
          <issue>1</issue>
          <fpage>22</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24415916"/>
          </comment>
          <pub-id pub-id-type="doi">10.3163/1536-5050.102.1.006</pub-id>
          <pub-id pub-id-type="medline">24415916</pub-id>
          <pub-id pub-id-type="pii">JMLA-D-13-00018</pub-id>
          <pub-id pub-id-type="pmcid">PMC3878932</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <source>iMedicalApps - Reviews of Medical Apps &#38; Healthcare Technology</source>
          <year>2019</year>
          <access-date>2018-07-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.imedicalapps.com/">https://www.imedicalapps.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dolan</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Top Five Medical Apps at Harvard Medical School</article-title>
          <source>Mobi Health News</source>
          <year>2011</year>
          <access-date>2018-07-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mobihealthnews.com/10745/top-five-medical-apps-at-harvard-medical-school">https://www.mobihealthnews.com/10745/top-five-medical-apps-at-harvard-medical-school</ext-link>
          </comment>
        </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>Scott</surname>
              <given-names>IA</given-names>
            </name>
            <name name-style="western">
              <surname>Scuffham</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Harch</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Borchi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Going digital: a narrative overview of the effects, quality and utility of mobile apps in chronic disease self-management</article-title>
          <source>Aust Health Rev</source>
          <year>2020</year>
          <month>02</month>
          <volume>44</volume>
          <issue>1</issue>
          <fpage>62</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1071/AH18064</pub-id>
          <pub-id pub-id-type="medline">30419185</pub-id>
          <pub-id pub-id-type="pii">AH18064</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>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/1/e27/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id>
          <pub-id pub-id-type="medline">25760773</pub-id>
          <pub-id pub-id-type="pii">v3i1e27</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376132</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>Jin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Development and evaluation of an evaluation tool for healthcare smartphone applications</article-title>
          <source>Telemed J E Health</source>
          <year>2015</year>
          <month>10</month>
          <volume>21</volume>
          <issue>10</issue>
          <fpage>831</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2014.0151</pub-id>
          <pub-id pub-id-type="medline">26431261</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>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Validation of a tool evaluating educational apps for smart education</article-title>
          <source>J Educ Comput Res</source>
          <year>2015</year>
          <month>03</month>
          <day>26</day>
          <volume>52</volume>
          <issue>3</issue>
          <fpage>435</fpage>
          <lpage>50</lpage>
          <pub-id pub-id-type="doi">10.1177/0735633115571923</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>Paglialonga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lugo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Santoro</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>An overview on the emerging area of identification, characterization, and assessment of health apps</article-title>
          <source>J Biomed Inform</source>
          <year>2018</year>
          <month>07</month>
          <volume>83</volume>
          <fpage>97</fpage>
          <lpage>102</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(18)30104-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2018.05.017</pub-id>
          <pub-id pub-id-type="medline">29852318</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(18)30104-7</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>Ok</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>EY</given-names>
            </name>
            <name name-style="western">
              <surname>Bryant</surname>
              <given-names>BR</given-names>
            </name>
          </person-group>
          <article-title>How to find good apps: an evaluation rubric for instructional apps for teaching students with learning disabilities</article-title>
          <source>Interv Sch Clin</source>
          <year>2015</year>
          <month>06</month>
          <day>19</day>
          <volume>51</volume>
          <issue>4</issue>
          <fpage>244</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1177/1053451215589179</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>Papadakis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kalogiannakis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zaranis</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Designing and creating an educational app rubric for preschool teachers</article-title>
          <source>Educ Inf Technol</source>
          <year>2017</year>
          <month>01</month>
          <day>30</day>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>3147</fpage>
          <lpage>65</lpage>
          <pub-id pub-id-type="doi">10.1007/s10639-017-9579-0</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>Hurst</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Evaluating health and wellness mobile applications</article-title>
          <source>J Hosp Librariansh</source>
          <year>2018</year>
          <month>07</month>
          <day>17</day>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>266</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.1080/15323269.2018.1472928</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>Böhme</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>von Osthoff</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Frey</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hübner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Development of a rating tool for mobile cancer apps: information analysis and formal and content-related evaluation of selected cancer apps</article-title>
          <source>J Cancer Educ</source>
          <year>2019</year>
          <month>02</month>
          <volume>34</volume>
          <issue>1</issue>
          <fpage>105</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1007/s13187-017-1273-9</pub-id>
          <pub-id pub-id-type="medline">28819928</pub-id>
          <pub-id pub-id-type="pii">10.1007/s13187-017-1273-9</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>Fiore</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>How to evaluate mobile health applications: a scoping review</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>234</volume>
          <fpage>109</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="medline">28186025</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>Chener</surname>
              <given-names>TS</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fegely</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Santaniello</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>A detailed rubric for assessing the quality of teacher resource apps</article-title>
          <source>J Inf Technol Educ Innov Pract</source>
          <year>2016</year>
          <volume>15</volume>
          <fpage>117</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.28945/3527</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>Eccles</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Wigfield</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>In the mind of the actor: the structure of adolescents' achievement task values and expectancy-related beliefs</article-title>
          <source>Pers Soc Psychol Bull</source>
          <year>2016</year>
          <month>07</month>
          <day>2</day>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>215</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1177/0146167295213003</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>Brandenburg</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Ellinger</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>The future: just-in-time learning expectations and potential implications for human resource development</article-title>
          <source>Adv Dev Hum Resour</source>
          <year>2016</year>
          <month>07</month>
          <day>21</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>308</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1177/1523422303254629</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>Rothman</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>McEvoy</surname>
              <given-names>MD</given-names>
            </name>
          </person-group>
          <article-title>Mobile technology in the perioperative arena: rapid evolution and future disruption</article-title>
          <source>Anesth Analg</source>
          <year>2017</year>
          <month>03</month>
          <volume>124</volume>
          <issue>3</issue>
          <fpage>807</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1213/ANE.0000000000001858</pub-id>
          <pub-id pub-id-type="medline">28151816</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>Jamu</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Lowi-Jones</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Just in time? Using QR codes for multi-professional learning in clinical practice</article-title>
          <source>Nurse Educ Pract</source>
          <year>2016</year>
          <month>07</month>
          <volume>19</volume>
          <fpage>107</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1016/j.nepr.2016.03.007</pub-id>
          <pub-id pub-id-type="medline">27428702</pub-id>
          <pub-id pub-id-type="pii">S1471-5953(16)30009-9</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>HARDEN</surname>
              <given-names>RM</given-names>
            </name>
          </person-group>
          <article-title>AMEE guide no 14: outcome-based education: part 1-an introduction to outcome-based education</article-title>
          <source>Med Teach</source>
          <year>1999</year>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1080/01421599979969</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>Popham</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>What's wrong--and what's right--with rubrics</article-title>
          <source>Educ Lead</source>
          <year>1997</year>
          <volume>55</volume>
          <issue>2</issue>
          <fpage>72</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.ascd.org/publications/educational-leadership/oct97/vol55/num02/What's-Wrong%E2%80%94and-What's-Right%E2%80%94with-Rubrics.aspx"/>
          </comment>
        </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>Ouzzani</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hammady</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fedorowicz</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Elmagarmid</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Rayyan-a web and mobile app for systematic reviews</article-title>
          <source>Syst Rev</source>
          <year>2016</year>
          <month>12</month>
          <day>5</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>210</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://systematicreviewsjournal.biomedcentral.com/articles/10.1186/s13643-016-0384-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13643-016-0384-4</pub-id>
          <pub-id pub-id-type="medline">27919275</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13643-016-0384-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC5139140</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>O'Neil</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Nominal group technique: a process for initiating curriculum development in higher education</article-title>
          <source>Stud High Educ</source>
          <year>2006</year>
          <month>08</month>
          <day>5</day>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>129</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1080/03075078312331378994</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>Humphrey-Murto</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Varpio</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gonsalves</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wood</surname>
              <given-names>TJ</given-names>
            </name>
          </person-group>
          <article-title>Using consensus group methods such as delphi and nominal group in medical education research</article-title>
          <source>Med Teach</source>
          <year>2017</year>
          <month>01</month>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>14</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1080/0142159X.2017.1245856</pub-id>
          <pub-id pub-id-type="medline">27841062</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>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liberati</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
            <collab>PRISMA Group</collab>
          </person-group>
          <article-title>Preferred reporting items for systematic reviews and meta-analyses: the PRISMA statement</article-title>
          <source>Br Med J</source>
          <year>2009</year>
          <month>07</month>
          <day>21</day>
          <volume>339</volume>
          <fpage>b2535</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/cgi/pmidlookup?view=long&#38;pmid=19622551"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.b2535</pub-id>
          <pub-id pub-id-type="medline">19622551</pub-id>
          <pub-id pub-id-type="pmcid">PMC2714657</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>Grainger</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Townsley</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Langlotz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>WJ</given-names>
            </name>
          </person-group>
          <article-title>Apps for people with rheumatoid arthritis to monitor their disease activity: a review of apps for best practice and quality</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2017</year>
          <month>02</month>
          <day>21</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e7</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2017/2/e7/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.6956</pub-id>
          <pub-id pub-id-type="medline">28223263</pub-id>
          <pub-id pub-id-type="pii">v5i2e7</pub-id>
          <pub-id pub-id-type="pmcid">PMC5340922</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <source>Airtable</source>
          <year>2019</year>
          <access-date>2019-01-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.airtable.com/">https://www.airtable.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <source>Qualtrics</source>
          <year>2019</year>
          <access-date>2019-03-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.qualtrics.com/">https://www.qualtrics.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <source>Rstudio: Open Source &#38; Professional Software for Data.</source>
          <year>2019</year>
          <access-date>2019-09-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.rstudio.com/">http://www.rstudio.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gamer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lemon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fellows</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>irr: Various Coefficients of Interrater Reliability and Agreement</article-title>
          <source>The Comprehensive R Archive Network</source>
          <year>2019</year>
          <access-date>2019-09-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://CRAN.R-project.org/package=irr">https://CRAN.R-project.org/package=irr</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Revelle</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>psych: Procedures for Psychological, Psychometric, and Personality Research</article-title>
          <source>The Comprehensive R Archive Network</source>
          <year>2018</year>
          <access-date>2019-09-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://CRAN.R-project.org/package=psych">https://CRAN.R-project.org/package=psych</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wickham</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Reshaping data with the reshape package</article-title>
          <source>J Stat Soft</source>
          <year>2007</year>
          <volume>21</volume>
          <issue>12</issue>
          <fpage>-</fpage>
          <pub-id pub-id-type="doi">10.18637/jss.v021.i12</pub-id>
        </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>Cronbach</surname>
              <given-names>LJ</given-names>
            </name>
          </person-group>
          <article-title>Coefficient alpha and the internal structure of tests</article-title>
          <source>Psychometrika</source>
          <year>1951</year>
          <month>09</month>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>297</fpage>
          <lpage>334</lpage>
          <pub-id pub-id-type="doi">10.1007/BF02310555</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>GY</given-names>
            </name>
          </person-group>
          <article-title>Sample size formulas for estimating intraclass correlation coefficients with precision and assurance</article-title>
          <source>Stat Med</source>
          <year>2012</year>
          <month>12</month>
          <day>20</day>
          <volume>31</volume>
          <issue>29</issue>
          <fpage>3972</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1002/sim.5466</pub-id>
          <pub-id pub-id-type="medline">22764084</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davies</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Rafique</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Vincent</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Fairclough</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Packer</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Vincent</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Haq</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Mobile medical education (MoMEd) - how mobile information resources contribute to learning for undergraduate clinical students - a mixed methods study</article-title>
          <source>BMC Med Educ</source>
          <year>2012</year>
          <month>01</month>
          <day>12</day>
          <volume>12</volume>
          <fpage>1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmededuc.biomedcentral.com/articles/10.1186/1472-6920-12-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6920-12-1</pub-id>
          <pub-id pub-id-type="medline">22240206</pub-id>
          <pub-id pub-id-type="pii">1472-6920-12-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC3317860</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
