CMS Just Proposed the Biggest Change to RPM Since 2019. Here's What It Means for Your Program.

On July 14, CMS released its CY 2027 Physician Fee Schedule proposed rule, and for remote patient monitoring it is the most consequential rulemaking since the RPM codes were created in 2019. Last year’s rule expanded RPM — new 2-day device codes, a 10-minute management code, higher rates. This year’s proposal moves in the other direction: guardrails.

If your health system runs its own RPM program with your own clinical staff, this proposal largely validates the choices you’ve made. If you’re evaluating whether to outsource care management to an RPM vendor, you need to read this before you sign anything.

What CMS is actually proposing

Four provisions matter for RPM and RTM, effective January 1, 2027 if finalized:

Care management must be performed by clinical staff employed by the billing practice. CMS proposes to allow payment for RPM and RTM services only when performed by employed clinical staff — not when delivered by contractors. This is the headline. It strikes directly at the outsourced-monitoring model where a vendor’s nurses perform the billable treatment management time.

A separately reportable initiating visit would be required at the onset of RPM or RTM services.

The established-patient requirement extends to RTM, closing the gap that allowed RTM programs to enroll patients with no prior relationship to the billing provider.

Downward revaluation of the device supply codes. CMS believes devices cost less than its original estimates and proposes to revalue RPM/RTM services accordingly. No specific rates have been published yet — those come with the full rule text — but the direction is clear.

CMS is also seeking comment on a broader idea: bundling the RPM and RTM CPT codes into four new HCPCS G-codes. That’s a request for information, not a proposal, but it signals where CMS’s thinking is headed.

One important note: all of this is proposed. There is a 60-day comment period, a final rule is expected around November 1, and CMS has a track record of softening aggressive proposals after industry comment. But the direction of travel is unmistakable.

Why CMS is doing this

This isn’t arbitrary. It’s the direct product of a three-year OIG enforcement arc. OIG’s September 2024 report found that about 43% of Medicare RPM enrollees didn’t receive all three components of the service, and that CMS couldn’t identify the ordering provider for 44% of enrollees. Its August 2025 follow-up showed Medicare RPM payments reaching $536 million in 2024 — up 31% in a single year — and flagged dozens of practices billing RPM for patient panels where they had no prior medical relationship with the vast majority of patients.

Every one of the 2027 proposals maps onto a specific OIG finding. The initiating visit and established-patient requirements target enrollment mills. The employment requirement targets turnkey arrangements where a distant vendor does everything and a practice collects the reimbursement. The revaluation targets device economics OIG believes are inflated.

The honest read: CMS is not trying to kill RPM. It’s trying to kill a specific way of doing RPM.

If you run your own program, this is mostly good news

Health systems that operate RPM the right way — your patients, your ordering providers, your employed nurses doing the treatment management, real clinical decision-making documented in your EHR — are already substantially compliant with what CMS is proposing. The initiating visit requirement will need workflow attention, and the documentation bar rises. But the structural model survives intact.

More than that: these guardrails work in your favor. They raise the cost of entry for low-quality operators, they reduce the audit cloud hanging over the entire category, and they concentrate reimbursement in the hands of organizations that own genuine patient relationships. Legitimate programs have spent years competing against arrangements that shouldn’t have been billable in the first place. CMS is now proposing to say so in regulation.

The caution flag is on the revenue side. Between the proposed conversion factor reduction and the device-code revaluation, per-patient monthly economics will likely compress in 2027. We won’t know the magnitude until the rate tables publish, and I’d advise against re-baselining any program budget until the final rule lands. But build your 2027 planning with some headroom.

If you’re considering outsourcing care management — pause

This is the part of the proposal that should change how you evaluate vendors this year.

A meaningful share of the RPM vendor market is built on a clinical-services model: the vendor supplies the devices, the software, and the nurses who perform the monthly monitoring minutes, and the practice bills 99457 and 99458 for that time. Under the rule as proposed, that time would no longer be billable — because it wasn’t performed by clinical staff employed by your organization.

If you sign a multi-year agreement in 2026 that depends on vendor-employed staff performing your billable care management, you are taking on regulatory risk that the vendor cannot contract away. Ask any vendor pitching you an outsourced clinical model three questions:

1. Whose W-2 are the nurses on, and what happens to my billing if the employment requirement is finalized as written?
2. What does the transition plan look like if I need to bring monitoring in-house mid-contract?
3. How does the platform support my staff doing this work efficiently — or was it built assuming yours would?

There are legitimate arguments the industry will make in comments — that supervised staffing arrangements deserve flexibility, that a strict employment test will hurt access in rural and understaffed markets. Some of those arguments may prevail. We’ll be making some of them ourselves. But here is the line I’d draw: outsourced care management isn’t inherently the wrong choice — for many health systems it’s the only practical way to launch — but signing an agreement that has no contractual answer to this proposed rule is. If the vendor can’t show you the migration path in writing, the regulatory risk is yours, not theirs.

Where we stand

CareSimple has always been built on the premise that the health system owns the patient relationship and the clinical work, and the vendor’s job is to make that work scalable — cellular devices that work out of the box, logistics that don’t burden your staff, and integration deep enough that RPM lives inside your EHR workflows rather than beside them. More than 90% of our customers run their RPM programs exactly this way: their clinicians, their billing, our platform. The 2027 proposal doesn’t threaten that model. In several ways, it endorses it.

But I also want to speak directly to the rest — the customers who have asked us to take on care management services alongside the platform, and the health systems in our pipeline asking for the same today. We went into those programs with eyes open about where CMS was headed, and we’re not going to pretend this proposal doesn’t apply to us. It does. So here is our commitment: if the employment requirement is finalized as written, every CareSimple customer with an outsourced care management arrangement will have a defined, contractually supported migration path in place before January 1, 2027 — whether that means transitioning monitoring to your employed staff on our platform, restructuring the staffing arrangement into a configuration that meets the final rule’s requirements, or adjusting contract terms and pricing to reflect the new model. No one gets stranded mid-contract, and no one keeps paying for a delivery model that can no longer bill.

That’s also how we’d answer the three questions above, and it’s the standard I’d hold any vendor to — including us. Regulatory flexibility shouldn’t be a discovery you make during an audit; it should be written into the agreement before you sign it.

We’ll be filing comments during the open period, and we’d encourage every health system running RPM to do the same — particularly on the initiating-visit mechanics and the device revaluation, where real-world operational and cost data will matter to CMS. Comments are submitted through Regulations.gov under file code CMS-1848-P. When the final rule publishes in November, we’ll break down exactly what changed and what the 2027 rate tables mean for program economics.

In the meantime, if you’re modeling 2027 scenarios for your RPM program — or stress-testing a vendor proposal against this rule — that’s a conversation we’re having with health systems every week right now. Reach out.

The provisions described above are proposed, not final, and are subject to change in the final rule expected in late 2026. Consult your billing and compliance teams before making program decisions based on proposed rulemaking.

Sources: CMS — Calendar Year (CY) 2027 Medicare Physician Fee Schedule Proposed Rule (fact sheet, July 14, 2026). Public comments: Regulations.gov, file code CMS-1848-P.