MedAppz case study

01 · The problem

Care runs on a dozen tools that don’t talk to each other.

A clinic’s day crosses the front desk, the consult room, the pharmacy, the lab and the cash counter. Most practices stitch that together from separate software, paper registers and WhatsApp — and every hand-off is a place where a record is retyped, a result waits or a bill leaks.

MedAppz started from the opposite end: one patient record, and small apps that each do a single job well on top of it. A solo doctor installs a handful; a hospital installs what its wards and theatres need. Nobody buys a suite they will never use.

02 · The 3-layer platform

The clinic, the engines and the foundation.

The platform is built in three layers. The clinic is the screens a front desk and a doctor use all day. The engines — scheduling, approvals, rules, consent, notifications, forms, search, print and the AI gateway — are definition-driven and versioned, and none of them knows what a patient is, which is exactly what lets a new specialty app reuse them unchanged. The foundation is the part a regulator always asks about.

The same eleven-step patient journey a clinic walks through the browser is walked by the test suite against a real database on every change.

03 · Rain AI

Ask by voice. It prepares the work. You confirm.

Rain is the assistant inside every app. Ask by voice or text — in 18 languages, or mixed with English in the same sentence — and it reads the record, prepares the paperwork and spots what is missing, showing where every answer came from.

Nothing is written on the model’s word. Rain’s draft comes back as a card; a person reads it, changes what is wrong and presses Confirm, and the record then shows their name. Anything clinical or financial must be grounded in records the clinic holds, and a high-risk answer stays a draft until a named clinician accepts it — enforced by the database, not the screen.

04 · App store and starter packs

22 apps live in clinics, 480+ in the catalogue.

Apps are browsable by function — front office, clinical, revenue cycle, engagement, operations, compliance, analytics and business — and by specialty. Each listing says plainly whether it is live, in design or in development.

Nine starter packs bundle the apps for a job to be done, from a solo clinic and a dermatology practice to surgical safety, ward operations, diagnostics QA and international patients.

05 · White-label and partner console

Your brand on the front. The same platform underneath.

A hospital can put its own name, logo and colours on the product, the patient app and its emails. Agencies, distributors and hospital groups run clinics under their own brand from the partner console: create a clinic, put it on one of their bundles and prices, see usage across every clinic, and get one statement a month.

What is not live yet is said on the page: a partner’s own app in the stores waits on the native apps, which are in development.

06 · ABDM / ABHA

Ready for the national network — and honest that it is not plugged in.

Everything that comes before India’s Ayushman Bharat Digital Mission gateway is built: care contexts prepared from real records and checked against the patient they claim to belong to, and ABDM consents on the same versioned engine as every other consent.

The certified gateway connection needs NHA certification and a Health Facility Registry identifier, and it is in development. Until then nothing is sent to the network and no ABHA is verified — and the product says so.

07 · Pricing model

A price a clinic can work out for itself.

One monthly price for the size of practice, and metered charges only for the things that cost money to send. No platform fee, no setup fee, a 14-day free trial with no card, and a data export that works from day one.

08 · The build

A modular monolith that keeps working when the line drops.

MedAppz is a multi-tenant modular monolith in TypeScript and NestJS on PostgreSQL, with a React client. Isolation is enforced inside the database, so no screen has to remember to filter by clinic.

Health camps run with no signal: registration and screening happen on the device and go up once, in order, when the signal returns. The front desk does the same for the hour the line goes down. Raising a new bill offline is not built yet, and the offline page says that too.