On this page▾
- What rules apply to an online doctor consultation app in India?
- How the Telemedicine Practice Guidelines turn into app features
- Which features does a telemedicine app need?
- Patient app
- Doctor app
- Operations panel
- How much does telemedicine app development cost in India?
- What does the app cost to run after launch?
- How long does it take, and what delays launch?
- How to protect patient data in a telemedicine app
- How to choose a telemedicine app development company
- Frequently asked questions
Key takeaways
- An online doctor consultation app in India must follow the Telemedicine Practice Guidelines, 2020. They decide who can consult, how consent works and which medicines a doctor may prescribe in each type of consult.
- Since 6 October 2026, National Medical Commission (NMC) guidelines bar platforms from selling paid ranking of doctors.
- Indicative 2026 build cost in India is ₹12 lakh to ₹20 lakh for a consult app and ₹25 lakh to ₹45 lakh for a multi-specialty platform.
- Video is a running cost. At AWS list prices, a 20-minute two-person video consult uses about US$0.07 of media.
- Register on both app stores as an organisation, not an individual.
An online doctor consultation app is a mobile app that lets a patient consult a registered doctor by video, audio or chat, then receive an e-prescription and pay. In India, building one is less about video and more about rules.
The Telemedicine Practice Guidelines, 2020 shape the consent screen, the prescription screen and the doctor directory. The Digital Personal Data Protection Act, 2023 (DPDP Act) shapes how you store all of it. This guide maps those rules to features, then sets out what telemedicine app development costs in India in 2026 and what it costs to run.
What rules apply to an online doctor consultation app in India?
Three rule sets apply to every online doctor consultation app in India. The Telemedicine Practice Guidelines, 2020 govern the consultation. The DPDP Act, 2023 and its 2025 Rules govern patient data. The NMC guidelines of 6 October 2026 govern how the platform lists and promotes doctors. Integration with the Ayushman Bharat Digital Mission (ABDM) is optional for most private apps.
| Rule set | What it controls | Status in October 2026 |
|---|---|---|
| Telemedicine Practice Guidelines, 2020 | Who consults, identity, consent, prescribing, records | In force |
| DPDP Act, 2023 and DPDP Rules, 2025 | Consent notices, security, breaches, patient rights | Phased; main duties from May 2027 |
| NMC advertising guidelines, 6 October 2026 | Doctor listings, reviews, ranking, promotions | In force |
| ABDM | Health IDs, record sharing, registries | Optional unless you connect |
Telemedicine Practice Guidelines, 2020
- What it controls
- Who consults, identity, consent, prescribing, records
- Status in October 2026
- In force
DPDP Act, 2023 and DPDP Rules, 2025
- What it controls
- Consent notices, security, breaches, patient rights
- Status in October 2026
- Phased; main duties from May 2027
NMC advertising guidelines, 6 October 2026
- What it controls
- Doctor listings, reviews, ranking, promotions
- Status in October 2026
- In force
ABDM
- What it controls
- Health IDs, record sharing, registries
- Status in October 2026
- Optional unless you connect
The NMC rules are the newest, and most competitor guides miss them. "The Guidelines shall come into force with immediate effect," states the public notice signed by Dr. Raghav Langer, Secretary of the National Medical Commission (opens in a new tab), on 6 October 2026. There was no grace period.
For an app, three clauses change the product spec. Clause 9.4 requires every platform hosting doctors to ensure no paid ranking of doctors and transparent listing practices (opens in a new tab) (PDF). Explanation V bars fake or paid patient reviews. Clause 8.1(x) restricts discounts, coupons and cashbacks that encourage unnecessary consultations.
So remove "featured doctor" slots, sponsored search positions and "first consult free" banners from your first-version spec. Sort doctors by availability, specialty and language instead.
How the Telemedicine Practice Guidelines turn into app features
The Telemedicine Practice Guidelines, 2020 are rules for doctors, but almost every clause becomes a screen or a database field. They were issued on 25 March 2020 by the Board of Governors in supersession of the Medical Council of India, as Appendix 5 of the 2002 professional conduct regulations. A Registered Medical Practitioner (RMP) is a doctor enrolled on a State Medical Register or the Indian Medical Register.
The table below maps the clauses that matter most for an online doctor consultation app.
| Clause | What the guidelines require | What the app must do |
|---|---|---|
| 5.1, 5.2 | Only registered doctors; platform shows name, qualification, registration number, contact | Verified doctor onboarding; registration number on every profile |
| 3.2.5 | Registration number on prescriptions, website, messages, receipts | Auto-insert it on every e-prescription and invoice |
| 3.2.3 | Ask age; a minor consults only with an identified adult | Age field, minor flag, adult identity capture |
| 3.4 | Consent implied if the patient starts the consult; explicit if a health worker, doctor or caregiver starts it | Store who initiated; record explicit consent where needed |
| 3.7.2 | Keep logs of the interaction and the prescription | Consult log, chat history, prescription archive |
| 5.4 | AI may support a doctor but cannot counsel or prescribe | No AI-issued advice or prescriptions |
| 5.6 | Grievance mechanism for patients | In-app complaints with tracking |
5.1, 5.2
- What the guidelines require
- Only registered doctors; platform shows name, qualification, registration number, contact
- What the app must do
- Verified doctor onboarding; registration number on every profile
3.2.5
- What the guidelines require
- Registration number on prescriptions, website, messages, receipts
- What the app must do
- Auto-insert it on every e-prescription and invoice
3.2.3
- What the guidelines require
- Ask age; a minor consults only with an identified adult
- What the app must do
- Age field, minor flag, adult identity capture
3.4
- What the guidelines require
- Consent implied if the patient starts the consult; explicit if a health worker, doctor or caregiver starts it
- What the app must do
- Store who initiated; record explicit consent where needed
3.7.2
- What the guidelines require
- Keep logs of the interaction and the prescription
- What the app must do
- Consult log, chat history, prescription archive
5.4
- What the guidelines require
- AI may support a doctor but cannot counsel or prescribe
- What the app must do
- No AI-issued advice or prescriptions
5.6
- What the guidelines require
- Grievance mechanism for patients
- What the app must do
- In-app complaints with tracking
Source: Telemedicine Practice Guidelines, 25 March 2020 (opens in a new tab) (PDF), Ministry of Health and Family Welfare.
Prescribing is where most first versions go wrong. The guidelines split medicines into four lists, and the allowed list depends on the mode and the type of consult. A first consult means a new patient, a new condition, or more than 6 months since the last consult with that doctor.
| List | Example in the guidelines | When it can be prescribed |
|---|---|---|
| List O | Paracetamol, ORS, antacids | Any mode, any consult |
| List A | Clotrimazole ointment; refills for diabetes or hypertension | First consult only on video; refills on follow-up |
| List B | Add-on drugs to an ongoing treatment | Follow-up consult only |
| Prohibited | Schedule X drugs, narcotic and psychotropic substances | Never via telemedicine |
List O
- Example in the guidelines
- Paracetamol, ORS, antacids
- When it can be prescribed
- Any mode, any consult
List A
- Example in the guidelines
- Clotrimazole ointment; refills for diabetes or hypertension
- When it can be prescribed
- First consult only on video; refills on follow-up
List B
- Example in the guidelines
- Add-on drugs to an ongoing treatment
- When it can be prescribed
- Follow-up consult only
Prohibited
- Example in the guidelines
- Schedule X drugs, narcotic and psychotropic substances
- When it can be prescribed
- Never via telemedicine
The drug-list table is a rules engine. The prescription screen has to know whether the call is video, audio or chat, and whether this patient saw this doctor for this condition within 6 months. Build the engine with editable drug lists, because the Board of Governors can modify them.
The guidelines do not require video recording. They require records of the consult. If the doctor sends the prescription to a pharmacy, the patient must consent and keep the right to choose the pharmacy. If you plan to fulfil medicines yourself, read our guide to online pharmacy website development first, because drug licensing is a separate regime.
Which features does a telemedicine app need?
A telemedicine app needs three products: a patient app, a doctor app and an operations panel. The patient app books and pays, the doctor app consults and prescribes, and the panel runs the service. Most first versions underbuild the operations panel, which is where doctor verification, refunds and payouts live.
Patient app
- Search by symptom, specialty and language, then book now or schedule
- Pay upfront by UPI (Unified Payments Interface) or card
- Consult by video, audio or chat, with a network check before the call
- Download e-prescriptions, notes and receipts; message during a follow-up window
Doctor app
- Set availability and consult fees
- See history and shared reports before the call
- Write a prescription that applies the drug-list rules automatically
- Track earnings and payout statements
Operations panel
- Verify registration and degree documents before a profile goes live
- Monitor live consults, handle refunds and complaints
- Run doctor payouts and export records
Video is the technical core. Most apps use WebRTC, the open standard that browsers and mobile apps use for real-time audio and video, through a managed provider. Design for weak networks: the call should drop to audio, not freeze.
Language support matters as much as video quality. India's public telemedicine service, eSanjeevani, has crossed 50 crore (500 million) consultations. It handles 2.5 to 3 lakh consultations a day in 15 languages (opens in a new tab), All India Radio reported on 6 October 2026. A private app aimed at patients beyond the metros needs regional-language screens and doctors filtered by language.
Raqbash built a telemedicine platform for a multi-specialty clinic network that shows the full stack. It runs low-latency video with in-call chat and file sharing, digital prescriptions, and booking with reminders and payments on iOS and Android. Most of that work sits behind the call screen.
How much does telemedicine app development cost in India?
Telemedicine app development in India costs an indicative ₹12 lakh to ₹20 lakh (₹1,200,000 to ₹2,000,000) for a consult app in 2026. A multi-specialty platform with instant consults, payouts and ABDM costs ₹25 lakh to ₹45 lakh (₹2,500,000 to ₹4,500,000). The jump comes from real-time matching and money movement, not from screens.
| Scope | Includes | Indicative cost (India, 2026) | USD equivalent | Timeline |
|---|---|---|---|---|
| Consult app | Patient and doctor apps, video, audio and chat, guideline-aware prescriptions, admin panel, payments | ₹12 lakh to ₹20 lakh | US$12,629 to US$21,048 | 14 to 18 weeks |
| Telemedicine platform | Everything above, plus instant matching, split payments and payouts, ABDM, analytics | ₹25 lakh to ₹45 lakh | US$26,310 to US$47,358 | 6 to 9 months |
Consult app
- Includes
- Patient and doctor apps, video, audio and chat, guideline-aware prescriptions, admin panel, payments
- Indicative cost (India, 2026)
- ₹12 lakh to ₹20 lakh
- USD equivalent
- US$12,629 to US$21,048
- Timeline
- 14 to 18 weeks
Telemedicine platform
- Includes
- Everything above, plus instant matching, split payments and payouts, ABDM, analytics
- Indicative cost (India, 2026)
- ₹25 lakh to ₹45 lakh
- USD equivalent
- US$26,310 to US$47,358
- Timeline
- 6 to 9 months
These are Raqbash's indicative ranges, not quotes. They assume one cross-platform codebase for iOS and Android, one backend and an Indian cloud region. They exclude store fees, cloud and video usage, and post-launch support. USD figures use ₹95.02 per US dollar, the FBIL reference rate for the week ended 16 October 2026 (opens in a new tab) published by the Reserve Bank of India.
Illustrative split of a ₹16 lakh (₹1,600,000) consult app. Assume two specialties, scheduled consults only, one payment gateway and no ABDM.
| Work | Share | Amount |
|---|---|---|
| Discovery and guideline mapping | 8% | ₹1,28,000 |
| UX and design | 12% | ₹1,92,000 |
| Patient and doctor apps | 30% | ₹4,80,000 |
| Backend, prescription engine, admin panel | 28% | ₹4,48,000 |
| Video, payments, notifications | 10% | ₹1,60,000 |
| QA, security testing, store release | 12% | ₹1,92,000 |
Discovery and guideline mapping
- Share
- 8%
- Amount
- ₹1,28,000
UX and design
- Share
- 12%
- Amount
- ₹1,92,000
Patient and doctor apps
- Share
- 30%
- Amount
- ₹4,80,000
Backend, prescription engine, admin panel
- Share
- 28%
- Amount
- ₹4,48,000
Video, payments, notifications
- Share
- 10%
- Amount
- ₹1,60,000
QA, security testing, store release
- Share
- 12%
- Amount
- ₹1,92,000
Three decisions move an estimate the most. Instant "consult now" queues need matching logic and far more testing than scheduled slots. Doctor payouts add refunds, holds and statements. Each specialty with its own intake form, such as mental health or paediatrics, adds flows.
Quotes on page one of Google range from a few thousand dollars to over a million, because each describes a different product. Compare against general mobile app development cost bands to see what the telemedicine rules add.
If budget is tight, start with the consult-app scope. Hire it as an MVP development project on a production foundation, so the same codebase grows into the platform tier later.
What does the app cost to run after launch?
Running costs for a telemedicine app in India start on launch day and grow with consult volume. The four lines are video minutes, store fees, annual platform updates and maintenance. The video line grows with every consult, while store fees and maintenance are yearly, so model video before you set consult prices.
Video. Amazon Chime SDK, the AWS video service, charges US$0.0017 per attendee-minute for WebRTC media (opens in a new tab). An illustrative 20-minute consult with one patient and one doctor uses 40 attendee-minutes, or about US$0.068 (about ₹6.5). At 10,000 consults a month, that is about US$680 (about ₹64,600). Recording, HD and extra participants cost more.
Store fees. The Apple Developer Program costs 99 USD per membership year (opens in a new tab), about ₹9,400.
Annual platform updates. Google raises its minimum target every year. From 31 August 2026, new apps and updates must target Android 16 (API level 36) (opens in a new tab), with an extension available to 1 November 2026. The API level is the Android version your app declares it is built for. Budget a small engineering block for this every year.
Maintenance. Budget an indicative 15 to 20 percent of the build cost a year for security patches, OS updates and small changes, before cloud and video usage.
How long does it take, and what delays launch?
A consult app takes an indicative 14 to 18 weeks to build in India, and a platform takes 6 to 9 months. The usual delays are not engineering. They come from medical sign-off on prescription flows, app store review, and approvals for payment and video accounts.
| Phase | Share of timeline | What stalls it |
|---|---|---|
| Discovery and guideline map | 10% | Medical lead not available |
| Design and prototype | 20% | Consent and prescription screens re-reviewed |
| Build sprints | 45% | Payment gateway or video account approvals |
| QA on real devices | 15% | Weak-network bugs found late |
| Store release | 10% | Wrong developer account type |
Discovery and guideline map
- Share of timeline
- 10%
- What stalls it
- Medical lead not available
Design and prototype
- Share of timeline
- 20%
- What stalls it
- Consent and prescription screens re-reviewed
Build sprints
- Share of timeline
- 45%
- What stalls it
- Payment gateway or video account approvals
QA on real devices
- Share of timeline
- 15%
- What stalls it
- Weak-network bugs found late
Store release
- Share of timeline
- 10%
- What stalls it
- Wrong developer account type
Open both store accounts in the company's name. Apple's App Review page says certain apps must be submitted by the legal entity that provides the services (opens in a new tab) rather than an individual developer, and it lists healthcare among those fields. On Google Play, personal accounts created after 13 November 2023 must run a closed test with 12 testers for 14 continuous days (opens in a new tab) before production access. An organisation account avoids both problems.
Ayushman Bharat Digital Mission (ABDM) integration adds its own gate. Every new app must be tested in the ABDM sandbox and pass a security audit (opens in a new tab) before going live, according to a Press Information Bureau (PIB) backgrounder of 6 July 2026. The same backgrounder reported over 93 crore (930 million) ABHA accounts. Plan ABDM as a phase two unless your patients already use Ayushman Bharat Health Account (ABHA) numbers.
How to protect patient data in a telemedicine app
Patient data in a telemedicine app is personal data under the DPDP Act, 2023, and consult notes are among the most sensitive data you will hold. Build the consent notice, rights handling and security controls into the first version, not after launch.
The DPDP Rules, 2025 were notified on 14 November 2025 with an 18-month period for phased compliance (opens in a new tab) (PDF), according to a PIB backgrounder of 17 November 2025. That puts the main duties in May 2027. A Data Fiduciary is the organisation that decides why and how data is processed. The PIB backgrounder says it must issue a separate, clear consent notice and answer access or erasure requests within 90 days. Penalties reach ₹250 crore (₹2,500,000,000) for failing to keep reasonable security safeguards.
For security testing, use the OWASP Mobile Application Security Verification Standard (MASVS) (opens in a new tab) as the checklist. Its control groups cover storage, authentication, network traffic and privacy, which map directly onto consult records, logins and video sessions.
Host patient data in an Indian cloud region, keep video unrecorded by default, and log who opened which record. Our checklist on healthcare website compliance in India covers the CERT-In reporting rules and SPDI Rules that apply today.
Ask any vendor who owns the code, the cloud account and the data. Raqbash's security, NDA and IP ownership terms show one way to put that in writing.
How to choose a telemedicine app development company
Choose a telemedicine app development company by testing its regulatory knowledge before its portfolio. Ask how the guidelines shape consent, prescriptions and doctor listings. A vendor that cannot explain List A on a video first consult will build the prescription screen wrong.
Ask each vendor:
- Show us the guideline-to-feature map for our scope.
- How does the prescription screen change between video, audio and chat?
- How do you verify a doctor's registration before the profile goes live?
- How do listings and search avoid paid ranking under the National Medical Commission (NMC) guidelines?
- What is the video cost per consult at our expected volume?
- Whose developer accounts, cloud and repositories will we use?
- What does the annual Android target-API update cost?
A quote that calls the app "HIPAA-compliant" and never mentions the Digital Personal Data Protection Act is borrowing US wording. The Health Insurance Portability and Accountability Act (HIPAA) is US law.
To see what a specialist treats as standard, compare quotes against Raqbash's telemedicine app development services, which cover patient, doctor and ops apps with guideline-aware prescriptions.
The build itself sits within our mobile app development services for iOS and Android.
If you are planning an online doctor consultation app, Raqbash's in-house team starts with the guideline map in this article and a written scope. We send an itemised estimate before you commit. Your medical lead reviews the consent and prescription flows before build. We work in two-week sprints with an installable build at the end of each one, and you get a named point of contact and post-launch monitoring. To get an estimate against your own specialties and doctor network, scope your consultation app with our team.