Remote Patient Monitoring

Overview

Remote Patient Monitoring (RPM) is the core workflow of the vitalera platform. It enables healthcare professionals to monitor patient health data collected from devices, questionnaires, and manual entries, all from a centralized dashboard. The same infrastructure powers wellness monitoring, sports health tracking, and research data collection. The same workflow applies whether you are monitoring post-surgical patients, tracking employee wellness metrics, or collecting wearable data from athletes.

Workflow Steps

1. Enrollment

1. Create a monitored patient via the API or web application
2. Assign the patient to a care plan
3. Patient receives a registration link and sets up their mobile app

2. Device Setup

1. Patient pairs Bluetooth medical devices through the mobile app
2. Wearable devices (Garmin, Fitbit) are linked through OAuth flows
3. Devices automatically sync health data to the platform

3. Data Collection

Data flows into vitalera through multiple channels:

Source	Method	Examples
Bluetooth devices	SDK integration	Blood pressure, SpO2, temperature, weight, glucose
Wearables	API integration	Heart rate (Garmin, Fitbit), activity data
Questionnaires	In-app completion	PHQ-9, symptom surveys, daily check-ins
Manual entry	Patient input	Symptoms, medication adherence

4. Automated Alarms

The platform evaluates incoming observations against configured alarm thresholds:

• Threshold alarms: Trigger when a value exceeds or falls below defined limits
• Trend alarms: Trigger on significant changes over time
• Missing data alarms: Trigger when expected measurements are not received

5. Review & Action

Healthcare professionals use the web dashboard to:

• Review triggered alarms and prioritize patients
• Validate patient-submitted observations
• View historical trends and charts
• Communicate with patients via secure messaging
• Schedule video call appointments

6. Reporting

• Export patient data in CSV format
• Track billable time for CPT code reporting
• Generate clinical reports for care coordination

Integration Points

• API: Full programmatic access to all RPM data
• Webhooks: Real-time notifications for new observations and alarms
• SDKs: Native device integration for custom mobile apps

For non-clinical use cases

Wellness and sports platforms use the same enrollment, device, data, alert, and review flow described above but with different terminology: participants instead of patients, coaches instead of professionals, and programs instead of care plans. The underlying API resources and data pipeline are identical regardless of the domain.