Collab-Care: SmartNurse RPM Platform

The biggest obstacle in Remote Patient Monitoring isn't the data capture; it's the data isolation. Every medical device manufacturer builds its own siloed application ecosystem. For a nurse managing 50 patients, checking 50 different apps is impossible. We designed the SmartNurse platform to be a unifying aggregator. The dashboard connects via secure APIs and direct Bluetooth LE profiles to pull data from watches, glucose monitors, and weight scales. This data is normalized into a unified structure within MongoDB, giving providers the 360-degree view they need to make rapid, informed decisions.

Our real-time layer, powered by NestJS and WebSockets, ensures that critical metrics are propagated instantly. When a wearable watch detects a fall, the 'Live View' dashboard doesn't just receive a passive log; it visually changes: the patient’s card pulses red, an audible alert triggers, and actionable response buttons ('Acknowledge', 'Call Watch', 'Dispatch') appear immediately. This immediate visibility is what drives the 75% response time improvement.

Because healthcare is mobile, the patient-facing component must be equally reliable. We developed React Native mobile applications that focus on simple data gathering and patient engagement. These apps handle Bluetooth device connectivity and feature robust 'offline-first' functionality. Data captured when connectivity is poor (like inside a large hospital or rural area) is queued locally and synced automatically as soon as a network is detected, ensuring data continuity essential for medical compliance.

Collab-Care's business model relies on B2B licensing for healthcare organizations (the 'Corporate' user). This model has complex scalability requirements: a clinic may start with 20 monitored patients and grow to 500 within a few months, varying the required support and feature tiers. Managing this manually would be impossible. We integrated the Stripe Billing API to fully automate the corporate subscription lifecycle.

Corporate administrators log in to their portal to select subscription packages, manage licenses, and add team members. We utilized Stripe's metered billing features where 'Active Patient' counts are reported as usage throughout the billing cycle. Stripe automatically adjusts the upcoming invoice based on the maximum usage or proration logic we defined. This ensures fair billing: a corporate client only pays for the active monitoring capacity they actually utilize, reducing friction and improving client retention.

The core technology challenge was interoperability. While FDA/Health Canada approved devices were crucial, the emerging request was to also include consumer-grade wearables for general wellness monitoring (which are noted as monitors only in our system’s disclaimer). We faced a chaotic mix of Bluetooth data profiles, varied vendor API schemas, and disparate data transmission frequencies.

Our solution was to build a sophisticated device abstraction layer within the NestJS backend. This adapter pattern allows us to map conflicting data points (e.g., one device reports temperature in Celsius every minute; another reports only when it spikes; a third only supports Fahrenheit) into a single, canonical 'VitalSign' object structure used throughout the frontend. This approach makes the frontend agnostic to the device manufacturer, simplifying dashboard maintenance and allowing us to rapidly onboard new devices without re-architecting the system.