What Is Changing With RPM Billing in 2027?
As of September 2026, CMS has proposed prohibiting Medicare payment for remote patient monitoring (RPM) and remote therapeutic monitoring (RTM) services performed by third-party contracted clinical staff under the CY 2027 Physician Fee Schedule proposed rule (CMS-1848-P). If finalized, only clinical staff who are direct employees of the billing practice would be eligible to furnish RPM and RTM services for Medicare billing purposes starting January 1, 2027. The proposal also adds new requirements for an initiating visit, extends the established-patient rule to RTM, and explores consolidating 17 existing RPM and RTM billing codes into four new G-codes.
Third-party vendor ban: Practices could no longer bill Medicare for monitoring performed by contracted staff from outside RPM companies. Staff must be direct employees of the billing practitioner under general supervision.
New initiating visit requirement: A separately billable face-to-face or telehealth visit must occur before RPM or RTM services begin, with documented clinical appropriateness assessment and patient consent.
Comment deadline: The 60-day public comment period closes September 14, 2026. CMS has specifically requested data on how prevalent outsourced RPM arrangements are and how this restriction might affect patient access.
How the Proposed RPM Outsourcing Ban Works
Under current Medicare rules, physician practices can outsource RPM and RTM monitoring to third-party companies. These vendors supply clinical staff who review transmitted device data, contact patients by phone, and log the management time that the billing practice submits to Medicare. The billing practitioner does not need to employ the monitoring staff directly. CMS has allowed this arrangement under the “incident to” billing framework, where services furnished by clinical staff under a physician’s general supervision can be billed under the physician’s NPI.
The CY 2027 proposed rule would close that arrangement. CMS states that outsourcing RPM and RTM to third-party companies “can fragment care, lead to insufficient involvement and oversight of the billing practitioner, or result in services that do not actually represent or facilitate all required aspects of RPM or RTM services.” Under the proposal, clinical staff performing monitoring must be direct employees of the billing practitioner or practice. They do not have to work at the practice’s physical location, but they must meet all “incident to” requirements under 42 C.F.R. section 410.26, including direct employment and general supervision by the billing provider.
CMS is also proposing a mandatory initiating visit before any RPM or RTM services begin. The billing practitioner must conduct a face-to-face or telehealth encounter to assess clinical appropriateness, discuss the monitoring plan with the patient, and obtain consent. This visit is separately billable but must occur before the first monitoring claim is submitted. For RTM, CMS proposes extending the established-patient requirement that already applies to RPM, meaning new patients cannot be enrolled in RTM without a prior relationship with the billing provider.
Separately, CMS is seeking comment on whether to consolidate all 17 existing RPM and RTM CPT codes (99453, 99454, 99445, 99457, 99458, 99470, and their RTM counterparts) into just four new G-codes. Each consolidated code would bundle device supply, data transmission, and at least 20 minutes of treatment management with required real-time patient interaction into a single billing unit. This is a comment solicitation, not a formal proposal, but it signals CMS’s direction for simplifying remote monitoring billing.
Who Does the 2027 RPM Change Affect?
The outsourcing ban affects any practice that currently contracts with a third-party company to perform RPM or RTM monitoring and bills Medicare for those services. Family medicine practices are among the highest users of RPM for chronic disease management. Blood pressure monitoring for hypertensive patients, glucose monitoring for diabetic patients, and weight tracking for patients with heart failure are standard RPM use cases in primary care.
In our experience matching family medicine providers with billing partners, many small to mid-size practices rely on third-party RPM vendors because they lack the internal staff to monitor transmitted data, make the required patient contact calls, and log the clinical time. For these practices, the vendor handles the operational side while the practice bills Medicare. If the outsourcing ban is finalized, that model ends.
Larger health systems and ACOs with employed clinical staff may absorb the change more easily. They already have the infrastructure to assign monitoring tasks to in-house care coordinators or medical assistants. Independent family medicine practices face a harder choice: hire staff to run the program internally, restructure vendor arrangements so vendor staff become practice employees, or stop billing RPM entirely. The financial stakes are significant, as the broader 2027 family medicine Medicare payment changes already include a conversion factor reduction that puts additional pressure on practice revenue.
RPM vendors are also directly affected. Companies whose business model depends on providing contracted clinical staff to billing practices would need to restructure as staffing agencies or employment intermediaries, or pivot to technology-only roles where they supply devices and software but not monitoring personnel.
How Will This Affect Family Medicine RPM Revenue?
For a family medicine practice with 100 Medicare patients enrolled in RPM, the monthly revenue from monitoring services can reach $10,000 to $18,000 depending on the code mix and patient engagement levels. The table below shows the 2026 national average reimbursement for each RPM code and the approximate monthly revenue at stake for a 100-patient panel.
| CPT Code | Description | 2026 Avg. Rate | Monthly Revenue (100 patients) |
|---|---|---|---|
| 99453 | Setup and education (one-time) | $22 | $2,200 (at enrollment) |
| 99454 | Device supply, 16+ days data | $47 | $4,700 |
| 99457 | First 20 min. management | $52 | $5,200 |
| 99458 | Each additional 20 min. | $41 | $4,100 (at 50% utilization) |
Estimated figures based on 2026 national non-facility Medicare payment rates. Actual reimbursement varies by GPCI. Monthly revenue assumes all 100 patients meet the 16-day data threshold and receive at least 20 minutes of management time.
The revenue risk is not the reimbursement rate itself. CMS is not proposing to cut RPM payment amounts. The risk is operational: if a practice cannot staff the monitoring function with direct employees, it loses the ability to bill these codes entirely. A practice generating $10,000 per month in RPM revenue through an outsourced vendor drops to zero RPM revenue on January 1 if it has no internal monitoring staff in place. That is the scenario CMS is creating, intentionally, to force monitoring back under the billing provider’s direct control.
What Should Your Practice Do Before January 2027?
The comment deadline is September 14, 2026, and the final rule is expected by November. If finalized as proposed, the outsourcing ban and initiating visit requirement take effect January 1, 2027. These steps should begin now.
1. Audit your current RPM staffing model. Identify whether the clinical staff performing your RPM monitoring are direct employees of your practice or contractors supplied by a third-party vendor. If they are contractors, the current billing arrangement will not survive finalization.
2. Model the financial impact of losing RPM revenue. Calculate your monthly RPM billing by code (99453, 99454, 99457, 99458, and the 2026 codes 99445 and 99470). Compare this against the cost of hiring internal staff to perform the same monitoring. If the math does not work, you need to know that before January, not after.
3. Evaluate restructuring your vendor relationship. Some vendors may offer to transition their monitoring staff into your practice as direct employees or to operate under a staffing agency model. Review whether the proposed arrangement satisfies the direct employment and “incident to” requirements CMS is proposing.
4. Establish your initiating visit workflow. The new requirement means every RPM and RTM patient must have a documented face-to-face or telehealth visit with the billing provider before monitoring begins. Build this into your onboarding process now, including consent documentation and clinical appropriateness assessment.
5. Prepare for potential code consolidation. While CMS has not formally proposed replacing the 17 existing RPM and RTM codes with four new G-codes, the comment solicitation signals this is under active consideration. Track the final rule for any structural changes to the code set.
6. Submit a public comment by September 14. CMS is specifically requesting data on how widespread outsourced RPM arrangements are and how the ban would affect patient access. If your practice relies on a vendor, your experience is exactly the type of input CMS is collecting.
7. Coordinate with your billing company. If you outsource your medical billing (separate from RPM monitoring), confirm that your billing partner understands the proposed RPM changes and can update claim submission logic, code mapping, and denial management for the new requirements.
Providers often come to us after a billing change has already hit their revenue. Getting matched with a billing company that handles RPM transitions proactively is what we do. Connect with a vetted family medicine billing partner within 30 minutes at no cost.
Common RPM Billing Mistakes to Avoid During the Transition
The first mistake is assuming the outsourcing ban will not be finalized. CMS proposed a narrower version of RPM restrictions in 2019 and pulled back after public comment. That history gives some practices a false sense of security. The 2027 proposal is broader, backed by OIG enforcement findings including a $14.9 million settlement connected to false RPM claims, and aligned with a clear regulatory trend toward tightening “incident to” billing. Planning as if the ban will be finalized is the safer approach. If CMS softens the proposal, your practice adjusts upward, which is the easier direction.
The second mistake is continuing to bill RPM through an outsourced vendor past the effective date and hoping the claims process normally. If the final rule mirrors the proposal, Medicare will deny these claims. Worse, retroactive enforcement under the False Claims Act is a real risk for practices that bill RPM without meeting the direct employment standard. The OIG has specifically identified RPM as an enforcement priority.
A third mistake is conflating your RPM vendor (the company that supplies devices and monitoring staff) with your medical billing company (the company that submits your claims to Medicare). The outsourcing ban targets the clinical monitoring function, not the claim submission function. You can still outsource your medical billing. You cannot outsource the monitoring itself for Medicare billing purposes.
Finally, some practices assume that dropping RPM is a clean exit with no downstream effects. RPM contributes to quality measures under MIPS, supports chronic care management documentation, and strengthens the data trail for E/M coding at higher levels. Losing RPM does not just reduce one revenue line. It weakens the documentation infrastructure that supports several others.
In-House RPM vs. Outsourced Billing Support
The CMS proposal draws a sharp line between two types of outsourcing that practices often conflate. Clinical monitoring (reviewing device data, contacting patients, logging management time) must be performed by direct employees under the proposed rule. Medical billing (submitting claims, managing denials, handling payer follow-up) remains fully outsourceable. Your billing company is not your RPM vendor, and the proposed rule does not affect your ability to use one.
Across the billing companies we vet, a recurring pattern is that practices running RPM programs in-house already generate cleaner claims and fewer denials than practices outsourcing to vendors. The reason is straightforward: when the monitoring staff are embedded in the practice, they have direct access to the patient chart, can coordinate with the provider in real time, and document in the same EHR. Vendor-supplied staff often work in separate systems and submit documentation that does not align with the practice’s charting standards, creating denial triggers.
For practices that need to bring monitoring in-house, the staffing cost is real. A dedicated medical assistant or care coordinator handling RPM for 100 patients at $18 to $22 per hour represents roughly $3,000 to $3,800 per month in labor. Against $10,000 or more in monthly RPM revenue, the margin works for most panel sizes above 50 patients. Below that threshold, practices should evaluate whether the program justifies the overhead.
One question we hear constantly from practice managers is whether their billing company can help them set up an in-house RPM workflow. The answer depends on the billing partner. Some billing companies in our network offer practice consulting that includes RPM program design, EHR configuration, and staff training alongside their core claim submission services. Others handle claims only. Matching with the right partner matters more during a transition like this than during steady-state billing.
Frequently Asked Questions
Is CMS banning remote patient monitoring entirely?
CMS is not banning RPM. The proposed rule restricts who can perform the monitoring for Medicare billing purposes. Practices can still run RPM programs, but the clinical staff doing the monitoring must be direct employees of the billing practice, not contracted through a third-party vendor.
Does the outsourcing ban apply to RPM device vendors?
The ban targets clinical staffing, not device supply. Companies that provide RPM devices, software platforms, or data transmission infrastructure are not affected by the direct employment requirement. The restriction applies only to the clinical staff who review data, contact patients, and log management time.
Can my RPM vendor staff become employees of my practice?
Potentially. Some vendors may restructure so their monitoring staff are employed by the practice under a staffing or employment agency arrangement. However, the arrangement must satisfy CMS’s “incident to” requirements, including direct employment and general supervision by the billing practitioner. Review any proposed arrangement with a compliance advisor before implementation.
Does this change affect commercial insurance RPM billing?
The proposed rule applies to Medicare Part B only. Commercial payers and Medicare Advantage plans set their own RPM billing policies. However, commercial payers often follow CMS’s lead on coverage and documentation requirements, so practices should monitor for similar policy shifts from their major payers.
What happens to my existing RPM patients on January 1?
If the ban is finalized, any RPM services performed by third-party contracted staff after January 1, 2027, would not be billable to Medicare. Patients can remain in the RPM program, but the monitoring must transition to direct employees before claims can be submitted. The initiating visit requirement applies to new enrollments, not existing patients already in an RPM program.
When will CMS finalize the 2027 physician fee schedule?
The final rule is expected in November 2026, with changes taking effect January 1, 2027. The 60-day public comment period closes September 14, 2026. CMS may revise or withdraw the outsourcing ban based on comments received, though the enforcement trend and OIG findings suggest the agency is committed to tightening RPM billing standards.
Next Steps
For the full picture of 2027 billing changes affecting family medicine, including the conversion factor reduction and MIPS transition to Value Pathways, review our related coverage.
If your practice currently outsources RPM monitoring, start the financial modeling and staffing evaluation now. Waiting for the final rule in November leaves less than 60 days to build or restructure an in-house monitoring program.
If your billing arrangement is not keeping pace with CMS updates, get matched with a billing company that handles RPM claim submission and can advise on program restructuring, at no cost and with quotes returned within 30 minutes.
The RPM outsourcing ban is one of the most disruptive changes in the CY 2027 proposed rule for family medicine practices. We match providers with billing companies that understand these transitions and help protect your revenue through them.
