Telemedicine software development: what to build and how
Telehealth exploded during the pandemic and then settled into a new normal. Virtual care is not going away, but the easy wins are already taken. Basic video consultation apps are a commodity. What actually differentiates telehealth platforms now is the clinical workflow around the video call: the intake, the scheduling, the documentation, the prescribing, and the billing.
This page covers what telemedicine software development actually involves. Not the video call part, which is solved infrastructure. The clinical platform around it, which is where the real development complexity lives.
What telemedicine software actually includes
A lot of people think telemedicine software is a video call application with a healthcare branding layer. It is not. A production telehealth platform includes:
Patient scheduling
Online self-scheduling for video appointments, with time zone handling, provider availability management, and insurance verification at booking time.
Pre-visit intake
Patient demographics, chief complaint, current medications, allergies, insurance. Collected before the visit so the physician does not spend the first ten minutes of a video call asking basic questions.
HIPAA-compliant video
WebRTC-based video that uses encrypted peer-to-peer connections. The video data does not pass through your servers, which helps with HIPAA compliance. Providers like Daily.co, Twilio Video, and Amazon Chime all offer HIPAA-eligible video infrastructure.
Virtual waiting room
Patients join a waiting area before the physician is ready. The physician can see how many patients are waiting, their wait time, and their chief complaint before starting the call.
Clinical documentation during and after the visit
Physicians need to document what happened. In a telehealth context, this means integration with the documentation system: SOAP notes, prescription documentation, referral generation.
Prescription management
E-prescribing for telehealth visits where prescriptions are appropriate. This requires integration with the NCPDP SCRIPT standard and a connection to a pharmacy network.
Post-visit follow-up
After-visit summaries sent to the patient, follow-up appointment scheduling, referral processing, lab order fulfillment.
Billing
Telehealth billing uses the same CPT codes as in-person visits (99201-99215 for office visits) but with a modifier (95 for live synchronous video, 02 for telehealth in place of service). Some payers have specific requirements for telehealth billing that differ from in-person claims.
The real-time requirements of telehealth
Video calls are the obvious real-time feature. But telehealth has other real-time requirements that affect architecture.
Queue management
Patients enter a virtual queue and wait to be seen. Physicians need to see the queue updating in real time. When a patient joins, the physician's dashboard should update immediately. When the physician is ready to start a call, the patient should be notified in real time.
Multi-party coordination
A telehealth visit might involve a physician, a nurse, and a family member. A group therapy session might involve a therapist and multiple patients. The platform needs to handle room management for these multi-party scenarios.
Status updates
When a prescription is sent, the patient should see it. When a lab order is placed, it should appear in the patient record immediately. Real-time status propagation keeps all parties informed without requiring page refreshes.
Socket.io handles most of these requirements well. For video itself, WebRTC is the standard, but managing WebRTC sessions directly is complex. Signaling servers, STUN/TURN servers, and peer connection management are all required. Using a managed service like Daily.co or Twilio Video handles the WebRTC infrastructure and lets you focus on the clinical workflow layer.
Scheduling for telehealth: it is different from in-person scheduling
Telehealth scheduling has some differences from in-person appointment booking that matter for software design.
Time zones
An in-person appointment is always in the clinic's time zone. A telehealth appointment might involve a patient in a different time zone. The scheduling system needs to handle time zone conversions correctly and display the appointment time in the patient's local time zone.
Multi-state licensing
A physician licensed in California cannot (generally) provide telehealth to a patient in Texas without a Texas license. The scheduling system needs to capture the patient's state and validate that the seeing physician is licensed there. This gets complex for platforms serving multiple states.
Provider availability across multiple platforms
Some physicians do telehealth part-time alongside in-person practice. Their availability calendar needs to account for both. Integration with existing calendar systems (Google Calendar, Outlook) is often needed.
Buffer time
Video visits need buffer time between appointments for documentation. A 15-minute video visit might need a 5-minute buffer after for notes and prescription submission.
HIPAA-compliant video: what it actually means
Video calls in healthcare have specific HIPAA requirements. Most standard video tools (Zoom, Google Meet, FaceTime) are not HIPAA-eligible by default. HIPAA-eligible video requires a vendor BAA and specific configuration.
Using a HIPAA-eligible video infrastructure provider is the right approach:
Twilio Video
Offers BAAs for healthcare use cases
Daily.co
HIPAA-eligible video APIs
Amazon Chime
Another option with AWS's BAA coverage
Zoom for Healthcare
Configured version of Zoom with BAA support
How HIPAA-eligible video works technically
From a technical standpoint, HIPAA-eligible video uses WebRTC with encrypted peer-to-peer connections. The video stream itself does not pass through the vendor's servers (it passes through STUN/TURN relay servers for connection establishment, but the actual media is peer-to-peer). This means the vendor cannot access the content of the call, which satisfies the encryption requirement.
What you need to handle at the application level:
- Authentication before joining a call
- Audit logging that a visit occurred (with physician, patient, and timestamp)
- Ensuring that call recording (if used) is stored in HIPAA-compliant storage
Asynchronous telehealth: the underbuilt opportunity
Most telehealth platforms focus on synchronous video visits. But asynchronous care is a legitimate model for several specialties.
Dermatology
A patient submits photos of a skin condition. The dermatologist reviews them on their own schedule, sends a diagnosis and prescription. No video call required.
Ophthalmology
A patient submits vision test results. The optometrist reviews and sends a prescription update.
Mental health check-ins
Between scheduled therapy sessions, patients submit mood logs, journal entries, or questionnaire responses. The therapist reviews them asynchronously and responds.
Medication management
A patient reports their medication side effects and current dosing. The physician reviews and adjusts the prescription without a live visit.
Asynchronous telehealth has lower infrastructure requirements than live video (no real-time architecture needed), but it requires careful workflow design for how submissions are routed to the right provider, how responses are delivered, and how clinical documentation is handled for the asynchronous encounter.
Telehealth billing: the specific requirements
Telehealth billing has gotten more complex as payer policies have evolved since 2020. Key things your billing module needs to handle for telehealth:
Telehealth visits use POS 02 (telehealth) rather than POS 11 (office). Some payers distinguish between POS 02 (where the provider is) and POS 10 (patient's home as the telehealth originating site).
Synchronous telehealth visits (live video or audio) use modifier 95 on standard E&M CPT codes. Not all payers accept this modifier for all codes.
Some payers reimburse audio-only (telephone) visits; others do not. CPT codes for telephone services (99441-99443) apply, but coverage varies.
Many states require insurance payers to reimburse telehealth at the same rate as in-person visits. Your billing system should be aware of state-level parity rules when processing claims.
Frequently asked questions
Telehealth software is more complex than it looks from the outside. The video call is the easy part. The clinical workflow, scheduling, documentation, multi-state licensing, and payer-specific billing requirements are where the real development complexity lives.
If you are building a telehealth platform, getting the architecture right for real-time features, HIPAA-compliant video, and the billing layer from the start will save you significant rework later.
Discuss Your Telehealth Architecture