Statutory Compliance Architecture for the Illinois Eavesdropping Act
Multi-specialty practices in Illinois operate under one of the strictest recording regimes in the country. Article 14 of the Criminal Code, codified at 720 ILCS 5/14-1 through 14-9, regulates the act of capturing a private conversation, not merely how long a recording is kept. For ambient documentation, that distinction defines the compliance posture: retention controls cannot cure consent that was never obtained.
The exposure is criminal, not administrative. Under 720 ILCS 5/14-4, a first violation of Section 14-2 is a Class 4 felony, and a subsequent violation is a Class 3 felony. Section 14-6 separately grants any aggrieved party a civil action for actual and punitive damages and injunctive relief.
All-Party Consent Under 720 ILCS 5/14-2
Section 14-2(a)(1) prohibits knowingly and intentionally using an eavesdropping device in a surreptitious manner to record all or any part of a private conversation without the consent of all parties. Section 14-1 defines a private conversation as one in which at least one party reasonably expects privacy, which describes nearly every exam-room exchange.
Being the treating clinician does not satisfy the all-party requirement. Every audible participant—patient, parent or guardian, interpreter, family member, resident, student, or chaperone—must consent before capture begins. Directive P1 therefore governs the first moment of every encounter: confirm and timestamp verbal consent from every person present before the microphone opens, and reconfirm whenever someone new enters the room.
Consent Gate and EHR Field Architecture
Merry AI enforces Article 14 at the software layer rather than relying on clinician memory. Directive P7 defines a three-step deployment: install the browser extension, enable the consent gate, and map the History of Present Illness (HPI) field in the EHR note. Until the gate is satisfied, the audio pipeline and DOM injection remain disabled.
When the clinician confirms consent, Merry writes an attestation directly into the encounter note: an ISO 8601 timestamp, the consent method, the encounter identifier, and the names and roles of all audible participants. Because the artifact lives in the legal medical record rather than a vendor log, an auditor or court can verify that consent preceded capture.
Chart Container Validation and Multi-Tab Safeguards
Multi-specialty clinicians routinely keep several charts open across tabs, iframes, and split-pane layouts. Merry binds capture state to a validated chart container by reading the active patient header and chart identifiers. If the header changes or another tab gains focus, capture pauses and injection is refused until consent is reconfirmed, preventing cross-patient contamination.
Audio is processed only in volatile RAM and zeroized at session end with 0-day retention. No audio file, transcript cache, speaker embedding, or voiceprint persists, so no recording exists to subpoena. This posture also limits exposure under the Biometric Information Privacy Act, 740 ILCS 14, where Merry collects written biometric consent with electronic signature consistent with Public Act 103-0769.
Specialty Documentation Within a Consent-Gated Encounter
Each specialty brings its own documentation framework, and the consent artifact must sit alongside each one. Behavioral health notes capture DSM-5-TR criteria, duration, functional impairment, and suicide risk assessment. Cardiology requires NYHA functional class, LVEF, and guideline-directed medical therapy. Orthopedics depends on ROM degrees, laterality, and provocative tests such as Lachman and McMurray. Pediatrics follows Bright Futures screening and immunization counseling.
Pediatric and interpreter-mediated visits carry the highest participant counts. A well-child visit may include two parents, a sibling, and a trainee; a behavioral health intake may include a certified interpreter. Each voice is a party to the private conversation, and each name belongs in the attestation before ambient capture starts.
CMS Billing Integrity: G2211 and Modifiers 25/59
HCPCS add-on code G2211 requires documentation of care that serves as the continuing focal point for needed services or ongoing care for a single serious or complex condition. Ambient notes must surface that longitudinal complexity explicitly. Modifier 25 requires a significant, separately identifiable E/M service, and Modifier 59 requires a distinct procedural service; both demand clearly separated narrative blocks.
Consent attestation strengthens billing defensibility. CMS documentation integrity guidance emphasizes patient identification, authorship validation, and audit trails. An encounter identifier and timestamped participant list in the same note give reviewers a coherent provenance chain from lawful capture to signed claim. Peer-reviewed informatics consensus on EHR documentation is indexed at https://www.ncbi.nlm.nih.gov/pmc/.
Comparative Liability and Audit Readiness
The table below contrasts three documentation models against Article 14 and BIPA exposure points.
| Compliance Dimension | Manual Charting | Standard Generic AI Scribes | Merry AI Compliance Architecture |
|---|---|---|---|
| All-party consent (14-2) | No device used | Often verbal, undocumented | Gate blocks capture until attested |
| Consent evidence | Not applicable | Vendor log outside chart | ISO 8601 attestation in note |
| Audio retention | None | Days to indefinite | RAM-only, 0-day |
| Multi-tab safety | Not applicable | Variable | Pauses on header or tab change |
| BIPA (740 ILCS 14) | Not implicated | Training reuse risk | No voiceprints; written consent |
Generic scribes typically rely on BAA assurances and vendor-side consent logs while retaining audio or transcripts for quality review or model training. Under Article 14, a stored file magnifies exposure because it can be forensically reviewed to determine whether consent preceded clinical content.
Clinician attestation remains the final safeguard. Every AI-drafted note requires review and signature by the treating clinician, who confirms clinical accuracy, code selection, and the completeness of the participant list. When any party declines, the encounter proceeds with manual charting and no audio is processed.
Practice leaders preparing for audit should verify consent-gate configuration, HPI field mapping, and tab-switch behavior across each specialty template. Schedule a 15-Minute Workflow Audit to review your deployment against 720 ILCS 5/14-2 and 740 ILCS 14.


