10 lines
951 B
Markdown
10 lines
951 B
Markdown
```markdown
|
|
### Scenario E — Ward isolation during infrastructure failure
|
|
|
|
A typhoon damages the hospital uplink. ICU bedside monitoring continues on the ward server; critical values still alert the charge nurse; acknowledgments are recorded locally. When connectivity returns, the ward backlog syncs to central with a full audit trail — no duplicate pages, no lost observations.
|
|
|
|
**What we bring:** Ward gateway architecture (`VigilCare.WardGateway`), idempotent clinical sync batch engine, ops fleet visibility for degraded gateways, and six documented chaos experiments proving the design.
|
|
|
|
**What the hospital brings:** UPS-backed ward server, network partition procedures, clinical policy for local-only mode (who owns escalation when composite scores are unavailable).
|
|
|
|
**Demo assets:** `ward-outage-reconnect-01` simulator scenario, `scripts/demo-network-partition.sh`, Grafana fleet panels, `docs/resilience/climate/` experiment artifacts. |