<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-journal-title><issn pub-type="epub">1438-8871</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">v27i1e70755</article-id><article-id pub-id-type="doi">10.2196/70755</article-id><article-categories><subj-group subj-group-type="heading"><subject>Viewpoint</subject></subj-group></article-categories><title-group><article-title>Developing Infrastructure to Realize the Value of Patient-Generated Health Data in a Large Integrated Health Care System: The Veterans Health Administration Experience</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Newton</surname><given-names>Terry J</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Shah</surname><given-names>Nilesh</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lewis</surname><given-names>Katherine</given-names></name><degrees>LCSW</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Zocchi</surname><given-names>Mark S</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bixler</surname><given-names>Felicia R</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Etingen</surname><given-names>Bella</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff6">6</xref><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lipschitz</surname><given-names>Jessica M</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Robinson</surname><given-names>Stephanie A</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff10">10</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hogan</surname><given-names>Timothy P</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Shimada</surname><given-names>Stephanie L</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref><xref ref-type="aff" rid="aff11">11</xref></contrib></contrib-group><aff id="aff1"><institution>Office of Connected Care, Veterans Health Administration</institution><addr-line>Washington</addr-line><addr-line>DC</addr-line><country>United States</country></aff><aff id="aff2"><institution>eHealth Partnered Evaluation Initiative, Veterans Affairs Bedford Healthcare System</institution><addr-line>Bedford</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff3"><institution>Center for Health Optimization and Implementation Research (CHOIR), Veterans Affairs Bedford Healthcare System</institution><addr-line>200 Springs Road, Bldg. 70</addr-line><addr-line>Bedford</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff4"><institution>Division of Health Informatics and Implementation Science, Department of Population and Quantitative Health Sciences, University of Massachusetts Medical School</institution><addr-line>Worcester</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff5"><institution>Center of Innovation for Complex Chronic Healthcare (CINCCH), Edward Hines Jr. Veterans Affairs Hospital</institution><addr-line>Hines</addr-line><addr-line>IL</addr-line><country>United States</country></aff><aff id="aff6"><institution>Research and Development Service, Dallas Veterans Affairs Medical Center</institution><addr-line>Dallas</addr-line><addr-line>TX</addr-line><country>United States</country></aff><aff id="aff7"><institution>Peter O&#x2019;Donnell Jr School of Public Health, University of Texas Southwestern Medical Center</institution><addr-line>Dallas</addr-line><addr-line>TX</addr-line><country>United States</country></aff><aff id="aff8"><institution>Department of Psychiatry, Brigham and Women's Hospital</institution><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff9"><institution>Department of Psychiatry, Harvard Medical School</institution><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff10"><institution>The Pulmonary Center, Boston University School of Medicine</institution><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff11"><institution>Department of Health Law, Policy, and Management, Boston University School of Public Health</institution><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Mavragani</surname><given-names>Amaryllis</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Clancy</surname><given-names>Carolyn</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Tiase</surname><given-names>Victoria</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Mark S Zocchi, PhD, Center for Health Optimization and Implementation Research (CHOIR), Veterans Affairs Bedford Healthcare System, 200 Springs Road, Bldg. 70, Bedford, MA, 01730, United States, 1 781-687-4737; <email>Mark.Zocchi@va.gov</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>6</day><month>6</month><year>2025</year></pub-date><volume>27</volume><elocation-id>e70755</elocation-id><history><date date-type="received"><day>13</day><month>01</month><year>2025</year></date><date date-type="rev-recd"><day>28</day><month>03</month><year>2025</year></date><date date-type="accepted"><day>04</day><month>04</month><year>2025</year></date></history><copyright-statement>&#x00A9; Terry J Newton, Nilesh Shah, Katherine Lewis, Mark S Zocchi, Felicia R Bixler, Bella Etingen, Jessica M Lipschitz, Stephanie A Robinson, Timothy P Hogan, Stephanie L Shimada. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 6.6.2025. </copyright-statement><copyright-year>2025</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://www.jmir.org/2025/1/e70755"/><abstract><p>Patient-generated health data (PGHD) encompass health-related information created, recorded, and gathered by patients in their daily lives, and are distinct from data collected in clinical settings. PGHD can offer insight into patients&#x2019; everyday health behaviors and conditions, supporting health management and clinical decision-making. The Veterans Health Administration (VHA) has developed a robust infrastructure to collect PGHD, including automatically collected data from digital sensors and patient-entered data. This effort is guided by comprehensive policy and strategy documents to ensure the secure storage and effective use of PGHD. This paper describes the development and implementation of an infrastructure to support PGHD within the VHA and highlights envisioned clinical and research uses of PGHD to advance health care for US veterans. The PGHD database was built to Fast Healthcare Interoperability Resources standards, facilitating secure data storage and exchange of PGHD. Clinical tools, such as the provider-facing dashboards, make PGHD accessible from the electronic health records. Research and evaluation efforts focus on evaluating PGHD&#x2019;s impact on patient engagement, clinical outcomes, and health care equity. The VHA&#x2019;s comprehensive PGHD infrastructure represents a significant advancement in personalized health care and patient engagement. The integration of PGHD into clinical practice can enhance shared decision-making and self-management, while research and evaluation efforts can address how to maximize the benefits of PGHD for veterans. The VHA&#x2019;s approach sets a benchmark for other US health care systems in leveraging PGHD to achieve the broad aims of enhancing stakeholder health care experiences, improving population health and health equity, and reducing costs.</p></abstract><kwd-group><kwd>patient-generated health data</kwd><kwd>Veterans Health Administration</kwd><kwd>mobile health apps</kwd><kwd>health data interoperability</kwd><kwd>clinical decision-making</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Patient-generated health data (PGHD) are health-related data that are created, recorded, or gathered by patients in their everyday lives. PGHD can be used to promote health and wellness or to help address a health concern [<xref ref-type="bibr" rid="ref1">1</xref>]. PGHD overlap with the related concepts of digital phenotyping and personal sensing but can also include nondigital format data [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. PGHD are distinct from data generated in clinical settings, as they provide insight from patients&#x2019; everyday lives, outside of the health care encounter [<xref ref-type="bibr" rid="ref4">4</xref>]. PGHD often include (but are not limited to) biometric data, symptomatology, and activity levels, and can be collected manually or through digital devices such as wearables (eg, smartwatches), mobile health apps, and Bluetooth-enabled medical devices (eg, blood pressure cuffs). Integrating PGHD into clinical care has the potential to improve outcomes by supporting care delivery processes across the care continuum, including disease prevention and diagnosis, health management, interventions, patient-provider communication, and shared decision-making [<xref ref-type="bibr" rid="ref5">5</xref>]. In addition, PGHD have the potential to empower and engage patients in managing their own health, including engagement in healthy behaviors and monitoring of chronic conditions [<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>The Veterans Health Administration (VHA) Digital Health Office and Office of Connected Care is responsible for the development of an evolving suite of veteran- and health care team&#x2013;facing virtual care tools, many of which support the collection of PGHD. In 2001, the VHA launched the tethered online patient portal, My Health<italic>e</italic>Vet, and later allowed veterans to manually track their personal health data, such as vital measurements, diet, sleep, or physical activity for their own records. In 2014, the VHA launched Annie for Veterans (&#x201C;Annie&#x201D;), a VHA SMS text messaging system modeled after the Florence Simple Telehealth system created by the National Health Service in the United Kingdom [<xref ref-type="bibr" rid="ref7">7</xref>]. Annie sends automated self-care reminders to veterans and allows veterans to send self-entered PGHD to their clinical teams.</p><p>In 2020, the VHA&#x2019;s Office of Connected Care launched a new initiative to expand the VHA&#x2019;s ability to collect PGHD from veterans who want to share their data through home medical devices (eg, digital glucometers) and activity trackers (eg, Fitbit) (Newton and Frisbee, unpublished data, 2020). In May 2023, the Office of Connected Care released the Share My Health Data mobile health app, allowing veterans to sync Bluetooth-enabled medical devices, smartwatch and wearable activity trackers, and third-party mobile health apps (eg, Apple Health) and share the corresponding PGHD with the VHA (<xref ref-type="fig" rid="figure1">Figure 1</xref>). The Share My Health Data app also allows veterans to directly self-enter PGHD, such as body weight, and can sync with continuous glucose monitoring devices. Prior to using the app, veterans must first accept the end-user license agreement and the data collection agreement. The data collection agreement informs the user that the VHA may collect and store any PGHD that the user has agreed to share with the VHA. Consent for the VHA to use a veteran&#x2019;s PGHD includes the purposes for use such as clinical care, veteran population health initiatives, quality improvement efforts, and research.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>The Veterans Health Administration Share My Health Data mobile app&#x2014;settings and daily dashboard screens. VA: Veterans Affairs.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v27i1e70755_fig01.png"/></fig><p>There is great interest, both across VHA and other US health care systems, in harnessing PGHD to reduce costs, improve clinical outcomes and health equity, and enhance stakeholder health care experiences [<xref ref-type="bibr" rid="ref8">8</xref>]. To support these goals, the VHA&#x2019;s Office of Connected Care has developed the PGHD database, where veterans&#x2019; PGHD are stored and transformed into data elements that can be accessed by the VHA health care team members and researchers. The Office of Connected Care aims to support researchers who study PGHD to improve clinical care processes and veteran health outcomes, as well as integrate the collection and use of PGHD within research and evaluation projects to support their aims and objectives [<xref ref-type="bibr" rid="ref1">1</xref>].</p><p>This manuscript describes the technical requirements, infrastructure, unique attributes and limitations, and potential clinical, research, and evaluation uses of the PGHD database as part of the VHA&#x2019;s broader efforts to realize the value of PGHD in advancing health care for US veterans. As the PGHD database evolves and lessons are learned from researchers, field testers, and pilot projects, the goal will be to integrate PGHD into fundamental clinical workflows and build a knowledge base for where integration provides the greatest value.</p></sec><sec id="s2"><title>PGHD Technical Requirements</title><p>Data collected in the PGHD database are guided by a series of VHA policy and strategy documents, the development of which was overseen by the Office of Connected Care [<xref ref-type="bibr" rid="ref9">9</xref>]. These documents provide guidance on key aspects of collecting, storing, and using PGHD within the health care system, including data access and management, clinical workflows, management of anticipated risks, implementation, and evaluation (U.S. Department of Veterans Affairs, unpublished data, 2021) [<xref ref-type="bibr" rid="ref10">10</xref>]. The VHA Directive 6506 defines PGHD as, &#x201C;health data created, recorded or gathered electronically by or from veterans, beneficiaries, or their authorized delegates outside the clinical health care setting to help address a health concern&#x201D; [<xref ref-type="bibr" rid="ref9">9</xref>]. The directive further defines PGHD as either solicited (ie, PGHD that the VHA providers request from veterans) or unsolicited (ie, PGHD that are provided by veterans without a request from the VHA providers) and outlines the VHA&#x2019;s efforts around the use of PGHD as threefold: (1) supporting veterans with self-management; (2) supporting clinical decision-making and care delivery for individual veterans; and (3) supporting data use for health care analytics, including population health, quality improvement, and research. The expectations for provider documentation and for the use of PGHD within the electronic health record are also outlined in VHA Directive 6506.</p><p>The VHA&#x2019;s PGHD database contains data collected from several sources, including VHA mobile apps, third-party mobile health apps, and Bluetooth-enabled digital devices. <xref ref-type="fig" rid="figure2">Figure 2</xref> depicts the data flow from these sources to the end-users of the data. To ensure the standardization across sources, data in the PGHD database go through a Fast Healthcare Interoperability Resources (FHIR)&#x2013;compliant application programming interface (API). The FHIR standard is designed to facilitate the exchange of data between different health care applications by organizing data elements into resources and transmission through an API [<xref ref-type="bibr" rid="ref11">11</xref>]. PGHD obtained through the API are stored in an analytic cloud environment via two processes: one is a direct copy of the FHIR-compliant data (in JavaScript Object Notation [JSON] format); and the other is a normative copy created by an Extract, Transform, and Load data integration process. Once loaded into the Corporate Data Warehouse and the Health Data and Analytics Platform, data can be displayed for viewing by VHA clinicians and staff through the Virtual Care Manager and Clinician Decision Support Consoles, and by veterans through the Share My Health Data App. A parallel copy is loaded on the VHA&#x2019;s Informatics and Computing Infrastructure Workplace servers for operational and research use. Separate data integration and validation processes are applied to other sources, so that these data sources can also be stored in the PGHD database using the same FHIR standard.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>The flow of patient-generated health data (PGHD) in the Veterans Health Administration. CDW: Corporate Data Warehouse; FHIR: Fast Healthcare Interoperability Resources; HDAP: Health Data and Analytics Platform; VA: Veterans Affairs; VINCI: VA Informatics and Computing Infrastructure.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v27i1e70755_fig02.png"/></fig></sec><sec id="s3"><title>PGHD Infrastructure</title><p>A formal PGHD governance structure ensures that data contained in the PGHD database adhere to the FHIR data standard and mappings, and that data are stored securely and in accordance with VHA policy. Rows in the database represent observations of specific PGHD measurements taken over a specific time period, such as the number of steps taken during a calendar day, systolic blood pressure taken at a specific date and time in mm Hg, or total sleep duration in minutes. Data elements in the PGHD are linked to specific patients in the VHA through a unique patient identifier and can be merged with other VHA data sources in the VHA&#x2019;s Corporate Data Warehouse. Across data sources, over 130 million observations of PGHD have been collected from over 25,000 patients in the VHA since May 1, 2023. While the PGHD database contains data from Annie and patient-entered vital signs, most of the observations come from third-party health apps connected via the Share My Health Data App. Share My Health Data allows users to share data collected from health aggregator apps such as Apple Health, fitness trackers such as Fitbit or Garmin, pair over 50 Bluetooth-enabled medical devices, and input patient-entered vitals. The most common types of PGHD are from daily activity summaries (eg, daily steps and distance traveled), exercise, sleep, and vital signs. Recent updates enabling the collection of high-frequency data from digital sensor devices (eg, minute-by-minute heart rate [pulse] data, glucose readings from continuous glucose monitoring devices, etc) will allow even more granular insight into veterans&#x2019; experiences outside the clinical encounter.</p><p>Importantly, PGHD from clinical programs, such as remote home monitoring telehealth, are currently not stored in the PGHD database. These programs are closely monitored by clinicians through established protocols and procedures. Conversely, data contained in the PGHD database are more likely to fall under the category of &#x201C;unsolicited&#x201D; data and will not typically be actively monitored. Providers retain autonomy in determining with their patients when to review unsolicited PGHD and are not responsible for making use of the data unless doing so is specified in the veteran&#x2019;s care plan [<xref ref-type="bibr" rid="ref9">9</xref>].</p></sec><sec id="s4"><title>Unique Attributes and Potential Limitations of Unsolicited PGHD</title><p>Although PGHD can offer valuable insights into patients&#x2019; daily activities, vital signs, and sleep patterns, several limitations of such data must be acknowledged. Wearable digital devices, while improving in precision, often have inconsistencies in data capture due to various factors such as device placement, user adherence, battery life, and other technical issues [<xref ref-type="bibr" rid="ref12">12</xref>]. For example, step counts can vary significantly based on the make, model, and type of device (eg, smartphone vs Bluetooth digital pedometer vs smartwatch), and heart rate measurements can be affected by movement or improper device placement [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Heterogeneity, variability, and data quality are also known challenges with sleep data [<xref ref-type="bibr" rid="ref15">15</xref>].</p><p>Another limitation of PGHD relates to its completeness and representativeness. The data that are in the PGHD database, for example, depend on what are available through an API from third-party digital health companies. Metadata that come from Apple Health may differ from what are available through Garmin or Fitbit. Additionally, not all individuals consistently use their devices and, in some cases, users may make unintentional entry errors (in cases of manual, self-entered PGHD) or intentionally alter data reporting. These behaviors can lead to gaps in data that can affect the continuity and reliability of health monitoring.</p><p>It can also be difficult to determine if a daily summary measurement (eg, daily step count) represents a full or partial day of use. Additionally, individuals who use mobile health apps and digital devices are likely not representative of broader patient populations, as users of mobile apps and digital devices tend to be younger, more health-conscious, and of higher socioeconomic status, or in other cases, have a higher burden of disease and health care needs. These trends can limit the generalizability of research findings generated from PGHD [<xref ref-type="bibr" rid="ref16">16</xref>]. Finally, a key distinction between PGHD from wearables and devices and traditional health care data collected in clinical settings is that PGHD are tied to the device generating the data. As a result, there is some inherent uncertainty regarding the identity of the individual operating the device transmitting PGHD to the VHA.</p><p>Given these limitations, appropriately representing and analyzing PGHD are critical for health systems looking to integrate such data for clinical, research, and evaluation use. The lack of certain metadata from third-party health apps limits the ability to discern between older and newer makes and models of common wearables and other devices. Prior studies on older devices have raised concern about the performance in populations with chronic conditions and mobility issues [<xref ref-type="bibr" rid="ref17">17</xref>]. As such, individuals and providers could become concerned (or reassured) about a patient&#x2019;s status based on unreliable data from an unreliable device. In future iterations of the database, it is possible that more metadata from the third-party health aggregators (eg, make and model) will be available; however, availability will be dependent on what is available through the APIs, and may differ from one device or app to another.</p><p>These limitations necessitate careful consideration when interpreting PGHD and underscore the importance of complementing it with more traditional data obtained during clinical encounters. As a tool for monitoring health and wellness, consistent collection of PGHD can help monitor important trends over time and can help minimize the risk of any one individual data point being inaccurate.</p></sec><sec id="s5"><title>Potential Clinical Uses of the PGHD Database</title><p>The PGHD database establishes the infrastructure necessary to develop tools that support clinical use of PGHD. Currently, patients can view their own PGHD through the Share My Health Data mobile app&#x2019;s daily dashboards and the VHA clinicians can view their patients&#x2019; PGHD through Power BI (Microsoft) clinical dashboards accessed through the VHA&#x2019;s electronic health record and a provider-facing web application called Virtual Care Manager. These provider dashboards do not require additional logins but do require knowledge of where they are located within the electronic health record. These dashboards display PGHD alongside data from the patient&#x2019;s medical record to facilitate the identification of trends and opportunities for clinical intervention. The Patient Generated Vitals and Health Data Dashboard contains tabs for different types of PGHD, such as blood pressure, blood glucose, weight, diet or nutrition, activity, and pulse oximetry data (<xref ref-type="fig" rid="figure3">Figures 3</xref> and <xref ref-type="fig" rid="figure4">4</xref>). The Diabetes Dashboard combines PGHD (blood glucose, blood pressure, weight, nutrition, activity, and blood oxygen levels) with data collected during in-person visits, laboratory results, and active medication information.</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>The Veterans Health Administration&#x2013;Patient Generated Vitals and Health Data Dashboard&#x2014;summary tab. BP: blood pressure; CPRS: computerized patient record system; DOB: date of birth; HgbA1c: hemoglobin A<sub>1c</sub>; MPR: medication possession ratio; PGHD: patient-generated health data.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v27i1e70755_fig03.png"/></fig><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>The Veterans Health Administration&#x2013;Patient Generated Vitals and Health Data Dashboard&#x2014;activity tab. BP: blood pressure; PGHD: patient-generated health data.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v27i1e70755_fig04.png"/></fig><p>The Office of Connected Care is currently conducting pilot tests to assess the usability of PGHD in clinical care and the PGHD clinical dashboards. The pilot tests are designed to identify the level of effort required by veterans to sync and share their medical or activity devices, and to assess how clinical teams are incorporating PGHD into their clinical practice and workflows. Ongoing evaluations of the pilot tests will identify barriers and potential solutions to the integration of PGHD into clinical practice. Although the VHA has not yet committed to a set of metrics to define &#x201C;success&#x201D; for the expansion of PGHD, there is commitment to studying the lessons learned from the ongoing pilot studies to inform targets for growth.</p></sec><sec id="s6"><title>Potential Research and Evaluation Uses for the PGHD Database</title><p>The VHA has identified five priority areas for virtual care research, two of which directly relate to the VHA&#x2019;s PGHD initiatives: (1) identifying implementation strategies to increase patient and clinician adoption of effective virtual care technologies, and (2) examining how best to use PGHD in combination with electronic health record data to generate clinically valuable alerts and predictions for providers [<xref ref-type="bibr" rid="ref18">18</xref>]. The development of the Share My Health Data app and accompanying clinician dashboards will facilitate research and evaluation initiatives aligned with both of these priorities.</p><p>Identifying implementation strategies to increase patient and clinician adoption of effective virtual care technologies marks the beginning of an extensive research and evaluation effort to understand the value of PGHD. Specific areas of interest include the role of PGHD in facilitating patient engagement in treatment or self-management, shared decision-making, and population health management. The VHA&#x2019;s PGHD-related research agenda also focuses on research to inform improvements to PGHD implementation and to evaluate the safety, effectiveness, and health equity of PGHD solutions [<xref ref-type="bibr" rid="ref1">1</xref>]. Examples include studies that engage with clinicians to understand which types of PGHD should be prioritized for clinical use, the evaluation of practice protocols for PGHD, barriers and solutions to the interoperability of PGHD with the electronic health record, solutions to address disparities in access to PGHD, the impact of PGHD on patient outcomes and effectiveness of care, and the most effective ways to integrate PGHD into clinical workflows and decision-making processes.</p><p>The PGHD database can also be leveraged as part of research and evaluation initiatives designed to measure the impact of broader health care interventions. Doing so is critical to examining how best to use PGHD in combination with electronic health record data to generate clinically valuable alerts and predictions. For example, rather than relying on data captured in the electronic health record collected during clinical encounters, the Share My Health Data app can be used to gather real-world data in between clinical encounters to assess the effectiveness of interventions being tested such as continuous glucose monitoring data, digital home blood pressure cuff readings, sleep quality, or daily step counts from wearables.</p><p>The aforementioned research and evaluation priorities represent cutting-edge work in the field of health services research and technology-assisted care. Thus, the advent of the PGHD database represents an avenue to disrupt the field of health care delivery such that clinicians are able to adopt a more personalized and data-informed approach to treatment.</p></sec><sec id="s7" sec-type="discussion"><title>Discussion</title><p>Both within and outside of the VHA, health care systems have been increasingly interested in exploring the potential value of PGHD. As personal digital devices that can seamlessly capture these data have become commonplace, the next era of health care will involve capturing and harnessing these rich data elements in patients&#x2019; day-to-day lives outside of the clinician&#x2019;s office to facilitate delivering care that is informed by each patient&#x2019;s unique digital phenotype. The advent of the Share My Health Data app and accompanying clinician dashboards represent an important step the VHA is taking to be on the cutting edge of this transformation. The extensive collection and thoughtful application of PGHD not only support the individual health journeys of veterans but can also contribute broadly to the efficiency and effectiveness of health care and service delivery.</p><p>The next step of the PGHD initiative at the VHA is focused on research and evaluation to identify how best to integrate PGHD into workflows and find where it provides the most value. The VHA is particularly interested in identifying high-priority clinical use cases for PGHD and understanding implementation strategies to encourage patient and provider adoption. On the provider end, evaluations of attitudes toward PGHD and barriers to integrating PGHD-driven insights into care are needed. On the patient end, work is needed to encourage engagement and better understand expectations around the use of PGHD. Veterans can currently access the PGHD that they share through the Share My Health Data app; plans exist for the development of rules and alerts, and an online platform where veterans can more fully interact with their data. Further, although the Share My Health Data app alerts users that their data may not be regularly monitored by their care teams, veterans may still expect their providers to review data prior to and during clinical appointments or to notify them of any concerns in between appointments. How to effectively communicate to veterans how PGHD will be used by their care teams is necessary to ensure that it aligns with veteran expectations and preferences.</p><p>As the PGHD infrastructure at the VHA evolves, developing and integrating clinical alerts and predictions that make care more proactive and individualized for patients is crucial. Certainly, in the digital phenotyping space, we have seen that important clinical occurrences such as mood episodes can be predicted with this type of PGHD [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>], but we have yet to see the broad implementation of alerts or models of care that leverage these types of data in routine practice.</p><p>The future of health care at the VHA, underpinned by the expansive use of PGHD, looks toward not only achieving the broad goals of enhancing stakeholder experiences, improving population health and health equity, and reducing costs but also setting a benchmark for other US health care systems. The VHA is committed to the broad dissemination of research and operational findings related to the implementation of PGHD across its clinics and facilities nationwide. As the VHA pursues the next step of rollout for the Share My Health Data app, the emphasis will be on establishing clear ethical standards for using this data, identifying and addressing challenges presented by the data itself, and streamlining clinical workflows for implementation success. Already, numerous lessons have been learned that have yielded valuable insights. As the VHA&#x2019;s PGHD infrastructure evolves, the VHA is committed to sharing these lessons broadly, along with accompanying recommendations. The hope is that these lessons will be beneficial for other health care systems and their own efforts to better integrate PGHD into health care delivery.</p></sec></body><back><ack><p>The authors would like to acknowledge the critical contributions of Kevin Troutner, Vincent Catania, and their team members who built and supported the technical infrastructure necessary for the Veterans Health Administration's (VHA) Patient-Generated Health Data Program described in this manuscript. The authors would also like to thank Dr Meredith Josephs for her leadership as executive sponsor of the Veteran Affair's (VA) Patient-Generated Health Data Program. This work was supported by the US Department of Veterans Affairs; Office of Connected Care; and Office of Research and Development, Health Services Research and Development Service, Quality Enhancement Research Initiative Program (PEC 15-470; principal investigator: TPH). The views expressed in this article are those of the authors and do not necessarily reflect the position or policy of the Department of Veterans Affairs or the United States government.</p></ack><notes><sec><title>Data Availability</title><p>The Veterans Health Administration (VHA) patient-generated health data (PGHD) on which this project is based are not permitted to leave the VHA firewall without a data use agreement. This limitation is consistent with other work based on VHA data. However, VHA data are made freely available to investigators behind the Department of Veterans Affairs' firewall with appropriate documentation.</p></sec></notes><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">Annie</term><def><p>Annie for Veterans</p></def></def-item><def-item><term id="abb2">API</term><def><p>application programming interface</p></def></def-item><def-item><term id="abb3">FHIR</term><def><p>Fast Healthcare Interoperability Resources</p></def></def-item><def-item><term id="abb4">JSON</term><def><p>JavaScript Object Notation</p></def></def-item><def-item><term id="abb5">PGHD</term><def><p>patient-generated health data</p></def></def-item><def-item><term id="abb6">VHA</term><def><p>Veterans Health Administration</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nazi</surname><given-names>KM</given-names> </name><name name-style="western"><surname>Newton</surname><given-names>T</given-names> </name><name name-style="western"><surname>Armstrong</surname><given-names>CM</given-names> </name></person-group><article-title>Unleashing the potential for patient-generated health data (PGHD)</article-title><source>J Gen Intern Med</source><year>2024</year><month>02</month><volume>39</volume><issue>Suppl 1</issue><fpage>9</fpage><lpage>13</lpage><pub-id pub-id-type="doi">10.1007/s11606-023-08461-4</pub-id><pub-id pub-id-type="medline">38252246</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mohr</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>M</given-names> </name><name name-style="western"><surname>Schueller</surname><given-names>SM</given-names> </name></person-group><article-title>Personal sensing: understanding mental health using ubiquitous sensors and machine learning</article-title><source>Annu Rev Clin Psychol</source><year>2017</year><month>05</month><day>8</day><volume>13</volume><fpage>23</fpage><lpage>47</lpage><pub-id pub-id-type="doi">10.1146/annurev-clinpsy-032816-044949</pub-id><pub-id pub-id-type="medline">28375728</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>Onnela</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Rauch</surname><given-names>SL</given-names> </name></person-group><article-title>Harnessing smartphone-based digital phenotyping to enhance behavioral and mental health</article-title><source>Neuropsychopharmacology</source><year>2016</year><month>06</month><volume>41</volume><issue>7</issue><fpage>1691</fpage><lpage>1696</lpage><pub-id pub-id-type="doi">10.1038/npp.2016.7</pub-id><pub-id pub-id-type="medline">26818126</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tiase</surname><given-names>VL</given-names> </name><name name-style="western"><surname>Hull</surname><given-names>W</given-names> </name><name name-style="western"><surname>McFarland</surname><given-names>MM</given-names> </name><etal/></person-group><article-title>Patient-generated health data and electronic health record integration: a scoping review</article-title><source>JAMIA Open</source><year>2020</year><month>12</month><volume>3</volume><issue>4</issue><fpage>619</fpage><lpage>627</lpage><pub-id pub-id-type="doi">10.1093/jamiaopen/ooaa052</pub-id><pub-id pub-id-type="medline">33758798</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>Lavallee</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Austin</surname><given-names>E</given-names> </name><etal/></person-group><article-title>mHealth and patient generated health data: stakeholder perspectives on opportunities and barriers for transforming healthcare</article-title><source>Mhealth</source><year>2020</year><volume>6</volume><fpage>8</fpage><pub-id pub-id-type="doi">10.21037/mhealth.2019.09.17</pub-id><pub-id pub-id-type="medline">32190619</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>Alaboud</surname><given-names>K</given-names> </name><name name-style="western"><surname>Shahreen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Islam</surname><given-names>H</given-names> </name><etal/></person-group><article-title>Clinicians&#x2019; perspectives in using patient-generated health data to improve ischemic heart disease management</article-title><source>AMIA Jt Summits Transl Sci Proc</source><year>2022</year><volume>2022</volume><fpage>112</fpage><lpage>119</lpage><pub-id pub-id-type="medline">35854732</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="web"><article-title>From Flo to Annie &#x2013; how Flo is being used in the USA</article-title><source>The Health Foundation</source><access-date>2025-05-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.health.org.uk/article/from-flo-to-annie">https://www.health.org.uk/article/from-flo-to-annie</ext-link></comment></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nundy</surname><given-names>S</given-names> </name><name name-style="western"><surname>Cooper</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Mate</surname><given-names>KS</given-names> </name></person-group><article-title>The quintuple aim for health care improvement: a new imperative to advance health equity</article-title><source>JAMA</source><year>2022</year><month>02</month><day>8</day><volume>327</volume><issue>6</issue><fpage>521</fpage><lpage>522</lpage><pub-id pub-id-type="doi">10.1001/jama.2021.25181</pub-id><pub-id pub-id-type="medline">35061006</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="web"><article-title>Veterans Health Administration VHA Directive 6506 review and use of patient-generated health data under the office of connected care</article-title><source>Department of Veterans Affairs</source><year>2021</year><access-date>2025-05-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.va.gov/vhapublications/ViewPublication.asp?pub_ID=9252">https://www.va.gov/vhapublications/ViewPublication.asp?pub_ID=9252</ext-link></comment></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><article-title>VA Enterprise Cloud &#x2013; Mobile Application Platform (Cloud) Assessing (VAEC-MAP) (173VA005OP2)</article-title><source>Fed Regist</source><year>2021</year><access-date>2025-05-05</access-date><volume>86</volume><issue>213</issue><fpage>61852</fpage><lpage>61855</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://www.govinfo.gov/content/pkg/FR-2021-11-08/pdf/2021-24368.pdf">https://www.govinfo.gov/content/pkg/FR-2021-11-08/pdf/2021-24368.pdf</ext-link></comment></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="web"><article-title>Welcome to FHIR&#x00AE;</article-title><source>HL7 FHIR Release 5</source><access-date>2025-05-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://HL7.org/FHIR">https://HL7.org/FHIR</ext-link></comment></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Canali</surname><given-names>S</given-names> </name><name name-style="western"><surname>Schiaffonati</surname><given-names>V</given-names> </name><name name-style="western"><surname>Aliverti</surname><given-names>A</given-names> </name></person-group><article-title>Challenges and recommendations for wearable devices in digital health: data quality, interoperability, health equity, fairness</article-title><source>PLOS Digit Health</source><year>2022</year><month>10</month><volume>1</volume><issue>10</issue><fpage>e0000104</fpage><pub-id pub-id-type="doi">10.1371/journal.pdig.0000104</pub-id><pub-id pub-id-type="medline">36812619</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bent</surname><given-names>B</given-names> </name><name name-style="western"><surname>Goldstein</surname><given-names>BA</given-names> </name><name name-style="western"><surname>Kibbe</surname><given-names>WA</given-names> </name><name name-style="western"><surname>Dunn</surname><given-names>JP</given-names> </name></person-group><article-title>Investigating sources of inaccuracy in wearable optical heart rate sensors</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><fpage>18</fpage><pub-id pub-id-type="doi">10.1038/s41746-020-0226-6</pub-id><pub-id pub-id-type="medline">32047863</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Angelucci</surname><given-names>A</given-names> </name><name name-style="western"><surname>Canali</surname><given-names>S</given-names> </name><name name-style="western"><surname>Aliverti</surname><given-names>A</given-names> </name></person-group><article-title>Digital technologies for step counting: between promises of reliability and risks of reductionism</article-title><source>Front Digit Health</source><year>2023</year><volume>5</volume><fpage>1330189</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2023.1330189</pub-id><pub-id pub-id-type="medline">38152629</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>Perez-Pozuelo</surname><given-names>I</given-names> </name><name name-style="western"><surname>Zhai</surname><given-names>B</given-names> </name><name name-style="western"><surname>Palotti</surname><given-names>J</given-names> </name><etal/></person-group><article-title>The future of sleep health: a data-driven revolution in sleep science and medicine</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><fpage>42</fpage><pub-id pub-id-type="doi">10.1038/s41746-020-0244-4</pub-id><pub-id pub-id-type="medline">32219183</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>Dobson</surname><given-names>R</given-names> </name><name name-style="western"><surname>Stowell</surname><given-names>M</given-names> </name><name name-style="western"><surname>Warren</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Use of consumer wearables in health research: issues and considerations</article-title><source>J Med Internet Res</source><year>2023</year><month>11</month><day>21</day><volume>25</volume><fpage>e52444</fpage><pub-id pub-id-type="doi">10.2196/52444</pub-id><pub-id pub-id-type="medline">37988147</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>Lauritzen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Mu&#x00F1;oz</surname><given-names>A</given-names> </name><name name-style="western"><surname>Luis Sevillano</surname><given-names>J</given-names> </name><name name-style="western"><surname>Civit</surname><given-names>A</given-names> </name></person-group><article-title>The usefulness of activity trackers in elderly with reduced mobility: a case study</article-title><source>Stud Health Technol Inform</source><year>2013</year><volume>192</volume><fpage>759</fpage><lpage>762</lpage><pub-id pub-id-type="medline">23920659</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hogan</surname><given-names>TP</given-names> </name><name name-style="western"><surname>Sherman</surname><given-names>SE</given-names> </name><name name-style="western"><surname>Dardashti</surname><given-names>N</given-names> </name><name name-style="western"><surname>McMahon</surname><given-names>N</given-names> </name><name name-style="western"><surname>Slightam</surname><given-names>C</given-names> </name><name name-style="western"><surname>Zulman</surname><given-names>DM</given-names> </name></person-group><article-title>Realizing virtual care in VA: supporting the healthcare system&#x2019;s journey towards enhanced access, engagement, and outcomes</article-title><source>J Gen Intern Med</source><year>2024</year><month>02</month><volume>39</volume><issue>Suppl 1</issue><fpage>1</fpage><lpage>4</lpage><pub-id pub-id-type="doi">10.1007/s11606-024-08618-9</pub-id><pub-id pub-id-type="medline">38393612</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cho</surname><given-names>CH</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>T</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>MG</given-names> </name><name name-style="western"><surname>In</surname><given-names>HP</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>L</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>HJ</given-names> </name></person-group><article-title>Mood prediction of patients with mood disorders by machine learning using passive digital phenotypes based on the circadian rhythm: prospective observational cohort study</article-title><source>J Med Internet Res</source><year>2019</year><month>04</month><day>17</day><volume>21</volume><issue>4</issue><fpage>e11029</fpage><pub-id pub-id-type="doi">10.2196/11029</pub-id><pub-id pub-id-type="medline">30994461</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>HJ</given-names> </name><name name-style="western"><surname>Cho</surname><given-names>CH</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Prediction of impending mood episode recurrence using real-time digital phenotypes in major depression and bipolar disorders in South Korea: a prospective nationwide cohort study</article-title><source>Psychol Med</source><year>2023</year><month>09</month><volume>53</volume><issue>12</issue><fpage>5636</fpage><lpage>5644</lpage><pub-id pub-id-type="doi">10.1017/S0033291722002847</pub-id><pub-id pub-id-type="medline">36146953</pub-id></nlm-citation></ref></ref-list></back></article>