How to Build a Telemedicine App in 2026: The Visit Flow First

Start with the care model, not the video call

"Telehealth app" covers very different businesses. A dermatology service that reviews photos overnight and a therapy platform with weekly video sessions share almost no workflow.

Four decisions shape the build:

1. How does care happen? Asynchronously, in live video, through device data, or a mix.
2. Where are your patients? One state or many. Licensure follows the patient.
3. Will clinicians prescribe? And if so, any controlled substances?
4. Who pays? Cash, subscriptions, employers or insurance. Insurance adds the most work.

The first answer picks your care model. Each one builds a different product:

Each model has its own budget band. The calculator in our telemedicine app development cost guide lets you switch them on and off.

How to build a telemedicine app, step by step

Nine steps. Partners and licensure start in the first weeks, because they take longer than the code. The same order works if you call it a telehealth app.

1. Pick one specialty and one or two statesA narrow start lets you hire a small clinical team with the right licenses and write intake forms that actually fit the condition. Multi-state comes after the first state works.
2. Set up the clinical and legal structureWho employs or contracts the clinicians, and under which entity? Some states restrict who can own a medical practice, so many direct-to-consumer services use a structure set up with healthcare counsel. This shapes your data model and your BAAs.
3. Sign the core partnersA video SDK, an e-prescribing partner and, if you bill insurance, a clearinghouse. Check that each signs a BAA on the plan you will use. eRx onboarding and prescriber setup take weeks.
4. Design the whole visit flowBooking, location check, intake and consent, waiting room, visit, note, prescription, payment, follow-up. Walk through it with a clinician and with a patient who has the condition.
5. Build the provider side firstClinicians need a schedule, a queue, the patient's intake, a note template and a one-click path to prescribe. If their side is slow, visits run late and your unit economics break.
6. Build the patient appsA web link that joins a visit without installing anything, plus mobile apps if patients return often. Reminders, rescheduling and a pre-visit device check cut no-shows and failed calls.
7. Add the operations consoleStaff need to see today's visits, reassign a patient when a clinician is sick, fix a payment and manage provider licenses and expiry dates.
8. Put the compliance basics inBAAs, access control, audit logs, encryption and PHI-free notifications. Our guide on how to build a HIPAA compliant app covers each one.
9. Soft launch with real visitsStart with a waitlist or one clinic. Watch connection failures, average visit length, time from booking to prescription and support tickets. Fix, then open up.

Video: rent an SDK or build on WebRTC?

Founders often ask whether to build their own video to save money. In telehealth, the math rarely works. Video SDK usage costs a few tenths of a cent per participant minute at list price, so a 20-minute visit costs around 15 cents in media.

• A video SDK gives you rooms, tokens, reconnection, network quality signals, device switching and a BAA on the right plan. You build the waiting room, the visit screen and what happens when a call drops.
• Your own WebRTC stack means running media and TURN servers, testing every browser and phone combination, and owning incidents during live visits. It makes sense at very high volume or when you need custom media processing.

Whichever you choose, keep recording off by default, never put patient names in room names, and give patients a browser link so they can join without installing an app. We go deeper on rooms, signaling and quality in how to build a video chat app.

Licensure and prescribing rules

These rules decide who can see which patient and what they can prescribe. Get them wrong and the app works perfectly while breaking the law.

• Licensure follows the patient. Clinicians generally need a license in the state where the patient is during the visit. Ask for the patient's location at booking, confirm it at visit start, and route only to licensed clinicians.
• Compacts help, but don't replace licenses. The Interstate Medical Licensure Compact, the Nurse Licensure Compact and PSYPACT speed up multi-state licensing in member states.
• State practice rules vary. Some states set conditions for establishing a patient relationship by telehealth, for async care, or for consent. Store these as rules per state.
• e-Prescribing goes through a certified partner. The partner connects to the national pharmacy network. Prescribing controlled substances electronically (EPCS) adds DEA requirements: identity proofing for prescribers and two-factor signing in certified software.
• Controlled substances by telemedicine. The Ryan Haight Act generally requires an in-person evaluation first. The DEA has extended its temporary telemedicine flexibilities several times while it works on permanent rules, and it issued a separate rule for buprenorphine treatment. Check the current status before launch.

What you build and what you rent

A telemedicine platform is mostly integration work around a visit flow you own. A typical split:

Many early-stage services run on an EHR built for virtual care and add a custom patient experience on top. Enterprise platforms sold to health systems integrate with their EHR through FHIR and launch inside it with SMART on FHIR, which adds months of site approvals.

Payments and insurance: decide early

How patients pay changes intake, the provider's note and the ops console. It is not a checkout screen you add at the end.

• Cash pay and subscriptions. The simplest path: a card processor, clear prices before booking, refunds for visits that didn't happen. Many direct-to-consumer services start here and accept HSA and FSA cards.
• Insurance. You check eligibility at intake through a clearinghouse, capture the right diagnosis and procedure codes in the note, submit claims and track denials. Telehealth billing rules differ by payer and by state, and Medicare's telehealth rules have depended on repeated extensions by Congress.
• Employer or health plan contracts. Patients pay nothing at the visit; you need eligibility files, reporting and sometimes SSO from the sponsor.

If insurance is on your roadmap, store coverage details and codes from day one, even if you bill cash at first. Retrofitting them into old visit records is painful.

What goes into the first version

A telemedicine MVP needs a complete visit loop for one specialty, not every care model. A typical split:

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Retail · Startup700+stores aggregatedMobile application for Grocery shops→Food delivery3.5 moto MVP launchOptimizing and controlling delivery for a Pizzeria Chain→EdTech4 moto a full iOS app on the App StoreA mobile app to develop brain functions→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Timeline and budget at a glance

An EHR-integrated virtual care platform for health systems typically runs $300k–700k and 7–12 months. US onshore agencies quote about 2–2.5 times these figures. For the full breakdown, video and eRx running costs and a calculator, see our telemedicine app development cost guide.

Mistakes that cost the most later

• Trusting the profile address. Licensure depends on where the patient is right now. Ask and record the location at every visit.
• Hard-coding prescribing rules. DEA and state rules have changed repeatedly since 2020. Put them in configuration your clinical team can update.
• Forgetting the clinician's day. A provider app that needs five screens per visit costs you minutes per patient, every visit.
• No plan for dropped calls. Without reconnection, audio fallback and a callback path, one bad network turns into a refund and a one-star review.
• Picking a video plan without a BAA. Many SDKs sign BAAs only on certain plans. Switching vendors after launch means rebuilding the visit screen.
• Adding insurance "later" when patients expect it. In specialties where patients expect coverage, cash-only launches stall. Decide early, because eligibility belongs in intake.

Telemedicine launch checklist

Tick what is already true for your service. It shows how close you are to the first real visit.

FAQ

Where Gilzor fits

We build healthcare web and mobile apps, backends, integrations and QA. For a US blood testing laboratory, our team built native iOS and Android apps and web apps where patients book an online consultation with a doctor, the doctor orders tests, and results and follow-up come back through the app. We work from Poland and Cyprus, with a few shared hours a day with the US East Coast.

Send us your specialty, your care model and the states you plan to serve. We'll map the visit flow, the partners you need and a first version you can launch in one state.