Telemedicine app development services for video visits and remote care
Our telemedicine app development services cover the full patient journey online: booking, identity check, a pre-visit questionnaire, the video visit, secure messaging, prescriptions and follow-up, plus the clinician tools that make a remote day of appointments run on time. We build for iPhone, Android and the web, with health data handled under GDPR or HIPAA from the first version, and your organisation owns the code. Whether you name it telehealth or telemedicine, our telehealth app developers work as one team with design, backend and testing, from the first written scope to the approved store listing.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Who we build telemedicine apps for
Our telemedicine work is for private clinics and clinic chains adding remote visits, occupational health providers, mental health and therapy services, specialist practices following up patients between visits, digital health startups building their first product, and hospitals adding video and messaging to existing patient services. The common thread is a care team that already knows how to treat patients and needs software that makes remote care as reliable as a visit in person, without adding work for clinicians.
What we build
- Booking and triage. Appointment types, clinician calendars, a questionnaire that routes the patient to the right professional, reminders and a waiting room.
- Video visits. Encrypted video in the app and the browser, built on WebRTC, that adapts to a weak connection, falls back to audio, and lets the clinician invite an interpreter or a family member.
- Secure messaging. Messages and photos between patient and care team, with response time rules, handover between clinicians and an audit trail.
- Clinician console. The day's visits, patient background, notes, templates and the summary sent to the patient after the visit, in one view.
- Prescriptions and referrals. Integration with the national e-prescription service or your prescribing system, and referrals to laboratories and specialists.
- Remote monitoring. Readings from home devices or the phone's health data, with thresholds that alert the care team. This is the feature most likely to be a medical device, so it is scoped separately.
- Payments and insurance. Card payment through a payment provider, insurer or employer billing, and receipts for reimbursement.
Integration with the record
A telemedicine app should not become a second patient record. Visit notes, prescriptions and results belong in your electronic health record, and the app reads and writes them through its interfaces, preferably HL7 FHIR, with the clinician's own identity and permissions. Patients sign in with strong authentication, such as a national e-identity where one exists. The app stores as little as possible on the device and keeps every view and change in an audit log. Our guide to hospital mobile apps explains FHIR integration and the European Health Data Space in more detail. If the app itself calculates, monitors or supports diagnosis, it may be a medical device; see medical device software development.
The rules that shape a telemedicine app
Most of what makes telemedicine different comes from health and data law. We do not give legal advice; your legal and regulatory advisers decide what applies. The rules we build for most often are these (all read on 11 November 2026):
- GDPR. Health data is a special category of personal data. Each data item has a documented purpose and legal basis, a data protection impact assessment is done before launch, and every supplier signs a data processing agreement.
- Cross-border care in the EU. Directive 2011/24/EU on patients' rights in cross-border healthcare states that in the case of telemedicine, healthcare is considered to be provided in the Member State where the healthcare provider is established, and lets the patient's own country apply the same conditions to reimbursement of care received through telemedicine as it would at home.
- Medical device rules. Software intended for diagnosis, monitoring or treatment decisions can fall under the EU Medical Device Regulation or FDA oversight. Booking, video and messaging do not; remote monitoring with alerts or symptom checkers that suggest a diagnosis can.
- HIPAA in the United States. Under 45 CFR 160.103, a business associate is a person who creates, receives, maintains or transmits protected health information on behalf of a covered entity, and the definition includes subcontractors of a business associate. The technical safeguards in 45 CFR 164.312 include audit controls, automatic logoff and encryption.
- Prescribing controlled medicines remotely in the US. The DEA and HHS published a fourth temporary extension of the telemedicine flexibilities for prescribing controlled medications on 31 December 2025, running through 31 December 2026. A US service that prescribes such medicines needs a plan for whatever rule follows, built into the prescribing flow as a setting rather than hard-coded.
Getting through app review
Apple's App Review Guidelines treat healthcare as a regulated field. Guideline 5.1.1(ix) asks that apps in highly regulated fields such as healthcare be submitted by a legal entity that provides the services, not by an individual, so the app is published under your organisation's account. Guideline 1.4.1 says medical apps that could be used for diagnosing or treating patients may be reviewed with greater scrutiny, and that a regulatory clearance should be linked when there is one. Guideline 5.1.3 forbids using health data for advertising and storing personal health information in iCloud. On payments, guideline 3.1.3(d) allows one-to-one real-time services, with medical consultations named as an example, to be paid with methods other than in-app purchase. We plan the store submission from the start, with a demo account and test data for the reviewers.
Video that works on a bad day
A video visit fails in ordinary ways: an elderly patient on an old tablet, a weak mobile signal in a parked car, a clinician's laptop with two cameras. We design for those cases. The app tests camera, microphone and connection before the visit, adapts video quality to the bandwidth, falls back to audio when video is not possible, reconnects without losing the session, and gives the clinician a one-tap way to switch to messaging. Recording is off by default and only used with consent where your policy allows it.
Accessibility and design for patients
Patients using telemedicine may be unwell, anxious, elderly or reading in a second language. That means large text and touch targets, plain words instead of clinical shorthand, few steps to join a visit, captions where possible, and testing with VoiceOver and TalkBack against WCAG 2.2. A visit link that opens in the browser without installing anything helps the patients least comfortable with apps.
How we build it
- Care pathway workshop. Clinicians and administrators walk through a typical remote visit from booking to follow-up.
- Regulatory questions in writing. Medical device status per feature, data protection impact assessment and the markets you serve.
- Scope and fixed price in writing. Apps, integrations, the first pathway and what this phase leaves out.
- Pilot with one team. Real visits with a small group of clinicians and patients, through TestFlight and Google Play testing, before the public launch.
- Launch and extend. No-show rates, visit length and patient feedback tracked from the first week, then the next pathway.
Video visits are one kind of health app. For patient access, care companions, remote monitoring and reimbursed apps, see healthcare mobile app development.
You own it
As a standard term, the source code is in a repository in your organisation's own account, and the store listings, hosting and video infrastructure are in your organisation's name. Hosting runs in an EU region for European providers. You can keep us for maintenance, run it yourself or hand it to another team. For delivering prescribed medicines after a consultation, read our guide to medicine delivery app development. For the SaaS side of a digital health product, read our healthcare SaaS guide; for staff rosters, see healthcare scheduling software; and for the app build in general, see app development. For the patient record behind the visits, see EHR software development. See prices. For booking the visits, in person and remote, see patient appointment scheduling software.
Questions we get
What does a telemedicine app need in its first version?
Usually booking, identity check, a pre-visit questionnaire, the video visit itself, a summary afterwards and secure messaging with the care team, plus a clinician view to run the day. Payments, e-prescriptions and remote monitoring are added when the first flow is in daily use.
Can patients pay for consultations in the app without Apple's in-app purchase?
For one-to-one real-time consultations, yes. Apple's guideline 3.1.3(d) lets apps that sell real-time person-to-person services, with medical consultations named as an example, use purchase methods other than in-app purchase. One-to-few and one-to-many services, such as group classes, must use in-app purchase.
Is a telemedicine app a medical device?
Booking, video visits and messaging are not medical devices. Features that diagnose, monitor a condition with alerts or recommend treatment can be. We answer that question for each feature in writing, with your regulatory adviser, before it is built.
Can we serve patients in other EU countries?
Often, yes. Under the EU's cross-border healthcare rules, telemedicine is considered provided in the Member State where the healthcare provider is established. Licensing of your clinicians and reimbursement by the patient's insurer still follow national rules, so your advisers confirm each market.
Do you sign a business associate agreement for US clients?
Yes. Under HIPAA, a supplier that creates, receives, maintains or transmits protected health information on behalf of a covered entity is a business associate, and so are its subcontractors, such as the hosting provider. We sign the agreement and make sure the chain behind us is covered.
Who owns the app, the code and the patient data?
Your organisation. The code is in your repository, the store listings and hosting are in your organisation's name, and patient data stays in the region you choose, in the EU for European providers.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.