Telehealth integration with FHIR-based EHRs in 2026 works through four established patterns. Picking wrong burns integration budget and produces workflow friction.
Pattern 1: SMART-launched telehealth app. SMART on FHIR launch spec provides the pattern: telehealth app launches from EHR with patient context, reads clinical data, writes visit notes back as Encounter + Observation resources. Best for tightly-integrated telehealth workflows.
Pattern 2: External telehealth platform + FHIR sync. Doxy.me, Zoom for Healthcare, or custom platforms run separately from the EHR. Visit metadata (start/end, participants) syncs to FHIR as Encounter resources; clinical documentation happens in the EHR post-visit.
Pattern 3: Ambient documentation during telehealth. Voice-recognition tools (Nuance DAX, Suki, Abridge) capture the visit, extract clinical documentation, write to FHIR as Observation and Condition resources.
Pattern 4: Async telehealth (store-and-forward). Patient submits photos, symptoms, or questions via Questionnaire; clinician reviews and responds asynchronously. QuestionnaireResponse → clinical review → Task or Communication resource.
Vendor state (mid-2026)
| Platform | SMART launch | FHIR sync | Ambient integration |
|---|---|---|---|
| Doxy.me | Add-on | Basic | External |
| Zoom for Healthcare | Add-on | Basic | External |
| Amwell | Full | Full | Native |
| Teladoc | Full | Full | Native |
| Epic MyChart Video | Native | Native | Epic Nuance DAX |
Documentation quality
Ambient documentation lifts clinical note quality significantly (measured by completeness against clinical criteria) but requires terminology binding discipline. Site-specific vocabularies need custom ConceptMap or the notes contain non-standard codes.
Common integration mistakes
1. Video-only, no EHR sync. Telehealth data trapped in platform; not part of longitudinal chart. 2. No SMART launch. Clinician context-switches between EHR and telehealth tool, slowing workflow. 3. Ambient documentation without review. Auto-generated notes need clinician verification before finalization.
Telehealth on FHIR is now a mainstream integration pattern. The four above cover essentially every deployment; pick based on workflow requirements.
