Washington My Health My Data Act: What Businesses Need to Know About Consumer Health Data

Kevin Henry

Data Privacy

Published Updated

9 minutes read
Share this article
Washington My Health My Data Act: What Businesses Need to Know About Consumer Health Data

Washington’s My Health My Data Act (MHMDA) regulates consumer health data beyond traditional medical records. If your business operates in Washington, targets Washington consumers, or processes this data for a covered organization, you should assess what information you handle, why you use it, and who can access it.

Which businesses and data are covered by the Washington My Health My Data Act?

The Act generally covers a legal entity that conducts business in Washington or provides products or services targeted to Washington consumers and determines, alone or jointly, the purposes and means of collecting, processing, sharing, or selling consumer health data. A consumer includes a Washington resident or a person whose consumer health data is collected in Washington, acting in an individual or household context—not an employment context. Washington’s statutory definitions describe these terms.

Consumer health data is personal information linked or reasonably linkable to a consumer that identifies their past, present, or future physical or mental health status. Examples include information about diagnoses, treatment, medication, reproductive or sexual health, gender-affirming care, biometrics, genetic data, and precise location that could indicate an attempt to obtain health services. The definition also reaches certain health-related inferences derived from nonhealth information, including algorithmic inferences.

Small businesses are still covered; the Act defines them using consumer-count and revenue thresholds rather than exempting them. Processors—such as vendors handling data on behalf of a regulated entity or small business—also have duties under the Act. Certain information is exempt, including HIPAA-protected health information and some information maintained by covered entities that is intermingled with exempt information. These are specific data-based exemptions, not a blanket exemption for every organization subject to HIPAA. See the Act’s exemptions and processor requirements.

Before collecting consumer health data, a regulated entity or small business generally needs the consumer’s consent for a specified purpose, unless the collection is necessary to provide a product or service the consumer requested. Sharing generally requires separate, distinct consent, unless the sharing is necessary to provide that requested product or service. Consent must be obtained before the relevant collection or sharing.

The consent request must clearly and conspicuously explain the categories of data involved, the purpose and specific ways the data will be used, the categories of entities it will be shared with, and how the consumer can withdraw consent. The Act defines sharing broadly, while providing specific exclusions, including certain disclosures to processors acting consistently with disclosed purposes. Review the collection and sharing requirements and the statutory definition of sharing.

Businesses should map data flows and check that their purposes, consent notices, privacy policy, and vendor arrangements align. The Act also requires access to consumer health data to be restricted to personnel and service providers who need it for permitted purposes, alongside reasonable administrative, technical, and physical security practices. The data-security provision sets out these obligations.

Consent must be a clear affirmative act showing the consumer’s freely given, specific, informed, opt-in, voluntary, and unambiguous agreement. Written consent may be provided electronically. A business cannot rely on acceptance of broad terms of use that combine health-data processing with unrelated material, a person’s hovering over or closing content, or consent obtained through deceptive design.

In practice, present a clear choice before collecting or sharing the data, explain the purpose in understandable terms, and keep the consumer’s choice separate from unrelated agreements. The exact consent design should match the data and use being disclosed. The statutory definition appears in RCW 19.373.010.

Consumers may ask whether a business is collecting, sharing, or selling their health data and request access to it. Access includes a list of third parties and affiliates with whom the data was shared or sold, along with an active email address or other online contact method for those recipients. Consumers can also withdraw consent to future collection and sharing and request deletion.

Businesses must provide a secure, reliable request method described in their privacy policy. They may require a consumer to use an existing account, but cannot require the consumer to create a new one. They may seek additional information reasonably necessary to authenticate a request if commercially reasonable efforts are insufficient.

Generally, respond without undue delay and within 45 days; a single 45-day extension is permitted when reasonably necessary if the consumer is notified within the original period and given the reason. For consumer health data deletion requests, delete the data from the business’s records, including archived or backup systems, and notify affiliates, processors, contractors, and other third parties that received it. Recipients must honor the request. A deletion from archives or backups may be delayed as needed for restoration, but not more than six months from authentication. The Act also requires an appeal process for refusals. See the consumer-rights and request provisions.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

What authorization is required to sell consumer health data?

Selling or offering to sell consumer health data requires valid authorization from the consumer before the sale. This consumer health data sale authorization must be separate and distinct from consent to collect or share data, written in plain language, and consistent with the sale that takes place.

The authorization must identify the specific data, the seller and purchaser with their contact information, and the sale’s purpose, including how the data will be gathered and used by the purchaser. It must also state that goods or services are not conditioned on signing, explain the consumer’s right to revoke and how to do so, warn that the purchaser may redisclose the data, and provide an expiration date one year from signature. The consumer must sign and date it, and receive a copy. The seller and purchaser must retain the authorization for six years from signature or from when it was last in effect, whichever is later. RCW 19.373.070 lists these requirements and defects that make an authorization invalid.

What must a consumer health data privacy policy include?

A Washington consumer health data privacy policy must clearly and conspicuously disclose the categories of health data collected and the purposes for which it is collected, including how it will be used. It must also identify the categories of sources from which the data is collected, the categories of data shared, the categories of third parties and specific affiliates receiving it, and how consumers can exercise their rights.

The business must prominently link to the policy from its homepage. If it wants to collect, use, or share additional categories of data or use the data for additional purposes not disclosed in the policy, it must disclose the change and obtain affirmative consent before doing so. Processor contracts must also be consistent with the policy. The requirements are set out in the consumer health data privacy policy provision.

For Washington My Health My Data Act processor obligations, use a binding contract that states processing instructions and limits what the processor may do. The processor must follow those instructions and, where possible, assist the regulated entity or small business with its compliance. A processor that acts outside its instructions or contract scope may itself be treated as a regulated entity or small business for that data. See RCW 19.373.060.

How does the geofencing prohibition apply to health care services?

The Act makes it unlawful for any person to implement a geofence around an entity providing in-person health care services when the geofence is used to identify or track people seeking care, collect consumer health data from them, or send them notifications, messages, or advertisements related to their health data or health care services.

A geofence is a virtual boundary established through location-detection technology that is 2,000 feet or less from the perimeter of a physical location. The prohibition focuses on the geofence’s location and use, not merely on whether the operator is a health care provider. Review the statutory geofence definition and the geofencing prohibition.

In short, businesses should identify covered data and vendors, obtain valid consent or authorization where required, support access and deletion rights, publish a compliant privacy policy, and avoid prohibited health-care-location geofencing.

FAQs

Who must comply with the Washington My Health My Data Act?

Regulated entities that do business in Washington or target Washington consumers and determine how consumer health data is handled generally must comply. Small businesses are covered under the Act’s definitions, and processors have contractual and assistance obligations when handling data for regulated entities or small businesses. Certain data and activities are exempt, so assess the specific information and processing involved. See the definitions, processor obligations, and exemptions.

What data qualifies as consumer health data under the Act?

It is personal information linked or reasonably linkable to a consumer that identifies their past, present, or future physical or mental health status. The definition includes health conditions and treatment, reproductive or sexual health, gender-affirming care, biometrics, genetic data, certain precise location information, and certain health-related inferences. See RCW 19.373.010.

Consent is generally required before collection for a specified purpose and before sharing, for which consent must be separate and distinct from collection consent. The Act allows an exception to these consent requirements to the extent the collection or sharing is necessary to provide a product or service the consumer requested. The collection and sharing provision explains the conditions and required disclosures.

Does selling consumer health data require separate written authorization?

Yes. A sale requires a signed, plain-language authorization that is separate and distinct from consent to collect or share the data. It must identify the data, seller, purchaser, purpose, revocation method, and other required terms, and expires one year after signature. The sale-authorization provision provides the full requirements.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles