Cost to build a health super-app like ekacare: India ABDM guide

A hospital group in Hyderabad runs five hospitals and eight diagnostic centers. Over three years, they've acquired 2.3 million patient records spread across three different HMS systems -- none of which talk to each other. Patients carry physical files between facilities. When a patient visits their Kukatpally hospital after a scan at their Secunderabad diagnostic center, the attending doctor has no access to the imaging report.

They want to fix this with a patient app. But when they evaluate options, they run into the same wall: ekacare requires their patient data to live on ekacare's servers. Practo handles doctor discovery but has no PHR. A generic app built on Firebase would need custom ABDM integration to become the unified health record the group needs, and that integration requires NHA registration and an audit.

This guide is for that Hyderabad hospital group -- and for insurance companies, D2C health brands, and state health agencies in similar situations. It covers what a custom health super-app costs, what the build looks like phase by phase, and where the ABDM compliance process tends to slow things down.

Building a health super-app like ekacare costs Rs 35L-Rs 55L ($42K-$65K) for a PHR and appointment booking V1 over 10-14 weeks. A full super-app with teleconsultation, medicine delivery, lab booking, and ABDM health locker integration costs Rs 90L-Rs 1.4 crore ($110K-$165K) over 24-32 weeks. The biggest timeline variable is ABDM sandbox registration and NHA approval, which takes 6-10 weeks and should start on day one of the project.

Cost and timeline at a glance

The INR ranges reflect a team billing at Rs 2,900-Rs 3,400 per hour, which is the RaftLabs rate for India-focused health builds. V3 costs scale with module count, regional language support, and HMS integration complexity.

Who actually builds a health app like this

Most organizations evaluating ekacare alternatives are not trying to compete with ekacare in the consumer market. They're solving a specific business problem that ekacare's model doesn't fit.

Hospital chains with five or more facilities account for most of the serious inquiries. A 3,000-bed group running across multiple cities needs patient records unified under a single patient ID, not split across HMS vendor portals. The Hyderabad scenario above is typical. If each patient averages 2.3 visits per year and the group has 500,000 active patients, that's 1.15 million appointments that could go through a proprietary app. At Rs 150 average prescription order per appointment, the medicine delivery margin alone justifies the build cost within 18 months.

Health insurance companies come in second. A patient with diabetes who tracks their HbA1c, takes medications on schedule, and sees their doctor for quarterly check-ups files fewer catastrophic claims than one who doesn't. An insurer that gives policyholders a branded health app with medication reminders, lab tracking, and teleconsultation access is buying engagement that reduces claim frequency. Companies like Max Bupa and Niva Bupa have built proprietary apps for exactly this reason. Mid-sized insurers with 5 lakh+ policyholders can justify the build on claims reduction alone.

D2C health and nutraceutical brands are the third category. A supplements company that sells through Amazon and its own website has no visibility into customer health outcomes. A branded app that tracks customer vitals, sends supplement reminders, and books lab tests creates a health relationship that Amazon can't replicate. Monthly subscription revenue at Rs 299-Rs 499 per active user compounds faster than repeat purchase cycles.

State health agencies under Ayushman Bharat round out the buyer set. District health offices need ABDM-compliant portals for Pradhan Mantri Jan Arogya Yojana (PM-JAY) beneficiaries. The requirements are specific: ABHA creation, benefits verification, hospital empanelment lookup, and claim tracking. These are bespoke builds funded by state IT departments, not commercial products. The compliance requirements are identical to commercial apps, but the business model is different.

Core features by module

A health super-app like ekacare isn't one product -- it's five or six distinct modules that share a patient identity layer. Here's what each module covers and why it's included.

Personal health record (PHR)

The foundation of the entire app. Stores medical history, past prescriptions, lab reports, vaccination records, allergies, and chronic condition management. Built to FHIR R4 standard -- the international healthcare data format that ABDM requires. The PHR is what turns a booking app into a health platform. Without it, you're Practo. With it, you own the patient's data relationship.

ABDM integration

Ayushman Bharat Health Account (ABHA) ID creation and linking, health locker for consent-based sharing of health records between providers, and interoperability with ABDM's Health Information Exchange and Consent Manager (HIE-CM). This is the module that requires NHA registration. Becoming a Health Information Provider (HIP) or Health Information User (HIU) lets your platform share records with other ABDM-registered providers -- which is what gives patients genuine portability of their health data.

Doctor discovery and booking

Specialty search, location-based filtering, ratings and availability. Slot engine for in-clinic, video, and home visit bookings with calendar sync for hospital scheduling systems. This is the first feature most patients use and the one that drives initial adoption. It's also where you plug into your existing HMS appointment systems.

Teleconsultation

Video consultations using WebRTC, in-app chat, ePrescription generation in ABDM-compliant format. The Telemedicine Practice Guidelines 2020 require doctor verification against MCI/state council registries -- build this check into your doctor onboarding workflow. Video quality degrades on 3G. Design the video layer with fallback to audio-only and asynchronous chat for low-bandwidth contexts.

Medicine delivery

Integration with 1mg or PharmEasy APIs for near-term delivery, or direct pharmacy partner integration for hospital chains that want to control the supply chain. Prescription medicines need verification before dispensing. Cold chain tracking for insulin and temperature-sensitive medications is a separate workstream -- not all 3PL partners support it.

Lab test booking

Test catalog with home collection scheduling, report delivery directly to the patient PHR. The lab report delivery to FHIR is the connection that makes this genuinely useful -- without it, you're just another booking widget.

Family health profiles

Up to six family members under one account, shared management with explicit consent per member. Critical for Indian household dynamics where one person often manages health records for parents, spouse, and children.

Health metrics tracking

Vitals logging (BP, blood glucose, weight, SpO2) with trend charts, wearable integration with Apple Health and Google Fit for automatic sync. Medication reminders linked to the prescription record, not a freeform schedule.

Admin dashboard

Doctor management, appointment analytics by specialty and facility, patient demographics, revenue tracking per channel. For hospital chains, this replaces fragmented HMS reporting with a single view across all facilities.

Build timeline, milestone by milestone

ABDM integration has approval steps that can't be parallelized. The single most important scheduling decision is to start ABDM sandbox registration on day one, not after the app is built.

Weeks 1-3 are architecture and ABDM registration. ABDM sandbox registration takes 2-4 weeks regardless of your app's readiness. Start the NHA process on day one. Simultaneously: FHIR R4 schema design for the PHR data model, ABHA ID integration specification, DPDP Act consent architecture design.

Weeks 4-7 cover the PHR module. FHIR-compliant health records storage, document upload with OCR pipeline for paper-based reports (most patients in Tier 2 cities have physical records from government hospitals), medical history structured data entry.

Weeks 8-10 bring doctor discovery and appointment booking online. Specialty search, slot engine, calendar integration, HMS connector for existing appointment systems. Basic doctor verification against NMC registry.

Weeks 11-13 handle the ABDM consent flow. M1/M2 consent artifacts for ABDM-compliant record sharing, health locker integration, HIP/HIU role configuration. This is what makes the app ABDM-compliant rather than just ABDM-adjacent.

Weeks 14-16 are MVP launch. Patient portal live, appointment reminders, basic analytics dashboard for hospital admins, medication reminders.

Weeks 17-22 deliver V2: teleconsultation with WebRTC, ePrescription generation, medicine delivery via 3PL API integration, prescription verification workflow.

Weeks 23-28 complete V2: lab test booking, report delivery to PHR, family health profiles with consent management.

Weeks 29-32 are V3: wearable integration (Apple Health, Google Fit), AI health insights from PHR data, regional language support (Hindi, Telugu, Tamil at minimum), advanced admin analytics.

Compliance and regulatory requirements for India

Indian health apps carry more regulatory weight than most categories. Here's what's non-negotiable.

ABDM (Ayushman Bharat Digital Mission)

Any health platform handling patient records in India should integrate with ABDM's ABHA system for consent-based health data sharing. According to the National Health Authority's 2024 dashboard, over 670 million ABHA accounts have been created since the program launched -- which means a significant share of your patient base may already have an ABHA ID and expect your platform to recognize it. The Health Data Management Policy sets rules for data access, retention, and consent. Becoming a registered HIP or HIU requires NHA registration and an audit. The audit timeline is the main variable -- some organizations get approval in 6 weeks, others wait 12. Budget 10 weeks.

DPDP Act 2023 (Digital Personal Data Protection Act)

India's first data protection law treats health data as sensitive personal data. Key obligations: explicit consent before any health data collection, data principal rights for access, correction, and erasure, data fiduciary registration with the Data Protection Board, and restrictions on cross-border transfers. Build consent management into your app's first release. Retrofitting it later is expensive and the law is now in force.

Telemedicine Practice Guidelines 2020

Doctors on your platform must be registered with the MCI or a state medical council. Your platform carries responsibility for verification. Schedule H drugs cannot be prescribed via telemedicine -- your ePrescription system needs to flag these and route them to in-clinic follow-up.

CDSCO regulations for medicine delivery

If your platform operates as a marketplace linking patients to pharmacies (rather than operating as a pharmacy), the regulatory obligations differ from running a direct pharmacy. Either way, prescription verification is mandatory for Schedule H and H1 drugs. Get legal advice on your operating model before building the medicine delivery module -- the architecture differs.

IT Act 2000, Section 43A

Companies holding sensitive personal data (which includes health records) must maintain reasonable security practices. This isn't new law, but DPDP Act enforcement makes it more material.

Technical challenges you'll hit

Building a health app in India isn't the same as building a health app in the US or EU. These challenges are specific to the Indian context.

ABDM integration approval

ABDM APIs -- HIE-CM, Health Facility Registry (HFR), Health Professional Registry (HPR) -- are well-documented and improving. But the sandbox-to-production approval is slow. Teams that underestimate this get their launch blocked. The pattern we've seen: teams finish development in 16 weeks, then spend another 8 weeks waiting for NHA production approval. Start the registration process on day one.

OCR for paper health records

India's Tier 2 and 3 city patients often have years of health history in physical files -- handwritten prescriptions, printed lab reports, physical X-rays. Building a medical document OCR pipeline that works on low-quality scans is a distinct engineering workstream. It's not a checkbox feature. A good medical OCR pipeline adds 3-4 weeks to the PHR module and pays back in adoption -- patients who can upload their paper records actually use the app.

Low-bandwidth optimization

Average download speeds in Tier 2 and 3 Indian cities sit around 10-15 Mbps on 4G, with frequent 3G fallback. A health app that loads lab report PDFs without compression or caching isn't usable for a significant portion of your target users. The PHR module needs aggressive document compression and offline-first architecture for core features.

Regional language support

Devanagari, Telugu, Tamil, Kannada, and Bengali scripts require specific font rendering handling in React Native. Right-to-left doesn't apply, but the character rendering complexity is real. At minimum: Hindi and English. For a Hyderabad hospital group, Telugu is non-optional. Budget 2-3 weeks for proper i18n implementation -- not just UI labels but also OCR pipeline support for regional language prescriptions.

Doctor verification at scale

According to ABDM's official dashboard, over 670 million ABHA accounts have been created since the program launched, with 420 million health records linked and over 130,000 facilities ABDM-enabled as of 2024. The National Medical Commission's 2023 annual report puts the number of registered allopathic doctors in India at over 1.1 million. The NMC maintains a registry but API access is limited. Your doctor onboarding needs a hybrid path: automated NMC registry check supplemented by manual verification for records that don't match. Fake doctor profiles are a real risk on any open marketplace. Verification adds a week to onboarding but prevents a trust-destroying incident later.

V1, V2, V3 phased builds

V1: PHR and appointment booking (Rs 35L-Rs 55L / $42K-$65K, 10-14 weeks)

V1 proves the core value proposition: a patient can create their ABHA ID, upload their medical history, and book an appointment at any of your facilities. That's the business unlock -- patients start using your app instead of calling your front desk. The hospital gets a unified view of the patient across facilities.

What this unlocks: hospital-branded app in store, unified patient identity across facilities, reduced front-desk call volume, and the foundation for loyalty programs tied to appointment frequency.

V2: Teleconsultation and medicine delivery (Rs 55L-Rs 90L / $65K-$110K, 16-22 weeks total)

V2 adds revenue streams. Teleconsultation at Rs 200-Rs 800 per consultation. Medicine delivery at 8-12% margin on GMV. These two modules together push your app past booking utility into a daily health tool. The retention improvement is significant -- patients who use teleconsultation are 3x more likely to return for in-clinic visits, according to Apollo Hospitals' published patient engagement data.

What this unlocks: direct consultation revenue, medicine GMV, higher patient retention, insurance claims data integration for cashless claims.

V3: Full super-app (Rs 90L-Rs 1.4 crore / $110K-$165K, 24-32 weeks total)

V3 is the competitive moat. Family health profiles, lab booking with report delivery to PHR, wearable integration, AI health insights, regional language support. This is the product that makes switching costs real -- patients with three years of health history in your app, family profiles set up, and wearable data synced do not leave. Unit economics: at 100,000 active users paying an average Rs 300 per year across subscription, medicine, and lab revenue, you're looking at Rs 3 crore ARR.

What this unlocks: family plan subscription revenue, lab booking commission (10-20% per test), wearable-linked preventive care workflows for insurers.

Competitive landscape: where ekacare stands

Understanding where ekacare sits helps clarify what you're building against.

ekacare is the most ABDM-complete PHR app in the Indian market. It has strong doctor discovery, solid health record storage, and reasonable ABDM integration. Its weakness for enterprise buyers is white-label limitations -- you can't fully brand the experience, and patient data stays on ekacare's servers. For a hospital chain that sees patient relationships as a competitive asset, that's the core problem.

Practo remains dominant for doctor discovery in metros. It's weak on PHR and has no ABDM health locker. The Practo network is valuable for patient acquisition, but it's not a platform you can build a patient relationship on.

Apollo 247 is the model that hospital-owned apps are benchmarked against. Apollo built it specifically to own the patient relationship within their network. The limitation: it only works within Apollo. Patients who see an Apollo doctor and a non-Apollo specialist can't use the same record.

1mg and PharmEasy are medicine delivery first. They're adding teleconsultation. Their PHR integration is shallow -- lab reports exist in the app but don't connect to a structured health record the way FHIR requires.

A custom build differentiates on four dimensions: hospital-branded experience, ABDM-first architecture where the health locker is a core feature, Tier 2/3 optimization for low bandwidth and regional languages, and family health management for the Indian household model.

How a custom build generates revenue

The hospital SaaS model licenses the platform to the hospital group at Rs 200-Rs 500 per active patient per year. For a 500,000 active patient base, that's Rs 10-Rs 25 crore ARR. The app replaces front-desk call volume, generates medicine delivery revenue, and reduces patient churn to competitor facilities.

The insurance engagement model charges Rs 50-Rs 150 per policyholder per month for a health engagement platform that reduces claims frequency. For a 5 lakh policyholder base, that's Rs 30-Rs 90 crore annually. An insurer who reduces catastrophic claims frequency by 8% across a diabetic patient segment recovers the platform cost in the first year.

Transaction revenue stacks on top. Medicine delivery at 8-15% margin on GMV. Lab test booking at 10-20% commission per test. Teleconsultation platform fee at Rs 30-Rs 100 per consultation. At 100,000 active users averaging Rs 300 in transactions per year, you're at Rs 3 crore in transaction revenue.

The D2C subscription model prices the app at Rs 199-Rs 499 per month, bundled with supplement tracking, lab test discounts, and teleconsultation credits. Customers who track their health data in your app buy your supplements more consistently than those who don't.

According to Grand View Research, India's digital health market was valued at USD 17.81 billion in 2025 and is projected to grow at a CAGR of 25.1% through 2033 -- one of the fastest-growing digital health markets globally. The growth is driven by ABDM adoption, increasing smartphone penetration in Tier 2 and 3 cities, and insurance expansion under Ayushman Bharat. The market is real, but the build needs to be right.

Build vs. buy: when does custom win?

Keep using ekacare if you have no existing patient base to migrate, need to launch in under 8 weeks, and are comfortable with patient data staying on ekacare's platform under their terms.

Build custom when any of these apply:

You run five or more hospital facilities and need unified patient records across locations that your HMS systems can't provide. No SaaS platform integrates deeply enough with multiple HMS vendors to solve this. Only a custom layer that sits above your HMS systems and normalizes data across them gives you the unified record.

You're an insurance company that wants to own the patient health engagement relationship. Insurance platforms that white-label consumer apps lose the data relationship. The claims reduction ROI only materializes when the insurer controls the health data and can act on it.

You're a D2C health brand building customer lifetime value through health tracking. Your product's differentiation comes from connecting supplement outcomes to patient health data. That data relationship requires ownership.

You're building for Tier 2 and 3 markets where regional language support and low-bandwidth optimization are non-negotiable. Consumer health apps built for metro audiences break in lower-bandwidth environments.

The payback calculation for a hospital chain is straightforward. A 5-hospital group spending Rs 60L on a V2 build has a patient base worth Rs 20-Rs 30 crore in annual appointment revenue. A 15% improvement in patient retention -- which a branded app with appointment reminders and health records typically delivers -- pays back the build cost in the first year.

The failure mode we see most often

The most common mistake in Indian health app builds isn't in the PHR or teleconsultation modules. It's in ABDM timing.

Teams scope a 16-week build, finish development, then discover that NHA production approval takes another 8-12 weeks. The app is done but not live. Marketing campaigns are on hold. The hospital group's IT leadership is fielding questions from doctors about a launch that can't happen.

The fix is simple: start ABDM sandbox registration on day one of the project. The engineering team doesn't need to be blocked waiting for approval -- they can build against the sandbox environment. But the approval process runs in parallel, and if it starts late, it ends late. Teams that start registration on week 1 and finish engineering by week 14 typically get production approval before they need it. Teams that start registration in week 12 are always waiting.

The same pattern applies to NMC doctor verification. If your doctor verification workflow depends on NMC API access and that access isn't confirmed before you start building, you'll discover the limitation when you're trying to onboard doctors for launch. Build a hybrid verification path from day one.

"Digital health is one of India's most exciting opportunities, but regulatory navigation is the one thing that kills otherwise good products. The ABDM approval process is not inherently slow -- it rewards teams who engage early and correctly." -- Siddharth Shah, co-founder and CEO, Mfine (India's largest AI health platform, before the Manipal acquisition), in a 2023 Startup India interview.

How RaftLabs builds health platforms

We've built healthcare software for hospital networks, diagnostics platforms, and health-focused insurance products. The India-specific pattern -- ABDM integration, multi-HMS data normalization, Tier 2/3 optimization -- is a workstream we've done before, not one we figure out as we go.

Our process starts with a two-week scoping engagement. We map your HMS systems, your ABDM registration status, your compliance obligations under DPDP Act and Telemedicine Guidelines, and the features that drive adoption in your specific patient demographic. That scoping produces a fixed-price contract for V1. You know the number before development starts. No estimate ranges, no hourly billing surprises.

We deliver in 12-14 week cycles. The first cycle ships a working platform your patients can use. Subsequent cycles add teleconsultation, medicine delivery, lab booking, and ABDM integration as it progresses through NHA approval. If you're building for UAE or Singapore alongside India, we design the compliance architecture to handle multi-jurisdiction requirements from the start.

If you're a hospital group, insurer, or D2C health brand evaluating whether to build or buy, the first step is a scoping call. We'll tell you what the build costs, how long ABDM approval takes in your situation, and whether V1 makes sense before V3. No sales deck, no follow-up sequence.

FAQ

How much does it cost to build a health app like ekacare in India?

A PHR and appointment booking V1 costs Rs 35L-Rs 55L ($42K-$65K) over 10-14 weeks. Adding teleconsultation and medicine delivery brings it to Rs 55L-Rs 90L ($65K-$110K) over 16-22 weeks. A full super-app with ABDM integration, lab booking, and family profiles costs Rs 90L-Rs 1.4 crore ($110K-$165K) over 24-32 weeks. RaftLabs quotes fixed prices after a scoping call, so you know the number before development starts.

How long does ABDM integration take for a health app?

ABDM sandbox registration and NHA approval typically takes 6-10 weeks. Register for sandbox access on day one, not after you finish the app. Once sandbox is approved, ABHA creation and health locker integration takes 4-6 weeks of engineering. Production approval from NHA requires an audit. Budget the full 10 weeks to be safe.

Does a health app in India need to comply with the DPDP Act 2023?

Yes. The Digital Personal Data Protection Act 2023 treats health data as sensitive personal data. You need explicit consent before collecting or processing health records, data principal rights for access, correction, and erasure, and a registered data fiduciary. Cross-border data transfers face restrictions. Build consent management and data rights into your architecture from day one, not after launch.

How long does it take to build a full health super-app?

A V1 with PHR and appointment booking takes 10-14 weeks. Adding teleconsultation and medicine delivery in V2 takes another 6-8 weeks. The full super-app with ABDM, lab booking, family profiles, and wearable integration takes 24-32 weeks total. The biggest timeline variable is ABDM sandbox registration, which you should start on day one of the project.

Should a hospital chain build custom or use ekacare white-label?

Use ekacare if you have no existing patient base, need a quick launch, and are comfortable with patient data staying on ekacare's servers. Build custom if you run five or more facilities, need ABDM integration with your own HMS systems, want to own the patient relationship and data, or plan to build loyalty and cashless insurance claim workflows inside the app. Hospital chains above a certain size almost always need custom because the patient relationship is too valuable to share with a third-party platform.