When Your RPM Vendor Does the Clinical Work
What CMS's Proposed 2027 Employment Requirement Could Mean for Remote Monitoring Revenue
A remote monitoring vendor is not automatically the problem. Under CMS's CY 2027 Physician Fee Schedule proposed rule, the consequential question is more specific: who performs the clinical work supporting your RPM or RTM billing?
CMS proposes to allow payment for RPM and RTM services only when performed by clinical staff employed by the billing practice rather than contractors. If finalized as proposed, that could require organizations using outsourced clinical-staff models to reconsider staffing, workflow, vendor responsibilities, and program economics.
The proposed change
Today, remote monitoring programs may be structured in a range of ways, including models that rely on contracted third-party clinical staff operating under applicable Medicare requirements. CMS's CY 2027 proposal narrows that: payment would be available only when RPM/RTM services are performed by clinical staff employed by the practice.
CMS also proposes a separately reportable initiating visit for RPM and RTM, and an established-patient requirement for RTM. Code-level effects on individual CPT families should not be overclaimed until the specific service mix has been modeled against the proposal as written.
“only to allow payment for RPM or RTM services when performed by clinical staff employed by the practice and not when those services are delivered by contractors.”
This is a proposal. It is not final policy, and the comment period remains open through September 14, 2026.
Using a vendor is not the same as outsourcing the billable clinical work
The diagnostic question is not “Do you use an RPM vendor?” Technology vendors can remain relevant under the proposal — platforms, devices, connectivity, logistics, and technical support are not the clinical work at issue. The question is: who performs the clinical work supporting the billed services?
Vendor provides the platform, devices, connectivity, logistics, and technical support. Clinical staff employed by the practice perform the relevant clinical work supporting billed services.
Practice employees and vendor personnel divide clinical activities such as monitoring review, outreach, and escalation.
Contractor or vendor personnel perform the clinical work supporting RPM/RTM billing.
These classifications are screening categories to structure an internal review. They are not legal determinations.
Why this is a revenue question, not just a compliance memo
If finalized as proposed, this change would not merely add a documentation step. It would affect the operating model that supports an existing revenue stream. Programs built on contracted clinical labor would need a different staffing structure to keep the same services billable.
The exposure is measurable, and it should be measured with your own data:
Affected treatment-management claims × applicable Medicare reimbursement × share of relevant work performed by contracted clinical staff = prospective revenue exposure requiring analysis
No dollar figure should be assumed from this framework alone. Actual exposure depends on CPT mix, staffing structure, billing arrangements, service documentation, and the final CMS policy.
Current compliance and proposed 2027 eligibility are different questions
A model that may become ineligible under a future rule is not automatically noncompliant today.
These are two separate analyses, and conflating them produces bad decisions.
Whether today's model satisfies current Medicare requirements for the services being billed, as those requirements exist now.
Whether the model would remain billable if CMS finalizes the CY 2027 employment restriction as proposed.
Retrospective recoupment exposure should never be derived solely from this proposed change. A proposal about future payment eligibility says nothing, by itself, about the propriety of past claims.
What organizations should map now
Regardless of how the rule finalizes, this is a reasonable operational inventory to hold before September:
- 01Which entity bills each RPM/RTM service?
- 02Who employs the clinical staff performing monitoring, outreach, escalation, and other clinical work supporting billed services?
- 03Which functions are performed by the vendor versus practice employees?
- 04Which CPT/service families and how much annual Medicare revenue depend on the current staffing model?
- 05What does the vendor agreement say operationally about staffing, responsibility, and change management? Legal interpretation of the agreement should be handled by counsel.
- 06Could the practice in-source relevant work, restructure responsibilities, or alter the program if the proposal becomes final?
2027 RPM/RTM Vendor-Model Revenue & Compliance Readiness Diagnostic
You know what CMS proposed. We determine what it could mean for your specific remote-monitoring operating model.
- —Map current RPM/RTM staffing and vendor responsibilities
- —Separate technology services from clinical work supporting billing
- —Identify current-state compliance questions requiring review
- —Model prospective revenue attached to potentially affected workflows
- —Assess operational remediation paths: in-source, restructure responsibilities, renegotiate the operating model, or reconsider affected services
- —Executive findings and action roadmap
This is an operational and reimbursement-readiness analysis. It is not legal advice.
Who actually performs the clinical work in your RPM or RTM program?
If the answer includes contracted third-party clinical staff, quantify the exposure before the proposed policy becomes an operational surprise.
Primary source: Centers for Medicare & Medicaid Services, CMS-1848-P, CY 2027 Medicare Physician Fee Schedule Proposed Rule, and the CMS CY 2027 PFS Proposed Rule Fact Sheet.
Source intelligence: Analysis based on primary CMS source materials monitored through ClinEfficiency Pro's PAULA policy intelligence system.
Last reviewed: August 11, 2026.