Remote Patient Monitoring
Realtime monitoring of patients in nonclinical settings with data streams and realtime AI

Remote patient monitoring (RPM), though having many recent breakthroughs, is not a modern concept. It is a catch-all concept that describes any way a patient can be monitored outside of the clinical setting, and has been around for decades, starting from the 1940s when X-Ray images were sent via telephone lines. Now in the modern day it has developed to encompass a suite of devices and digital solutions including wearable devices and modern fitness smartphone applications.
RPM can have broad implications, including improved care access (especially for patients in remote or underserved areas), better care for patients with chronic conditions, and reduced hospital readmissions by allowing timely interventions outside the clinical setting. Developments in cloud computing and artificial intelligence have accelerated what is possible here, enabling faster innovation cycles and more sophisticated clinical decision support. What we discuss in this article lies at the intersection of these breakthroughs.
Background
Recent attempts at similar solutions push the boundaries of real-time healthcare. In academia, there were several notable developments, including a scalable framework for AI-driven RPM developed by Cognizant Technology Solutions in January 2025, as well as a paper on an RPM solution that leverages 5G networks to get latency down to the low double digits, published in March 2025.
Latency here is of paramount importance. When the average response time of emergency services in urban areas of the United States is 8 to 12 minutes, every second counts. Here, we explore a real-world solution that displays a real-time patient monitoring dashboard with intelligent clinical notifications.
Architectural Design Philosophy
The solution follows a hybrid edge-cloud model that balances real-time clinical needs with security and compliance. A low-cost edge device collects vital signs locally while the cloud handles heavy lifting through managed IoT ingestion, real-time streaming analytics, and serverless compute. Security is a top priority: end-to-end encryption, least-privilege access controls, and network isolation protect sensitive health data at every layer.
The cloud backbone manages device fleet connectivity, handles real-time data ingestion at scale, and runs streaming analytics that enrich raw vitals with patient context. A patient profile store personalises risk assessments, while automated certificate rotation and TLS encryption keep data safe in transit. The solution is served through a custom domain with SSL termination behind a CDN distribution, ensuring low-latency access for clinical staff regardless of location.
The real-time patient dashboard is a web application hosted in a containerised environment, consuming data directly from the stream. Clinical notifications are dispatched through a managed pub/sub service, enabling multi-channel alerting to care teams.
System Architecture
The edge device acts as an intelligent sensor hub, using a pulse oximeter to capture heart rate and blood oxygen saturation. A local data pipeline filters noise, smooths readings, and validates measurements against physiological norms before transmitting to the cloud. A simulation mode allows testing of alert scenarios without physical hardware, which is critical for validating clinical thresholds during development.
The device communicates over a standard IoT protocol using an SDK that handles connection management, certificate-based authentication, and reliable message delivery. The wiring setup uses a standard I2C connection, keeping the hardware footprint minimal and reproducible.

Intelligent Analytics
A real-time AI algorithm determines personalised risk scores and clinical indices by combining current vitals from the edge device with longitudinal patient history from the profile store. The system detects anomalies using circadian rhythm baselines, accounting for the fact that a heart rate of 95 bpm means something different at 3am than at 3pm, and triggers multi-channel alerts to care teams when thresholds are breached.
The dashboard surfaces AI-generated natural language summaries alongside raw metrics, giving clinicians actionable context without requiring manual interpretation of the data. Alerts are deduplicated within a rolling time window to prevent alert fatigue, a well-documented problem in clinical environments.

The analytics function processes incoming vitals in real-time, enriches them with patient context, and places the result onto a second stream consumed by the dashboard. Clinical notification processing runs as a separate concern, keeping alert logic decoupled from the analytics pipeline.

Real-World Performance

While academic benchmarks target latencies under 20ms, this system achieves 60–200ms end-to-end in production, a strong result for real-world deployments where network variability, device firmware, and cloud scheduling all introduce jitter. During simulated emergencies, the system maintained sub-second alert delivery while running complex personalised analytics concurrently.
Two key optimisations drive the low-latency performance. First, provisioned concurrency on the analytics function eliminates cold start delays, keeping complex enrichment in the low double-digit millisecond range. Second, enhanced fan-out on the data stream pushes records to consumers rather than requiring them to poll, reducing the time between ingestion and processing.
The RPM solution demonstrates that AI and cloud infrastructure have moved well beyond abstract concepts. They are becoming the operational backbone of real-world health solutions. With a measured average end-to-end latency of ~100ms including edge network overhead, this architecture shows what is achievable today. Healthcare innovators are invited to build on these patterns and extend quality care beyond the hospital walls.