A queue patients can see
Tokens are numbered by the server per doctor per day. Patients check in on the day and watch the queue from their phone.
Clinic and hospital software
Shorter waiting rooms. Calmer front desks. One system for the whole clinic.
Appointments, a live OPD queue, consultations with e-prescriptions, lab, pharmacy, beds and billing in one console. Patients book real slots and watch their token move; doctors prescribe from their phone.
- Patient app with live token and family profiles
- Doctor app: queue, quick consult, sign and send Rx
- Console for reception, lab, pharmacy, IPD and billing
- 3 apps
- Patient, doctor and console
- Live tokens
- Patients see who is ahead
- 11 modules
- Front desk to finance
- 2 databases
- Postgres for money, Mongo for records
Why Arogya
Built around the OPD, where clinics lose the most time
Most clinics juggle a register, a billing tool and WhatsApp. Arogya puts the queue, the consultation and the bill in one flow.
Prescriptions in one tap
Doctors pick a diagnosis and medicines, then sign and send. The patient gets it in the app and the visit closes with a bill.
Records that stay consistent
Billing, stock and beds live in Postgres with transactions; clinical notes, vitals and lab results in MongoDB.
The apps, step by step
From booking a slot to a prescription in the patient’s pocket
Every screen below is a real screenshot from an automated end-to-end test run against the live backend. Nothing is a mock-up.
The console
A console for every desk in the hospital
Reception, doctors, lab, pharmacy, wards and accounts work in the same system, so nothing is typed twice.
The day at a glance
Footfall, department mix, each doctor’s progress and alerts.
Token lanes per doctor
Call next, move to the end, mark no-show, and a TV display mode for the waiting area.
Appointments
A day calendar with a column per doctor; book, check in, reschedule and cancel.
The whole patient on one page
Vitals and trends, visits, prescriptions, lab reports, bills and current medication.
Patients
Registration with UHID, allergy and chronic-condition alerts.
Doctors
OPD days, hours, fees, rooms and availability.
Laboratory
Sample to results to report, with automatic high and low flags.
Pharmacy
Stock, expiry, Schedule H and counter sales that update billing.
Beds and admissions
Ward bed board with admit, discharge and cleaning states.
Billing
Invoices, part payments and payment modes; status always computed from what was paid.
Reports
Revenue, departments and doctor performance.
Tested end to end
Every flow, run like a real user, on the real server
This is the full automated test report for Arogya. The production build was started on its own database and a robot used the apps and the console exactly as your customers and staff would. Each screenshot below is one step of that run, in order, with what it proves.
- 32
- screens tested
- 14
- API and security checks
- 0
- failures
- Passed
- run on 14 November 2026
-
Welcome
Onboarding from the production web build.
-
Sign in with mobile number
App detected the live API.
-
OTP sent
Server issued a one-time code.
-
Home with live token
Ananya is checked in today; her token and queue position come from the server.
-
Today’s visit: patients ahead
Live “patients ahead” count, refreshed every few seconds.
-
Find a doctor
Doctors with their next free slot, computed by the server.
-
Real free slots for Monday
Slots come from the doctor’s hours minus existing bookings.
-
Book for self or family
Family members (daughter, father) come from the account.
-
Confirm appointment
Fee from the doctor’s record.
-
Appointment confirmed
Written to Postgres; the slot is now blocked for everyone else.
-
Appointment AP-33436195
Reschedule and cancel are available until the visit.
-
Dashboard
Signed in with a real staff password; footfall and doctor progress from live data.
-
OPD queue
Token lanes per doctor; Ananya is waiting with Dr. Arjun.
-
Appointments
Calendar of every consultation, including app bookings.
-
Doctor: today’s OPD queue
Dr. Arjun signs in by OTP and sees his live queue.
-
Quick consultation
Diagnosis and medicine picked; allergies and vitals shown.
-
Prescription sent
Prescription stored in MongoDB; visit Completed and bill raised in Postgres.
-
Visit completed
Patient screen updated after the doctor finished.
-
Prescription
Dolo 650 for viral fever, straight from the doctor’s app.
-
Health records
Prescriptions and lab reports for the whole family.
-
Bills
Bills raised by consultations, lab and pharmacy.
-
Family members
Daughter and father linked to Ananya’s account.
-
Notifications (live feed)
Visits, reports and bills, built by the server.
-
Patient record: Ananya
Today’s prescription from the doctor app appears in the record.
-
Patients
Register with UHID; allergy and chronic-care alerts.
-
Doctors
OPD days, hours and fees.
-
Laboratory
Sample → results → report ready.
-
Pharmacy
Stock, expiry and counter sales.
-
Beds & IPD
Ward bed board.
-
Billing
Includes the consultation invoice just raised.
-
Reports
Reports from live data.
-
Settings
Team and settings.
API, sign-in and security checks
- Health endpoint reports the database up
- Every response carries a request id and security headers
- Wrong staff password is refused (401) with a sentence
- Staff sign-in returns a signed token
- Console data needs a session (401 without a token)
- Console bootstrap loads every collection from the database
- Malformed JSON gets a clean 400, not a crash
- Unknown endpoint answers 404 in the standard error shape
- Invalid phone number is rejected with a sentence
- Wrong OTP is refused
- Patient OTP sign-in works
- A patient token cannot open the console (403)
- Doctor OTP sign-in works
- Sign-in is rate limited (429 after 10 tries a minute)
No browser errors and no server errors were recorded during the run. Screens use demo data; the one-time code shown in test mode is replaced by an SMS in production.
Features
Everything between the front door and the final bill
Real-time slots
Slots come from doctors’ hours and existing bookings, in the app and at the desk.
Live OPD tokens
Server-numbered tokens per doctor per day, visible to patients.
E-prescriptions
Sign and send from the doctor app; stored with the patient’s record.
Lab workflow
Orders, sample collection, results with flags and report release.
Pharmacy and stock
Stock levels, expiry and counter sales linked to billing.
IPD and beds
Admit, discharge and the ward board, with a final bill on discharge.
Billing and dues
Part payments, discounts and patient-app payment of dues.
Family accounts
One phone number books for children and parents.
Built to be trusted
The rules a clinic depends on, enforced by the server
Whether a change comes from the patient app, the doctor app or the console, the same checks run on the backend.
- Tokens are numbered by the server per doctor per day
- A doctor has one patient in consultation at a time
- Slots can’t be double-booked
- Completed, cancelled and no-show visits are final
- Lab reports need results before they are released
- Payments can’t exceed the bill; a bed holds one patient
What you get
A complete product, not a template
Three working applications on one backend, with your name, colours and logo on them.
Patient and doctor app
One React Native codebase for Android, iOS and the web; patients and doctors sign in by phone.
Expo · React Native · TypeScript
Hospital console
Front desk, OPD queue, consultation, lab, pharmacy, beds, billing and reports.
Next.js 16 · React 19
Backend API
Appointments, queue, billing and stock in Postgres; prescriptions, vitals and lab results in MongoDB.
NestJS · PostgreSQL · MongoDB
Next.js 16React 19React Native · ExpoNestJSPostgreSQLMongoDBPrismaTypeScript end to end
Ways to buy
Pick how you want to launch
Pricing depends on your scope and number of locations. Tell us what you need and we’ll send a quote within one working day.
Source licence
Your developers take it from here.
- Full source code of all three apps
- Setup guide and going-live checklist
- Automated end-to-end test suite
- 30 days of email support
Most chosen
Launch under your brand
We brand it, connect it and launch it with you.
- Everything in Source licence
- Your name, colours, logo and domain
- SMS, payments and hosting connected
- App Store and Play Store submission
Managed platform
We run it; you run the business.
- Everything in Launch under your brand
- Hosting, backups and monitoring
- Updates and security patches
- Priority support
FAQ
Questions buyers ask
Can we use it for a single clinic?
Yes. It works for a one-doctor clinic and grows to a multispeciality OPD with lab, pharmacy and wards.
Can patients book for family members?
Yes. Children and parents are linked to the account holder’s phone number, and every booking, record and bill shows who it is for.
Does it work on Android and iOS?
Yes. The patient and doctor apps are one React Native (Expo) codebase that builds for Android, iOS and the web.
Where is patient data stored?
On your own servers. Billing and appointments are in PostgreSQL; clinical records are in MongoDB, keyed to the patient.
Is it ready for real patients?
The product is complete and tested end to end. To go live you connect an SMS provider for OTPs, Razorpay for online payments and your hosting. That package covers all three.
Do I get the source code?
With a source licence or launch under your brand, yes: all three apps and the backend, with setup docs and the automated test suite.
Book a demo
See Arogya running with your own doctors and departments
A 30-minute walkthrough of the apps and the console on a live server. We’ll show the exact flows on this page and answer questions about branding, pricing and launch.
- Live demo, not slides
- Quote within one working day
- Launch plan for your city or branch