CMS targets remote monitoring oversight, but the proposed fix reaches too far
CMS’s proposed 2027 Physician Fee Schedule would tighten Medicare’s rules for remote physiologic monitoring and remote therapeutic monitoring in several important ways. The proposal would require an initiating visit before RPM or RTM begins, extend the established-patient requirement to RTM, and limit payment to services furnished by clinical staff who are direct employees of the billing practitioner or practice.
The policy goal is understandable. Medicare payment for remote monitoring depends on real clinical work, not on a device shipped to a home and forgotten. Program integrity begins to erode when services are billed without the full set of required components, and CMS is responding to documented concerns raised by the HHS Office of Inspector General. In 2022, 43% of Medicare enrollees receiving RPM did not receive all three required components of the service.
That is a serious failure of oversight.
Program integrity is the right target, but employment status is a blunt instrument
The proposal treats staffing structure as a proxy for accountability. In practice, those are not the same thing. Whether a nurse is paid directly by the billing practice does not answer the clinically relevant questions: Was the patient appropriately selected for monitoring? Were alerts reviewed? Was supervision documented? Did the patient’s care team act when data changed? Did the service remain integrated into the plan of care?
A remote-monitoring program can be poorly run whether its staff are employees or contractors. It can also be tightly supervised whether the clinicians sit on payroll or work through a qualified partner. The regulatory problem is not the existence of outside clinical support. The problem is the absence of demonstrable oversight, documentation, and follow-through.
CMS is trying to solve fragmentation, insufficient practitioner involvement, and services that fail to meet the full requirements of RPM or RTM. Those concerns are real. But an employment rule alone does not establish clinical quality, and it does not guarantee that the billing practitioner is meaningfully accountable for what happens after the device is deployed.
Why maternal health makes the policy stakes more immediate
Pregnancy and the postpartum period show why remote monitoring exists in the first place. A patient’s blood pressure, symptoms, or other clinically important signals can change between visits. When access to in-person care is limited, remote monitoring can give the care team a chance to intervene before a complication becomes a crisis.
For maternal patients, the value of RPM is not the hardware and not the corporate structure behind the clinician reviewing the data. The value lies in the clinical bridge between appointments. That bridge matters most for patients facing transportation barriers, fewer local obstetric services, or fewer opportunities for routine in-person follow-up.
A direct-employment requirement could narrow that bridge. Large health systems may be able to absorb the added staffing burden. Smaller practices, rural clinicians, and obstetric groups already operating with thin personnel margins may not. If they cannot bring monitoring functions in-house, they may simply stop offering reimbursable RPM or RTM.
The result would not automatically be lower-quality remote care. In some settings, the result could be no remote care at all.
Accountability can be written into the rule without blocking qualified partners
CMS has other ways to protect Medicare without tying payment to payroll status. A stronger framework would hold the billing practice and its partners to clear standards of oversight and documentation. The crucial question is not who issues the paycheck, but who is accountable for the patient’s monitoring and management.
A workable rule could require a clearly identified clinical entity responsible for reviewing readings and escalating abnormalities. It could require documented protocols for response times, communication, and patient engagement. It could require auditable records showing who reviewed data, when the review occurred, and what action followed. It could also require explicit documentation of the relationship between the billing practice and any contracted monitoring partner, along with enforcement when those standards are not met.
Those safeguards would go directly to the behavior CMS is trying to control. They would make it harder to bill for hollow services while preserving flexibility for practices that rely on qualified clinical partners to deliver care.
The initiating visit adds structure, but the staffing rule may still miss the point
The proposed initiating-visit requirement could strengthen clinical accountability by establishing the patient relationship before monitoring begins. That step would help document that RPM or RTM is clinically appropriate and not simply attached to a billing opportunity. Extending the established-patient requirement to RTM would move in the same direction.
The employee-only payment rule goes further. It does not just define supervision or documentation standards; it reshapes how practices may organize care delivery. For some organizations, that change will be manageable. For others, especially those in already strained markets, it may be a barrier that has little to do with patient safety and a great deal to do with staffing capacity.
Remote monitoring works best when it extends the reach of the care team without forcing every practice to build an entire internal monitoring workforce. If CMS wants to curb misuse, the cleaner approach is to regulate the quality of the care pathway, not the employment contract behind it.
Medicare can demand real oversight without shrinking access
Medicare has every reason to insist on responsible use of RPM and RTM. These services should not become billing shells, and they should not function without supervision. But remote monitoring is a clinical service, not an organizational form. The patient benefit depends on whether meaningful data are reviewed, whether abnormal findings are acted on, and whether the patient remains connected to a qualified team.
The proposed rule tries to solve a quality problem by limiting one staffing model. That may reduce some bad actors, but it also risks excluding practices that deliver legitimate remote care through compliant partnerships. For maternal health in particular, the practical question is whether patients can still get timely monitoring between visits when access is already fragile.
CMS can strengthen accountability, preserve flexibility, and keep remote care available where it is most needed. The unresolved issue is whether the final rule will focus on demonstrable oversight, or whether it will treat employment status as a substitute for clinical responsibility.