Washington Healthcare AI Compliance Checklist
Compliance Checklist for healthcare businesses operating in Washington. Based on No comprehensive AI law — high-risk AI bill (HB 2157) died in committee; narrow measures only (companion chatbots, HB 2225; AI content disclosure, HB 1170) (No Law).
This checklist captures the statutory compliance actions required under No comprehensive AI law for healthcare businesses in Washington. Unlike best-practice guidance, every item on this checklist reflects a direct legal obligation that carries liability if not satisfied. The items are organized by compliance domain and are designed to be actionable by an internal team without specialized legal training — but compliance with each item is a legal requirement, not an aspiration.
Healthcare companies in Washington face very high AI compliance risk. No comprehensive AI law — high-risk AI bill (HB 2157) died in committee; narrow measures only (companion chatbots, HB 2225; AI content disclosure, HB 1170) — currently no law — requires washington has not enacted a comprehensive ai law — its high-risk ai bill (hb 2157) died in committee. only narrow measures are law, including ai companion-chatbot safeguards (hb 2225) and ai content-provenance disclosure by large providers (hb 1170). The deadline is N/A — penalties of N/A will apply to businesses that are not compliant by that date. The checklist-specific guidance below reflects this regulatory context.
The healthcare sector's Very High risk classification under Washington's AI framework reflects the breadth of AI deployments in this industry and the documented regulatory focus on these systems. Clinical decision support tools, AI-powered billing and coding software, patient-facing chatbots, and diagnostic imaging algorithms — all of these systems fall within the scope of No comprehensive AI law when they influence decisions affecting individuals in Washington. The risk concentration in this sector means regulators have prioritized enforcement against AI-assisted diagnosis and automated insurance authorization, making preemptive compliance especially critical. Operators that have deployed these tools without a formal compliance review are exposed to liability that compounds rapidly and over time. Each automated decision that touches a covered individual without the required disclosure or documentation is, in states with per-violation penalty structures, a separate actionable event. This accumulation logic is the enforcement lever regulators use to reach significant settlements — a high-volume AI workflow generating hundreds or thousands of discrete violations can aggregate to penalties far exceeding what a single violation might trigger. The practical implication: the longer a non-compliant AI system remains in production, the larger the potential aggregate exposure, and the more attractive the target becomes for enforcement agencies seeking visible settlements.
Operator obligations in Washington do not vary by the source or sophistication of the AI system involved — they apply equally to off-the-shelf AI tools purchased from third-party vendors as to custom-built models developed internally. This is a crucial point for healthcare businesses: if you are using a third-party AI product that makes or recommends decisions affecting people in ways covered by No comprehensive AI law, you are the deployer of record and bear the full compliance obligation, both the affirmative duties to disclose and document, and the liability for failures to do so. Vendor AI compliance due diligence itself is now a statutory obligation in multiple states — you must be able to demonstrate that before deploying a vendor's AI system, you: evaluated the system's risk classification; obtained vendor documentation of the system's bias testing, fairness assessment, and training data provenance; reviewed vendor contracts for compliance representations and indemnification; and documented that due diligence for regulatory production if needed. If a vendor cannot or will not provide basic documentation of their AI system's testing and compliance posture, deploying their tool creates documented exposure that you cannot shift retroactively to the vendor. The checklist guidance on this page applies without exception regardless of whether your AI was built internally or procured from a platform — contracting around these obligations with a vendor is not permitted by law.
Building a compliance timeline appropriate for healthcare businesses in Washington requires prioritizing obligations by deadline, enforcement probability, and penalty exposure. The highest-priority items — Tier 1, due in the first 30 days — are disclosure obligations: the legal requirement to notify individuals when AI materially influences a decision that affects them. These obligations are both mandatory and immediately verifiable by regulators, making them the highest enforcement target. Tier 1 also includes the AI inventory — a documented record of every system deployed — because regulators will ask for this in any investigation and its absence is itself an aggravating factor. The second tier, due within 60 days, consists of documentation requirements: maintaining decision logs; records of which AI systems are deployed, what decisions they influence, and how they were evaluated for bias; designated compliance ownership; and vendor compliance due diligence documentation. Failure to maintain these records when requested by a regulator is often treated as a separate violation. The third tier — formal bias audits, documented impact assessments, ongoing monitoring, and human-review pathways — requires more time and resources but is increasingly mandatory as AI law frameworks mature and as enforcement priorities shift from disclosure to outcomes. With Washington's deadline of N/A, businesses should complete tier one immediately, tier two within 60 days, and have tier three in progress before the deadline to demonstrate good-faith compliance.
The penalties and enforcement posture associated with No comprehensive AI law provide critical context for prioritizing compliance investment and understanding mitigation opportunities. Penalty structures under No comprehensive AI law are still being finalized, but comparable state AI laws have established per-violation fines in the range of $500 to $25,000. This per-violation structure means that a business with 1,000 non-compliant AI-driven decisions can face aggregate liability in the millions — a reality that has shaped settlement negotiations in early enforcement cases. Regulators in states with active AI law enforcement — including those with whistleblower provisions that allow individuals to trigger investigations without agency resources being the limiting factor — have demonstrated a willingness to act aggressively on well-documented complaints and visible violations. For healthcare businesses in Washington, the most likely enforcement triggers are: complaints from individuals who received AI-driven decisions without required disclosures; third-party bias audits or media investigations that surface discriminatory AI outcomes; and regulatory sweeps targeting specific high-risk use cases such as AI-assisted diagnosis and automated insurance authorization. Critically, regulators have consistently stated that documented good-faith compliance programs — even incomplete ones appropriate for the business's size and maturity — significantly reduce enforcement probability and penalty severity. Building the compliance infrastructure described in this checklist guide creates a documented record that regulators routinely take into account when determining whether to pursue formal enforcement versus issuing guidance, and how to calibrate penalties among violators. This documented good-faith record is often the difference between a warning letter, a negotiated settlement, and the maximum available penalty.
AI Compliance Context for Washington
Washington's regulatory posture on AI is silence rather than permission: washington legislature has not advanced substantive ai legislation. General consumer-protection statute (UDAP) and federal residual coverage provides the residual framework. For clinical decision-making and patient-record AI in Washington, federal signals set the ceiling while regional precedent sets the floor.
Federal law still governs Healthcare AI in Washington primarily through HIPAA Privacy Rule (45 CFR 164.502) and FDA SaMD guidance. Adjacent federal authorities include HIPAA Privacy Rule (45 CFR § 164.502(b)); HIPAA Security Rule (45 CFR § 164.308–316); FDA Software as Medical Device (SaMD) Guidance (FDA-2021-D-0074 (updated 2023)). HIPAA Privacy Rule (enforced by HHS Office for Civil Rights) applies to ai systems processing patient health information must ensure privacy, consent, and secure transmission. ai-driven diagnosis or treatment recommendations must comply with data minimization. Penalty exposure: $141–$71,162 per violation (2024 adjusted); annual cap $2.13m per tier. HHS Office for Civil Rights intensified AI-bias investigations in 2025 under HIPAA and Section 1557 of the ACA.
Washington's immediate neighbors also lack AI-specific statutes, so operators defer primarily to federal frameworks until regional precedent emerges.
Because Washington has no dedicated AI statute, regulatory obligations fall back to general consumer-protection statute (UDAP) and federal residual coverage layered with federal sector-specific rules.
Start with these concrete compliance actions. (1) Inventory every diagnosis, treatment recommendation, or care-triage decision running on AI in your Washington operations, tagging systems against HIPAA Privacy Rule (45 CFR 164.502) and FDA SaMD guidance. (2) Run a Healthcare-specific bias evaluation against the HIPAA Privacy Rule within 45 days, with patient-safety liability and algorithmic bias producing disparate treatment outcomes as your top risk to retire. (3) Document decision-explainability procedures under Conduct AI impact assessments for patient data handling. (4) Add human-review checkpoints for high-stakes outputs and wire alerts to the signals behind FDA cleared over 950 AI/ML medical devices through 2024 and is issuing real-world performance guidance. (5) Track regional precedent as your early-warning indicator. (6) Train small-tier staff on AI disclosure obligations specific to Healthcare, and maintain the following sector artefacts: clinician workflow, patient-record access, PHI minimisation, bedside triage, and diagnostic concordance. Sequence these steps across a 90-day onboarding, with a board-level review before go-live.
The enforcement surface for Healthcare centres on HHS OCR, FDA, FTC, and the statute operators most often under-document is HIPAA Security Rule (45 CFR § 164.308–316) — a gap that surfaces in patient-safety liability disputes. Build an evidence binder covering clinician workflow, patient-record access, PHI minimisation, bedside triage, and diagnostic concordance. Treat FDA cleared over 950 AI/ML medical devices through 2024 and is issuing real-world performance guidance as your leading indicator and escalate when the signal shifts.
With 11-50 employees you can justify a half-time compliance lead and part-time external counsel on retainer. Small-stage Healthcare operators should deploy a named compliance lead, formal AI inventory, quarterly bias spot-checks, and a documented escalation path, with semi-annual internal audit with annual external review and ownership resting with a designated AI compliance lead reporting to the CEO. small-business budgets ($50K-$250K) justify a compliance lead plus a GRC tool such as Credo AI, Fairly, or Holistic AI. For Healthcare specifically, the sharpest exposure to manage is patient-safety liability and algorithmic bias producing disparate treatment outcomes. Given Washington's concentration in its principal industries, core regulated activities deserve priority in your AI inventory.
Verified 2026-07-02. See https://app.leg.wa.gov/billsummary?BillNumber=2157&Year=2025 for the Washington Attorney General public record on Washington AI policy.
Disclosure & Transparency
Risk Assessment
Governance & Policy
Technical Requirements
More for Washington Healthcare
AI laws for Healthcare in other states
Anchored to the primary government source (statute, bill text, or agency rule) and verified directly against it · Last verified Jul 2, 2026. See our methodology.
- ↗app.leg.wa.govhttps://app.leg.wa.gov/billsummary?BillNumber=2157&Year=2025
- ↗hunton.comhttps://www.hunton.com/privacy-and-cybersecurity-law-blog/washington-state-en…
- ↗iapp.orghttps://iapp.org/resources/article/us-state-ai-governance-legislation-tracker/