Telemedicine app development in 2026: cost, features, timeline
TL;DR
Telemedicine app development in 2026 costs from $25,000 to more than $700,000 across the eight vendor guides we checked, and takes from 2 to 3 months for a simple app to 9 to 16 months for a multi-role platform. The spread is scope. Video is the cheap, rented part: Twilio Video bills $0.004 per participant per minute, so a 20-minute, two-person visit costs 16 cents in media. Prescribing, EHR integration, clinician tooling and mobile platform rules carry the budget.
- Four of the eight guides start their entry tier at $40,000 and top it out between $70,000 and $90,000.
- E-prescribing quotes run from $10,000 to $100,000; DoseSpot says a certified integration can be live in as little as 30 days.
- DEA telemedicine prescribing flexibilities end December 31, 2026. Medicare's non-behavioral ones run through December 31, 2027.
- A scheduled visit runs in the browser. Native code earns its cost when the app has to ring.
Telehealth is a routine part of the clinical week
Start with demand, because it decides the backlog. FAIR Health's Q2 2026 tracker release puts telehealth at 5.6% of medical claim lines for the commercially insured, with 18.3% of patients filing a telehealth claim. Mental health was the top diagnostic category nationally and in every region: 53.7% of patients with a telehealth claim had one for a mental health condition.
The clinicians are already there. NCHS found that 80.0% of office-based physicians used telemedicine in 2024, and in AMA survey data 49.6% of physicians had run a video visit in the week before the survey.
Grand View Research estimates the global market at $157.9 billion in 2026. Fine for a board slide. The claims data says more: you are most likely building recurring, scheduled sessions, often behavioral, for clinicians who already know another video tool. Yours has to be the easier one to open.
Four dates to design for before 2028
Each date below ends up as a field or a control in your system, so it belongs in the architecture review.
December 31, 2026. The DEA and HHS fourth temporary extension of telemedicine flexibilities for prescribing controlled medications runs through that date. Its intended successor, a special registration rule, has been at OIRA review since August 25, 2026, with no public text, per McDermott Will & Schulte. Opioid use disorder has its own path: the buprenorphine rule, which the extension notice says took effect December 31, 2025, allows an initial six-month supply, split across prescriptions, after a telemedicine encounter. In code: a prescriber registration record, the patient's location per encounter, an exportable prescribing log.
May 11, 2027. HHS funding recipients with 15 or more employees must meet WCAG 2.1 level AA for web content and mobile apps, after the May 7, 2026 extension. Booking, the waiting room and the in-call controls are all web content or app screens, so build them to that standard.
July 2027. The Unified Agenda carries the HIPAA Security Rule overhaul as a long-term action, with final action projected for that month. The proposal would require multi-factor authentication, encryption of ePHI at rest and in transit, and a penetration test at least once every 12 months. Visit recordings are ePHI at rest.
December 31, 2027. Medicare covers non-behavioral telehealth in the patient's home through that date, per Telehealth.HHS.gov. Behavioral telehealth at home is permanent, but its in-person visit requirement is waived only until the same date. Keep those rules in configuration, so a policy change is a setting rather than a release.
How we compared the numbers
Three rules, applied to every figure below.
- A price counts only if a vendor publishes it on its own live page. We use each vendor's tier labels where it has them and read every page on October 16, 2026.
- Run costs come from each video provider's own pricing page. Platform rules come from Apple, Google, the IETF and WebKit; regulatory dates from the Federal Register, HHS, CMS and eCFR.
- Our own figures are shares rounded to five points, and any group with fewer than three data points is not published.
Two disclosures. Mercury Development builds telemedicine software natively and cross-platform and has built web apps since 2008, so we earn from every option here. The author contributes to Bubblewrap and PWABuilder, tools that package web apps for app stores, and the last section argues for the web.
Published telemedicine app cost bands at a glance
| Published guide | Lowest published band | Highest published band | Published timeline |
|---|---|---|---|
| Space-O Technologies | $25,000 to $80,000, basic | $150,000 to $300,000+, advanced | 3 to 4 months up to 6 to 12 months |
| Cleveroad | $40,000 to $70,000, MVP | $100,000 to $300,000+, enterprise | 1,200 to 2,400 hours |
| Appinventiv | $40,000 to $70,000, simple | $100,000 to $300,000, highly complex | 2 to 3 months up to 9+ months |
| TechnBrains | $40,000 to $70,000, basic MVP | $120,000 to $300,000+, enterprise | 2 to 4 months up to 8 to 14+ months |
| Fora Soft | $40,000 to $90,000, Tier 1 MVP | $400,000+, Tier 3 enterprise | 12 to 16 weeks up to 9 to 14 months |
| Saigon Technology | $75,000 to $120,000, basic | $150,000 to $250,000+, custom | 2 to 6+ months of development |
| Attract Group | $80,000 to $180,000, scheduling and video MVP | $300,000 to $700,000+, multi-role platform | 3 to 5 months up to 9 to 16 months |
| Topflight Apps | $150,000 to $200,000, simple platform | $300,000 to $450,000, next band up | not published in months |
Eight guides, floors six times apart. Read the overlap, not the average: four of the eight start their entry tier at $40,000, and four top out at $300,000 or $300,000 plus.
In most guides the tier jumps follow the same short list: EHR integration, e-prescribing, more user roles. Attract Group's top tier adds EHR and FHIR integration, e-prescribing through Surescripts or an equivalent, remote monitoring and role-based access for several provider types. Fora Soft instead puts e-prescribing and a lightweight EMR inside its $40,000 to $90,000 Tier 1. Before comparing two quotes, check which definition of MVP each one uses.
The video call is the cheapest line on the bill
The visit screen sells the project. It is also close to the cheapest line in it.
Build cost first. Guides price the video module from $3,500 for 70 hours of patient-side work at Cleveroad up to $20,000 to $40,000 at Topflight Apps. Fora Soft draws the line that matters: a self-hosted media server only earns its keep in the millions of monthly participant-minutes. Below that, wire a vendor SDK.
Then run cost. Twilio Video bills $0.004 per participant per minute in group rooms and lists itself as HIPAA eligible; its FAQ says Twilio can sign a business associate agreement. Daily charges $0.004 after 10,000 free minutes a month, plus $500 a month for its HIPAA and BAA add-on. Vonage lists $0.00410 and sells the BAA through sales. LiveKit offers BAAs to Scale and Enterprise customers.
Do the arithmetic once. A 20-minute visit with two participants is 40 participant-minutes: $0.16 on Twilio, $0.32 if you record both. At 5,000 visits a month, media costs $800 before recording.
Access and storage decide whether you need a BAA. RFC 8827 says all WebRTC media channels MUST be secured via SRTP. Through a media server, RFC 9605 describes two layers: hop-by-hop to the server, and end-to-end, which the server cannot decrypt. Unless you add the second layer, for example with SFrame, the media server decrypts the stream and can read it. HHS guidance requires a BAA with any vendor that is more than a mere conduit for PHI, and one that records visits is past that line.
The features that belong in release one
The guides converge on the same core, and the list is right. Patients get sign-up with identity checks, intake and consent, scheduling, a waiting room, the visit with chat as a fallback, a summary, payment and reminders. Clinicians get availability, a queue and notes. Admins get credentialing and an audit log.
Two fields get missed and cost the most to add later. One is the patient's location for each visit, because a clinician generally has to be licensed or legally permitted to practice in the state where the patient is located, per Telehealth.HHS.gov. The other is each clinician's state licenses: the Interstate Medical Licensure Compact lists 44 member states plus DC and Guam as of September 30, 2026, three of them still implementing, and a compact speeds licensure up without removing it.
Defer the rest out loud. AI scribes, remote monitoring, insurance claims and white-label tenancy sit in the upper tiers of most of these guides.
How to charge for visits and memberships without breaking store rules is covered in our guide to HIPAA compliant payment processing.
E-prescribing: integrate a certified network or carry the audit
E-prescribing quotes run from $10,000 to $30,000 at Space-O and $15,000 to $25,000 at Topflight Apps up to $40,000 to $100,000 at Attract Group. The gap is one decision: whose software carries the DEA obligations.
Build electronic prescribing of controlled substances yourself and 21 CFR Part 1311 becomes your spec. It requires identity proofing at NIST SP 800-63-1 Assurance Level 3 or above, two-factor authentication, and a third-party audit before the application handles a single controlled substance prescription. The audit repeats whenever that functionality changes or every two years; certification by a DEA-approved organization on the same schedule can replace it.
Most telemedicine products should not carry that. DoseSpot says its JumpStart platform is Surescripts and EPCS certified and, development and certification included, can have you e-prescribing in as little as 30 days. Fora Soft reports that DrFirst and Surescripts quote typically $40 to $90 base per provider a month, plus an EPCS module. Your prescribers have their own stake: CMS counts a prescriber as compliant at an EPCS rate of 70% or higher, and began its 2025 non-compliance notifications in September 2026.
EHR integration is a second project with its own budget
Guides disagree here more than anywhere. Cleveroad prices EHR integration at $4,000 to $7,000, Space-O at $15,000 to $50,000, Attract Group at $30,000 to $80,000 or more per EHR. Fora Soft quotes $10,000 to $30,000 in development plus $1,500 to $8,000 a month through an aggregator such as Redox, or $40,000 to $120,000 for direct SMART on FHIR with Epic or Oracle Health.
The API is rarely the expense. Epic lists over 750 no-cost APIs and interfaces for app developers, and Redox starts its Core plan at $35,000 a year. You pay for direction and ownership. Reading demographics into the visit is routine. Writing the note back into the chart is separate scope with its own approval, and someone has to decide which record wins a conflict. Settle that before design.
Teams that build and connect these interfaces are ranked in our list of EHR/EMR development companies.
Platform rules that set the mobile timeline
A telemedicine app that rings is a calling app to both mobile platforms, and both make you build it as one.
On iOS, Apple's PushKit documentation says apps receiving VoIP pushes must report the call quickly to CallKit, and apps linked against the iOS 13 SDK or later are terminated if they fail to. An on-demand visit that has to ring like a phone call needs VoIP pushes, and VoIP pushes need CallKit. Scheduled visits joined from a reminder can use ordinary notifications.
On Android, an app targeting Android 14 or higher that keeps a call running in a foreground service must declare the service type, such as camera, microphone or phone call, and again in Play Console with a demo video, per Play Console Help. Full-screen incoming-call screens are for calling and alarm apps: Google Play revokes the default USE_FULL_SCREEN_INTENT permission from apps that don't fit that profile, per Android's behavior changes.
Store rules sit on top. Apple's App Review Guidelines say healthcare apps should be submitted by the legal entity that provides the services, and that apps may not store personal health information in iCloud. Google Play requires a Health apps declaration from every published app. New Play apps and updates must target Android 16 since August 31, 2026, with extensions available to November 1, 2026, and App Store uploads must be built with Xcode 26 since April 28, 2026.
Review itself is quick. Apple says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. If a plan budgets weeks for review, ask what the weeks are for.
Which entity submits the app and through which route is covered in our guide to App Store approval for healthcare apps.
How long a telemedicine app takes to build
Published phase plans agree on the order and disagree on the length. Attract Group's is the most detailed:
- Discovery and requirements: 2 to 4 weeks, against 1 to 2 weeks of paid discovery at Fora Soft.
- UX design and prototype: 3 to 6 weeks.
- MVP development: 8 to 16 weeks. Fora Soft quotes 12 to 16 weeks for its whole Tier 1.
- Integration and compliance hardening: 4 to 8 weeks.
- Pilot and iteration: 4 to 8 weeks.
- Store review: 2 to 4 weeks for Apple, against Apple's own 48-hour figure for 90% of submissions.
Attract Group totals that at 5 to 12 months to an initial MVP launch and 10 to 18 months for a full platform.
Four dependencies sit outside the code and can hold up launch on their own: business associate agreements with every vendor that touches PHI, EHR sandbox access, prescriber identity proofing and organization developer accounts, which on Apple require a D-U-N-S Number. Start all four in week one.
What a telemedicine app costs to run
Run costs scale with visits and clinicians, not with screens.
- Maintenance: 15 to 20% of build cost a year at Topflight Apps and Fora Soft, 15 to 25% at Attract Group.
- Hosting: $500 to $5,000 or more a month at Appinventiv. Fora Soft puts a direct primary care platform with 1,500 to 5,000 patients at about $1,500 to $5,000 a month.
- Media: the per-minute arithmetic above, plus any HIPAA add-on.
- Security testing: $10,000 to $30,000 per round at Attract Group, and the Security Rule proposal would make a penetration test annual.
- Platform upkeep: an app that is not rebuilt to the stores' current SDK requirements cannot ship fixes.
The run year is broken down line by line in our guide to healthcare app maintenance cost.
Which budget fits your project
| Your situation | Published band to plan against | What decides it |
|---|---|---|
| Scheduled video visits for one practice, browser first, no prescribing | $25,000 to $90,000 | Whether release one includes payments and a clinician console |
| Patient apps on iOS and Android with chat, payments and an admin panel | $70,000 to $180,000 | Native or cross-platform, and whether the app has to ring |
| Prescribing through a certified vendor plus one EHR connection | $120,000 to $300,000 | Read-only or write-back EHR integration |
| Multi-role, multi-state platform with EHR write-back, EPCS and remote monitoring | $300,000 to $700,000+ | Number of systems of record |
| Off-the-shelf telehealth software instead of a build | $30 to $300+ per provider per month | Whether your workflow is the product |
The bands are compiled from the guides in the first table, not from our quotes. The last row is Attract Group's SaaS range.
What our telehealth requirement and code reviews show
Counted by hand in October 2026 from our healthcare requirement records where the requested product put a patient or study participant on live video with a clinician or care team. Veterinary products were excluded. Record counts stay unpublished under our client agreements, and shares are rounded to five points.
- None started from a blank page. Each request extended something the buyer already ran: a shipped app, a prototype, a service platform or a research system.
- Around 60% needed the existing code stabilized or reviewed before feature work could be planned. Typical finds: a mobile build that would not compile, screens grown without boundaries, a legacy platform to check for salvageable code.
- Around 60% named HIPAA in their requirements.
- Around 60% needed clinician or admin tooling in the same scope as the patient side.
Requests that named a specific video vendor, needed e-prescribing or needed EHR write-back each had fewer than three data points, so we do not publish those shares.
Video was never the whole scope and never the hard part. The hard part was the codebase the video had to live in.
Start the visit in the browser, go native when it has to ring
Opinion, with the mechanism.
A scheduled visit is a link the patient taps at a known time, and browsers already do that well. WebRTC peer connections work in browsers covering 97.26% of global usage, Safari on iOS since version 11, and doxy.me runs visits from a single link with no apps. A browser-first patient side skips installs and store review, and Fora Soft puts the saving at $30,000 to $60,000 of native development. We have moved clinical software this way before: a 510(k) FDA-cleared imaging application went from Windows desktop to HIPAA-compliant multi-user web access in three months.
Native code earns its cost at three moments. When the app must ring, because iOS ties VoIP pushes to CallKit. When the call has to keep running while the patient uses another app, which is what Android's camera and microphone foreground service types exist for. And when a device joins the visit, because Web Bluetooth is not supported in Safari on iOS. Reminders are not on the list: once added to the Home Screen, web apps on iOS have received Web Push since iOS 16.4.
So ship the web visit first, and build native only for the flows that need it. For the vendor view, our ranking of telemedicine app development companies covers who builds these products and what each one leaves out.
Written by Alexey Rodionov, Lead Front-end Developer at Mercury Development since 2020. Alexey is a Google Developer Expert in Web Technologies and a Chromium contributor whose code ships in Chrome DevTools, Google's Bubblewrap and Microsoft PWABuilder. The requirement and code reviews behind this article's own figures, where incoming telehealth briefs and inherited codebases are read for video, platform and integration constraints, come from the engineering practice he works in.
Send us your visit flow, and we will mark what needs native code
Tell us how a visit starts, who joins it, what it has to prescribe or write back, and which systems hold your records. We will return a build map: what runs in the browser, what needs native code, which vendors need a BAA and where the integration risk sits.