Original research · Dataset
Ambient recording consent index
Consent regime for recording a private conversation across 51 US jurisdictions, mapped to what an ambient documentation product must actually do.
Short answer
Do ambient AI scribes need all-party consent?
10 of 51 US jurisdictions require all-party consent to record a private conversation, and 5 more are unsettled enough that prudent products treat them the same way. Because a single national default cannot satisfy both regimes, a defensible ambient scribe captures consent from every participant, records the jurisdiction and wording used, and can prove it later.
Cite as: Ambient recording consent index, Compare Healthcare API, last reviewed 2026-09-01.
Key findings
- 10 jurisdictions require all-party consent outright and a further 5 are contested enough that a multi-state product should treat them as all-party. That is 15 of 51 — roughly a third of the US map — where a single global "recording is on" setting is not defensible.
- The practical consequence is a product requirement, not a policy page: per-encounter consent capture, stored with a timestamp, the consenting party, the jurisdiction and the wording shown, and a hard block on capture when consent is absent.
- Because the strictest applicable rule wins, most multi-state products should default to all-party consent everywhere. It is cheaper to build one compliant flow than fifty-one conditional ones.
- Consent is separate from HIPAA. HIPAA governs what you may do with PHI once you hold it; state wiretap law governs whether you were permitted to record in the first place. A signed BAA does not cure a recording made without required consent.
The index
Jurisdiction by jurisdiction, with the product implication rather than the statute text.
| Jurisdiction | Regime | Notes |
|---|---|---|
| Alabama | One-party | One participant's consent suffices under the general statute. |
| Alaska | One-party | One-party consent. |
| Arizona | One-party | One-party consent. |
| Arkansas | One-party | One-party consent. |
| California | All-party | All parties must consent to recording a confidential communication. Treat clinical encounters as confidential by default. |
| Colorado | One-party | One-party consent. |
| Connecticut | Contested | One-party for criminal liability; a civil statute creates all-party exposure for recording telephonic conversations. Design for all-party. |
| Delaware | All-party | Statutory language supports an all-party requirement. |
| Florida | All-party | All parties must consent to interception of an oral communication. |
| Georgia | One-party | One-party consent. |
| Hawaii | One-party | One-party consent. |
| Idaho | One-party | One-party consent. |
| Illinois | All-party | All-party consent for private conversations. |
| Indiana | One-party | One-party consent. |
| Iowa | One-party | One-party consent. |
| Kansas | One-party | One-party consent. |
| Kentucky | One-party | One-party consent. |
| Louisiana | One-party | One-party consent. |
| Maine | One-party | One-party consent. |
| Maryland | All-party | All-party consent required. |
| Massachusetts | All-party | Strict: secret recording is prohibited outright. |
| Michigan | Contested | Statute reads all-party; case law has been read to permit participant recording. Design for all-party. |
| Minnesota | One-party | One-party consent. |
| Mississippi | One-party | One-party consent. |
| Missouri | One-party | One-party consent. |
| Montana | All-party | All parties must be notified. |
| Nebraska | One-party | One-party consent. |
| Nevada | Contested | One-party in person; case law has been read to require all-party for telephone. Design for all-party. |
| New Hampshire | All-party | All-party consent required. |
| New Jersey | One-party | One-party consent. |
| New Mexico | One-party | One-party consent. |
| New York | One-party | One-party consent. |
| North Carolina | One-party | One-party consent. |
| North Dakota | One-party | One-party consent. |
| Ohio | One-party | One-party consent. |
| Oklahoma | One-party | One-party consent. |
| Oregon | Contested | One-party for telephone; in-person conversations generally require notifying all participants. Design for all-party. |
| Pennsylvania | All-party | All-party consent required. |
| Rhode Island | One-party | One-party consent. |
| South Carolina | One-party | One-party consent. |
| South Dakota | One-party | One-party consent. |
| Tennessee | One-party | One-party consent. |
| Texas | One-party | One-party consent. |
| Utah | One-party | One-party consent. |
| Vermont | Contested | No general statute; case law disfavours surreptitious recording in private settings. |
| Virginia | One-party | One-party consent. |
| Washington | All-party | All-party consent required for private communications. |
| West Virginia | One-party | One-party consent. |
| Wisconsin | One-party | One-party consent. |
| Wyoming | One-party | One-party consent. |
| District of Columbia | One-party | One-party consent. |
What this means for your product
Consent is a feature with a data model, not a line in a privacy policy.
- Capture consent per encounter and per participant, not once per patient account.
- Record jurisdiction, timestamp, disclosure wording version and who obtained it.
- Make refusal a first-class path: the encounter must proceed with documentation unrecorded.
- For telehealth across jurisdictions, apply the stricter rule by default.
- Retain the consent record at least as long as the audio, transcript or note it covers.
- Expose the record to your customers, since their audits become your obligations.
Evidence & sources
Federal privacy and professional-guidance references. Jurisdiction-level classifications derive from each state's own publicly published statutes as of the compile date.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: What a covered entity and its business associates may do with PHI, and why a signed BAA is a precondition rather than a feature.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: Administrative, physical and technical safeguards a vendor handling recorded encounter audio must implement.
American Medical Association · Research · Tier B — published methodology
Supports: Professional expectations for oversight and transparency of AI-generated clinical content.
Centers for Medicare & Medicaid Services · Regulation · Tier A — primary documentation
Supports: Authentication and attestation requirements that make clinician review of an AI-generated note non-optional.
Source tiers are defined on the methodology page. Outbound links are unaffiliated and carry no commercial relationship.
Frequently asked questions
- Do I need patient consent to record a clinical encounter?
- Practically, yes. 10 US jurisdictions require all-party consent to record a private conversation and 5 more are contested enough to treat identically, so a defensible ambient product captures consent everywhere and records that it did.
- What is the difference between one-party and all-party consent?
- One-party consent requires only one participant — typically the clinician — to consent to the recording. All-party consent requires every participant, including the patient and anyone else in the room or on the call.
- Which rule applies to a telehealth visit across state lines?
- Potentially both. When participants are in different jurisdictions, the conservative and common approach is to apply the stricter rule, which in practice means capturing all-party consent for every recorded telehealth encounter.
- Is a consent checkbox enough?
- A checkbox with no audit record is weak evidence. Capture who consented, when, in what jurisdiction, and under which disclosure wording, and retain that record for as long as the audio or note exists. Compliance checklist.