Telemedicine · Hospital · Patient Portal · e-Pharmacy · Wellness
Healthcare App Development in India — Telemedicine, Patient, and Hospital Apps Built for Real Compliance, Not a Demo
Telemedicine and video-consult apps, doctor appointment booking apps, patient portals, hospital-staff apps, e-pharmacy apps, and wearable-linked wellness apps — built by an Ahmedabad-based team since 2012. Priced fixed in INR, wired to ABDM, HL7/FHIR, and your existing HIS or EMR from day one, and shipped with DPDP Act consent and MCI Telemedicine Practice Guidelines 2020 baked in.
- ✓Telemedicine, appointment booking, patient portal, and hospital-staff apps built as one clinically usable system
- ✓ABHA ID, ABDM Health Locker, eSanjeevani, and DigiLocker integrations wired at launch, not left as a phase-two backlog
- ✓HL7 v2 and FHIR R4 sync with existing HIS, EMR, LIS, and RIS — no double data entry between the app and the hospital
- ✓MCI Telemedicine Practice Guidelines 2020, DPDP Act 2023 consent, Drugs & Cosmetics Act e-prescription rules built in
- ✓Twilio Video, Agora, and Vonage video consults with recording, e-prescription, and Razorpay checkout in one flow
Why a healthcare app is a fundamentally different build from a generic consumer app
A healthcare app is not an ecommerce app with a stethoscope icon. Every screen inside it touches sensitive personal data (PHI in HIPAA language, "sensitive personal data" in India's DPDP Act 2023), and every workflow has to survive an audit by a regulator, a hospital committee, or a corporate insurer's compliance team. The margin for a shortcut is close to zero — a wrongly captured consent, an unlogged doctor-patient consult, or a prescription issued without the doctor's registered signature is not a bug, it is a regulatory exposure.
That is the wall a standard consumer-app template collapses at. Firebase Auth with anonymous sign-in, an unlogged chat SDK, generic push notifications without content templating, and a payments flow that does not distinguish between an OP consult fee, a diagnostic bill, and a pharmacy invoice — all of those are non-starters the moment the app leaves the founder's laptop. A patient booking flow written for restaurant delivery does not know that a Wednesday 3pm slot for Dr. Sharma is also blocked by his OT list at Apollo, or that a follow-up consult inside 7 days is free under his clinic's policy, or that the prescription he writes has to persist as a signed PDF on the ABDM Health Locker.
Fruxinfo has been building custom software from Ahmedabad since 2012 and healthcare-specific builds since 2015. What we ship today is a proper multi-role clinical app — patient, doctor, front-office, hospital admin — on one shared backend, wired to the HIS or EMR the hospital already runs, priced in INR up-front, and handed over with source code you own. The App Store and Play Store review paperwork (including HealthKit, Fitness API, and telemedicine category submissions) is done by our team, not left as a checklist for the clinic.
Must-have features — the modules a healthcare app cannot ship without
Founders and hospital IT teams who call us for a healthcare app arrive with two extreme feature lists. Either the list is Practo-plus-Halodoc-plus-Ada on year five, or it is one screen and a booking button. The right first move is a scoped MVP that covers the compliance floor and the clinically meaningful loop — nothing above, nothing below. Everything else waits for real usage data.
The reference MVP we ship for a single hospital or a clinic chain is a working multi-role system with the modules listed below. It goes live in fourteen to twenty weeks depending on integrations, and lets real patients book, consult, pay, and receive a prescription the day it hits the store — not a beta that needs six more months of clinical review.
- ›Patient app (Flutter iOS + Android) — phone OTP + ABHA sign-in, doctor and specialty search, slot booking, video consult, e-prescription download, digital-payments checkout, health-records vault
- ›Doctor app (Flutter iOS + Android, tablet-tuned) — daily schedule, patient queue, past visits, live video consult, e-prescription pad with tapered dose logic, notes, referral out
- ›Front-office panel (web, tuned for a clinic tablet) — walk-in registration, slot reshuffle, cash and card checkout, TPA and insurance verification, physical file scan-to-record
- ›Hospital admin dashboard (web) — doctor onboarding with MCI/NMC verification, department config, TPA panel, refund console, DPDP Act consent audit, DISHA-ready audit log
- ›Backend and API — Node.js or Laravel with HL7 v2 and FHIR R4 adapters, PostgreSQL or MySQL, Redis for slot locks, S3 for signed prescription PDFs and imaging thumbnails
- ›Video consult — Twilio Video, Agora, or Vonage with optional recording (with explicit two-party consent capture), WhatsApp fallback for last-mile connectivity issues
- ›Payments — Razorpay checkout for online, cash and card at counter, TPA pre-auth for cashless insurance, refund flow to source, GST invoice per bill
- ›Compliance — DPDP Act 2023 consent capture, MCI Telemedicine Practice Guidelines 2020 disclosures, Drugs & Cosmetics Act e-prescription signature rules, DISHA-ready encryption
Typical MVP scope — the smallest healthcare app a real clinic can put in front of real patients
The right MVP for a healthcare app is not the founder's dream feature list minus the last five items. It is the minimum flow that lets a patient book, consult, pay, and get a prescription without a workaround — and lets the clinic operate without maintaining a parallel paper register. Ship that, watch the usage, then decide what version-two looks like from real data instead of assumption.
For a single-specialty clinic (dental, dermatology, IVF, orthopaedics, mental health), the MVP is a patient app plus a doctor app plus a front-office panel — no full hospital admin, no HIS integration. Twelve to sixteen weeks, ₹4-8 lakh. For a multi-specialty hospital with 20-100 doctors, the MVP adds a hospital admin dashboard, TPA cashless-claim intake, and an HL7 or FHIR adapter to the existing HIS. Sixteen to twenty-four weeks, ₹10-22 lakh. For a telemedicine platform aggregating independent doctors, the MVP adds doctor onboarding with MCI/NMC verification, revenue-share settlement, and a review engine. Fourteen to twenty weeks, ₹9-18 lakh. For an e-pharmacy or diagnostic booking app, the MVP adds a catalogue, prescription upload with pharmacist review, and rider dispatch. Twelve to eighteen weeks, ₹6-14 lakh.
Every MVP ships with compliance capture switched on from day one — DPDP Act consent, MCI Telemedicine Guidelines disclosures on the first consult screen, and the e-prescription rules under the Drugs & Cosmetics Act. Retrofitting compliance three months after launch takes two to three times the effort of building it in from the start, and no clinic wants to be the test case for a Ministry of Health audit.
Cost to build a healthcare app in India — the real INR ranges
Healthcare app cost is the single most-asked question on the first discovery call, and the honest answer depends on which of the four common builds you are running. Below are the ranges we quote after a proper discovery — not a range pulled from a marketing blog. Every number assumes a Flutter build (one codebase, iOS + Android), a Node.js or Laravel backend, source code in your Git, and App Store plus Play Store submission handled by us.
A single-specialty clinic app — patient app, doctor app, front-office panel, no full hospital admin, no HIS integration — starts at ₹4 lakh and ships in twelve to sixteen weeks. A telemedicine or video-consult platform — patient app, doctor app, video and e-prescription flow, Razorpay checkout, admin — sits in the ₹6-14 lakh range and ships in fourteen to twenty weeks. A multi-specialty hospital app with 20-100 doctors, HIS or EMR integration on HL7 v2 or FHIR R4, TPA cashless-claim intake, and full admin lands in the ₹10-22 lakh range and ships in sixteen to twenty-four weeks. A large hospital-chain or health-tech-startup build — patient plus doctor plus front-office plus admin plus pharmacy plus lab plus wearable ingestion, ABDM Health Locker sync, LIS/RIS integration, DISHA-ready encryption at rest and in transit — is quoted after discovery and starts at ₹22 lakh.
Recurring costs stay predictable. Twilio Video runs about USD 0.004 per participant-minute (a 15-minute consult costs roughly ₹5 in video charges) and Agora runs a similar meter with a free tier for low volumes. Razorpay charges 2 percent on domestic cards and UPI is free for merchants under current MDR rules. WhatsApp Business API conversation cost runs ₹0.85-2.85 per notification for appointment reminders and follow-ups. Push notifications on Firebase are free at any realistic launch scale. HIS/EMR integrations that run through an on-premise engine sometimes need a small Windows VM (₹8,000-15,000 per month depending on the HIS vendor). App Store fees are USD 99 per year for Apple, USD 25 one-time for Google — we set both up under your business name.
Everything is fixed-scope. The number in the quotation is the number you pay, and every change request during the build is estimated in writing before work starts. Post-launch, an optional support retainer covers bug fixes, dependency upgrades, iOS and Android annual updates (both stores drop apps that fall behind the target SDK), and a 24-hour SLA on standard tickets.
- ›Single-specialty clinic app (patient + doctor + front-office) — ₹4-8 lakh, 12-16 weeks
- ›Telemedicine / video-consult platform (patient + doctor + admin) — ₹6-14 lakh, 14-20 weeks
- ›Multi-specialty hospital app with HIS/EMR integration — ₹10-22 lakh, 16-24 weeks
- ›Large hospital-chain build with HIS + LIS + RIS + ABDM + pharmacy + lab — from ₹22 lakh
- ›E-pharmacy app with prescription upload + pharmacist review + rider dispatch — ₹6-14 lakh, 12-18 weeks
- ›Diagnostic booking + phlebotomy dispatch app — ₹5-12 lakh, 12-18 weeks
- ›Wellness / fitness / mental-health app with wearable ingestion — ₹3-8 lakh, 10-14 weeks
- ›Twilio Video ~ USD 0.004/participant-minute + Razorpay 2% MDR + WhatsApp API ₹0.85-2.85 per message
Tech stack and integrations a live healthcare app runs on in India
A healthcare app in India lives on the reliability of roughly ten integrations. Miss one and the app either fails a compliance audit or fails to move the workflow the clinic already runs on. Below is the reference stack we ship, and the integrations Indian hospitals, clinics, and health-tech founders actually ask for on the first call. Every line item plugs in through the vendor's or the regulator's official spec, so nothing is a scraped hack that breaks at the next release.
The frontend is Flutter for iOS and Android (one codebase, native performance), with Next.js for the front-office panel and hospital admin on the web. The backend runs on Node.js (NestJS or Express) or Laravel — chosen against the team you plan to grow later. HL7 v2 messages travel through Mirth Connect (now NextGen Connect) or a lightweight custom adapter; FHIR R4 resources go through HAPI FHIR or the HIS vendor's own FHIR endpoint. Storage is PostgreSQL or MySQL for transactional data, Redis for slot locks and live queues, and S3-compatible object storage for signed prescription PDFs and imaging thumbnails (with SSE-KMS encryption at rest).
ABDM (Ayushman Bharat Digital Mission) integration is the single most-requested compliance line item in India today. We wire ABHA ID sign-in, Health Information Provider (HIP) and Health Information User (HIU) roles as per the Sandbox spec, and consent flow through the Consent Manager (typically the NHA's own consent-manager reference implementation). Health-record push to and pull from the ABDM Health Locker is standard on multi-specialty builds.
Video consults plug into Twilio Video, Agora, Vonage, or Zoom Video SDK. Recording is optional and gated behind explicit two-party consent capture (which the MCI Telemedicine Guidelines require if the consult is being stored). WhatsApp Business API through AiSensy, Interakt, Gupshup, or Wati handles appointment reminders, prep instructions, e-prescription delivery, and follow-up templates. Payments plug into Razorpay, Cashfree, or PayU — with GST invoicing, TPA cashless pre-auth, and refund-to-source flows.
HIS/EMR integration is where most healthcare apps go quiet. We work with the deployed HIS the hospital already runs — Napier, HMS Wolters Kluwer, Suvarna, Medixcel, MocDoc, HealthPlix, or the hospital's internal build. HL7 v2 ADT/ORM/ORU messages cover admission, orders, and results; FHIR R4 Patient, Appointment, Encounter, Observation, Medication, and DocumentReference resources cover the modern integration surface. LIS integration is standard for lab-result delivery; RIS or PACS integration handles imaging where relevant. eSanjeevani integration is available for public-sector telemedicine deployments.
Compliance and reporting round out the stack. DPDP Act 2023 consent capture, MCI Telemedicine Practice Guidelines 2020 disclosures, Drugs & Cosmetics Act digital-prescription rules, IT Act 2000 signature requirements, and DISHA-ready encryption logs are built in. HIPAA-adjacent controls (BAA-scoped subprocessors, PHI segregation, audit logs) are available for US-facing deployments. GA4 and Firebase Analytics run in privacy-aware mode — no PHI ever leaves the primary backend, event names carry only clinical intent (booking_completed, consult_ended, prescription_downloaded) with zero patient identifiers attached.
- ›Flutter iOS + Android (patient and doctor apps), Next.js web (front-office + hospital admin)
- ›Node.js (NestJS / Express) or Laravel backend with Mirth / HAPI FHIR integration layer
- ›PostgreSQL or MySQL + Redis + S3 with SSE-KMS encryption for prescription PDFs and imaging
- ›ABDM — ABHA sign-in, HIP + HIU roles, Consent Manager, Health Locker push/pull
- ›HL7 v2 (ADT / ORM / ORU) + FHIR R4 (Patient, Appointment, Encounter, Observation, Medication)
- ›Twilio Video / Agora / Vonage / Zoom Video SDK with two-party consent-gated recording
- ›Razorpay, Cashfree, PayU with TPA cashless pre-auth and refund-to-source flows
- ›DPDP Act, MCI Telemedicine Guidelines 2020, Drugs & Cosmetics Act, DISHA-ready encryption
Monetization models — how healthcare apps actually earn revenue in India
A healthcare app has more revenue levers than a first-time founder or a hospital IT head usually realises, and choosing the right mix at launch decides whether the app pays for itself in eighteen months or drags on the P&L for three years. Below are the models we architect for, with real India-market ranges. Most successful builds run two or three of these in combination.
Consult fee take-rate is the standard telemedicine model. The platform charges a doctor or a clinic 10-25 percent on every paid consult, deducted before settlement and shown on the doctor's daily payout view. A single-hospital app usually skips this and lets the hospital pocket the full consult fee — the app value there is footfall retention, not marketplace commission.
Subscription plans are the retention lever. Practo Plus and Halodoc's equivalent are the reference examples — a ₹99-299 monthly plan that offers unlimited GP consults, free follow-ups within 7 days, discounted diagnostic tests, and priority slots. Subscription revenue is the highest-margin line item once the base grows, and we wire it as a Razorpay Subscriptions or Stripe Billing product with a manage-plan screen.
Diagnostic-test commissions, e-pharmacy fulfilment margins, and second-opinion fees are three transactional levers most healthcare apps under-index on. Diagnostics run 20-40 percent gross margin to the platform on partnership with labs like Dr. Lal PathLabs, Metropolis, Thyrocare, or SRL. E-pharmacy runs 8-20 percent gross margin depending on the brand and PBM contract. Second-opinion fees for chronic-disease patients (oncology, cardiology, orthopaedics) run ₹1,500-8,000 per consult with a much higher LTV than a general consult.
Insurance TPA cashless intake is a low-take-rate but sticky lever for hospitals — a per-claim service fee or a small percentage of the claim value, paid by the TPA or the insurance company. Wearable-linked wellness programmes for corporate HR buyers (₹500-2,500 per employee per year) is another line item for platforms with a fitness or chronic-care module.
Advertising in a healthcare app is a lever we consciously deprioritise. Ads on a clinical surface break the trust the app spent months building and often trigger both MCI Guidelines and DPDP Act red flags. If ads are on the table, they belong in a wellness / lifestyle sub-app, not on the clinical consult flow.
- ›Consult fee take-rate — 10-25% on every paid consult, deducted before doctor payout
- ›Subscription plans (Practo Plus-style) — ₹99-299 monthly, unlimited GP + priority slots + follow-ups
- ›Diagnostic-test commission — 20-40% gross margin on partner labs (Dr. Lal, Metropolis, Thyrocare, SRL)
- ›E-pharmacy fulfilment margin — 8-20% gross on prescription and OTC orders
- ›Second-opinion fees for chronic-disease patients — ₹1,500-8,000 per consult, high LTV
- ›TPA cashless intake service fee — per-claim or percentage of claim, paid by TPA/insurer
- ›Corporate wellness programmes — ₹500-2,500 per employee per year, HR-buyer contract
- ›Ads: deliberately deprioritised on clinical surfaces to protect trust and stay MCI/DPDP-clean
Timeline and delivery process — how we ship a healthcare app end-to-end
Every healthcare project runs on fixed-scope, milestone-billed sprints with a Friday demo. The hospitals, clinic chains, and health-tech founders we ship for know what will be on staging every week and which invoice covers which milestone. Below is the standard timeline for a mid-sized multi-role healthcare app (patient + doctor + front-office + admin, HIS integration on FHIR).
Weeks 1-3 are the blueprint and compliance-audit phase. On-site or Zoom discovery with the founder, medical director, IT head, and operations lead. We walk the current patient journey — how walk-ins are registered today, how the physical OP register moves, how the OT list is blocked, how insurance TPA claims move, how prescriptions are handed over, and how follow-ups are chased. We come out with a written scope document, wireframes for all roles, a data model with the FHIR resource map, an HL7/FHIR integration plan with the HIS vendor's confirmation, a payments-and-refund flow, a DPDP Act consent map, and a fixed-price quotation. Nothing gets coded until the scope is signed.
Weeks 4-8 are backend, admin, and the HIS/FHIR integration. Backend, PostgreSQL schema, admin dashboard, doctor onboarding with MCI/NMC verification, and the HL7/FHIR adapter are the first modules built. By end of week 8 the hospital admin can onboard doctors, and the HIS integration can round-trip a test patient through ADT and ORU messages.
Weeks 9-14 are the patient app. Onboarding, doctor and specialty search, slot booking, checkout, video consult, e-prescription download, health-records vault, and follow-up reminders — module by module against a weekly demo. Twilio Video, Razorpay, WhatsApp API, and ABDM Health Locker wire in as horizontal capabilities.
Weeks 15-18 are the doctor app and front-office panel plus launch hardening. Doctor daily schedule, video consult, e-prescription pad, and referral flow. Front-office walk-in registration, TPA pre-auth, and cash counter. End-to-end soak tests with real doctors and real patients in a controlled cluster. App Store and Play Store review submission on week 17. The launch checklist — DPDP Act consent audit, MCI Guidelines disclosure audit, e-prescription signature audit, HIS round-trip audit, TPA test-claim audit — is signed off before go-live.
Post-launch, the first four weeks are a hyper-care sprint with daily standup, live production monitoring on Sentry and Datadog, and same-day patches on P0 issues. From month two, the app moves to the standard retainer cadence — a fortnightly release, a monthly clinical-and-analytics review, and a quarterly roadmap conversation with the medical director and IT head.
Who this build is for — the five healthcare-app client types we ship for
Every healthcare app enquiry that lands on our contact form fits into one of five patterns. Knowing which one your build is running lets the first call move quickly past positioning and straight to the module list and the number.
The single-specialty clinic (dental, IVF, dermatology, orthopaedic, mental health) wants a branded patient app to cut down phone-based booking, no-shows, and follow-up chasing. Scope is a patient app plus a lightweight doctor app plus a front-office panel — no full hospital admin, no HIS integration. Typical build is ₹4-8 lakh, ships in twelve to sixteen weeks. Retention on the app usually pays back inside eight to twelve months on reduced no-show rate alone.
The multi-specialty hospital wants an app that shows the department roster, lets patients book online with real doctor availability, replaces the walk-in queue with a token flow, and pushes reports and prescriptions into the patient's ABDM Health Locker. Scope adds the hospital admin, TPA cashless intake, and an HL7/FHIR adapter to the existing HIS. Typical build is ₹10-22 lakh, ships in sixteen to twenty-four weeks.
The telemedicine platform is a founder or a corporate health-tech team building a marketplace of doctors — usually across cities, sometimes cross-border. Scope is patient app, doctor app, doctor onboarding with MCI/NMC verification, revenue-share settlement, ratings and reviews, and a subscription plan. Typical build is ₹9-18 lakh, ships in fourteen to twenty weeks. The regulatory floor is higher than for a single hospital — MCI Guidelines have to be visible on the first consult screen for every doctor-patient pair.
The e-pharmacy or diagnostic booking app is a chain or a health-tech aggregator. Scope for pharmacy adds a catalogue, prescription upload with pharmacist review under the Drugs & Cosmetics Act rules, cart, rider dispatch, and settlement. Scope for diagnostics adds a test catalogue, home-collection scheduling, phlebotomist dispatch, and lab-report delivery to the patient app. Typical build is ₹6-14 lakh, ships in twelve to eighteen weeks.
The corporate wellness / mental-health / chronic-care app is a startup or a corporate HR arm building a preventive-care platform. Scope is a wearable-linked wellness app (Google Fit, Apple HealthKit, Fitbit, Garmin), a coach or therapist app, group programmes, and an admin. Typical build is ₹3-8 lakh for the MVP, ships in ten to fourteen weeks — a smaller starting scope because there is no live-consult layer on day one.
If your build does not fit cleanly into one of these five, that is normal — most real projects sit at the boundary between two, especially between the multi-specialty hospital and the telemedicine platform. The blueprint call places the project on the map and quotes against the closest reference.
The next step — book a healthcare-app blueprint call
The fastest way to know what your healthcare app should actually cost and what should be in scope is a 30-minute conversation. We will ask about the setup (single clinic, multi-specialty hospital, telemedicine marketplace, e-pharmacy, diagnostic, or wellness), the existing HIS or EMR you run, whether ABDM integration is a launch requirement or a phase-two ask, whether TPA cashless intake is on the table, and the timeline you are working against. At the end of the call you get a written blueprint — recommended scope, module list, integrations, indicative timeline, and a fixed-price quotation — with no obligation to move forward.
Call +91-99245-12890 or drop an enquiry through the contact form. We reply the same working day.
Healthcare app questions we hear on the first call
What hospital IT heads, clinic founders, telemedicine platforms, and health-tech teams ask before starting a healthcare-app build. If yours isn’t here, we will answer it on the discovery call.
Explore Related Services
Combine these services with what you just explored for a complete digital strategy from Fruxinfo.
Mobile App Development
Native and cross-platform iOS, Android, and Flutter apps for modern business needs.
Learn more →CRM for Healthcare & Hospitals
Patient follow-ups, referring doctor commission ledger, OP-to-IP conversion tracking, TPA claims, and HIPAA-aware access with HL7/FHIR HIMS integration.
Learn more →Healthcare Website Development
HIPAA-aware hospital, clinic, and telemedicine websites — HL7/FHIR EMR + HIS integration, appointment engines, video consult, and WhatsApp patient follow-ups built in.
Learn more →
