Query Health Technical WG 9/28/2011

1. Query HealthTechnical WG9/28/2011

2. Agenda

3. Administrative Stuff and Reminders • Consensus vote on the Revised Project Charter – Email will be sent out shortly • Sign up for the S&I Framework F2F • - http://wiki.siframework.org/October+F2F+Meeting • October 18-19, 2011 • Hyatt Regency at Crystal City | 2799 Jefferson Davis Highway | Arlington, Virginia 22202 • WG Lead

4. Abstract Model Discussion • http://wiki.siframework.org/Query+Health+Abstract+Model+and+Terminology • Propose discussing the Abstract Model further today and address the posts and any other open issues that the WG participants identify • Capture the changes required to refine the Abstract Model so that we can move towards a final version of the Abstract Model • Set up a consensus vote to approve the abstract model and terminology for the Initiative

5. Discussion Items from Posts • Authorization vs Trust/Identity – Arien M/David M/John M/Jeff Brown • Support for Intermediate conversations between Agent and Gateway – Rob Rosen • Support for Intermediaries or Trusted Third Parties – Rob Rosen • Composer / Agent / Aggregator relationship – Marc Hadley • Query Envelope and Security/Trust Information – Marc H/Rob R • Support for multiple query types – Should there be a common minimum ? – Marc H • Periodic Time based queries (Publish/Subscribe) – Mike Buck • http://wiki.siframework.org/file/view/The%20Hub%20Query%20Examples%20PCIP.pdf • Notes on the Abstract Model - Bobby Lee • http://wiki.siframework.org/message/list/Query+Health+Abstract+Model+and+Terminology

6. Next Steps and Actions • Refine and Post the Abstract Model for Consensus at the WG level • Validate Abstract Model using User Stories and Sample Queries from Clinical WG • Should we start Technical Requirements work stream based on Use Cases and the Abstract Model ?

7. Reference Material

8. 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. Query Authorized Requestors Participating Responders

9. Query Lifecycle Authorized Requestor 1 7 Aggregator Composer 6 • Requestor optionally uses a composer to create a query and submits it to their dedicated agent. • Agent submits the query over the Internet to each participating responder’s gatewayand awaits responses. • At each participating responder, the standard gateway passes the request 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. Agent 2 5 Gateway Gateway 4 3 Adapter Adapter Clinical Data Clinical Data Responder “1” Responder “N” …

10. Query Envelope Query Response Responder identifier Response identifier (unique within responder space) Requestor identifier Query identifier Freeform notes for requestors (List of) Response Items Item name/tag Item status Item response payload • Requestor identifier • Query identifier (unique within requestor space) • Freeform notes for responders • Query type and version • (List of) Query Items • Item name/tag (unique within request) • Item request payload

11. 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

12. Using the Discussion Tab on Wiki to Leave Comments • Click on the “Discussion” tab • Select a discussion thread you would like to view or respond to • How to start a new thread: • Click “+ New Post” • Enter the “Subject” • Enter the post as the “Message” • Check “Monitor this topic” to receive e-mail notifications • Click “Post” • You can share a specific discussion by right-clicking on the title and copying the link