Licensure is usually filed under "legal" and then discovered, late, to be a product problem. It decides which clinician your matching engine may offer a given patient, what happens when a patient books from an airport in a different state, and whether your growth plan is "launch nationally" or "launch in five states and staff the sixth deliberately."
This page is the structural version — what the rules govern, what the compacts do and do not do, and the seven things your software has to model. It is not legal advice and the specifics change frequently. Retain counsel licensed in the states you intend to operate in; this page exists to make that conversation shorter and cheaper.
The rule that generates every other rule
The general principle across US telehealth is that care is treated as occurring where the patient is physically located at the time of the encounter, so the clinician generally needs authority to practice in that state. State medical, nursing and behavioral health boards set the requirements; there is no federal telehealth licence.
Everything else — compacts, exceptions, registration pathways — varies that principle. So the first product consequence is blunt: your system has to know where the patient is at the moment of the visit, and record how it knew. Not the billing address. Not the signup address. The location at the time of the encounter.
What the compacts actually do (and the distinction teams get wrong)
Compacts are agreements among member states that create a faster route to practice across state lines. The critical thing product teams misunderstand is that they do not all work the same way.
| Compact | Profession | Mechanism |
|---|---|---|
| Interstate Medical Licensure Compact (IMLC) | Physicians | An expedited pathway to obtaining full licences in member states — you still end up holding multiple licences |
| Nurse Licensure Compact (NLC) | RNs / LPNs | A multi-state privilege to practice in other member states from one home-state licence |
| PSYPACT | Psychologists | Authority to practice telepsychology across participating states |
| PT Compact | Physical therapists / assistants | Compact privilege in member states |
| Counseling Compact | Licensed professional counselors | Privilege to practice across member states |
| Social Work Licensure Compact | Social workers | Privilege to practice across member states |
| ASLP-IC | Audiologists / SLPs | Privilege to practice across member states |
That IMLC-versus-NLC distinction is worth an engineering meeting. For physicians, the compact does not produce one licence covering member states — it accelerates getting several, each with its own number, renewal date and status, so your data model needs a row per licence. For nurses, the multi-state privilege model is keyed to home state plus privilege status instead. Build one generic "provider licences" table that represents both, or you will rebuild it the first time you add a second profession.
The exceptions that create false confidence
Most states carve out narrow situations — consultation with an in-state provider, continuity of care for an established patient temporarily out of state, emergencies, and in some cases a telehealth registration narrower than full licensure. These vary substantially by state, and they are exactly the kind of thing that gets summarized into a product requirement as "we're covered for follow-ups" when the actual exception is far narrower.
Treat every exception as a per-state configuration value your legal counsel sets, not a rule your engineers infer from an article. Software should implement a policy table someone else owns.
Controlled substances are a separate regime
If your product involves prescribing controlled substances — which now includes much of behavioral health, ADHD and weight management — federal rules on telemedicine prescribing sit on top of state licensure and are their own analysis, governed by a sequence of temporary flexibilities and proposed rulemaking whose dates have changed repeatedly.
Product consequence: prescribing capability must be gated independently of visit capability. A clinician who can lawfully conduct the visit may not be able to prescribe a given schedule of drug in that state under that modality. One boolean is not enough.
Two more constraints that shape the build
Modality rules. States differ on whether audio-only counts as a telehealth encounter for a given service, on telehealth-specific informed-consent requirements, and on whether an in-person visit is required before certain care. Your visit record needs a modality field, and your consent flow needs to be per-state configurable — the consent language a state requires is a state-level string, not a global one.
Corporate practice of medicine. Many states restrict who may own an entity that practices medicine, which is why so many telehealth companies operate through a professional corporation with a management services agreement to the technology company. It has product consequences — which entity employs the clinician, which holds the patient relationship, how billing flows — so it is a question for counsel to answer before you build billing.
The seven things your software must model
This is the transferable part.
- Provider licences as first-class records — state, licence type, number, status, issue and expiry dates, plus compact privileges represented alongside licences rather than instead of them.
- Patient location at time of encounter — captured, attested, and stored with the encounter. Patients travel, and the state they booked from is not necessarily the state they will be sitting in.
- A matching engine that filters on state at booking and re-checks at visit start. The re-check is the part everyone skips and it is the one that catches the airport case.
- A graceful out-of-state flow. When the re-check fails, the patient needs a real path — reschedule, reassign to a licensed clinician, or a clear explanation. Not an error screen. This is a UX problem with a compliance trigger.
- Licence verification and expiry monitoring. Primary source verification at onboarding and a recurring re-check, with automatic suspension of matching when a licence lapses. A clinician quietly practicing on an expired licence is a systems failure, not a personal one.
- An audit trail linking each encounter to the specific licence or privilege that authorized it. If you are ever asked to demonstrate that care was delivered lawfully, this record is the answer. Design it in; it cannot be reconstructed later.
- A prescribing gate evaluated separately from the visit gate, per state, per drug schedule, per modality.
Get those seven right and adding a state becomes a configuration change plus a recruiting problem. Get them wrong and every new state is a code change.
The unprofitable advice
Do not launch in fifty states. Launch in three to five, chosen for clinician supply and demand density, and make the state list a configuration value from day one. National coverage sounds like a growth strategy and is usually a licensing, recruiting and support cost you have taken on before you have proven the core product.
The second piece: model licensure before you build matching, not after. Retrofitting state eligibility into a booking system that already assumes any clinician can see any patient is one of the more expensive rewrites in health tech, because it touches scheduling, availability, notifications, billing and reporting simultaneously.
Our $1,999 Healthtech & Mental Health MVP Blueprint surfaces exactly these decision points in seven days — intended-use boundary, sensitive-data inventory, clinical dependency map and the decisions that need a lawyer rather than an engineer. Full prices are on the pricing page; an MVP build starts at $12,000.
To be explicit about the boundary: Zee Palm builds HIPAA-aware, compliance-conscious systems and maps clinical and regulatory decision points during planning. We do not provide legal advice, issue certifications, or determine your licensure obligations. See the trust page for our security and BAA position, and HIPAA-aware development for how we handle PHI.
If you are building a telehealth or remote-care product — or a mental health product, where the compact landscape is moving fastest — tell us which states you plan to operate in and we will tell you what that implies for the build.
Frequently asked questions
Do telehealth providers need a license in every state where they see patients?
As a general rule, yes — care is typically treated as occurring where the patient is physically located during the encounter, so the clinician needs authority to practice in that state. Compacts, narrow state exceptions and specific telehealth registration pathways modify this. Confirm the current position for each state you intend to operate in with counsel, because the details change and vary by profession.
Does the Interstate Medical Licensure Compact give doctors one multi-state license?
No, and this is the most common misunderstanding. The IMLC is an expedited pathway to obtaining full licenses in member states — a physician still ends up holding a separate license per state, each with its own number and renewal. The Nurse Licensure Compact works differently, granting a multi-state privilege from a home-state license. Your provider data model needs to represent both patterns.
What happens if a patient joins a telehealth visit from a different state?
That is the case your product has to handle deliberately. Best practice is to capture and attest patient location at the start of the encounter, re-check clinician eligibility at that moment rather than relying on the booking-time check, and offer a real path — reassign or reschedule — rather than an error. Record what location was captured and how.
Are the rules different for mental health telehealth?
The structure is the same but the compacts differ by profession — PSYPACT for psychologists, the Counseling Compact for licensed professional counselors, the Social Work Licensure Compact for social workers — each with its own member states and status. Prescribing adds a separate federal layer for controlled substances, which is particularly relevant in behavioral health.
Should we build state licensure logic into version one?
Model it in version one even if you launch in one state. Making the state list a configuration value and giving encounters a location and an authorizing-license reference costs very little at the start. Retrofitting eligibility into an existing booking system touches scheduling, availability, billing and reporting at once, and is one of the more expensive rewrites in health tech.