Healthcare
Patients book clinic visits or video consultations, doctors manage their day in their own app, and the clinic runs schedules from one admin.
Not client work. This sample shows how we would scope and build this type of product. Names and figures in any previews are invented.
Overview
This sample project shows how we would approach clinic booking and telemedicine for a group of outpatient clinics; the doctor and patient details in our previews are invented. It treats India's Telemedicine Practice Guidelines (2020) and the DPDP Act 2023 as requirements to plan for, while the clinic and its advisers remain responsible for compliance.
Project facts
Illustrative sampleFlutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
Product preview
Illustrative screens. Doctors, patients, fees and clinic locations are invented.
Sample screens: names, prices and figures are examples, not client data.
How it works
The same flow covers in-clinic visits and video consultations, with consent recorded at each step that needs it.
Patients choose a doctor by speciality and clinic, pick an in-person or video slot and pay upfront. The slot is held during payment, so it cannot be double-booked.
The patient reads a plain-language notice, gives consent and uploads earlier reports, so the doctor has context before the visit.
Online bookings sit in the same queue as walk-in tokens, so the clinic keeps to time and patients know when to come in.
Video calls fall back to audio on weak connections, and the doctor sees history and reports on the same screen.
A template-based prescription with the doctor's registration number is shared with the patient as a PDF.
Prescriptions and reports stay in the patient's record, every view is logged, and a reminder prompts the follow-up visit.
Then it starts again at step 1: Patient books a clinic or video slot
How we would build it
A clinic group wants patients to book clinic or video visits, pay upfront and get prescriptions in the app, while reception still handles walk-ins.
Key features
7 capabilities that shape the scope and the estimate.
Platforms
Patient and doctor apps for Android and iOS from one codebase, and a web admin for reception and clinic managers.
Apps for Android phones and tablets, tested on budget and mid-range devices and published on Google Play or privately.
Apps for iPhone and iPad, built to Apple's guidelines and released through TestFlight and the App Store.
One Flutter or React Native codebase for Android and iOS, with native modules where a feature needs them.
Back-office panels for operations, support and finance teams: orders, users, content, reports and permissions.
Technology
Flutter patient and doctor apps from one codebase, a NestJS back end with role-based access, and hosting built on AWS in an Indian region.
Mobile
Build Android and iOS apps from one shared codebase, so you launch on both platforms faster with a consistent experience.
Used for
Cloud & DevOps
Ready-made building blocks for mobile apps, such as push notifications, phone OTP login and crash reports, so you launch sooner.
Used for
Backend
A structured way to build back ends on Node.js, so large business systems stay organised, testable and easy to hand over.
Used for
Data
A reliable database for the records your business runs on: orders, payments, bookings and stock, kept accurate and easy to report on.
Used for
Payments & maps
Lets customers in India pay by UPI, cards, netbanking or wallets, and handles subscriptions, refunds and payouts to sellers or partners.
Used for
Cloud & DevOps
Cloud hosting for your app, website and data, with data centres in India and room to grow when traffic rises.
Used for
Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
Privacy & security
Patients consent at sign-up and before each teleconsultation, after a plain-language notice.
Reception sees bookings and payments; clinical notes and prescriptions are visible only to the treating doctor and the patient.
Data is encrypted in transit and at rest, and files open only through short-lived links.
Solutions
Video, audio and chat consultation platforms with scheduling, e-prescriptions, payments and records, designed around the Telemedicine Practice Guidelines.
Appointment apps for clinics, polyclinics and hospital OPDs with slot and token booking, live queue status, reminders, prepayment and a reception console.
Patient records, visit notes, treatment plans, billing and recalls for clinics, dental and physiotherapy practices, diagnostic centres and speciality care.
Gallery
An illustrative photo of the setting this sample is built for, not a client photo.
More work
Other illustrative projects with overlapping apps, industries or services. They are samples, not client work.
Delivery app development
An illustrative platform for neighbourhood grocery stores: slot or express delivery, store picking, batched delivery runs, and payment by UPI or cash on delivery.
Runs on
Built with
E-commerce & marketplaces
An illustrative ordering app for a distributor's retailers and sales team, with tier pricing, credit limits, trade schemes and GST invoicing.
Runs on
Built with
Device management & kiosk solutions
An illustrative kiosk product for retail chains: locked Android tablets for catalogues and price checks, a staff launcher, and a console to enrol, update and monitor every device.
Runs on
Built with
FAQ
We design for the practical requirements the guidelines describe: identifying the patient and the registered medical practitioner, recording consent, supporting video, audio and text consultations, and issuing prescriptions with the doctor's registration details. Limits on what can be prescribed remotely are enforced as the clinic defines them. The clinic's medical and legal team signs off on the final flows.
Usually as a second phase. Integrating with the Ayushman Bharat Digital Mission means registering as an integrator, building against the ABDM sandbox and passing review before going live. Scope depends on the role: a clinic sharing records acts as a health information provider. We plan the data model early so records can be linked to ABHA later without a rewrite.
Dependable video over Indian mobile networks needs media servers, TURN relays and bandwidth adaptation, which take real effort to run well. A managed WebRTC provider handles that and charges by usage, so the budget goes into booking, prescriptions and records. If volumes grow until usage fees dominate, self-hosting open-source media servers becomes worth evaluating.
Next step
Tell us how appointments and prescriptions work today, and we will suggest a first release.
