Query+Health+Abstract+Model+and+Terminology

include component="page" wikiName="siframework" page="Query Health Header"



The wiki page will be used to facilitate the creation of the abstract model and discussions surrounding the abstract model which will aid in the development and recommendation of standards and specifications that will be used by Query Health.

__The Abstract Model was approved by the Technical WG Call for Consensus of the Abstract Model (Round 2) which ended on 10/12/2011 11:59 pm PT__

=Overview= The Query Health Abstract Model attempts to define the logical concepts, terms and actors involved in Query Health transactions. = = =Purpose= The purpose of the Abstract Model is to provide the Query Health Initiative with a common terminology for communication within and across the work groups. In addition the Abstract Model will serve as the conceptual model that will be used to further elaborate and recommend Query Health standards, services and components. = = =Terms=

//__Query Network__//: The Query Network represents a 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 Requestor__//: An authorized Query Network participant who issues a query to Participating Responders on the Query Network.

//__Participating Responder__//: A Query Network participant who intends to respond to the query issued by a requestor.

A simplified view of the Query Network, Authorized Requestors and Participating Responders are as shown in Figure 1 below:



__//Figure 1: Query Network//__

//__Query Lifecycle__//: The Query Lifecycle represents the interactions between the Authorized Requestors and Participating Responders using logical concepts that will aid in the elaboration and recommendation of Query Health standards, services and components. The Query Lifecycle is shown in Figure 2 along with simple descriptions of actions performed in each step.



__//Figure 2: Query Lifecycle//__

//__Query Builder UX__//: The Query Builder UX when used provides an easy to use interface to Authorized Requestors to build queries that will be submitted to Participating Responders.

//__Orchestrator__//: The Orchestrator is responsible for determining at what time and frequency the query should run (one time, monthly, etc) and submitting the query when appropriate to its Agent.

//__Requestor Agent__//: The Requestor Agent is responsible for submitting the queries to the Participating Responders via the Responder Agents and collect responses from the Responder Agents.

//__Responder Agent__//: Responder Agents receive the queries from Requestor Agents and calculate the site results using appropriate source data. Before calculating the site results, the Responder agents will perform initial identity validation and may perform additional services such as authorization checks, manual review of queries etc. The Requestor Agent and the Responder Agents establish the necessary secure transport channels between the Authorized Requestor and Participating Responders to facilitate sending and receiving of queries, results etc.

Note: All communication between the Authorized Requestors and Participating Responders are asynchronous.

//__Aggregator__//: The Aggregator receives interim and final results from the Agents and makes them available to the Authorized Requestor. Before making the results available, the Aggregator may perform additional functions like mixing of results, masking of certain information from the results etc.

//__Query Envelope__//: The Query Envelope represents the container that will be used to hold the query requests and query results in a Query Network.

Sample Query Envelopes for requests and responses are as Figure 3 below. These are just samples and the exact details of the data elements, their structure and formats etc. will be determined as the Initiative progresses.



__//Figure 3: Query Envelope//__

//__Query Type__//: The Query Type provides the flexibility required for Query Health Initiative to facilitate different query syntaxes, clinical models and results sets. Query Type implies the following:
 * <span style="font-family: Arial,Helvetica,sans-serif;">Query Syntax
 * <span style="font-family: Arial,Helvetica,sans-serif;">Clinical Information Model
 * <span style="font-family: Arial,Helvetica,sans-serif;">Response Format

<span style="font-family: Arial,Helvetica,sans-serif;">An example Query Type is “MU Stage 1 EP/1.0” which is specified and defined in Meaningful Use Stage 1 regulation. <span style="font-family: Arial,Helvetica,sans-serif; font-size: 14.6667px;">The Query Health Initiative goal is to support at least two Query Types (one simple and one complex) based on the User Stories prioritized by the clinical work group.

Members Developing and Refining the Artifact

 * Member Name || Organization ||
 * Eric Heflin || Medicity, IHE, NwHIN ||
 * Marc Hadley || MITRE ||
 * Sean Nolan || Microsoft ||
 * Steve Felt || Greenway ||

**Reference Materials:**
The following are different versions of presentations that have been discussed and updated based on the discussions within the Technical WG and the discussion posts. These materials are the primary source of the above abstract model concepts.

Version 4; Based on 10/6/2011 Technical WG Discussion. [|Query Health Abstract Model draft 20111010 v4.pptx]

Version 3; will discuss for consensus next week. ---S [|Query Health Abstract Model draft SPN 20110930 v3.pptx]

New diagrams based on discussion. ---S [|Query Health Abstract Model draft SPN 20110920 v2.pptx]

For discussion, I created three diagrams that may be useful in defining the terminology of actors from broad to granular --- goal being to have enough detail to start to make tradeoffs and choices, but leaving room for the possible architectures we've seen to date. Feedback and improvements welcome in the discussion tab of this page. ---Sean Nolan [|Query Health Abstract Model draft SPN 20110916.pptx]

The Primary Care Information Project's Hub System as presented during the Summer Concert Series produced the following [|The Hub Query Examples PCIP.pdf] It contains a PDF of hundreds of quality metric, meaningful use, and public health related distributed queries that were built in the Hub system or anticipated in the future. All of these examples could be built using this Generic User Story. These examples could be used by the committees as a starting point to help define the domain of queries for the Query Health project. [|The Hub Query Examples PCIP.pdf]
 * Distributed Query Examples**

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"