Telehealth Consent: Definition, Template & Example

A telehealth consent form documents that a client agreed to receive care by video or phone after learning the modality's risks, privacy limits, emergency procedures, and technology-failure backup plan. Clinicians obtain and document it before or at the first virtual session. Most US states require some form of telehealth consent by statute, regulation, or Medicaid policy, and documented verbal consent usually satisfies them.

Free to use and share. No signup required.
Already have session bullets or a transcript? Generate a structured draft with BastionGPT — you review and sign it.
Who writes it

Therapists, psychologists, counselors, and any clinician delivering care by video or phone; trainees under supervision

Audience

The client or guardian and the virtual-care provider; later, payers, auditors, and licensing boards

Typical length

400 to 800 words · 5 to 10 minutes to review with the client (clinical team estimate)

Format family

Short consent form (compare: informed consent for treatment, NPP acknowledgment, release of information)

When it's used

Before or at the first telehealth session; revisited when the platform, modality, or client location materially changes

Standards context

Required by law or Medicaid policy in most US states; board standards govern in Canada and Australia; a standalone signed form is a convention

What is a telehealth consent form?

A telehealth consent form documents that, before care began by video or phone, the clinician explained the modality, its risks and limits, the privacy arrangements, and the plan for emergencies and technology failure, and the client agreed to proceed. No single body authored it. The closest thing to a shared lineage in mental health is Guideline 4 of the Guidelines for the Practice of Telepsychology, developed by the joint task force of the American Psychological Association, the Association of State and Provincial Psychology Boards, and the APA Insurance Trust, adopted July 31, 2013 and revised in 2024, alongside state statutes led by California Business and Professions Code section 2290.5, which began as the Telemedicine Development Act of 1996, a written-consent mandate, and reached its current verbal-or-written, documented standard with AB 809 in 2014. You will also see the document called a telemedicine consent, telepsychology consent, teletherapy consent, telemental health consent, or virtual care consent.

The disambiguation that matters: in nearly every jurisdiction the legal event is obtaining and documenting consent, not collecting a signature, and no jurisdiction requires a standalone telehealth form as a blanket rule. A general informed consent for treatment that specifically names telehealth is expressly sufficient in California Medi-Cal, New York, and Indiana. The telehealth consent is also not a privacy document: the Notice of Privacy Practices acknowledgment records receipt of privacy practices, while this form records agreement to a modality. And the most repeated myth runs the other way: traditional Medicare requires no consent at all for standard telehealth video visits; its annual verbal-consent rule applies only to communication technology-based services such as virtual check-ins and e-visits.

Who uses telehealth consent forms and when

Everyone delivering virtual behavioral health keeps one: solo therapists and psychologists, group practices, telepsychiatry services, hospital and health-system virtual care programs, and platform-based practices. The share of psychologists' clinical work done by telepsychology rose from about 7 percent before the pandemic to more than 85 percent during it (Pierce and colleagues, American Psychologist, 2021), and the consent form followed the migration. Obtain and document consent before or at the first telehealth session, then revisit it when something material changes: a new platform with different privacy characteristics, a shift from video to audio-only, or a client in a new state. For minors, the guardian consents and the minor assents, with the same telehealth disclosures layered onto the minor consent. This form records the agreement to the modality; the per-session clinical record lives in the telehealth therapy note, which is where each session's modality, platform, and client location belong.

Telehealth consent form structure: what goes in each section

Modality and platform. Name the service types offered (video, phone when clinically appropriate) and the specific platform, with a line on when in-person care is still expected. Pitfall: a form that says "video or phone" but never names the platform; Ontario's CPSO expects fresh consent when the technology materially changes, and an unnamed platform leaves nothing to compare a change against.

Risks and limits of telehealth. State the tradeoffs in behavioral health terms: possible technology failure mid-session, reduced nonverbal cues, and situations (crisis, some assessments) that call for in-person care. Pitfall: pasting general telemedicine risk language about the absence of a physical exam while skipping the risks that matter in psychotherapy, such as an interrupted session during emotionally intense work.

Privacy and the home setting. Cover both ends of the call: what the practice does (encrypted platform, business associate agreement in place, no session recording) and what the client controls (a private room, headphones, who else is home). Standard confidentiality limits still apply and belong here. Pitfall: a paragraph on encryption with silence about the client's own room; household members overhearing a session is a more common privacy failure than an intercepted video stream.

Identity and location verification at each session. The form commits both parties to a start-of-session routine: confirm identity, confirm the client's physical address today, and confirm the client can speak privately. Location drives licensure and emergency response. Pitfall: treating location as intake data; a client who quietly takes sessions from another state puts the clinician outside licensure, a problem no consent form cures after the fact.

Emergency plan and local resources. Record an emergency contact who can physically reach the client, the client's local emergency number, and the nearest emergency department, and state when the clinician will use them. Pitfall: a plan that reads "call 911"; a clinician dialing 911 reaches dispatch near the clinician, not the client, so the plan has to run through the client's local resources and named contact.

Technology-failure backup plan. Script the failure: who calls whom, on which number, after how many minutes, and what happens if reconnection fails (reschedule, switch to phone, move to the emergency plan). Pitfall: no ordering of steps, which turns a dropped connection with a distressed client into an improvised judgment call and, afterward, an undocumentable one.

Recording and AI tools. State the default (no recording by either party) and that any recording, including AI scribe or transcription processing, needs its own separate consent. Pitfall: stretching the telehealth consent to cover recording; recording consent is a distinct object under the APA Ethics Code (Standard 4.03) and many state Medicaid rules, and some states add all-party consent under recording law.

Right to refuse or withdraw. The client can decline telehealth, withdraw consent at any time, and ask about in-person alternatives without penalty. California ties this right directly to its consent statute, and Kentucky's telepsychology rule requires the right to refuse plus a description of alternatives. Pitfall: framing telehealth as the only way to access the practice; the withdrawal right is one of the disclosures state rules name explicitly.

Licensure line, consent statement, and documentation. Close with the clinician's license number and state(s), a line that services are available only while the client is physically in a jurisdiction where the clinician holds a license, and the consent statement itself: a written signature or a note that verbal consent was given, by whom, and on what date. Pitfall: a filed signature with no documented consent event; California's standard is that consent, verbal or written, "shall be documented", and a bare signature page shows agreement without the required conversation.

Blank template (copy and adapt)

TELEHEALTH CONSENT FORM

Client: ____________________________  DOB: ____________
Clinician: _________________________  License # and state(s): ____________
Practice phone: ____________________  Portal/email: ______________________

MODALITY AND PLATFORM
Services offered by: [ ] secure video   [ ] phone (when appropriate)
Platform: __________________________

RISKS AND LIMITS
I understand telehealth carries risks, including technology failure,
interruption, and reduced nonverbal cues, and that some situations may
require in-person or local care instead.

PRIVACY
The practice uses an encrypted platform and does not record sessions.
Privacy also depends on my own space and device. The standard limits of
confidentiality still apply.

EACH SESSION
My clinician will confirm my identity, my physical location (address),
and that I can speak privately before we begin.

EMERGENCY PLAN
Emergency contact (name and phone): _____________________________________
Local emergency number: ___________  Nearest ER: ________________________
Local crisis line: ______________________________________________________

IF TECHNOLOGY FAILS
If the connection drops, my clinician will call me at: __________________
If we cannot reconnect within ____ minutes, the plan is: ________________

RECORDING
Neither party records sessions. Any recording or AI processing would
require my separate written consent.

LOCATION AND LICENSURE
Services are available while I am physically located in: ________________
I will tell my clinician before joining from a different state,
province, or country.

AGREEMENT
I have had the chance to ask questions. I may decline or withdraw from
telehealth at any time and ask about in-person options.
Consent: [ ] written (signed below)   [ ] verbal, documented in the record
Client/guardian signature: ___________________  Date: ___________
Clinician signature: _________________________  Date: ___________

Free to use and share, no signup. The PDF includes a one-page cheat sheet with section-by-section pitfalls and a pre-sign checklist; the DOCX is the blank template, ready to adapt.

Sample telehealth consent form

Scenario: a licensed marriage and family therapist in private practice completes telehealth onboarding with a new adult client who will attend weekly video sessions from home. All details are fictional.

Telehealth Consent. Client: R.L., 29  ·  Clinician: D. Okafor, LMFT (Colorado license 1847)  ·  Completed: 08/04/2026, reviewed together by video

Modality and platform: Weekly individual psychotherapy by secure video on ClearPath Telehealth, with phone backup at the cell number on file. In-person sessions remain available at the Lakewood office by arrangement.

Risks and limits: Reviewed possible connection failure, interruption, and reduced nonverbal cues. R.L. understands that a crisis may require local, in-person, or emergency care rather than video.

Privacy: Platform is encrypted with a business associate agreement in place; neither party records sessions. R.L. will join from a home office with a closed door and headphones, and will reschedule rather than hold a session with others in the room. Standard confidentiality limits reviewed and unchanged.

Each session: Clinician confirms identity, street address, and ability to speak privately at the start of every session.

Emergency plan: Emergency contact: T.L. (sister), (555) 014-2276, aware she is listed. Local emergency number: 911. Nearest emergency department: Riverview Medical Center, about 4 miles from home. Crisis line 988 saved in R.L.'s phone. If safety requires, clinician will contact emergency services near the address confirmed at the start of session.

If technology fails: Clinician calls R.L.'s cell within 5 minutes of a dropped connection. If not reconnected by 15 minutes, the session is rescheduled. Any safety concern moves straight to the emergency plan.

Recording: No recording by either party. Any future recording or AI processing requires separate written consent.

Location and licensure: Services are provided while R.L. is physically in Colorado, where D. Okafor is licensed. R.L. will give notice before joining from any other state; those sessions may need to be rescheduled.

Agreement: Questions invited and answered (R.L. asked about work travel; in-state trips are fine, out-of-state trips need advance notice). R.L. may decline or withdraw from telehealth at any time and ask about in-person options. Signed electronically by R.L. 08/04/2026; countersigned D. Okafor, LMFT, 08/04/2026; review documented in the chart.

This sample is fictional and for educational purposes. It does not describe a real patient.

↑ Back to the template and downloads

Why this sample works

  • The consent event is documented, not just signed. The record shows who reviewed the form, how (together by video), the client's question, and the date, which is what verbal-or-written consent statutes actually test.
  • The emergency plan names a person, a facility, and a location. A named contact who knows she is listed, the nearest emergency department, and a per-session address check give the clinician something to act on from another city.
  • The technology-failure plan has an order of operations. Who calls whom, on which number, after how long, and when the emergency plan takes over; a dropped call follows a script instead of a guess.
  • The licensure line anticipates travel. Consent is tied to the client's physical presence in a licensed state, with advance notice for exceptions, the constraint that binds hardest when clients move around.
  • Recording and AI tools are closed off explicitly. The default is no recording, and any future recording or scribe processing is routed to its own separate consent instead of riding on this one.

Writing these after every session? BastionGPT drafts complete notes from bullets, dictation, or a transcript.

Generate a note from bullets

Documentation and compliance considerations

Sort the rules by strength before you build the form. In the United States, the consent event itself is LAW in most states: the Center for Connected Health Policy reports that the majority of states put "some sort of telehealth specific informed consent requirement" in statute, administrative code, or Medicaid policy (CCHP publishes no numeric tally; commonly cited secondary counts land at 45 states plus the District of Columbia). California's Business and Professions Code section 2290.5 is the model: verbal or written consent, documented, and noncompliance "shall constitute unprofessional conduct". PAYER POLICY is a separate layer: some state Medicaid programs require written consent (Alabama and Georgia among them), and traditional Medicare requires consent only for communication technology-based services, once a year and verbal, with the cost-sharing discussion documented. Everything else is CONVENTION: the standalone form, the annual re-consent ritual, and the signature itself are practice choices rather than legal requirements, and a few states (Florida, Hawaii, and Illinois among them) have no telehealth-specific consent rule at all, leaving general consent law in charge.

Outside the US, board standards carry the weight. Ontario's CRPO electronic practice standard (updated effective January 1, 2024) requires consent specific to electronic services, and Ontario's CPSO adds the rare explicit answer on platform switches: re-consent when the modality or technology materially changes (more in the Canada telepsychology note). Australia's AHPRA telehealth guidance holds virtual care to the in-person standard, and the Psychology Board of Australia Code of Conduct, effective December 1, 2025, treats consent as an ongoing process to revisit after a reasonable period, widely read as about 12 months: the closest thing to an annual rule in any of the three countries. Wherever you practice, the consent record is ordinary clinical-record material: clients can request it, disclosure to third parties runs through a release of information, and retention follows general record law rather than any telehealth-specific clock. If a client carries elevated risk, align the consent's emergency section with the safety plan so the address check, contacts, and local resources match instead of drifting apart.

↑ Back to the template and downloads

Common telehealth consent form errors auditors flag

Read the audit record carefully, because the famous telehealth numbers are not consent findings. The HHS Office of Inspector General's South Carolina Medicaid telemedicine audit (A-04-18-00122, April 2020) found 97 of 100 sampled payments unallowable and recommended a $1,524,536 federal refund, but for 95 of those claims the failure was missing start and stop times or missing consulting-site location, not consent; vendor pages recycle it as a consent statistic anyway. The parallel 2018 Medicare telehealth audit failed 31 of 100 sampled claims on originating-site and eligibility grounds. There is also no denial code specific to telehealth consent: a consent-shaped denial routes through generic codes such as CARC 16 with an N-series remark. Where consent failures actually surface is licensing exposure, since statutes like California's make undocumented consent unprofessional conduct. The BastionGPT Clinical Advisory Board sees the same errors most often in telehealth consent form reviews:

  • A signature on file, no consent event in the record. The chart holds a signed PDF but never says who obtained consent, when, how (verbal or written), and what was discussed; documented-consent statutes test the event, not the artifact.
  • Location verified once, at intake. The client travels, the record cannot show which state any session came from, and the clinician cannot show sessions stayed inside licensed jurisdictions; site and location documentation is exactly what the OIG telemedicine audits flagged.
  • An emergency plan built for an office. "Call 911" with no per-session address confirmation, no local emergency department, and no named contact who can physically reach the client.
  • Medicare rules imported where they do not apply. Annual re-consent rituals copied from the virtual check-in rules onto standard video visits, while the coverage condition that does apply since October 1, 2025 (an in-person visit within the 6 months before the first telemental health service, then at least annually, with exceptions) goes untracked.
  • The consent stretched over recording and AI tools. Session recording or scribe processing treated as covered by the telehealth consent, when it needs its own separate consent and, in some states, all-party agreement under recording law.
How BastionGPT helps

BastionGPT is specifically trained, tuned, and clinically tested on telehealth consent forms.

  • Draft a complete telehealth consent from your practice details: platform, modalities, backup steps, emergency workflow, and the states or provinces you serve, ready for attorney review.
  • Rewrite dense consent language in plain English; analyses of US consent forms find most are written above recommended reading levels, and BastionGPT brings the level down while keeping every disclosure intact.
  • Check a finished form before you file it: licensure and location line, emergency plan completeness, technology-failure steps, recording clause, and the documented-consent line.

See how clinicians use it day to day on the AI therapy notes page.

Many BastionGPT users report saving more than 90 minutes per day on documentation.

HIPAA-compliant with a signed BAA on every plan. Your data is never used to train models. BastionGPT drafts, you review and sign.

Frequently asked questions

In most US states, documented verbal consent is legally sufficient: California, Arizona, Texas, and New York all accept it, and Canadian college standards and Australian board guidance do the same. Write down who consented, when, and how. Written consent is the exception, required by a minority of state Medicaid programs (Alabama, Georgia, and Idaho among them) and in some recording situations. A signature is belt and suspenders, not a universal legal requirement.

Not for standard telehealth video visits. The annual verbal-consent requirement applies only to communication technology-based services such as virtual check-ins and e-visits, where cost sharing must be disclosed; that consent can be collected by auxiliary staff under general supervision. See the CMS Telehealth Services fact sheet. Separately, since October 1, 2025 Medicare telemental health carries an in-person visit requirement (within the 6 months before the first telehealth service, then at least annually, with exceptions); that is a coverage condition, not a consent rule, but it belongs on the same compliance checklist.

No jurisdiction requires a separate document as a blanket rule. A general informed consent for treatment that specifically names telehealth and includes the required disclosures is expressly sufficient in California Medi-Cal, New York, and Indiana. Use a standalone form when a payer requires a discrete telehealth acknowledgment or when you want a single auditable record of the telehealth disclosures.

No US telehealth statute requires annual re-consent. The annual idea is imported from two narrower rules: Medicare's once-a-year verbal consent for virtual check-ins and e-visits, and Australia's Psychology Board Code of Conduct (effective December 1, 2025), which treats consent as ongoing and worth revisiting after about 12 months. The trigger that matters everywhere is material change: a new platform with different privacy characteristics, a switch from video to audio-only, or a client in a new jurisdiction. Ontario's CPSO makes re-consent on material change an explicit requirement.

Licensure, not consent, is the binding constraint: you generally must be licensed where the client is physically located at the time of the session. Some states offer short windows (Arizona allows up to 90 days per year of practice by out-of-state providers; Utah has a 45-day transitional allowance), and a new state can also mean new consent reflecting that state's disclosures. Confirm and document the client's location at each session, and have clients agree in the consent to give notice before joining from somewhere new.

Address audio-only explicitly rather than assuming video language covers it. Texas Medicaid requires documented consent (verbal is fine) before audio-only behavioral health services, Medicare expects the practice to have video capability and a documented reason audio-only was used, and Kentucky's telepsychology rule excludes routine audio-only telephone care except in limited-connectivity situations. A line in the consent naming phone sessions, when they are used, and their added limits covers most of this.

No. Under 45 CFR 164.506, consent to use health information for treatment, payment, and operations is optional, and HIPAA imposes no telehealth-consent duty. HIPAA's role is different: it governs how the platform and the records are secured, which is why the Notice of Privacy Practices acknowledgment and the telehealth consent are separate documents. Telehealth consent requirements live in state law, Medicaid policy, and licensing board standards.

As long as the clinical record they belong to. Retention comes from general record law, not telehealth rules: Texas, for example, requires telehealth records including consent be kept at least 5 years, or the program's required period if longer, and state and provincial minimums elsewhere often run longer. HIPAA's six-year clock covers compliance documentation such as policies, not the chart, so do not treat it as your retention rule.

Yes. Give it your platform, modalities, emergency workflow, and the states or provinces you serve, and it drafts the form, rewrites it in plain language, and checks a finished version for the disclosures reviewers look for: location and licensure line, emergency plan, backup steps, recording clause, and the documented-consent line. Have your attorney or board resources confirm state-specific wording. BastionGPT is HIPAA-compliant with a signed BAA on every plan, and your data is never used to train models.

Educational content, not legal or billing advice. Sample notes are fictional. Follow your organization's policies and your board, payer, and jurisdiction requirements.