Posted on

Nov 11, 2026

Is AI Scribing Legal in Tennessee Under the One-Party Wiretap Statute? 2026 Clinical Operations Playbook

Is AI Scribing Legal in Tennessee Under the One-Party Wiretap Statute? 2026 Clinical Operations Playbook - Scribing.io
Is AI Scribing Legal in Tennessee Under the One-Party Wiretap Statute? 2026 Clinical Operations Playbook - Scribing.io

Is AI Scribing Legal in Tennessee Under the One-Party Wiretap Statute? 2026 Clinical Operations Playbook

Yes, AI scribing is legal in Tennessee because Tenn. Code Ann. § 39-13-601(b)(5) permits recording when one party to the conversation, typically the treating clinician, consents. The recording must not serve a criminal or tortious purpose, the clinician must remain present, and the vendor must operate under a HIPAA business associate agreement.

Tennessee's one-party consent statute authorizes clinician-initiated ambient AI recording

CLINICAL UPDATE 2026: Revised for 2026 CMS CPT G2211 attestation rules, California SB 1120 compliance, and NCCI Modifier 25 bundling criteria.

Tennessee's criminal wiretapping statute, Tenn. Code Ann. § 39-13-601, makes it unlawful to intentionally intercept a wire, oral, or electronic communication. Subsection (b)(5) carves out the exception that governs every ambient AI scribe deployment in the state: a person not acting under color of law may intercept a communication when that person is a party to it, or when one of the parties has given prior consent.

The physician, nurse practitioner, or physician assistant conducting the visit is a party to the exam room conversation. When that clinician activates the AI scribe, the clinician supplies the single consent Tennessee requires. No statutory provision requires the patient's separate permission, a signed form, or an audible announcement before the recording begins.

Tennessee adopts its definitions from the state's Wiretapping and Electronic Surveillance Act (Tenn. Code Ann. § 40-6-303). An "oral communication" is one uttered by a person who exhibits an expectation that it is not subject to interception, under circumstances justifying that expectation. A closed exam room plainly qualifies, which is why the consent exception, not the absence of privacy, is the legal foundation for ambient documentation.

Federal law aligns with Tennessee. The Electronic Communications Privacy Act, 18 U.S.C. § 2511(2)(d), uses the same one-party framework and the same criminal or tortious purpose limitation. A Tennessee clinic that satisfies the state statute generally satisfies the federal Wiretap Act for in-state, in-person encounters.

The stakes of misapplying the exception are significant. A violation of § 39-13-601 is a Class D felony under § 39-13-602, carrying two to twelve years of incarceration and fines up to $5,000. Section 39-13-603 creates a private civil action allowing recovery of the greater of actual damages, $100 per day of violation, or $10,000, plus punitive damages and attorney fees. Class action counsel multiply that statutory floor across every recorded patient.

One-party consent protects the recording only while the clinician remains a party

The most common Tennessee exposure is not the initial activation. It is the moment the clinician leaves the room while the microphone keeps running. Once the clinician exits, the clinician is no longer a party to the conversation between the patient and a spouse, parent, or caregiver. No participant in that remaining conversation has consented, and the one-party exception no longer applies.

Consider a routine pediatric visit. The physician steps out to retrieve a vaccine, leaving a smartphone running the AI scribe on the counter. The two parents discuss a custody dispute, a medication they have been withholding, or a suspected injury. That segment is arguably an unconsented interception of an oral communication, and it may now sit in the vendor's processing pipeline and in a draft note.

Operational policy must therefore treat room exit as a mandatory pause trigger. Your written AI documentation policy should state that the recording device is paused or stopped whenever the consenting clinician is not physically present or actively participating by telehealth. Medical assistants and nurses who room patients should not activate the scribe on the clinician's behalf unless they themselves remain parties to the recorded conversation.

Third parties present with the clinician do not defeat consent. Interpreters, family members, students, and chaperones may all be captured lawfully while the clinician participates, because Tennessee requires only one consenting party. Best practice is still to announce the recording when a new person joins, because their presence changes the privacy expectations of the patient.

The crime-tort exception can convert lawful recording into felony exposure

Tennessee's one-party exception disappears when the communication is intercepted "for the purpose of committing any criminal or tortious act." This language mirrors federal law and has become the primary hook for plaintiffs challenging ambient AI tools nationally.

Plaintiffs typically argue that the purpose of recording extended beyond documentation: for example, to train commercial AI models, to sell de-identified voice data, or to disclose protected health information without authorization. If a court accepts that the recording was made to accomplish a tortious disclosure or an intrusion upon seclusion, the clinician's consent no longer insulates the clinic.

Federal courts generally require that the criminal or tortious purpose be independent of the recording itself, meaning the recording must be a means to a separate wrong. Medical directors should not rely on that judicial nuance. The cleaner defense is contractual and documentary: prove that the sole purpose of the recording is clinical documentation, and that the vendor is prohibited from secondary use.

Tennessee's ELVIS Act adds a voice-specific dimension. The Ensuring Likeness Voice and Image Security Act of 2024 recognizes a property right in an individual's voice. Vendor contracts that permit use of patient or clinician voiceprints to build synthetic voice products create avoidable conflict with that statute and strengthen a plaintiff's "secondary purpose" narrative.

A business associate agreement frames the AI vendor as agent, not eavesdropper

The emerging national litigation theory treats the AI vendor as a separate third party "listening in" on the visit. Class action complaints filed in 2025 under California's Invasion of Privacy Act targeted ambient documentation deployments using this theory, arguing that a vendor with the technical capability to use recordings for its own purposes is an independent eavesdropper.

Tennessee has not adopted California's "capability" approach, and its statute focuses on the consenting party's purpose. However, a Tennessee clinic with California patients, or a defendant facing a creative plaintiff, benefits from the same structural defense: the vendor must function as an extension of the clinic, akin to a dictation device or a contracted transcriptionist.

Five contract terms establish agent status for a Tennessee deployment:

  • A signed HIPAA business associate agreement under 45 C.F.R. § 164.504(e) before any patient audio is processed.

  • An explicit prohibition on model training using identifiable audio or transcripts without separate written patient authorization.

  • A defined audio retention window with automated deletion after note finalization, documented in the vendor's data map.

  • Subprocessor disclosure listing every cloud, speech recognition, and large language model provider touching the audio.

  • Breach notification timelines aligned with HIPAA and Tenn. Code Ann. § 47-18-2107 for any non-HIPAA personal information.

Review your current vendor against these terms using the State AI Scribe Consent & Compliance Vault, which tracks state-by-state wiretap classifications, disclosure statutes, and pending legislation relevant to ambient documentation.

HIPAA, not the wiretap statute, governs what happens to the audio afterward

The wiretap analysis answers only whether the recording was lawfully captured. Every subsequent use, disclosure, retention, and destruction decision falls under HIPAA's Privacy and Security Rules and Tennessee's medical records statutes.

Ambient documentation is a permitted use for treatment and health care operations under 45 C.F.R. § 164.506, so no patient authorization is required for the core scribe function. The Security Rule requires a documented risk analysis covering the recording device, transmission encryption, vendor storage, and access controls. Smartphones used as scribe endpoints need mobile device management and remote wipe capability.

Decide in writing whether raw audio becomes part of the designated record set. If your clinic retains audio after the note is signed, patients may request access to it, and Tennessee's ten-year physician record retention expectation under Board of Medical Examiners rules may arguably extend to that audio. Most clinics avoid this burden by deleting audio once the clinician attests the final note, retaining only the signed documentation.

The Tennessee Information Protection Act, effective July 1, 2025, largely exempts HIPAA-regulated protected health information and covered entities. Do not assume the exemption covers every data element: marketing analytics, website tracking, and non-patient voice data collected by a scribe vendor may fall outside HIPAA and inside TIPA.

Interstate telehealth imports all-party consent rules into Tennessee clinics

Wiretap law generally follows the location of the parties, and courts frequently apply the more protective state's rule. When a Tennessee physician conducts a telehealth visit with a patient physically located in an all-party consent state, Tennessee's one-party rule no longer settles the question.

Every state bordering Tennessee (Kentucky, Virginia, North Carolina, Georgia, Alabama, Mississippi, Arkansas, and Missouri) follows one-party consent for in-person conversations. Regional referral patterns are therefore low risk. The exposure arises with patients who are traveling, seasonal residents, college students, or telehealth patients in states such as California, Florida, Washington, Pennsylvania, Maryland, Massachusetts, Illinois, and Montana.

California's Penal Code § 632 requires consent of all parties to a confidential communication, and § 637.2 authorizes $5,000 in statutory damages per violation. Florida Statute § 934.03 treats unconsented recording as a third-degree felony. A Tennessee clinic recording a Florida-located telehealth patient without express consent carries Florida felony exposure regardless of Tennessee law.

The operational fix is simple: capture the patient's physical location at the start of every telehealth encounter and require verbal, documented consent before activating the scribe for any out-of-state patient. Many multi-state groups adopt universal verbal consent to remove the location variable entirely.

Groups operating Texas clinics alongside Tennessee sites face separate disclosure obligations. Texas is a one-party state, but provider disclosure duties for AI use in clinical care require their own workflow, detailed in our guide to Texas Medical Board Rule 165.1 AI Disclosure Compliance.

Patient notice is optional under Tennessee law but essential for defensibility

Tennessee law does not require notice, yet silent recording is a poor operating model. Patients who later discover undisclosed recording file Board complaints, post public reviews, and contact plaintiffs' firms. A brief disclosure costs seconds and eliminates the "secret recording" narrative that drives most privacy litigation.

A three-layer notice model works for most Tennessee practices:

  • Posted signage in check-in and exam areas stating that AI documentation tools may record visits.

  • A Notice of Privacy Practices update describing ambient documentation, vendor processing, and the patient's right to decline.

  • A verbal script at visit start, such as: "I use a secure AI assistant to help write my notes. Is that okay with you?"

Document the patient's response in the note using a structured consent field rather than free text. A consistent phrase, timestamped and tied to the clinician who obtained it, is far more persuasive in litigation or a Board inquiry than a generic policy binder. Standardize this language across specialties with the 1,000+ Specialty Clinical Macros library.

Honor refusals without friction. If a patient declines, the clinician documents manually or uses post-visit dictation. Never pressure a patient, and never resume recording after refusal without fresh consent. Behavioral health, substance use disorder, reproductive health, and minor confidentiality visits warrant default opt-in rather than opt-out handling, particularly where 42 C.F.R. Part 2 records are involved.

Six documentation parameters determine whether a Tennessee deployment survives audit

The table below maps each legal control to its documentation requirement, its audit failure mode, and the corresponding Scribing.io Clinical Interface mechanism.

Tennessee AI scribe compliance controls and audit vulnerabilities

Clinical Parameter

Documentation Requirement

Audit Vulnerability

Scribing.io DOM Mechanism

One-party consent basis

Identify the consenting clinician by name and credential for each recorded encounter

Recording activated by staff who were not parties to the conversation

Session start bound to authenticated clinician login with timestamped attribution

Continuous party presence

Pause or stop events logged whenever the clinician exits the room

Audio captured of patient and family after clinician departure (§ 39-13-601 exposure)

Manual pause control with session gap logging and clinician attestation of active participation

Patient location (telehealth)

Patient's physical state recorded before scribe activation

All-party consent violation under California, Florida, or similar statutes

Location confirmation prompt with mandatory verbal consent field for out-of-state patients

Patient notice and response

Structured consent statement with timestamp and refusal handling

No proof of disclosure, fueling "secret recording" claims and Board complaints

Structured consent macro inserted into the note header and locked after attestation

Recording purpose limitation

BAA plus written prohibition on model training and secondary use

Crime-tort exception argument that recording served commercial purposes

BAA-governed processing with documentation-only use restrictions

Audio retention and deletion

Written policy defining whether audio enters the designated record set

Unmanaged audio archives subject to access requests, subpoenas, and breach exposure

Configurable retention window with deletion after clinician note sign-off

Consent workflows create no billable service and never alter code selection

The AI scribe consent conversation is administrative. It does not count toward medical decision making, does not add time toward time-based E/M selection, and does not justify a separate diagnosis code. Coders should not append Z71.89 (ICD-10-CM), other specified counseling, to reflect a recording disclosure. Reserve Z71.89 for genuine clinical counseling that the note substantively documents.

Administrative examination encounters carry special recording considerations. When a visit is coded with Z02.9 (ICD-10-CM), encounter for administrative examinations, unspecified, a third party such as an employer or school may ultimately receive the report. Confirm that the patient understands the visit is being recorded and summarized for a non-treating recipient, and keep audio retention minimal.

G2211 attestation depends on documentation the AI cannot invent. The visit complexity add-on code requires that the clinician serve as the continuing focal point for all needed services or provide ongoing care for a single serious or complex condition. An ambient note must reflect that longitudinal relationship in the clinician's own assessment and plan. Templated G2211 language generated identically across every visit is a predictable audit target.

Modifier 25 claims require separately identifiable E/M work. When a procedure occurs at the same visit, NCCI bundling rules treat routine pre-procedure evaluation as included. The AI-generated note must clearly separate the problem-oriented history, exam findings, and decision making from the procedure note. Review drafts to confirm the scribe has not merged the two into one narrative.

California SB 1120 matters for Tennessee groups contracting with California-regulated health plans. The law requires that medical necessity determinations be made by licensed clinicians rather than automated tools. It does not regulate ambient scribes directly, but it signals regulatory expectations: AI may draft, but a licensed human must decide and sign.

Clinician attestation remains the legal anchor. Every AI-generated note must be reviewed, edited, and signed by the rendering provider before claim submission. Under the False Claims Act, an unreviewed AI hallucination that inflates complexity is the signing clinician's error, not the vendor's.

A 30-day rollout protocol makes Tennessee deployments defensible

Medical directors can implement a compliant program in four weeks without slowing clinic throughput. Assign a named compliance owner, typically the practice administrator or privacy officer, to track each milestone.

Week one: contracts and risk analysis

Execute the business associate agreement and confirm the five contract terms listed earlier. Complete a HIPAA Security Rule risk analysis covering recording endpoints, network transmission, vendor storage, and subprocessors. Document the clinic's decision on audio retention and designated record set status.

Week two: policy and notice

Adopt a written AI documentation policy citing Tenn. Code Ann. § 39-13-601(b)(5) as the consent basis. Include the room-exit pause rule, the telehealth location rule, and refusal handling. Update the Notice of Privacy Practices and install exam room signage.

Week three: training and templates

Train every clinician on three behaviors: verbal disclosure, pausing on room exit, and line-by-line note review before signing. Load structured consent macros and specialty templates. Train medical assistants that they may not activate recording for encounters they will not attend.

Week four: audit and calibration

Pull a sample of twenty notes per clinician. Verify consent documentation, confirm no recording gaps suggest unattended capture, and check G2211 and Modifier 25 language for templated repetition. Repeat the audit quarterly and after any vendor model update.

Tennessee's statute gives clinics a clear legal footing for ambient AI. The risk lies in operational drift: unattended devices, unchecked out-of-state telehealth, and vague vendor contracts. Clinics that document the consenting party, the purpose, and the patient's response turn a one-party statute into a durable compliance position.

Frequently asked questions about AI scribing legality in Tennessee

Do Tennessee patients have to sign consent before AI scribe recording?

No signed consent is legally required. Tenn. Code Ann. § 39-13-601(b)(5) permits recording when one party, usually the treating clinician, consents. Best practice is still verbal disclosure documented in a structured note field, because disclosure defeats "secret recording" claims and supports defense in Board complaints or civil litigation.

What happens if the AI scribe records after the clinician leaves?

The one-party exception may fail because the clinician is no longer a party to the conversation. Recording a patient and family without any consenting participant risks Class D felony exposure under § 39-13-602 and civil damages of at least $10,000 under § 39-13-603. Policies should require pausing at room exit.

Does Tennessee law apply to telehealth patients in other states?

Not exclusively. When the patient sits in an all-party consent state such as California or Florida, that state's stricter rule likely applies. Record the patient's physical location before activating the scribe and obtain documented verbal consent from every out-of-state patient, or adopt universal verbal consent across all encounters.

Can coders bill Z71.89 for the AI scribe consent discussion?

No, the consent conversation is administrative and not a billable clinical service. Z71.89 should reflect genuine clinical counseling documented in the note. The disclosure also does not count toward medical decision making or total time for E/M level selection, and it never justifies G2211 or Modifier 25.

What vendor terms protect against the crime-tort exception argument?

Require a signed HIPAA business associate agreement, an explicit ban on training models with identifiable audio, a defined audio deletion window, full subprocessor disclosure, and breach notification timelines. These terms prove the recording's sole purpose is clinical documentation, defeating claims that recording served a separate tortious or commercial objective.

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Image

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.