240 likes | 357 Vues
Query Health Distributed Population Queries Implementation Group Meeting. October 4, 2011. Participation Instructions for WebEx. Select the “Q&A” button in the WebEx toolbar. Select “All Panelists” in the Q&A box. Type your question and hit send.
E N D
Query Health Distributed Population QueriesImplementation Group Meeting October 4, 2011
Participation Instructions for WebEx Select the “Q&A” button in the WebEx toolbar. Select “All Panelists” in the Q&A box. Type your question and hit send. We’ll call on you to state your comment / question . • Please Note: • This session will be recorded • Lines are open so please mute your line to avoid “Music on Hold”
Agenda • Summary of Last Meeting & Reminders • WG updates • Clinical • Technical • Business • Charter – Final Call for consensus • Discussion Forums • Open discussion / Next Steps
Query HealthScope and Approach HIT Policy Committee: Policy Guideposts Practice drives standards Rough consensus Running code (open source) Pilot Specifications Standards
Query HealthCalendar Implementation Group Tuesdays 1:30pm-3:00pm EDT Clinical Work Group Wednesdays 12pm-1pm EDT Business Work Group Thursdays 11am-12pm EDT Technical Work Group NEW TIME Thursday 2:00 pm-3:00 pm EDT First Face to Face Meeting October 18-19 Sign Up at QueryHealth.org Download to your calendar at QueryHealth.org
Query HealthWho’s participating (As of 9/27) 100+ Participating Organizations • Public Health Agencies • Health IT Vendors • Health Information Exchanges • Academic Partners • Health Systems • Patient Advocacy Organizations
Recap of Last Meeting • Reviewed Query Health Scope, Approach, Timeline, and Organization • Reviewed activities of each working group • Clinical – Use Cases, User Stories, Clinical Information Models • Technical – Architectural principles, technical standards / specifications, design of pilot implementations • Business – best practices for privacy, data use, network partner coordination • Discussion on Implementation Workgroup activities
Clinical Working Group Update from 9/21 Meeting
Key Topics Covered/Discussed • Presented & Discussed Community User Story proposals • Inpatient & Outpatient • All Hazards User Story (Presented by Taha Kass-Hout) • Reviewed updated Generic User Story (Presented by Michael Buck) • The community was asked to provide feedback on the Generic User Story last week
Key Topics Covered/Discussed User Story Recap
Key Decisions & Next Steps Decisions • Michael Buck was chosen as Working Group lead. A second lead can be added in the future. • The Working Group members decided it would be best to have the Generic User Story be included as part of the Use Case supplemented by 1-2 additional User Stories. Work Assignments/Next Steps • Query Health Clinical Working Group Call for Consensus • Generic User Story • Ranking of User Stories • Deadline for submitting consensus vote is COB (8 PM ET) October 4th (TODAY!!)
Business Working Group Update from 9/28 Meeting
Key Topics Covered/Discussed • Defined Goals of Business Working Group • Documented and Detailed the Operations Requirements(was Business Requirements) for User Stories and inclusion in the Use Case and Requirements document being prepared by Clinical Working Group; • 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; • Preparation of 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) • Merideth Vida, Support Team Lead for the Clinical Working Group, presented an overview of the Query Health Generic User Story and invited the Business Workgroup members to review and provide feedback.
Business Working Group Key Decisions and Next Steps • Decisions • Alice Leiter chosen as Working Group lead. • Work Assignments/Next Steps • Review and populate the Operations Requirements Matrix spreadsheet (columns D and E) • Focus on Generic User Story • Review the Query Health Operations Requirements-Narrativedocument for context on business requirements • Review Generic User Story for any privacy/security implications that need documentation • Workgroup focused on providing Business Requirements for each user story and documenting additional requirements needed for distributed queries
Technical Working Group Update from 9/28 Meeting
Technical Workgroup Meeting Time Adjustment • The WG Lead is requesting a change in the meeting time to support a broader base of potential participants • Currently Wednesday 3-4pm ET or Thursday 2-3 pm ET are open and can be used with minimum conflicts with other initiatives. • Group will be polled for preferences and notice will be sent out
Technical WG Update • Discussed the Abstract Model in detail • Addressed the various discussion posts and followed up with others • Refined the abstract model based on the discussion • Refined the Query Life Cycle and added/clarified terminology
Query Lifecycle 1a Authorized Requestor Query Builder UX 1b 8 • Requestor optionally uses a query builder user interface to create a query and submits it to their dedicated orchestrator. • The orchestrator determines at what time and frequency the query should run (one time, monthly, etc.) and submits the query when appropriate to its agent. • Agent submits the query over the Internet to each participating responder’s gatewayand awaits responses. Gateways may provide a number of services: additional authorization, manual review, etc. • The standard gateway passes accepted requests to a site-specific adapter. • The adapter calculates site results for their site and returns them to the gateway. • The gateway returns site results to the appropriate agent. • The agent returns site results to the aggregator that combines site results into combined results • The aggregator makes interim and final results available to the requestor. 7 2 Aggregator Orchestrator Agent 3 6 Gateway Gateway 5 4 Adapter Adapter Clinical Data Clinical Data Responder “1” Responder “N” …
Next Steps and Actions • Posted the Abstract Model for Technical WG consensus • Don’t forget to review and vote by October 5, 2011 • Will be discussing the outcome of Abstract model consensus • Validate Abstract Model using User Stories from Clinical WG
Charter Voice Vote Approval? • All comments from the Initiative members have been received and dispositioned • Consistent and rigorous focus on access to clinical data sources for queries • Timeline driven by community as the workgroups evolve • Identification, not definition, of standards • Leverage and consideration of existing standards and technologies • Work has been done to ensure outreach to any individuals/organizations with NO votes • How would the Implementation Workgroup like to proceed?