Statutory Scope of Washington MHMDA for Telehealth and Wellness
Washington's My Health My Data Act is codified at RCW 19.373. It regulates any entity that conducts business in Washington, or targets Washington consumers, and collects, processes, shares, or sells consumer health data. Its reach is deliberately wider than HIPAA. Direct-to-consumer telehealth platforms, behavioral coaching services, symptom trackers, and wellness programs operating outside a covered-entity relationship all fall within it. Obligations took effect March 31, 2024 for regulated entities and June 30, 2024 for small businesses.
Protected health information governed by HIPAA is exempted under RCW 19.373.100. That exemption attaches to the data, not to the organization. Consider a hybrid practice that runs a HIPAA-covered telehealth clinic alongside a cash-pay wellness program. It must treat the wellness data stream as MHMDA-regulated, and any ambient documentation tool moving between both contexts inherits that split obligation.
Consumer Health Data Under RCW 19.373.010
The statutory definition is deliberately broad. Consumer health data includes personal information that identifies a consumer's past, present, or future physical or mental health status, including inferences derived from nonhealth data. Encounter audio, transcripts, coaching notes, wellness assessments, and the draft note an ambient scribe generates all qualify. Even audio held for seconds in memory constitutes collection and processing, which is why consent must precede capture rather than follow it.
Consent Before Ambient Capture: The P1 Mandate
RCW 19.373.030 requires consent for collection that is separate from consent for sharing. Consent must be freely given, specific, informed, and unambiguous; general terms of use and pre-checked boxes do not qualify. The statute does permit collection necessary to provide a requested service. Ambient capture, however, is a documentation method rather than the service the patient requested. Affirmative consent recorded before capture is therefore the conservative and defensible posture.
Merry enforces this sequence architecturally. The capture control remains disabled until the clinician confirms that the patient has consented to collection of consumer health data for the current encounter. Audio is then processed in volatile RAM and shredded at zero days. Nothing is written to disk or cloud storage, so no corpus exists to retain, breach, or subpoena.
Because Merry never sells or shares consumer health data, its processing does not trigger the sharing consent of RCW 19.373.030. It also does not trigger the valid authorization regime of RCW 19.373.070, which requires a signed authorization retained six years by seller and purchaser. Downstream processors act only under RCW 19.373.060 contracts that prohibit secondary use, model training, or resale.
Encounter-Level Consent in the Note Header
Platform-level consent captured once in an intake portal is difficult to tie to a specific encounter during an Attorney General inquiry or litigation. Merry instead writes consent text into the note header for every encounter, for example: 'Patient consented to collection of consumer health data for ambient documentation; audio processed in volatile memory and not retained.' The attestation lives in the legal medical record and can be reviewed without querying a separate consent system.
Clinician attestation remains the final safeguard. The clinician reviews, edits, and signs every note. Merry suggests structure for DSM-5-TR criteria, NYHA class and LVEF, range of motion in degrees, and Bright Futures domains. It never assigns diagnoses, G2211, or modifiers 25 and 59. Those determinations stay with the clinician and the billing workflow, consistent with NCCI expectations for significant, separately identifiable services.
Deployment Protocol: The P7 Configuration Sequence
Implementation follows three ordered steps. First, install the Merry browser extension and restrict it to an allowlist of EHR and telehealth hostnames. Second, enable the consent banner, which blocks capture until consent is confirmed and timestamps that confirmation. Third, map the note header field so consent text lands in the correct chart location for every encounter.
DOM Targeting, iframes, and Multi-Tab Charting
Header mapping uses allowlisted selectors such as textarea[name='clinicalNote'], div[contenteditable='true'], or rich-text containers like .ProseMirror and .ql-editor. Insertion is idempotent: the extension checks for an existing header before writing, which prevents duplication when the script reloads. Manual edits are preserved, because content is appended or merged rather than overwritten.
Embedded charting frames require explicit handling. The extension injects only into allowlisted frames, such as iframe[id='encNoteFrame'], and logs the target selector and URL for each write to support forensic review. In tabbed EHRs, Merry reads active tab state through aria-selected='true' and binds content to the encounter identifier. It pauses capture on tab change, so documentation cannot land in an inbox message or billing note.
Statutory Comparison and Audit Defensibility
The table below contrasts three documentation postures against core MHMDA obligations.
| Compliance Dimension | Manual Charting | Standard Generic AI Scribes | Merry AI Compliance Architecture |
|---|---|---|---|
| Consent timing (RCW 19.373.030) | No ambient capture | Often platform-level or post-hoc | Affirmative consent recorded before capture |
| Audio retention | None | Persistent audio or transcripts common | Volatile RAM only; shredded at 0 days |
| Sharing and sale (RCW 19.373.070) | Minimal exposure | Vendor model training may resemble sharing | Never sold or shared; processor-only contracts |
| Deletion (RCW 19.373.040) | Chart-level only | Audio, transcripts, and backups to purge | No audio corpus; note-level workflow only |
| Encounter auditability | Clinician narrative | Separate consent system | Consent persisted in note header |
| Specialty criteria | Clinician-dependent | Generic summaries | Structured prompts; clinician confirms |
Deletion requests under RCW 19.373.040 must be answered within 45 days, extendable once by 45 days, and deletion extends to processors and archives. Because Merry retains no audio, a request reduces to note text and metadata in the EHR. Those records should be evaluated against the clinic's medical record retention duties. Clinics should also publish a consumer health data privacy policy under RCW 19.373.020 that matches actual system behavior.
Enforcement runs through the Washington Consumer Protection Act, RCW 19.86, which includes a private right of action. That makes documented consent a litigation asset rather than an administrative formality. Peer-reviewed literature on ambient documentation and patient consent is indexed at https://www.ncbi.nlm.nih.gov/pmc/.
Clinics preparing for regulatory review can Schedule a 15-Minute Workflow Audit. The audit validates extension allowlists, consent banner behavior, and note header mapping against RCW 19.373 before the next Washington encounter.


