By Sagar Shankaran, Founder of CallSphere
An AI receptionist that books patients across state lines hits two regulators at once: HIPAA at the federal level and the state medical or therapy board where the patient sits. Here is the 2026 rulebook.
Key takeaways
A federally compliant AI receptionist booking a California patient with a clinician licensed only in Texas is a HIPAA non-issue and a California Medical Board problem. The 2026 stack must handle both.
flowchart LR
Voice[Voice call] --> Redact[PII / PHI redaction]
Redact --> LLM[LLM with BAA]
LLM --> Resp[Response]
Resp --> Sanitize[Remove non-needed PHI]
Sanitize --> Caller[Caller]
Resp --> AuditDB[(Audit DB)]HIPAA at 45 CFR 160.203 establishes federal preemption only when state law is contrary to and less stringent than the Privacy Rule. State laws that are more protective of the patient — and most state telehealth licensing laws are — survive untouched. State medical, dental, nursing, psychology, and behavioral health boards each define telehealth as the practice of medicine occurring at the location of the patient at the time of the encounter. That means a clinician must be licensed in the state where the patient is physically located when the visit happens — not where the clinic is incorporated.
In 2025 and into 2026, states have layered new mechanisms onto this baseline. The Interstate Medical Licensure Compact (IMLC), the Psychology Interjurisdictional Compact (PSYPACT), the Counseling Compact, and the Audiology and Speech-Language Pathology Compact all shorten the path to multi-state practice. Colorado (Senate Bill 24-168), California (Senate Bill 1192), and a growing list of states have enacted out-of-state telehealth registration regimes that allow non-licensed providers to deliver telehealth under specific conditions and registration.
The Drug Enforcement Administration (DEA) Special Registration for Telemedicine, repeatedly delayed through 2025 and 2026, also intersects whenever a controlled substance prescription is in play.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for healthcare in your browser — 60 seconds, no signup.
An AI receptionist is not practicing medicine — but it is the gatekeeper that decides which clinician sees which patient. If the agent books a Texas-licensed therapist with a patient on a Colorado phone number, it has just helped create the conditions for a Colorado Mental Health Board complaint. The compliance burden falls on the practice, not on the AI vendor, but the vendor's design directly determines whether the practice can defend itself.
The minimum viable design is patient-state detection at intake (phone area code is a first signal but not authoritative — ANI manipulation and forwarding break it), clinician-licensure mapping in a structured table, real-time match logic before the booking is offered, and a written record of which licensure check fired and why. For multi-state groups, the agent must also surface state-specific Notices of Privacy Practices and consent flows — California's CMIA, New York's SHIELD Act, Texas HB 300, and Washington's My Health My Data Act each impose disclosures that go beyond HIPAA.
CallSphere's Healthcare Voice Agent does state-aware routing as a first-class feature. The intake flow asks for patient ZIP code or address, validates the state, and consults a clinician licensure table inside our healthcare_voice PostgreSQL database. Each clinician row carries an array of state licenses, compact memberships (IMLC, PSYPACT, Counseling Compact), and DEA telemedicine status. Before any appointment is offered, the agent runs a license-state match. Mismatches are routed to a human or to the next licensed clinician — never silently booked. Across 50+ businesses on the platform, this logic has prevented hundreds of non-licensed bookings. Our behavioral-health LP at /lp/behavioral-health ships with PSYPACT logic on by default. State-specific notices and consent capture are part of the post-call analytics record alongside sentiment (–1.0 to +1.0), lead score (0–100), and the AI summary. Multi-state groups should review /industries/healthcare and /industries/behavioral-health, and start with a 7-day free pilot.
Does HIPAA preempt state telehealth licensing? No. HIPAA preempts only state laws that are less stringent than the Privacy Rule. State licensing laws are about the practice of medicine, not privacy, so they sit alongside HIPAA — not under it.
Still reading? Stop comparing — try CallSphere live.
See the healthcare AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
Is the patient's location or the clinician's location what counts? The patient's physical location at the time of the encounter. Every state medical board has confirmed this since the 2020 emergency declarations expired.
What about PSYPACT and IMLC? Compacts shortcut multi-state licensure for participating clinicians. The agent must check membership and active status, not just registration.
Does the AI vendor need state licenses too? No. The AI is not practicing medicine. But the vendor's product must give the practice the tools to comply.
What about the DEA Special Registration for Telemedicine? Delayed multiple times through 2026. Until it lands, controlled-substance prescribing across state lines uses the in-person and Ryan Haight Act exceptions.

Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
HIPAA-aware AI customer support uses privacy-conscious design, minimal data handling, and human routing for clinical cases. A 2026 guide for providers.
How clinics in Escazú, San José, and Liberia can capture US and Canadian medical-tourism inquiries around the clock with CallSphere's HIPAA-capable AI voice and chat agents — across time zones and languages.
American medical clinics miss a huge share of inbound calls at the front desk. See how CallSphere HIPAA-capable AI voice and chat agents book patients 24/7 without adding staff.
Using GPT-Realtime-2 for healthcare voice agents. BAA scope, PHI handling, retention, logging, and why a managed platform usually wins this build.
AI receptionist TCO can swing 10x by pricing model. Most SMBs pay $199-$299/month for full-featured, and a 24-month all-in TCO lands at $4.7K-$7.2K — vs $100K+ for a human seat. Here is the line-by-line model.
AWS HealthScribe became the open scribe layer EHR vendors built on top of in 2026. Here's the API surface, the per-encounter pricing, the BAA terms.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco