Statutory Scope of Nevada SB 370 for Multi-Specialty Groups
Nevada SB 370, enacted in 2023 and codified in NRS Chapter 603A, governs consumer health data that is collected, shared, or sold by regulated entities doing business in Nevada or targeting Nevada consumers. Its operative provisions took effect March 31, 2024. The statute requires consent before collection and a separate signed authorization before any sale. It grants consumers rights of access and deletion. It also prohibits geofencing within 1,750 feet of locations where in-person health care services are provided.
The scoping question comes first. SB 370 exempts protected health information governed by HIPAA under 45 CFR Parts 160 and 164. For a multi-specialty group operating as a covered entity, the signed clinical note in the EHR is ordinarily PHI and falls under federal rules. Consumer health data outside that boundary remains within SB 370 scope. Examples include patient portal analytics, marketing data, and telemetry held by vendors that are not functioning as business associates. A compliance program must classify every data store before it can answer a deletion request correctly.
Deletion obligations attach to stored data across the regulated entity's records and network. They also extend to each affiliate, processor, contractor, and third party that received the data. Regulated entities must notify processors within 30 days and respond to the consumer within 45 days of authentication. The Nevada Attorney General enforces the statute under the deceptive trade practices provisions of NRS Chapter 598. The statute does not create a private right of action.
Consent and Zero-Retention Audio Controls
Merry AI processes ambient audio in volatile memory only. Audio exists only as long as needed to generate the draft note, and then the memory buffer is overwritten. No audio file, transcript archive, or audio-derived embedding is written to persistent storage, logs, or error traces. When a deletion request arrives, Merry holds no audio artifact that needs to be located or purged.
Directive P1: Consent and Retention Attestation
Each encounter record should state two facts. First, the patient consented to ambient documentation. Second, no audio was retained after note generation. Merry AI writes this attestation into the mapped note header, with a timestamp and the clinician identifier. This supports SB 370's consent-before-collection requirement for any data in statutory scope. It also gives HIPAA and payer auditors a record made at the time of the encounter.
Zero audio retention does not remove obligations for the generated note. Several persistent stores remain: the note itself, structured fields, autosave drafts, audit trails, and downstream billing or registry feeds. Each belongs in the group's deletion catalog, classified as either PHI-exempt or SB 370-scoped.
Directive P7: Installation and Field Mapping
Deployment follows three configuration steps. First, install the Merry AI browser extension through managed enterprise browser policy. Second, enable the consent prompt so that capture cannot begin until the clinician confirms patient agreement. Third, map the note header field in each specialty template. This places the consent attestation and the Merry template identifier in a consistent, searchable location. Records staff can then use the identifier to find Merry-generated notes during any deletion, restriction, or amendment workflow.
Specialty Documentation Integrity
Multi-specialty groups face distinct criteria. Behavioral health notes require DSM-5-TR specifiers, symptom duration, and risk assessment. Cardiology notes require NYHA functional class and LVEF, with the date and modality of the study. Orthopedic notes require ROM in degrees, strength grades, and named stability tests. Pediatric notes require Bright Futures screening results and the anticipatory guidance topics discussed. Merry AI presents these elements for clinician confirmation so they are not buried in narrative prose.
Billing Alignment: G2211 and NCCI Modifiers
CMS guidance in MLN006764 confirms that G2211 may be reported with office/outpatient codes 99202-99205 and 99211-99215. It may also be reported with home or residence codes 99341, 99342, 99344, 99345, and 99347-99350. G2211 is not payable when the base E/M carries modifier 25. Since January 1, 2025, there is an exception when the same-day service is an annual wellness visit, vaccine administration, or Medicare Part B preventive service. Under the NCCI manuals, modifier 59 and its X subsets require a distinct encounter, a distinct anatomic site, or a service that is not normally bundled. Merry AI flags documentation that does not support billed modifiers before claim submission. Peer-reviewed literature on documentation integrity is indexed at https://www.ncbi.nlm.nih.gov/pmc/.
Comparative Liability and Audit Readiness
The table below contrasts three documentation models across SB 370 and CMS audit dimensions.
| Compliance Dimension | Manual Charting | Standard Generic AI Scribes | Merry AI Compliance Architecture |
|---|---|---|---|
| Audio retention | None recorded | Audio and transcripts often archived for QA or model training | RAM-only; buffer overwritten after note generation |
| Consent documentation | Variable; often verbal only | Optional or held vendor-side | Consent prompt gates capture; attestation in mapped header |
| SB 370 deletion surface | EHR stores only | EHR plus vendor archives, logs, and backups | EHR stores only; no persistent Merry audio |
| Processor notice (30 days) | No vendor involved | Vendor-side search and purge required | Notice acknowledged; nothing stored to purge |
| Specialty structured criteria | Depends on the clinician | Mostly narrative; discrete fields often missed | NYHA, LVEF, ROM, DSM-5-TR, and Bright Futures presented for confirmation |
| G2211, modifier 25, modifier 59 | Left to coder inference | Generic prose | Pre-submission flags against MLN006764 and NCCI |
Clinician attestation remains the control. Merry AI drafts the note, and the clinician reviews, edits, and signs it. Signature confirms clinical accuracy, consent status, and billing support. To confirm that consent prompts, header mappings, and your deletion catalog meet both SB 370 and CMS expectations, Schedule a 15-Minute Workflow Audit.


