STAT+: After Medicare punts RPM overhaul to 2029, advocates see window to fight back

Medicare regulators moved forward with a plan to stop hospitals and other providers from using outside companies for remote patient monitoring. The policy matters because many providers currently depend on vendors to deliver these services. Instead, providers would need to create and operate monitoring programs themselves.

Implementation has been delayed for two years, placing the change in 2029 according to the question. The stated purpose is to give providers time to build in-house services. That period could involve hiring staff, developing systems, and changing operating processes, although the article does not describe specific requirements.

Opponents view the delay as more than preparation time. Christopher Adamec said stakeholders have two years to develop something better. Vendors and other advocates may use the window to seek value-based payment rules, operating guardrails, or another alternative to an outright ban.

Remote patient monitoring is a way to collect and review a patient’s health information while the patient is away from a hospital or clinic. It can support ongoing observation rather than relying only on occasional office visits. The source article identifies remote monitoring as the service at the center of Medicare’s proposed policy, but it does not define the technology.

In practice, a patient may use a connected device to record measurements such as blood pressure, blood sugar, weight, or heart rate. The information can be transmitted to a clinical team through digital systems. Clinicians review the readings, look for changes, and contact the patient or adjust care when appropriate.

This model separates monitoring from the physical care site. It can involve technology vendors that provide equipment, software, staffing, or support for providers. The article’s dispute concerns who may deliver that service, not whether remote monitoring itself exists.

The proposed ban has faced overwhelming opposition. The article names health technology companies, hospitals, insurers, and specialty organizations among those objecting. That range matters because it includes the businesses delivering monitoring, the providers using it, payers involved in coverage, and professional groups representing clinical specialties.

The Remote Monitoring Leadership Council is also advocating for another approach. Christopher Adamec, a lobbyist who advises the council, described its members as leading vendors. He said his mission is to find a value-based payment pathway, operating guardrails, or another alternative to the ban.

Despite the opposition, Medicare regulators pushed the plan forward. They offered a two-year delay rather than abandoning it. That delay creates a formal window for the affected groups to develop and promote a replacement policy before providers must stop relying on third-party services.

If providers can no longer use third parties, hospitals and other organizations would need to develop or operate remote-monitoring services internally. That could require new staff, technology, workflows, and administrative capacity. The article specifically says the delay is intended to give providers time to build in-house services.

Technology vendors could lose contracts with hospitals, insurers, and other providers. Their current role might shrink or change if they can only supply tools rather than deliver complete monitoring services. The article does not quantify the business impact, but it identifies vendors as major opponents of the proposal.

Patients could experience changes as providers reorganize their programs. Access, staffing, communication, or service continuity could be affected during a transition, although the article does not report specific patient outcomes. The two-year delay is meant to reduce disruption while stakeholders seek another policy.

Hospitals may rely on outside remote-monitoring companies because vendors can provide specialized technology and operational support without requiring each hospital to create every capability from scratch. Outside companies may also offer established workflows and staff experienced in handling monitoring programs. The article does not list these specific reasons, but it shows that providers currently use third parties.

An outside company can supply some combination of connected devices, software, data review, patient outreach, and technical assistance. The hospital remains involved in patient care, while the vendor supports the monitoring operation. This division can make it easier to launch or expand a program, depending on the provider’s resources.

Regulators’ two-year delay recognizes that replacing vendors with internal services is not immediate. Providers need time to build those operations. Meanwhile, hospitals and vendors are pressing for value-based payments, guardrails, or another solution that would preserve outside help while addressing Medicare’s concerns.

An alternative to an outright ban could allow third-party monitoring while imposing clear conditions. Regulators might define who may deliver services, what providers must oversee, how patient information is handled, and how vendors are accountable. The article calls this kind of approach a set of guardrails, but it does not specify the rules.

Another option is a value-based payment pathway. Instead of rewarding activity alone, payment would be linked to the quality, results, or usefulness of care. A provider and vendor could share responsibility for meeting agreed measures, such as timely review or better management of monitored patients. Specific measures are not provided in the article.

These alternatives would preserve a role for vendors while giving Medicare more control over quality and accountability. The Remote Monitoring Leadership Council is using the two-year delay to pursue such options. Whether regulators accept them remains unresolved.

Medicare decides reimbursement through coverage rules, payment policies, and evidence about whether a service fits a covered benefit and is medically necessary. Decisions can involve federal regulations, official payment schedules, and evaluations of how care is delivered. The source article does not explain Medicare’s general reimbursement process, so this broader description draws on established health-policy knowledge.

Traditional fee-for-service payment pays separately for individual services or billable activities. A provider receives payment when it performs a covered visit, procedure, or other qualifying service. Value-based payment instead connects some payment to results, quality, patient outcomes, coordination, or cost control, depending on the program.

In this dispute, a value-based pathway could let third-party monitoring continue under performance expectations. The article does not state which outcomes Medicare would use. Christopher Adamec presented value-based payment as one possible alternative to the proposed ban.