Skip to content

Telehealth operations · Realtime control room

VHH Command Center

A control-room portal for telehealth deployments across 11 northern Saskatchewan communities: live fleet map, telemetry alerts, per-community chat, and WebRTC ring-out.

Role
Senior Software Engineer, Cloud & AI · control-room portal, realtime services and iOS companion
Organization
Virtual Health Hub
Timeframe
2024 – 2026
  • Next.js
  • Socket.IO
  • WebRTC
  • MapLibre
  • Drizzle
  • SwiftUI
  • Web Push
  • AWS CDK
  • Elastic Beanstalk
  • CloudFront
  • Cognito

Context

At the time of the build, Virtual Health Hub's telehealth deployments spanned 11 communities across northern Saskatchewan. The portal brings together the live geospatial fleet map, machine telemetry with an acknowledge/resolve alert workflow, per-community topic channels, and WebRTC ring-out to on-site assistants.

Alerts are acknowledged and resolved, not just displayed. Chat is scoped by community and by topic (operations, clinical, maintenance). Ring-out to an on-site assistant is phone-style WebRTC voice/video, from a browser or from the SwiftUI iOS companion.

The build

  1. Live fleet map on MapLibre.

    Every deployment renders on a live geospatial fleet map.

  2. Acknowledge/resolve alert workflow, plus Web Push.

    Each alert runs through an acknowledge/resolve workflow. Critical alerts also go out over Web Push.

  3. Per-community topic channels on Socket.IO.

    Operations, clinical, and maintenance channels for each community, with realtime chat.

  4. Phone-style WebRTC ring-out, web and iOS.

    An operator rings an on-site assistant directly over WebRTC. Targets are browser peers and a native SwiftUI iOS companion in TestFlight beta.

  5. A pluggable integration-adapter seam.

    Third-party machine data comes in through a pluggable integration-adapter seam.

  6. AWS, defined in CDK.

    On AWS: Elastic Beanstalk, CloudFront, and Amazon Cognito, defined in CDK.

Outcome

11

northern Saskatchewan communities with monitored telehealth deployments

Ops · Clinical · Maintenance

topic channels per community

Web + iOS

WebRTC ring-out targets (browser peers; SwiftUI companion, TestFlight beta)

Ack → Resolve

alert acknowledge/resolve workflow

  • Shipped to production: a control-room portal monitoring telehealth deployments across 11 northern Saskatchewan communities.
  • One surface covers fleet location, machine telemetry, the alert acknowledge/resolve workflow, and per-community communication, with voice and video reach to on-site assistants from the browser and a native iOS companion (TestFlight beta).
  • Third-party machine data comes in through a pluggable integration-adapter seam.

Engineering notes

Hosting and sign-in

The portal runs on AWS (Elastic Beanstalk, CloudFront, Cognito), with the infrastructure defined in CDK. Sign-in goes through Amazon Cognito.

Scope and integration

Channels are scoped by community and by topic: operations, clinical, and maintenance. Third-party machine data sits behind a pluggable integration-adapter seam.

Relevant if

  • A live operations console for distributed hardware. A MapLibre fleet map, machine telemetry with acknowledge/resolve alerts, Web Push for critical alerts, and a pluggable adapter seam for third-party machine data: the pattern behind a portal monitoring telehealth deployments across 11 northern Saskatchewan communities.

  • Voice and video inside your own product. Phone-style WebRTC ring-out to browser peers and a native SwiftUI iOS app, or Amazon Chime SDK. Also see react-native-chime-sdk, an open-source (Apache-2.0) React Native binding for the Amazon Chime SDK, published by Mahmood Ul Islam.

  • Operational chat, scoped per site and topic. Topic channels (operations, clinical, maintenance) on Socket.IO, on AWS defined in CDK: Elastic Beanstalk, CloudFront, and Cognito.

Planning a realtime operations system on AWS? Talk directly with the engineer who shipped this one.