HealthOS — From Operational Gaps to a Production Healthcare Platform
Running technology across multiple healthcare sites, I kept seeing the same operational gaps: fragmented workflows, clinical and administrative systems that didn't talk to each other, coordination done by hand, and poor continuity between pharmacy, billing, HMO, and patient operations. On top of that, the internet connection could not be relied on.
I designed HealthOS around those operational problems rather than starting from a feature list. It is one multi-tenant platform for patient records, consultations, nursing, laboratory, pharmacy, billing, HMO processes, inventory, and reporting — and because a ward cannot stop admitting patients when a link goes down, it keeps full clinical and billing function with no connection at all.
HealthOS is now in production with active healthcare users.
My role
Founder and technical architect. I identified the problem, decided what to build, and own the architecture end to end — the multi-tenant model, the offline-first data and synchronization strategy, workflow and role separation, the security model, and the infrastructure and deployment design. I set implementation priorities and release direction, contribute directly to development and deployment, and iterate on the system as it runs in production.
Architecture & technical focus
- Multi-tenant client architecture with per-tenant separation
- Offline-first data handling and synchronization strategy
- Local-network hub sync for sites with no internet but a working LAN
- Role-based access control and workflow separation
- Flutter-based multi-platform application
- Backend APIs and database services
- Cloud deployment and DNS architecture
- Healthcare billing, HMO, pharmacy, and inventory workflow design
Status
In production · Active healthcare users
- Systems Architecture
- Flutter
- APIs
- PostgreSQL
- Offline-first
- Multi-tenant SaaS
- Cloud Infrastructure
