AI Scribe Consent Form: Patient Consent Template, Two-Party Recording Laws, HIPAA Disclosures, and EHR Workflows

An AI scribe consent form is a standardized clinical and legal disclosure document (or structured verbal consent attestation) used by hospitals, ambulatory medical groups, and telehealth practices to obtain a patient’s informed permission before using an ambient clinical intelligence (ACI) or AI medical scribe system to listen to, transcribe, and summarize a medical encounter. While the federal HIPAA Privacy Rule permits covered entities to use Business Associate software for treatment and health care operations under 45 CFR § 164.506 without a separate written HIPAA authorization, state wiretapping and electronic eavesdropping statutes, state-level healthcare AI transparency laws, and institutional medical-legal risk management policies require explicit patient notification and consent before activating microphone capture in an exam room or virtual visit.

Why HIPAA Alone Is Not Enough: One-Party vs. All-Party (Two-Party) Recording Laws

Health system compliance officers designing AI clinical documentation workflows must reconcile two distinct legal frameworks:

1. Federal HIPAA Privacy Rule (45 CFR § 164.506 & § 164.520): Under HIPAA, generating a clinical progress note is a core Treatment and Health Care Operations (TPO) activity. Provided the health system has executed a valid HIPAA Business Associate Agreement (BAA) with the AI scribe vendor, prohibited the vendor from using Protected Health Information (PHI) to train commercial foundation models without de-identification under 45 CFR § 164.514, and updated its Notice of Privacy Practices (45 CFR § 164.520), HIPAA itself does not mandate a separate signed authorization form for routine progress notes (with heightened exceptions for 45 CFR § 164.508(a)(2) psychotherapy notes and 42 CFR Part 2 substance use disorder records).
2. State Wiretapping and All-Party Audio Recording Statutes: Audio recording of a confidential in-person or telehealth conversation is governed by state wiretapping and privacy statutes. While federal law (18 U.S.C. § 2511(2)(d)) and roughly three dozen states follow a one-party consent rule (where the clinician’s own participation legally suffices under wiretapping law), at least 11 to 13 U.S. jurisdictions enforce strict all-party (two-party) consent statutes—including California (Cal. Penal Code § 632), Florida (Fla. Stat. § 934.03), Illinois (720 ILCS 5/14-2), Maryland, Massachusetts, Michigan, Montana, New Hampshire, Oregon (for in-person conversations), Pennsylvania (18 Pa.C.S. § 5703), and Washington (RCW 9.73.030). In all-party consent states, recording a confidential conversation between a physician, patient, and accompanying family member without the consent of every participant present can constitute a misdemeanor or felony and trigger statutory civil damages.

What Should Be Included in an AI Scribe Consent Form?

To satisfy state recording statutes, American Medical Association (AMA) augmented intelligence transparency principles, and malpractice carrier guidelines, a comprehensive AI scribe consent form must include seven core elements:

Required Consent Section	Clinical & Legal Disclosure Purpose	Specific Technical & Regulatory Facts to State
1. Purpose of Ambient AI Documentation	Explains what the tool is and why the clinician is using it	Clarifies that the ambient AI assistant listens to the conversation solely to draft the clinical visit note so the clinician can focus directly on the patient rather than typing
2. Scope of Audio Capture & Third Parties	Addresses state all-party wiretapping laws for everyone in the room	Notifies the patient (and any accompanying family member, spouse, parent, or caregiver in the exam room or video call) that their spoken conversation will be processed during the visit
3. Ephemeral Audio Deletion (No Permanent Recording)	Alleviates patient surveillance concerns and defines the Designated Record Set	States clearly that audio is processed transiently to generate a draft clinical note and that raw audio files are automatically deleted after note completion (not stored in the permanent medical chart)
4. HIPAA Encryption & No Commercial Model Training	Confirms HIPAA Security Rule (45 CFR § 164.312) and BAA boundaries	Confirms that data transmission is encrypted under a HIPAA Business Associate Agreement and that identifiable patient audio/text is never sold or used to train public AI models
5. Mandatory Human Clinician Review & Sign-Off	Prevents misconception that AI is making autonomous medical decisions	States that the AI tool does not diagnose or prescribe autonomously; the licensed clinician reviews, edits, and verifies the accuracy of the note before signing it into the EHR
6. Right to Decline or Pause Without Penalty	Protects patient autonomy and sensitive topic disclosure	Affirms that consent is completely voluntary: the patient may decline before the visit or ask the clinician to pause/stop recording at any moment during the exam without affecting their medical care
7. Patient / Legal Representative Signature or Verbal Attestation	Creates an auditable timestamped record in the EHR	Captures patient name, date of birth, signature (or portal e-signature), date/time, and relationship of legal guardian/representative if applicable

Reusable AI Scribe Patient Consent Form Template (Written Intake & Verbal Script)

Health systems typically combine a written consent clause inside their pre-visit HIPAA-compliant intake forms or patient registration forms with a brief verbal confirmation at the start of each encounter.

1. Written Patient Consent Form Template (Pre-Visit Portal / Check-In Kiosk)

CONSENT FOR USE OF AMBIENT AI CLINICAL DOCUMENTATION ASSISTANT

1. How Ambient Documentation Works: During your medical visit (in-person or telehealth), your healthcare provider may use a secure, HIPAA-compliant Artificial Intelligence (AI) documentation assistant (“AI Scribe”). This tool listens to the conversation between you and your provider using a secure mobile device or workstation microphone in order to draft a clinical summary of your visit for your Electronic Health Record (EHR). This allows your provider to give you their undivided attention rather than typing on a computer during your appointment.

2. Audio Privacy and Automatic Deletion: Your conversation is transmitted over encrypted channels governed by a federal HIPAA Business Associate Agreement (BAA). The audio is processed temporarily to create a draft clinical note for your provider and is automatically deleted once the note is finalized. Raw audio recordings are not saved as part of your permanent medical record, and your identifiable health information is not sold or used to train public AI models.

3. Provider Review and Clinical Decisions: The AI Scribe is a documentation tool only; it does not make medical decisions. Your licensed healthcare provider personally reviews, edits, and approves every word of the clinical note before signing it into your medical chart.

4. Accompanying Family Members or Caregivers: If a family member, caregiver, or other guest joins you in the exam room or telehealth session, your consent confirms that all participants present are aware of and agree to the use of the AI documentation assistant during the visit.

5. Your Right to Decline or Stop at Any Time: Your consent is completely voluntary. You may choose not to allow the AI Scribe, or you may ask your provider to pause or turn off the tool at any point during your visit (for example, when discussing a sensitive personal matter). Declining or revoking consent will never affect your access to care or the quality of treatment you receive.

☐ I CONSENT to the use of the Ambient AI Clinical Documentation Assistant during my clinical encounters.
☐ I DO NOT CONSENT to the use of the Ambient AI Clinical Documentation Assistant.

Patient Name: ___________________________   Date of Birth: ____/____/______
Signature of Patient or Legal Representative: ___________________________   Date/Time: ____________
If signed by Representative, Relationship to Patient: ___________________________

2. Point-of-Care Verbal Consent Script & EHR Dot-Phrase Attestation

Even when a patient has signed a general annual intake consent, clinical governance policies recommend a 15-second verbal confirmation before tapping “Record” in the exam room:

• Clinician Verbal Script: “To make sure I can focus completely on you today instead of typing, I’d like to use our secure medical AI scribe on my phone to help draft my clinical note. It encrypts the audio, deletes the recording after the note is written, and I review everything myself. We can pause or turn it off anytime. Is it okay with you [and your guest] if I turn that on now?”
• EHR Note Attestation Footer (.aiscribeconsent): “Verbal informed consent for use of HIPAA-compliant ambient AI clinical documentation was obtained from the patient (and all accompanying individuals present) prior to initiating audio capture. This clinical note was generated with ambient AI assistance and was personally reviewed, edited, and verified for clinical accuracy by the signing provider.”

How Is an AI Scribe Consent Form Structured in EHR Workflows and HL7 FHIR?

In enterprise EHR architectures (such as Epic, Oracle Health, and athenaOne), AI scribe consent is tracked as a discrete, machine-readable data element rather than an unindexed scanned PDF:

1. Pre-Visit Digital Check-In (FHIR QuestionnaireResponse): During MyChart or mobile eCheck-In, the patient completes the AI scribe consent item. Their selection writes a discrete patient-level FYI flag or document status in the EHR header.
2. HL7 FHIR R4 Consent Resource Representation: Interoperable EHRs represent the signed directive using an HL7 FHIR R4 Consent resource where status = "active", scope = "adr" or "patient-privacy", category identifies ambient documentation recording, patient references the Patient resource, dateTime logs the exact timestamp of execution, and provision.type = "permit" (or "deny" if the patient opted out).
3. Hard-Stop Mobile App Gatekeeping: Native ambient mobile apps (such as Epic Haiku Ambient Module) display an explicit on-screen consent toggle or check the patient’s FHIR Consent status before enabling the microphone stream—preventing accidental recording when a patient has an active opt-out on file.

Frequently Asked Questions

What should be included in an AI scribe consent form?

An AI scribe consent form should state: (1) the purpose of the ambient AI tool (drafting clinical notes during the conversation); (2) that all parties present in the exam room or telehealth session are included; (3) how audio is encrypted and automatically deleted after note generation (ephemeral processing); (4) that identifiable patient data are protected under a HIPAA BAA and not used to train public AI models; (5) that a human clinician reviews, edits, and signs the final note; and (6) that the patient can decline or ask to pause recording at any time without affecting their care.

How is an AI scribe consent form structured in EHR workflows?

Health systems operationalize AI scribe consent across two layers: (1) a written electronic signature captured during pre-visit portal check-in or annual registration (stored as a discrete EHR flag or HL7 FHIR R4 Consent resource), paired with (2) an encounter-level verbal confirmation checkbox in the clinician’s mobile recording app that automatically appends a standardized consent and human-review attestation statement to the bottom of the signed progress note.

Is written patient consent legally required for an AI medical scribe?

Under federal HIPAA rules (45 CFR § 164.506), clinical documentation is a treatment/operations activity covered by a Business Associate Agreement, so HIPAA alone does not mandate a separate signed authorization for standard progress notes. However, in the 11 to 13 U.S. states with all-party (two-party) audio recording laws—and under emerging state healthcare AI disclosure statutes—explicit patient (and third-party guest) consent is legally required before capturing audio, making documented written and/or verbal consent a universal clinical compliance standard.