Hi,
I'm sharing ZamSync as a potential resource for WHO-supported digital health programs operating in low-connectivity environments.
ZamSync is an open-source Rust engine for replicating health event data between field clinic nodes and a central hub over 2G, satellite, or intermittent connections. It handles the specific failure modes common in those settings: mid-transfer power cuts, hours of disconnection, and network latency above 500ms. Core guarantees: no duplicate events, no data loss on crash, exact resume after reconnect.
It was built around the Bhutan ePIS clinic network case (604,000 patient records, district clinics on 23 kbps rural links) but the architecture is generic. It runs as a static binary on a Raspberry Pi 3 with under 10 MB RAM and zero runtime dependencies.
Concrete question: is there a WHO working group or digital health initiative focused on standardizing offline sync infrastructure for primary care in LMICs? I want to understand whether ZamSync maps to an active gap or whether there's already a preferred approach being recommended to implementers.
GitHub: https://github.com/Etoile-Bleu/ZamSync
Deep dive: https://dev.to/etoile_bleu/-i-built-a-sync-engine-for-clinics-that-run-on-2g-and-lose-power-mid-transfer-here-is-why-and-18od
Hi,
I'm sharing ZamSync as a potential resource for WHO-supported digital health programs operating in low-connectivity environments.
ZamSync is an open-source Rust engine for replicating health event data between field clinic nodes and a central hub over 2G, satellite, or intermittent connections. It handles the specific failure modes common in those settings: mid-transfer power cuts, hours of disconnection, and network latency above 500ms. Core guarantees: no duplicate events, no data loss on crash, exact resume after reconnect.
It was built around the Bhutan ePIS clinic network case (604,000 patient records, district clinics on 23 kbps rural links) but the architecture is generic. It runs as a static binary on a Raspberry Pi 3 with under 10 MB RAM and zero runtime dependencies.
Concrete question: is there a WHO working group or digital health initiative focused on standardizing offline sync infrastructure for primary care in LMICs? I want to understand whether ZamSync maps to an active gap or whether there's already a preferred approach being recommended to implementers.
GitHub: https://github.com/Etoile-Bleu/ZamSync
Deep dive: https://dev.to/etoile_bleu/-i-built-a-sync-engine-for-clinics-that-run-on-2g-and-lose-power-mid-transfer-here-is-why-and-18od