Arizona telehealth launch guide · 2026
Start here
To launch a telehealth service in Arizona, start with professional authority and the care model. Arizona §36-3602 generally requires verbal or written informed consent before telehealth, subject to its exceptions. Electronic consent is included. The statute addresses confidentiality and continued application of prescribing and licensing rules. A telehealth encounter therefore needs more than a general website agreement: the clinical team must establish that the proposed method meets the applicable professional requirements.
This guide covers patients in Arizona. Ownership, professional authority, prescribing, and payment depend on the service and care model.
Published by Bask Health · Editorial process
Updated
Your launch, mapped out
Arizona
Document consent before the remote encounter
The essentials
Start with the decisions that shape your legal structure and clinical workflow.
| Launch decision | Arizona |
|---|---|
| State requirement | Arizona generally requires informed telehealth consent, including verbal, written, or electronic consent. |
| Regulators | Arizona Medical Board; Arizona Board of Osteopathic Examiners in Medicine and Surgery |
| Professional ownership | Review the medical entity, permitted owners, clinical control, and management fees with state healthcare counsel. |
| Clinician authority | Check the issued license or applicable state pathway for each profession and service. |
| Patient location | Confirm where the patient is physically located at each encounter, including follow-up. |
| Care format | Have the clinical team match video, telephone, or asynchronous assessment to the patient and applicable rules. |
| Prescriptions | Review the clinician, medication, examination, monitoring, and pharmacy together. |
| Pharmacy fulfillment | Check the actual dispensing location and its authority to serve patients in the state. |
| Patient information | Map clinical and nonclinical data, vendor access, consent, and applicable privacy duties. |
| Payment model | Separate direct-payment terms from payer coverage, enrollment, and reimbursement requirements. |
Summary only, not legal advice. Confirm the requirements for your business with Arizona counsel.
These references support the discussion in each step. Operational suggestions are separate from legal requirements.
Local planning
Include patients who split time between Arizona and another state. Check the patient's physical location at every visit and before follow-up care.
A useful launch plan starts with a narrow service definition. Specify the patient group, treatment, follow-up schedule, and geographic area. Then test whether your clinical team and local partners can deliver it.
Interview prospective patients about appointment access, travel, language, and payment preferences. Check their ability to use the intended care format. These interviews inform the operating plan; they do not establish market size or clinical eligibility.
Arizona §36-3602 generally requires verbal or written informed consent before telehealth, subject to its exceptions. Electronic consent is included. The statute addresses confidentiality and continued application of prescribing and licensing rules. A telehealth encounter therefore needs more than a general website agreement: the clinical team must establish that the proposed method meets the applicable professional requirements.
Sources: Arizona Revised Statutes §36-3602; Arizona Revised Statutes §36-3606: interstate registration; Arizona Revised Statutes §36-3605: communication medium.
Keep the consent text, its version, and the acceptance record with the clinical workflow. Distinguish permission to receive treatment from permission to receive promotional messages. Test a patient who cannot complete video and needs another care format. Have the clinician decide whether that alternative is suitable before the visit continues.
The steps below are operating recommendations. The linked state material supports the specific legal summary above. Your advisers must apply current law to your actual entity, clinicians, products, and patients.
Step by step
Use these eight steps to turn the Arizona service plan into assigned work. Finish the clinical and legal decisions before configuring the patient journey around them.
Arizona §36-3606 gives eligible professionals a registration route for interstate telehealth. It is a defined alternative with conditions, rather than a conversion of another state's license into unrestricted Arizona practice. The statute limits in-person services and addresses offices in Arizona. Read the interstate registration statute.
Describe the proposed work location before choosing that route. A doctor who will remain outside Arizona presents a different plan from a doctor who will also examine patients at an Arizona office. Ask the relevant board to confirm the credential needed for the actual arrangement.
Record the chosen route beside each professional's role in the business. If the service later adds a physical location, reopen the credential review. Do not let a telehealth registration become the basis for offering a broader service that nobody assessed when the original application was filed.
The Arizona application framework calls for professional-license information, contact details, evidence of liability coverage, and an Arizona statutory agent. It also includes restrictions concerning license status and disciplinary history. Those conditions deserve a credential review before the founder forecasts available clinical capacity. See §36-3606(A).
Use a registration checklist for each profession, with a named person responsible for the evidence. Ask the insurance adviser to confirm the geographic and service scope of coverage. Keep the actual policy evidence with the application record. A certificate from a different business should not quietly substitute for the proposed practice's coverage.
Prepare an exception process for an application that does not meet the expected conditions. The recruitment team needs a clear status such as awaiting review or unavailable for Arizona assignments. Avoid advertising a clinician's availability while eligibility is still a question.
Discuss the care model and integrations for your Arizona launch.
Arizona's interstate provision calls for annual registration updates and a report of patients and encounters. It also specifies notification after certain license restrictions or disciplinary actions. A business should treat the credential as an ongoing responsibility rather than a document collected once during hiring. Read the continuing obligations.
Decide how the practice will count Arizona encounters by professional and encounter type. Keep the report definition consistent through staff changes and software migrations. If billing data combines several services into one charge, confirm that it still supplies the information needed for the clinical report.
Test the reporting process with sample visits before the first reporting period closes. Separately, define who receives a clinician's notice of a restriction and who reviews scheduled appointments. A licensing event can affect tomorrow's coverage even if the next annual update is months away. Keep a sample report with the approved definition of an encounter. That example helps a future operations owner reproduce the count after a software change.
Arizona §36-3602 addresses informed telehealth consent. Section 36-3605 separately directs the professional to make a good-faith determination about the communication medium and access to records. The consent process should explain the service; it should not force the doctor to accept a clinically unsuitable format. Review consent requirements and the medium determination.
For a mobile-first service, rehearse a patient who can complete intake but cannot maintain video. Give the clinician enough information to decide what comes next. An administrative switch to telephone should not silently settle a clinical question.
Keep the patient's agreement and the doctor's assessment as different records. The fact that a patient prefers a convenient method does not establish that it can support the proposed diagnosis. Explain the alternative, including any examination or rescheduling step, before promising that treatment will proceed.
Arizona's interstate statute requires registration with the prescription-monitoring program before a registrant prescribes a controlled substance to an Arizona patient. It also preserves Arizona's prescribing, dispensing, and professional-practice rules. A telehealth registration alone does not settle the medication decision. See the prescribing conditions.
List the medications under consideration and ask the clinical lead which assessment each one needs. The credentialing owner should document the relevant drug authority separately from the general telehealth registration. The pharmacy should review the intended arrangement before the business promises fulfillment.
Use a sample case in which a clinician's general registration is current but the medication-specific evidence is missing. Route that request for resolution before a prescription decision. A generic green credential indicator can conceal the missing requirement if the system combines all professional authority into one status.
Arizona lists exceptions to interstate registration for specified circumstances, including some care for residents of another state and a low encounter count. The exact facts matter. A seasonal resident, a newly acquired Arizona patient, and a person receiving after-care for an out-of-state procedure may follow different analyses. Review the exceptions in §36-3606(E).
Ask counsel to describe the evidence needed for any exception the service intends to use. Give staff a way to record the relevant relationship without making their own legal determination. Track the usage of any pathway with an encounter limit.
For the launch rehearsal, compare a patient who continues care with their home-state professional and a patient recruited by the new brand. A shared winter address does not make their clinical relationships equivalent. When the evidence is incomplete, the business needs a licensed route or a clear pause while the question is resolved.
An Arizona brand may begin with remote care and later want an examination site, local support office, or wider clinical offering. Review that expansion against the original credential choice before making commitments. The interstate statute's limits should be part of the project plan, not a surprise discovered after a lease is signed.
Have counsel review the entity, ownership, management agreement, and referral arrangements separately. This article's registration analysis does not answer those business-structure questions. Bring a diagram that identifies the practice, administrative company, and organizations receiving patient payments.
Price the proposed service using the work it actually includes. Allocate time for registration maintenance and encounter reporting. If another organization charges for an examination or medication, make the separation clear in the offer. The financial plan should reflect the selected Arizona model rather than an assumed nationwide process.
A useful Arizona release test reaches beyond the first booked visit. Generate a sample annual encounter report and ask the credential owner to reconcile it with the fictional patient records. Check that the professional's identity and encounter types remain understandable after export.
Next, simulate a restriction reported on a clinician's other-state license. The team should know who reviews Arizona eligibility, who checks future appointments, and who communicates any necessary change to patients. Record those responsibilities before enrollment opens.
Finally, test a proposed transition from remote care to an Arizona in-person service. Confirm that the project prompts a fresh credential review rather than inheriting the registration status unchanged. These rehearsals convert the statute's ongoing conditions into concrete operating work. They also give Bask a useful basis for discussing the records, reporting, and workflow integrations the actual service needs.
What to launch
Choose a Arizona treatment category with your clinical team. These examples describe operating decisions, not promises of patient eligibility or partner availability.
A seasonal-resident model should distinguish continuity with an existing home-state professional from acquisition of new Arizona patients. Document the relationship relevant to the chosen authority. Do not assume that every winter visitor fits the same registration exception simply because their permanent address is elsewhere.
Arizona's exception language includes specific circumstances involving a home-state behavioral-health professional. Have counsel assess that pathway for the intended population. The clinical team still needs a suitable encounter format and an Arizona emergency response plan. Preserve a current callback method when the patient travels.
Separate the general interstate registration, medication-specific authority, and pharmacy review. A business should be able to explain which evidence supports each one. Include the encounter type in reporting design and keep the patient's requested product from determining whether the clinician approves treatment.
Built for telehealth
Bring the Arizona service plan to a Bask walkthrough. Review intake, clinical records, pharmacy connections, payments, and support against the actual workflow. Confirm integrations and state coverage before signing partner agreements.
Built with Bask
Customer experiences supplied with permission. These are individual testimonials, not independently audited results or evidence of Bask availability in another country.
“Bask gave us the infrastructure and confidence to scale faster than we could have on our own. From clinical workflows to backend automation, their platform removed major operational friction and let our team focus on patient experience and growth instead of technical headaches. What stands out most is their execution speed and reliability. When challenges come up, they solve them quickly and thoughtfully, not with generic responses. Bask is not just a platform. They are a true operating partner.“
No. Section 36-3606 supplies a conditional telehealth pathway and limits in-person work and offices. Select the credential using the clinician's intended location and activities. Revisit that choice if the company later adds a physical clinical service in Arizona.
The statute calls for annual updates and information about Arizona patients and encounter types. It also addresses notice of certain disciplinary or license changes. Assign the reporting owner and data source before the first patient visit instead of reconstructing a year's activity later.
The statute adds prescription-monitoring registration before controlled prescribing and preserves other applicable laws. The practice must review the clinician, medication, assessment, and pharmacy route together. General registration should not appear as a blanket medication authorization in the operating system.
Test the credential route, consent evidence, care-format decision, and encounter report. Include a seasonal resident whose relationship differs from a newly acquired patient's relationship. Then simulate a license-status change so the team can show how it reassesses future Arizona appointments.
Compare state, city, and country guides. Check the jurisdiction that applies to the patient, clinician, and business before you expand.
Bask Health publishes this AI-assisted guide from the references below. It has not received independent legal or clinical approval. Read the research method and correction policy.
Your next step
Bring your treatment plan, target patient group, and launch dependencies. Discuss the software and integrations your service needs.