# Immunomate

> The CMS and CRM panels of a telemedicine app with real-time video consultations, which reached 500+ registered users.

- Page: https://deependra.in/work/immunomate-telemedicine
- Type: Case study 06 of 6
- Last updated: 2026-11-05
- Author: [Deependra Vishwakarma](https://deependra.in/about), senior software engineer in Mumbai

## Key facts

- Project: Immunomate
- Client: Mind Frame India Advertising & Creative Pvt. Ltd.
- What: Telemedicine platform
- Role: Developer, CMS and CRM panels
- Year: 2022

## The brief behind Immunomate

I built the CMS and CRM applications of a telemedicine web app with real-time video consultations, doctor–patient chat and appointment scheduling, on several levels including the doctor panel and the admin panel. I also worked on its backend with Laravel, Firebase Firestore and WebRTC, and cut API response times with Redis caching.

A healthcare startup making consultations accessible online: patients book, meet the doctor on video and follow up in chat. Behind the panels is a telemedicine app backend: Laravel APIs with Redis caching, Firestore for real-time chat, WebRTC for video, and privacy and access control designed in from the start.

## What constrained the work

Reliable real-time video and chat, appointment scheduling, and careful handling of patient information.

## How Immunomate is built

- **Laravel** for the core API: accounts, appointments and records.
- **Firebase Firestore** for real-time chat and presence.
- **WebRTC** for peer-to-peer video consultations.
- **Redis caching** in front of the busiest API endpoints.

## Trade-offs and why

- Firestore for real-time features instead of self-hosted sockets: faster to ship and scale, at the cost of vendor lock-in for that part of the system.
- Peer-to-peer video keeps latency and server cost low, but needs fallbacks for restrictive networks.

## What changed, measured

- **500+**: registered users. Definition: Registered users of the Immunomate telemedicine app.
- **40%**: reduction in API response time after Redis caching. Definition: Reduction in API response time after adding Redis caching.

CMS and CRM applications built on several levels, from the doctor panel to the admin panel.

Redis caching cut API response times by 40%.

Three responsive web views delivered for patients, doctors and administrators.

## Lessons from Immunomate

Real-time features are easiest to ship on managed infrastructure. Keep the core data in your own database.

In healthcare, privacy and access control come first. Design them in from the start.

## Technologies used

Laravel, Firebase Firestore, WebRTC, Redis, REST APIs

## Services used

- [SaaS development and web platforms](https://deependra.in/services/build/web-platforms) (Product engineering): Custom web applications, APIs and integrations, built to be inherited.
- [Security audit and penetration test](https://deependra.in/services/secure/security-audit) (Security and compliance engineering): An attacker's view of your application and infrastructure, and a fix list you can act on.

## Where this work happened

- [India](https://deependra.in/markets/india) (Mumbai, Bengaluru): A senior software engineer in Mumbai for Indian startups and product teams, on the same clock as you and close enough to meet in person when a session is worth it. It is for founders with a consumer launch to scale, a media or publishing platform to keep fast, or a PHP system to modernise.

---

Cite as: Deependra Vishwakarma, "Immunomate", https://deependra.in/work/immunomate-telemedicine (last updated 2026-11-05).

This is the Markdown version of https://deependra.in/work/immunomate-telemedicine; the page is the canonical source. Start a project: https://deependra.in/contact