Washington telehealth launch guide · 2026
Start here
To launch a telehealth service in Washington, start with professional authority and the care model. Washington's Department of Health describes telehealth as subject to professional scope, state standards, and federal and state law. It also explains the telemedicine training requirement that began in 2021. Medical and osteopathic doctors are exempt from that training requirement; other covered professionals need their own review. A single onboarding checklist should not apply the exemption to the whole clinical team.
This guide covers patients in Washington. Ownership, professional authority, prescribing, and payment depend on the service and care model.
Published by Bask Health · Editorial process
Updated
Your launch, mapped out
Washington
Apply the training requirement to the correct professions
The essentials
Start with the decisions that shape your legal structure and clinical workflow.
| Launch decision | Washington |
|---|---|
| State requirement | Washington's telemedicine training requirement includes an exemption for medical and osteopathic doctors. |
| Regulators | Washington Medical Commission; Washington Board of Osteopathic 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 Washington counsel.
These references support the discussion in each step. Operational suggestions are separate from legal requirements.
Local planning
Map data across intake, support, and marketing before the first patient visit. Include both medical and osteopathic doctors in the licensing review.
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.
Washington's Department of Health describes telehealth as subject to professional scope, state standards, and federal and state law. It also explains the telemedicine training requirement that began in 2021. Medical and osteopathic doctors are exempt from that training requirement; other covered professionals need their own review. A single onboarding checklist should not apply the exemption to the whole clinical team.
Sources: Washington Department of Health: telehealth resources.
Track required training by professional role. Confirm authority for patients physically in Washington and review exceptions before using them. Have counsel assess Washington privacy duties for information collected outside a traditional clinical record. Test the intake, care, and marketing systems separately so permission to receive care is not treated as permission to share health-related data.
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 Washington service plan into assigned work. Finish the clinical and legal decisions before configuring the patient journey around them.
Washington's Uniform Telehealth Act applies to services delivered to a patient located in Washington. It authorizes telehealth within professional scope and applicable state and federal law, and permits a practitioner-patient relationship to begin remotely. It does not authorize establishing that relationship through email, instant messaging, text messaging, or fax. The broader telehealth definition likewise excludes those tools used in isolation. Chapter 18.134 RCW
That distinction matters for a messaging-first product. Intake messages can help organize information, but the clinical group must specify how a valid relationship begins and what evaluation supports treatment. Choose the care format after examining the condition and information needed, not after deciding which interaction costs least. Record where the patient is during each encounter; the act places care at that location. A Washington address retained from signup cannot establish authority for a visit that the patient attends while traveling elsewhere.
The act recognizes Washington credentials and other authorized routes, including applicable compacts. It also permits certain services from a professional licensed in good standing elsewhere: consultation with a responsible treating practitioner, specialty assessment or diagnosis and treatment recommendations without providing treatment, and qualifying continuity follow-up by a primary care practitioner, mental health practitioner, or recognized clinical specialist for an established patient temporarily in Washington who received treatment where the professional is located and licensed. RCW 18.134.050
Write separate appointment types for these situations. A second-opinion assessment should not silently become recurring medication management under the same exception. A continuity visit needs evidence of the prior treatment and temporary presence, rather than a checkbox saying the patient is established. Have the credentialing team review the exact route before assigning the encounter. For a service recruiting new Washington patients at scale, evaluate ordinary Washington practice authority instead of stretching a limited exception into the default business model. Review requirements for the doctor's own location as well.
Discuss the care model and integrations for your Washington launch.
Washington applies the standards for comparable in-person care to telehealth, including prescribing, identity verification, records, informed consent, privacy, and security. The act restricts regulators from imposing a different professional standard merely because care is remote or limiting the technology that may be used. That does not make every technology clinically adequate for every patient. RCW 18.134.040
Training is a separate roster question. RCW 43.70.495 requires covered professionals delivering clinical telemedicine services to complete training and retain an attestation. Medical and osteopathic doctors are exempt from that particular requirement. Qualifying alternative training can satisfy the requirement for other professionals when accompanied by an attestation. Washington telemedicine training statute
Do not extend a doctor's exemption to the rest of the team. Keep training evidence beside each applicable credential and review content when the role changes. The encounter still needs a practical escalation process when a visual assessment, examination, or local diagnostic test is necessary.
Permission to deliver care under the Uniform Telehealth Act does not create a payment obligation for every carrier or public program. The act preserves the reimbursement requirements in the relevant insurance and medical-assistance chapters. It also prevents direct billing for a telehealth service that is not a permissible telemedicine service under those chapters without the patient's consent to be billed before the service. RCW 18.134.070
Configure checkout and clinical escalation together. Staff need to know when a proposed service falls outside the applicable covered telemedicine pathway and how to explain the charge before care. A notice added to an invoice afterward cannot serve that purpose. Keep evidence of the patient's decision with the service and price that were described. When the doctor changes the planned modality or recommends a different assessment, give the billing team a route to recheck the terms without delaying necessary clinical guidance. Avoid treating a generic subscription agreement as the answer to every unexpected charge.
Washington's My Health My Data Act covers a broad category of information linked or reasonably linkable to a consumer that identifies physical or mental health status. It includes information about seeking care and certain inferences drawn from other information. Its exemptions identify particular protected information and processing contexts, including HIPAA-protected information; they should not be treated as a blanket exemption for every tool a health business uses. Chapter 19.373 RCW, definitions and exemptions
Inventory the eligibility quiz, lead form, advertising tags, appointment scheduler, analytics events, support tickets, and clinical system. Ask what each recipient can infer from an event name or page address, not just whether a field contains a diagnosis. Have counsel classify those flows and their exemptions. A visitor who leaves before creating a patient account can still generate information needing review. Give the marketing and product teams concrete rules about which data may enter their systems rather than relying on the clinical platform's compliance claims.
For covered consumer health data, the act distinguishes consent to collect from consent to share, with an exception to the extent necessary to provide a product or service the consumer requested. Required sharing consent must be separate from collection consent. A sale requires its own valid authorization, with specified content, separate from those consents. Broad terms of use and deceptive interfaces do not satisfy the statutory consent definition. RCW 19.373.010, .030, and .070
Use those distinctions in vendor review. A service necessary to book an appointment and an advertising audience built from treatment interests do not automatically share the same legal basis. Identify the purpose, categories of information, recipients, and withdrawal method before adding a new integration. Publish the required consumer health data privacy policy and make sure it describes the actual flows. The law also addresses new categories and purposes, so a later product experiment may require updated disclosure and consent before the data starts moving.
The act gives covered consumers rights to access information, withdraw consent, and request deletion. Responses generally must occur within 45 days of receipt, with one additional 45-day extension when justified and timely explained. Deletion duties include notifying recipients and addressing archived or backup copies under the statute's limited delay, which cannot exceed six months from authentication. A consumer cannot be required to create a new account merely to exercise these rights. RCW 19.373.040
Build a request register that tracks receipt, authentication, affected systems, vendor notices, completion, and any appeal. Keep this process distinct from destroying a medical record that another law requires the practice to retain; counsel must determine what information the act covers and which exemptions apply. Processor contracts should contain binding instructions and appropriate assistance obligations. Test a request from a person who submitted an eligibility form but never booked care. That person is easy to lose if support searches only the patient chart.
The My Health My Data Act prohibits specified geofencing around entities providing in-person health services when used to identify or track care seekers, collect consumer health data, or deliver health-related notifications, messages, or advertising. Its geofence definition concerns a virtual boundary no more than 2,000 feet from the physical location's perimeter. This restriction needs an advertising review separate from ordinary clinical consent. RCW 19.373.010 and .080
Ask agencies and ad vendors to explain how location audiences are built before activating a campaign around clinics. Then run a complete launch exercise: a visitor reads about treatment, submits information, declines optional sharing, schedules a consultation, receives a billing explanation, and later asks for deletion of covered marketing data. Review the actual network destinations and staff handoffs at each point. Washington launch readiness depends on both clinical access and the handling of information before and after care; approving the video room alone leaves much of the patient journey unchecked.
What to launch
Choose a Washington treatment category with your clinical team. These examples describe operating decisions, not promises of patient eligibility or partner availability.
The out-of-state specialty pathway expressly distinguishes assessment, diagnosis, and treatment recommendations from providing treatment. Design the service description, clinician instructions, and follow-up offer around that boundary. If a patient wants ongoing care after the opinion, route the request through a separately verified authority pathway rather than letting a support agent extend the original appointment type. Out-of-state services
A symptom quiz or treatment-interest form can create consumer health data before a medical relationship exists. Review inferred interests, persistent identifiers, and third-party disclosures together. A product that does not issue prescriptions still needs to assess whether the Washington privacy law covers its information and how consumers exercise their rights. Health-data definitions
A program combining doctors, nurses, and other professionals needs role-specific credential and training records. Washington's medical and osteopathic doctor exemption from the statutory training requirement does not remove the requirement for other covered team members. Keep the signed attestation for required training available rather than relying on a vendor's general statement that its software is easy to use. Training requirements
Built for telehealth
Bring the Washington 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’s no-code builders and licensed professional network allowed us to launch quickly, while their headless technology makes it easy to plug into their system and gives us more control over the user journey as we grow. The platform supports strong integrations - like Intercom for real-time patient support - and offers a comprehensive set of webhooks that give us the data we need to deliver a more personal patient experience. What really stands out is the partnership: the Bask team is deeply invested, collaborative, and works closely with us as we build and scale. We’d strongly recommend Bask to teams looking for a well-designed platform and a partner committed for the long haul.”
No. Washington recognizes ordinary practice authority and specific out-of-state exceptions. The specialty assessment exception permits assessment, diagnosis, or treatment recommendations, but excludes providing treatment. The continuity exception also has conditions, including an established patient temporarily in Washington. Review the exact service and credential route before booking.
Medical and osteopathic doctors are exempt from the particular training requirement in RCW 43.70.495. Other covered professionals must review the requirement for their roles and retain the required attestation. The exemption does not remove professional standards, scope limits, privacy obligations, or the need to know how the care platform works.
No. The act includes exemptions for specified information and processing contexts. A company should analyze its actual data flows rather than assume its HIPAA relationship exempts all marketing, support, or pre-appointment information. Health interests inferred from identifiers or browsing activity can require a separate review from the clinical chart.
The Uniform Telehealth Act requires prior patient consent for direct billing of a telehealth service that is not a permissible telemedicine service under the identified coverage chapters. Review the service, plan, and applicable law before care, explain the charge, and preserve the decision. An invoice disclaimer added afterward does not supply prior consent.
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.