TELEICU/Change management: Difference between revisions
From OHC Network Wiki
More languages
More actions
Content deleted Content added
Automated edit (via update-page on MediaWiki MCP Server) |
Fix Mermaid diagram: remove <pre> wrapping (via update-page on MediaWiki MCP Server) |
||
| Line 10: | Line 10: | ||
== Change lifecycle == |
== Change lifecycle == |
||
<pre> |
|||
{{#mermaid:flowchart LR |
{{#mermaid:flowchart LR |
||
PLAN["Plan<br/>(RFC document)"] |
PLAN["Plan<br/>(RFC document)"] |
||
| Line 29: | Line 28: | ||
ROLLOUT -->|"fail → pause"| PLAN |
ROLLOUT -->|"fail → pause"| PLAN |
||
}} |
}} |
||
</pre> |
|||
== Change types == |
== Change types == |
||
Revision as of 08:52, 6 July 2026
Process for planning, reviewing, and deploying changes across the TELEICU fleet.
Change lifecycle
Change types
| Type | Review required | Staging | Canary | Rollout window | |---|---|---|---|---| | Security patch | Light (1 reviewer) | Yes | 1 site | Within 7 days | | Bug fix | Normal (2 reviewers) | Yes | 1 site | Next business day | | Feature/middleware update | Full (2 reviewers + hub lead) | Yes | 2 sites | Scheduled window | | OS update (NixOS flake) | Full (2 reviewers) | Yes | 2 sites | Quarterly | | Hardware change | Site-specific | N/A | N/A | As needed | | Emergency patch | Post-hoc review | Bypassed | Bypassed | Immediate |
RFC template
Every change should document:
- What is changing and why
- Risk assessment — what could break
- Rollback plan — how to undo
- Impact scope — which sites/nodes are affected
- Testing performed — what was validated in staging
- Monitoring — what to watch during rollout
Approval gates
- Peer review (code/infra team)
- Hub admin sign-off (if clinical impact is possible)
- Ops lead approval for fleet-wide rollout