Stop Outsourcing Remote Patient Monitoring This Isn't Advice

CMS's proposed crackdown on billing for outsourced patient onboarding would cut reimbursement for about 75 percent of those services. This move threatens the engine that makes remote patient monitoring scalable for hospitals, potentially stranding billions in technology investments.

Medical Disclaimer: This article is for informational purposes only and does not constitute medical advice. Always consult a qualified healthcare professional before making health decisions.

What is Remote Patient Monitoring's Hidden Dependency?

Key Takeaways

• Outsourced onboarding hides internal skill gaps.
• Vendor-driven enrollment fuels most RPM growth.
• Policy changes can collapse the entire model.

I first noticed this hidden dependency when a hospital I consulted for tried to launch an RPM program without touching its own staff. The plan was simple: buy the devices, sign a contract with a third-party vendor, and let the vendor handle every patient call, education, and data upload. On paper it sounded efficient, but the reality was a silent addiction. The health system handed over the heavy lifting of Medicare education, device set-up, and chronic care enrollment to a call center that existed outside the walls of the hospital.

The core value proposition of "what is RPM healthcare" is supposed to be about continuous data collection, clinician-driven interpretation, and timely interventions. Instead, hospitals have turned that proposition into a transactional service: the vendor calls the patient, explains the program, and ticks a box for billing. This transformation masks an operational skill gap. When a hospital’s internal team never learns how to enroll a patient, they become dependent on a vendor that can disappear at any time. In my experience, this dependency is not about the technology itself - sensors, wearables, and data platforms are still needed - but about shifting the human-intensive work of enrollment and education to a third party.

Because Medicare reimbursement for RPM relies on documented education and device training, the outsourced model captures the billable time that the health system would otherwise need to perform. The vendor’s staff become the "customer acquisition engine" for the RPM program. If that engine stops receiving payment, the whole program stalls, leaving hospitals with expensive devices and no clear path to patient adoption. This hidden dependency is why CMS’s proposal matters: it attacks the financial fuel that keeps the vendor’s call centers running, and consequently threatens the scalability of RPM for the entire health system.

The Silent Engine That CMS Wants to Shut Off

When CMS introduced the rule change, the focus was on specific billing codes - those that reimburse for "educational" and "onboarding" interactions. Those codes are the lifeblood of the outsourced model. By stripping reimbursement, CMS is essentially turning off the financial switch that powers the massive call centers and field teams that enroll patients into RPM programs. In my work with health systems, I have seen how these teams operate 24/7, handling thousands of enrollment calls each month. Without a reimbursable line item, the economics crumble.

The proposed rule does not target the devices themselves - no one is saying the blood pressure cuff or glucose monitor should be banned. Instead, the rule strategically strikes at the human-intensive services layer that makes RPM scalable. Think of it as pulling the plug on the customer acquisition pipeline while leaving the product on the shelf. Hospitals that have invested heavily in RPM technology will suddenly find themselves with a shelf full of devices but no way to get patients to use them.

For vendors, the impact is immediate. The business model that many RPM companies have built over the past decade relies on per-member-per-month fees that include education and onboarding services. Without those fees, the revenue stream dries up. UnitedHealth, CVS, and Kaiser have already rallied against the proposal, arguing that it would cripple the "remote patient monitoring" ecosystem (UnitedHealth, CVS push back on Medicare plan to curb remote patient monitoring). Their pushback underscores how tightly the industry’s revenue and patient acquisition are intertwined.

In practical terms, a hospital that relies on an outsourced vendor will see enrollment numbers plummet the moment the rule takes effect. The vendor’s staff will no longer be able to bill for the time spent walking a patient through Medicare eligibility, device setup, and data transmission instructions. That loss of billable activity translates into fewer hires, fewer call-center slots, and ultimately fewer patients enrolled. The silent engine that fuels RPM growth will sputter, leaving hospitals with costly tech assets and a broken patient pipeline.

Your Chronic Care Management Program Is Built on Sand

From my perspective, many chronic care management programs look solid on the surface, but the foundation is sand. If the enrollment process is handled entirely by a vendor's 1-800 number, the health system does not truly own the patient relationship. The vendor becomes the gatekeeper, and the hospital inherits patients whose onboarding story is undocumented within its own electronic health record.

This disconnect creates a dangerous situation. Clinical teams receive data streams from monitors - blood pressure trends, weight changes, glucose readings - but they have never been part of the conversation that convinced the patient to join the program. When a clinician asks, "Why did you enroll?" the answer often comes from a script read by a vendor rep, not from a trusted provider. If the vendor disappears, the hospital is left holding a stack of devices and a cohort of patients who may not understand the program’s purpose.

The proposed CMS rule shines a light on this hidden weakness. By removing reimbursement for the vendor’s educational calls, the rule forces health systems to confront the fact that they have not built internal competency for Medicare RPM education. In my experience, when hospitals try to quickly internalize the process after a vendor exits, they encounter steep learning curves, compliance pitfalls, and patient attrition. The onboarding conversation is not a simple checkbox; it requires nuanced knowledge of Medicare’s complex billing requirements, patient literacy levels, and the technology’s workflow.

Furthermore, the financial model that vendors used - bundling education, device management, and data analytics into a per-member fee - masked the true cost of patient acquisition. Health systems thought they were paying a flat rate for a complete solution, but the reality was that the bulk of the expense was the vendor’s labor. Once that labor is no longer reimbursable, the cost structure collapses, and the hospital either has to absorb those costs internally or abandon the program altogether.

The Looming RPM In Health Care Reckoning for CFOs

As a CFO watches the balance sheet, the math becomes brutal. Hospitals have poured capital into RPM devices - sensors, platforms, and integration tools - often counting those expenses as long-term assets. However, the operational expense that drove patient acquisition - the vendor’s staffing and call-center operations - has been treated as a variable cost tied to reimbursement. When CMS pulls that reimbursement, the variable cost disappears, but the sunk capital remains.

This creates a sharp decline in projected return on investment (ROI). In my work with finance teams, we model scenarios where the per-member-per-month fee drops to zero. The revenue from Medicare reimbursement evaporates, leaving only the hardware cost and a thin margin from downstream clinical services. Suddenly, the ROI curve that once looked like a gentle slope turns into a steep cliff.

The healthcare B2B sales pitch - "we handle everything" - has been a comfort blanket for many executives. Vendors promised a seamless telehealth bundle that included enrollment, device management, and data analytics for a single price. With the new rule, that promise unravels. CFOs now face a decision: invest heavily to build an internal enrollment team, re-train existing staff, and redesign workflows; or cut RPM growth targets and accept a missed opportunity in chronic disease management.

Building an internal capability is not cheap. It requires hiring or retraining nurses, case managers, and support staff; developing training modules on Medicare rules; and integrating enrollment steps into existing electronic health record workflows. Yet, the alternative - abandoning RPM - means losing a strategic tool for reducing readmissions, improving patient outcomes, and meeting value-based care metrics. The rule forces CFOs to confront a hidden cost that was previously hidden behind a vendor’s billable services.

A Painful But Necessary Pivot for Remote Patient Monitoring

From my standpoint, the only viable path forward is to bring the RPM education and onboarding functions inside the health system. This pivot is painful because it overturns years of reliance on external vendors, but it is necessary for long-term sustainability. The first step is to integrate the enrollment conversation into existing clinical workflows - primary care visits, nursing check-ins, and case-management calls.

Retraining nurses and case managers to own the Medicare RPM conversation does more than replace a vendor; it transforms a cost center into a clinical competency. When a nurse explains the program during a routine appointment, the patient receives the information from a trusted source, increasing adherence and reducing confusion. In my experience, internalizing this process also streamlines documentation, as the enrollment notes sit directly in the patient’s electronic health record, satisfying Medicare’s documentation requirements without a separate vendor interface.

Health systems must also invest in technology that supports this internal model. A user-friendly portal that guides staff through eligibility checks, enrollment forms, and device pairing can replicate the vendor’s efficiency. By embedding these tools into the daily workflow, the system reduces the friction that previously required a dedicated call center.

The payoff is a more resilient RPM program. When policy shifts occur - like the current CMS proposal - systems that own the entire process can adapt quickly, reallocating resources without fearing a loss of reimbursement for outsourced services. Moreover, internal ownership aligns RPM with broader chronic care management goals, enabling tighter coordination between data collection, clinical decision-making, and reimbursement strategies.

In short, the future of remote patient monitoring belongs to those who stop treating it as an outsourced product and start treating it as an innate function of modern chronic care management. By building internal competency, health systems protect their investments, improve patient outcomes, and stay ahead of regulatory changes.

FAQ

Q: Why is CMS targeting outsourced RPM onboarding?

A: CMS believes that billing for vendor-run education and onboarding inflates costs and may not meet Medicare’s intent. By removing reimbursement for those codes, they aim to push health systems to internalize the work.

Q: How are vendors like UnitedHealth and CVS responding?

A: They have publicly pushed back, arguing that the rule would cripple the RPM ecosystem and leave hospitals with unused technology. See the UnitedHealth, CVS push back on Medicare plan to curb remote patient monitoring article.

Q: What happens to hospitals that have already invested in RPM devices?

A: They risk having costly hardware with no clear path to patient enrollment. Without reimbursed onboarding, the devices sit idle unless the hospital builds internal capabilities to drive adoption.

Q: How can a health system transition from outsourced to internal RPM onboarding?

A: Start by training existing nurses and case managers on Medicare RPM rules, embed enrollment steps into regular visits, and deploy internal software tools that guide staff through eligibility checks and documentation.

Q: Will the CMS rule affect all RPM services?

A: The rule specifically removes payment for vendor-run education and onboarding codes. It does not ban the devices themselves, but it will heavily impact any program that relies on third-party staff for those billable interactions.