7.25.25
10 min. Read

CMS RFI review: 12 ideas from health tech cos

In this article:

Issue 251

Welcome back to E&O: SaMD, a paying subscribers-only weekly newsletter focused on the world of digital pharma products, prescription digital therapeutics and other FDA-regulated digital health.

 E&O: Software as a Medical Device

 

This week’s newsletter is tough to categorize as it spans a few different business models. Earlier this year, CMS put out a request for information, which included a number prompts and questions about how CMS should pay for health technologies. Read on below for some ideas and excerpts from more than a dozen health tech and big tech companies that responded to the RFI…  Was this forwarded to you? Click this link for more info on how to become a paying subscriber.

Excerpts and ideas from 12 health tech companies that responded to the CMS Health Technology RFI

With nearly 1,000 responses, the request for information focused on health technology that CMS published earlier this year is a lot to sift through. I read through dozens of responses from health tech companies and put together this round-up below. I focused mostly on ideas I found that were related to CMS reimbursement of digital health, but just as many or more were focused on how to improve health data interoperability. Read on for suggestions from Google, Teladoc, Spring Health, Verily, Omada Health, Sword Health, Samsung, Click Therapeutics and more.

Expand types of providers who can bill remote monitoring codes, reimburse asynchronous comms, pay for patient navigation tools and provider portals

Mental health provider Spring Health included an interesting section in its comments focused on how reimbursement for digital health should change so that providers are more likely to adopt it:

“Expand remote monitoring codes to cover:

  • Asynchronous Communication, which minimizes hassle for patients and providers and allow for between-encounter check-ins and updates;
  • Digital Navigation Tools, which help patients find experienced providers who match their needs for access;
  • Caregiver Portals, to incentivize provider use of advanced tooling for tracking patient progress, visualizing change over time and across patients, identifying potential flags for interventions, providing comparative information to other providers; and
  • PRO and Passive Monitoring Tools, which help patients track their progress, and specifically which take advantage of AI tools that can provide insights and support patients and their care teams in shared decision-making;

Allow reimbursement for services delivered by a wider array of licensed behavioral health professionals, including coaches, social workers, and out-of-state providers under interstate licensure compacts; and Pilot a digital-first Alternative Payment Model (“APM”) comparing AI-enabled and traditional models, using [an outcomes framework Spring outlined in a different part of its letter], with a goal of establishing the value proposition for both the provider and the patient in using AI tools and illustrating how these tools can be used successfully in routine care settings.”

Create new reimbursement codes specific to digital care so that real world data and digital health-driven outcomes could be better studied

Omada submitted one of the longest letters I read in response to the RFI, so the excerpt below is just a fraction of their thinking on how CMS could facilitate broader adoption of digital health. In the excerpt below Omada suggests how CMS could best collect real world data on digital health outcomes:

“Omada believes the best way [for CMS] to collect [real world] data would be to enable healthcare providers who use digital health tools and digital health products to submit claims for that care. If this were to occur, digital care, like traditional care today, would produce substantive clinical data that can be used to further study digital care and its efficacy, safety, and economics (both immediate cost and long-term ROI), just as we study the claims data of traditional care today. Unfortunately, there are current impediments to this analysis. For example:

  • A significant majority of CPT codes require synchronous care or are not otherwise amenable to use by providers of asynchronous care. In addition, there are even more Category 1 E&M codes that describe care that can safely and effectively be supplied asynchronously with the support of digital health tools and products but cannot be billed for using existing CPT codes. Some research has been conducted on the quantity of Category 1 E&M CPT codes for services that could be supplied asynchronously as well as synchronously.
  • Not all digital health tools and digital health products (and perhaps even very few) are FDA-regulated devices, and many, if not most, should not be treated as devices under the provisions of the 21st Century Cures Act. This means, however, that category 2 CPT codes (for devices) are not usable for many health care services . Using device codes would muddy the analytic data about what care services actually occurred and could undermine the integrity of results on outcomes or costs.”

Expand Medicare coverage for more digital care navigation offerings

Transcarent also had a wide-ranging letter that focused on a number of areas beyond CMS reimbursement for digital tools, but one section focused on reimbursement that caught my eye was about digital care navigation services:

“Expanding Medicare coverage of digital care navigation services beyond breast and cervical cancer is essential to ensure equitable access to timely, coordinated care across a broader range of conditions. While recent policy changes rightly acknowledge the value of navigation in cancer screening and follow-up, beneficiaries facing other complex or chronic health conditions including diabetes, cardiovascular disease, musculoskeletal disorders, and mental health challenges, stand to benefit equally from personalized, technology-enabled support.”

Remove the “non-standard” plan design barrier for exchange-based health plans to help adoption of virtual-first health plans 

Teladoc included an interesting suggestion focused on a regulation that applies to health plans listed on the government exchanges. I didn’t see this included in other letters from health tech companies (though I’m sure Teladoc wasn’t the only one to suggest this):

“Remove the regulatory cap on ‘non-standard’ plan design to encourage innovation and the expansion of virtual-first plan offerings on Federally-facilitated Exchanges (FFEs) and State-based Exchanges on the Federal platform (SBE-FPs).”

Make wearables and apps DME, allow Medicaid 115 waivers for wearables, require MA to cover wearables, create a CMS registry of evidenced-based digital health

Oura sent CMS a long letter with many specific recommendations focused on interoperability issues as well as Medicare reimbursement. (Oura’s recently hired Chief Medical Officer, Dr. Ricky Bloomfield spent many years on Apple’s health team.) I’ll just focus on Oura’s reimbursement-focused comments:

“CMS should lower the barrier to access for proven digital health tools, including evidence-based wearable devices, through the following mechanisms: a. Medicare Coverage Expansion: cover wearable devices and apps under Medicare as durable medical equipment or remote monitoring tools. b. Medicaid Waivers and State Innovation: allow states to cover wearable devices via Medicaid 1115 waivers or incentives. The federal government could create a streamlined template for states to use. c. Medicare Advantage and Private Plan Benefits: encourage/require MA and private plans to offer evidence-based wearable devices as wellness or chronic care benefits.”

CMS floated the idea of a product registry for digital health tools and asked if CMS should be the entity to create such a registry. Like many commenters, Oura agreed that it could do that, but Oura advocated for a very light touch here (also note that the company wrote “could” and not “should” haha):

“CMS could create a registry of health applications and request submissions of outcomes data tied to these apps. This could be as simple as a link to PubMed or other journal articles. AI could be used to summarize key points in a user-friendly way, or app owners could submit their own summaries.”

Higher shared savings percentages for ACOs that adopt digital tools

Amazon largely focused on interoperability issues, but it did include a brief comment or two on how CMS could drive adoption of digital health tools in accountable care organizations:

“To accelerate the adoption and effective use of digital health tools in accountable care organizations (ACOs), we recommend a multi-faceted approach. This includes offering higher shared savings percentages for ACOs demonstrating effective digital tool implementation, providing grants or subsidies to offset initial investment costs, and introducing bonus payments tied to patient engagement metrics via digital platforms. Additionally, allowing digital health investments to count towards risk-bearing requirements can reward further adoption. These measures should support the implementation of crucial technologies, such as real-time patient event notifications, automated quality reporting, predictive analytics, telehealth services, and integration of diverse data sources including EHRs, claims, and patient-reported outcomes.”

CMS should help enable the creation of a modern personal health record via a secure identity layer and a robust API gateway

Okay, this suggestion from Google is a bit outside my focus on reimbursement of digital care, but I had to point out that the company that helped pioneer the concept of a PHR is suggesting CMS take another crack at it:

“The RFI notes the fractured, labor-intensive nature of managing multiple provider portals. A modern Personal Health Record (PHR) can solve this, but it must be more than a simple data repository; it must be a dynamic, patient-controlled hub for engagement that fosters a competitive marketplace of innovation… One option is for CMS to foster an ecosystem built on a multi-cloud platform where third-party applications, including PHRs, can securely access a beneficiary’s data from multiple sources with their express consent.”

“Recommendation: CMS can provide the key infrastructure components for this ecosystem. Drawing on our experience with Public Sector cloud projects and the Medical Records Android API, this would involve:

  • A Secure Identity Layer: Fostering an ecosystem of compatible and trusted digital identity providers. This allows beneficiaries to use a compliant identity of their choice (NIST 800-63-3 IAL2/AAL2) to eliminate the need for multiple portal logins and passwords.
  • An API Gateway: Building on the success of Blue Button 2.0, create a robust API gateway that allows authenticated and authorized third-party apps to access data from participating payers and providers, enforcing security and consent protocols.”

CMS-FDA should team up to figure out a framework for AI-enabled medical products regulation and reimbursement

Google-owned Verily also submitted a letter to CMS that covered a number of topics. It tackled the subject of AI-based care reimbursement but wasn’t super specific about what it would like to see from CMS. Instead, it suggested (in broad strokes) how CMS and FDA might work together to figure it out:

“In summary, FDA should consider a commensurate risk-based framework for postmarketing surveillance of safety and effectiveness for deployed AI-enabled medical products, and CMS could leverage shared insights from surveillance activities to inform and predictably implement coverage determinations or novel payment structures for AI-enabled medical products perhaps with support and input from diverse stakeholder discussions.”

Apple only submitted comments focused on digital IDs and health data interoperability. Those comments were largely descriptive of Apple’s practices and a few light suggestions for things CMS may want to keep in mind. It didn’t comment on CMS reimbursement for digital tools — like, potentially, Apple Watch.

Publish guidance focused on software-enhanced medicine and create incentive programs for their adoption, as well as HCPCS codes for them

Click Therapeutics a number of ways CMS might help drive adoption of software-enhanced medicines, which is what it calls its prescription digital therapeutic products when they are paired with a drug:

“It is strongly recommended that CMS offer programs and incentives that can act as examples to encourage favorable coverage from payers for FDA-authorized [Software-Enhanced] Medicines. This guidance should recognize the unique value proposition of SE Medicines as integrated therapeutic solutions and acknowledge their FDA authorization status, including of any added clinical benefit claims (e.g., favorable pricing or formulary positioning for added clinical benefits, and better reimbursement rates to plans/payers achieving superior SE Medicine utilization).”

“CMS should actively encourage and support the development and implementation of innovative payment models for SE Medicines, including value-based contracts. Given that SE Medicines can generate rich datasets on usage and outcomes, they are particularly well-suited for arrangements where reimbursement is tied to achieving pre-defined clinical or economic endpoints.”

“Payer reluctance often stems from uncertainty about the cost-effectiveness of new technologies and the absence of established billing and reimbursement mechanisms. As a major payer, CMS’s actions have a profound influence on the broader payer landscape. If CMS establishes incentive programs for SE Medicines within Medicare and Medicaid and spearheads the development of specific HCPCS codes for the software components and associated services, it would send a powerful signal to private payers regarding the legitimacy, value, and expectation of coverage for these therapies. This can create a positive cascade, encouraging wider payer adoption and thereby facilitating improved patient access to SE Medicines.”

Work with wearables companies to help make consumers aware of their medical benefits

Like some of the other clinically-minded wearables companies (Whoop and Oura), Samsung’s comments to CMS focused on a number of areas including data interoperability issues between consumer health platforms and EHRs. One idea from Samsung that I didn’t see elsewhere was focused on real-time insurance eligibility and benefit coverage checks (similar to what Amazon is doing with companies like Omada, Hinge, and Talkspace):

“CMS should also consider forming strategic partnerships with major consumer health platforms (e.g., Samsung Health) to enable real-time insurance eligibility verification, benefit coverage checks, and prior authorization workflows direction with digital health applications as well as data-sharing integrations with Medicare. A significant barrier to patient engagement and adoption of digital health interventions is uncertainty about insurance coverage. By partnering with platforms like Samsung Health, CMS can integrate seamless payer eligibility and prior authorization processes, empowering Medicare beneficiaries with immediate clarity on covered services. This integration would significantly accelerate the implementation of frictionless digital enrollment pathways, encouraging patients to engage proactively with personalized health recommendations that are verified as reimbursable by insurance, thereby reducing uncertainty and promoting widespread adoption of beneficial digital health interventions.”

Other suggestions from Samsung:

“[Open] pathways for remote therapeutic monitoring (RTM) and remote physiological monitoring (RPM) reimbursement for non-traditional platforms… much of the value lies in passive monitoring, digital coaching, asynchronous alerts, and non-billable coordination activities that contribute significantly to clinical outcomes, especially for high-risk patients.” “Samsung urges CMS to explore reimbursement for digital health tools for prevention and rehabilitation.”

“Today, patients and caregivers often navigate a disjointed digital experience – using separate applications for continuous glucose monitoring, insulin management tools, medication adherence, and coaching – each with its own login, data silos, and learning curve. This fragmentation creates cognitive and operational burdens, especially for patients managing chronic conditions. Tools like Samsung Health can serve as orchestration platforms that unify these services into one interface, streamline the experience, and enable seamless data sharing with caregivers and providers. Providing development incentives and introducing ‘orchestration reimbursement codes’ would stimulate the creation of more scalable, integrated solutions while addressing the current inefficiencies and complexity in managing multiple apps and device.”

Give providers in value-based care organizations bonuses based on wearable usage in patient population

Whoop focused some of its comments on the need for bi-directional data flow between devices like theirs and EHRs, but also touched on reimbursement for digital health tools. Whoop seemed most interested in value-based care arrangements:

“CMS should support devices and technologies that deliver predictive analytics, personalized alerts, and care plan integration. Additionally, CMS could allow wearable engagement to count toward quality measures and offer bonus payments tied to usage thresholds. This bonus payment mechanism could live within Medicare Advantage or value-based care arrangements with incentives tied to defined wearable usage thresholds. For example, CMS might establish a tiered incentive structure in which providers receive performance-based bonuses if a certain percentage of attributed beneficiaries meet sustained engagement criteria with approved wearable devices.”

Move from “minutes monitored” to “outcomes delivered” reimbursement for digital health

Sword Health, a digital MSK company that recently expanded into mental health care and plans to launch additional care programs in the future, sent in a letter that included fewer detailed suggestions than its peers. One specific recommendation Sword included for CMS:

“Based on our experience, savings from outcome‑based contracts can fund $0 cost‑sharing and targeted roll‑outs for example in rural or dually‑eligible populations, where the benefits of digital health products might be most beneficial. CMS can modernize digital health reimbursement by moving from ‘minutes monitored’ to ‘outcomes delivered.’ An outcomes‑based episode, grounded in the real‑world data infrastructure outlined above, will (a) protect beneficiaries from ineffective products, (b) unleash innovation among high‑performing vendors, and (c) curb the unchecked spending growth from the past few years.”

Links to E&O’s reports, databases, newsletters

Click below for dedicated pages for each of those categories:

  • Read through the long-form E&O research reports here.
  • Search and sort the E&O databases here.
  • Skim more than 300 past issues of E&O newsletters here.
And so ends Issue 251 of E&O: Software as a Medical Device. If you learned something from today’s issue, help me out and forward this newsletter to a friend or two.
Issue 251 Digital health research from Brian Dolan

 E&O: Software as a Medical Device

Welcome back to E&O: SaMD, a paying subscribers-only weekly newsletter focused on the world of digital pharma products, prescription digital therapeutics and other FDA-regulated digital health.

This week's newsletter is tough to categorize as it spans a few different business models. Earlier this year, CMS put out a

Paying Subscribers Only

It's a good one, too.
This digital health research is for paying Exits & Outcomes subscribers only. Subscribe now to read this article, get the weekly newsletter, and receive unrestricted access to past and future research from the Exits & Outcomes archives. Smash the link above or below to subscribe yourself -- or head over to our pricing page to subscribe your team or your whole company!
×

Full access to E&O's research and newsletters.

Get the subscribers-only newsletters + research reports + databases
Pricing updates: Teladoc, Maven, Garner, Kaia and more
8.29.25
4 min. Read
Pricing for Aetna Transform and 2nd.MD. Teladoc on PFS. Plus: Secret funding.
8.22.25
7 min. Read
New wearable BP 510(k) sheds light on Whoop-FDA. Trials: BetterHelp, Click, DynamiCare, Axena, Kaiser
8.08.25
8 min. Read
CMS proposes changes to digital mental health G codes, four year test of online DPP reimbursement.
7.16.25
10 min. Read
Digital mental health G code adoption “slow and challenging”
7.11.25
< 1 min. Read
FDA clears Lumosity-maker’s DTx for ADHD. Withings 510(k) for ECG app.
6.16.25
< 1 min. Read
Virtual Clinics Tracker: Growth metrics, NOCD pricing, Valera-Vita, more
6.06.25
5 min. Read
More details as Omada IPO is (set for) next week. CAC, ARPU, lost customers, NPS decreases, more
5.30.25
9 min. Read
PHTI’s premature PDT pricing analysis. CPT billing code rejects.
5.23.25
7 min. Read
PDT bill is back. Anthem covers Luminopia. FDA PCCP for Cognoa.
5.16.25
7 min. Read
  • First
  • Previous
  • 1 of 40
  • Next
  • Last