How CryoHealth is built

CryoHealth links satellite-based glacial lake outburst flood (GLOF) early warning with offline health guidance for community health workers in Gilgit Baltistan. It is four open-source services sharing one PostgreSQL + PostGIS database.

System architecture →

The services, how data flows from satellite scene to alert, and the design rules that hold it together.

EO pipeline →

How CryoHealth-geo turns Sentinel-2 scenes into lake observations and hazard scores.

Schema design →

All 17 tables in the shared database, grouped by domain, with columns, relationships, and enums.

How CRYO Health handles account, workforce, and patient case information.

Account & Data Deletion

How to request deletion of a CRYO Health account and associated personal data.

Repositories

All four repositories are public on GitHub.

CryoHealth-api ↗NestJS 11 · TypeORM · PostgreSQL + PostGIS
Product logic: authentication and roles, alert policy, offline sync, admin, and the public Open Data API. Owns every schema migration.
github.com/uExel/CryoHealth-api
CryoHealth-geo ↗Python 3.12 · FastAPI
Sentinel-2 earth-observation pipeline: NDWI water-extent monitoring and hazard scoring. Pure computation, no policy decisions.
github.com/uExel/CryoHealth-geo
CryoHealth-app ↗Expo · React Native
Offline-first field app: GLOF alerts for the public and IMCI triage for community health workers.
github.com/uExel/cryohealth-app
cryohealth ↗TanStack Start · Cloudflare Workers
This website: hazard map, alerts, CHW and admin views, and the Open Data explorer.
github.com/uExel/cryohealth