The Telemedicine Inflection Point
Telemedicine — the delivery of healthcare services using digital communications technology — was a slowly growing field for decades before the COVID-19 pandemic compressed a decade of adoption into a matter of months. Between February and April 2020, telehealth visit volumes increased by 154% in the United States alone. Similar step-changes occurred across the Asia-Pacific, Europe, and the Middle East as lockdowns made in-person care impossible and patients and providers discovered that many consultations can be conducted effectively at a distance.
What has followed is not a return to baseline but a new equilibrium. Telemedicine now occupies a permanent, mainstream position in healthcare delivery in most high- and middle-income countries. For healthcare organisations considering or expanding their telemedicine capability, the question is no longer whether to invest but how to do it well.
Types of Telemedicine
Understanding the types of telemedicine is essential for defining the scope of a telemedicine programme and making appropriate technology choices.
Synchronous Telemedicine
Synchronous telemedicine involves real-time, two-way communication between patient and provider — typically a video consultation, though telephone-only consultations remain valuable for patients without video capability. This is the closest digital equivalent to an in-person consultation and is the most familiar form of telemedicine for most clinicians and patients.
Video consultations are appropriate for a wide range of clinical scenarios: follow-up consultations for established conditions, mental health consultations, medication reviews, post-operative checks, and many acute presentations that can be assessed without physical examination. They are not appropriate for every situation — examinations requiring palpation, auscultation, or invasive procedures require in-person attendance.
Asynchronous Telemedicine
Asynchronous telemedicine — also called "store and forward" — involves the collection and transmission of clinical information from patient to provider for review at a later time. The patient uploads images, completes questionnaires, records symptoms, or submits investigation results; the clinician reviews this information and responds, without both parties needing to be present simultaneously.
Dermatology (skin lesion assessment), ophthalmology (retinal imaging review), radiology (teleradiology), and chronic disease monitoring are well-established asynchronous telemedicine applications. The advantage is efficiency: a clinician can review asynchronous consultations in batches, managing a higher volume than would be possible in synchronous appointments.
Remote Patient Monitoring
Remote patient monitoring (RPM) involves the continuous or periodic collection of patient-generated health data — blood pressure, blood glucose, pulse oximetry, weight, ECG — via connected devices, with transmission to the clinical team for monitoring and intervention when needed. RPM is particularly valuable for patients with chronic conditions (heart failure, hypertension, diabetes, COPD) who need frequent monitoring but do not require regular in-person visits.
RPM programmes require robust infrastructure: connected devices that are reliable and easy for patients to use, secure data transmission, an analytics platform to identify patients who need intervention, and clinical workflows for triage and response.
Technical Requirements
Video Conferencing Infrastructure
For synchronous telemedicine, the video platform is the core technical component. Requirements include:
- Video and audio quality: Minimum 720p video and clear audio are required for clinical consultations. Network-adaptive bitrate ensures quality degrades gracefully on poor connections rather than failing completely.
- Security: End-to-end encryption is mandatory for clinical consultations. The platform must comply with relevant data protection regulations (HIPAA in the US, GDPR in Europe, and equivalent frameworks elsewhere).
- Accessibility: The platform must be usable without software installation for patients, functioning in a standard web browser on both desktop and mobile devices.
- Integration with EHR: The consultation should be documented in the patient's EHR record. Ideally, the video session is launched from within the EHR, the encounter is automatically created, and the clinician can access the patient's record during the consultation.
Messaging and Asynchronous Communication
Secure clinical messaging — integrated with the EHR patient record — enables asynchronous telemedicine workflows. Patient-submitted photos, symptom questionnaires, and follow-up queries are received and managed through the messaging platform, with responses documented in the clinical record.
Integration with EHR/HIS
EHR integration is what distinguishes a clinically embedded telemedicine platform from a generic video calling application. Key integration requirements include:
- Appointment scheduling: Telemedicine appointments booked through the patient portal or call centre should appear in the clinician's schedule alongside in-person appointments
- Encounter documentation: The consultation should create an encounter record in the EHR where the clinician can document findings, prescriptions, and referrals
- Pre-consultation data access: The clinician should be able to review the patient's history, medications, and test results before and during the consultation
- Post-consultation workflow: Prescriptions, referrals, and follow-up appointments initiated during the telemedicine consultation should follow the same workflow as those from in-person encounters
FHIR integration is increasingly the standard mechanism for telemedicine-EHR connectivity, with FHIR Appointment, Encounter, and Communication resources providing the structural framework.
Regulatory and Consent Considerations
Telemedicine regulation varies significantly by jurisdiction and is evolving rapidly. Key considerations include:
Licensure and scope: In many jurisdictions, clinicians must hold a licence in the patient's location to provide telemedicine services. Multi-state or cross-border telemedicine requires understanding of applicable licensure frameworks. The US Interstate Medical Licensure Compact (IMLC) facilitates multi-state licensing for physicians.
Prescribing: Remote prescribing rules — particularly for controlled substances — are tightly regulated in most jurisdictions. In the US, the DEA's telemedicine rules govern remote prescribing of scheduled substances.
Informed consent for telemedicine: Patients should be informed that their consultation is occurring via telemedicine, the limitations of remote assessment, and their right to an in-person consultation. Consent should be documented in the clinical record.
Data residency and privacy: Where patient data is stored and processed is regulated in many jurisdictions. Cloud-hosted telemedicine platforms must comply with data residency requirements — for example, the requirement that health data about EU citizens be processed within the EU under GDPR.
Patient and Provider Adoption
Technology alone does not create a successful telemedicine programme. Adoption barriers on both sides must be actively managed.
For patients, the key barriers are digital literacy (particularly in elderly populations), device or connectivity limitations, concerns about privacy, and a preference for in-person care for complex or sensitive issues. Strategies to address these include clear patient-facing instructions, telephone-based consultation options for patients without video capability, and proactive outreach to patients who would benefit from remote monitoring.
For clinicians, barriers include unfamiliarity with the technology, concern about reduced diagnostic accuracy, documentation burden, and workflow disruption. Addressing these requires adequate training, EHR integration that reduces rather than adds to documentation burden, and clinical leadership championing of telemedicine as a legitimate and valuable care modality.
Infrastructure Requirements
The infrastructure requirements of a telemedicine programme extend beyond the software platform:
Network bandwidth: Video consultations require sustained bandwidth of at least 1–2 Mbps per consultation. Healthcare facilities hosting multiple concurrent video consultations need to plan network capacity accordingly.
Clinical workstations: Clinicians need appropriate hardware — webcam, microphone, headset — that may not be standard issue. In specialist settings, additional peripherals such as digital stethoscopes, otoscopes, or dermoscopes may be relevant.
Patient-side connectivity: In RPM programmes, patient devices require reliable home internet or cellular data. In some programmes, the healthcare organisation provides connected devices to patients with limited digital access.
Build vs Buy Decision
Most healthcare organisations should not build a telemedicine platform from scratch. The development and maintenance costs are significant, and the regulatory compliance requirements (security, privacy, medical device classification in some jurisdictions) are demanding.
The build vs buy decision is better framed as a question of integration depth and branding. Pure SaaS telemedicine platforms (Teladoc, Doxy.me, Doceree, and many regional providers) offer rapid deployment but limited EHR integration. EHR-native telemedicine modules (Epic MyChart Video Visits, Oracle Telehealth) offer deep integration but may be less feature-rich. Custom-integrated platforms built on specialist video APIs (Vonage, Twilio, Daily.co) can offer both — at a higher development investment.
The right choice depends on the scale and complexity of the telemedicine programme, the EHR environment, and the organisation's technical capability to manage ongoing development.
FZ Consulting LLP provides telemedicine strategy, platform selection, and implementation advisory services for healthcare organisations at all stages of their virtual care journey. Contact our team to discuss your telemedicine programme.