
← All productsProduct · Device-to-EMR platform
Vysio
Wearable hemodynamic monitoring, from the bedside to the EMR.
Overview
Vysio is the end-to-end software platform behind a wearable hemodynamic monitor. We built every layer: a Bluetooth gateway that streams readings off the device, a real-time nurse-station dashboard, a FHIR R4 canonical store with a custom code system for the device's biomarkers, event-driven orchestration, and an HL7v2 translation engine that delivers results into any hospital EMR. The whole stack runs as a hardened, self-hosted deployment with secrets management and zero-trust networking.
What you get
- ✓BLE 5.0 device gateway (Python / Bleak) with resilient retry and backoff
- ✓Real-time nurse station (Next.js, Server-Sent Events) with tiered clinical alerting
- ✓HAPI FHIR R4 canonical store with a custom Vysio CodeSystem for StO₂ and SFI
- ✓Event-driven FHIR Subscriptions orchestrated through n8n
- ✓Mirth Connect FHIR ↔ HL7v2 ORU^R01 translation for any EMR
- ✓Epic, Oracle Health (Cerner), and universal HL7v2 EMR integration
- ✓SMART on FHIR (OAuth 2.0) and remote-patient-monitoring billing codes (99453–99458)
- ✓Hardened cloud: nginx/TLS, HashiCorp Vault, Tailscale + UFW on AWS
How it's built
Vysio moves a reading from the wearable to the chart through four layers — device, gateway, middleware, and EMR. We engineered all of them.
1
Device & Bluetooth
- Vysio wearable: near-infrared spectroscopy (VCSEL 850 nm + 660/740 nm LEDs)
- Measures hemoglobin (HbT), tissue oxygen saturation (StO₂), and speckle flow index (SFI) every 15 minutes
- BLE 5.0 (ANNA-B412) streamed by a Python gateway that parses readings and forwards them over HTTPS with key auth and exponential-backoff retry
2
Nurse station (edge)
- Real-time Next.js 16 / React 19 dashboard with a live multi-patient grid over Server-Sent Events
- Tiered clinical alerting — stable, advisory, warning, emergency — with trend charts
- Writes FHIR Observations and connects to the EMR over OAuth 2.0
3
Middleware & cloud
- nginx reverse proxy terminating TLS and routing /fhir, /n8n, and /mirth
- HAPI FHIR R4 canonical store (PostgreSQL) with a custom Vysio CodeSystem and REST-hook Subscriptions
- n8n orchestration triggered by FHIR Subscription webhooks
- Mirth Connect translating FHIR to HL7v2 ORU^R01 (MSH/PID/PV1/OBR/OBX) with reference ranges and abnormal flags
- HashiCorp Vault for secrets; Tailscale (WireGuard) + UFW for zero-trust access on AWS EC2
4
EMR integration
- Epic: FHIR R4 Observation write-back, flowsheet rows, Best Practice Alerts + InBasket, and RPM billing (CPT 99453–99458) via SMART on FHIR
- Oracle Health (Cerner): CareAware and HL7v2 via Bridges
- Other EMRs (Meditech, Allscripts…): universal HL7v2 ORU^R01 over MLLP

Built with
- BLE 5.0
- Python
- Bleak
- Next.js 16
- React 19
- HAPI FHIR R4
- Mirth Connect
- n8n
- HL7v2
- SMART on FHIR
- HashiCorp Vault
- nginx
- PostgreSQL
- Docker
- AWS EC2
- Tailscale