The Remote Care Revolution Is Stuck in Healthcare’s Old System
Remote patient monitoring (RPM) has become one of digital health's most persuasive promises: care that follows patients beyond hospital walls, detects deterioration earlier, supports chronic-disease management, and reduces pressure on overstretched clinics. From connected blood-pressure cuffs and wearable sensors to virtual wards and AI-supported alerts, the technology is no longer futuristic.
A new perspective article in Healthcare, titled The Unfinished Ecosystem: Why Remote Patient Monitoring Has Matured Unevenly, and What Closing the Gap Will Require, argues that this is precisely the problem. RPM has matured faster than the systems meant to govern, finance, regulate and sustain it.
The article, written by Temitope S. Ajagbe of Safeguard Medix, reviews evidence from 2015 to 2026 across chronic-disease care, telemedicine, AI-enabled monitoring, virtual wards, patient engagement, health equity, reimbursement and liability. It is not a clinical trial or systematic review, but a policy-oriented narrative synthesis drawing on studies from the United States, Italy, Portugal, Romania, Cameroon, Saudi Arabia, Sudan, Israel, Australia and other settings.
The paper identifies four structural gaps holding RPM back: provider economics, professional liability, patient privacy and equity, and patient engagement and adherence. Together, these gaps explain why RPM can succeed in a well-funded pilot, a pandemic emergency or a specialist pathway, but struggle to become routine across health systems.
RPM works in pockets, but scale exposes the gaps
The study highlights a paradox. In selected use cases, the evidence for RPM is increasingly convincing. Pacemaker remote follow-up can reduce costs compared with in-office visits, particularly when patient travel and reimbursed transportation are considered. Hypertension monitoring has been linked with improved outcomes in large retrospective cohorts. Structured heart-failure programmes, virtual wards, post-surgical monitoring and diabetes RPM have shown promise in reducing utilisation, improving follow-up or supporting earlier intervention.
However, when the field is assessed as a whole, the evidence becomes less conclusive. Studies often use different outcome measures, time horizons, cost assumptions and comparison groups. Some focus only on payer costs; others consider provider costs or wider societal costs. Many fail to capture the hidden labour that RPM creates: reviewing data, triaging alerts, documenting findings, contacting patients and coordinating care.
RPM is often sold as efficiency, but in real-settings, it creates a new form of clinical work. Continuous data streams do not manage themselves. A sensor reading becomes valuable only when someone interprets it, knows when to act, and has a system for escalation.
The COVID-19 pandemic revealed both RPM's potential and its fragility. During lockdowns and emergency conditions, telemonitoring and virtual care scaled rapidly in several health systems because regulatory and reimbursement barriers were temporarily relaxed. The article treats this as a natural experiment. When friction was removed, RPM expanded quickly. But as emergency rules ended, many programmes weakened or contracted. The pattern suggests the binding constraint was not whether the technology could operate, but whether ordinary health-system rules could sustain it.
RPM cannot scale on temporary exceptions - it needs permanent payment, workforce, governance and accountability models, the study asserts.
Payment and liability are the weak links
The first major gap is economic. Most healthcare payment systems are still built around visits, procedures and encounters. RPM is different because it is asynchronous, continuous and team-based. It generates work between visits, often across multiple conditions and care settings. If reimbursement only pays for devices or narrow billing categories, providers may lack the resources to staff monitoring properly.
The article argues that reimbursement must follow the work created by data, not the device that produces it. This includes clinical review, alert management, patient outreach, care coordination and engagement support. Without payment for these activities, RPM programmes risk depending on grants, temporary policy windows, philanthropy or overextended staff.
The second gap is liability. RPM turns episodic care into continuous observation. This raises difficult questions. What counts as adequate review of incoming data? How fast must clinicians respond to different alerts? Who is responsible if a warning is missed after hours? What happens when an AI system prioritises one alert and suppresses another?
AI and federated learning make these questions harder. An algorithmic tool may help detect risk, but it also introduces new layers of accountability involving device manufacturers, software vendors, algorithm developers, monitoring services, health systems and clinicians. If a patient deteriorates and an alert was not acted upon, responsibility may be distributed across actors who do not yet share a clear legal framework.
The article calls for profession-wide standards defining alert categories, response times, clinical responsibilities, training requirements and liability across the RPM chain. This is especially urgent as AI-enabled decision support becomes more common in chronic-disease care, mental health monitoring, heart-failure prediction and home-based risk scoring.
For providers, clear rules are not bureaucratic detail; they are a precondition for adoption. Clinicians are unlikely to embrace continuous monitoring if they believe it exposes them to unlimited responsibility for data streams they are not staffed or paid to manage.
Patients must be beneficiaries, not just data sources
The third gap concerns privacy, equity and net benefit. RPM is often described as patient-centred, but the article asks a tougher question: does monitoring consistently make patients better off?
RPM can reduce travel burdens, support home-based care, improve convenience and help clinicians detect deterioration earlier. But it can also expose patients to unclear data-sharing arrangements, surveillance concerns, digital exclusion and uneven access. Modern RPM platforms often involve several actors: device companies, cloud providers, algorithm vendors, monitoring services and clinical teams. Patients may not fully understand who sees their data, how long it is stored, whether it is used to train algorithms, or how it may be shared. Consent forms and privacy notices are often too technical to support meaningful understanding.
Equity is equally important. The article notes that rural and lower-resource hospitals may be less likely to implement RPM, even though their patients could benefit substantially from remote care. Evidence from Cameroon shows that low-cost IoT-based cardiovascular monitoring is technically feasible in a low-resource setting, but infrastructure, regulation and financing remain major constraints. Reviews from Sudan and Saudi Arabia similarly suggest that telemedicine and RPM can expand access only when structural support exists. Without that support, digital care can reinforce existing inequalities.
The fourth gap is engagement and adherence. RPM does not work because a device is deployed. It works when patients remain enrolled, transmit data regularly, understand the process, trust the care team and receive timely responses. The paper argues that engagement should be treated as a core measure of RPM maturity, not a secondary outcome. Programmes should report enrolment rates, active-use rates, data-transmission completeness, alert-response adherence, attrition by subgroup and patient-reported usability. These measures matter because drop-out may be highest among patients with greater social or clinical vulnerability.
A programme that loses high-risk patients is not merely underperforming, but may also be widening the gap between those who can participate in digital care and those who cannot.
The next phase of digital care needs stronger rules
The study recommends the following policy interventions:
- Economic evaluations of RPM need standardisation so health systems can compare costs, benefits, clinician time, caregiver burden and long-term outcomes.
- Reimbursement should pay for the work of monitoring, not simply the device.
- Professional bodies and regulators should define liability and competency standards, especially for AI-mediated RPM.
- Privacy and patient benefit should be built into design from the beginning.
- Engagement and adherence should become primary outcomes and reimbursable activities.
- Underserved settings need deliberate investment in connectivity, affordability, multilingual interfaces, device access and community trust.
Governments shouldn't treat RPM as health-system infrastructure, not just digital innovation. For international organisations and development agencies, it offers a tool to extend chronic care and specialist support into underserved settings, but only if equity is designed into deployment. For businesses and investors, opportunities exist in virtual wards, AI triage, cybersecurity, patient engagement tools, low-cost devices, federated learning and remote-care platforms.However, commercial success will depend increasingly on evidence, reimbursement clarity, interoperability and public trust.
The article also carries a warning for the Global South. RPM could help overcome shortages of specialists, long travel distances, weak continuity of care and overstretched hospitals. However, if introduced without financing, regulation, privacy safeguards and local engagement, it could become another layer of digital inequality.
The author notes that the study is a perspective article, not an original empirical study or systematic review. Its literature synthesis is representative rather than exhaustive. Some claims about the post-pandemic contraction of RPM programmes remain plausible but need stronger long-term evidence.
Overall, RPM's future will be decided by whether health systems can build the payment models, liability rules, privacy protections, equity safeguards and engagement structures that make monitoring trustworthy and sustainable. The next challenge is whether policy can catch up with technology. Until it does, RPM will remain powerful in pockets, promising in pilots and unfinished at scale.
- FIRST PUBLISHED IN:
- Devdiscourse
Google News