Block 4. Integrations — EHR, Scheduling, Prescribing, Payments

1

The Telemedicine Integration Map: What Connects to What

The telemedicine integration map: EHR, scheduling, pharmacy, labs, billing, payments and identity — the standard on each link and where PHI must not flow.

2

HL7 v2, FHIR, and the EHR Integration Reality

FHIR integration vs legacy HL7 v2, SMART on FHIR app launch, and the 2026 FHIR R4 / US Core 6.1.0 baseline — what wiring a telehealth app to an EHR takes.

3

Integrating with Epic, Oracle Health (Cerner), athenahealth, and the Rest

Epic EHR integration in plain English — plus Oracle Health (Cerner), athenahealth, and aggregators like Redox: the sandbox, review, and go-live reality.

4

Scheduling and Calendar Integration

How telemedicine scheduling and calendar integration work: FHIR Appointment and Slot, EHR sync, time zones, reminders that cut no-shows, and the PHI rule.

5

e-Prescribing and EPCS

What EPCS requirements mean for a telemedicine build: DEA identity proofing, two-factor signing, third-party audits, Surescripts routing, Ryan Haight.

6

Lab Orders and Results

How to add lab orders and results to a telemedicine app: FHIR and HL7 v2, LOINC coding, the BAA boundary, and the immediate-results-release rule.

7

Payments, Insurance, and Claims

How telemedicine billing works: keep card data out of the PHI boundary, run real-time eligibility, and route 837 claims through a clearinghouse.

8

Identity, SSO, and Provider Directories

How telemedicine identity works: NIST proofing levels, mandatory MFA, provider SSO via SMART on FHIR, and the directory that gates who can practice.

9

The Integration Decision Guide: Direct, Aggregator, or Iframe

EHR integration approaches compared: direct, aggregator (Redox), embedded iframe (SMART on FHIR), or standalone — four questions to pick the right path.