Skip to content
TDIA
Menu

Practice change

The patient's location changes the care you can give.

A multistate program is not a national platform launch. It is a set of local clinical pathways that the practice must be able to operate safely.

A road forks between a hospital campus and an independent practice

Imagine a current California patient logging in from a hotel in a neighboring state. They want a refill. Mid-visit, they mention chest pressure and the connection fails. Before the appointment began, the practice needed to know whether it could care for the patient at that location, what the remote assessment could establish, who could prescribe, where the patient could go next, and who would own the work after the call.

That is the launch problem. Telehealth describes a mode of care. Multistate work describes where the patient is when care happens. A state-by-state expansion succeeds when the practice builds a reliable local pathway for both.

Verify the patient's present location at every encounter

Before a nonemergent visit, verify the patient's identity, physical location, callback number, service requested, and the clinician's authority under that state's current law. A full license, compact privilege, temporary-practice route, reciprocity, or telehealth registration are different pathways with different conditions. Do not reduce them to a single "telehealth license" field.

For a patient located in California, the Medical Board says the treating physician needs a current California license. California law defines the originating site as the patient's location at the time of service. It also requires the initiating provider to tell the patient about telehealth, obtain verbal or written consent, and document that consent before care. Telehealth does not lower the standard of care or change ordinary scope, privacy, record, or professional-responsibility duties.

Patient travel changes the analysis. If a location check shows that the practice lacks authority for nonemergent care, do not proceed with that care until the question is resolved. If urgent symptoms emerge, shift to emergency direction and local services, document the handoff, and do not mistake a licensing problem for permission to abandon a patient.

Build a local pathway, not a national service menu

Use a service-by-state matrix. For each patient state and service, identify the clinician's legal route and effective dates, the treating entity, patient population, prescribing and controlled-substance authority, local laboratory and pharmacy options, in-person referral or emergency path, authoritative clinical record, and coverage review.

The matrix should answer a physician's real question: "Can I safely deliver this service to this patient here today?" A state may permit one clinician and service combination but not another. A compact may help with physician authority while leaving payer, pharmacy, controlled-substance, entity, and emergency-workflow questions unresolved.

Use remote care only when it is clinically sufficient

Do not define remote suitability by appointment label. For each program, determine what history, examination, data, and follow-up the clinical question requires; what remote care cannot establish; what red flags stop the visit; and where the patient receives in-person care.

California's dangerous-drug rule gives this decision real weight. Prescribing, dispensing, or furnishing a dangerous drug without an appropriate prior examination and medical indication is unprofessional conduct. The examination may use telehealth, including an asynchronous questionnaire, only when that method meets the standard of care for the patient and decision at hand. Video is not always required, and a questionnaire is not automatically enough.

For each clinical pathway, name the clinician who can decide that remote care is sufficient, the local referral or emergency option, the patient instructions, and the owner of any pending work. A national protocol becomes useful only when it has a workable local destination.

Consent is more than a platform click. Capture the required telehealth consent, clinical context, remote findings, assessment, rationale, orders, patient instructions, and follow-up plan in an authoritative clinical record. The practice may use several systems, but it needs a reliable way to reconcile information from intake, video, portal messages, remote devices, laboratory and imaging orders, and local partners.

Set a policy for summaries, scores, transcriptions, and draft notes. Identify their source and version, who validates them, when a clinician relies on them, how errors are corrected, and how clinically important information reaches the record. Technology can support the encounter; it cannot own the clinical decision.

Prescribing does not begin at checkout

For each drug program, map the assessment and indication, patient state, prescriber authority, pharmacy or fulfillment partner, monitoring, refill criteria, adverse-effect response, and after-hours coverage. Compounded products, mailed medication, local administration partners, and multi-entity marketing or fulfillment models each add facts that the clinical pathway must make visible.

Controlled substances need a separate, dated pathway. The DEA's temporary federal telemedicine flexibilities currently run through December 31, 2026. They permit certain DEA-registered practitioners to prescribe Schedule II-V controlled medications through audio-video telemedicine without a prior in-person evaluation, subject to the temporary rule and other federal and state requirements. FDA-approved Schedule III-V narcotic medications for opioid-use-disorder treatment have a limited audio-only pathway. This is not permanent law, and it does not replace state authority, clinical judgment, or recordkeeping.

Let results and disconnections create visible work

A laboratory order, image, patient photograph, device reading, portal message, or local-partner report is not closed merely because it was technically received. Define who reviews it, interprets it, contacts the patient or covering clinician when needed, escalates failed outreach, and documents closure. Name a backup before the primary clinician leaves or the service changes hands.

Use the same discipline for a lost connection. For any service with plausible urgent deterioration, determine when staff reconnect, when they call the patient, when they call local emergency services, what address and information are available, and who remains responsible until the handoff is clear. HHS's more detailed plan for telebehavioral health includes current location, local emergency resources, a nearby support contact, other care-team members, and the disconnected-visit response. Tailor that model to the actual risk; do not paste it blindly into every low-risk service.

Make vendors support continuity, not obscure it

Map the full data flow: intake, video, messaging, transcription, remote monitoring, portal, e-prescribing, payment, laboratory, pharmacy, analytics, and the clinical record. For each vendor, identify its purpose, access, retention, outage fallback, record-return and termination process, and the person who reconciles clinically important information.

Where HIPAA applies, the Security Rule requires appropriate safeguards for electronic protected health information handled by covered entities and business associates. Classify each vendor under the actual relationship rather than assuming every vendor needs the same contract. A business associate agreement alone does not establish a secure, usable, or continuous clinical workflow.

Let coverage validate the launch, not authorize it

Clinical and legal authority come first. Coverage is a separate question answered by the issued policy and relevant contracts. Before a state or service launch, compare the real operation with the application, declarations, definitions, endorsements, exclusions, named insureds and professionals, territory, services, limits, defense provisions, retroactive dates, notice terms, and partner assumptions.

Before a material state or service launch, give the broker or carrier the actual facts: patient states, clinician roles and authority, entity names, services, prescribing and controlled-substance work, vendors and local partners, emergency plan, and effective dates. Ask whether the issued terms require notice, endorsement, or another application. Do not launch clinical care until the authority, entity and service pathway, patient-location plan, and applicable contract requirements are resolved; the issued policy and endorsements control coverage.

The final launch test is concrete. If a traveling patient needs medication, disconnects during symptoms, and has an abnormal result tomorrow, can the team identify the authority to act, local care path, clinical recipient, record, contract, and policy route to review? If not, the state is not ready.

Sources