CMS recently released its proposed Medicare Physician Fee Schedule for 2027, including several provisions related to remote physiologic monitoring (RPM) and remote therapeutic monitoring (RTM).
The proposal offers an early view into how CMS is thinking about clinical relationships, staffing, service valuation, and billing structures as remote monitoring continues to mature.
The most important context is also the simplest: these policies are proposed, not final. Nothing in the proposal requires RPM programs to change how they operate today.
Still, the comment period gives provider organizations and digital health companies a useful opportunity to understand the policy direction, assess how the proposals relate to their programs, and contribute informed feedback before CMS publishes a final rule.
What CMS Has Proposed
The 2027 Medicare Physician Fee Schedule proposed rule includes several remote-monitoring provisions.
CMS is proposing to require practitioners reporting RPM or RTM services to furnish a separately reportable initiating visit when monitoring begins.
The agency is proposing that RTM services be furnished only to established patients. This would more clearly connect the beginning of remote therapeutic monitoring to an existing practitioner-patient relationship.
CMS is proposing to allow payment for RPM and RTM services performed by clinical staff only when those staff members are employed by the practice, rather than when those services are performed by contracted clinical staff.
CMS is also reviewing how remote-monitoring services are valued under the Physician Fee Schedule. The agency believes some devices may be available at lower costs than initially estimated.
Separately, CMS is requesting feedback on whether the current RPM and RTM codes could eventually be bundled and replaced with four new HCPCS G-codes. This is a request for comment, not a formal proposal to replace the existing codes in 2027.
Each of these distinctions matters. Proposed policies may change during rule making, while requests for comment are intended to help CMS evaluate potential future approaches.
What the Proposal Does, and Does Not Mean
The proposal does not mean that remote monitoring is being discontinued or that organizations need to reconsider the value of existing programs.
It also does not eliminate the role of digital health partners.
RPM programs depend on a broad range of capabilities beyond clinical staffing, including connected devices, logistics, patient engagement, data management, workflow automation, analytics, integrations, and technical support. Those capabilities remain central to operating remote care at scale.
The clinical-staff proposal is narrower. As currently written, it addresses whether or not RPM or RTM work performed by contracted clinical staff would be billable.
The proposal’s practical effect will depend on its final language, CMS’s accompanying guidance, and the specific structure of each program. It is too early to draw broad conclusions about individual organizations or vendor models.
For now, the appropriate response is understanding, not restructuring.
Why CMS Is Reviewing Remote Monitoring
Remote monitoring has grown meaningfully within Medicare.
The HHS Office of Inspector General reported that Medicare payments for RPM exceeded $500 million in 2024. OIG also developed billing measures that CMS and other organizations could use to identify patterns that may warrant closer review.
Examples included practices billing for a high proportion of patients with no previous history at the practice and billing for multiple monitoring devices for the same patient in one month.
CMS referenced recent OIG recommendations when discussing whether the existing remote-monitoring code structure provides sufficient clarity and oversight.
This type of review is a normal part of a growing care model. As utilization increases, CMS evaluates whether payment policies still reflect current technology costs, clinical practice, and program-integrity needs.
At the same time, federal health guidance continues to recognize remote monitoring’s role in helping patients manage chronic conditions and supporting care decisions between visits. The HHS remote patient monitoring guidance highlights benefits such as providing a fuller picture of a patient’s health, supporting earlier care decisions, and reducing travel burdens.
Taken together, the signals point toward continued support for remote care alongside greater clarity about how services are initiated, delivered, and documented.
Questions Remote-Care Leaders Can Consider
Programs do not need to make immediate changes in response to the proposed rule. They can, however, use the rule making process as an opportunity to better understand their current operations.
Helpful questions include:
How is the initiating visit incorporated into the patient journey?
Which responsibilities belong to the practitioner, employed clinical staff, technology partner, and device partner?
How are patient interactions and clinical time documented?
How do abnormal readings move from the monitoring platform to the appropriate care-team member?
Where are communication, escalation, and follow-up activities recorded?
Can the program clearly distinguish clinical services from technology, logistics, and administrative support?
These are useful questions regardless of where the final rule lands. Clear roles and connected workflows help teams operate consistently, support patients, and maintain visibility as programs grow.
Technology can make that work easier. Impilo brings device logistics, patient communications, monitoring data, alerts, workflow automation, and EHR connectivity into one platform. The goal is give each organization the infrastructure and flexibility to operate its chosen model clearly and efficiently.
What Happens Next
CMS is accepting public comments on the proposed rule through September 14, 2026, according to the official CMS rule page.
During that period, provider organizations, professional associations, technology companies, and other interested parties can respond to the proposed policies and provide information about their likely effects.
The final rule may adopt, revise, delay, or decline to finalize individual proposals. Until that process is complete, remote-care leaders should continue serving patients under current requirements while following the rule making process closely.
The broader takeaway is measured but important: as remote monitoring grows, CMS is looking for payment policies that reflect current costs, recognizable clinical relationships, and clearly delivered services.
That is not a reason for programs to become anxious. It is an opportunity for the industry to help shape thoughtful policy for the next stage of remote care.
Frequently Asked Questions
Are the proposed 2027 RPM and RTM changes in effect now? No. They are part of a proposed rule and do not change current Medicare requirements. CMS will consider public comments before deciding which provisions to include in the final rule.
Does the proposal prevent practices from working with RPM vendors? No. The proposal does not prohibit practices from using technology, device, logistics, integration, or administrative partners. One provision addresses payment for RPM and RTM services performed by contracted clinical staff, but its effect will depend on the final language and each program’s structure.
Should RPM programs change their staffing models now? The proposal alone is not a reason to make immediate staffing changes. Programs can use this period to understand their current responsibilities and workflows, follow CMS updates, and consult qualified reimbursement or legal professionals if the final rule affects their model.
