Project case study · Full-stack development and cloud deployment
HealthyMitra – Care Circles for Remote Caregiving
A Next.js platform built around care circles, letting family caregivers book appointments and diagnostics for a patient, receive updates from doctors and labs, hold audio and video consultations, and share posts with per-post visibility — deployed on AWS ECS with automated CI/CD.
What it is
HealthyMitra is a Next.js monolith that makes it possible for caregivers — a son or daughter, for example — to look after a patient such as a parent digitally.
It is organised around care circles. Every user has one, and users can join each other's circles as either a patient or a caregiver, which is what determines who can act on whose behalf.
Problem and approach
Problem
Caring for a family member remotely means coordinating appointments, reports, doctors, and updates across people who are not in the same place, with no shared place to hold any of it.
Solution
A care circle that ties a patient, their caregivers, and their doctors together, so bookings, updates, consultations, and shared posts all happen in one context with explicit control over who sees what.
How it works
Care circles
Every user has a care circle. Users join each other's circles as a patient or as a caregiver, which establishes who can act for whom.
Booking on behalf of a patient
Caregivers book appointments and diagnostic reports for their patient, and receive instant updates from doctors and diagnostic centres.
Talking to a doctor
Patients can reach doctors at any time through a chat interface that also supports audio and video calls over WebRTC.
Shared updates with controlled visibility
Users post updates into their care circle and set the audience per post: everyone in the circle, caregivers only, doctors, or a selected few.
Deployment
The platform runs on AWS ECS, with GitHub Actions building and deploying it automatically.
How I built it
- 1.
Care circle model
Built the care circle as the core structure, with patient and caregiver roles determining what each member can do.
- 2.
Consultations
Built the chat interface and added WebRTC audio and video calling for consultations.
- 3.
Payments and administration
Implemented Razorpay payments and an admin dashboard that shows and controls everything in the platform.
- 4.
Deployment and CI/CD
Containerised the platform with Docker, deployed it on AWS ECS, and built a GitHub Actions pipeline so releases deploy automatically.
Challenges and decisions
Health updates shared in a family context are not uniformly sensitive — some are for everyone in the circle, some only for caregivers or doctors.
Approach: Made visibility a per-post choice, letting the author target everyone in the care circle, caregivers only, doctors, or a selected few.
Lesson: When content is personal, per-item visibility is more honest than a single circle-wide setting.
Skills and technologies
What I learned
- How role structure inside a care circle drives nearly every permission decision in the product.
- That privacy controls in a health context need to be granular enough to match how families actually share.