<?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 article-type="letter" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</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">v14i1e83564</article-id>
      <article-id pub-id-type="pmid">41481793</article-id>
      <article-id pub-id-type="doi">10.2196/83564</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Letter</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Research Letter</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>AI-Enabled Customer Relationship Management Platforms for Patient Services in Health Care, Early Lessons From Governance, and Program-Level Outcomes</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Benis</surname>
            <given-names>Arriel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Oluwagbade</surname>
            <given-names>Emmanuel</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Okoye</surname>
            <given-names>Augustine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Gupta</surname>
            <given-names>Anup Kant</given-names>
          </name>
          <degrees>MBA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Strategic Management &amp; Leadership</institution>
            <institution>Kelley School of Business</institution>
            <institution>Indiana University Bloomington</institution>
            <addr-line>107 S Indiana Ave</addr-line>
            <addr-line>Bloomington, IN, 47405</addr-line>
            <country>United States</country>
            <phone>1 (812) 855 4848</phone>
            <email>anupgupta8@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0009-2362-9155</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Strategic Management &amp; Leadership</institution>
        <institution>Kelley School of Business</institution>
        <institution>Indiana University Bloomington</institution>
        <addr-line>Bloomington, IN</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Anup Kant Gupta <email>anupgupta8@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>2</day>
        <month>2</month>
        <year>2026</year>
      </pub-date>
      <volume>14</volume>
      <elocation-id>e83564</elocation-id>
      <history>
        <date date-type="received">
          <day>5</day>
          <month>9</month>
          <year>2025</year>
        </date>
        <date date-type="rev-request">
          <day>22</day>
          <month>10</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>18</day>
          <month>11</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>1</day>
          <month>1</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Anup Kant Gupta. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 02.02.2026.</copyright-statement>
      <copyright-year>2026</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (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 Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2026/1/e83564" xlink:type="simple"/>
      <abstract>
        <p>This research letter summarizes early lessons from 4 enterprise implementations of artificial intelligence–enabled customer relationship management platforms in health care and describes governance practices associated with improvements in affordability, adherence, and access at program level.</p>
      </abstract>
      <kwd-group>
        <kwd>artificial intelligence</kwd>
        <kwd>health care customer relationship management</kwd>
        <kwd>salesforce</kwd>
        <kwd>patient affordability</kwd>
        <kwd>patient adherence</kwd>
        <kwd>patient access</kwd>
        <kwd>digital transformation</kwd>
        <kwd>governance</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Health systems continue to face pressure to improve patient outcomes while safeguarding affordability and equitable access [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. Electronic health records support clinical workflows but are not designed for proactive patient outreach or service coordination [<xref ref-type="bibr" rid="ref5">5</xref>]. Artificial intelligence (AI)-enabled customer relationship management (CRM) platforms support automated eligibility checks, outreach, and risk alerts [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. This research letter summarizes early descriptive insights from enterprise implementations of AI-enabled CRM platforms.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Program Selection and Sampling Frame</title>
        <p>A case-informed thematic analysis was conducted across 4 large health care programs. These were the largest CRM-based patient service deployments accessible to the author during this period. Programs were included if they had live AI-enabled CRM workflows for affordability, adherence, or access for at least 12 months. Each program operated independently with different teams, geographies, and product lines. Data reflect operations recorded between January 2019 and March 2024 across the 4 programs. All outcomes reflect a descriptive analysis of the operational dashboards and do not infer causal relationships.</p>
      </sec>
      <sec>
        <title>Data Sources and Definitions</title>
        <p>The following three data sources were used, each aggregated at program level.</p>
        <list list-type="order">
          <list-item>
            <p>Governance documents summarizing decision logs, compliance checkpoints, and escalation patterns.</p>
          </list-item>
          <list-item>
            <p>Stakeholder feedback was gathered through routine program review meetings and documented in standard internal templates.</p>
          </list-item>
          <list-item>
            <p>Internal dashboards tracking key operational indicators. These dashboards were deidentified, contained no patient level data, and were part of routine program monitoring.</p>
          </list-item>
        </list>
        <p>Program level outcome metrics were defined as follows.</p>
        <list list-type="order">
          <list-item>
            <p>Adoption: proportion of active CRM users among provisioned patient service staff within a measurement window.</p>
          </list-item>
          <list-item>
            <p>Affordability efficiency: average time for co-pay or financial assistance verification.</p>
          </list-item>
          <list-item>
            <p>Therapy initiation time: average days between benefit verification and therapy start.</p>
          </list-item>
          <list-item>
            <p>Discontinuation rate: proportion of enrolled patients who stopped therapy during a defined period.</p>
          </list-item>
        </list>
        <p>Baseline values came from preimplementation operations, and follow-up reflected the first stable post launch period. Findings are observational.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This work used only aggregated, deidentified operational dashboards and program documents. No patient-level identifiable data or human subject interaction occurred. Institutional review board approval was not required.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Theme 1: Patient Outcome Alignment and Sponsorship</title>
        <p>Programs that centered goals on patient experience and outcomes such as therapy initiation time or affordability enrollment sustained stronger executive sponsorship. Programs framed as IT upgrades struggled to maintain alignment.</p>
      </sec>
      <sec>
        <title>Theme 2: Continuous Engagement and Adoption</title>
        <p>High adoption correlated with structured engagement of patient service teams and compliance officers. Regular feedback cycles supported adoption above 85% vs below 60% in minimally engaged programs [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      </sec>
      <sec>
        <title>Theme 3: Hybrid Governance Improved Delivery Efficiency</title>
        <p>All 4 programs used a hybrid model that combined Agile sprints with scheduled compliance reviews. This approach reduced backlog resolution time by about 30%. <xref rid="figure1" ref-type="fig">Figure 1</xref> summarizes the governance structure.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Hybrid governance framework for artificial intelligence–enabled customer relationship management. The framework illustrates three concentric layers: (1) patient outcomes (affordability, adherence, access) at the core, (2) agile delivery and stakeholder engagement in the middle layer, and (3) governance and compliance checkpoints in the outer layer. Arrows depict how governance structures enable engagement, which in turn drives improved patient outcomes.</p>
          </caption>
          <graphic xlink:href="medinform_v14i1e83564_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Theme 4: Program-Level Improvements in Affordability, Adherence, and Access</title>
        <p>Changes reflect aggregated dashboards and are not causal. Examples include a reduction in co-pay verification time from 4 days to 3 days (25% faster), a 12% reduction in therapy discontinuation rates, and a shortening of therapy initiation time from 20 days to 17 days (15% faster) (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Program level customer relationship management–enabled improvements.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="120"/>
            <col width="250"/>
            <col width="420"/>
            <col width="210"/>
            <thead>
              <tr valign="top">
                <td>Patient service</td>
                <td>Artificial intelligence functionality</td>
                <td>Outcome</td>
                <td>Example (anonymized)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Affordability</td>
                <td>Automated co-pay verification</td>
                <td>Reduced processing time (4 days to 3 days, a 25% improvement)</td>
                <td>Fortune 10 rollout (USA)</td>
              </tr>
              <tr valign="top">
                <td>Adherence</td>
                <td>Predictive risk alerts</td>
                <td>12% reduction in therapy discontinuation</td>
                <td>Consulting-led program</td>
              </tr>
              <tr valign="top">
                <td>Access</td>
                <td>Automated prior authorization</td>
                <td>Therapy initiation shortened (20 days to 17 days, a 15% improvement)</td>
                <td>Enterprise-wide program</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of Findings</title>
        <p>Across 4 large-scale implementations, AI-enabled CRM platforms supported improvements in affordability, adherence, and access through workflow automation, risk identification, and coordinated service tasks. The most consistent predictors of success were early alignment with patient-centered outcomes, continuous stakeholder engagement, and hybrid governance structures.</p>
      </sec>
      <sec>
        <title>Interpretation and Limitations</title>
        <p>Results reflect aggregated, unaudited operational dashboards and cannot establish causality [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Findings describe program-level improvements observed post implementation and may not generalize to organizations with different scales, regulatory environments, or infrastructure maturity.</p>
      </sec>
      <sec>
        <title>Future Directions</title>
        <p>Future studies should incorporate multi-site comparative designs, validated outcomes, and integration with digital therapeutics and device streams to strengthen evidence for CRM-enabled patient service transformation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CRM</term>
          <def>
            <p>customer relationship management</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <collab>Digital Health and Innovation</collab>
          </person-group>
          <source>Global Strategy on Digital Health 2020–2025</source>
          <year>2025</year>
          <publisher-loc>Geneva, Switzerland</publisher-loc>
          <publisher-name>World Health Organization</publisher-name>
        </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>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>A'Court</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fahy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Beyond adoption, a new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale up, spread, and sustainability of health and care technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e367</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/11/e367/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8775</pub-id>
          <pub-id pub-id-type="medline">29092808</pub-id>
          <pub-id pub-id-type="pii">v19i11e367</pub-id>
          <pub-id pub-id-type="pmcid">PMC5688245</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>Blease</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kaptchuk</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bernstein</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Halamka</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>DesRoches</surname>
              <given-names>CM</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and the future of primary care: exploratory qualitative study of UK general practitioners' views</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>03</month>
          <day>20</day>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>e12802</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/3/e12802/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12802</pub-id>
          <pub-id pub-id-type="medline">30892270</pub-id>
          <pub-id pub-id-type="pii">v21i3e12802</pub-id>
          <pub-id pub-id-type="pmcid">PMC6446158</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>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>High-performance medicine: the convergence of human and artificial intelligence</article-title>
          <source>Nat Med</source>
          <year>2019</year>
          <month>01</month>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>44</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-018-0300-7</pub-id>
          <pub-id pub-id-type="medline">30617339</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-018-0300-7</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>Adler-Milstein</surname>
              <given-names>Julia</given-names>
            </name>
            <name name-style="western">
              <surname>Holmgren</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kralovec</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Worzala</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Searcy</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>Vaishali</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record adoption in US hospitals: the emergence of a digital "advanced use" divide</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>1142</fpage>
          <lpage>1148</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29016973"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocx080</pub-id>
          <pub-id pub-id-type="medline">29016973</pub-id>
          <pub-id pub-id-type="pii">4091350</pub-id>
          <pub-id pub-id-type="pmcid">PMC7651985</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>Davenport</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kalakota</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The potential for artificial intelligence in healthcare</article-title>
          <source>Future Healthc J</source>
          <year>2019</year>
          <month>06</month>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>94</fpage>
          <lpage>98</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2514-6645(24)01059-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.7861/futurehosp.6-2-94</pub-id>
          <pub-id pub-id-type="medline">31363513</pub-id>
          <pub-id pub-id-type="pii">S2514-6645(24)01059-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC6616181</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>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Emanuel</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Predicting the future, big data, machine learning, and clinical medicine</article-title>
          <source>N Engl J Med</source>
          <year>2016</year>
          <month>09</month>
          <day>29</day>
          <volume>375</volume>
          <issue>13</issue>
          <fpage>1216</fpage>
          <lpage>1219</lpage>
          <pub-id pub-id-type="doi">10.1056/nejmp1606181</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in healthcare: past, present and future</article-title>
          <source>Stroke Vasc Neurol</source>
          <year>2017</year>
          <month>12</month>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>230</fpage>
          <lpage>243</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://svn.bmj.com/lookup/pmidlookup?view=long&amp;pmid=29507784"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/svn-2017-000101</pub-id>
          <pub-id pub-id-type="medline">29507784</pub-id>
          <pub-id pub-id-type="pii">svn-2017-000101</pub-id>
          <pub-id pub-id-type="pmcid">PMC5829945</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Cegielski</surname>
              <given-names>Cg</given-names>
            </name>
          </person-group>
          <article-title>An integrated big data analytics-enabled transformation model: Application to health care</article-title>
          <source>Information &amp; Management</source>
          <year>2018</year>
          <month>01</month>
          <volume>55</volume>
          <issue>1</issue>
          <fpage>64</fpage>
          <lpage>79</lpage>
          <pub-id pub-id-type="doi">10.1016/j.im.2017.04.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rumsfeld</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Joynt</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Maddox</surname>
              <given-names>TM</given-names>
            </name>
          </person-group>
          <article-title>Big data analytics to improve cardiovascular care: promise and challenges</article-title>
          <source>Nat Rev Cardiol</source>
          <year>2016</year>
          <month>06</month>
          <volume>13</volume>
          <issue>6</issue>
          <fpage>350</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1038/nrcardio.2016.42</pub-id>
          <pub-id pub-id-type="medline">27009423</pub-id>
          <pub-id pub-id-type="pii">nrcardio.2016.42</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
