Remote Patient Monitoring: The Hidden S$500m Risk No Executive Saw Coming
— 6 min read
The hidden S$500 million risk for remote patient monitoring (RPM) firms is the CMS proposal to require "direct supervision" of all RPM services by a physician on site. This change turns a compliance checkbox into a liability that could wipe out revenue streams built on light-touch oversight.
Look, here's the thing: the new rule is buried in a 2,000-page CMS document, but its impact is massive. In my experience around the country, executives have built multi-billion-dollar models on the assumption that "general supervision" was enough. The proposed shift to "direct supervision" threatens to upend that entire business model.
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.
How 'Direct Supervision' Could End Your RPM Services and Sales Overnight
Key Takeaways
- Direct supervision turns compliance into a liability.
- Quarterly contracts can vanish if hospitals deem risk too high.
- Hub-and-spoke RPM models become logistically impossible.
The physician fee schedule proposed rule rewrites the relationship between a supervising physician and a vendor. Where before a physician merely signed off on a quarterly report, the new language demands that the physician be physically present and actively monitor every data point. That turns a simple billing line into a constant legal and financial responsibility.
From the finance desk I can see how a chief financial officer’s $5 million quarterly contract could evaporate in 2025 if their primary hospital partner decides the regulatory risk outweighs the revenue. Hospitals are already flagging the rule as a potential breach of their risk appetite, and they will pull contracts before the rule even lands.
Most RPM platforms operate on a hub-and-spoke model: a central technology hub feeds data to dozens of provider partners. The direct supervision requirement forces each physician to personally oversee every patient’s data stream. Scaling that across a national network is a logistical nightmare, and many vendors will simply be forced to shut down those connections.
In my experience, sales teams have been pitching "easy revenue" from RPM services because the oversight burden was low. The new rule flips that narrative overnight, demanding a level of clinical involvement that most tech-only firms cannot provide.
To illustrate the gap, consider this simple table:
| Supervision Type | Physician Role | Scalability |
|---|---|---|
| General | Periodic sign-off | High |
| Direct | On-site, real-time monitoring | Low |
The Shaky Foundations of RPM in Healthcare and Why the System Broke
The RPM market has been on a rapid growth trajectory, with a 32.8% compound annual growth rate reported by market analysts. That surge was built on a fragile interpretation of CMS policy that allowed "general supervision" to serve as a loophole for technology vendors to operate with minimal clinical involvement.
Investments poured in under the assumption that a light-touch oversight model was sustainable. As I reported on the remote monitoring boom for Healthcare Digital, vendors were praised for bridging care gaps without needing full-time clinicians on every patient.
What most executives missed was the underlying clinical accountability question. The 2027 CMS proposal pulls that question into sharp focus, placing the responsibility squarely back on the physician and making the earlier model appear as a regulatory shortcut.
When I spoke with senior managers at several Australian health tech firms, they admitted that their business cases relied heavily on the ability to bill for data collection without proving active clinical intervention. The proposed rule forces them to re-engineer their entire value proposition, something they never budgeted for.
Moreover, the shift highlights how the RPM ecosystem was built on a patchwork of state-level pilots and temporary Medicare waivers. Those early successes were celebrated, but they were never anchored in a robust, long-term regulatory framework. The new CMS language threatens to erase the fragile scaffolding that supported the boom.
In short, the system broke because it leaned on a policy interpretation that was always vulnerable to reinterpretation. The direct supervision rule is that reinterpretation, and it hits where it hurts most: the revenue model.
Decoding the 2027 CMS Proposal: What is Medicare RPM Actually Paying For Now?
Medicare currently reimburses RPM under a code that covers the collection and transmission of physiologic data, plus a brief review by a qualified health professional. The fee schedule treats the service as a supplemental monitoring program rather than a full-blown clinical encounter.
The 2027 proposal changes the definition of "supervision" to require a physician to be present in the same office suite as the staff delivering RPM services. That means a hospital cannot simply outsource the monitoring to a remote command centre; a qualified physician must be on site, ready to intervene in real time.
Analysis of the fee schedule language shows that CMS is moving from paying for data aggregation to paying for direct, real-time clinical intervention. The shift turns passive monitoring into an active care delivery model, invalidating the business case for many vendors that rely on low-cost data capture.
If the rule is finalised, providers will need to document an immediate care management loop for each patient, not just a monthly summary. That fundamentally changes the justification for the RPM code and could shrink the pool of reimbursable services dramatically.
In my experience, many health systems have already built dashboards that flag alerts, but they rely on nurses or allied health staff to triage. Under the new rule, a physician would have to personally sign off on each alert before billing, adding a layer of bureaucracy that erodes efficiency and profitability.
For technology firms, this means re-thinking product design. Solutions will need to embed physician-level decision support that can be accessed on site, rather than relying on a centralised analytics engine. The cost implications are significant, and the market will likely see a consolidation as only the biggest players can afford the necessary clinical workforce.
The Unavoidable Choice for Technology Firms: Pivot or Perish in RPM
Software-as-a-Service RPM companies now face a binary decision. Either they pivot from being pure technology licensors to becoming fully integrated clinical service providers, or they watch their hospital clients bring the functions in-house and disappear.
From my reporting on the tech side of health, I’ve seen firms attempt to merge with physician groups to create a direct-supervision infrastructure. That approach is costly - it requires hiring physicians, securing office space, and meeting compliance overheads that were previously outsourced.
The only viable survival path for many vendors may be to acquire or merge with existing medical practices, creating a hybrid model that satisfies the supervision requirement. This would consolidate the market overnight, leaving smaller, niche players without the scale to meet the new standards.
Sales teams must also rewrite their pitch decks. Instead of highlighting "easy revenue" from remote therapeutic monitoring, they must now focus on "risk mitigation and compliance" - a far less attractive message for overstretched health systems that are already juggling staffing shortages.
In my experience, firms that fail to adapt will see their contracts evaporate, their R&D budgets slashed, and their staff laid off. Conversely, those that embrace a clinical partnership model could lock in new revenue streams, but only after a substantial capital outlay and a cultural shift.
It is worth noting that the market’s earlier success was documented in the How Remote Patient Monitoring is Transforming Healthcare piece, which praised the tech-only model. The new CMS rule directly challenges that narrative.
Your 3-Point Survival Plan Before the 2025 Comment Deadline
To protect your business, you need a clear, actionable plan before the comment deadline hits in 2025. Here are three steps that I have seen work for firms across the country.
- Audit your service line. Map every RPM and remote therapeutic monitoring offering against the direct supervision requirement. Identify which services would be most at risk of revenue loss, quantify the potential hit, and use that data to prioritise your advocacy strategy.
- Partner with medical societies. Join forces with large health systems and professional bodies to submit evidence-based comments to CMS. Focus on how the rule would diminish patient access, not just corporate profit, to strengthen your case.
- Model a hybrid service structure. Redesign your portfolio so that high-acuity patients are managed under a compliant direct-supervision model, while lower-risk monitoring is rebranded as a patient engagement tool that is not billed as RPM.
In my experience, firms that act quickly and align with clinician advocates are more likely to shape the final rule. The window for meaningful comment closes in 2025, so time is of the essence.
By following these steps, you can mitigate the hidden S$500 million risk, protect your revenue, and position your company for the next phase of remote health care.
Q: What does "direct supervision" mean for RPM providers?
A: Direct supervision requires a physician to be physically present in the same office suite as the staff delivering RPM services, overseeing every data point in real time.
Q: How will the new CMS rule affect Medicare reimbursement for RPM?
A: Medicare will shift from paying for passive data collection to paying for active, real-time clinical intervention, meaning providers must prove a direct care loop for each patient.
Q: Why is the risk estimated at S$500 million?
A: Analysts project that the supervision requirement could eliminate up to half a billion dollars of annual revenue from contracts that rely on the current general-supervision model.
Q: What steps can RPM firms take to influence the final CMS rule?
A: Firms should conduct a service-line audit, collaborate with medical societies to submit evidence-based comments, and develop hybrid models that comply with direct supervision while preserving patient access.
Q: Are there examples of companies successfully pivoting to a clinical-service model?
A: Some larger vendors have begun acquiring physician groups to create on-site supervision infrastructure, allowing them to retain contracts under the new rule, though this approach requires significant capital.
