Multi-stakeholder healthcare platform

Domain: Healthcare / Patient Management Engagement: Full product build (ongoing) Team Size: Multi-developer, full-stack Recognition: Our client was featured on Shark Tank with the product we built for them.

---

The Problem

A healthcare startup came to us with a comprehensive vision: manage patient care across residential societies in urban India, end-to-end. Residents would book consultations, nursing visits, physiotherapy, ambulance services, and pharmacy orders — all from a single app. Hospitals, nurses, paramedics, and society managers each needed their own interfaces with role-specific workflows.

No off-the-shelf solution could handle the multi-stakeholder complexity, real-time dispatch requirements, and India-specific payment and notification integrations.

---

What We Built

A complete healthcare ecosystem with 6 applications, a shared SDK, and an AI-powered emergency dispatcher -- delivered as a microservices architecture.

Platform Components

Backend API (NestJS)

• RESTful API serving all frontend applications
• TypeORM with PostgreSQL for relational data
• Bull queues (Redis-backed) for async job processing
• JWT authentication with refresh token rotation
• Swagger/OpenAPI documentation auto-generated

Patient Mobile App (React Native / Expo)

• Consultation and service booking
• Real-time appointment tracking
• Pharmacy ordering (EvitalRx integration)
• Push notifications via Firebase FCM
• OTP-based phone authentication

Staff Web App (Next.js)

• Nurse check-in workflows
• Appointment management and scheduling
• Patient vitals recording
• Service fulfillment tracking

Admin Dashboard (Next.js)

• Hospital and society onboarding
• Staff management and KPI tracking
• Financial reporting and analytics
• System configuration

Resident Web App (Next.js)

• Web-based booking for residents without the mobile app
• Account management and history

Shared SDK (npm package)

• Common TypeScript types across all frontends
• API client with token refresh interceptors
• Auth store (Zustand with localStorage persistence)
• Ensures consistency across 4 frontend applications

AI Emergency Dispatcher

• Real-time emergency call handling with Socket.IO
• Live audio transcription via Whisper
• AI symptom detection using LLaMA 3 (Ollama)
• Urgency classification and triage
• 10+ emergency scenario scripts for operator training

---

Technical Highlights

Architecture

• Microservices with shared SDK for type safety across apps
• Dockerized PostgreSQL + Redis with separate dev/prod environments
• Makefile-driven database management (backup, restore, health checks)
• Per-repo git configuration for team collaboration

Booking System

9 service types supported: Ambulance, First Aid, Neighbor SOS, Remote Care, Consultation, Home Nursing, Physiotherapy, Routine Checkup, Blood Test

Role-Based Access (6 roles)

Role	Auth Method	Interface
Super Admin	Email + Password	Admin Dashboard
Hospital Admin	Email + Password	Staff Web App
Nurse	Email + Password	Staff Web App
Paramedic	Email + Password	Staff Web App
Society Manager	Phone + Password	Staff Web App
Resident	Phone + OTP	Mobile App / Web App

Integrations

• Payments: Razorpay
• Notifications: Firebase FCM (push), AiSensy (SMS/WhatsApp)
• Storage: AWS S3
• Pharmacy: EvitalRx API
• AI: Ollama (LLaMA 3), Whisper STT

---

Tech Stack

Layer	Technology
Backend	NestJS 11, TypeORM, PostgreSQL, Redis, Bull
Mobile	React Native, Expo 50
Web Apps	Next.js 16, React 19, Tailwind CSS 4, shadcn/ui
State	Zustand, React Hook Form + Zod
Tables	TanStack React Table
Auth	JWT with refresh tokens, OTP
DevOps	Docker Compose, Makefile automation
Monitoring	Error tracking, health checks

---

Outcome

• Full platform delivered and operational across multiple residential societies
• Our client took the product to Shark Tank, where it was featured on the show
• 6 coordinated applications sharing a single backend with role-isolated access
• AI dispatcher enables faster emergency response with automated triage
• Modular architecture allows adding new service types without backend changes
• Shared SDK eliminates type drift across frontend applications

---

Key Takeaway

This project demonstrates our ability to architect and deliver a multi-application healthcare ecosystem from scratch -- backend, mobile, web, admin, and AI components -- with production-grade auth, payments, notifications, and real-time features. The shared SDK pattern we developed here has since become a standard in our toolkit.