Washington My Health My Data Act Compliance: Requirements and Checklist
Washington’s My Health My Data Act (MHMDA), Chapter 19.373 RCW, regulates consumer health data beyond the information covered by some other privacy laws. If your organization does business in Washington or targets Washington consumers and determines why or how their health data is processed, use this guide to assess your coverage, consent practices, consumer-request process, vendor contracts, and safeguards.
Which organizations and data fall under the Act?
The Act generally applies to a legal entity that conducts business in Washington or targets consumers in the state and determines the purposes and means of collecting, processing, sharing, or selling consumer health data. It covers Washington residents and people whose consumer health data is collected in Washington in an individual or household context; it does not cover an individual acting in an employment context. The Act’s definitions in RCW 19.373.010 explain who is a regulated entity and consumer.
Consumer health data is personal information linked or reasonably linkable to a consumer that identifies the person’s past, present, or future physical or mental health status. Examples include diagnoses, treatment, medication use, reproductive or sexual health information, gender-affirming care, biometric or genetic data, and precise location that could reasonably indicate an attempt to obtain health services or supplies. The definition also includes certain health-related inferences derived from nonhealth information.
Some information and activities are excluded or exempt, including specified HIPAA-protected information, certain Washington health care information, and data governed by listed federal or state laws. These are data-specific exemptions; being a health care provider or handling some HIPAA-protected information does not by itself establish that every data set or activity is outside the Act. Review the exact conditions in RCW 19.373.100.
The Act defines a “small business” using consumer-volume and revenue thresholds. Small businesses are covered, but many duties had a later compliance date for them. Do not treat the label as a blanket exemption.
What must a consumer health data privacy policy disclose?
Your consumer health data privacy policy must clearly and conspicuously describe the categories of consumer health data you collect and why, including how you use it; the categories of sources; the categories of data you share; and the categories of third parties and specific affiliates with whom you share it. It must also explain how a consumer can exercise the rights provided by the Act. Publish a prominent link to the policy on your homepage, as required by RCW 19.373.020.
Keep the policy consistent with actual data practices and processor instructions. If you plan to collect, use, or share a new category of consumer health data, or use data for a new purpose, disclose the change and obtain the consumer’s affirmative consent before proceeding. A broad or vague policy statement is not a substitute for required consent.
As a practical checklist, map each data category to its source, purpose, use, and recipients; identify affiliates specifically; and provide clear instructions for access, withdrawal, and deletion requests. Update the policy and related notices when those practices change.
When is consent required for collection and sharing?
Unless an exception applies, obtain the consumer’s consent before collecting consumer health data for a specified purpose. For sharing, obtain a separate and distinct consent from the collection consent. The Act allows collection or sharing to the extent necessary to provide a product or service that the consumer requested. Evaluate that exception narrowly against the actual service requested and the data use at issue; it is not general permission for unrelated processing.
Consent must be a clear affirmative act showing freely given, specific, informed, opt-in, voluntary, and unambiguous agreement. The request must clearly and conspicuously state the data categories, purpose and specific uses, categories of entities with whom the data will be shared, and how the consumer can withdraw consent. A general terms-of-use agreement, deceptive design, or passive interaction such as hovering over or closing content does not qualify as consent under the Act. See RCW 19.373.010 and RCW 19.373.030.
Document the consent flow and preserve records showing what notice the consumer saw, what action they took, and when consent was given or withdrawn. Do not unlawfully discriminate against consumers for exercising their rights.
How should organizations handle consumer rights and deletion requests?
Consumers may ask whether you collect, share, or sell their health data and request access to it. An access response must include a list of third parties and affiliates with whom you shared or sold the data, along with an active email address or other online contact mechanism for those entities. Consumers may also withdraw consent for future collection and sharing and request deletion.
Set up a secure and reliable request method that reflects how consumers normally interact with your organization, describe it in the privacy policy, and authenticate requests using commercially reasonable efforts. You cannot require a consumer to create a new account, though you may require use of an existing account. Provide responses free of charge up to twice per year; fees or refusal are permitted only for requests that are manifestly unfounded, excessive, or repetitive, and your organization bears the burden of showing that basis.
Respond without undue delay and within 45 days of receiving a request. You may extend the response period once by up to 45 additional days when reasonably necessary because of the complexity or number of requests, but you must notify the consumer within the initial 45 days and explain why. The same 45-day response period applies to an appeal of a refusal, which must include a written explanation and, if denied, a way to contact the attorney general. The timelines and duties appear in RCW 19.373.040.
For a deletion request, delete the data from your records and notify affiliates, processors, contractors, and other third parties with whom you shared it. Those recipients must honor the request. Deletion from archived or backup systems may be delayed when necessary to enable restoration, but that delay may not exceed six months from authentication of the request.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhat authorization is required to sell consumer health data?
Before selling or offering to sell a consumer’s health data, obtain a separate consumer health data sale authorization. This is distinct from consent to collect or share data. The authorization must be a plain-language document signed and dated by the consumer and must identify the specific data to be sold, the seller and purchaser with their contact information, and the purpose of the sale, including how the purchaser will gather and use the data.
It must also state that goods or services are not conditioned on signing, explain the consumer’s right to revoke the authorization and how to do so, warn that the purchaser may redisclose the data and that it may no longer be protected by the Act, and include an expiration date one year from the date of signature. Give the consumer a copy. An authorization is invalid if required information is missing, it has expired or been revoked, it is combined into a compound authorization, or a service is conditioned on signing.
Both the seller and purchaser must retain a copy of each valid authorization for six years from signature or from the date it was last in effect, whichever is later. See RCW 19.373.070 for the complete requirements.
What processor, recipient, and geofencing restrictions apply?
A processor may handle consumer health data only under a binding contract with the regulated entity or small business. The contract must set processing instructions and limit what the processor may do with the data; the processor must follow those instructions and assist the organization with its duties using appropriate technical and organizational measures where possible. If the processor acts outside the contract’s instructions or scope, it may be treated as a regulated entity or small business for that data. These processor contract requirements should align with your privacy policy, consent language, deletion workflows, and security practices. Reviewing processor contract requirements can help assess whether your agreements reflect those duties.
The Act’s definition of sharing excludes certain disclosures, including some disclosures to a processor consistent with the purpose disclosed to the consumer, and some disclosures to a third party with whom the consumer has a direct relationship when the consumer requested the service and the organization retains control and ownership of the data. Check each condition in RCW 19.373.010; do not assume every vendor transfer qualifies for an exclusion.
The geofencing prohibition makes it unlawful for any person to implement a geofence around an entity that provides in-person health care services when the geofence is used to identify or track consumers seeking care, collect consumer health data from them, or send notifications, messages, or advertisements related to their health data or health care services. The statutory prohibition is based on those purposes; RCW 19.373.080 does not specify a distance threshold.
Organizations must also limit employee, processor, and contractor access to what is necessary for an authorized purpose or a requested product or service, and maintain administrative, technical, and physical safeguards that meet the reasonable standard of care in the industry, appropriate to the volume and nature of the data. See RCW 19.373.050.
What are the compliance deadlines and enforcement risks?
The Act’s principal compliance date for regulated entities was March 31, 2024. Small businesses had a later date of June 30, 2024, for the provisions that specify that extension. As of November 18, 2026, both dates have passed, so covered organizations should treat applicable requirements as current obligations. The relevant provisions and dates appear throughout Chapter 19.373 RCW.
A violation is treated as an unfair or deceptive act or practice under Washington’s Consumer Protection Act for purposes of enforcement. The attorney general may bring an action under the CPA, and a person injured in business or property may have a private CPA claim if the statutory requirements for that claim are met. The available procedures and remedies depend on the circumstances; review RCW 19.373.090, RCW 19.86.080, and RCW 19.86.090.
In short, an effective compliance checklist starts with identifying covered data and exemptions, publishing an accurate privacy policy, obtaining valid consent or sale authorization where required, honoring consumer requests on time, controlling processors and recipients, securing data, and avoiding prohibited health-care geofencing.
FAQs
When must an organization obtain separate consent to share consumer health data?
Obtain consent for sharing before sharing, and make it separate and distinct from consent to collect the data. The Act permits sharing to the extent necessary to provide a product or service the consumer requested, and certain processor or other disclosures may fall outside the statutory definition of sharing. Check the exact conditions in the Act before relying on an exception.
How long does an organization have to respond to a deletion request?
Respond without undue delay and within 45 days of receiving the request. You may extend the response period once by up to 45 additional days if reasonably necessary, provided you notify the consumer within the first 45 days and explain the reason. Deletion from archived or backup systems may be delayed for restoration needs, but no more than six months from authenticating the request.
Do sale authorizations need to be retained?
Yes. Both the seller and purchaser must keep a copy of each valid authorization for six years from its signature or from the date it was last in effect, whichever is later. The consumer must also receive a copy.
What does the Act prohibit near in-person health care services?
It prohibits implementing a geofence around an entity that provides in-person health care services when the geofence is used to identify or track people seeking care, collect consumer health data, or send health-data- or care-related notifications, messages, or advertisements. The statute does not state a specific distance threshold.
Table of Contents
- Which organizations and data fall under the Act?
- What must a consumer health data privacy policy disclose?
- When is consent required for collection and sharing?
- How should organizations handle consumer rights and deletion requests?
- What authorization is required to sell consumer health data?
- What processor, recipient, and geofencing restrictions apply?
- What are the compliance deadlines and enforcement risks?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today