Platform Features
Vantrexia is a HIPAA-compliant Remote Patient Monitoring (RPM) platform designed for medical practices that need to monitor patients with chronic conditions at scale. The platform connects medical devices, automates billing workflows, and delivers real-time clinical intelligence — all behind AES-256 encryption and comprehensive audit logging.
Vantrexia's exception-based triage model enables a single clinician to monitor up to 100 patients simultaneously. The platform surfaces only the patients who need attention, reducing alert fatigue and maximizing clinical efficiency.
Core Features
The platform is organized into six primary modules, each designed to handle a specific aspect of remote patient monitoring operations:
Monitor system health, patient vitals, transmission rates, and clinical KPIs from a single command center. Auto-refreshing charts update every 30–60 seconds with role-based views for admins, clinicians, and billing staff.
Support a 1:100 clinician-to-patient ratio with intelligent risk scoring. Patients are automatically ranked by severity (Critical → Warning → Normal → No Data) so clinicians focus on those who need immediate attention.
Automatically generate and track claims for CPT codes 99453, 99454, 99457, 99458, and more. The smart billing engine runs every 4 hours, with 13 built-in report endpoints for revenue analytics.
Create patients manually or import them directly from eClinicalWorks. All protected health information is AES-256 encrypted at the field level with full FHIR R4 compliance and conflict resolution.
Deliver real-time alerts via Firebase Cloud Messaging with HIPAA-safe payloads. PHI is automatically sanitized before transmission, and per-patient threshold configuration ensures relevant alerting.
End-to-end AES-256 encryption, comprehensive audit logging, role-based access control, automatic session management, and full BAA support. Every PHI access is recorded and retrievable.
How It All Fits Together
Vantrexia operates as a cohesive system where each module feeds data into the others. Here is the typical data flow through the platform:
Patient Enrollment
Patients are created manually or imported from eClinicalWorks. The system assigns a FHIR R4-compliant resource ID and encrypts all demographic data with AES-256. An external identifier links the patient back to their EMR record.
Device Data Collection
Connected devices (blood pressure monitors, pulse oximeters, glucose meters, weight scales) transmit vital sign readings through the observation pipeline. Each reading is validated, stored as a FHIR Observation resource, and checked against the patient's configured alert thresholds.
Triage & Alerts
The triage engine continuously evaluates readings against per-patient thresholds. Breached thresholds generate alerts, trigger push notifications, and update the patient's risk score (0–100). Clinicians see a priority-ranked triage dashboard with color-coded severity indicators.
Clinical Review
Clinicians review flagged patients, acknowledge alerts, document interventions, and escalate as needed. Each action is audit-logged with timestamps and user attribution for compliance documentation.
Automated Billing
The billing engine automatically generates CPT-coded claims based on device transmissions, clinical time, and escalation events. A daily Celery task at 2:00 AM processes device-based billing, while the smart engine runs every 4 hours to catch additional billable activities.
Key Platform Metrics
The dashboard surfaces the following real-time KPIs to give clinical and administrative staff instant visibility into operations:
| Metric | Description | Refresh Rate |
|---|---|---|
| Active Patients | Total patients currently enrolled in RPM monitoring | 30 seconds |
| Vital Alerts | Count of unacknowledged threshold breaches | 30 seconds |
| Transmission Rate | Percentage of expected device transmissions received | 60 seconds |
| System Health | Status of Database, eCW, Celery, and FHIR services | 10 seconds |
| Triage Queue | Patients by risk level (Critical, Warning, Normal, No Data) | 30 seconds |
| Billing Pipeline | Claims by status: pending, submitted, paid, denied | 60 seconds |
Security & Compliance
Every feature in Vantrexia is built with HIPAA compliance at its foundation. Security is not an afterthought — it is embedded into every API endpoint, database query, and UI component.
Encryption: All PHI fields are encrypted at rest using AES-256 via django-encrypted-model-fields. Data in transit is protected with TLS 1.3.
Access Control: Role-based permissions (Admin, Clinician, Staff, Billing) enforce least-privilege access. Every API endpoint requires JWT authentication with 15-minute token expiry.
Audit Logging: Every PHI access, modification, export, and deletion is recorded with timestamps, user IDs, IP addresses, and action descriptions. Audit logs are immutable and retained for 7 years.
Session Management: Automatic session timeout after 15 minutes of inactivity. Account lockout after 5 failed login attempts with progressive delays.
Technology Stack
| Layer | Technology | Purpose |
|---|---|---|
| Frontend | React 18 + TypeScript + Vite | Provider dashboard and admin interface |
| Backend | Django 5 + Django REST Framework | REST API, business logic, FHIR compliance |
| Database | PostgreSQL 15 | Primary data store with field-level encryption |
| Cache / Broker | Redis 7 | Caching, session store, Celery message broker |
| Task Queue | Celery + Celery Beat | Async processing, scheduled billing, sync jobs |
| Mobile | React Native + Expo | Patient-facing mobile application |
| Infrastructure | Docker + Nginx + GitHub Actions | Containerized deployment, CI/CD pipeline |
Getting Started
Ready to explore the platform? Start with any of these guides:
If you're new to Vantrexia, we recommend starting with the Quick Start Guide to get the platform running locally, then walking through the Your First Patient tutorial to experience the full workflow end-to-end.