Michigan MCL 750.539c: Ambient Scribe Consent

1. The Statutory Foundation of MCL 750.539c for Clinical Audio

Michigan's eavesdropping statute MCL 750.539c establishes that any person who wilfully uses a device to eavesdrop upon a private conversation 'without the consent of all parties thereto,' or who knowingly aids or procures another to do so, is guilty of a felony. Read alongside the definitional section MCL 750.539a, where eavesdropping means to overhear, record, amplify, or transmit any part of the private discourse of others without the permission of all persons engaged in that discourse, the statute plainly reaches ambient clinical recording. An exam room encounter is a paradigmatic private conversation: it occurs in restricted space, carries an expectation of privacy, and involves protected health information. You can locate the interpretive literature surrounding these code sections through the National Library of Medicine's archive at https://www.ncbi.nlm.nih.gov/pmc/.

Any microphone or ambient scribe deployed in a Michigan ambulatory setting falls squarely within the statutory phrase 'device to eavesdrop.' The consequence is that the act of capturing exam-room audio, absent documented consent, can expose both the operating clinician and the deploying organization to felony liability under MCL 750.539c and to civil damages under MCL 750.539h. This is not an abstract risk; the statute expressly extends to those who procure or employ another to conduct the recording, which reaches the informatics leaders who authorize the deployment.

Because the courts have not settled whether Michigan functions as a one-party or all-party jurisdiction for participant recordings, a health system cannot responsibly rely on the more permissive reading. The prudent design collapses the ambiguity by treating every ambient clinical recording as eavesdropping that requires the consent of all parties, and then operationalizes that consent through front-loaded disclosure and an auditable consent artifact captured before any audio is recorded.

2. Where Consent Enters the Ambulatory Workflow

Within a typical Michigan ambulatory visit, consent obligations intersect four discrete workflow stages, and each stage carries its own control point. At check-in, the patient receives written or digital notice that the clinic may use ambient documentation technology and that explicit consent is required. During pre-rooming and triage, staff determine whether recording will be enabled for this provider and this encounter, and the consent gate verifies that a valid Consent resource exists before any exam-room capture is technically possible.

The provider encounter itself constitutes the private conversation protected by MCL 750.539c, so all parties present, including the patient, the clinician, any interpreter, and any accompanying family member, must be informed participants of record who understand that recording is occurring and its purpose. Post-visit, the ambient system produces a draft, the clinician attests, and the consent record must remain discoverable and auditable so the organization can demonstrate that valid consent preceded every recorded encounter.

2.1 Practical Documentation Controls

Michigan health systems typically formalize several controls to remain safely inside the statute. Disclosure is delivered at or before the start of audio capture, using both a verbal script and a written consent form that describes purpose, retention, access, and the right to decline. Patients retain an unconditional ability to refuse or revoke without any effect on the care they receive, and the system must stop recording the instant a refusal is registered. Standardized disclosure scripts and revocation-handling language are maintained in the Scribing Template Directory so every clinic uses validated wording rather than improvised phrasing.

2.2 Distinguishing Audio from Video Risk

Michigan's specific statutory hazard is audio, because MCL 750.539c and MCL 750.539a target the overhearing and recording of discourse rather than silent imaging. Some sites accordingly run video-only security capture with audio disabled except where explicit consent is documented, and ambient documentation is scoped to the acoustic channel that the eavesdropping statute governs. Isolating the audio channel as the controlled surface makes the compliance boundary far easier to defend during an investigation.

3. Software Requirements: A Consent-Driven Activation Model

The governing engineering principle is simple to state and difficult to compromise: no audio capture can occur unless a valid all-party consent record exists and is active for the current encounter and physical location. To enforce it, the ambient client performs a pre-recording authorization check that transmits the encounter identifier, patient identifier, room location, and participating provider identifiers to a backend service, which confirms that a FHIR Consent resource authorizes audio recording for exactly that context before returning an activation token.

The system is architected to fail closed. If consent is missing, expired, revoked, or scoped to a different encounter, recording does not start, and the interface states plainly that consent is required to enable ambient documentation. Real-time consent updates are pushed to the client, so if a patient revokes consent or a new participant is added, the backend revises the consent state and the client pauses or terminates capture immediately rather than waiting for the encounter to end.

3.1 Geofencing and Location Awareness

Because MCL 750.539d separately addresses the placement of recording devices in a private place without the consent of persons entitled to privacy there, location awareness is a first-class compliance requirement. Each exam and consult room is mapped to a FHIR Location resource and to its physical capture devices, and recording is permitted only when the device is in a designated private room, the current encounter is associated to that room, and the Consent resource authorizes capture for that encounter and location. Hallways and waiting rooms, where consent of all transient parties is impossible to guarantee, are disabled by default.

4. Modeling the Immutable FHIR Consent Resource

The FHIR Consent resource is the natural encoding for the operationalization of MCL 750.539c inside the EHR. The resource is scoped to patient privacy with a category indicating audio recording for documentation, names the patient as subject and the organization and specific providers as performers, and carries a permit provision constrained by time, location, encounter, and purpose of use limited to clinical documentation and care coordination rather than marketing. The participants present are enumerated explicitly so the record reflects the participant-of-record disclosure that the statute demands.

Immutability and precise timestamping convert this from a workflow nicety into an evidentiary instrument. Once a Consent is created, the original is never modified in place; revocations and mid-visit changes are represented as new versions or related deny provisions, which preserves non-repudiation. The recording start time is programmatically constrained to fall after the consent timestamp, and each capture event generates an AuditEvent referencing the Consent resource identifier and version, so the organization can show that for encounter X at time T, capture began only because consent C was recorded at an earlier time.

4.1 Mapping Merry AI's Geofenced Consent Gate

Merry AI decomposes the anchor requirement into a geofenced gate that will only activate ambient capture in a designated private room after it identifies the location, encounter, and patient, queries for an active Consent resource, presents a consent workflow if none exists, and captures the resulting immutable, timestamped FHIR Consent write-back before any microphone opens. This directly implements the 'before recording begins' expectation that Michigan compliance guidance places at the center of lawful monitoring. If you want to see the gate exercised against your own room map and EHR, Book a 15-Minute Workflow Audit.

5. Governance, Attestation, and Defensible Compliance

Beyond the statute, Michigan health systems formalize ambient recording through written risk-management policy that cites MCL 750.539c, 750.539a, and 750.539d, staff training that forbids activation without confirmed consent, and vendor contracts and business associate agreements requiring the ambient vendor to implement consent gating, provide audit logging, and limit data use to agreed clinical purposes. Privacy and security review boards prioritize opt-in designs over implied consent, and they look for precisely the encoded, queryable consent artifact described above.

Physician attestation closes the compliance loop and connects it to reimbursement integrity. The ambient system drafts, but the note is not part of the legal record until the rendering clinician reviews, edits, and signs it, writing back a signed Provenance and attestation timestamp. This is essential when the encounter supports the CPT G2211 add-on for a continuing focal point of care or the ongoing management of a serious or complex condition, because the attesting clinician, not the software, must defend that complexity-capture decision in an audit.

The following table contrasts three approaches to Michigan ambulatory documentation so the compliance delta is explicit.

Taken together, these controls demonstrate that while MCL 750.539c never uses the phrases 'geofenced consent gate' or 'FHIR Consent write-back,' the statute's core prohibition against eavesdropping on a private conversation without the consent of all parties is faithfully implemented by explicit participant-of-record disclosure, consent captured before recording begins, geofenced restriction to private clinical spaces, and an immutable, timestamped consent artifact the health system can audit and defend. That is the clinically and legally rigorous implementation pattern Michigan ambulatory and health-system documentation workflows should adopt.