<?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="letter" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v11i1e46046</article-id>
      <article-id pub-id-type="pmid">37040464</article-id>
      <article-id pub-id-type="doi">10.2196/46046</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>Uptake of Remote Physiologic Monitoring in the US Medicare Program: A Serial Cross-sectional Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Buis</surname>
            <given-names>Lorraine</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Fletcher</surname>
            <given-names>Dana</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Sharp</surname>
            <given-names>John</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Curtis</surname>
            <given-names>Jeffrey R</given-names>
          </name>
          <degrees>MD, MS, MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Division of Clinical Immunology and Rheumatology</institution>
            <institution>University of Alabama at Birmingham</institution>
            <addr-line>1825 University Blvd</addr-line>
            <addr-line>Shelby 121H</addr-line>
            <addr-line>Birmingham, AL, 35233</addr-line>
            <country>United States</country>
            <phone>1 2059370585</phone>
            <email>jcurtis@uab.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8907-8976</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Willig</surname>
            <given-names>James</given-names>
          </name>
          <degrees>MD, MSPH</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7462-368X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Division of Clinical Immunology and Rheumatology</institution>
        <institution>University of Alabama at Birmingham</institution>
        <addr-line>Birmingham, AL</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Division of Infectious Diseases</institution>
        <institution>University of Alabama at Birmingham</institution>
        <addr-line>Birmingham, AL</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Jeffrey R Curtis <email>jcurtis@uab.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>1</day>
        <month>5</month>
        <year>2023</year>
      </pub-date>
      <volume>11</volume>
      <elocation-id>e46046</elocation-id>
      <history>
        <date date-type="received">
          <day>27</day>
          <month>1</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>31</day>
          <month>3</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>4</day>
          <month>4</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>10</day>
          <month>4</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Jeffrey R Curtis, James Willig. Originally published in JMIR mHealth and uHealth (https://mhealth.jmir.org), 01.05.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 mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on https://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://mhealth.jmir.org/2023/1/e46046" xlink:type="simple"/>
      <kwd-group>
        <kwd>remote patient monitoring</kwd>
        <kwd>remote therapeutic monitoring</kwd>
        <kwd>digital health</kwd>
        <kwd>mobile technology</kwd>
        <kwd>mHealth</kwd>
        <kwd>mobile health</kwd>
        <kwd>remote monitoring</kwd>
        <kwd>patient monitoring</kwd>
        <kwd>cost</kwd>
        <kwd>economic</kwd>
        <kwd>payment</kwd>
        <kwd>Medicare</kwd>
        <kwd>insurance</kwd>
        <kwd>health coverage</kwd>
        <kwd>outpatient</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The opportunity to provide continuous care to patients between office visits using digital technologies holds tremendous potential to improve health care quality and patient outcomes. In 2019, the Center for Medicare and Medicaid Services (CMS) launched the remote physiologic monitoring (RPM) program that provided reimbursement for using technology to monitor patients between visits [<xref ref-type="bibr" rid="ref1">1</xref>]. RPM delivers continuous or periodic digital data to a central location. These data typically are reviewed by clinical staff (eg, nurses, medical assistants) whose time is billed “incident to” the supervising physician. RPM offers an intuitive complement to remote care delivered via telehealth. In part related to the COVID-19 public health emergency, RPM subsequently was expanded by CMS to improve coverage and reduce barriers to access.</p>
      <p>The RPM program requires that a biosensor be used to monitor patients between visits, often but not always in conjunction with a smartphone app. For many health conditions, a biosensor device is a logical component to chronic disease management. Examples include continuous glucose monitoring (diabetes), daily weights via a smart scale (heart failure), dysrhythmia detection (cardiac conditions), and ambulatory blood pressure monitoring (hypertension). Early evidence supporting RPM use appears favorable [<xref ref-type="bibr" rid="ref2">2</xref>]. Outside of isolated published examples that have largely been confined to a single chronic illness, the extent to which RPM has been deployed on a national scale is unknown. Using US Medicare data, we examined the uptake of RPM in the United States from 2019 (its inception year) to 2021.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>We examined publicly available Medicare Part B National Summary Data File data from January 2019 to December 2021 [<xref ref-type="bibr" rid="ref3">3</xref>]. We extracted Medicare payment amounts and the associated services allowed based on relevant Current Procedural Terminology (CPT) codes; individual patient information is not available in this data source. RPM services were grouped as setup (CPT 99453), data transmission (CPT 99454), and monitoring time, which is billed in 20-minute increments (CPT 99457,99458). Results were stratified by calendar year and analyzed in R version 4.2.3 (R Foundation for Statistical Computing).</p>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>In 2019, the total amount paid by CMS for RPM was US $5.5 million. In 2020, RPM payments increased almost 9-fold to US $41.5 million, followed by a further 2.5-fold increase in 2021, totaling more than US $101 million annually (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Medicare payments for remote patient monitoring services, 2019-2021.</p>
        </caption>
        <graphic xlink:href="mhealth_v11i1e46046_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p>Assuming providers initiate the program and bill setup fees only once per patient, the number of new patients increased from 20,640 (2019) to 90,149 (2020) and further increased to 123,476 (2021). The total payments made by CMS for the technical service (data transmission) were comparable to the payment for the time spent monitoring. Most (69%) monthly reimbursement for patient monitoring was for 20 minutes; only 31% was for monitoring beyond 20 minutes.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>Based on national data from the Medicare program, RPM grew approximately 19-fold over 3 years, suggesting rapid uptake. However, some have raised concerns about the potential for overuse of RPM without clinical benefit [<xref ref-type="bibr" rid="ref3">3</xref>]. Moreover, the use of RPM appears to be confined to a small group of physicians, predominantly primary care providers focused on hypertension or diabetes management [<xref ref-type="bibr" rid="ref4">4</xref>]. In addition to Medicare, both commercial insurance programs and many states’ Medicaid programs also cover RPM services [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Importantly, in 2022 CMS further expanded remote monitoring for certain medical specialties (musculoskeletal [rheumatology, orthopedics], respiratory medicine). Under this new program called remote therapeutic monitoring (RTM), a software app alone can be used for monitoring, and patients provide data through the app without a biosensor [<xref ref-type="bibr" rid="ref6">6</xref>]. The software itself is the medical device and would be registered and cleared by the US Food and Drug Administration as a class 1 (or higher) device.</p>
      <p>Thus beginning in 2022, RTM widens the spectrum of health domains available for monitoring, since any patient-reported outcome (eg, disease activity) or clinically relevant information (eg, medication adherence) now is reimbursable. We eagerly await the evaluation of the impact on patient outcomes offered by RPM and RTM, recognizing that much work to optimize their use remains.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CMS</term>
          <def>
            <p>Center for Medicare and Medicaid Services</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CPT</term>
          <def>
            <p>Current Procedural Terminology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">RPM</term>
          <def>
            <p>remote physiologic monitoring</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">RTM</term>
          <def>
            <p>remote therapeutic monitoring</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was supported by the National Institute of Arthritis and Musculoskeletal and Skin Diseases (P30AR072583). The funders had no role in the design and conduct of the study; collection, management, analysis, and interpretation of the data; preparation, review, or approval of the manuscript; and decision to submit the manuscript for publication.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data can be shared and are publicly available (see manuscript for source).</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>JRC contributed toward the concept and design of the study; drafting the manuscript; statistical analysis; administrative, technical, or material support; and supervision. JW made critical revisions to the manuscript for important intellectual content. JRC and JW contributed toward the acquisition, analysis, or interpretation of data and obtained funding for the study.</p>
      </fn>
      <fn fn-type="conflict">
        <p>JRC receives consulting fees from and owns stock in TNacity Blue Ocean. JRC is a part-time employee of Illumination Health (a health care research organization). JW has no conflicts of interest.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>Payment policies for CY 2019</article-title>
          <source>Federal Register</source>
          <access-date>2022-10-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.federalregister.gov/documents/2018/11/23/2018-24170/medicare-program-revisions-to-payment-policies-under-the-physician-fee-schedule-and-other-revisions#h-81">https://www.federalregister.gov/documents/2018/11/23/2018-24170/medicare-program-revisions-to-payment-policies-under-the-physician-fee-schedule-and-other-revisions#h-81</ext-link>
          </comment>
        </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>Taylor</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>EE</given-names>
            </name>
            <name name-style="western">
              <surname>Snoswell</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Caffery</surname>
              <given-names>LJ</given-names>
            </name>
          </person-group>
          <article-title>Does remote patient monitoring reduce acute care use? A systematic review</article-title>
          <source>BMJ Open</source>
          <year>2021</year>
          <month>03</month>
          <day>02</day>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>e040232</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33653740"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2020-040232</pub-id>
          <pub-id pub-id-type="medline">33653740</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2020-040232</pub-id>
          <pub-id pub-id-type="pmcid">PMC7929874</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>Mecklai</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Kramer</surname>
              <given-names>DB</given-names>
            </name>
          </person-group>
          <article-title>Remote patient monitoring - overdue or overused?</article-title>
          <source>N Engl J Med</source>
          <year>2021</year>
          <month>04</month>
          <day>15</day>
          <volume>384</volume>
          <issue>15</issue>
          <fpage>1384</fpage>
          <lpage>1386</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMp2033275</pub-id>
          <pub-id pub-id-type="medline">33853209</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>Tang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mehrotra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>Rapid growth of remote patient monitoring is driven by a small number of primary care providers</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2022</year>
          <month>09</month>
          <volume>41</volume>
          <issue>9</issue>
          <fpage>1248</fpage>
          <lpage>1254</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2021.02026</pub-id>
          <pub-id pub-id-type="medline">36067430</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>Remote patient monitoring</article-title>
          <source>Center for Connected Health Policy</source>
          <access-date>2023-04-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cchpca.org/topic/remote-patient-monitoring/">https://www.cchpca.org/topic/remote-patient-monitoring/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Medicare Program; CY 2022 payment policies under the physician fee schedule and other changes to part B payment policies; Medicare Shared Savings program requirements; provider enrollment regulation updates; and provider and supplier prepayment and post-payment medical review requirements</article-title>
          <source>Federal Register</source>
          <access-date>2022-10-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://public-inspection.federalregister.gov/2021-23972.pdf">https://public-inspection.federalregister.gov/2021-23972.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
