This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Product Infobutton"

From HL7Wiki
Jump to navigation Jump to search
Line 14: Line 14:
 
*Health Information Exchange Standards
 
*Health Information Exchange Standards
 
===Integration Paradigm===
 
===Integration Paradigm===
*Messaging
+
*Web Services
 
===Type===
 
===Type===
 
Normative, ANSI Standard
 
Normative, ANSI Standard
Line 86: Line 86:
 
*HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain; Infobutton Request,  Release 3 (Jan 2010)
 
*HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain; Infobutton Request,  Release 3 (Jan 2010)
 
===Summary===
 
===Summary===
The approach outlined in this implementation guide allows Infobutton event notification and information resource event notification message payloads to be converted from an XML format to a URL-based format using a simple automated process. Specifically, the implementation guide's rules allow an XML-based Infobutton message model message payload to be converted to a set of parameters that can be included in an HTTP request using GET or POST methods.
+
The approach outlined in this implementation guide allows Infobutton knowledge requests to be converted represented in a URL-based format. The URL parameter names are derived from element names used in the ''Infobutton, Knowledge Request'' XML schema based on a simple set of rules.  
  
 
===Description===
 
===Description===
This implementation guide provides a specification for URL-based implementations of the Context-aware knowledge retrieval (Infobutton) standard. The intent of this specification is to support the majority of knowledge retrieval implementations that offer URLs as the primary or exclusive communication protocol. The ultimate goal is to enable a stepwise transition from URL-based implementations to a services-oriented approach.
+
This implementation guide provides a specification for URL-based implementations of the Context-aware knowledge retrieval (Infobutton) standard. The intent of this specification is to support the majority of knowledge retrieval implementations that offer URLs as the primary or exclusive communication protocol. The ultimate goal is to enable a stepwise transition from URL-based implementations to a services-oriented approach. This implementation guide was successfully balloted as a Draft Standard for Trial Use in January 2008. Since then, a large number of implementations became available, allowing the specification to be thoroughly validated and tested. In January 2010, an updated specification was balloted and approved as an HL7 International standard.  
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
Line 96: Line 96:
  
 
===Benefits===
 
===Benefits===
The main goal of this implementation approach is to support compatibility with most EHR and knowledge resource implementations, maximizing adoption.
+
The primary goal of this implementation approach is to support compatibility with most EHR and knowledge resource implementations, which exclusively support URLs as a communication protocol.  
This document assumes knowledge of the Context-aware Knowledge Retrieval (Infobutton) standard normative specification.
 
 
 
The intent of this recommendation is to support backwards compatibility with the majority of the infobutton and information resources that exclusively support URLs as the communication protocol. The ultimate goal is to enable a stepwise transition from URL-based implementations to an HL7 Implementation Technology Specification (ITS). Nevertheless, it is not the intent of this document to create a URL-based HL7 ITS.
 
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
 
+
This implementation has received wide adoption in the United States. Most large knowledge publishers have implemented this specification. Most of the large EHR vendors also have at least some level of compliance to the URL-based specification. More advanced implementations are available at institutions with home-grown systems, such as Intermountain Healthcare, Partners Helathcare, Columbia University, and the Veterans Health Administration. Yet, more recently, EHR vendors have been starting to provide more advanced knowledge retrieval / infobutton applications.
  
 
===Resources===
 
===Resources===

Revision as of 17:22, 4 November 2010

Product Brief - Context-Aware Knowledge Retrieval (Infobutton)

back to Main_Page
back to Product_List

Product Name - HL7 Version 3 Standard: Context-aware Information Retrieval (Infobutton), Release 1

  • HL7 V3 Standard: Context-Aware Information Retrieval (Infobutton) Knowledge Request, Release 1


Topic of Clinical Decision Support Domain


Topics

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Web Services

Type

Normative, ANSI Standard

Releases

ANSI/HL7 V3 INFOB, R1-2010

Summary

Clinicians face numerous knowledge needs during the course of patient care and the majority of these needs are not met, compromising the quality of care. Likewise, in order to be partners in the decision making process, patients need to be well-informed about their health and health care options. Online health knowledge resources that are capable of solving clinicians’ and patients’ knowledge needs are now widely available, but a series of barriers hinder a more effective and frequent use of these resources to support decision-making. Context-aware knowledge retrieval into Clinical Information Systems (CIS), such as Electronic Health Record (EHR) and Personal Health Record (PHR) systems, is an increasingly promising approach for delivering relevant clinical knowledge to the point of care as well as patient-tailored educational material to support patient-centered care. These kinds of knowledge retrieval tools have been known as "Infobuttons."

To support the integration of knowledge resources into CISs, the Clinical Decision Support Work Group (CDS WG) has been developing a set of standard specifications for context-aware knowledge retrieval. The first of these specifications, entitled Context-Aware Knowledge Retrieval (Infobutton), Knowledge Request Standard, was approved in September 2010 as a normative ANSI/ISO HL7 standard. This specification provides a standard mechanism for Clinical Information Systems to submit knowledge requests to knowledge resources. In addition, a URL-based implementation guide has been developed to specify knowledge request implementations using the HTTP protocol.

Description

The core artifact of the Infobutton, Knowledge Request is an information model (Refined Message Information Model, or simply RMIM) that defines the structure and semantics of a context-aware knowledge request. In essence, the RMIM provides a standardized representation of the context of an interaction between a user and a CIS. Context is represented in the RMIM in terms of the following dimensions: patient (e.g., gender, age, main primary concept of interest), user (e.g., patient vs. provider, discipline), care setting (e.g., inpatient, outpatient), and CIS task (i.e., order entry, lab results review). Knowledge resources that implement this standard become context-aware in the sense that they are able to receive, process, and make inferences over the context in order to retrieve relevant, context-specific knowledge content in any particular context.

The RMIM is technology agnostic. For implementation purposes, two representation mechanisms have been defined: URL-based representation and XML. The RMIM automatically generates an XML schema that can be used by implementers to create and validate knowledge requests.

The Context-Aware Knowledge Retrieval (Infobutton), Knowledge Request Standard can be implemented through the following representation and transport mechanisms:

  • As a URL using HTTP GET or POST (see Context-Aware Knowledge Retrieval, URL-Based Implementation Guide for details)
  • As a Web Service

The Context-Aware Knowledge Retrieval, URL-Based Implementation Guide and the Context-Aware Knowledge Retrieval, Service-Oriented Architecture Implementation Guide provide these implementation details.

Business Case (Intended Use, Customers)

  • Clinical Information System developers
  • Clinical knowledge resource publishers
  • Clinical Decision Support developers
  • Health care organizations


Benefits

To improve quality of care by providing clinicians with seamless access to up-to-date clinical knowledge at the point of decision-making. To support patient-centered care by enabling patients to be partners in the decision-making process.



Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Clinical Decision Support

Education

Relationship to/ Dependencies on, other standards

Links to current projects in development


Product Name - HL7 V3 IG: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton)

  • HL7 V3 Implementation Guide: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton) (Topic of Clinical Decision Support Domain)

Type

Informative (IG)

Releases

HL7 V3 INFOBUTTON, R1

  • HL7 Version 3 Implementation Guide: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 1 - 2/1/2007
  • HL7 Version 3 Implementation Guide: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 2 - 6/2/2008
  • HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain; Infobutton Request, Release 3 (Jan 2010)

Summary

The approach outlined in this implementation guide allows Infobutton knowledge requests to be converted represented in a URL-based format. The URL parameter names are derived from element names used in the Infobutton, Knowledge Request XML schema based on a simple set of rules.

Description

This implementation guide provides a specification for URL-based implementations of the Context-aware knowledge retrieval (Infobutton) standard. The intent of this specification is to support the majority of knowledge retrieval implementations that offer URLs as the primary or exclusive communication protocol. The ultimate goal is to enable a stepwise transition from URL-based implementations to a services-oriented approach. This implementation guide was successfully balloted as a Draft Standard for Trial Use in January 2008. Since then, a large number of implementations became available, allowing the specification to be thoroughly validated and tested. In January 2010, an updated specification was balloted and approved as an HL7 International standard.

Business Case (Intended Use, Customers)

  • Vendors: Health Care IT,
  • Vendors: Decision Support

Benefits

The primary goal of this implementation approach is to support compatibility with most EHR and knowledge resource implementations, which exclusively support URLs as a communication protocol.

Implementations/ Case Studies (Actual Users)

This implementation has received wide adoption in the United States. Most large knowledge publishers have implemented this specification. Most of the large EHR vendors also have at least some level of compliance to the URL-based specification. More advanced implementations are available at institutions with home-grown systems, such as Intermountain Healthcare, Partners Helathcare, Columbia University, and the Veterans Health Administration. Yet, more recently, EHR vendors have been starting to provide more advanced knowledge retrieval / infobutton applications.

Resources

Work Groups Clinical Decision Support

Relationship to/ Dependencies on, other standards

  • Infobutton
  • The URL-based representation is derived directly from the Infobutton message model RMIM.

Links to current projects in development



Product Name - HL7 V3 Implementation Guide: Context-Aware Knowledge Retrieval (Infobutton) - Service-Oriented Architecture Implementation Guide

  • HL7 Version 3 Implementation Guide: DSS Knowledge Module Implementation of the Context-Aware Information Retrieval (Infobutton) Domain, Release 1; **alternate names:
    • Context-Aware Knowledge Retrieval (Infobutton) - Decision Support Service (DSS) Implementation Guide, or
      HL7 V3 Implementation Guide: Context-Aware Knowledge Retrieval (Infobutton) - Service-Oriented Architecture, Release 1

Type

DSTU ballot 2011Jan

Releases

Summary

The present specification complements the previous ones by enabling the implementation of context-aware knowledge retrieval applications through a Service-Oriented Architecture (SOA) based on the SOAP (Simple Object Access Protocol) protocol and the REST (Representational State Transfer) software architecture style.

Description

The SOA Implementation Guide for context-aware information retrieval ('Infobutton') leverages the HL7 Decision Support Services (DSS) standard. More specifically, the scenarios and interactions defined in the proposed specification will be implemented as a DSS 'knowledge module.' This project focuses on the specification of a DSS module to support a SOA-based integration of knowledge resources into electronic health records. The proposed implementation guide will not specify the payloads of the Infobutton DSS knowledge module. The knowledge module payloads have been / will be defined elsewhere in HL7 normative specifications, including the Context-aware Information Retrieval (Infobutton) DSTU. These work products will be developed independently of, and in parallel with this SOA implementation guide. 1) The SOA IG will be an instance (a.k.a., knowledge module) of the broader DSS Standard. 2) Unlike the present Infobutton DSTU (Project 265), the SOA IG will support back and forth communication between EHRs, Infobutton Managers, and knowledge resources. Resources will be able to respond in a standardized fashion, which is not supported by the present Infobutton DSTU. 3) The Infobutton DSTU will serve as the payload for knowledge request operations in SOA implementations. 4) SOA-enabled knowledge resources will respond with a knowledge retrieval metadata payload, which is being developed in parallel to the SOA IG

1) Knowledge response specification was improved, with significant detail added. 2) Examples were added and updated based on changes to the Context-Aware Knowledge Retrieval, Knowledge Request Standard that was balloted in May 2010. 3) Specification and examples were updated based on recent updates to the HL7/OMG Decision Support Services specification.Specify a service-oriented implementation approach for context-sensitive knowledge integration into clinical information systems leveraging the HL7/OMG Decision Support System (DSS).

Business Case (Intended Use, Customers)

  • Clinical Information System developers
  • Clinical knowledge resource publishers
  • Clinical Decision Support developers
  • Health care organizations

Benefits

Specify a service-oriented implementation approach for context-sensitive knowledge integration into clinical information systems leveraging the HL7/OMG Decision Support System (DSS).

Implementations/ Case Studies (Actual Users)

Resources

Work Groups Clinical Decision Support

Relationship to/ Dependencies on, other standards

  • Infobutton
  • DSS

Links to current projects in development