Query Health Technical Working Group F2F meeting 10/17/2011 Agenda.

Slides:

Advertisements

Similar presentations

Query Health Pilots Sub-Work Group December 8, 2011.

Advertisements

DIRECT TRANSPORT FOR QH 10/18-19 F2F NOTES (SPN).

360Exchange (360X) Project 10/25/12. Reminders / announcements Mission / scope review Workgroup updates Implementation sites 1 Agenda.

S&I Framework Provider Directories Initiative esMD Work Group October 19, 2011.

Identity Management Based on P3P Authors: Oliver Berthold and Marit Kohntopp P3P = Platform for Privacy Preferences Project.

NHIN Direct Project Communications Work Group Message for State HIE/RECs August 30, 2010.

1 Privacy and Security Tiger Team Meeting Discussion Materials Topics Patient Authentication Hearing Questions for RFC on Meaningful Use Stage 3 October.

Query Health Technical WG 9/14/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders11:05 – 11:10 am Summer Concert Series Patterns Discussion11:10.

Edward Tsai – CS 239 – Spring 2003 Strong Security for Active Networks CS 239 – Network Security Edward Tsai Tuesday, May 13, 2003.

 MODERN DATABASE MANAGEMENT SYSTEMS OVERVIEW BY ENGINEER BILAL AHMAD

Microsoft ® Application Virtualization 4.6 Infrastructure Planning and Design Published: September 2008 Updated: February 2010.

Query Health Technical WG 8/2/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm Specification, RI and Pilot Updates2:05 – 2:20 pm Comparison between.

Query Health Business Working Group Kick-Off September 8, 2011.

Rich ElmoreCoordinator Merideth Vida Clinical Alice Leiter Operations “Dragon” Nageshwara Bashyam Technical ONC Annual Meeting: MU Training Day Query Health:

Query Health Distributed Population Queries Implementation Group Meeting January 31, 2012.

Query Health Distributed Population Queries Implementation Group Meeting March 13, 2012.

Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.

Query Health Distributed Population Queries Implementation Group Meeting October 4, 2011.

HIT Standards Committee HIT Standards Committee Privacy and Security Workgroup Discussion of NwHIN Power Team Recommendations August 6,

An XMPP (Extensible Message and Presence Protocol) based implementation for NHIN Direct 1.

OOI CyberInfrastructure: Technology Overview - Hyrax January 2009 Claudiu Farcas OOI CI Architecture & Design Team UCSD/Calit2.

Query Health Distributed Population Queries Implementation Group Meeting November 1, 2011.

Query Health Distributed Population Queries Implementation Group Meeting November 22, 2011.

Query Health Technical WG 3/1/2012. Agenda TopicTime Slot Administrative stuff and reminders2:00 – 2:05 pm HIMSS Update2:05 – 2:10 pm RI Update2:10 –

Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.

Query Health Technical WG 4/19/2012. Agenda TopicTime Slot Administrative stuff and reminders2:05 – 2:10 pm F2F Recap2:10 – 2:30 pm HQMF Translator UML2:30.

Query Health Distributed Population Queries Implementation Group Meeting October 25, 2011.

Module 9: Configuring IPsec. Module Overview Overview of IPsec Configuring Connection Security Rules Configuring IPsec NAP Enforcement.

Query Health Clinical Working Group Kick Off September 7, 2011.

Query Health Distributed Population Queries Implementation Group Meeting September 27, 2011.

Workshop Outputs and Goals Hannes Tschofenig Internet Privacy Workshop, December 2010.

Query Health Concept-to-Codes (C2C) SWG Meeting #12 March 6,

Query Health Technical WG 4/26/2012. Agenda TopicTime Slot Administrative stuff and reminders2:05 – 2:10 pm RI and Spec Updates2:10 – 2:20 pm HQMF to.

Query Health Distributed Population Queries Implementation Group Meeting January 17, 2012.

Clinical Quality Language (CQL) Bryn Rhodes Chris Moesel Mark Kramer.

1 CS 502: Computing Methods for Digital Libraries Lecture 19 Interoperability Z39.50.

Query Health Technical WG 10/13/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders2:05 – 2:10 pm Abstract Model Consensus Vote and Comments.

Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.

Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.

Query Health Technical WG 5/31/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm HQMF Schema and Sample Changes2:10.

Module 5: Designing Security for Internal Networks.

Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting August 1, 2011.

Query Health Distributed Population Queries Implementation Group Meeting October 11, 2011.

WSDL in a Healthcare Enterprise Architecture Lorraine Constable, Constable Consulting John Koisch, Guidewire Architecture Jean Henri Duteau, GPI.

Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting May 9, 2011.

MDPHnet & ESP Data Partner Participation Overview The following slides describe the necessary steps for a data partner to participate in the MDPHnet Network.

Query Health Distributed Population Queries Implementation Group Meeting February 7, 2012.

Query Health Distributed Population Queries Implementation Group Meeting December 13, 2011.

1 DAF Phase 3 Objective  Enable researchers to access data from multiple organizations and data sources within a Learning Health System (LHS) infrastructure.

Query Health Technical WG Update 12/1/2011. Agenda TopicTime Slot F2F Update (Actions, Decisions and FollowUps) 2:05 – 2:50 pm Wrap Up2:50 - 2:55 pm.

Query Health Technical WG Update 1/12/2011. Agenda TopicTime Slot Administrative stuff and reminders2:00 – 2:05 pm Specification Updates QRDA HQMF Query.

Query Health Technical WG 6/14/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm QRDA Discussion2:10 – 3:00 pm.

Query Health Distributed Population Queries Implementation Group Meeting November 15, 2011.

Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.

Query Health Distributed Population Queries Implementation Group Meeting March 6, 2012.

Query Health Technical WG 12/13/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm Specification, RI and Pilot Updates2:10 – 2:20 pm.

Query Health Technical WG 5/10/2012. Agenda TopicTime Slot Administrative stuff and reminders2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm HQMF Consensus.

Query Health Technical WG 11/10/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders2:00 – 2:10 pm Proof of Concept Update2:10 -2:20 pm.

Query Health Distributed Population Queries Implementation Group Meeting December 6, 2011.

Final Rule Regarding EHR Certification Flexibility for 2014 Today’s presenters: Al Wroblewski, Client Services Relationship Manager Thomas Bennett, Client.

Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.

IPSec is a suite of protocols defined by the Internet Engineering Task Force (IETF) to provide security services at the network layer. standard protocol.

Query Health Technical WG Update 1/5/2012. Agenda TopicTime Slot Administrative stuff and reminders2:00 – 2:05 pm Technical Approach Consensus Update.

Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.

Query Health Distributed Population Queries Implementation Group Meeting January 4, 2012.

Query Health Distributed Population Queries Implementation Group Meeting November 8, 2011.

Query Health Technical WG 10/27/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders2:00 – 2:05 pm F2F Recap2:05 – 2:15pm Query Analysis.

Query Health Abstract Model Diagrams. Query Network Community of participants that agree to interact with each other. There will be many networks; requestors.

1 CDC Health Information Exchange (HIE) Accelerating State-wide Public Health Situational Awareness in New York Through Health Information Exchanges August.

Building Enterprise Applications Using Visual Studio®

Presentation transcript:

Query Health Technical Working Group F2F meeting 10/17/2011 Agenda

Our Mission for the F2F Get to know each other and forge the relationships we’ll need to get through the project successfully Agree on how to agree --- what are the key attributes of the right technical solution? Break the problem down into parallel sub-projects Self-select into groups to work on these projects Have fun and change the world!

Rough Agenda: Tuesday TUESDAY8:00amKeynotes 9:00amQH Overview (full QH Team) 10:00amDoug 11:00amTWG Kickoff NoonLunch Stuff 1:30pmToC Overview & Decision-Making Criteria 3:00pmBreak 3:15pmExisting Tech Overview (40 minute blocks) hQuery, Hub, NwHIN 4:45pmAdjourn

Rough Agenda: Wednesday WEDNESDAY8:00amExisting Tech Overview (40 minute blocks) I2b2, PopMedNet 10:00amBreak 10:15amExisting Tech Overview (40 minute blocks) OMOP, UPHN NoonLunch Stuff 1:30pmSelf-select into working groups 3:00pmBreak 3:15pmRecap and determine next steps 4:30pmReport out (full QH team) 5:30pmAdjourn * Note: Sean AWOL before noon and after 3:40pm

FIRST CONSENSUS! QUERY HEALTH ABSTRACT MODEL

Query Network Community of participants that agree to interact with each other. There will be many networks; requestors and responders may participate in multiple networks. The network will enforce an initial, but not necessarily final, authorization boundary. Authorized Requestors Participating Responders Query

Query Lifecycle 1.Requestor optionally uses a query builder user interface to create a query and submits it to their dedicated orchestrator. 2.The orchestrator determines at what time and frequency the query should run (one time, monthly, etc.) and submits the query when appropriate to its requestor agent. 3.Requestor agent submits the query over the Internet to each participating organization’s responder agent and awaits responses. Responder agents may provide a number of services: additional authorization, manual review, etc. 4.The responder agent calculates site results using the appropriate data sources. 5.The responder agent returns site results to the appropriate requestor agent. 6.The requestor agent returns site results to the aggregator that combines site results into combined results 7.The aggregator makes interim and final results available to the requestor. Requestor Agent Responder Agent Responder Agent Query Builder UX Aggregator Source Data Authorized Requestor 1a 1b Responder “1”Responder “N” … Orchestrator 2 7 Note: All communication between Requestors and Responders are asynchronous.

Query Envelope Query Requestor identifier Query identifier (unique within requestor space) Security and Privacy Context (auth, privacy, etc.) Optional recurrence information to support repeated queries Freeform notes for responders Query type and version Query Payload Response Responder identifier Response identifier (unique within responder space) Requestor identifier Query identifier Freeform notes for requestors Results Usage policy information Response Payload

Query Payload Query Health supports multiple “query types” traveling over the same transport and envelope* Types are identified by a name and version – E.g., “MU Stage 1 EP/1.0” Each type implies – Query syntax – Clinical information model – Response format *Goal is to support two types in pilots; one very simple and one more complex to support the clinical workgroup user stories.

SESSIONS

Sub-project types: Should be plug&play Transport – Define the way queries and responses will move around Query Type: Measures – Define query and response payloads for measure-based queries (e.g., MU stage 1 by name). How will we standardize the universe of measures, input parameters, and output format? Query Type: Granular / ToC CIM – Define query and response payloads for queries that involve computation against a defined clinical model (e.g., hQuery Javascript or just SQL). Authentication & Policy Expression – This is a bit more vague … how to represent in the envelope the information required to authenticate queries and communicate inbound and outbound usage policies?

How to agree? Strawman criteria: Vendor-neutral Asynchronous Scalable (Computation) Scalable (Operation) Extensible Developer-friendly / approachable Minimal new technology (both conceptual and physical) Leverages existing work/standards (NwHIN, ToC CIM, etc.) Policy-friendly (e.g., manual review) Achievable with existing EHRs Has volunteer resources for a reference implementation!