Trent/vigilcare-clinical
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Finish: Phase 33 — Alert Quality Analytics

Browse Source
This commit is contained in:
voltsrage
2026-06-24 03:39:24 +08:00
parent 185dc93fa1
commit 68c397350b
26 changed files with 934 additions and 169 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/VigilCare-Partner-Brief.md
+10
View File
@@ -0,0 +1,10 @@
```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.