Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Health Data Interoperability topic
No spam. Unsubscribe anytime.
State health data sharing, HIE and analytics debated; witnesses ask clearer roles and privacy guardrails
Summary
Witnesses at the Health & Welfare Committee urged clearer statutory distinction between interoperability work carried out by the state health information exchange and the broader unified health data space, and recommended aligning data‑sharing decisions with existing data‑use agreements and privacy practices.
Beth Anderson, chief executive of the state health information exchange, told the Health & Welfare Committee that proposed bill language on interoperability and a unified health data space needs clearer separation so each program’s goals and legal constraints are explicit.
Anderson said the draft text bundles HIE interoperability work (electronic health record connections and clinical data flows) with the wider unified health data space goals (integrating non‑clinical data for statewide analytics). She recommended either making the unified health data space provisions explicit or splitting the bill into separate sections so that interoperability items (for example, EHR integration and existing HIE projects) remain distinct from the state’s unified analytics objectives.
Anderson also asked lawmakers to ensure the bill respects current data use agreements and privacy controls: “any decisions to share the data should align with restrictions that exist or periods in place,” she said, and suggested adding explicit language that data sharing be “allowed by the data‑use agreements in place for each dataset.”
Separately, Sam Wyche and Mike Fisher from the Office of the Health Care Advocate urged the committee to treat claims‑data integration as permissive rather than mandatory and to preserve best practices for privacy and security if the state is to assemble claims and clinical data for monitoring payment reforms. The health care advocate’s office also warned that retaining analytics capabilities developed under recent ACO work would require resources and should be prioritized carefully.
Why it matters: The committee is considering statutory language that will shape how clinical and claims data are shared across payers, providers and state agencies — a prerequisite for implementing total‑cost‑of‑care contracts, global budgets and performance monitoring. Witnesses recommended clearer statutory roles, alignment with existing privacy and data‑use frameworks, and staged approaches to claims‑data integration.
Next steps: Witnesses offered to submit written redlines for how to separate interoperability and unified data‑space provisions and to provide sample language clarifying permitted uses and data‑use agreement requirements. Committee staff said they will circulate suggested language for review.
