A new, powerful Citizen Portal experience is ready. Switch now

Supporters urge safeguards in AI‑behavioral health bill; industry warns of overbreadth

April 02, 2026 | Finance Committee, SENATE, SENATE, Committees, Legislative, Maryland


This article was created by AI summarizing key points discussed. AI makes mistakes, so for full details and context, please refer to the video of the full meeting. Please report any errors so we can fix them. Report an error »

Supporters urge safeguards in AI‑behavioral health bill; industry warns of overbreadth
Delegate Lily Chi told the Senate Finance Committee that House Bill 883 seeks to prevent consumer harms from AI systems that claim to be behavioral‑health professionals or otherwise give the impression they provide clinical care.

"AI is not licensed. They are not accountable to a regulatory body, and they cannot exercise professional judgment grounded in human relationships or lived experiences," Carissa Proctor of the National Association of Social Workers (Maryland chapter) testified in support. Proctor urged safeguards, including clear disclosures and crisis‑referral protocols when AI systems encounter suicide‑related content.

Kaiser Permanente’s Allison Taylor suggested a clarifying amendment to exclude administrative or supplementary uses of AI by licensed providers, saying the bill should not unintentionally restrict clinically supervised, provider‑led use of tools.

Industry witnesses — including Hannah Allen of the Maryland Chamber of Commerce, Tara Hoops of the Chamber of Progress and Margaret Durkin of TechNet — urged an unfavorable report in the bill’s current form. They argued the current language swept in broad categories of consumer‑facing AI (voice assistants, coding tools, photo editors) and said the requirement to display a disclosure at the beginning of each use or to implement suicide‑detection infrastructure would impose heavy compliance burdens and degrade user experience.

Opponents and some proponents pointed to Utah’s framework as an example of a narrower, risk‑based approach and asked the committee to consider removing or narrowing a private right of action that was added in the house.

The committee heard several favorable and unfavorable testimonies and questions about definitions (such as the scope of "developer" and whether chat‑GPT–style tools are captured). The hearing concluded without a committee vote recorded.

View the Full Meeting & All Its Details

This article offers just a summary. Unlock complete video, transcripts, and insights as a Founder Member.

Watch full, unedited meeting videos
Search every word spoken in unlimited transcripts
AI summaries & real-time alerts (all government levels)
Permanent access to expanding government content
Access Full Meeting

30-day money-back guarantee