Gantt Chart for Telehealth Program Launch

Telehealth has moved from a pandemic-era emergency measure to a permanent, growing component of healthcare delivery. The question for health systems, medical practices, and payers is no longer whether to implement telehealth — it's how to do it rigorously enough to deliver quality care, maintain billing compliance, navigate the still-evolving regulatory landscape, and actually get physicians to use it.

A telehealth program launch is not simply a technology installation. It is a clinical program design project that happens to require a technology platform. The platform selection, EHR integration, workflow design, provider training, patient communication, and regulatory compliance all must converge before the first virtual visit. A Gantt chart that maps all of these workstreams — and their dependencies — is what separates a telehealth launch that serves patients from one that creates new administrative problems while solving old clinical ones.

---

Telehealth Program Types and Their Gantt Implications

Before building the Gantt chart, define the telehealth program type — each has different platform requirements, regulatory considerations, and implementation complexity:

Synchronous video visits (primary focus of this guide): Real-time video between patient and provider. The dominant telehealth modality. Requires: platform selection, EHR integration, scheduling workflow, documentation templates, billing workflow (place of service code 02, modifier GT), and provider training.

Asynchronous (store-and-forward): Patient submits photos, history, or data; provider reviews and responds without real-time interaction. Common in dermatology (photo review), ophthalmology (retinal screening), and some primary care use cases. Lower platform complexity; different billing rules.

Remote Patient Monitoring (RPM): Patient uses connected devices (blood pressure cuff, glucometer, continuous glucose monitor, pulse oximeter, weight scale) at home; data transmits to care team for review. Separate Medicare benefit (CPT codes 99453, 99454, 99457, 99458). Requires RPM platform, patient device provisioning, care management workflow.

Direct-to-Consumer (DTC) telehealth: Health system competes with Teladoc, MDLive, Amazon Clinic for urgent care or primary care visits. Higher marketing investment, patient acquisition cost, and platform requirements for consumer-facing experience.

This guide focuses on health system and medical practice synchronous video visit programs — the most common implementation.

---

Phase 1: Strategic Planning and Service Line Selection (Months 1–3)

Service line selection:

Not all clinical services are equally suited to telehealth. High-utility service lines for video visits:

Target patient population:

• Established patients (most payers require an established relationship for most telehealth services — verify payer-specific rules)
• Patients with transportation challenges (rural, elderly, disabled)
• Patients managing chronic conditions who benefit from higher visit frequency without travel burden

Payer analysis — telehealth reimbursement landscape:

Telehealth reimbursement is the most rapidly changing element of healthcare policy in the current era. Key facts as of 2026:

• Medicare: Telehealth coverage expanded dramatically during the COVID-19 public health emergency. Many expansions have been extended through legislation but require annual reauthorization. Verify current Medicare telehealth benefit at CMS.gov before finalizing service line scope.
• Medicare Advantage: Plans may cover telehealth beyond traditional Medicare; verify plan-by-plan
• Medicaid: State-by-state — some states cover telehealth broadly (California, Florida); others have narrow coverage (check state Medicaid agency)
• Commercial: Most major commercial payers cover synchronous video visits at parity with in-person visits (parity laws in 40+ states require equal coverage); verify your specific payer contracts

---

Phase 2: Platform Selection (Months 2–5)

Platform selection is the most consequential technology decision in a telehealth launch. The platform determines: patient experience, provider experience, EHR integration depth, data retention and HIPAA compliance, and total cost of ownership.

Platform categories:

EHR-native platforms:

• Epic MyChart Video (Zoom for Healthcare embedded in MyChart): Tightly integrated with Epic scheduling and documentation; patient initiates video from MyChart app; provider joins from Epic; encounter documentation is in-Epic. Best choice for Epic shops — no separate platform needed.
• Oracle Health (Cerner) TeleHealth: Similar integrated model for Cerner environments

Standalone HIPAA-compliant video platforms:

• Zoom for Healthcare: HIPAA Business Associate Agreement (BAA) available; widely used; requires separate integration with EHR for scheduling and documentation
• Doxy.me: Simple, no-download browser-based; popular in small practices for its ease of use and no patient account requirement
• Teladoc Health Enterprise: Enterprise platform for large health systems; virtual care management capabilities
• Amwell Enterprise: Health system-focused; clinical workflow features
• Wheel: Clinician network + platform (if augmenting staff for surge capacity)

Selection criteria:

• EHR integration capability (bidirectional scheduling, auto-documentation, charge capture)
• Patient experience (download-free browser-based preferred; mobile app if target population is mobile-first)
• Provider experience (interface simplicity — if it takes more than 2 clicks to start a video visit, adoption suffers)
• Compliance (HIPAA BAA, SOC 2 Type II, state-specific telehealth regulations)
• Analytics and reporting
• Cost model (per-visit, per-provider-seat, or enterprise flat fee)

---

Phase 3: EHR Integration and Workflow Design (Months 3–10)

EHR integration is the second-highest risk element of telehealth implementation (after provider adoption). A telehealth platform that isn't integrated with the EHR creates parallel documentation, dual scheduling systems, and billing gaps.

Integration touchpoints:

Scheduling: Telehealth appointment types must be configured in the EHR scheduler with the correct:

• Visit type (new patient vs. established patient — different billing rules)
• Duration (video visits are often 30–50% shorter than in-person; schedule accordingly)
• Place of service code (02 = telehealth provided other than patient's home; 10 = patient's home — billing impact varies)
• Provider access to video link from EHR workspace

Patient communication workflow:

• Appointment reminder with telehealth link (not a generic reminder)
• Pre-visit technology check (verify patient has working camera, microphone, internet)
• Patient intake forms (can be completed in patient portal before visit)
• Consent for telehealth (must be documented — patient-specific consent required in most states)

Documentation templates:

• Telehealth-specific documentation: must include documentation that the visit was conducted via telehealth (required for Medicare and most commercial payer billing)
• Appropriate physical exam documentation: a telehealth visit cannot document a physical exam that was not performed — document what was assessed remotely
• Place of service on claim must match documented site of service

Billing workflow:

• Place of service code 02 (or 10 for home) on claim
• Modifier GT (via interactive audio and video telecommunications systems) — required by many payers
• Originating site requirements: Medicare has historically required the patient to be in a clinical facility (RHC, FQHC, hospital outpatient, physician office) — check current status of home originating site allowances
• Audio-only visits: covered by Medicare with different billing codes (CPT 99441-99443); lower reimbursement than video; some states restrict audio-only

---

Phase 4: State Medical Licensure and Regulatory Compliance (Months 1–12)

State licensure for telehealth is the regulatory element that most often surprises health systems expanding beyond their primary state. A physician providing telehealth must hold a medical license in the state where the patient is located at the time of the visit — not the state where the physician is located.

Interstate Medical Licensure Compact (IMLC):

• 40+ states now participate in the IMLC
• A physician licensed in one IMLC member state can apply for expedited licensure in other member states
• IMLC is not automatic — each additional state still requires a separate application and fee — but the process is significantly faster (4–8 weeks vs. 4–8 months for standard licensure)
• Physicians must hold a license of record (primary license) in one IMLC member state

States not in IMLC (as of 2026): California is the most significant non-participating state — large patient population with no compact pathway; standard CA licensure takes 4–8 months.

State telehealth practice standards:

Some states have specific telehealth practice laws:

• In-person exam requirement before telehealth prescribing (most states have relaxed this post-pandemic; verify current status)
• Informed consent for telehealth (must be documented in the patient record)
• Platform standards (some states specify platform requirements — e.g., must be synchronous video, not audio-only)

---

Phase 5: DEA Registration for Controlled Substance Prescribing via Telehealth (Months 3–9)

Ryan Haight Act: Federal law (21 CFR Part 1306) historically required an in-person evaluation before prescribing controlled substances (Schedule II–V) via telemedicine. During the COVID public health emergency, the DEA waived this requirement — but the long-term regulatory status is in flux as of 2026.

DEA Special Registration for Telemedicine:

The SUPPORT Act of 2018 required the DEA to create a special registration that would allow prescribing controlled substances via telemedicine without a prior in-person visit. As of 2026, the DEA has proposed regulations for this special registration — check current DEA guidance for implementation status.

DEA registration by state: Each DEA registrant (physician, NP, PA) must hold a DEA registration in the state where the prescription is written — for telemedicine, this is the state where the patient is located. A physician licensed in 10 states must have 10 DEA registrations to prescribe Schedule II-V drugs to patients in all 10 states.

Gantt impact: If the program includes psychiatric services with medication management (the highest-value behavioral health telehealth use case), DEA registration in all target patient states must be planned and tracked explicitly. DEA registration applications take 3–6 weeks; must be filed state-by-state.

---

Phase 6: Technology and IT Infrastructure (Months 3–8)

Provider equipment:

• Camera quality matters for clinical telehealth: 1080p minimum; 4K preferred for dermatology or wound assessment
• Lighting: good front lighting (ring light or window light) significantly improves patient perception of provider professionalism
• Background: neutral, professional background; virtual backgrounds require green screen for acceptable quality
• Headset: wired headset for audio quality; wireless introduces latency and dropout risk
• Internet: 10 Mbps dedicated upload for stable 1080p video; Wi-Fi is acceptable but wired Ethernet is more reliable for clinical use

Patient technology access — addressing the digital divide:

• Assess target patient population's technology access before launch (do not assume broadband and smartphone access)
• Low-income, elderly, and rural populations may lack access: plan for audio-only alternatives where clinically appropriate
• Patient-loaner tablet program for frequent telehealth users who lack home broadband
• Consideration: Federally Qualified Health Centers (FQHCs) and Rural Health Clinics (RHCs) can provide originating site services for Medicare patients without home broadband

IT security:

• HIPAA Security Rule: all video communications must be encrypted end-to-end
• Platform must sign a Business Associate Agreement (BAA) — this is non-negotiable; consumer video platforms (FaceTime, standard Zoom) are not HIPAA-covered without a BAA
• Data residency: verify patient video data is not stored on the platform without explicit consent (most clinical telehealth platforms do not record sessions; verify)
• Access control: providers must use multi-factor authentication to access telehealth platform and EHR

---

Phase 7: Provider Training and Adoption (Months 5–12)

Provider adoption is the most common reason telehealth programs fail to achieve their utilization targets. Physicians who find the technology burdensome simply don't use it — they schedule in-person visits instead.

Training components:

Technology training (30–60 minutes):

• Platform access and login
• Starting and joining a video visit
• Screen sharing (for patient education materials)
• Troubleshooting common patient technology issues

Clinical skills for telehealth (60–90 minutes):

• Virtual physical examination techniques (what can be assessed via video; what cannot)
• Patient communication on video (eye contact with camera, not screen; speaking pace)
• Managing technical difficulties during visit (when to convert to audio-only; when to reschedule)
• Documentation standards for telehealth visits
• Recognizing when an in-person visit is required

Billing training (30 minutes):

• Place of service codes
• Telehealth-specific modifiers
• Documentation requirements for billing compliance

Champion physician program:

Identify 3–5 early-adopter physicians in the first service line to launch. Give them extra support, monitor their first 20 visits closely, and use their experience to refine the workflow before broader rollout.

---

Phase 8: Patient Marketing and Communication (Months 5–12)

Patients will not use telehealth they don't know exists. Patient communication is an implementation requirement, not a marketing luxury.

Communication channels:

• Patient portal messaging to established patients (the most effective channel — directly reaches the target population)
• After-visit summary insertion (inform patients at checkout that their follow-up visit can be telehealth)
• Phone reminder messaging (for patient populations less likely to use portal)
• Website and patient education materials (technology requirements, how to join a video visit)
• Front desk scripting (staff who book appointments should offer telehealth option proactively)

Patient-facing technology readiness:

• Browser-based video visits (no app download required) dramatically improve patient completion rates
• Pre-visit technology check (automated test of camera and microphone before the visit day)
• Clear instructions for joining the visit sent 24 hours before appointment

---

Building Your Telehealth Program Gantt Chart at gantt-chart.io

Structure your telehealth program Gantt chart with these parallel tracks:

1. Strategic planning — service line selection, payer analysis, governance
2. Platform selection — RFP, evaluation, contracting, BAA execution
3. EHR integration — scheduling configuration, documentation templates, billing workflow
4. State licensure and regulatory — IMLC applications for target states, state telehealth compliance
5. DEA registrations — state-by-state tracking for controlled substance prescribing
6. IT infrastructure — provider equipment, security configuration, network assessment
7. Provider training — curriculum development, training delivery, champion program
8. Patient communication — materials development, portal messaging, front desk training
9. Billing compliance — coder training, place of service configuration, claim audit plan
10. Pilot launch — first service line, first providers, first patients
11. Scale — phased rollout to additional service lines and providers

Key milestones:

• Platform BAA executed
• EHR integration testing complete
• State licenses in place for target states
• DEA registrations confirmed
• Provider training complete for pilot service line
• First virtual visit completed
• First clean claim submitted and paid
• 90-day utilization review and optimization

---

Conclusion

Telehealth program launches succeed when they are planned as clinical operations projects, not technology installations. The platform matters far less than the workflow design, provider adoption strategy, and regulatory compliance framework.

A Gantt chart at gantt-chart.io that tracks EHR integration alongside state licensure, DEA registration alongside provider training, and patient communication alongside billing workflow — with a pilot milestone before broad rollout — gives your telehealth leadership team the structure to build a program that physicians actually use and patients actually benefit from.