Query+Health+Quickstart+Page

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

On this Quickstart page, you will find resources, artifacts, and key deliverables pertaining to the Query Health initiative within the S&I framework, from background materials to use case summaries and educational artifacts. The purpose of this page is to provide users with a one-stop shop for all the consensus-approved documents and relevant materials so that they may get up to speed on the progress and next steps in the Query Health initiative.

media type="custom" key="11206848" align="right"
There are a number of important uses for distributed queries, including quality measures, disease outbreaks, comparative effectiveness analysis, efficacy of drug treatments and monitoring health trends. These are largely supported today by extracting data from source systems and integrating it into a centralized database where queries and analysis are managed. The Query Health initiative moves away from the centralizing tendency to “bring the data to the questions” to distributed population queries that “bring questions to the data.” Distributed queries provide access to data, for analysis purposes, while maintaining patient privacy and security by keeping protected health information safely behind healthcare organization firewalls. This will reduce the complexity of managing patient consent and authorizations, audit logs and access lists requirements.

The Query Health initiative will establish requirements for the clinical information model, distributed queries and results expression, with the objective of giving providers, consumers, researchers and others insight into prevention issues, healthcare research and disease outbreaks. Standards and services for distributed population queries will be selected to enable widespread adoption of the clinical information model and query capabilities. Use of these standards and services will result in increased speed and reduced transaction costs for stakeholders to analyze and apply information, ultimately reducing the cost of healthcare and improving the health of citizens.

==Background on the S&I Framework Query Health Initiative== If you are looking to get started with the Query Health initiative, start by reading some of the background materials produced. This will give you a good start at understanding the challenges of distributed queries, the approach taken by the S&I Framework to address these challenges, and the building blocks necessary as an implementer.

**I want to understand the context of this initiative and what community-led decisions were made** (click below for documents and links): The Use Case is the foundation for identifying and specifying the standards to support the data interoperability and developing reference implementations and tools to ensure consistent and reliable adoption of standards. ||< Final ||~  || 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. || Final ||~  || **I want to understand the clinical perspective in distributed queries** (click below for documents and links): -- ||~   || **I want to understand the technical perspective in distributed queries** (click below for documents and links): 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. ||< Final ||
 * **Type** || **Name** || **Description** ||< **Version** ||~ .................. ||
 * [[image:siframework/wiki_icon.png]] || Query Health Project Charter || The Project Charter outlines the purpose, scope, value statement, and target outcomes of the Query Health initiative. This document will provide a high level overview of the background, purpose, and goals of the initiative. ||< Final ||~  ||
 * [[image:siframework/wiki_icon.png]] || Query Health Use Case || The Use Cases describes the operational context for the data exchange, the stakeholders with an interest in the Use Case, the information flows that must be supported by the data exchange, and the types of data required in the data exchange.
 * [[image:siframework/wiki_icon.png]] || Query Health Abstract Model || The Query Health Abstract Model attempts to define the logical concepts, terms and actors involved in Query Health transactions.
 * **Type** || **Name** || **Description** ||< **Version** ||
 * [[image:siframework/wiki_icon.png]] || Generic User Story || The purpose of the generic user story is to provide a set of agreed upon business actors, abstract roles, elements, and processes for distributed queries. This generic user story will be used as a starting point and tailored for specific types of queries and responses from the user point of view. The functional requirements based on the user stories will need to take into account the variability of queries and information that may need to be exchanged, and this may be reflected in a richer set of requirements than a single user story may convey.
 * The content of this document has been incorporated in to the Use Case ||< Final ||
 * [[image:siframework/wiki_icon.png]] || Expanded Analysis User Story || The Expanded Analysis User Story was selected by the community as a more specific user story on which the Query Health initiative can focus. This user story focuses on Expanded Analysis for Diabetic Care in an Outpatient Setting.
 * The content of this document has been incorporated in to the Use Case ||< Final ||
 * [[image:siframework/wiki_icon.png align="left"]] || Functional Requirements || Functional Requirements identify the capabilities a system playing a role must have in order to enable interoperable exchange of the healthcare data of interest. This includes Information Interchange Requirements, System Requirements and Dataset Requirements.
 * The content of this document has been incorporated in to the Use Case ||< Final ||
 * [[image:siframework/word_icon.png]] || [|Query Health CEDD] || The Query Health Clinical Element Data Dictionary (CEDD) serves as a tool for implementers to use in setting up their source data in support of distributed queries. The CEDD serves as one building block within the larger Query Health solution, and is intended to give implementers a foundation of working specifications and examples. //Note: Currently on version 0.4.// || Draft ||
 * [[image:siframework/excel_icon.png]] || [|Query Health CEDD Crosswalk] || The Query Health CEDD describes the QH data elements, relationships, applicable data types, and how they are used in support of a specific query. The crosswalk is used to determine gaps where is there no data defined to support a sample query. || Final ||
 * **Type** || **Name** || **Description** ||< **Version** ||
 * [[image:siframework/wiki_icon.png]] || Query Health Abstract Model || The Query Health Abstract Model attempts to define the logical concepts, terms and actors involved in Query Health transactions.
 * [[image:siframework/wiki_icon.png align="center"]] || Query Health Proof of Concepts || The Query Health Proof of Concepts are the implementation approaches proposed for Query Health. These Proof of Concepts will lead to a solid technical foundation based on which standards and specifications will be derived and a solid reference implementation will be created. || Draft ||
 * [[image:siframework/wiki_icon.png]] || Query Analysis || The Query Analysis focuses on the possible approach to Quality Measure type queries; it specifically focuses on defining Query Conversions from standards notations to implementation notations. It will be rolled into the Proof of Concepts once finalized. || Draft ||
 * [[image:siframework/wiki_icon.png]] || Query Health Technical Approach || The goal of the technical approach document is to identify the following
 * Query Health specifications and standards that will promote interoperability among Query Health Network participants
 * Architecture Layers and Components that will lead to building a robust Query Health Reference Implementation that conforms to the Query Health specifications and standards while retaining the required flexibility to extend it for purposes beyond the prioritized pilot user stories. || Final ||

**I want to understand the operational perspective in distributed queries** (click below for documents and links):
 * **Type** || **Name** || **Description** ||< **Version** ||
 * [[image:siframework/word_icon.png]] || [|Query Health DUA - Final for Consensus - Updated 031212.doc] || The Query Health Data Use Agreement is a template that can be used by parties involved in data sharing as part of the Query Health Network. It is a living document that can be tweaked to the needs of both parties. It's ultimate purpose is to protect patient data. || Draft undergoing consensus ||
 * [[image:siframework/ppt_icon.png]] || [|OWG Technical Approach Primer Presentation] || The Operations Workgroup Technical Approach Primer provides an overview and breakdown of the Query Lifecycle and the steps of the Technical Approach. It is intended to provide a high level explanation of what occurs at each step, using non-technical language. || Final ||
 * [[image:siframework/wiki_icon.png]] || Query Health Technical Approach Risk Assessment || The Query Health Technical Approach Risk Assessment is based on the Technical Approach Primer and its purpose is to evaluate the Technical Approach from a Privacy, Policy, and Security standpoint. This wiki page is being converted into a forma list of recommendations. || Final ||

media type="custom" key="13278002"

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