back to projects
02

Glucose Care

in progress

Multi-app healthcare platform for diabetic patient care

Code

Overview

Glucose Care is a healthcare platform built for diabetic patients and the providers around them. Instead of one app, it's an ecosystem of connected services covering patients, hospitals, pharmacies, labs, and insurance, currently in active development with a team.

Problem

Diabetic patients need coordinated care across hospitals, pharmacies, labs, and insurance, but these systems normally don't talk to each other. Patients deal with fragmented records and manual coordination between providers; providers lack a shared system to manage the same patient across hospital visits, prescriptions, and lab results.

Solution

A modular backend ecosystem connecting patients, hospitals, pharmacies, labs, and insurance into one platform. Each domain — hospital, patient, pharmacy, and so on — is built as its own service with clean, well-defined APIs, rather than one shared codebase handling every concern. This keeps each part of the system independently maintainable while still sharing common infrastructure like authentication, logging, and error handling.

Features

  • Multi-role system spanning patients, hospitals, pharmacies, labs, and insurance
  • AI-assisted features for patients and providers via OpenAI integration
  • Video consultations between patients and providers via Zoom API
  • Authentication via Google Auth and iOS Auth, backed by Firebase
  • Modular service architecture, one service per domain

My Role

Backend developer on the team. Worked on refactoring the backend from a single monolithic codebase into modular services, building shared middleware for logging, error handling, and authentication, and designing clean API boundaries between services so each team member could work on a domain without stepping on shared code.

Architecture

The platform is split into domain services (hospital, patient, pharmacy, lab, insurance) that each expose their own REST API, with shared middleware for authentication, request logging, and error handling pulled into common packages so every service behaves consistently. Auth flows through Google Auth and iOS Auth on the client side, backed by Firebase, with session handling shared across services. AI features (OpenAI) and video consultations (Zoom) are integrated as service-level capabilities rather than bolted onto a single app, so any domain service can call into them as needed.

Technical Stack

Node.jsTypeScriptMongoDBOpenAIZoom APIGoogle AuthiOS AuthFirebase

Engineering Challenges

The backend started as a monolith and became difficult to extend as more patient, hospital, and pharmacy features were added — changes in one area risked breaking unrelated functionality, and the codebase became harder to reason about as a team. The fix was breaking it into modular services with their own clean APIs, while keeping shared concerns — logging, error handling, auth middleware — centralized in shared packages so each service didn't reimplement the same logic differently. This required deliberate API design at the boundaries between services to keep them independent without duplicating core infrastructure.

Impact

Faster authentication, cleaner and more maintainable APIs, better system-wide error tracking, and a noticeably improved developer experience for the team working across services. The project is still in active development.