1 / 11

Query Health Operations WG

Query Health Operations WG. Face-to-Face Meeting. 0ctober 18 & 19, 2011. Agenda. Introductions & Meeting Objectives Overview of F2F Agenda Rules of the Road Review of Operations Workgroup Goals Discussion of “Operational Requirements for Query Health” Document Reference Materials

xia
Download Presentation

Query Health Operations WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Query HealthOperations WG Face-to-Face Meeting 0ctober 18 & 19, 2011

  2. Agenda • Introductions & Meeting Objectives • Overview of F2F Agenda • Rules of the Road • Review of Operations Workgroup Goals • Discussion of “Operational Requirements for Query Health” Document • Reference Materials • HITPC Tiger Team Recommendations • Policy Sandbox

  3. Introductions & Meeting Objectives • Introductions • Name • Organization • How many miles did you travel to be at the F2F? • Meeting Objectives • Finalize the “Operational Requirements for Query Health” Document • Discuss Data Use Agreement Template (time permitting)

  4. Agenda for Tuesday, October 18th

  5. Agenda for Wednesday,October 19th

  6. Rules of the Road • Be present at the meeting by limiting side conversations and closing computer • Be respectful of others • Be mindful of how much you are contributing to the conversation in comparison to others • Facilitators reserve the right to parking lot issues for resolution at another date • Thank you for volunteering with the Query Health Initiative! We understand if you need to step out briefly to address other business issues.

  7. Review of Operations Workgroup Goals • Defined Goals of Operations Workgroup • Document and Detail the Operations Requirements for User Stories and inclusion in the Use Case and Requirements document being prepared by Clinical Workgroup; • Ensure linkage between the Query Health Initiative and the guidance received from the Health IT Policy Committee (HITPC) and the Privacy and Security Tiger Team, and; • Prepare guidance documents (as prioritized by the work group), such as those related to: • Adherence to privacy and security requirements and considerations; • Evaluation of transaction cost / time to implement distributed queries; • Other operational guidance (or feedback to other responsible groups)

  8. Operational Requirements for Query Health • Finalize Best Practice Considerations (Section 2.4) • Finalize the following sections: • Regulatory Issues (Section 2.5) • Assumptions (Section 5.0) • Risks, Issues, and Obstacles (Section 13.0)

  9. Reference Materials

  10. Recommendations from HITPC for the Operations WG • Public Health Considerations: • Query Health should not substitute new Data Use Agreements or other restrictions and agreements to Public Health • Public Health should not be equated with research and has well established rules and accountability.  • Any Public Health Query must be evaluated for feasibility and urgency of responses.  • Clarification around the use of PHI:  “For a public health permitted use, individually identifiable health information may be provided by the disclosing entity to the public health agency consistent with applicable law and regulation.” • Restrictions on Data Use: • There should be clear agreement between the data source and the information request covering use or reuse of the query result data.  • The Data Use Agreement should permit follow-up queries based on previous query results as long as the data source controls all decisions to release data. • Pilots Considerations • The use of pilots is particularly valuable for uncovering issues with the sandbox restrictions, data use agreements and governance that can be addressed as policy issues by the HITPC.

  11. Policy Sandbox Query requests and responses shall be implemented in the pilot to use the least identifiable form of health data necessary in the aggregate within the following guidelines: Disclosing Entity: Queries and results will be under the control of the disclosing entity (e.g., manual or automated publish / subscribe model). Data Exchange: Data will be either 1) mock or test data, 2) de-identified data sets or limited data sets each with data use agreements1 or 3) a public health permitted use2 under state or federal law and regulation. Small cells: For other than regulated/permitted use purposes, cells with less than 5 observations in a cell shall be blurred by methods that reduce the accuracy of the information provided3. Notes: It is understood that de-identified data sets do not require a data use agreement, but in the abundance of caution, and unless otherwise guided by the Tiger Team or HIT Policy Committee, the pilot will have data use agreements for de-identified data For a public health permitted use, individually identifiable health information may be provided by the disclosing entity to the public health agency consistent with applicable law and regulation. The CDC-CSTE Intergovernmental Data Release Guidelines Working Group has recommended limiting cell size to three counts presuming a sufficiently large population. This is also reflected in Guidelines for Working with Small Numbers used by several states.

More Related