<?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">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v7i1e43993</article-id>
      <article-id pub-id-type="pmid">37639303</article-id>
      <article-id pub-id-type="doi">10.2196/43993</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>Outcomes of End-User Testing of a Care Coordination Mobile App With Families of Children With Special Health Care Needs: Simulation Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Girishan Prabhu</surname>
            <given-names>Vishnunarayan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mungoli</surname>
            <given-names>Neelesh</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Wong</surname>
            <given-names>Willis</given-names>
          </name>
          <degrees>MS, MBA, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Duke University School of Medicine</institution>
            <addr-line>40 Duke Medicine Circle</addr-line>
            <addr-line>Durham, NC, 27710</addr-line>
            <country>United States</country>
            <phone>1 4088398691</phone>
            <email>williswong1993@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2694-298X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Ming</surname>
            <given-names>David</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2836-6656</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Pateras</surname>
            <given-names>Sara</given-names>
          </name>
          <degrees>MSW, LCSW</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7154-5222</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Fee</surname>
            <given-names>Casey Holmes</given-names>
          </name>
          <degrees>MS</degrees>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3305-4606</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Coleman</surname>
            <given-names>Cara</given-names>
          </name>
          <degrees>MPH, JD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3572-8467</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Docktor</surname>
            <given-names>Michael</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9540-6382</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Shah</surname>
            <given-names>Nirmish</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7506-0935</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Antonelli</surname>
            <given-names>Richard</given-names>
          </name>
          <degrees>MS, MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6222-6329</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Duke University School of Medicine</institution>
        <addr-line>Durham, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Boston Children's Hospital</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Family Voices</institution>
        <addr-line>Concord, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Accountable Care and Clinical Integration</institution>
        <institution>Boston Children's Hospital</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Pediatrics</institution>
        <institution>Harvard Medical School</institution>
        <addr-line>Boston, MA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Willis Wong <email>williswong1993@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>28</day>
        <month>8</month>
        <year>2023</year>
      </pub-date>
      <volume>7</volume>
      <elocation-id>e43993</elocation-id>
      <history>
        <date date-type="received">
          <day>8</day>
          <month>3</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>24</day>
          <month>5</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>16</day>
          <month>6</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>6</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Willis Wong, David Ming, Sara Pateras, Casey Holmes Fee, Cara Coleman, Michael Docktor, Nirmish Shah, Richard Antonelli. Originally published in JMIR Formative Research (https://formative.jmir.org), 28.08.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2023/1/e43993" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Care for children with special health care needs relies on a network of providers who work to address the medical, behavioral, developmental, educational, social, and economic needs of the child and their family. Family-directed, manually created visual depictions of care team composition (ie, care mapping) and detailed note-taking curated by caregivers (eg, care binders) have been shown to enhance care coordination for families of these children, but they are difficult to implement in clinical settings owing to a lack of integration with electronic health records and limited visibility of family-generated insights for care providers. Caremap is an electronic health record–integrated digital personal health record mobile app designed to integrate the benefits of care mapping and care binders. Currently, there is sparse literature describing end-user participation in the co-design of digital health tools. In this paper, we describe a project that evaluated the usability and proof of concept of the Caremap app through end-user simulation.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to conduct proof-of-concept testing of the Caremap app to coordinate care for children with special health care needs and explore early end-user engagement in simulation testing. The specific aims included engaging end users in app co-design via app simulation, evaluating the usability of the app using validated measures, and exploring user perspectives on how to make further improvements to the app.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Caregivers of children with special health care needs were recruited to participate in a simulation exercise using Caremap to coordinate care for a simulated case of a child with complex medical and behavioral needs. Participants completed a postsimulation questionnaire adapted from 2 validated surveys: the Pediatric Integrated Care Survey (PICS) and the user version of the Mobile Application Rating Scale (uMARS). A key informant interview was also conducted with a liaison to Spanish-speaking families regarding app accessibility for non–English-speaking users.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A Caremap simulation was successfully developed in partnership with families of children with special health care needs. Overall, 38 families recruited from 19 different US states participated in the simulation exercise and completed the survey. The average rating for the survey adapted from the PICS was 4.1 (SD 0.82) out of 5, and the average rating for the adapted uMARS survey was 4 (SD 0.83) out of 5. The highest-rated app feature was the ability to track progress toward short-term, patient- and family-defined care goals.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Internet-based simulation successfully facilitated end-user engagement and feedback for a digital health care coordination app for families of children with special health care needs. The families who completed simulation with Caremap rated it highly across several domains related to care coordination. The simulation study results elucidated key areas for improvement that translated into actionable next steps in app development.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>complex care</kwd>
        <kwd>care coordination</kwd>
        <kwd>digital health tools</kwd>
        <kwd>simulation</kwd>
        <kwd>family-centered design</kwd>
        <kwd>user-centered design</kwd>
        <kwd>participatory design</kwd>
        <kwd>co-design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Care for &#62;13 million children with special health care needs in the United States [<xref ref-type="bibr" rid="ref1">1</xref>] often requires their parents or caregivers to manage information and communication across a complex ecosystem of providers and disciplines located both within and outside of traditional health care settings. These include, but are not limited to, medical, social, behavioral, developmental, educational, home care, and supportive therapy providers [<xref ref-type="bibr" rid="ref2">2</xref>]. The organization of such a complex care team requires effective care coordination, defined as a “patient- and family-centered, assessment-driven, team-based activity designed to meet the needs of children and youth while enhancing the caregiving capabilities of families” [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. Effective care coordination is associated with better outcomes [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]; however, effective care coordination for children with special health care needs is challenging to implement and sustain at a systematic level.</p>
      </sec>
      <sec>
        <title>Promising Tools for Care Coordination for Families of Children With Special Health Care Needs</title>
        <p>Two existing family-centered tools hold promise to facilitate effective care coordination for families of children with special health care needs: care binders and care maps. Care binders are manually organized by many families of children with special health care needs to manage their child’s care and organize relevant health information (history, procedures, and medications) over time and across different health care systems and providers [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Care mapping is a family-driven process that visually highlights a family’s needs, strengths, and interactions among all resources available to support the child (<xref rid="figure1" ref-type="fig">Figure 1</xref> [<xref ref-type="bibr" rid="ref8">8</xref>]) [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Field experience with patients and families has demonstrated that the process of manually creating a hand- or computer-drawn care map can help families of children with special health care needs to prioritize needs, identify service gaps, and facilitate communication with care teams to clarify roles, responsibilities, and desired outcomes [<xref ref-type="bibr" rid="ref11">11</xref>]. Care mapping offers a summative overview of interrelated connections across each child’s multidisciplinary care team members. Coupled with the traditional, family-curated <italic>3-ring binder</italic>, care mapping offers the ability for a family to comprehensively archive health information and family-reported insights over time.</p>
        <p>Although care binders and care mapping can play an important role in coordinating care for children with special health care needs, responsibility falls on families of children with special health care needs to create and maintain these tools for the organization of information across a complex network of services and providers. Furthermore, these tools are not integrated with electronic health records (EHRs). As a result, rich insights from caregivers contained within binders and care maps are difficult to share and largely invisible to health care providers across sectors, ultimately contributing to care fragmentation. Preserving the core benefits of these care coordination tools while concurrently identifying ways to scale up their use by both caregivers and health providers will be important to broaden access to family-driven and family-centered care coordination tools that may help to improve health outcomes for children with special health care needs.</p>
        <p>Digital health tools developed to meet the care coordination needs of families of children with special health care needs [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>] have the potential to support effective care coordination, but there has been limited research to date into the impact of these tools on outcomes. Currently, there is a dearth of measurable experiences of the implementation of digital health tools for children with special health care needs and their families [<xref ref-type="bibr" rid="ref14">14</xref>]. Furthermore, despite growth in digital health tool development, there exist two major obstacles to broader real-world implementation of digital care coordination tools for children with special health care needs: (1) the lack of integration of patient- and family-reported content with EHR data and (2) the inability of health care providers to visualize insights recorded by patients and families over time.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>An example of a hand-drawn care map showing a network of support that contains various entities in health care, legal, financial, education, community, and other resources centered around the patient’s family (reproduced from Lind [<xref ref-type="bibr" rid="ref8">8</xref>] with permission from Cristin Lind).</p>
          </caption>
          <graphic xlink:href="formative_v7i1e43993_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Caremap: A Digital Care Mapping and Health Binder Tool</title>
        <p>A digital personal health record (PHR) is a digital health tool designed to securely access, manage, and share health information. In contrast to paper-based tools such as care mapping and care binders, a digital PHR can (1) access information across multiple health systems, (2) store and share family-reported health insights (eg, care goals and symptoms), and (3) facilitate communication with providers. A digital PHR can leverage Fast Healthcare Interoperability Resources (FHIR) open-data standards to securely access and share data among multiple EHRs and mobile apps [<xref ref-type="bibr" rid="ref15">15</xref>]. FHIR standards are increasingly being adopted by health systems for digital health apps [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>], and the 21st Century Cures Act now requires electronic health information to be shared freely with patients by health provider entities [<xref ref-type="bibr" rid="ref18">18</xref>]. By applying these features to integrate the core benefits of care maps and care binders, digital PHRs are well positioned to facilitate care coordination for children with special health care needs [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>Caremap [<xref ref-type="bibr" rid="ref20">20</xref>] is an FHIR-enabled digital PHR mobile app designed by patients and families in collaboration with digital health developers, clinicians, and researchers to support family-centered care coordination for children with special health care needs and make family-reported longitudinal insights visible to health care providers. After initial development of the Caremap app, it was entered into the US Health Resources and Services Administration Maternal and Child Health Bureau’s Care Coordination for Children with Special Health Care Needs Challenge in 2019, where it was declared the winner by a panel of federal judges and expert advisors who evaluated the app’s potential for impact, sustainability, accessibility, and innovation in care coordination [<xref ref-type="bibr" rid="ref13">13</xref>]. Before further testing in real-world clinical environments, rigorous proof-of-concept testing with families of children with special health care needs was identified as a critical next step.</p>
        <p>User-centered design with early end-user engagement is increasingly recognized as essential for digital health tool development [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. The goal of this study was to co-design with end users a simulation exercise to conduct proof-of-concept testing of the Caremap mobile app to coordinate care for children with special health care needs. The specific aims of the study included (1) engaging end users (ie, families of children with special health care needs) in app co-design using a mobile app simulation, (2) evaluating the usability of the app using validated measures of app usability and care integration, and (3) exploring user perspectives on how to make further improvements to the app using survey feedback and key informant interviews.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Setting and Approach</title>
        <p>This was a prospective study with adults from families with children with special health care needs who participated in an internet-based simulation exercise to test the usability of the Caremap mobile app as part of the Maternal and Child Health Bureau’s Care Coordination for Children with Special Health Care Needs Challenge that sought innovative technology-based solutions to address care coordination for children with special health care needs [<xref ref-type="bibr" rid="ref13">13</xref>]. Usability testing was originally intended to be conducted in person using real EHR data; however, because of the COVID-19 pandemic and the closure of many ambulatory clinics across the United States, the original in-person usability testing plan was adapted into an internet-based simulation exercise based on a simulated patient case.</p>
      </sec>
      <sec>
        <title>Rationale for Simulation as an Approach to End-User Testing</title>
        <p>We selected simulation as the approach for usability testing because of its supporting evidence base as a methodology for user testing [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>] and for the flexibility offered by simulation during the COVID-19 pandemic. Simulation offered a rapid and inexpensive technique to efficiently gather feedback from a broad sample of users from multiple regions, identify pain points, and make critical adjustments early in the app development process.</p>
      </sec>
      <sec>
        <title>Caremap Mobile App Description</title>
        <p>Caremap is an iOS-compatible, FHIR-enabled mobile app that allows users to view and share a summary of their child’s latest health record, set patient- and family-centered care goals, track symptoms, monitor progress toward care goals, and share health data across care entities to ultimately facilitate care coordination across multiple care team members. Caremap includes 2 primary components: a patient-facing mobile app (<xref rid="figure2" ref-type="fig">Figure 2</xref>) and a clinical dashboard (<xref rid="figure3" ref-type="fig">Figure 3</xref>); only the patient-facing mobile app was assessed in this study. A detailed description of the core components of the patient-facing mobile app can be found in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Select screenshots of the Caremap digital personal health record (PHR) mobile app. (A) My Health tab showing PHR features. (B) Track tab showing a sample of trackable family-reported health outcomes for users. (C) Insights tab showing a graphical summary design of user-tracked outcomes. EHR: electronic health record.</p>
          </caption>
          <graphic xlink:href="formative_v7i1e43993_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Interface of the Caremap prototype clinical dashboard to be integrated into an electronic health record showing an overview of the patient’s pertinent health information, including active care goals, allergies, problems list, and medications. The dashboard also shows items flagged by the Caremap mobile app user (yellow flags) for review. In addition, the dashboard summarizes family-reported outcomes for the patient.</p>
          </caption>
          <graphic xlink:href="formative_v7i1e43993_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Participants and Recruitment</title>
        <p>Participants in the simulation exercise for app testing were recruited using convenience sampling via direct email outreach to a national sample of families of children with special health care needs engaged with Family Voices. Family Voices [<xref ref-type="bibr" rid="ref27">27</xref>] is a national family-led organization of friends and families representing, and providing support to, families of children with special health care needs. Family Voices leads a network of state-level organizations that are present in all 50 US states, 5 US territories, and 3 tribal communities. The inclusion criteria for participants in this study were being a family member caring for a child or youth with special health care needs, having access to the requisite technology (iOS-compatible device and internet access), and being able to speak English. Upon the completion of the simulation exercise, participants received compensation consistent with best practice standards for family-engaged research [<xref ref-type="bibr" rid="ref28">28</xref>]. In total, 38 families were recruited into the study. Individual participant-level demographics were not collected to respect the privacy of the families recruited.</p>
      </sec>
      <sec>
        <title>Simulation Exercise Design and Implementation</title>
        <p>The testing version of Caremap included a prepopulated complete record of information about a simulated pediatric patient with complex behavioral and medical needs, including information about medical conditions, medical equipment, patient goals, emergency care, allergies, medications, hospitalizations, and the care team. The cocreation of the simulated patient case and fictitious biopsychosocial elements involved an interdisciplinary team of families of children with special health care needs from Family Voices and the family advisory committee of Boston Children’s Hospital, clinicians and researchers from Boston Children’s Hospital, and an elementary special education teacher. The simulated patient case was reflective of the lived experience of, and real-world challenges faced by, children with special health care needs and their families.</p>
        <p>Between October 12, 2020, and November 2, 2020, the participating families downloaded and used the Caremap mobile app to complete the simulation exercise. For the simulation, participants assumed the role of a family to the simulated child with complex needs, <italic>Isabella</italic> (aged 9 years), and used the Caremap mobile app to review the case details on their personal devices. Participants were invited to familiarize themselves with the Caremap app on their own, after which they were provided with specific activities within Caremap to coordinate <italic>Isabella’s</italic> care in response to simulated real-world scenarios that demonstrate use cases for Caremap’s mobile features. These activities included (1) reviewing <italic>Isabella’s</italic> profile and making additions and changes to health data such as medications and medical history; (2) tracking medication use and symptoms related to <italic>Isabella’s</italic> health, including urination frequency, mood, bowel movements, and sleep over the last 3 days; (3) reviewing simulated data graphics based on previous simulated data entries; and (4) communicating and sharing health data with other care team members via the app. The simulation was designed to take around 30 minutes. Immediately after the simulation experience with the Caremap app, participants were invited to complete a 29-item web-based survey to gather family-reported feedback. Complete simulation instructions for participants can be found in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
      </sec>
      <sec>
        <title>Outcomes or Measures</title>
        <p>Study data were collected and recorded on the web using REDCap (Research Electronic Data Capture; Vanderbilt University) [<xref ref-type="bibr" rid="ref29">29</xref>]. The survey had two parts: (1) an <italic>experience of care integration</italic> instrument containing 12 questions adapted from the Pediatric Integrated Care Survey (PICS), a validated instrument that captures family-reported experiences with care integration (ie, working with their child’s care team to plan, manage, and track their child’s care) [<xref ref-type="bibr" rid="ref30">30</xref>], and (2) a <italic>functionality assessment</italic> instrument containing 17 questions adapted from the user version of the Mobile Application Rating Scale (uMARS) [<xref ref-type="bibr" rid="ref31">31</xref>], a validated tool that assesses mobile app usability. The final study survey items (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>) were adapted by the research team, which included investigators and family partners, and vetted with Family Voices; for example, the PICS question “In the past 12 months, how often have you felt that your child’s care team members thought about the ‘big picture’ when caring for your child, meaning dealing with all of your child’s needs?” was adapted in this study to “Based on your experience using Caremap, how easy or difficult would it be for Isabella’s family to make sure that the ‘big picture’ was taken into account when decisions and recommendations were made about Isabella’s care?” The adapted survey questions were a combination of 5-point Likert scale questions and sliding scale questions rated from 0 to 100. The questions were also grouped into the following themes from the original uMARS instrument: engagement, functionality, aesthetics, information, and subjective quality, as well as perceived impact (not part of the uMARS).</p>
        <p>In addition, participants responded to 3 open-ended questions associated with the <italic>functionality assessment</italic> instrument on app functionality to evaluate their perceived level of understanding of the opportunities in care coordination after the simulation, their confidence in the app’s ability to coordinate care across team members, and their confidence in their own ability to coordinate care. Refer to the full survey in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> for more details.</p>
      </sec>
      <sec>
        <title>Key Informant Interview</title>
        <p>In addition to the user-reported measures of app usability and care integration, a key informant interview was conducted with a liaison to Spanish-speaking families of children with special health care needs at Boston Children’s Hospital to assess the potential benefits and challenges of Caremap regarding advancing health equity, particularly for Spanish-speaking families of children with special health care needs.</p>
      </sec>
      <sec>
        <title>Analysis</title>
        <p>Quantitative data collected from the adapted PICS and uMARS survey were summarized using descriptive statistics. Sliding scale responses were converted to 5-point Likert scores for ease of comparison (eg, scores of 0-20 on the sliding scale=1 out of 5 on the Likert scale). Top and bottom box analysis of the adapted PICS and uMARS survey results was also conducted, where the top box responses represented the 2 most favorable responses for each question (ie, Likert score of 4 or 5) whereas the bottom box responses represented the 2 least favorable responses (ie, Likert score of 1 or 2) [<xref ref-type="bibr" rid="ref32">32</xref>]. Free-response answers from the <italic>functionality assessment</italic> survey were categorized by <italic>constructive</italic> versus <italic>positive</italic> commentary, and thematic analysis was conducted on these responses by 1 reviewer for key themes and verified by 2 other reviewers independently. Insights from the key informant interview were summarized into key learnings and translated directly into actionable steps for app improvements.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>The study was reviewed by the Performance Excellence Group at Boston Children’s Hospital, and it was determined to be exempt from institutional review board review.</p>
      </sec>
      <sec>
        <title>App Security Assessment, Informed Consent, and Participation</title>
        <p>Caremap was reviewed with the Boston Children’s Hospital information security team. The review included a thorough assessment of the overall solution, validation of the data security protections in place, identification of the use of protected health information in the solution by patients and care teams, and vulnerability code scanning for the app. The review resulted in the approval of the app for the limited scope of the simulation study. Protected health information was not used in the simulation, and participants did not have the ability to upload or import personal information into the app during simulation testing. Participants were required to read through, and acknowledge, a consent letter describing the risks and benefits of the simulation study before participating in it. Parent and caregiver participants received US $100 in compensation after the completion of the simulation exercise and all postsimulation surveys.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>Over 1 month, from October 13, 2020, to November 12, 2020, a total of 45 families signed up for the simulation, and 38 (84%) families from 19 states (<xref rid="figure4" ref-type="fig">Figure 4</xref>) completed both the simulation exercise and the survey. On the basis of aggregate internet connectivity data by state, participants spent an average of 34 minutes reviewing the simulated patient’s health information and using the Caremap app during the simulation.</p>
      <fig id="figure4" position="float">
        <label>Figure 4</label>
        <caption>
          <p>Map of participants recruited by US states highlighted in gray.</p>
        </caption>
        <graphic xlink:href="formative_v7i1e43993_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <sec>
        <title>User-Reported Experience of Care Integration and App Functionality</title>
        <p>The survey results from the participants (N=38) based on the <italic>experience of care integration</italic> and <italic>functionality assessment</italic> instruments are summarized in <xref ref-type="table" rid="table1">Tables 1</xref> and <xref ref-type="table" rid="table2">2</xref>. The responses from the <italic>experience of care integration</italic> survey demonstrated an average score of 4.1 (SD 0.82; range 3.8-4.5) out of 5 across all measures (5=very easy and 1=very difficult). Top and bottom box analysis revealed that the most highly rated capabilities included the app’s ability to track progress toward short-term goals (question 9, with a rating of 95% of the responses in the top box) and the ability for families to communicate with care teams regarding concerns about care (question 1, with a rating of 84% of the responses in the top box). The lowest-rated capabilities included the app’s ability to help families think about future care needs to ensure that they are taken care of (question 11, with a rating of 11% of the responses in the bottom box) and the ability to make sure that the <italic>big picture</italic> was considered when decisions were made for care (question 12, with a rating of 11% of the responses in the bottom box).</p>
        <p>The <italic>functionality assessment</italic> survey showed an average app usability rating of 4 (SD 0.83; range 1-5) out of 5, with the perceived impact of the app being the highest-scoring category. Participants also rated the app highest in areas of engagement (out of 5: mean 4.1, SD 0.82; range 2-5), perceived impact (out of 5: mean 4.3, SD 1.18; range 2-5), and information quality (out of 5: mean 4.2, SD 0.70; range 1-5). Participants rated the app lowest in terms of functionality (out of 5: mean 3.8, SD 0.76; range 2-5) and aesthetics (out of 5: mean 3.9, SD 0.81; range 2-5).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Summary of the experience of care integration survey (adapted Pediatric Integrated Care Survey [PICS]).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="110"/>
            <col width="270"/>
            <col width="170"/>
            <col width="180"/>
            <col width="130"/>
            <col width="140"/>
            <thead>
              <tr valign="top">
                <td>Question</td>
                <td>PICS domain<sup>a</sup></td>
                <td>Category score (Likert scale), mean (SD)</td>
                <td>Likert score, mean (SD; range)</td>
                <td>Rating in the top 2 box (%)</td>
                <td>Rating in bottom 2 box (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Care team communication</td>
                <td>4.2 (0.82)</td>
                <td>4.3 (0.85; 2-5)</td>
                <td>84</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Care team communication</td>
                <td>4.2 (0.82)</td>
                <td>4.2 (0.77; 2-5)</td>
                <td>79</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Care team communication</td>
                <td>4.2 (0.82)</td>
                <td>4.1 (0.74; 2-5)</td>
                <td>82</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Care team communication</td>
                <td>4.2 (0.82)</td>
                <td>4.1 (0.91; 2-5)</td>
                <td>71</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Team functioning, performance, quality, and connectivity</td>
                <td>4.1 (0.85)</td>
                <td>4.0 (0.82; 2-5)</td>
                <td>74</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Family impact</td>
                <td>3.9 (0.81)</td>
                <td>4.0 (0.81; 2-5)</td>
                <td>79</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>Family impact</td>
                <td>3.9 (0.81)</td>
                <td>3.9 (0.81; 2-5)</td>
                <td>66</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>Team functioning, performance, quality, and connectivity</td>
                <td>4.1 (0.85)</td>
                <td>4.1 (0.87; 2-5)</td>
                <td>74</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>Care goals and care planning</td>
                <td>4.3 (0.72)</td>
                <td>4.5 (0.60; 3-5)</td>
                <td>95</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>Care goals and care planning</td>
                <td>4.3 (0.72)</td>
                <td>4.1 (0.82; 2-5)</td>
                <td>68</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>Family impact</td>
                <td>3.9 (0.81)</td>
                <td>3.8 (0.81; 2-5)</td>
                <td>76</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>Integrator</td>
                <td>3.8 (1.01)</td>
                <td>3.8 (1.01; 1-5)</td>
                <td>68</td>
                <td>11</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Domains based on the PICS developed by Antonelli et al [<xref ref-type="bibr" rid="ref32">32</xref>].</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Summary of the functionality assessment survey (adapted user version of the Mobile Application Rating Scale [uMARS]).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="110"/>
            <col width="270"/>
            <col width="170"/>
            <col width="180"/>
            <col width="130"/>
            <col width="140"/>
            <thead>
              <tr valign="top">
                <td>Question</td>
                <td>uMARS domain<sup>a</sup></td>
                <td>Category score (Likert scale), mean (SD)</td>
                <td>Likert score, mean (SD; range)</td>
                <td>Rating in top 2 box (%)</td>
                <td>Rating in bottom 2 box (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Engagement</td>
                <td>4.1 (0.82)</td>
                <td>4.4 (0.82; 2-5)</td>
                <td>89</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Engagement</td>
                <td>4.1 (0.82)</td>
                <td>3.8 (0.90; 2-5)</td>
                <td>69</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Engagement</td>
                <td>4.1 (0.82)</td>
                <td>4.3 (0.72; 2-5)</td>
                <td>89</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Functionality</td>
                <td>3.8 (0.76)</td>
                <td>3.7 (0.79; 2-5)</td>
                <td>71</td>
                <td>8</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Functionality</td>
                <td>3.8 (0.76)</td>
                <td>3.9 (0.73; 2-5)</td>
                <td>63</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Aesthetics</td>
                <td>3.9 (0.81)</td>
                <td>4.0 (0.91; 2-5)</td>
                <td>63</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>Aesthetics</td>
                <td>3.9 (0.81)</td>
                <td>3.9 (0.69; 3-5)</td>
                <td>71</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>Information</td>
                <td>4.2 (0.70)</td>
                <td>3.9 (0.80; 1-5)</td>
                <td>82</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>Information</td>
                <td>4.2 (0.70)</td>
                <td>4.2 (0.69; 3-5)</td>
                <td>84</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>Information</td>
                <td>4.2 (0.70)</td>
                <td>4.5 (0.61; 3-5)</td>
                <td>84</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>App subjective quality</td>
                <td>3.9 (1.05)</td>
                <td>4.3 (0.86; 2-5)</td>
                <td>79</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>App subjective quality</td>
                <td>3.9 (1.05)</td>
                <td>4.0 (0.96; 2-5)</td>
                <td>66</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>App subjective quality</td>
                <td>3.9 (1.05)</td>
                <td>3.3 (1.27; 1-5)<sup>b</sup></td>
                <td>26</td>
                <td>13</td>
              </tr>
              <tr valign="top">
                <td>14</td>
                <td>Perceived impact</td>
                <td>4.2 (1.10)</td>
                <td>4.2 (1.09; 1-5)<sup>b</sup></td>
                <td>63</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>15</td>
                <td>Perceived impact</td>
                <td>4.2 (1.10)</td>
                <td>4.2 (1.10; 1-5)<sup>b</sup></td>
                <td>58</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>16</td>
                <td>Perceived impact</td>
                <td>4.2 (1.10)</td>
                <td>4.3 (1.18; 1-5)<sup>b</sup></td>
                <td>68</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>17</td>
                <td>Perceived impact</td>
                <td>4.2 (1.10)</td>
                <td>4.2 (1.02; 2-5)<sup>b</sup></td>
                <td>61</td>
                <td>0</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>Domains based on the user version of the uMARS [<xref ref-type="bibr" rid="ref31">31</xref>].</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>Likert scores converted from a sliding scale score based on the process outlined in the <italic>Methods</italic> section.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Thematic Analysis of Free-Response Commentary by Simulation Participants</title>
        <p>The identified core themes from the thematic analysis along with representative participant comments are shown in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. Positive feedback highlighted that Caremap (1) would make coordinating care easier for families of children with special health care needs, (2) is a convenient way to store and manage health care data, (3) facilitates improved communication with care teams, and (4) promotes shared understanding of care plans that could prevent inadvertent misses by providers and enhance care safety. The positive commentary repeatedly pointed to Caremap’s advantages in creating (1) accessibility for parents with busy schedules, (2) central information storage capability, and (3) capability to share knowledge with both providers and other caregivers, facilitating cross-stakeholder understanding. The constructive feedback indicated a need for integration of the Caremap mobile app with existing secure messaging platforms (eg, patient portals) to streamline communication with providers; participants also provided recommendations for functionality improvements that would enhance the app user experience (UX; eg, direct import of contacts within the device used). Additional constructive feedback highlighted the importance of integrating Caremap into the existing life structure of families of children with special health care needs without creating added burden as well as customizability of app features and UX to fit specific end users’ needs.</p>
        <boxed-text id="box1" position="float">
          <title>Results of thematic analysis and representative commentary.</title>
          <list list-type="bullet">
            <list-item>
              <p>Caremap mobile app makes coordinating care easier for families of children with special health care needs</p>
              <list list-type="bullet">
                <list-item>
                  <p>“This app would make organizing and coordinating my child’s health care needs so much more effective, streamlined and all around easier. As parents if [of] special needs kiddos, our brains are always so full of information...info we need to tell doctors, info we need to tell therapists, Info [info] we think of we [at] 3am and have to then try to remember to tell ours [our] kiddos team are [at] a more reasonable hour in the day...if we had this app, we could click in at 3am and get all of those things off our mind, and the info would be there for the providers to see! Life changing!!”</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Caremap mobile app is a convenient way to store and manage health care data</p>
              <list list-type="bullet">
                <list-item>
                  <p>“Absolutely!! Everything in one user friendly app. It would help when my husband had to take our child to appointments too. He could always be in the loop with what is going on. And have access to the information if he didn’t know an answer to a question.”</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Caremap mobile app facilitates improved communication with care teams</p>
              <list list-type="bullet">
                <list-item>
                  <p>“Often times health professionals do not review charts in advance or don’t understand the bigger picture and the goals we have. This would be an excellent way to share those and encourage parents to speak up without feeling uncomfortable doing so.”</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Caremap mobile app promotes shared understanding of care plans to prevent inadvertent misses and enhance safety</p>
              <list list-type="bullet">
                <list-item>
                  <p>“Coordinating with all of the specialists, Teachers, therapists, etc is one of the most time consuming and frustrating tasks of a special needs parent. Streamlining coordination would safe [save] so much time and prevent so many misunderstandings and inadvertent ‘misses’ in the health care plan.”</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Need for integration of Caremap into existing tools for health care coordination without added burden on end users</p>
              <list list-type="bullet">
                <list-item>
                  <p>“I feel like this is a proof of concept for an app that ultimately could be integrated into something like a secure messaging platform for communicating within the app, allowing all care info to be centralized. I’d like to see something like a ‘visibility’ radio [button] selection for data in the app that would automatically share it to different family/care team members (either using the same app or a compatibly [compatible] platform in a medical facility). As is, it seems like it’s a good activity tracker combined with a limited note taking app and an address book.”</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Need for customizability of app user interface and functionality to match end-user needs</p>
              <list list-type="bullet">
                <list-item>
                  <p>“Thoughts on provider info and communicating with providers: Would be great to import provider contacts directly from phone contacts. Also would be helpful to put in next appt [appointment] with providers. Relationship field: leave a blank option to fill in. It’s impt [important] to know the provider specialty, but there’s too many for a drop down menu. Provider section also needs a blank notes field re: office, parking, nurse info. I find myself strongly preferring to contact our 20+ providers via online portal rather than phone. The feasibility of integrating this app with secure portals is likely a challenge. This limitation would limit my use of the app as a primary communication tool.”</p>
                </list-item>
                <list-item>
                  <p>“Ideas for improving: Add height to opening dashboard, as height and weight are both regularly required for monthly supply orders. Calendar integration would be great. Tracking appts [appointments] is the main reason I keep an online calendar. Would like an option to mark issues/goals/meds [medications] and export those into a checklist to guide an individual provider appt [appointment]. For discharge instructions, I would like to see a photo option, since those are often long and come in paper form.”</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Key Informant Interview</title>
        <p>Learnings from the key informant interview with a liaison to Spanish-speaking families of children with special health care needs at Boston Children’s Hospital are summarized in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>. These key themes were directly translated into actionable next steps for development in partnership with our key informant to enhance equitable access to Caremap.</p>
        <boxed-text id="box2" position="float">
          <title>Key informant interview learnings and next steps.</title>
          <list list-type="bullet">
            <list-item>
              <p>Solution must be accessible to users with limited tech literacy and a tool that supports, not burdens, families</p>
              <list list-type="bullet">
                <list-item>
                  <p>Need user support system onboarding new families; design must be simple to navigate (eg, yes or no answers)</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Platform needs to address cultural uniqueness and the ways families write, read, and absorb information</p>
              <list list-type="bullet">
                <list-item>
                  <p>Build out “About Me” field within Caremap app to account for cultural preferences and attributes</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Health education and information must be presented at comprehension levels that facilitate understanding</p>
              <list list-type="bullet">
                <list-item>
                  <p>Continue to translate and refine Caremap language and prompts to facilitate easy user experience for all families</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Access to child’s medical information (eg, medications and care team member details) would facilitate improved family-provider discussions, especially in emergency department and urgent settings</p>
              <list list-type="bullet">
                <list-item>
                  <p>Must include accessible information that matters most to all families in clinical situations; ensure broad access by making app available on lower-cost devices</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Overview</title>
        <p>This study used simulation to gather formative feedback from a national sample of caregivers of children with special health care needs on the usability and functionality of a digital PHR mobile app, Caremap. The findings reported by users during testing provided support for the proof of concept of the Caremap mobile app as a care coordination tool for children with special health care needs. Our use of simulation as a method for user engagement in the mobile app design process and our description of this novel approach can help inform other research teams leading mobile app development.</p>
      </sec>
      <sec>
        <title>Principal Findings</title>
        <p>Early end-user engagement in health innovations and technology development is highly important [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>], yet there is limited literature describing end-user contributions to digital health tools for children with special health care needs [<xref ref-type="bibr" rid="ref14">14</xref>]. This study was innovative because it demonstrated the feasibility of leveraging an internet-based app simulation co-designed with families of children with special health care needs as a user-centered approach to gather early formative feedback on the usability of a digital care coordination tool for children with special health care needs. Furthermore, this study demonstrated the effectiveness and flexibility provided by a simulation-based research method over traditional recruitment methods to quickly recruit participants nationally (eg, successful recruitment of 38 families of children with special health care needs from 19 states within 6 weeks with a completion rate of 38/45, 84%). Partnership with a family-led community-based group (Family Voices) representative of our target end users was a key strategy that enhanced study recruitment. The success of this user-engaged recruitment strategy can serve as a framework for future studies evaluating digital health tools serving targeted clinical populations such as children with special health care needs.</p>
        <p>Family-reported responses to survey items revealed high ratings from families of children with special health care needs across multiple domains. On the basis of the experience of the care integration survey (adapted PICS), families rated Caremap particularly highly in the <italic>care goals/care planning</italic> domain (out of 5: average 4.3, SD 0.72; range 4.1-4.5, across domain questions) as a tool to help track short-term care goals and as a highly engaging tool for care coordination. This was further reinforced as a strength of the app by the open-ended responses, with positive participant comments on the advantage of the tracking capability in Caremap, revealing how “daily health tracking [has become] a necessity” and that “there’s value in [Caremap]...as it would help me track progress/problems/etc. for appointments.” This demonstrates a real need among families of children with special health care needs for an improved tool to record care goals, symptoms, and medications in real time.</p>
        <p>The adapted PICS responses and open-ended participant comments also revealed that Caremap is promising as a tool to enhance communication with care team members, with high ratings in the <italic>care team communication</italic> domain (out of 5: average 4.2, SD 0.82; range 4.1-4.3). The open-ended participant feedback highlighted the role that asynchronous access to editing patient health data can play in communication with providers; as a participant noted, “if we had this app, we could click in at 3am and get all of those things off our mind, and the info would be there for the providers to see! Life changing!!” Other commentary highlighted ways in which even in-person communication could be enhanced by Caremap, with a participant stating that “often times health professionals...don’t understand the bigger picture and the goals we have. [Caremap] would be an excellent way to share those and encourage parents to speak up without feeling uncomfortable doing so.”</p>
        <p>On the basis of responses to the <italic>functionality assessment</italic> survey questions, the app scored highly in the <italic>information</italic> domain (out of 5: average 4.2, SD 0.70; range 3.9-4.5, across domain questions). Participants rated the app particularly highly as a credible source of information (question 10, out of 5: average 4.5, SD 0.61; range 3-5). This is an exciting early finding, indicating that Caremap and other digital health tools may be a viable way for health professionals to deliver information quickly and efficiently to families of children with special health care needs. In addition, the participants rated the app highly in the <italic>perceived impact</italic> domain (out of 5: average 4.2, SD 1.10; range 4.2-4.3, across domain questions). However, the SDs on these questions were high (1.09-1.18), indicating some discrepancy among participants on the app’s future care coordination value. Given the aforementioned evidence of Caremap’s tracking feature as a core advantage, this may indicate that Caremap can better serve certain populations of children with special health care needs where tracking of symptoms, medications, and goals is of particular importance (eg, children with cystic fibrosis needing to track pulmonary function and bowel movements to tailor medical management).</p>
        <p>Participants rated the app highly in the <italic>engagement</italic> domain (out of 5: average 4.1, SD 0.82; range 3.8-4.4, across domain questions), particularly when asked whether Caremap is an interesting app to use (functionality assessment survey, question 1, out of 5: average 4.4, SD 0.82; range 2-5). Although the simulation was designed to last 30 minutes, it was affirming to see that some participants actively used the app for simulation for &#62;40 minutes. However, these findings are based on a time-limited experience of a simulation exercise and prone to social desirability bias. Long-term app engagement, a common pitfall among digital health tools [<xref ref-type="bibr" rid="ref33">33</xref>], could not be measured. This will need to be further evaluated with future studies.</p>
        <p>Importantly, feedback from the users in our simulation study elucidated key areas for development; for example, the app received a low rating in the adapted PICS (<xref ref-type="table" rid="table1">Table 1</xref>) <italic>integrator</italic> domain (out of 5: average 3.8, SD 1.01; range 1-5) for the ability to help care teams keep the <italic>big picture</italic> in mind for care decision-making, as well as low scores in the <italic>family impact</italic> domain (out of 5: average score 3.9, SD 0.81; range 3.8-4.0) regarding communicating with care team members on high-level issues such as challenges at home for the family in caring for their child. This could suggest that future versions of Caremap need to place a family-written narrative that summarizes key care goals and priorities for the child front and center for the care provider to view. In addition, these low scores may be related to concerns from participants regarding Caremap’s ability to integrate with existing care coordination tools such as MyChart, limiting its use to engagement with care team members. This was compounded with expressed concerns from participants regarding provider engagement, as evidenced by comments such as “for full functionality, [parents] need buy in from the care providers” and “I hesitate it will be easy to contact providers [because] when you call, email or use this app, it can be difficult to get ahold of sometimes and listen and follow through on concerns.” This highlights the need for further trials with health providers using Caremap for care coordination to understand the facilitators and barriers to provider engagement, a key component of digital health tools to improve care coordination [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>In addition, in the <italic>functionality assessment</italic> survey, participants generally rated the app less favorably in functionality (questions 4 and 5) and aesthetics (questions 6 and 7). Particularly low scores on questions 4 and 5 suggest that participants found it difficult to navigate the app’s user interface (UI). The constructive comments by participants included a recommendation for a UI or UX enhancement; for example, a participant expressed the desire for the ability to toggle visibility between shared and unshared data. In addition, several participants commented about experiencing crashes and bugs during the simulation. This feedback suggests that UI and UX development are top of mind for participants, and further development to ensure logical UI and UX and minimal bugs is needed before a full-scale launch. Prioritizing UI and UX will also be highly important moving forward because users are more likely to engage with mobile health apps that match user expectations in terms of app looks and functionality based on popular industry-developed apps [<xref ref-type="bibr" rid="ref34">34</xref>]. Insights from our in-depth interview with the hospital liaison for Spanish-speaking families also highlighted how multicultural and socioeconomic accessibility needs to be a priority moving forward, including building in languages other than English and compatibility with non-iOS devices. This feedback is in line with current studies that suggest that mobile apps are not usable for diverse populations as they are designed currently [<xref ref-type="bibr" rid="ref35">35</xref>]. This emphasizes the need to engage with a more diverse user population in future app co-design and testing to generate broader insights on the barriers to use for non–English-speaking families and families with low-income status, as well as other diverse populations.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>This study has several strengths. First, our user-engaged approach in partnership with Family Voices, a national advocacy group for families of children with special health care needs, allowed for cocreation of a comprehensive and representative patient case for the simulation exercise and facilitated the nationwide recruitment of participants who had lived experience as caregivers for children with special health care needs. Another strength of this study was the use of validated measures to evaluate the participant experience of care integration and mobile app usability with questions adapted from the PICS and uMARS, respectively, improving the app’s comparability with other digital health tools. Finally, the use of a digital simulation was a novel method for user engagement that facilitated flexibility and efficiency in study recruitment during the COVID-19 pandemic.</p>
        <p>Several limitations of this study should also be considered. First, there was a risk of social desirability bias in terms of participants providing positive feedback because they may have perceived a high degree of investment in developing this app by the study team. To mitigate this risk, participants completed the simulation exercise and survey from home without contact from the study team or direct interaction with other study participants to ensure that the responses more likely reflected their own thoughts. In addition, the simulation exercise did not include actual use and testing of FHIR-enabled EHR integration, and issues surrounding integration in real-world implementation could not be elucidated. Furthermore, the Caremap app was only available in English and required an active internet connection at home for testing, which excluded the participation of non-English speakers and individuals without personal devices or internet connectivity. In addition, clinicians’ perceptions of usability were not included in this study, but gathering clinician perspectives will be a key future direction for continued app development. Finally, owing to the time-limited nature of the simulation exercise, long-term user engagement and impact have yet to be elucidated regarding Caremap as a tool for care coordination. However, this study was designed as a proof-of-concept exercise to serve as a foundation for future longitudinal studies that will further elucidate this aspect.</p>
      </sec>
      <sec>
        <title>Next Steps</title>
        <p>Future studies will need to be conducted to evaluate real-world implementation using structured implementation (eg, Consolidated Framework for Implementation Research) and digital health adoption (eg, Technology Acceptance Model) frameworks to understand the elements of patient and provider engagement with Caremap for care coordination. Future testing will need to include real-world testing of FHIR-enabled integration to validate end-to-end connectivity between Caremap users and care providers. This will include conducting prospective trials with health providers who serve children with special health care needs to test the embedded clinician dashboard. Prospective testing will also need to measure the impacts of the Caremap platform on meaningful patient- and family-centered outcomes and include diverse users reflective of the population of families of children with special health care needs. In 2021, the National Quality Forum, with the support of the Centers for Medicare &#38; Medicaid Services, convened a multistakeholder group of patients, advocates, informaticians, and multidisciplinary care providers and subsequently released a set of recommendations on how EHRs can be used to facilitate improved care communications and care coordination, including (1) collecting and sharing standardized data, (2) optimizing EHR usability for patients and caregivers (3) optimizing EHR usability for clinicians, (4) developing novel EHR data elements to improve measurement, and (5) leveraging EHR data to fill measurement gaps [<xref ref-type="bibr" rid="ref19">19</xref>]. Future studies will need to elucidate the ways in which Caremap can be developed to best align with these recommendations [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>This proof-of-concept simulation study has also helped to uncover specific areas for future investigation. Future work will need to include the exploration of improvements to the in-app UX through enhanced app aesthetics; family-centered communication with care providers; and additional app functions such as goal sharing, task delegation, calendar integration, and contingency plan documentation. Enhancing equitable access to this app will be a priority that will be addressed in future development, such as adapting the app for the Android platform, updating in-app language to enhance use for those with limited health literacy, and creating multilingual options (eg, a Spanish version). In future studies, demographic information of study participants should also be collected to examine differences in app engagement among various patient and caregiver subpopulations. As provider engagement will also be key to care coordination through Caremap, future studies will need to include health providers to uncover barriers and facilitators to their app engagement and use.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this paper, we describe the use of simulation to gather end-user feedback on the usability and functionality of Caremap, a novel mobile app designed by families, clinicians, and technology experts to improve care coordination for children with special health care needs. In this simulation exercise, a national sample of caregivers of children with special health care needs rated a novel FHIR-enabled mobile app highly as a usable tool for care coordination with strong potential to improve integrated care across sectors. This user-centered approach offered important insights into usability and proof-of-concept testing before the real-world implementation of the mobile app.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Detailed description of the Caremap mobile app.</p>
        <media xlink:href="formative_v7i1e43993_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 550 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Caremap simulation experience.</p>
        <media xlink:href="formative_v7i1e43993_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 390 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Adapted Pediatric Integrated Care Survey (PICS) and user version of the Mobile Application Rating Scale (uMARS) questionnaire (Caremap simulation feedback survey).</p>
        <media xlink:href="formative_v7i1e43993_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 209 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resources</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">PICS</term>
          <def>
            <p>Pediatric Integrated Care Survey</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">REDCap</term>
          <def>
            <p>Research Electronic Data Capture</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">UI</term>
          <def>
            <p>user interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">uMARS</term>
          <def>
            <p>user version of the Mobile Application Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">UX</term>
          <def>
            <p>user experience</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors wish to thank Sarah Gonzales, Duke Research Coordinator; Isabelle Sico, Duke Research Coordinator; Christopher Lunsford, Doctor of Medicine, Duke Neurodevelopmental Pediatrics; Joan Jasien, Doctor of Medicine, Duke Neurodevelopmental Pediatrics; Nitin Gujral, Master of Business Administration, Caremap developer; and Cristin Lind, Caremap contributor. DM’s contributions were supported by the National Heart, Lung, and Blood Institute of the National Institutes of Health (K12HL13830). Caremap was refined and tested as a result of funding support from the Maternal and Child Health Bureau of the Health Resources and Services Administration after its successful participation in the bureau’s Care Coordinate for Children with Special Health Care Needs Grand Challenge [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The data sets generated and analyzed during this study are available from the corresponding author on reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>RA, DM, CC, and CHF were responsible for study conception. RA, DM, SP, CHF, and CC were responsible for study design. CHF (lead), SP, RA, and CC were responsible for simulation design. CHF, SP, and CC were responsible for data collection. CHF, SP, WW, and RA analyzed and interpreted the results. WW, DM, RA, SP, CHF, CC, NS, and MD were responsible for draft manuscript preparation. All authors reviewed the results and approved the final version of the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>DM, RA, and MD collaborated on the development of the Caremap mobile app and technology used in this study. All other authors declare no other conflicts of interest.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>Children with special health care needs</article-title>
          <source>Health Resources and Services Administration’s (HRSA) Maternal and Child Health Bureau (MCHB)</source>
          <year>2020</year>
          <month>7</month>
          <access-date>2022-05-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mchb.hrsa.gov/sites/default/files/mchb/programs-impact/nsch-cshcn-data-brief.pdf">https://mchb.hrsa.gov/sites/default/files/mchb/programs-impact/nsch-cshcn-data-brief.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Council on Children with DisabilitiesMedical Home Implementation Project Advisory Committee</collab>
          </person-group>
          <article-title>Patient- and family-centered care coordination: a framework for integrating care for children and youth across multiple systems</article-title>
          <source>Pediatrics</source>
          <year>2014</year>
          <month>05</month>
          <day>28</day>
          <volume>133</volume>
          <issue>5</issue>
          <fpage>e1451</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1542/peds.2014-0318</pub-id>
          <pub-id pub-id-type="medline">24777209</pub-id>
          <pub-id pub-id-type="pii">peds.2014-0318</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>Kuo</surname>
              <given-names>DZ</given-names>
            </name>
            <name name-style="western">
              <surname>McAllister</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Rossignol</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Turchi</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Stille</surname>
              <given-names>CJ</given-names>
            </name>
          </person-group>
          <article-title>Care coordination for children with medical complexity: whose care is it, anyway?</article-title>
          <source>Pediatrics</source>
          <year>2018</year>
          <month>03</month>
          <volume>141</volume>
          <issue>Suppl 3</issue>
          <fpage>S224</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1542/peds.2017-1284G</pub-id>
          <pub-id pub-id-type="medline">29496973</pub-id>
          <pub-id pub-id-type="pii">peds.2017-1284G</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>Coller</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ehlenbach</surname>
              <given-names>ML</given-names>
            </name>
          </person-group>
          <article-title>Making time to coordinate care for children with medical complexity</article-title>
          <source>Pediatrics</source>
          <year>2019</year>
          <month>01</month>
          <volume>143</volume>
          <issue>1</issue>
          <fpage>e20182958</fpage>
          <pub-id pub-id-type="doi">10.1542/peds.2018-2958</pub-id>
          <pub-id pub-id-type="medline">30584058</pub-id>
          <pub-id pub-id-type="pii">peds.2018-2958</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>Allshouse</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Comeau</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rodgers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wells</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Families of children with medical complexity: a view from the front lines</article-title>
          <source>Pediatrics</source>
          <year>2018</year>
          <month>03</month>
          <day>01</day>
          <volume>141</volume>
          <issue>Suppl 3</issue>
          <fpage>S195</fpage>
          <lpage>201</lpage>
          <pub-id pub-id-type="doi">10.1542/peds.2017-1284D</pub-id>
          <pub-id pub-id-type="medline">29496970</pub-id>
          <pub-id pub-id-type="pii">peds.2017-1284D</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>McAllister</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Keehn</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Rodgers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lock</surname>
              <given-names>TM</given-names>
            </name>
          </person-group>
          <article-title>Care coordination using a shared plan of care approach: from model to practice</article-title>
          <source>J Pediatr Nurs</source>
          <year>2018</year>
          <month>11</month>
          <volume>43</volume>
          <fpage>88</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.1016/j.pedn.2018.09.009</pub-id>
          <pub-id pub-id-type="medline">30473161</pub-id>
          <pub-id pub-id-type="pii">S0882-5963(18)30109-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Klitzner</surname>
              <given-names>TS</given-names>
            </name>
            <name name-style="western">
              <surname>Rabbitt</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>R-K</given-names>
            </name>
          </person-group>
          <article-title>Benefits of care coordination for children with complex disease: a pilot medical home project in a resident teaching clinic</article-title>
          <source>J Pediatr</source>
          <year>2010</year>
          <month>06</month>
          <volume>156</volume>
          <issue>6</issue>
          <fpage>1006</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jpeds.2009.12.012</pub-id>
          <pub-id pub-id-type="medline">20223482</pub-id>
          <pub-id pub-id-type="pii">S0022-3476(09)01240-2</pub-id>
        </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>Lind</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Home page</article-title>
          <source>Cristin Lind: Reflections on Health, Parenting and Leadership</source>
          <access-date>2023-07-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cristinlind.com/">https://cristinlind.com/</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>Adams</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nicholas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mahant</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Weiser</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kanani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Boydell</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Care maps and care plans for children with medical complexity</article-title>
          <source>Child Care Health Dev</source>
          <year>2019</year>
          <month>01</month>
          <volume>45</volume>
          <issue>1</issue>
          <fpage>104</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1111/cch.12632</pub-id>
          <pub-id pub-id-type="medline">30462842</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antonelli</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Lind</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Care mapping: a how-to guide for patients and families</article-title>
          <source>Boston Children’s Hospital</source>
          <access-date>2022-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.childrenshospital.org/sites/default/files/2022-04/integrated-care-mapping-families.pdf">https://www.childrenshospital.org/sites/default/files/2022-04/integrated-care-mapping-families.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antonelli</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Lind</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Care mapping: an innovative tool and process to support family-centered, comprehensive care coordination</article-title>
          <source>Proceedings of the Annual Primary Care Innovation Conference of the Harvard Medical School Primary Care Center</source>
          <year>2012</year>
          <conf-name>Annual Primary Care Innovation Conference of the Harvard Medical School Primary Care Center</conf-name>
          <conf-date>October, 2012</conf-date>
          <conf-loc>Boston, MA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.childrenshospital.org/integrated-care/care-mapping"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>Digital health products for complex populations</article-title>
          <source>Center for Health Care Strategies</source>
          <access-date>2022-11-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.chcs.org/digital-health-products-complex-populations/">https://www.chcs.org/digital-health-products-complex-populations/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <article-title>Care coordination for CSHCN challenge</article-title>
          <source>Health Resources and Services Administration’s Maternal &#38; Child Health</source>
          <access-date>2022-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mchbgrandchallenges.hrsa.gov/challenges/care-coordination-cshcn">https://mchbgrandchallenges.hrsa.gov/challenges/care-coordination-cshcn</ext-link>
          </comment>
        </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>Bird</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ouellette</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hopkins</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>McGillion</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Carter</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Use of synchronous digital health technologies for the care of children with special health care needs and their families: scoping review</article-title>
          <source>JMIR Pediatr Parent</source>
          <year>2019</year>
          <month>11</month>
          <day>21</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e15106</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pediatrics.jmir.org/2019/2/e15106/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15106</pub-id>
          <pub-id pub-id-type="medline">31750840</pub-id>
          <pub-id pub-id-type="pii">v2i2e15106</pub-id>
          <pub-id pub-id-type="pmcid">PMC6895870</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>Saripalle</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Runyan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Using HL7 FHIR to achieve interoperability in patient health record</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <month>06</month>
          <volume>94</volume>
          <fpage>103188</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30106-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103188</pub-id>
          <pub-id pub-id-type="medline">31063828</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30106-6</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>Mandel</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Kreda</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Kohane</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Ramoni</surname>
              <given-names>RB</given-names>
            </name>
          </person-group>
          <article-title>SMART on FHIR: a standards-based, interoperable apps platform for electronic health records</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>09</month>
          <volume>23</volume>
          <issue>5</issue>
          <fpage>899</fpage>
          <lpage>908</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26911829"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv189</pub-id>
          <pub-id pub-id-type="medline">26911829</pub-id>
          <pub-id pub-id-type="pii">ocv189</pub-id>
          <pub-id pub-id-type="pmcid">PMC4997036</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>Bloomfield</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Polo-Wood</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Mandel</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>Opening the Duke electronic health record to apps: implementing SMART on FHIR</article-title>
          <source>Int J Med Inform</source>
          <year>2017</year>
          <month>03</month>
          <volume>99</volume>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2016.12.005</pub-id>
          <pub-id pub-id-type="medline">28118917</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(16)30273-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dworkowitz</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Provider obligations for patient portals under the 21st century cures act</article-title>
          <source>Health Affairs Forefront</source>
          <year>2022</year>
          <month>5</month>
          <day>16</day>
          <access-date>2023-01-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthaffairs.org/content/forefront/provider-obligations-patient-portals-under-21st-century-cures-act">https://www.healthaffairs.org/content/forefront/provider-obligations-patient-portals-under-21st-century-cures-act</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>Leveraging electronic health record EHR-sourced measures to improve care communication and coordination - shortened final recommendations report</article-title>
          <source>National Quality Forum</source>
          <year>2022</year>
          <month>9</month>
          <access-date>2023-06-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/346vkbb2">https://tinyurl.com/346vkbb2</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <article-title>Caremap homepage</article-title>
          <source>Caremap</source>
          <access-date>2022-07-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://caremap.health/">http://caremap.health/</ext-link>
          </comment>
        </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>Erwin</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Redesigning healthcare to fit with people</article-title>
          <source>BMJ</source>
          <year>2016</year>
          <month>08</month>
          <day>23</day>
          <volume>354</volume>
          <fpage>i4536</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.i4536</pub-id>
          <pub-id pub-id-type="medline">27553644</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>Thomson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Brouwers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Damman</surname>
              <given-names>OC</given-names>
            </name>
            <name name-style="western">
              <surname>de Bruijne</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Timmermans</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Melles</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How health care professionals evaluate a digital intervention to improve medication adherence: qualitative exploratory study</article-title>
          <source>JMIR Hum Factors</source>
          <year>2018</year>
          <month>02</month>
          <day>20</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>e7</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2018/1/e7/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/humanfactors.8948</pub-id>
          <pub-id pub-id-type="medline">29463494</pub-id>
          <pub-id pub-id-type="pii">v5i1e7</pub-id>
          <pub-id pub-id-type="pmcid">PMC5840481</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>Farao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Malila</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Conrad</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mutsvangwa</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rangaka</surname>
              <given-names>MX</given-names>
            </name>
            <name name-style="western">
              <surname>Douglas</surname>
              <given-names>TS</given-names>
            </name>
          </person-group>
          <article-title>A user-centred design framework for mHealth</article-title>
          <source>PLoS One</source>
          <year>2020</year>
          <month>8</month>
          <day>19</day>
          <volume>15</volume>
          <issue>8</issue>
          <fpage>e0237910</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0237910"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0237910</pub-id>
          <pub-id pub-id-type="medline">32813711</pub-id>
          <pub-id pub-id-type="pii">PONE-D-20-01209</pub-id>
          <pub-id pub-id-type="pmcid">PMC7444488</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>Clemensen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Larsen</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Kyng</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkevold</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Participatory design in health sciences: using cooperative experimental methods in developing health services and computer technology</article-title>
          <source>Qual Health Res</source>
          <year>2007</year>
          <month>01</month>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>122</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1177/1049732306293664</pub-id>
          <pub-id pub-id-type="medline">17170250</pub-id>
          <pub-id pub-id-type="pii">17/1/122</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>Kushniruk</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nohr</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Borycki</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>From usability testing to clinical simulations: bringing context into the design and evaluation of usable and safe health information technologies. Contribution of the IMIA human factors engineering for healthcare informatics working group</article-title>
          <source>Yearb Med Inform</source>
          <year>2013</year>
          <volume>8</volume>
          <fpage>78</fpage>
          <lpage>85</lpage>
          <pub-id pub-id-type="medline">23974552</pub-id>
          <pub-id pub-id-type="pii">me13010078</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alwashmi</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Hawboldt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fetters</surname>
              <given-names>MD</given-names>
            </name>
          </person-group>
          <article-title>The iterative convergent design for mobile health usability testing: mixed methods approach</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>04</month>
          <day>26</day>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>e11656</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/4/e11656/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11656</pub-id>
          <pub-id pub-id-type="medline">31025951</pub-id>
          <pub-id pub-id-type="pii">v7i4e11656</pub-id>
          <pub-id pub-id-type="pmcid">PMC6658163</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <article-title>Family voices homepage</article-title>
          <source>Family Voices</source>
          <access-date>2022-10-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://familyvoices.org/">https://familyvoices.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shelton</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hoover</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Allshouse</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <source>Children and Youth with Special Health Care Needs Research Network (CYSHCNet)</source>
          <year>2019</year>
          <access-date>2023-03-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cyshcnet.org/wp-content/uploads/2019/08/Standard-of-Compensation-Final-for-Researchers-1.pdf">https://cyshcnet.org/wp-content/uploads/2019/08/Standard-of-Compensation-Final-for-Researchers-1.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thielke</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Conde</surname>
              <given-names>JG</given-names>
            </name>
          </person-group>
          <article-title>Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title>
          <source>J Biomed Inform</source>
          <year>2009</year>
          <month>04</month>
          <volume>42</volume>
          <issue>2</issue>
          <fpage>377</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(08)00122-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id>
          <pub-id pub-id-type="medline">18929686</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(08)00122-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC2700030</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>Ziniel</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>HN</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Singer</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Antonelli</surname>
              <given-names>RC</given-names>
            </name>
          </person-group>
          <article-title>Validation of a parent-reported experience measure of integrated care</article-title>
          <source>Pediatrics</source>
          <year>2016</year>
          <month>12</month>
          <day>30</day>
          <volume>138</volume>
          <issue>6</issue>
          <fpage>e20160676</fpage>
          <pub-id pub-id-type="doi">10.1542/peds.2016-0676</pub-id>
          <pub-id pub-id-type="medline">27940672</pub-id>
          <pub-id pub-id-type="pii">peds.2016-0676</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stoyanov</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Hides</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kavanagh</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Development and validation of the user version of the mobile application rating scale (uMARS)</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2016</year>
          <month>06</month>
          <day>10</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e72</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2016/2/e72/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.5849</pub-id>
          <pub-id pub-id-type="medline">27287964</pub-id>
          <pub-id pub-id-type="pii">v4i2e72</pub-id>
          <pub-id pub-id-type="pmcid">PMC4920963</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antonelli</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ziniel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Pediatric integrated care survey 1.0 user manual</article-title>
          <source>Boston Children’s Hospital</source>
          <access-date>2023-06-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.childrenshospital.org/sites/default/files/2022-04/integrated-care-pics-user-manual.pdf">https://www.childrenshospital.org/sites/default/files/2022-04/integrated-care-pics-user-manual.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jakob</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Harperink</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rudolf</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Fleisch</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Haug</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mair</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Salamanca-Sanabria</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing adherence to mHealth apps for prevention or management of noncommunicable diseases: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>05</month>
          <day>25</day>
          <volume>24</volume>
          <issue>5</issue>
          <fpage>e35371</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/5/e35371/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/35371</pub-id>
          <pub-id pub-id-type="medline">35612886</pub-id>
          <pub-id pub-id-type="pii">v24i5e35371</pub-id>
          <pub-id pub-id-type="pmcid">PMC9178451</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lazard</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Babwah Brennen</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Belina</surname>
              <given-names>SP</given-names>
            </name>
          </person-group>
          <article-title>App designs and interactive features to increase mHealth adoption: user expectation survey and experiment</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2021</year>
          <month>11</month>
          <day>04</day>
          <volume>9</volume>
          <issue>11</issue>
          <fpage>e29815</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/11/e29815/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/29815</pub-id>
          <pub-id pub-id-type="medline">34734829</pub-id>
          <pub-id pub-id-type="pii">v9i11e29815</pub-id>
          <pub-id pub-id-type="pmcid">PMC8603164</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sarkar</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Gourley</surname>
              <given-names>GI</given-names>
            </name>
            <name name-style="western">
              <surname>Lyles</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Tieu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Clarity</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Newmark</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Usability of commercially available mobile applications for diverse patients</article-title>
          <source>J Gen Intern Med</source>
          <year>2016</year>
          <month>12</month>
          <volume>31</volume>
          <issue>12</issue>
          <fpage>1417</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27418347"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-016-3771-6</pub-id>
          <pub-id pub-id-type="medline">27418347</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-016-3771-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5130945</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
