Remote patient monitoring reimbursement: wider funnel, fewer vendors

Lower thresholds make more patients billable

Legal analyses tracking the rulemaking, including from McDonald Hopkins, describe CMS lowering the time thresholds required to bill remote patient monitoring. Benesch characterized the broader package as comprehensive updates to both RPM and remote therapeutic monitoring reimbursement. The practical effect is straightforward: patients who previously fell short of the minimum data transmission days or the minimum minutes of management time in a given period can now generate reimbursable services.

That matters most for the patients programs quietly wrote off. Intermittent users, patients enrolled mid-month, post-discharge cohorts monitored for short windows and anyone whose adherence was good but not quite good enough were effectively unbillable under the old structure. Finance teams that modeled RPM contribution margin on strict adherence assumptions should rebuild those models with the revised thresholds before signing off on next year's enrollment targets.

One caution for anyone briefing a board this quarter: the exact old and new thresholds, and the specific CPT codes affected, should be confirmed against the Federal Register text rather than secondhand summaries. Law firm alerts have been reliable directional indicators through this cycle, but the operational math depends on precise numbers.

This is a procurement and staffing decision disguised as a billing update.

The third-party monitoring restriction is the real disruption

MedCity News reported in July 2026 on CMS moving to shut down third-party remote patient monitoring arrangements. This is the provision that should be on the CIO and CMO agenda, because the dominant market structure for hospital RPM has been exactly that: a vendor supplies the devices, runs the connectivity, staffs the monitoring queue, escalates to the practice when thresholds are breached, and the practice bills.

If billing eligibility narrows to services furnished by the billing practitioner's own clinical staff, that entire arrangement has to be rebuilt. The components do not transfer cleanly. In-house monitoring requires licensed staff coverage during defined hours, an escalation protocol that an auditor would recognize, device procurement and reverse logistics, patient onboarding support, and device data flowing into the EHR as discrete, documentable values rather than as a parallel vendor dashboard.

Before any of that can be planned, legal teams need to establish whether the restriction is a billing-eligibility limitation or a broader prohibition on the arrangement itself. Those two readings produce very different remediation plans, and they point to different clauses in existing vendor contracts.

Senate pushback means the policy is still moving

ACOFP reported in early October 2026 that a group of senators is pressing CMS to reconsider its RPM changes. That is a useful signal for planning. It means the provisions are publicly contested, that CMS may face pressure to delay or soften enforcement, and that a health system which tears up a functioning vendor relationship too quickly could find itself rebuilding capability it did not need to rebuild.

It is not, however, a reason to wait. The asymmetry favors preparation. Organizations that map their exposure now and negotiate transition terms lose very little if the rule is softened. Organizations that assume a reversal and are wrong face a scramble with no staffing model and a vendor holding the device inventory. The letter, its signatories and the specific objections raised are worth pulling directly, because the substance of the objections tends to predict which provisions CMS is most likely to adjust.

The outcomes evidence is getting harder, not easier

Telehealth.org noted that CMS expanded RPM billing at roughly the same moment new research raised questions about RPM outcomes. For boards being asked to approve in-house monitoring staff, that timing is awkward. The investment case for RPM has often rested on avoided readmissions and earlier intervention, and a weakening evidence base makes that case harder to defend against competing capital requests.

Leaders should treat this as a reason to tighten internal measurement rather than to retreat. Programs that can show their own utilization, escalation and outcome data for specific conditions are in a far stronger position than programs relying on vendor-supplied aggregate claims. The study in question, its journal and the population it examined should be identified and read before anyone cites it in either direction.

Vendor viability is now part of the risk calculation

The capital environment compounds the operational risk. Telehealth.org put digital health funding at roughly $7.4 billion in 2026, with AI absorbing a growing share of investor attention, and Rock Health data reported through Healthcare Dive shows capital concentrating into fewer companies. CB Insights published a fresh quarterly read on the sector within the last week. The pattern across those sources is consistent: smaller, undifferentiated vendors are being squeezed out of the funding market.

Those are precisely the partners most likely to fail mid-contract, and a regulatory change that undercuts their core business model accelerates the problem. A monitoring vendor that loses billing-eligible status for its service loses its revenue logic at the same moment it struggles to raise. Health systems should be stress-testing contracts now for termination rights, transition assistance obligations, device ownership, and data export in a usable format. The contract question to answer first is simple: if this vendor stops operating in 90 days, who owns the devices in patients' homes and who holds the monitoring data?