CMS proposed rule would end vendor-run remote monitoring. Here’s what breaks for health systems.

• CMS would pay for RPM only when the billing practice’s own staff furnish it, ending the vendor-run model most programs rely on as of Jan. 1, 2027.
• The trigger: OIG found 43 percent of enrollees missing required components as RPM payments jumped 31 percent in a year — critics say the fix cuts off rural providers that can’t staff monitoring.

CMS wants to stop paying for remote patient monitoring when a third-party vendor runs the program. Under a proposed rule released July 14 as part of the 2027 physician fee schedule, Medicare would reimburse remote physiologic and therapeutic monitoring only when the service is furnished by clinical staff employed by the billing practice. This change would force health systems built on vendor-run RPM to either bring those programs in-house or walk away from a payment category that grew 31 percent in a single year.

Staff wouldn’t need to be on-site, as the tether is the billing relationship, not the location. But that distinction is exactly what unwinds the dominant “RPM-as-a-service” model, in which vendors supply the devices, the monitoring staff, and the workflow while the practice bills Medicare. CMS says that arrangement “can fragment care” and thin out oversight by the billing practitioner. Industry groups say the rule ends remote monitoring outright for the smaller and rural organizations that can’t staff it themselves. 

The proposed rule forces every health system to decide before Jan. 1, 2027, whether its RPM program is a clinical service it runs or a reimbursement stream it rents.

What would insourcing RPM actually require?

For a system whose RPM program runs on a vendor’s staff, the rule leaves three options: staff it internally, drop the program, or bet that the comment period softens the final rule.

The billing practice would have to employ the clinical staff who review device data, triage alerts and document the time that supports each billed code, work most vendors now sell as a turnkey service. That means hiring or reassigning nurses, sorting out licensure for monitoring staff who cover patients across state lines, and taking over the device logistics vendors currently absorb: provisioning, connectivity, returns. Health systems will have to answer questions that vendor contracts made invisible. How many FTEs does 20 minutes of monitoring per patient per month actually require at scale? Who owns the escalation pathway at 2 a.m.? What does the program cost to run when the per-patient service fee becomes payroll?

What other RPM changes are in the proposed rule?

The same rule carries three quieter provisions, each an operational headache. Remote therapeutic monitoring would be billable for established patients only, extending a requirement that already applies to RPM and closing the door on remote monitoring as a new-patient acquisition channel — a model some vendors built entire go-to-market strategies around. A separately reportable initiating visit would be required before monitoring can begin, inserting a scheduling and documentation step in front of every enrollment. And CMS is requesting comment on whether to bundle the RPM codes, a signal that the agency may restructure the payment itself in future rulemaking regardless of what happens to the staffing provision.

Behind the crackdown

The agency’s case rests on two OIG reports. The first, from 2024, found that 43 percent of Medicare RPM enrollees in 2022 did not receive at least one of the required components of the service billed on their behalf — education and device setup, device supply, or treatment management. The second, from 2025, tracked the money. Medicare payments for remote monitoring rose 31 percent in a single year, from $408 million in 2023 to $536 million in 2024.

In the proposed rule, CMS says outsourced arrangements “can fragment care” and weaken the billing practitioner’s oversight of the patient. When the practice that bills for monitoring never touches the monitoring, the code becomes a pass-through, and the OIG’s missing-component numbers are what a pass-through looks like at scale. CMS is not proposing to pay less for RPM. It is proposing to stop paying for RPM that the billing practice doesn’t perform.

Christopher Adamec, executive director of the Alliance for Connected Care, an industry coalition whose members include RPM vendors and health systems, says the proposal “ends RPM, both high quality and low quality.” The rule, in his reading, doesn’t distinguish between the pass-through arrangements the OIG flagged and well-run programs that happen to use outside clinical staff.

His argument lands hardest where vendor self-interest is weakest. Critical-access hospitals and rural health clinics adopted vendor-run RPM precisely because they cannot recruit and retain the nursing staff to watch device data around the clock — the same workforce shortage that limits every other service line they run. For rural operators, the rule doesn’t present a build-or-buy decision, it presents a build-or-quit decision, and most fall on the “quit” side. If the access argument holds, the beneficiaries who lose monitoring first are the chronic-disease patients in the counties with the fewest alternatives — the population RPM was supposed to serve best.

What should health IT leaders do before Sept. 14?

Three moves, in order:

1. Audit the billing arrangement. Determine how much current RPM revenue depends on a vendor furnishing the service under the practice’s billing number. For many systems, the answer is all of it.
2. Model the insourcing cost against the reimbursement at stake — monitoring FTEs, licensure, device logistics, plus the new initiating-visit workflow. A program that pencils out as a vendor service may not survive the math as a staffed one, and knowing that in October beats discovering it in December.
3. Decide whether to file a comment. The Sept. 14 deadline is the industry’s last real leverage before most provisions take effect Jan. 1, 2027, and CMS’s open question on code bundling suggests the agency is still deciding how far to go.

The proposal signals the end of light-touch RPM reimbursement. The systems most exposed are the ones that treated remote monitoring as a plug-in vendor service rather than a staffed clinical program.