Is AI Medical Scribing Legal in Montana? The 2026 All-Party Consent Playbook

Yes, AI medical scribing is legal in Montana when every party to the encounter knows the conversation is being recorded. MCA 45-8-213 prohibits...

Is AI Medical Scribing Legal in Montana? The 2026 All-Party Consent Playbook - Scribing.io

Is AI Medical Scribing Legal in Montana? The 2026 All-Party Consent Playbook

Yes, AI medical scribing is legal in Montana when every party to the encounter knows the conversation is being recorded. MCA 45-8-213 prohibits recording through a hidden device without all parties' knowledge. A documented verbal warning, captured before recording starts and stored in the chart, satisfies the statute.

Montana law permits AI scribing when every party knows recording occurs

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

Montana's controlling statute is MCA 45-8-213, titled "Privacy in communications." Subsection (1)(c) makes it an offense to knowingly record a conversation by use of a hidden electronic or mechanical device that reproduces a human conversation without the knowledge of all parties. Because the rule covers every participant, Montana is classified as an all-party state.

The statutory trigger is knowledge, not written consent. That wording differs from states such as California and Washington, which use consent language. In practice, Montana clinics should still obtain an affirmative verbal agreement. A patient who heard a warning and then objected has knowledge but has withdrawn cooperation, and continuing to record in that situation invites a privacy complaint even if a prosecutor would struggle with the statute.

The statute lists four exceptions. They cover public officials performing official duties, persons speaking at public meetings, persons given warning of the transcription or recording, and health care facilities recording emergency telephone communications. The third exception is the one AI scribing relies on. The statute also states that once one person provides the warning, either party may record.

The emergency telephone exception does not extend to exam rooms. It applies to a health care facility, as defined in MCA 50-5-101, or a government health agency recording emergency calls. An ambient scribe capturing a scheduled knee evaluation is not an emergency telephone communication, so the clinic must rely on the warning exception instead.

A first conviction carries criminal penalties. Violation is a misdemeanor punishable by a fine of up to $500, up to six months in county jail, or both, with steeper penalties for repeat convictions. The larger risk for a clinic is usually civil and regulatory: privacy tort claims, Board of Medical Examiners complaints, HIPAA investigations, and reputational harm in small communities.

Montana's constitutional privacy right exceeds the wiretap statute's requirements

Article II, Section 10 of the Montana Constitution states that the right of individual privacy is essential to a free society and shall not be infringed without a compelling state interest. Few state constitutions say this explicitly. Montana courts have read the clause broadly, and medical information sits at the center of what Montanans expect to remain private.

State v. Goetz (2008) shows how seriously Montana treats electronic capture of conversations. The Montana Supreme Court held that warrantless electronic monitoring of face-to-face conversations, even with one participant's consent, violated the state constitution. Goetz concerned government action, not private clinics. Still, the case shows Montana's judiciary regards undisclosed recording as a serious intrusion.

Medical directors should treat the statute as the minimum standard. A defensible program does more than avoid "hidden" devices. It gives clear notice, records an affirmative response, honors refusals immediately, and limits retention of raw audio. That standard holds up under criminal, constitutional, and civil review.

Do not rely on the word "hidden" as a shield. Some administrators argue that a visible phone or tablet on the counter is not a hidden device. That argument is weak. Patients rarely know a phone is running ambient capture, and a plaintiff's attorney will describe a device the patient did not understand as functionally hidden.

Montana health information law governs audio after the recording ends

The Uniform Health Care Information Act, codified at MCA 50-16-501 and following, governs how Montana providers disclose and protect health care information. Ambient audio and the transcripts derived from it are health care information once they identify a patient. Disclosure to an AI vendor must fit within the act's permitted uses, which align closely with HIPAA's treatment, payment, and operations framework.

HIPAA requires a Business Associate Agreement with every AI scribe vendor that touches protected health information. The BAA should address audio retention periods, subcontractor model hosting, de-identification, prohibitions on training models with identifiable data without authorization, and breach notification timelines. Montana clinics also face the state breach notification statute at MCA 30-14-1704 when computerized personal information is compromised.

The Montana Consumer Data Privacy Act, enacted in 2023 and amended in 2025, exempts HIPAA-covered entities and protected health information. That exemption does not cover every data element. Marketing pixels, patient portal analytics, and non-clinical voice data collected by a vendor outside the BAA can fall back under consumer privacy rules, so data maps should separate clinical audio from everything else.

Retention policy is a consent issue, not only an IT issue. Patients agree more readily when told that raw audio is deleted after the note is finalized. If your vendor keeps audio for 30 days, say so in the script and the written notice. Telling patients one thing while the vendor does another undermines the knowledge the statute requires.

A documented verbal warning satisfies Montana's knowledge standard

The warning must reach every party, not only the patient. In a typical Montana encounter that includes spouses, adult children, caregivers, medical interpreters, students, and any staff member who enters mid-visit. The statute uses "all parties to the conversation," so a family member who speaks during the visit is a party whose knowledge matters.

Step 1: Deliver a standardized pre-encounter script

Use the same words every time so training and audits stay consistent. A compliant script reads: "I use an AI documentation assistant that records our conversation to help write your visit note. The audio is used only for your medical record and deleted after the note is finalized. Is it okay with you, and with everyone here, if I turn it on?"

Step 2: Capture the response before activation

Recording should start only after the affirmative response. Best practice is to record the consent exchange itself as the first seconds of audio, then log a structured consent flag with a timestamp, the clinician's name, the parties present, and the response. A checkbox entered after the visit is weaker evidence than a timestamp created before capture began.

Step 3: Re-warn when parties change

New participants require a new warning. When a nurse, scribe trainee, or family member joins, the clinician should say a single sentence such as "Just so you know, my AI note assistant is running." Pause the device if the new participant objects. Train medical assistants to announce themselves when they enter a recording room.

Step 4: Honor refusal without friction

A refusal must stop recording immediately and must not change the quality of care. Document "Patient declined AI documentation" and proceed with manual or dictated notes. Avoid language that pressures patients, such as implying the visit will run longer. Coercive framing weakens the argument that the patient freely accepted the recording.

Step 5: Add written notice as a backup layer

Written notice supports, but does not replace, the verbal warning. Add an AI documentation paragraph to intake paperwork and post a sign in exam rooms. Written notice helps establish knowledge for companions who arrive late, and it gives the clinic a second artifact if a dispute arises months after the encounter.

Special populations need tailored consent handling

Minors, patients with limited capacity, and limited English proficiency patients need specific workflows. Obtain the warning from the legal guardian or surrogate, and from the patient when developmentally appropriate. Deliver the script through a qualified interpreter, and confirm that the interpreter, who is also a party to the conversation, has received the warning. Behavioral health and reproductive health visits often merit a default-off setting with opt-in activation.

Cross-border telehealth must follow the strictest applicable consent rule

Montana clinicians frequently treat patients located elsewhere. When a telehealth patient sits in another state, that state's recording law can apply alongside Montana's. The conservative rule is simple: apply the strictest consent standard of any state where a participant is physically located during the encounter.

Montana's neighbors use one-party rules. Idaho, Wyoming, North Dakota, and South Dakota generally permit recording with one party's consent. Montana clinics serving those patients still owe Montana-level warning because the clinician and device are in Montana. Patients in Washington, California, or Oregon trigger their own all-party or notice requirements, which may require explicit consent language.

Multistate groups should centralize the rules in one reference. The State AI Scribe Consent & Compliance Vault tracks recording consent and AI disclosure requirements by state. Groups with Texas locations should also review Texas Medical Board Rule 165.1 AI Disclosure Compliance, which addresses physician disclosure obligations that differ from wiretap rules.

Patient location must be documented at the start of each telehealth visit. Most telehealth templates already capture location for licensure purposes. Link that field to the consent workflow so the system displays the correct script automatically, rather than relying on the clinician to remember dozens of state rules.

Consent metadata must survive both payer audits and privacy complaints

Consent documentation and billing documentation fail for the same reason: missing specifics. A Montana orthopedic or primary care note produced by an AI scribe must show both a defensible recording warning and the clinical elements that support each billed code. Auditors reviewing a Modifier 25 claim will read the same note a privacy investigator would.

Consider a common Montana encounter. A 68-year-old rancher presents with worsening right knee pain from primary osteoarthritis, coded M17.11 (ICD-10-CM), and takes apixaban for atrial fibrillation, coded Z79.01 (ICD-10-CM). The physician manages the anticoagulation decision, evaluates the knee, and performs an arthrocentesis with injection (CPT 20610).

Each billed element needs distinct support. The E/M with Modifier 25 needs work beyond the procedure's inherent pre-procedure evaluation, such as anticoagulation risk assessment. G2211 needs documentation of a longitudinal relationship for the patient's serious or complex condition. NCCI edits bundle minor procedure evaluation into 20610, so vague notes lose the separate E/M.

Montana AI scribe documentation controls and audit exposure

Clinical Parameter

Documentation Requirement

Audit Vulnerability

Scribing.io DOM Mechanism

All-party recording warning (MCA 45-8-213)

Timestamped verbal warning before capture, list of parties present, affirmative response

Consent logged after visit or missing companions; privacy complaint or misdemeanor referral

Consent gate blocks audio capture until clinician logs warning, parties, and response

Mid-encounter participant change

Re-warning note when staff, interpreter, or family joins

New party unaware of recording; knowledge element fails for that participant

Participant prompt with one-tap re-warning entry and pause control

Telehealth patient location

State of patient location recorded at visit start

Wrong state script applied; out-of-state consent violation

Location field drives state-specific consent script selection

Knee OA severity (M17.11)

Laterality, range of motion in degrees, effusion, failed conservative therapy with dates

Generic "knee pain" language; medical necessity denial for 20610

Structured orthopedic exam fields extract ROM degrees and therapy history from dialogue

Anticoagulation management (Z79.01)

Agent, indication, bleeding risk discussion, hold or continue decision

E/M collapses into bundled pre-procedure evaluation under NCCI

Separate assessment block isolates anticoagulation decision from procedure note

Modifier 25 E/M

Significant, separately identifiable problem with its own MDM

Duplicated text between E/M and procedure; payer recoupment

Section-level separation flags copied text across E/M and procedure

G2211 longitudinal care

Attestation of ongoing relationship for serious or complex condition

Add-on billed without continuity evidence; post-payment review

Continuity attestation prompt linked to problem list and prior visits

Clinician attestation of AI note

Signed statement that clinician reviewed and edited AI draft

Unreviewed AI text treated as unauthenticated record

Sign-off requires review confirmation; edits logged in audit trail

Audio retention

Policy-defined deletion window matching patient disclosure

Retention exceeds what patient was told; UHCIA and HIPAA exposure

Configurable auto-deletion with deletion log tied to encounter ID

Human judgment remains the legal anchor. California SB 1120 requires that licensed physicians, not algorithms alone, make utilization review medical necessity decisions. Montana has no identical rule for scribes, but the principle carries over. The clinician, not the AI, owns the diagnosis, the code selection, and the signed record.

Specialty templates reduce documentation drift. Generic AI output often misses specialty-specific elements payers expect. Clinics can map visit types to the 1,000+ Specialty Clinical Macros so orthopedic, cardiology, and primary care notes capture required fields consistently, including laterality, measured ROM, and anticoagulant details.

Medical directors own the governance that makes consent defensible

Policy without monitoring will not protect the clinic. The medical director should approve a written AI documentation policy, designate a compliance owner, and require periodic chart sampling. Montana's small-town practice environment means one complaint can spread quickly, so prevention costs far less than remediation.

Core policy elements

  • Scope and approved tools: list each AI scribe product, version, and covered visit types.

  • Consent script and logging: mandate the standardized warning and pre-capture timestamp.

  • Refusal and pause rules: define how refusals are documented and honored.

  • Sensitive visit defaults: set opt-in only for behavioral, reproductive, and substance use care.

  • Clinician review requirement: require line-by-line review before signature.

  • Retention and deletion: match vendor configuration to patient disclosures.

  • Incident response steps: route consent failures to privacy officer within one business day.

Training and competency

Every clinician and medical assistant should complete onboarding that covers the statute, the script, re-warning triggers, and refusal handling. Use role-play for difficult scenarios such as a hesitant elderly patient or an adult child who objects for a parent. Repeat training annually and after any policy change.

Audit cadence

Sample at least ten AI-assisted encounters per clinician per quarter during the first year. Check that consent preceded capture, all parties were listed, and the signed note matches the clinical facts. Combine this review with coding audits for Modifier 25 and G2211 claims, since the same charts answer both questions.

Vendor due diligence

Ask vendors for written answers on data location, model training practices, audio retention defaults, subcontractors, SOC 2 or HITRUST status, and consent logging capabilities. A vendor that cannot block capture until consent is logged shifts all statutory risk to your clinicians' memory, which is not a defensible control.

Board and payer readiness

Keep an evidence binder ready. It should contain the policy, training records, the consent script, vendor BAA, audit results, and corrective actions. If the Montana Board of Medical Examiners, a payer, or the HHS Office for Civil Rights asks how the clinic handles AI documentation, the binder answers in minutes.

Scribing.io embeds Montana consent controls into each encounter record

The safest workflow makes noncompliance difficult. Within the Scribing.io Clinical Interface, Montana-configured clinics can require a logged warning before the microphone activates, capture the parties present, and tie consent metadata to the encounter ID. That record travels with the note into the chart.

Documentation logic reinforces billing integrity. Separate assessment blocks keep the anticoagulation decision distinct from the arthrocentesis note, structured fields prompt for ROM degrees and dated conservative therapy, and G2211 continuity prompts link to the problem list. Clinicians still review and sign every note, preserving the human accountability Montana regulators and payers expect.

Implementation should start with a pilot. Choose two clinicians, one in-person heavy and one telehealth heavy, run the consent workflow for 30 days, and audit every encounter. Fix script and workflow friction before expanding. Most clinics reach stable compliance rates within one quarter when the consent gate is enforced technically rather than by reminders.

The bottom line for Montana medical directors is straightforward. AI scribing is legal, the statute requires knowledge of all parties, the constitution expects meaningful privacy protection, and payers expect precise documentation. A pre-capture warning, structured consent log, clinician review, and disciplined retention policy satisfy all four expectations at once.

Frequently asked questions about Montana AI scribe consent

Is Montana a two-party consent state for recording patient visits?

Yes, Montana is an all-party state. MCA 45-8-213 prohibits recording conversations with a hidden device without the knowledge of all parties. Clinics using AI scribes must warn the patient and every other participant, including family and interpreters, before recording begins, then document that warning in the chart.

Does Montana require written consent for AI medical scribes?

Montana's statute requires knowledge, not a signed form. A documented verbal warning satisfies the "persons given warning" exception. Best practice adds written intake notice and exam room signage, but the core artifact is a timestamped verbal warning logged before capture, listing every party present and their affirmative response.

What penalties apply for unlawful recording in Montana clinics?

Violating MCA 45-8-213 is a misdemeanor. A first conviction carries a fine up to $500, up to six months in county jail, or both, with steeper penalties for repeat convictions. Clinics also face civil privacy claims under Montana's constitutional privacy right, HIPAA investigations, and Board of Medical Examiners complaints.

Can AI scribe notes support Modifier 25 and G2211 billing?

Yes, when the note shows separate work. Modifier 25 requires a significant, separately identifiable E/M beyond pre-procedure evaluation, such as anticoagulation management for Z79.01. G2211 requires documented longitudinal care. NCCI edits bundle generic evaluation into procedures like CPT 20610, so AI output must keep sections distinct and clinician-reviewed.

Which consent rule applies to Montana telehealth with out-of-state patients?

Apply the strictest rule of every state where a participant is located. Montana's all-party knowledge requirement applies because the clinician records from Montana. Patients in California or Washington add their own all-party consent requirements. Document patient location at visit start and select the matching consent script before recording.

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.