CMS vendor ban sparks backlash over remote monitoring rules

Drip

The gist

CMS’s proposed 2027 rule banning third-party vendors from Medicare RPM reimbursement has sparked fierce industry backlash and could upend remote patient care nationwide.

What to know

  • The new rule would restrict Medicare payments for remote monitoring to clinical staff directly employed by billing providers, aiming to curb $536 million in fraud flagged by the 2024 OIG report.
  • Experts warn this reverses years of expanded RPM access and threatens care models that rely on outsourced vendors for chronic condition management.
  • Critics advocate for a phased, data-driven approach rather than an abrupt vendor ban, fearing the proposal could destabilize digital health progress and limit patient access.

Fraud Fallout Fuels Crackdown

Rampant billing abuses and compliance failures in third-party RPM vendor models have triggered CMS’s move to restrict reimbursements to in-house clinical staff, aiming to restore oversight and data integrity.

CMS's 2027 proposal to restrict reimbursement for remote patient monitoring (RPM) services exclusively to clinical staff employed by billing providers arises from alarming fraud and compliance issues documented by the Office of Inspector General (OIG). The OIG's 2024 report revealed Medicare RPM payments surged to $536 million—a 31% increase from 2023—amid widespread billing abuses such as charging for device data days not generated and clinical time never spent, exposing systemic vulnerabilities in third-party vendor models. This regulatory move aims to curb the escalating costs and enhance billing transparency by ensuring that only directly employed clinical staff, subject to stricter oversight, can claim reimbursement.

Beyond financial fraud, the OIG findings highlight a fundamental compliance challenge rooted in the RPM vendor business model’s incentive structure, which prioritizes billing volume over clinical necessity and rigor. Vendors have been documented enrolling Medicare beneficiaries without physician-ordered monitoring or clinical justification, raising concerns not only about Medicare waste but also about the integrity of clinical trial data reliant on these services. As regulatory frameworks like 21 CFR Part 312 hold clinical trial sponsors accountable for data integrity regardless of vendor delegation, reliance on RPM vendors without rigorous oversight introduces significant compliance risks that contractual agreements alone cannot mitigate.

The OIG’s 2024 watchdog report further exposed critical gaps in RPM service delivery, noting that 43% of Medicare beneficiaries receiving RPM lacked at least one essential component—devices, education/setup, or treatment management—while Medicare itself lacks fundamental data on who ordered the monitoring. This absence of basic clinical and billing information underscores CMS’s rationale for tightening reimbursement rules to clinical staff directly employed by billing providers, aiming to close loopholes that have allowed widespread fraud and compromised patient care quality within the rapidly expanding RPM landscape.

Sources

Vendor Ban Disrupts Care Ecosystem

CMS’s proposed rule would cut off reimbursement for outsourced RPM and RTM services, jeopardizing the operational flexibility and rapid deployment that providers—especially in rural areas—depend on.

Legal and industry experts, including Foley & Lardner LLP partner Thomas Ferrante, emphasize that CMS’s 2027 proposed rule represents a significant narrowing of reimbursement pathways by mandating that remote patient monitoring (RPM) and remote therapeutic monitoring (RTM) services be delivered exclusively by clinical staff employed directly by billing providers. This change disrupts the current ecosystem where third-party vendors play a crucial role in supporting remote monitoring programs, thereby limiting the operational flexibility and scalability that many providers, especially smaller or rural ones, currently rely upon.

This proposal marks a stark departure from CMS’s prior trajectory since 2018, which had generally expanded access to RPM and RTM services. Thomas Ferrante highlights this shift as a reversal of CMS’s earlier posture that sought to broaden coverage, signaling a more restrictive approach that could curtail the growth and accessibility of remote monitoring in clinical practice.

Industry leaders like Christopher Adamec of the Alliance for Connected Care challenge CMS’s rationale that third-party vendors provide only a 'loose association' with treating practitioners, underscoring that many vendors are deeply integrated within care teams and provide indispensable infrastructure that would be costly and time-consuming for providers to replicate. Adamec argues that vendors serve as 'shovel-ready capabilities,' enabling providers to rapidly implement RPM services that are vital for preventing hospitalizations, particularly in underserved areas.

While CMS cites concerns over program integrity and the quality of care delivered by third-party clinical staff as justification for the proposed restrictions, stakeholders contend that this perspective overlooks the practical benefits and clinical integration many RPM vendors offer. The industry warns that eliminating reimbursement for third-party vendors risks undermining coordinated care efforts and could reduce access to essential remote monitoring services for Medicare beneficiaries.

Sources

Care Models Face Risky Overhaul

Forcing RPM programs to shift from outsourced to in-house clinical teams threatens to destabilize patient care and reverse hard-won advances in chronic disease management, prompting calls for a phased, data-driven transition.

The CMS 2027 proposed rule restricting reimbursement for remote patient monitoring (RPM) and remote therapeutic monitoring (RTM) services exclusively to clinical staff employed directly by billing providers threatens to upend care models that have thrived on partnerships with outsourced clinical vendors. These third-party organizations, which provide specialized infrastructure and trained personnel working under physician supervision, have become integral to many successful RPM programs by filling staffing gaps and enabling continuous patient monitoring. Forcing a rapid transition to fully in-house clinical teams risks disrupting services that currently improve patient outcomes, such as hypertension control and diabetes management, as these programs are not equipped to scale internal staffing quickly without compromising care continuity and effectiveness.

Beyond staffing upheaval, the proposed changes may inadvertently undermine the scalability and efficiency of RPM programs that rely on outsourced clinical expertise for timely data interpretation and intervention. Remote monitoring has expanded providers’ capacity to manage patients proactively outside traditional settings, supporting earlier interventions and better engagement. By limiting reimbursement eligibility, CMS’s proposal could reduce access to these benefits, potentially reversing gains in patient health outcomes and complicating the integration of RPM data into clinical workflows—a shift that some industry experts warn could destabilize the evolving digital healthcare landscape.

A more measured, phased approach could better balance CMS’s goals of accountability and value-based care evolution without destabilizing existing RPM delivery models. Introducing modifier codes to capture data on device types and staffing configurations, coupled with mandatory reporting of baseline and discharge patient outcomes, would provide CMS with the evidence needed to refine reimbursement policies. This strategy would facilitate a data-driven transition from fee-for-service to value-based RPM programs, ensuring that success is measured by improved patient health metrics rather than merely clinical staff time or claims volume, thereby preserving innovations in care delivery while aligning with Medicare’s statutory payment requirements.

Sources

Get the stories behind the trends

Deep-dive reporting and the weekly brief, in your inbox.