TELEICU/Canary rollout

flowteleicuCARE 3.0+

TeleICU

Architecture

Architecture overview

Topology Current state

Middleware

Strategy

Migration strategy

Decision matrix Path A: Ansible Path B: NixOS

Canary rollout

Operations

Security baseline

Incident management Monitoring

Backup & restore

Runbooks

Power loss

Node recovery Config drift CP failure Spoke unreachable

OS update SOP

Change & recovery

Change management

Rollback strategy New hospital setup Bulk migration

DR playbook

Flows

Site onboarding

Both migration paths use the same staged rollout process to minimize fleet-wide risk.

Gating criteria

A stage must pass all checks before promoting to the next:

• All nodes report healthy to K3s control plane
• VictoriaMetrics shows no anomaly in key metrics
• Downtime classifier reports expected status (no false positives)
• Hub admin confirms no degradation in clinical workflow
• Rollback tested and confirmed working

Per-path

NixOS path

TeleICU infrastructure

Architecture

Overview · Topology · Current state · Middleware

Strategy

Migration · Decision matrix · Path A: Ansible · Path B: NixOS · Canary rollout

Operations

Security · Incidents · Monitoring · Backup & restore

Runbooks

Power loss · Node recovery · Config drift · CP failure · Spoke unreachable · OS update

Change & recovery

Change mgmt · Rollback · New hospital · Bulk migration · DR

Flows

Site onboarding

Related

Open Healthcare Network's flagship product: an open-source, FHIR-native electronic medical record (EMR) and healthcare operating system.