Skip to content

CMS & Regulatory Compliance

Nevada SB 370

Nevada SB 370 Compliance for Multi-Specialty Groups

Document consent, confirm no audio retention, and map SB 370 deletion scope by specialty. Book your audit at https://cal.com/merryai/demo.

Executive Key Takeaways

  • Nevada SB 370 (NRS Chapter 603A) requires consent before collecting consumer health data and deletion responses within 45 days, while exempting HIPAA-governed PHI
  • Each encounter carries a clinician attestation of patient consent and confirmation that no audio was retained after note generation
  • Install the extension, enable the consent prompt, and map the note header field before clinical use
  • Validation via Access Clinical Prompts at templates.scribing.io
Regulatory Verification Framework
2026 Audit Ready
NRS Chapter 603A (as amended by Nevada SB 370, 2023)Verified Compliant

Consumer Health Data Consent

Affirmative consent required before collecting consumer health data, with separate signed authorization required before any sale

NRS Chapter 603A (SB 370)Verified Compliant

30-Day Deletion & Vendor Notice

Deletion from the regulated entity's records and network, notice to processors and third parties within 30 days, and consumer response within 45 days of authentication

NRS Chapter 603A (SB 370)Verified Compliant

30-Day Deletion & Vendor Notice

Exemption for protected health information governed by HIPAA, 45 CFR Parts 160 and 164

NRS Chapter 598 (SB 370 enforcement)Verified Compliant

AG Deceptive Trade Enforcement

Violations enforced by the Nevada Attorney General as deceptive trade practices, with no private right of action

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.

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.

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 DimensionManual ChartingStandard Generic AI ScribesMerry AI Compliance Architecture
Audio retentionNone recordedAudio and transcripts often archived for QA or model trainingRAM-only; buffer overwritten after note generation
Consent documentationVariable; often verbal onlyOptional or held vendor-sideConsent prompt gates capture; attestation in mapped header
SB 370 deletion surfaceEHR stores onlyEHR plus vendor archives, logs, and backupsEHR stores only; no persistent Merry audio
Processor notice (30 days)No vendor involvedVendor-side search and purge requiredNotice acknowledged; nothing stored to purge
Specialty structured criteriaDepends on the clinicianMostly narrative; discrete fields often missedNYHA, LVEF, ROM, DSM-5-TR, and Bright Futures presented for confirmation
G2211, modifier 25, modifier 59Left to coder inferenceGeneric prosePre-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.

Regulatory & Compliance FAQ

Does Nevada SB 370 apply to clinical notes generated in a multi-specialty group's EHR?

Generally, no. Signed clinical notes created by a HIPAA covered entity are protected health information under 45 CFR Parts 160 and 164, and SB 370 exempts PHI governed by HIPAA. Consumer health data outside that boundary remains within NRS Chapter 603A scope. This includes portal analytics, marketing data, and vendor telemetry not held under a business associate agreement. Groups should classify each data store before responding to any deletion request.

What deadlines govern SB 370 deletion requests and processor notification?

Once a consumer's request is authenticated, the regulated entity must respond without undue delay and no later than 45 days. Within 30 days, it must also notify each affiliate, processor, contractor, and third party that received the data. Merry AI acknowledges these notices and confirms in writing that no audio, transcript, or audio-derived embedding persists in its systems. This shortens the vendor portion of the response.

How should consent and zero audio retention be documented to satisfy Directive P1?

Each note should carry a header attestation stating that the patient consented to ambient documentation and that no audio was retained after note generation. The attestation should include a timestamp and the clinician identifier. Merry AI's consent prompt gates capture, so recording cannot begin without confirmation. The attestation supports SB 370's consent-before-collection requirement for in-scope data and gives auditors a record made at the time of the encounter.

How does SB 370 deletion interact with CMS record retention and G2211 billing?

Deletion rights do not override federal or state record retention duties. Medicare requires providers to retain documentation supporting submitted claims. NRS 629.051 generally requires Nevada providers to retain health care records for at least five years. Where deletion would conflict with these duties, the regulated entity may partially fulfill the request and should explain the basis within the 45-day window. Notes supporting G2211, modifier 25, or modifier 59 claims should be retained and tagged.

Where can clinics verify compliant templates?

Clinics can review specialty-aligned prompt templates at https://templates.scribing.io. These include header structures that carry the consent attestation and the Merry template identifier. Templates cover behavioral health DSM-5-TR specifiers, cardiology NYHA class and LVEF, orthopedic ROM degrees, and Bright Futures pediatric screening. Compliance officers should compare each template against their SB 370 data catalog and the group's internal coding policy before enabling it in production.

Explore More Knowledge

Related Clinical Rules & Compliance Guides

View all clinical rules & compliance
Illinois Eavesdropping Act: Family Medicine Scribing
CMS & Regulatory Compliance

Illinois Eavesdropping Act: Family Medicine Scribing

Capture all-party verbal consent under 720 ILCS 5/14-2 in every family medicine visit. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide
Washington MHMDA Compliance for Psychiatry Scribing
CMS & Regulatory Compliance

Washington MHMDA Compliance for Psychiatry Scribing

Separate RCW 19.373.030 consent before psychiatric recording; zero audio retention. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide
Illinois Eavesdropping Act: Multi-Specialty Compliance
CMS & Regulatory Compliance

Illinois Eavesdropping Act: Multi-Specialty Compliance

Timestamp all-party verbal consent in chart before capture; audio shreds from RAM at 0 days. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide