State Index

Controlled substances, state by state.

A repeatable framework for evaluating telehealth controlled substance workflows across jurisdictions — and the platform that holds them together.

ComplianceHIPAA + BAA
i. States in the registry

Workflow guides, state by state.

·

Arizona

Arizona workflow guide — licensure, prescribing rules, documentation.

·

California

California workflow guide — licensure, prescribing rules, documentation.

·

Colorado

Colorado workflow guide — licensure, prescribing rules, documentation.

·

Florida

Florida workflow guide — licensure, prescribing rules, documentation.

·

Georgia

Georgia workflow guide — licensure, prescribing rules, documentation.

·

Illinois

Illinois workflow guide — licensure, prescribing rules, documentation.

·

Indiana

Indiana workflow guide — licensure, prescribing rules, documentation.

·

Massachusetts

Massachusetts workflow guide — licensure, prescribing rules, documentation.

·

Michigan

Michigan workflow guide — licensure, prescribing rules, documentation.

·

Missouri

Missouri workflow guide — licensure, prescribing rules, documentation.

·

New York

New York workflow guide — licensure, prescribing rules, documentation.

·

North Carolina

North Carolina workflow guide — licensure, prescribing rules, documentation.

·

Ohio

Ohio workflow guide — licensure, prescribing rules, documentation.

·

Pennsylvania

Pennsylvania workflow guide — licensure, prescribing rules, documentation.

·

Tennessee

Tennessee workflow guide — licensure, prescribing rules, documentation.

·

Texas

Texas workflow guide — licensure, prescribing rules, documentation.

·

Virginia

Virginia workflow guide — licensure, prescribing rules, documentation.

·

Washington

Washington workflow guide — licensure, prescribing rules, documentation.

ii. Federal context

Read the federal layer first.

State workflows sit on top of federal rules. Before evaluating any single state, operators should be current on the federal layer: DEA telehealth controlled substances and Ryan Haight Act and telehealth.

iii. FAQ

Multi-state, plainly answered.

Why do telehealth controlled substance rules vary by state?
Because federal telemedicine rules are only one layer. States can impose their own licensure requirements, prescribing conditions, documentation expectations, and follow-up rules. Multi-state operators need workflows that can adapt without losing control.
Can a telehealth company use one controlled substance workflow in every state?
Usually not. Operators can standardize a core workflow, but they should expect state-specific differences in clinician eligibility, patient evaluation expectations, prescribing boundaries, and documentation requirements. The platform should support configurable per-state routing.
How should teams evaluate telehealth controlled substances by state without scattering rules across spreadsheets?
Start with a repeatable decision framework: confirm state licensure, review federal overlap, define intake and documentation requirements, map provider review steps, and decide how exceptions surface operationally. The goal is governed workflow, not rules scattered across spreadsheets.
How do state-specific rules interact with DEA and Ryan Haight questions?
DEA and Ryan Haight shape the federal layer, but states still matter. Even when a federal pathway looks workable, operators need to confirm whether a given state imposes extra conditions around licensure, evaluation, prescribing, or follow-up.
Is this page legal advice?
No. This page is an operational planning guide for telehealth teams. Organizations should work with qualified healthcare counsel and compliance professionals for legal interpretation and state-specific review.
vi. Begin

Multi-state workflows that hold.

One platform. State-aware routing. Audit trail across all jurisdictions.

Live in hoursReply within 24 hours