Telehealth expansion is the work of taking a virtual care program beyond its first clinic, state or service line. For most providers in late 2026, that growth happens inside a federal policy window with two fixed end dates, which shapes what is safe to build and what needs a fallback.
This guide explains that window, then walks through the four directions a program can expand: new states, new services, new payers and new modalities. It closes with a go or no-go list for each expansion decision.
What does telehealth expansion look like through 2027?
Planning to expand a telehealth program?
Agnotic builds and extends telemedicine platforms for new states, service lines, payers and care models.
Telehealth expansion through 2027 means growing a virtual care program while Medicare home telehealth is guaranteed only to the end of 2027 and controlled-substance tele-prescribing flexibilities only to the end of 2026. Providers can add states, services and payers now, but each addition needs a defined fallback for those two dates.
The window is a planning fact, not a reason to wait. Programs that expand with dated rules and tested fallbacks can keep growing whatever Congress and the DEA decide next. Programs that hard-code today's flexibilities into workflows face an expensive rewrite if a deadline passes.
Which federal rules set the expansion window?
Two federal rules set the window. Congress used the Consolidated Appropriations Act, 2026 to keep Medicare's home and non-rural telehealth flexibilities in force until 31 December 2027. For controlled substances, the DEA and HHS fourth temporary rule lets prescribers skip the prior in-person evaluation until 31 December 2026.
Claim coding sits inside that window too. Medicare telehealth claims for a patient at home use place of service 10, and other locations use 02, with modifier 95 for audio and video and 93 for audio-only. Those codes are stable inputs for expansion planning, while coverage of the visit itself depends on the dates above.
Everything else varies by state and payer. Each state Medicaid program and each commercial plan writes its own telehealth coverage policy, and state boards own licensure and prescribing. Expansion planning starts by listing which of these rules applies to each new market.
Keep that list as a living document owned by compliance, with a link to the source for every rule and a review date. When a rule changes, the list shows which services and markets are affected and which configuration values need updating.
Expanding into new states
Adding a state is mainly a licensure and operations project. Clinicians need authority to practice where the patient is located, through a full license, a compact privilege or a state telehealth registration, and the platform has to route patients only to clinicians who hold it.
- Credentialing: Add each clinician's authority for the new state to the credentialing table, with expiry dates and an owner.
- Routing: Extend location capture and routing rules so patients in the new state see only authorized clinicians.
- Consent text: Load the state's telehealth consent wording and any recording rules into the consent module.
- Prescribing limits: Add the state's controlled-substance and telehealth prescribing rules as configuration, since they can be stricter than federal ones.
- Medicaid rules: Load the state Medicaid program's telehealth coverage, modality and coding rules if the program will serve Medicaid patients.
Launch a new state with a small group of clinicians and a limited set of visit types. Watch routing errors, consent completion and claim denials for a few weeks before opening every service there.
Time zones and hours need attention as well. A program that adds a state two time zones away has to decide whether clinicians cover its evenings, how reminders are timed, and which local emergency numbers and crisis resources appear in the app for patients located there.
How should a program add new services or specialties?
A program should add a service only after defining which visits in it work virtually, what data the clinician needs before the visit, and how the patient gets to an in-person exam when needed. The video room is the same; the visit types, intake and follow-up are not.
Each new service brings its own intake. Dermatology needs photo upload with guidance on lighting. Behavioral health needs screening questionnaires and safety planning. Chronic disease follow-up needs home readings on screen. Build these as visit type configurations, not as separate apps.
Integration grows with each service. New visit types need matching appointment types in the EHR, the right note templates, order sets and result routing. Plan the EHR build with the service line's clinical lead before opening the schedule, or the first visits will be documented outside the chart.
Specialty services also raise the clinical-limit question more sharply. Write the list of symptoms that disqualify a visit from video for each new service, and put it in the booking flow so patients are redirected before a slot is wasted.
What changes when adding payers beyond Medicare?
Adding payers means adding coverage and coding rules per plan. Commercial plans and Medicaid programs decide which services they cover by telehealth, whether audio-only counts, which place of service and modifiers they expect, and whether the patient pays the same as in person.
- Eligibility: Check coverage and telehealth benefits before the visit, so patients are not surprised by a bill.
- Coding rules: Hold place of service and modifier rules per payer, derived from visit data rather than chosen by clinicians.
- Contracted rates: Confirm whether the contract pays telehealth at the in-person rate or a different one.
- Network status: Make sure the clinician is credentialed with the plan in the patient's state, not only licensed there.
- Denial tracking: Report denials by payer and reason for the first months, and fix rules before scaling volume.
Payer rules change on their own schedules, often at the start of a plan year. Store each rule with an effective date and a source document, so the revenue cycle team can update it without an engineering release.
Should expansion include asynchronous and remote care?
Expansion should include asynchronous and remote care where payers cover it and clinicians can staff it, because these models reach patients who cannot attend a live visit. They also carry different rules from video visits, so they need their own workflows.
Asynchronous care covers e-visits through the portal, store-and-forward images and interprofessional consults. Remote monitoring covers device readings reviewed between visits. Each has its own consent, documentation and time-tracking needs, and each should be designed as a separate service with its own owner.
Staffing is the usual constraint. Asynchronous queues grow quietly, and a message that waits days is worse than no service at all. Set a response target, staff the queue for it, and show the patient when to expect a reply.
Remote care also changes the data load. Device readings, photos and questionnaires arrive between visits, and each needs a home in the EHR as discrete data or a filed document, plus a rule for who reviews it and how fast. Decide that before enrolling the first patient, not after the queue fills.
How do you plan around the two deadlines?
Plan around the deadlines by writing down, for each service, what happens if the rule lapses on its end date, and building that fallback before you need it. The plan should name the services affected, the patients who would need a different route and the date the fallback would switch on.
- End of 2026, prescribing: Flag patients receiving controlled substances who have never had an in-person evaluation, and plan in-person or qualifying visits for them if no extension follows.
- End of 2027, Medicare home visits: Identify Medicare visit types that rely on the home and non-rural flexibilities, and model the in-person or clinic-site alternative.
- Dated configuration: Hold each rule with start and end dates, and switch behavior automatically on the date.
- Clock tests: Run the platform in a test environment with the date moved past each deadline and check scheduling, prescribing and claims.
- Communication: Draft patient and clinician notices in advance, so changes can be announced the day a decision is made.
An expansion go or no-go list
Use this list for each proposed expansion, whether a new state, service, payer or modality. A no on any line means the launch waits until it is fixed.
- Authority: Every clinician in the launch group holds active authority in the target state.
- Routing: Location capture and routing are tested for the new market.
- Consent: State and service consent text is loaded and reviewed by counsel.
- Visit types: Each new visit type has disqualifying symptoms, required pre-visit data and an in-person path.
- EHR build: Appointment types, note templates and result routing exist in the EHR.
- Payer rules: Coverage, coding and rates are confirmed for every payer in scope.
- Deadline fallback: The service has a written and tested fallback for the end-2026 and end-2027 dates where they apply.
- Staffing: Live and asynchronous queues have staff and response targets.
- Measures: Join rates, completion rates, denials and in-person conversion are reported from day one.
How Agnotic can help
Expanding a telehealth program is mostly configuration, integration and testing on a platform designed to change. Agnotic Technologies builds and extends telemedicine platforms so new states, visit types and payers are added as rules with effective dates, and so the end-2026 and end-2027 deadlines can be tested before they arrive.
The client's clinical, legal and revenue cycle leaders decide where and how to grow. Agnotic delivers the routing, consent, EHR integration and claim logic that each decision needs, with tests for every market.
Expand your telehealth program with fewer surprises
See how Agnotic extends telemedicine platforms for new markets, or browse the telehealth hub.
Related reading on Agnotic
Continue with the pandemic telemedicine record, the long-range outlook, federal requirements, Florida law and telehealth risks.
