Washington State HIPAA Laws: What You Need to Know About Patient Privacy and Compliance

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

Washington State HIPAA Laws: What You Need to Know About Patient Privacy and Compliance

Kevin Henry

HIPAA

May 16, 2025

7 minutes read
Share this article
Washington State HIPAA Laws: What You Need to Know About Patient Privacy and Compliance

HIPAA Privacy Rule Compliance

Washington State HIPAA laws require you to safeguard protected health information (PHI) and limit its use and disclosure to what is necessary for permitted purposes. Start by mapping all PHI you create, receive, maintain, or transmit, then document lawful bases for each use or disclosure under the HIPAA Privacy Rule.

Core obligations

  • Apply the minimum necessary standard to routine uses and disclosures, and document minimum necessary standard exemptions (for example, disclosures for treatment, to the individual, pursuant to a valid authorization, or as required by law).
  • Implement patient authorization protocols for uses and disclosures beyond treatment, payment, and health care operations (TPO). Authorizations must be specific, time-limited, revocable, and written in plain language.
  • Execute and maintain business associate agreements with vendors that access PHI, defining permissible uses, safeguards, breach reporting, and subcontractor flow-downs.
  • Publish a clear Notice of Privacy Practices and train your workforce on permissible uses, consumer consent requirements, and documentation expectations.

Practical compliance steps

  • Standardize intake, release-of-information, and patient authorization protocols so staff can quickly verify legal authority before sharing PHI.
  • Use role-based access and verify requestor identity before disclosure; log disclosures that require accounting.
  • Periodically audit charts and release workflows to confirm minimum necessary is consistently applied.

HIPAA Security Rule Requirements

The Security Rule requires administrative, physical, and technical safeguards for electronic PHI. Your risk analysis should drive a risk management plan that fits your size, complexity, and the sensitivity of the data you handle.

Electronic health record safeguards

  • Access controls: unique user IDs, multifactor authentication, automatic logoff, and least-privilege role design.
  • Transmission and storage: strong encryption in transit and at rest, email/portal policies, and secure device management.
  • Integrity and monitoring: audit logs, immutable logging for critical events, anomaly detection, and periodic access reviews.
  • Resilience: data backup, disaster recovery, and emergency mode operations testing at planned intervals.
  • Governance: security awareness training, sanction policies, vendor due diligence, and updated business associate agreements.

Washington State Health Care Information Act

Washington’s Health Care Information Act (HCIA), codified in RCW 70.02, complements HIPAA and may be more protective in certain areas. When state law is more stringent than HIPAA, you must follow the stricter rule.

Key Washington specifics

  • Clear consumer consent requirements for certain redisclosures and non-TPO uses of health care information.
  • Additional limits on secondary use and redisclosure; verify downstream recipients have legal authority before sharing.
  • Record-handling expectations, fees, and timelines that can differ from HIPAA; align your processes with state requirements.
  • Relevant citations include RCW 70.02.290, which provides state-level direction on disclosures under defined circumstances within the HCIA framework.

State agencies operationalize these requirements through internal policies. For example, DSHS Administrative Policy 5.06 guides confidentiality, release procedures, and minimum necessary practices for programs handling sensitive client data.

Washington My Health My Data Act

The Washington My Health My Data Act (MHMD) protects “consumer health data,” a category broader than HIPAA PHI. It applies to many organizations that collect, share, or sell health-related data—even if they are not HIPAA covered entities.

What MHMD requires

  • Consent: obtain clear, actionable consent before collecting or sharing consumer health data; record and honor withdrawals.
  • Authorizations for sale: a separate signed authorization is required for selling consumer health data, with strict content and expiry terms.
  • Transparency: publish a consumer health data privacy notice describing data types, purposes, sharing, and retention.
  • Consumer rights: provide access, deletion, and portability for covered data and maintain easy-to-use request channels.
  • Geofencing: do not use geofencing to track or target individuals around health care facilities for certain purposes.

If you handle both PHI and consumer health data, you must run parallel programs: HIPAA for PHI and MHMD for non-PHI data, ensuring your consent flows, disclosures, and patient authorization protocols correctly map to each regime.

Ready to simplify HIPAA compliance?

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

Workers' Compensation and HIPAA

HIPAA permits disclosures without patient authorization when necessary to comply with workers’ compensation laws. In Washington, this commonly involves sharing information with the Department of Labor & Industries (L&I), claims administrators, and insurers to evaluate and pay claims.

  • Limit each disclosure to the minimum necessary for the claim; segregate unrelated clinical details.
  • Use standardized release workflows for L&I and insurers, and verify requestor identity before sending records.
  • Document the legal basis for each disclosure and log those that require accounting under HIPAA.

Patient Rights under HIPAA

Patients have robust rights that your practice must honor promptly. Build user-friendly processes and clear scripts so staff can respond consistently and within legal timelines.

  • Right of access: provide copies in the requested format if readily producible; permit directed third-party transmissions when applicable.
  • Right to request amendment: review, decide, and append rebuttals when amendments are denied.
  • Right to request restrictions: especially for out-of-pocket payments where patients can require nondisclosure to health plans.
  • Right to confidential communications: accommodate reasonable requests for alternative addresses or contact methods.
  • Accounting of disclosures and a current Notice of Privacy Practices available in prominent locations and online.

Breach Notification Requirements

Under HIPAA, you must notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured PHI. Report to HHS and, for incidents affecting 500 or more residents of a state or jurisdiction, to prominent media as required.

Washington’s general data breach law imposes additional obligations when personal information is involved. In practice, organizations operating in Washington typically target the shortest applicable timeline, often no later than 45 days for state-law reportable events, and notify the Attorney General when thresholds (such as 500+ Washington residents) are met.

Coordinating multi-law incidents

  • Perform a quick legal triage to determine whether HIPAA, MHMD, and state breach laws all apply; many incidents trigger more than one regime.
  • Align notices to cover required content under each law, track distinct reporting portals, and preserve forensics and decision logs.
  • Update business associate agreements to clarify breach roles, timelines, and cooperation duties; test your incident response plan annually.

Conclusion

Effective compliance in Washington means harmonizing HIPAA with the HCIA and the My Health My Data Act. Build clear consent and patient authorization protocols, apply the minimum necessary standard with its exemptions, harden electronic health record safeguards, and prepare for fast, well-documented breach response. When state rules are stricter, follow the stricter requirement.

FAQs

What protections does Washington State provide beyond federal HIPAA laws?

Washington’s Health Care Information Act adds stricter rules on redisclosure and consent in some contexts, and the My Health My Data Act extends protections to consumer health data outside HIPAA. Together, they raise the bar for transparency, consent, and individual rights beyond federal baselines.

How does the My Health My Data Act impact patient data privacy?

It requires explicit consent to collect or share consumer health data, a separate authorization to sell such data, detailed public disclosures, and rights to access and deletion. It also prohibits certain geofencing around health services, meaning you must rethink marketing, analytics, and data-sharing practices that involve non-PHI health data.

What are the breach notification requirements under Washington State law?

For incidents covered by Washington’s data breach statute, notify affected residents as quickly as possible and typically no later than 45 days, with Attorney General notice when thresholds like 500+ residents are affected. If HIPAA also applies, meet the federal 60-day outside limit and align content to satisfy both laws, using the shortest applicable timeline.

Can providers share information for workers' compensation without patient authorization?

Yes. HIPAA allows disclosures without authorization when necessary to comply with workers’ compensation laws. In Washington, share only the minimum necessary information required for the claim, verify who is requesting it, and document the legal basis and scope of each disclosure.

Share this article

Ready to simplify HIPAA compliance?

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

Related Articles