HeZa

Context

HeZa is a health monitoring and disease surveillance platform aimed at African healthcare needs. It has to work for individual users tracking personal health, for healthcare providers running consultations, and for administrators watching outbreak data at a national scale.

Product surface

• Disease surveillance pulls real-time outbreak data from sources like the WHO and the NCDC, then visualizes it with geographic clustering and heatmaps.
• Telemedicine enables virtual consultations between patients and providers.
• Scheduling covers appointment creation, management, and reminders, including Calendly OAuth for provider calendars.
• Alerts notify users about outbreaks and emergencies, with SMS as a fallback when there is no internet.
• Offline support lets users contribute and read data when connectivity drops.

Architecture

• A Next.js web app and a React Native mobile client, sharing a common design system and generated API client.
• Go backend organized as modules (accounts, HCP, analytics, rating and review, billing) with GORM repositories and PostgreSQL.
• Admin dashboard built with React and Vite for user management, outbreak tracking, and alert management.

What I worked on

• Built telemedicine features enabling virtual consultations.
• Developed appointment scheduling and management flows.
• Built Go backend APIs supporting the healthcare and surveillance workflows.
• Shipped web and mobile features on the shared design system.

What the system taught me

Designing for offline-first changes how you model time and identity. Writes that happen on a disconnected device need to reconcile later without creating duplicates or losing order, which pushes you toward client-generated IDs and explicit sync points.