CMS Wants to Know Who’s Actually Watching Your RPM Patients. Most Practices Won’t Like the Answer.

CMS’s CY2027 Physician Fee Schedule proposed rule has been in the comment period since mid-July, and most of the coverage has gone where it always goes: conversion factor math, MIPS phase-out, the new telehealth platform modifiers. All real. None of it is the line practices running Remote Patient Monitoring or Remote Therapeutic Monitoring should be losing sleep over.

Buried in the Part B provisions is a proposal requiring RPM and RTM services to be furnished only by clinical staff who are direct employees of the billing practice — not contractors, not an outsourced monitoring vendor, not a staffing partner running the day-to-day patient check-ins. If it survives to the final rule, it takes effect 1 January 2027. Comments close 14 September.

The headline versus the operating reality

The headline is “CMS tightens remote monitoring rules”. The operating reality is that a meaningful share of the RPM/RTM market runs on exactly the staffing model this proposal would disallow. Practices that do not want to build and manage an in-house monitoring team — which is most small and mid-size practices — contract that work out to specialised RPM vendors who employ the clinical staff, run the platforms and bill the practice a per-patient fee. That arrangement is practically the default on-ramp into remote monitoring for anyone without hospital-system-scale infrastructure.

CMS’s proposal does not touch the technology. It does not touch medical necessity. It touches who is allowed to be on the payroll of the person doing the monitoring. Alongside it, CMS is also proposing a separately reportable initiating visit for RPM/RTM onset, restricting RTM to established patients, and floating a bundling of the existing codes into new G-codes. Any one would require a workflow update. Together they add up to CMS redrawing who is allowed to touch these codes at all.

Why this is a staffing problem before it is a billing problem

The instinct is to file this under “coding change, wait for the final rule, update the superbill in December”. That instinct is wrong here. If this finalises as proposed, practices using an outsourced RPM/RTM vendor do not have a coding problem in January — they have an eligibility problem. The claims will not be denied for the wrong modifier. They will be denied because the person who did the work was not allowed to have done it, and that is not something a resubmission fixes.

Which means the decision point is not Q1 2027. It is now, while the comment period is still open and there is runway to either restructure the staffing arrangement or make the case to CMS that the direct-employment requirement does not hold up operationally.

What to actually do with this

• Find out today whether your RPM/RTM monitoring is performed by your employees or by a contracted vendor’s staff. If you do not know without asking, that is the first sign this needs attention.
• If it is outsourced, start pricing what direct employment would cost — even roughly. Hiring, training and scheduling in-house monitoring staff is a materially different cost structure than a per-patient vendor fee, and that math needs to exist before the final rule does.
• Comment before 14 September if you have an operational reason the direct-employment model does not work — coverage across time zones, specialised staffing that is genuinely hard to hire in-house, patient volume that does not justify a full-time hire. CMS proposed rules get revised on exactly this kind of operator input.
• Start the conversation with your RPM/RTM vendor now. If the requirement finalises as written, they will be having it with every client at once.

The 2030 view

CMS has spent this year tightening the space between who bills a service and who actually performs it — the lab fraud crackdown, the telehealth platform modifiers, and now this. The common thread is not any single code or rule. It is that CMS is increasingly unwilling to pay for services where the billing entity and the delivering entity are two different organisations connected by a vendor contract.

Remote monitoring built an entire cottage industry on that separation. The practices that come out ahead will not be the ones who wait to see if this survives to the final rule. They will be the ones who already know what their staffing model looks like if it does.