States Are Splitting on AI Health Regulation, and Patients May Feel the Gap
Maryland and Virginia are taking notably different approaches to regulating AI in healthcare, reflecting a broader patchwork of state-level oversight. The divergence could shape where companies deploy products—and how protected patients really are.
AI in healthcare is increasingly being regulated not by a single national framework, but by a patchwork of state decisions. The Maryland-Virginia contrast is a useful case study in how quickly policy divergence can shape product design and market access.
This matters because healthcare AI is not just software; it is software that can affect diagnosis, access, triage, reimbursement, and clinical workflow. When states disagree on where oversight begins, vendors are pushed to comply with the most restrictive rules or to fragment their offerings by geography.
That fragmentation can slow innovation, but it can also expose gaps in patient protection. If a tool is considered sufficiently risky to regulate in one state but not another, the burden shifts to patients and providers to understand whether they are receiving comparable safeguards.
The bigger issue is that healthcare AI is moving faster than the regulatory frameworks meant to contain it. States are filling the void for now, but the result may be uneven standards, uncertain liability, and a growing compliance burden for organizations already struggling to operationalize AI responsibly.