Medicare’s remote monitoring overhaul gets a two-year reprieve as hospitals and vendors regroup
Medicare regulators have pushed ahead with a plan that would bar hospitals and other providers from relying on third parties to deliver remote patient monitoring services. The move landed despite intense opposition from health technology companies, hospitals, insurers, and specialty organizations that argued the policy would disrupt established care models and narrow access to monitoring programs already in use across the system.
The agency did not make the change immediate. Implementation is now delayed until 2029, creating a two-year window that advocates view as the most important part of the decision. During that period, providers are expected to build in-house services if they want to preserve RPM programs under the new framework, but the delay also gives opponents time to organize a response and press for a different regulatory path.
A policy fight over RPM is not just about who bills for the technology. It reaches into how chronic disease is managed at home, how hospitals extend supervision beyond the bedside, and how much operational control Medicare wants providers to keep inside their own walls.
A fight over control, not just billing
At the center of the dispute is a simple but consequential question: should a provider be allowed to outsource the technical and operational machinery behind remote patient monitoring, or must those services be built and run in-house? Medicare’s answer, at least for now, leans toward the second option. The prohibition on third-party delivery would force hospitals and other organizations to reassess vendor-dependent programs, renegotiate contracts, or invest in internal infrastructure to maintain RPM workflows.
That shift could prove especially difficult for smaller systems and practices that have relied on outside vendors for device logistics, data capture, patient engagement, and monitoring support. Large health systems may be better positioned to absorb the operational lift. Smaller groups may not be. In practical terms, the policy could redraw the line between organizations that can independently support RPM and those that cannot.
The opposition has been broad because the stakes are broad. Health tech firms see a threat to established service models. Hospitals worry about operational strain. Insurers and specialty organizations are also pushing back, reflecting concern that the rule could reduce flexibility in care delivery rather than improve it.
The delay gives advocates a real opening
Two years is not a long time in health policy, but it is long enough to build a counterproposal. Christopher Adamec, a lobbyist advising the Remote Monitoring Leadership Council, framed the delay as a chance to develop “something better,” including a value-based payment pathway, guardrails, or another alternative structure. His comment captures the strategic shift now underway: the immediate goal is no longer just to stop the policy, but to replace it with something that Medicare can accept and stakeholders can defend.
That search for an alternative is likely to focus on accountability. Regulators clearly want more direct control over how RPM is delivered and who is responsible for the service. Advocates, meanwhile, will try to show that third-party participation does not automatically mean weak oversight. A workable compromise would need to preserve clinical access while satisfying Medicare’s concern that monitoring should not be detached from the provider’s own clinical responsibility.
The delay also changes the leverage point. Rather than facing an abrupt operational cutoff, providers now have time to document how RPM is used in care delivery, how patients are served by current models, and what breaks if the system is forced into a narrower structure. In policy terms, a delayed effective date often becomes a lobbying window. This one is no different.
Why remote monitoring matters at the bedside
The policy is administrative, but its effects would be felt in patient care. Remote patient monitoring is often used to track patients outside the clinic, allowing clinicians to receive ongoing physiologic data and intervene before deterioration becomes an emergency. In chronic disease management, that kind of surveillance can support earlier medication adjustment, faster escalation of care, and more frequent contact between visits.
A rule that reshapes how those services are delivered can therefore affect more than vendor contracts. It can influence how quickly abnormal readings are reviewed, who answers alerts, and how reliably patients remain connected to the clinical team. If hospitals are forced to internalize every element of the service, some programs may become harder to sustain. If programs shrink, patients with limited mobility, multiple chronic illnesses, or frequent exacerbations may lose access to a layer of monitoring that helps keep care continuous.
At the same time, Medicare’s move suggests concern that outsourcing may blur responsibility. Regulators appear to want a tighter chain of accountability between the provider and the monitoring activity itself. In that sense, the policy is about clinical governance as much as it is about billing. The unresolved issue is whether that governance requires exclusion of third parties or whether it can be achieved through standards, oversight, and payment design.
The next phase of the debate will likely be technical and political at once. Advocates will need to show how RPM can remain clinically useful under a model that satisfies Medicare’s expectations. Regulators will need to justify why the current structure is insufficient and why a two-year runway is enough for providers to reorganize.
The 2029 deadline changes the tempo of the debate
A hard implementation date often forces immediate adaptation. A delayed one invites competing plans. By pushing enforcement to 2029, Medicare has effectively separated policy adoption from policy impact, and that creates room for a more concentrated campaign from stakeholders who want the rule revised or replaced before it takes effect.
The extension may also soften the immediate operational shock for providers while preserving the substance of the proposal. Hospitals can continue planning, vendors can continue advocating, and specialty groups can continue pressing for a framework that recognizes the role third parties already play in RPM delivery. For patients, the practical effect is that nothing changes overnight, but the direction of travel is still clear: Medicare wants a different model, and the industry now has a finite window to prove that another one should prevail.
The next test will not be whether opposition exists. It already does. The real question is whether stakeholders can convert that opposition into a policy design Medicare finds acceptable before the 2029 deadline closes the door on the current model.