Intake forms and appointment notes often end up in shared mailboxes and SharePoint folders, where the list of people with access can grow as teams and projects change. Washington’s My Health My Data Act puts specific rules around that kind of information, including some data that falls outside the Health Insurance Portability and Accountability Act (HIPAA). This article explains how the two laws relate and which parts of a Microsoft 365 environment to review.
What is the My Health My Data Act in Washington?
The Washington Attorney General describes the My Health My Data Act as the first privacy law in the country to protect personal health data that falls outside HIPAA. It sets rules for how regulated entities collect and share consumer health data, and it gives consumers the right to ask for deletion, including from archived and backup systems.
The definition of consumer health data is broad. The Attorney General’s FAQ says it includes health inferences drawn from non-health data, along with the use and purchase of prescribed medication.
The Act applies to entities that do business in Washington or target Washington consumers and determine the purpose and means of collecting, processing, sharing, or selling consumer health data. The core requirements took effect on March 31, 2024, for regulated entities and June 30, 2024, for small businesses. Businesses looking for guidance on health data privacy in Washington can read the Attorney General’s FAQ, which is a primary source.
Does the My Health My Data Act apply to HIPAA-covered businesses?
HIPAA governs protected health information (PHI) with covered entities and business associates. The Washington statute exempts information that meets the definition of PHI, and the exemption attaches to that information. A practice can hold PHI and also hold consumer health data outside the PHI definition, which may include data gathered through a website or a wellness app.
An existing HIPAA program may therefore leave some categories of health data unaddressed. A HIPAA Microsoft 365 configuration, such as encryption settings or a business associate agreement with Microsoft, addresses HIPAA obligations, and other data held by the business can call for its own review.
Microsoft states that each customer remains responsible for its own compliance program and internal processes and for aligning its use of Microsoft services with HIPAA. Whether the Washington law applies to a particular organization, and which data falls under which law, is a matter for legal counsel. Practices reviewing their HIPAA controls can see the services Centerlogic describes on its healthcare IT page.
Why Microsoft 365 healthcare compliance depends on configuration
Washington’s My Health My Data Act includes a section on data security practices. Under RCW 19.373.050, regulated entities and small businesses must limit access to consumer health data to the staff and contractors who need it and maintain security practices that meet a reasonable standard of care in their industry.
Microsoft 365 has tools that can support practices like these, and the results depend on the settings chosen for each one. Permissions decide who can open a file, and sharing settings decide who outside the organization can receive it. Classification determines which files receive extra protection, and monitoring determines whether anyone notices unusual activity. Written policies then set the expectations for how staff handle data day to day, and the technical controls should match them.
Microsoft 365 security and compliance tools for protecting health data
Several Microsoft 365 and Microsoft Purview capabilities support the controls described above.
- Sensitivity labels classify and protect data without hindering collaboration, according to Microsoft. A label can mark a document containing health information and apply protection settings to it.
- Data loss prevention (DLP) policies monitor user activities and apply protective actions, which can reduce inappropriate sharing or movement of sensitive data. Microsoft notes that training users matters as much as tuning the policies.
- Identity and access controls limit who can reach particular information.
- Audit logging records user and administrator activity across dozens of Microsoft services in the unified audit log, which supports reviews and investigations. Searching it requires assigned roles.
- Compliance Manager provides pre-built assessments and improvement actions that can be assigned to staff, along with a risk-based score that tracks progress. Available assessments depend on licensing.
Meeting a legal requirement takes a complete program, and each tool supports one control within it that the organization still has to design and review. Organizations that also serve Oregon residents may find Centerlogic’s article on how Microsoft 365 can help with Oregon’s privacy requirements useful.
Common Microsoft 365 security mistakes in healthcare and wellness businesses
These are technical control weaknesses to check, and any one of them is a configuration finding only.
- Too many people can open folders that hold sensitive records.
- External sharing links are broader than intended.
- Sensitive files carry inconsistent labels, and some are unlabeled.
- DLP policies were never configured or have gone unreviewed since the business changed.
- Audit logs are collected, but no one has been assigned to review them.
- Former employees and unused accounts keep access.
- Permission reviews happen without a set process.
- Security settings stay at their original values as headcount and tools change.
Organizations that want ongoing attention on these controls can look at Centerlogic’s managed cybersecurity services.
Microsoft 365 review for Vancouver, WA, healthcare and wellness businesses
Organizations that handle health-related information should revisit their Microsoft 365 configuration whenever the business grows, adds services, adopts new tools, or changes its data-sharing practices. Permissions set up for a small team can fall out of date as headcount and tools change.
Centerlogic is a Microsoft Solutions Partner based in Vancouver, WA. Eric Schulz of The Children’s Clinic, a Centerlogic client, describes the team as “excellent at explaining IT.” As a local option for healthcare IT in Vancouver, WA, Centerlogic can review a Microsoft 365 environment and recommend technical improvements where the configuration needs attention. Legal coverage decisions remain with qualified counsel.
Get in touch with Centerlogic to review your Microsoft 365 and data protection setup and learn which settings need attention.
FAQs
Is Microsoft 365 HIPAA compliant?
Microsoft enters into business associate agreements with covered entities and business associates, and its HIPAA and HITECH page lists the in-scope services. Compliance itself rests on each organization’s own program and configuration. Whether an agreement is required for a particular organization is a matter for legal counsel.
Can you be sued under the My Health My Data Act?
According to the Attorney General’s FAQ, any violation of the Act is treated as a violation of the Washington Consumer Protection Act. The Attorney General enforces that law, and it also allows private action. Individual circumstances belong with legal counsel.
Does the My Health My Data Act cover employee data?
The definition of a consumer in RCW 19.373.010 excludes an individual acting in an employment context. Patients and clients acting in a personal capacity can fall within the definition when the other criteria are met. Applying the definition to a specific workforce or client base is a matter for legal counsel.
When is consent required under the My Health My Data Act?
Under RCW 19.373.030, a regulated entity or small business collects consumer health data with consent for a specified purpose or, to the extent necessary to provide a product or service, the consumer requested. Sharing follows the same pattern, with consent that is separate and distinct from the collection consent. A consent request must clearly disclose the categories of data, the purpose of the collection or sharing, the categories of recipients, and how the consumer can withdraw consent.


