Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Health Data Hie topic

No spam. Unsubscribe anytime.

Committee debates unified health data space, privacy safeguards and payer access

3548040 · May 28, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Members reviewed Senate language directing development of a unified health data space, discussed integration rules set by the HIE steering committee, and raised concerns about payers having access to clinical data and administrative‑burden reductions for providers.

Conference negotiators reviewed language directing the development of a unified health data space (a statewide integrated clinical/claims data system) and debated limits on data integration, uses, and payer access.

The Senate language restores a provision directing the agency to collaborate with the health information exchange (HIE) steering committee to develop a unified health data space that integrates clinical and claims data, social‑drivers information, and other data types. The transcript shows negotiators added a requirement that any integration of data types occur "only upon the favorable vote of a majority of all voting members of the HIE steering committee and only for the specific uses approved" by that committee, Jen, legislative counsel, said.

Why it matters: A unified data space could improve clinical information access for providers and support population‑health and policy analysis. But the committee raised two central concerns: (1) privacy and security standards and the HIE steering committee’s role in approving specific integrations and uses; and (2) whether health insurers (payers) should be allowed access to integrated clinical data for uses beyond risk‑pool or insurer‑contributed data.

A committee member asked whether interoperability language effectively would require all contributors to use the same electronic health‑record software; presenters said interoperability is meant to require compatible interfaces rather than identical software. Several members expressed alarm at the prospect of payers having access to clinical data they did not contribute; one member noted last year’s bill restricting payers from certain prepayment medical‑review activities and asked whether payer access to clinical data would jeopardize patients. The group agreed to "phone a friend"—seek technical advice from HIE and privacy experts—and to draft counter‑language addressing payer access and administrative burden reduction.

The Senate language also proposes annual reporting on the unified health data space’s development and requires AHS to identify resources necessary for data linkages, timelines for setup, and systems for rapid access by patients, providers and payers "to the extent permitted by data‑use agreements." Several committee members asked that language specifically call out reducing administrative burdens on providers; others warned that a centralized data system without usage limits could be underused or raise privacy concerns.

Ending: Staff said they will revise the section to address concerns about payer access and administrative burdens and will consult with HIE technical experts and privacy advisors before returning with alternative text.