Consumer health data is a subset of information linked or reasonably linkable to a consumer that identifies past, present, or future physical or mental health. Personal information is broader and includes any information that can identify or be linked to a consumer, such as an IP address or device identifier. In practice, the Act applies stricter handling rules to health related data than to general personal data.
How consumer health data differs from personal information under the Act
The key distinction is scope. Consumer health data is a narrower class of data tied to a consumer’s physical or mental health, so it carries the Act’s most restrictive handling expectations. Personal information is broader and can include many ordinary identifiers that may identify or be linked to a person, but are not necessarily health related. That narrower health category is what drives the Act’s stricter treatment.
For a practical reading of the law, the question is not just whether data can identify someone, but whether it reveals or can reasonably be linked to health status, care, symptoms, diagnoses, treatment, or similar health inferences. That is why the same dataset can contain both ordinary personal information and separate consumer health data elements, with different compliance obligations attached to each.
Organisations often misread the Act by treating all personal information as if it were equally sensitive. In practice, the compliance burden changes when the data moves from general identification or device tracking into health related inference, because the law is designed to limit collection, use, disclosure, and sharing of that health data more tightly than generic personal information.
Where the boundary becomes operationally important
The boundary matters most in product design, analytics, advertising, and data sharing. A record can be personal information because it can identify a consumer, while also becoming consumer health data if it is linked to health concerns or used to infer health conditions. That means the same field, event, or interaction may need to be classified differently depending on how it is used and what it reveals.
Teams should think in terms of data flows rather than labels. A browser identifier, app event, location signal, or account record may look like ordinary personal information on its face, but if it is used to infer visits to a clinic, interest in treatment, or a condition-specific behaviour, the health-data rules become relevant. That is why classification has to follow the inference and linkage risk, not just the raw field name.
For a broader state-law comparison, the distinctions in US State Privacy Laws Guide help place Washington’s approach within the wider patchwork of privacy obligations. For the health-data side specifically, Health Data Privacy Beyond HIPAA Guide (My Health My Data) is the most direct reference for understanding how consumer health data is treated outside HIPAA.
Why this distinction changes compliance decisions
The distinction affects notice, consent, sharing, retention, and enforcement risk. General personal information can often be handled under the ordinary privacy program, but consumer health data typically requires a more cautious decision path because the law assumes greater sensitivity and greater harm if that data is collected or shared without proper restraint.
That creates a common trap for product and legal teams: they may correctly inventory personal information, but still miss that a subset of that inventory is health data because the health meaning emerges only after enrichment, linking, or downstream use. The compliance consequence is not just a policy gap, but a failure to apply the stricter controls to the right data classes.
Where health-data handling is in scope, the FTC Health Breach Notification Rule Guide is a useful companion for understanding breach handling in adjacent non-HIPAA health app contexts. If location signals are part of the workflow, Location Data Privacy Guide helps explain why geolocation can become sensitive when it is linked to health related activity.
Risk and Threat Considerations
Consumer health data creates higher exposure because it can reveal intimate conditions, treatment patterns, or care-seeking behaviour that ordinary personal information does not. The main risk is not only unauthorised disclosure, but also secondary use that allows profiling, targeting, or inference beyond what consumers would reasonably expect.
Failure mechanism: Organisations often classify based on source system rather than on inference, so health meaning is missed when it is assembled from app events, location traces, or engagement data.
Impact: Misclassification can lead to unlawful sharing, weak consent handling, and enforcement exposure, especially where the data is repurposed for advertising or analytics.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 and GDPR define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.PO-01 — Policy Establishment, Communication and Awareness | The Act requires policies that distinguish health data from general personal data. |
| Recommendation — Define data-classification rules that separate consumer health data from ordinary personal information. | ||
| NIST SP 800-53 Rev 5 | PT-2 — Authority to Process Personally Identifiable Information | The topic turns on how sensitive personal data categories are authorised and governed. |
| Recommendation — Restrict processing conditions for health-linked personal data and document the basis for use. | ||
| ISO/IEC 27001:2022 | A.5.12 — Classification of information | The answer depends on classifying health data differently from broader personal information. |
| Recommendation — Classify consumer health data separately and apply stricter handling controls to that class. | ||
| GDPR | Art. 9 — Special categories of personal data | The comparison hinges on distinguishing ordinary personal data from a more sensitive health category. |
| Recommendation — Map health-related data to the stricter sensitive-data workflow before sharing or analytics use. | ||
Practitioner Guidance
What to verify: Test data inventories against use cases, not just fields. If a data element can identify a consumer and also support a health inference, treat the health component as a separate classification decision.
Decision rule: If the data set can support a health-related inference, apply the stricter consumer health data controls first and only then assess whether the remaining information can be handled as ordinary personal information.
Practitioner takeaway: The operational mistake is treating “personal information” as the whole answer, when the real compliance trigger is whether any part of the dataset becomes consumer health data through linkage, inference, or downstream use.
Related resources from NHI Mgmt Group
- My Health My Data Act
- Why does collecting consumer health data under the Washington My Health My Data Act create higher compliance risk?
- What are the signs that a consumer health data program is failing under the Washington My Health My Data Act?
- How should organisations prepare for the Washington My Health My Data Act before it takes effect?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org