How long did this project take from start to launch?

The full engagement ran six months, covering architecture, the BLE abstraction layer, ABDM compliance work, and rollout to the first 500+ patients. That timeline included building and passing certification for India's ABDM framework, which is typically the longest pole in a healthtech project like this.

What happens if a patient loses internet connectivity mid-reading?

The mobile app buffers vitals locally and automatically retries and reconciles the data once connectivity returns, so clinicians never see a gap in the record even during rural mobile dropouts. This was a specific design requirement given the wide range of home network conditions across the patient base.

Does this approach work if we're not targeting the Indian market or ABDM compliance specifically?

The core architecture — the BLE device abstraction layer, anomaly detection with cohort-based thresholds, and the three-layer platform split — is regulation-agnostic and portable to other markets. ABDM was this client's specific compliance target, but the same consent, encryption, and audit-log patterns map cleanly onto frameworks like HIPAA or GDPR-driven health data rules.

How did you stop clinicians from just ignoring the alerts, like they did with the early prototype?

We replaced flat, one-size-fits-all thresholds with cohort-tuned anomaly detection, so a reading normal for one patient's baseline correctly triggers an alert for another, which pushed alert precision to 93%. That shift from raw connectivity to clinical intelligence is what took the dashboard from being ignored within days to becoming the team's daily primary tool.

Back to case studies

HealthTech & IoTSaaS Application DevelopmentAI-Powered Software

IoT Healthcare Remote Monitoring

Building a connected care ecosystem that bridges Bluetooth medical devices with clinical dashboards, giving remote care teams the same visibility they would have on a hospital ward — without requiring a single extra nurse on site.

Hospital-grade care delivered remotely for 500+ patients

Client

Confidential — HealthTech startup

Industry

HealthTech & IoT

Timeline

6 months

Technologies

8+ tools

The Challenge

!The client's monitoring program still ran on paper vitals charts and phone call check-ins, which meant clinicians had no way to see a patient's blood pressure, oxygen saturation, or ECG trend until the next scheduled call, sometimes 24-48 hours after a warning sign appeared. This delay was especially dangerous for maternal and chronic-care patients whose conditions could deteriorate quickly between check-ins.

!The market offered dozens of Bluetooth Low Energy medical devices from different manufacturers (blood pressure cuffs, pulse oximeters, portable ECG monitors), each with its own pairing protocol, data format, and firmware quirks. Without a standardised integration layer, onboarding a new device model required weeks of custom development, which made it impossible to scale device choice to patients across different regions and price points.

!India's Ayushman Bharat Digital Mission (ABDM) framework mandated strict rules around patient consent, data ownership, and interoperability with the national health data ecosystem, and the client had no existing infrastructure to satisfy any of it. Every vitals reading, consent artifact, and access log needed to be encrypted end-to-end and auditable, which is a materially different bar than a typical consumer health app.

!Maternal-care and chronic-disease patients needed to be monitored continuously in their homes rather than during periodic clinic visits, but many came from lower digital-literacy backgrounds and could not be expected to operate a complex app or manually log readings. The monitoring experience had to be close to zero-touch for the patient while still capturing clinical-grade data.

!Clinical teams were already stretched thin, and early prototypes that simply streamed every reading to a dashboard triggered constant, low-value notifications. Doctors began ignoring alerts altogether within days, which meant the system needed intelligence, not just connectivity, to be trusted in daily practice.

!Network conditions in the patients' homes varied enormously, from strong urban broadband to intermittent rural mobile data, and the platform could not silently drop vitals data during connectivity gaps. Any monitoring solution needed to buffer, retry, and reconcile data without clinicians ever noticing a gap in the record.

!The client's existing backend had been built as a quick MVP with no real data model for multi-device, multi-patient, multi-clinician relationships, and it could not support role-based access, audit trails, or the concurrency needed once patient volume grew past a small pilot group.

!Security reviewers and hospital partners required proof of encryption at rest and in transit, granular consent revocation, and clear data-retention policies before they would refer patients into the program, and none of this had been designed into the original product.

Our Solution

We architected a three-layer platform separating concerns cleanly: a Patient Mobile App for passive data capture, a Secure Cloud API for ingestion and business logic, and a Clinician Dashboard for review and intervention, so each layer could evolve and scale independently as device and patient volume grew.

We built a BLE device abstraction layer that normalised the disparate data streams, pairing flows, and error states from multiple medical device vendors into one internal schema, which let the client onboard a new device model in days instead of weeks and freed the roadmap to support additional vendors without re-architecting the ingestion pipeline.

We implemented ABDM-compliant consent and data-sharing workflows from the ground up, including granular, revocable patient consent records, end-to-end encryption of vitals and identity data, and immutable audit logs for every access event, satisfying both regulatory requirements and hospital partner security reviews.

We designed a real-time transmission pipeline built on WebSockets with local buffering on the mobile app, so vitals reached the clinician dashboard in under five seconds under normal conditions while still queuing and reconciling data automatically during connectivity drop-outs in rural areas.

We built an intelligent anomaly detection layer with configurable clinical thresholds per patient cohort, so a reading that was normal for one patient's baseline could correctly trigger an alert for another, cutting notification noise dramatically compared to the flat-threshold prototype.

We delivered a dedicated pregnancy monitoring module with a customised risk-scoring model tuned to maternal vitals patterns, giving maternal-care teams an at-a-glance risk trend rather than raw numbers they had to interpret manually during a busy shift.

We re-platformed the backend onto PostgreSQL and Redis with a proper multi-tenant data model supporting role-based access for doctors, nurses, and administrators, enabling the system to scale from a pilot cohort to 500+ concurrently monitored patients without a rewrite.

We ran the mobile app through structured usability testing with actual patients from the target demographic, simplifying onboarding to a two-tap device pairing flow and removing nearly all manual data entry, which was essential for adoption among lower digital-literacy users.

Measurable Impact

Patients monitored remotely

500+

Continuous home monitoring now replaces frequent in-person hospital visits for maternal and chronic-care cohorts.

Data latency

< 5 seconds

Vitals travel from the patient's BLE device to the clinician dashboard in near real time under normal network conditions.

Regulatory compliance

ABDM certified

The platform fully complies with India's Ayushman Bharat Digital Mission standards for consent, encryption, and interoperability.

Alert accuracy

93% precision

Cohort-tuned thresholds cut false-positive alerts sharply while still capturing every clinically significant event.

Device onboarding time

Weeks to days

The BLE abstraction layer turned custom, multi-week vendor integrations into a standardised, days-long process.

Delivery timeline

6 months

The full three-layer platform, from architecture to ABDM certification, was delivered in a single six-month engagement.

Clinical trust

90%+ daily active use by care teams

Doctors moved from ignoring notifications within days to relying on the dashboard as their primary monitoring tool during nearly every shift.

“SystimaNX translated complex clinical requirements into a platform our doctors actually trust. The real-time dashboard changed how our care team works every single day, and the ABDM compliance work meant we could finally bring hospital partners on board without months of security back-and-forth.”
C
Clinical Operations Director
HealthTech Platform, India (NDA)

Technology stack

React NativeNode.jsBLE SDKPostgreSQLRedisWebSocketsAWSABDM APIs