← Back to Blog

2027 RPM Proposed Rule: Initiating Visits, Employed Staff, and What Could Change

By the Positive Check TeamPublished 9 min read
Healthcare administrator reviewing remote patient monitoring policy and operations

Key takeaways

CMS has proposed consequential RPM and RTM changes for 2027, but none of them are final. Practices should model the operational impact now while continuing to follow current policy.

  • CMS would require a separately reportable initiating visit at the start of RPM or RTM.
  • CMS would pay for RPM and RTM only when the relevant clinical staff are employed by the billing practice, rather than supplied as contractors.
  • The proposal would extend an established-patient relationship requirement to RTM; RPM already has an established-relationship requirement.
  • CMS is also seeking feedback on code valuation and possible bundled HCPCS G-codes for remote monitoring.
  • Comments on CMS-1848-P are due September 14, 2026. Current rules remain in effect unless and until CMS finalizes changes.

In the CY 2027 Medicare Physician Fee Schedule proposed rule, CMS is considering changes that could reshape how practices start, staff, and bill Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM). The most immediate proposals are a separately reportable initiating visit and an employment requirement for clinical staff who perform remote-monitoring services. CMS is also reconsidering how the code families are valued and structured.

The essential qualifier is proposed. CMS published the proposal on July 14, 2026, and lists a September 14, 2026 comment deadline. The agency can modify or decline to finalize any provision. Practices should not change claims based on the proposal alone.

What did CMS propose for RPM and RTM in 2027?

CMS identified four policy areas that deserve immediate attention from billing practitioners, care-management operators, and remote-monitoring vendors:

  1. A separately reportable initiating visit. At the onset of RPM or RTM, the practitioner would need to furnish an initiating visit that is separately reportable.
  2. An established relationship for RTM. CMS would apply an established-patient relationship requirement to RTM, aligning it more closely with RPM.
  3. Practice-employed clinical staff. CMS says payment would be made only when RPM and RTM services performed by clinical staff are furnished by staff employed by the billing practice, not contractors.
  4. Possible valuation and code-structure changes. CMS proposes valuation changes and is seeking comment on whether existing RPM and RTM codes should be bundled, including through four possible HCPCS G-codes.

Current policy versus the 2027 proposal

IssueCurrent CMS policyCY 2027 proposal
Patient relationshipRPM requires an established relationship; CMS guidance does not apply the same requirement to RTM.Require an established relationship for both RPM and RTM.
Initiating serviceCurrent remote-monitoring policy does not impose the proposed, separately reportable initiating visit across both programs.Require a separately reportable visit when RPM or RTM begins.
Clinical staffingCertain services may be furnished by auxiliary personnel under general supervision; earlier CMS rulemaking recognizes contracted employees in specified RPM contexts.Pay only when clinical-staff services are furnished by staff employed by the billing practice.
Code structurePractices use the existing CPT code families and their component requirements.Revise valuation and gather comments on possible bundling and new HCPCS G-codes.
Effective dateCurrent rules apply now.Generally January 1, 2027 if provisions are finalized.

What the proposed employment restriction could mean

The proposed language is most consequential for arrangements in which a third party supplies clinical staff who perform the work represented by an RPM or RTM claim. If finalized as written, practices using outsourced clinical labor would need to determine whether the personnel performing each billable activity meet CMS's employment requirement.

This should not be read as an automatic prohibition on every outside technology company. A software platform, connected device supplier, data-transmission service, or administrative vendor is not necessarily performing the clinical-staff service billed by the practice. The key operational question is who performs the work represented by each code, under whose supervision, and with what employment relationship.

Do not classify the entire vendor relationship with one label. Map setup, device supply, data review, patient communication, treatment management, escalation, documentation, and billing separately.

CMS may clarify the scope in the final rule. Until then, practices should have compliance counsel and billing specialists review their specific contracts and workflows rather than treating this article as a billing determination.

How an initiating-visit requirement could affect enrollment

An initiating visit could add clinical capacity, scheduling, documentation, and patient-conversion steps before monitoring begins. Programs built around rapid remote enrollment should model the effect on time-to-start and determine which eligible practitioners can furnish the visit. They should also avoid assuming that a recent unrelated encounter will satisfy a requirement whose final details CMS has not yet established.

The same operational map should distinguish the initiating visit from device setup, patient education, transmission, and monthly treatment-management activities. Separate documentation makes it easier to test workflows against the eventual final language.

Why the valuation and G-code discussion matters

The proposal goes beyond staffing. CMS is considering whether the current component-based code structure appropriately reflects resource costs and is requesting comments on bundling RPM and RTM through potential HCPCS G-codes. A bundled structure could change which activities are reported separately, how incomplete monitoring periods are treated, and how practices forecast program economics.

This is an area for scenario planning, not a new 2027 revenue forecast. CMS is soliciting input, and any final code descriptions, valuations, or billing rules may differ from the concepts discussed in the proposal.

What practices should do before September 14

  • Inventory every person involved. Record who performs setup, education, review, communication, treatment management, escalation, and documentation.
  • Identify employment status. Separate practice employees, independent contractors, vendor personnel, and practitioner work.
  • Map work to codes. Do not assume every remote-monitoring task is a clinical-staff service or billable activity.
  • Model the initiating visit. Estimate scheduling capacity, patient drop-off, documentation changes, and cost.
  • Review vendor agreements. Confirm the scope of software, administrative support, and clinical labor instead of relying on marketing labels.
  • Submit specific comments. Give CMS concrete operational data, patient-access implications, and recommended clarifications through the official rulemaking process.
  • Wait for the final rule before changing claims. Continue following current CPT, CMS, MAC, and payer requirements.

How Positive Check fits into a practice-owned workflow

Positive Check provides automated patient outreach, structured documentation, risk signals, and care-team alerts. The platform can support a practice's remote-monitoring operations, but software use does not by itself make an activity billable or satisfy clinical-staff, supervision, time, device, or interactive-communication requirements.

Practices remain responsible for determining which activities qualify, who may perform them, and whether all requirements are met. See our current 2026 RPM billing guide for the rules in effect today, or request a workflow review.

Official sources

This article is for general educational purposes and is not legal, coding, or billing advice. CMS policy, CPT instructions, Medicare Administrative Contractor guidance, and payer rules should be reviewed for each billing situation. We will update this page when CMS publishes the final CY 2027 rule.

Frequently asked questions

Is the 2027 RPM rule final?

No. CMS-1848-P is a proposed rule. Current RPM and RTM requirements remain in effect while CMS reviews comments and prepares the final CY 2027 Medicare Physician Fee Schedule rule.

When is the deadline to comment on the 2027 proposed rule?

CMS lists September 14, 2026 as the comment deadline for CMS-1848-P. Organizations should use the submission instructions on the official CMS rule page.

Would the proposal ban RPM software vendors?

It does not state a blanket ban on software vendors. The proposed payment restriction focuses on RPM and RTM services performed by clinical staff who are not employed by the billing practice. Practices should separate software, data-transmission, and administrative functions from billable clinical work and evaluate each workflow against the final rule.

Can contracted staff support RPM under current Medicare policy?

Current CMS guidance permits certain RPM services to be furnished by auxiliary personnel under general supervision, and prior CMS rulemaking said auxiliary personnel can include contracted employees for setup and device-supply services. The precise requirements vary by code and payer. The 2027 proposal would materially narrow this approach if finalized as written.

When could the proposed changes take effect?

If finalized, CY 2027 Medicare Physician Fee Schedule policies would generally take effect January 1, 2027. CMS may revise or decline to finalize individual provisions after reviewing public comments.