TELEICU/New hospital setup playbook: Difference between revisions
More languages
More actions
Create TELEICU new hospital setup playbook (via create-page on MediaWiki MCP Server) |
Automated edit (via update-page on MediaWiki MCP Server) |
||
| Line 43: | Line 43: | ||
- [ ] Document site-specific notes in TeleicuSites entry |
- [ ] Document site-specific notes in TeleicuSites entry |
||
- [ ] Add to canary rollout pool for future updates |
- [ ] Add to canary rollout pool for future updates |
||
{{Navbox TELEICU}} |
|||
{{Related}} |
{{Related}} |
||
Latest revision as of 08:40, 6 July 2026
End-to-end process for standing up a brand-new hospital site in the TELEICU network.
Phase 1: Planning
- [ ] Identify hub assignment (which hub this spoke reports to) - [ ] Define hardware requirements from Hardware baseline - [ ] Register site in TeleicuSites - [ ] Assign hub admin contact - [ ] Provision UPS and network equipment
Phase 2: Hardware deployment
- [ ] Deploy PC/server at site - [ ] Connect UPS (configure graceful shutdown) - [ ] Connect network (primary + failover if available) - [ ] Verify internet connectivity
Phase 3: Provisioning
Follow Site onboarding flow for the chosen path (Ansible or NixOS).
Phase 4: Verification
- [ ] Node joined K3s cluster - [ ] Middleware services healthy - [ ] TELEICU streaming verified end-to-end with hub - [ ] Metrics flowing to VictoriaMetrics - [ ] Downtime classifier reporting - [ ] Alert routed to hub admin - [ ] Site entry updated in TeleicuSites (migration_status = done)
Phase 5: Handover
- [ ] Train site contact on basic troubleshooting (power cycle, check connectivity) - [ ] Provide hub admin with access credentials (via secure channel) - [ ] Document site-specific notes in TeleicuSites entry - [ ] Add to canary rollout pool for future updates