---
title: "Telemedicine Regulations in the USA: What Founders Must Know Before Launching"
description: "See what to build for before you launch by knowing telemedicine regulations in the USA that trip up founders on licensure, prescribing, consent, privacy and pay."
entityName: "EnactOn Technologies Private Limited"
pageType: "Article"
url: "https://www.enacton.com/blog/telemedicine-regulations-usa/"
rawMdUrl: "https://www.enacton.com/blog/telemedicine-regulations-usa.md"
lastUpdated: "2026-11-19"
---

# Telemedicine Regulations in the USA: What Founders Must Know Before Launching

## Additional Documentation & Details

> **Quick answer:** Telemedicine regulations in the USA are a patchwork: federal law sets rules for controlled substances, privacy and Medicare payment, while each state controls licensure, consent, standards of care and corporate structure. The rule that matters most is that care is regulated where the patient is located, so every clinician needs authority in every state they treat. Two dates matter right now: DEA prescribing flexibilities end December 31, 2026, and Medicare telehealth flexibilities run through December 31, 2027.

You built the video visit, hired the clinicians and lined up your first patients. Then a lawyer asks, "Which states are you launching in, and who is licensed there?" and your launch date quietly turns into a question mark. Telemedicine regulations in the USA are not hard because any one rule is complicated. They are hard because there are fifty-plus versions of them, and your product has to respect all of them at once.

If you are a telehealth founder, a clinical co-founder or a CTO about to launch or scale, this guide gives you the map: who regulates what, how licensure works, what the latest prescribing rules mean, and how each rule changes the product you build. When you reach the build stage, our [mobile app development](https://www.enacton.com/technologies/mobile-app-development/) team can show you how these rules turn into screens, data fields and workflows. This is educational, not legal advice, so use it to ask better questions of your healthcare counsel.

You will get a federal-versus-state breakdown, a plain-English guide to licensure and the Interstate Medical Licensure Compact, the current state of DEA and Medicare rules, a rule-to-feature table for your product team, and a launch checklist.

## Who regulates telemedicine in the USA: federal law or state law?

Both. Federal law covers a few big areas, such as controlled substances, privacy and Medicare payment, and state law covers almost everything about who can practice and how. In practice, most of your day-to-day compliance work comes from telemedicine laws by state.

| Area | Who sets the rules | What it means for you |
| :---- | :---- | :---- |
| Physician and clinician licensure | States | License needed where the patient is located |
| Controlled-substance prescribing | Federal (DEA) plus states | In-person evaluation rules, with temporary flexibilities |
| Privacy and security | Federal (HIPAA) plus state privacy laws | BAAs, encryption, access controls, breach rules |
| Medicare payment | Federal (CMS and Congress) | Coverage depends on time-limited statutory flexibilities |
| Medicaid and private payers | States | Varies by state and plan |
| Informed consent | Mostly states | Written or verbal requirements vary |
| Corporate structure and advertising | States, plus the FTC for advertising | Ownership and marketing claims need review |

The principle that ties it together is patient location. As the Center for Connected Health Policy notes in its [Fall 2025 state telehealth review](https://www.cchpca.org/2025/10/2025_infographicfinal.pdf), states regulate care based on where the patient sits at the time of the visit. If a patient in Ohio sees your Texas-licensed doctor, Ohio's rules apply to that visit.

**Key takeaway:** Think of telemedicine regulations in the USA as a federal floor with a state-by-state ceiling. Your product has to know where the patient is.

## What are the telehealth licensure requirements, and how does the Interstate Medical Licensure Compact help?

Telehealth licensure requirements are simple to state and painful to meet: your clinician must hold a valid license in the state where the patient is located. The Interstate Medical Licensure Compact speeds this up by letting eligible physicians get several state licenses through one application.

The compact has grown quickly. The IMLCC reports [46 member jurisdictions and more than 220,000 licenses issued](https://ombc.ca.gov/activity/20260825_mat_9.pdf) as of August 2026, and the AMA notes that physicians use it to obtain [an average of three additional licenses](https://www.ama-assn.org/practice-management/digital-health/interstate-medical-licensure-numbers). That is a big shortcut, but it is not magic: each state still issues its own license, charges its own fee and keeps its own rules.

| Path | How it works | Watch out for |
| :---- | :---- | :---- |
| Individual state licenses | Apply separately to each state board | Slow and expensive at scale |
| Interstate Medical Licensure Compact | One application, qualification letter, then expedited state licenses | Physicians only; not every state participates; state fees still apply |
| Other compacts and pathways | Separate compacts exist for some professions, such as nursing | Rules and membership differ by profession |
| Telehealth-specific registrations | Some states offer limited licenses or registrations for out-of-state telehealth | Scope and conditions vary widely |

For founders, the lesson is to treat licensure as a supply-chain problem. Decide your launch states, check which of your clinicians are licensed there, and plan the compact applications early, because licensing timelines will shape your launch calendar more than your engineering sprints will.

**Key takeaway:** Licensure is the gating item for every state you launch in. Start with a short list of states and expand as your clinician network grows.

## What do telehealth prescribing laws say about controlled substances?

Telehealth prescribing laws for controlled substances are the most time-sensitive part of the landscape. Federal law generally requires an in-person evaluation before prescribing controlled substances over the internet, but DEA and HHS have extended temporary flexibilities that allow telemedicine prescribing, and those currently end on December 31, 2026.

Here is where things stand in November 2026. DEA-registered practitioners may prescribe Schedule II through V controlled substances by telemedicine without a prior in-person visit under the [fourth temporary extension](https://www.healthlawalliance.com/blog/dea-telemedicine-special-registration-where-the-rule-stands), which runs through December 31, 2026. DEA [sent its final special registration rule to OIRA on August 25, 2026](https://www.mcdermottlaw.com/insights/dea-appears-close-to-finalizing-telemedicine-special-registration/), and the text is not public, so what happens on January 1 is still unclear. Narrower final rules for buprenorphine treatment of opioid use disorder and for VA patients took effect on December 31, 2025.

| Situation | Current status | What to do |
| :---- | :---- | :---- |
| Non-controlled prescriptions | State law governs; no DEA rule applies | Follow state standards of care and patient-relationship rules |
| Controlled substances, Schedules II to V | Allowed without in-person visit through Dec 31, 2026 | Plan for both outcomes on January 1 |
| Buprenorphine for opioid use disorder | Separate final rule in effect | Confirm conditions with counsel |
| Special registration | Final rule under White House review | Watch for publication and design for new requirements |

If your model depends on controlled substances, build a configuration switch now. Make it possible to require an in-person or established-patient flag before a controlled prescription, so you can change behavior in a day when the rule changes instead of in a quarter.

**Key takeaway:** Do not build a business model that only works while a temporary DEA flexibility exists.

## What are the patient consent rules for telemedicine?

Most states require some form of telehealth informed consent, though the details differ. According to the CCHP review, [45 states, DC and Puerto Rico](https://www.cchpca.org/2025/10/2025_infographicfinal.pdf) include a consent requirement in statutes, administrative code or Medicaid policy, and some states require written consent while others accept verbal consent.

A good consent covers what telehealth is, its limits (it may not replace an in-person exam), privacy and technology risks, alternatives, and what happens in an emergency. Because the frequency requirements are often vague, many platforms collect consent at first visit and again whenever the terms change.

**Key takeaway:** Treat consent as versioned data: who agreed, to which text, when and from which state.

## How does HIPAA apply to a telemedicine platform?

If you create, receive, maintain or transmit patient information on behalf of healthcare providers, HIPAA applies to you, either as a covered entity or as a business associate. That means a signed business associate agreement with each provider customer, safeguards for the data and a plan for breach notification.

- **Privacy Rule:** limits how patient information is used and shared, and gives patients rights to access it.
- **Security Rule:** requires administrative, physical and technical safeguards such as access controls, audit logs, encryption and risk analysis.
- **Breach Notification Rule:** requires you to notify affected parties when unsecured information is compromised.
- **Vendors:** every video, messaging, hosting and analytics vendor that touches patient data needs a BAA or a documented reason it does not.
- **State layers:** some states add stricter privacy rules, and substance use disorder records carry their own federal protections.

Your HIPAA compliance checklist should live next to your architecture diagram, not in a folder nobody opens.

**Key takeaway:** HIPAA is mostly engineering discipline: minimum necessary access, encryption, logging and vendor control.

<style>
    .cta-container {
        position: relative;
        background: linear-gradient(180deg, #101525 0%, #0b0b43 100%);
        border-radius: 12px;
        padding: 48px 32px !important;
        max-width: 850px;
        width: 100%;
        margin: 40px auto !important;
        text-align: center;
        color: #ffffff;
        overflow: hidden;
        box-shadow: 0 10px 30px rgba(0, 0, 0, 0.2);
        box-sizing: border-box;
    }
    .cta-wave-bg {
        position: absolute;
        top: 0;
        left: 0;
        width: 100%;
        height: 100%;
        background-image: url('/images/preview.webp');
        background-size: cover;
        background-position: center;
        opacity: 0.14;
        mix-blend-mode: screen;
        pointer-events: none;
    }
    .cta-content {
        position: relative;
        z-index: 1;
    }
    .cta-container h2.cta-title {
        font-weight: 700 !important;
        font-size: 32px !important;
        margin: 0 0 12px 0 !important;
        letter-spacing: -0.5px !important;
        color: #ffffff !important;
        line-height: 1.25 !important;
        border: none !important;
        padding: 0 !important;
    }
    .cta-container p.cta-description {
        font-weight: 400 !important;
        font-size: 16px !important;
        line-height: 1.5 !important;
        max-width: 620px !important;
        margin: 0 auto 28px auto !important;
        color: rgba(255, 255, 255, 0.9) !important;
    }
    .cta-badge-container {
        display: flex;
        justify-content: center;
        gap: 16px;
        margin-bottom: 32px !important;
        flex-wrap: wrap;
    }
    .cta-badge {
        font-weight: 500 !important;
        font-size: 13px !important;
        padding: 6px 16px !important;
        border: 1px solid rgba(255, 255, 255, 0.3) !important;
        border-radius: 6px !important;
        color: #ffffff !important;
        background: transparent !important;
    }
    .cta-btn {
        display: inline-block !important;
        font-weight: 900 !important;
        font-size: 15px !important;
        color: #000000 !important;
        background-color: #ffffff !important;
        padding: 14px 32px !important;
        border-radius: 6px !important;
        text-decoration: none !important;
        transition: opacity 0.2s ease, transform 0.2s ease !important;
        border: none !important;
        line-height: 1 !important;
    }
    .cta-btn:hover {
        opacity: 0.9 !important;
        transform: translateY(-2px) !important;
        color: #000000 !important;
    }
    @media (max-width: 600px) {
        .cta-container { padding: 36px 20px !important; }
        .cta-container h2.cta-title { font-size: 24px !important; }
        .cta-container p.cta-description { font-size: 15px !important; }
        .cta-badge-container { flex-direction: column; align-items: center; gap: 10px; }
        .cta-badge { width: 100%; box-sizing: border-box; }
    }
</style>
<div class="cta-container">
    <div class="cta-wave-bg"></div>
    <div class="cta-content">
        <h2 class="cta-title">Turning Regulations Into a Product Plan?</h2>
        <p class="cta-description">
            EnactOn builds telehealth software with HIPAA-aware architecture, configurable workflows and human-reviewed AI acceleration, working alongside your healthcare counsel to turn rules into requirements.
        </p>
        <div class="cta-badge-container">
            <div class="cta-badge">HIPAA-Aware Architecture</div>
            <div class="cta-badge">Configurable Compliance Workflows</div>
            <div class="cta-badge">Human-Reviewed AI Acceleration</div>
        </div>
        <a href="/enquiry/" class="cta-btn">Scope Your Telehealth Build</a>
    </div>
</div>

## How do Medicare and Medicaid pay for telemedicine?

Medicare pays for most telehealth services today because Congress extended the pandemic-era flexibilities, but the extension is temporary. The Consolidated Appropriations Act, 2026 extended them through December 31, 2027, as summarized by [KFF](https://www.kff.org/medicare/what-to-know-about-medicare-coverage-of-telehealth/), and [NASW](https://www.socialworkers.org/Advocacy/Policy-Updates/ID/3340/Congress-Passes-Two-Year-Extension-of-Medicare-Telehealth-Flexibilities) notes it also delayed the in-person requirement for tele-mental health to the same date.

| Payer | Current picture | Founder takeaway |
| :---- | :---- | :---- |
| Medicare (fee-for-service) | Home and geographic flexibilities extended through Dec 31, 2027 | Do not build a model that assumes permanence |
| Medicare Advantage | Plans may include some telehealth costs in basic benefits, regardless of the temporary expansions | Check each plan's policy |
| Medicaid | Set by each state, with different modalities and rules | Map state by state before you launch |
| Private payers | State payment parity laws vary | Verify coverage and rates per payer and state |

If you rely on insurance, budget for policy risk: two flexibilities lapsed briefly in late 2025 during the government shutdown, and your billing logic should be able to adapt quickly. Cash-pay and employer-contract models avoid some of that exposure.

**Key takeaway:** Reimbursement is policy, not physics. Build billing rules that you can change without redeploying the product.

## What are the advertising and corporate-practice-of-medicine rules?

Advertising is governed by the FTC and state rules, and corporate-practice-of-medicine laws in many states limit who can own a medical practice. Together they shape how you can market, how you can structure your company and who controls clinical decisions.

- **Corporate practice of medicine (CPOM):** many states restrict non-physicians from employing physicians or directing clinical judgment. Common solutions pair a physician-owned practice with a management services organization that provides technology and operations.
- **Advertising claims:** health claims must be truthful and substantiated, and some states regulate how clinicians and practices can advertise.
- **Endorsements and incentives:** be careful with paid reviews, influencer promotion and anything that rewards prescribing.
- **Clinical independence:** your product should not let non-clinical staff override clinical decisions.

States such as California, New York and Texas are often cited for stricter CPOM approaches, but rules change, so get state-specific legal advice before you finalize your structure.

**Key takeaway:** Decide your legal structure before you decide your org chart or your marketing copy.

## How does each rule change what you build?

Every regulation maps to a feature, a data field or a workflow. If you turn the rules into product requirements early, compliance becomes a design input instead of a rewrite.

| Rule area | Product feature | Data or workflow |
| :---- | :---- | :---- |
| Patient-location rule | Location check at visit start, with state confirmation | Visit record with patient state and timestamp |
| Licensure | Clinician license matrix and automatic routing by state | License number, state, expiry, compact status |
| Controlled-substance rules | E-prescribing with controlled-substance support, PDMP checks, audio-video enforcement, configuration switch | Established-patient flag, prescription audit trail |
| Consent | State-aware consent flow with versioning | Consent text version, signature, method, date |
| HIPAA | Encryption, role-based access, audit logging, BAA tracking | Access logs, vendor register, breach workflow |
| Reimbursement | Billing codes, modifiers and place-of-service logic that can change | Payer rules table, claim audit trail |
| Advertising and CPOM | Marketing claim review workflow and clinician-controlled clinical settings | Approval records, role separation |

This is the angle most teams miss: regulation is not a separate project that happens after launch. It is a set of requirements that belong in your backlog next to features.

**Key takeaway:** Write each rule as a user story and put it in the sprint plan.

## What should founders do before launching a telehealth product?

Work through this checklist in order, and revisit it each time you add a state.

1. **Pick launch states.** Start with a short list based on your clinicians' licenses and payer mix.
2. **Confirm licensure.** Map each clinician to each state, and begin compact or state applications early.
3. **Decide your corporate structure.** Involve healthcare counsel about CPOM before you hire or market.
4. **Define your prescribing model.** Separate non-controlled from controlled, and plan for the DEA change.
5. **Draft consent flows.** Check state requirements and version for every consent.
6. **Run a HIPAA risk analysis.** Sign BAAs, and document your vendors and safeguards.
7. **Map payers.** Decide whether you are cash-pay, insurance-based or both, and model policy risk.
8. **Review marketing claims.** Have counsel approve claims and testimonial practices.

## So, To Conclude It All

Telemedicine regulations in the USA reward founders who treat them as design input. Care is regulated where the patient is, licensure is the gating item, controlled-substance rules and Medicare policy both carry dates that can change your model, and every rule has a product feature behind it.

Your next step is simple: list your first five launch states, check clinician licensure for each and mark the two dates that matter most, December 31, 2026 for DEA flexibilities and December 31, 2027 for Medicare. Then turn the rule-to-feature table into tickets. If you want a hand with the build, our [enterprise software development](https://www.enacton.com/industries/) page shows how we scope integration-heavy platforms.

EnactOn is a [Clutch Certified](https://clutch.co/profile/enacton-technologies) engineering partner with 500+ products delivered for 350+ clients across 65+ countries, and medical is one of the largest industries in our Clutch client mix. We build telehealth software with senior-led architecture, HIPAA-aware data handling and human-reviewed AI acceleration, and we work alongside your healthcare counsel rather than replacing them. For telemedicine regulations in the USA, we turn the rules into a build plan.

[Connect with our experts](https://www.enacton.com/enquiry/)

## FAQs

### What is the difference between federal and state telemedicine law?

Federal law covers controlled-substance prescribing (DEA), privacy and security (HIPAA) and Medicare payment, while states control licensure, standards of care, consent, Medicaid, corporate structure and most professional rules. Because care is regulated where the patient is located, the state rules often drive your daily operations. Plan for a federal floor and a state-by-state layer on top.

### How does physician licensure work across states, and what is the Interstate Medical Licensure Compact?

A clinician needs a license in the state where the patient is located. The Interstate Medical Licensure Compact lets eligible physicians apply once and receive expedited licenses from participating states, with 46 member jurisdictions as of August 2026. Each state still issues its own license and charges its own fee, and other professions use different pathways, so confirm the rules for each clinician type.

### What are the rules for prescribing controlled substances by telemedicine?

Federal law generally requires an in-person evaluation before prescribing controlled substances online, but DEA and HHS temporary flexibilities currently allow telemedicine prescribing of Schedule II through V drugs through December 31, 2026. DEA has a special registration final rule under White House review, and its details are not public. Build a configuration switch so you can adapt quickly after the deadline.

### What are the patient consent rules for telehealth?

Most states require some form of informed consent, with 45 states, DC and Puerto Rico including a requirement in law or Medicaid policy. Some require written consent and others accept verbal consent. Collect consent at first visit, store the exact text version, and refresh it when your terms change.

### How does HIPAA apply to a telemedicine company?

If you handle patient information on behalf of providers, you are likely a business associate and need BAAs, encryption, access controls, audit logs and a breach response plan. Vendors that touch patient data, such as video and hosting providers, need agreements too. Use a written HIPAA compliance checklist and run a risk analysis before launch.

### Will Medicare and Medicaid reimburse our telehealth visits?

Medicare telehealth flexibilities are extended through December 31, 2027, but they are temporary and Congress has to act again to continue them. Medicaid coverage is set by each state and varies by modality, and private payer rules differ by state. Verify coverage for every payer and state you plan to bill.

### How do advertising and corporate-practice-of-medicine rules affect us?

Many states restrict who can own a medical practice or direct clinical judgment, so telehealth companies often use a physician-owned practice with a management services organization. Advertising claims must be truthful and substantiated, and states and the FTC watch endorsements and incentives. Get state-specific legal advice before you set your structure and marketing.

### How does each regulation affect product features?

Each rule maps to a requirement. Patient location drives a location check, licensure drives a clinician license matrix and routing, prescribing rules drive e-prescribing and PDMP workflows, consent drives a versioned consent flow, and HIPAA drives encryption and audit logs. Write them as user stories so compliance is part of the backlog.

### Can we launch in all 50 states on day one?

You can, but it is rarely wise. Each state adds licensure, consent, payer and legal work, so most teams launch in a small set of states and expand. Choose launch states based on your clinician licenses, payer mix and legal readiness.

### What changed in telemedicine regulations in 2026?

The biggest changes are Medicare flexibilities extended through December 31, 2027, DEA flexibilities set to expire December 31, 2026 with a final special registration rule pending, and the Interstate Medical Licensure Compact growing to 46 jurisdictions. Policy has moved quickly, so check the latest status before you rely on any single date.

### How does EnactOn help telehealth founders build compliant products?

We start with discovery of your launch states, payer model and clinical workflows, then use our Target-Market Alignment work to cut 30 to 40 percent of non-essential scope before building. Senior architects write the specification, AI speeds up delivery under human review, and every release passes a four-gate pipeline for functional, security, performance and deployment checks. We work alongside your healthcare counsel and do not provide legal advice.

---
## Company Entity & Canonical Verification
- **Legal Business Name:** EnactOn Technologies Private Limited
- **Headquarters:** 605, Luxuria Business Hub, Nr. V R Mall, Vesu, Surat, Gujarat, INDIA – 395007
- **Official Website:** https://www.enacton.com
- **Direct Contact:** contact@enacton.com | +91 74260 60610
- **Career Enquiries:** careers@enacton.com | (+91) 90790 45453
- **Primary Service Category:** Custom Software Development, Startup MVP Engineering, White-Label Platform Development & IT Consulting
