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
(New page: =Product Brief - Infobutton= __TOC__ back to Main_Page<br/>back to Product_List ==Product Name== HL7 Version 3 Standard: Context-aware Information Retrieval (Infobutton), Release ...)
 
Line 5: Line 5:
  
 
HL7 Version 3 Standard: Context-aware Information Retrieval (Infobutton), Release 1
 
HL7 Version 3 Standard: Context-aware Information Retrieval (Infobutton), Release 1
Last Ballot: DSTU Ballot 1 - January 2008
+
<br/>Topic of Clinical Decision Support Domain
 +
 
  
 
===Topics===
 
===Topics===
 
*
 
*
 
===Standard Category===
 
===Standard Category===
*
+
*Health Information Exchange Standards
 
===Integration Paradigm===
 
===Integration Paradigm===
 
*Messaging
 
*Messaging
 
===Type===
 
===Type===
DSTU (pursuing Normative ballot)
+
Normative, ANSI Standard
  
 
===Releases===
 
===Releases===
HL7 V3 INFOBUTTON, R1, DSTU (ends Jan 2010)
+
ANSI/HL7 V3 INFOB, R1-2010
  
 
===Summary===
 
===Summary===
 +
An 'infobutton' is a point-of-care information retrieval application that automatically generates and sends queries to on-line health information resources ('e-resources') using patient data extracted from the electronic medical record and background information ('context') that is captured from the interaction between a clinical user and a clinical information system (e.g., user role, patient age and gender, task being performed by the user).
  
 +
This specification focuses on a context-aware knowledge retrieval transaction, primarily on the Knowledge Request step, representing a Context-aware knowledge request event initiated by the EHR (e.g., as a result of a user clicking on an Infobutton). The storyboard also includes the knowledge response step in which a knowledge resource fulfills a knowledge request. The latter step will be covered in a separate future specification.
  
 
===Description===
 
===Description===
 +
An 'infobutton' is a point-of-care information retrieval application that automatically generates and sends queries to on-line health information resources ('e-resources') using patient data extracted from the electronic medical record and background information ('context') that is captured from the interaction between a clinical user and a clinical information system (e.g., user role, patient age and gender, task being performed by the user). Currently, e-resources typically provide HTTP-based Application Program Interfaces (API) that can be used by infobuttons. However, these APIs are based on proprietary syntax and vocabularies, requiring the development of custom software for each e-resource that an infobutton needs to link to. The goal of this proposal is to facilitate the implementation of infobuttons by supporting the integration between Clinical Information Systems and e-resources.
  
 +
The Knowledge resource response to an infobutton knowledge request message payload for this interaction is outside the scope of this specification.
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
 
+
Vendors: Health Care IT, Decision Support
  
 
===Benefits===
 
===Benefits===
 
+
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. Online health knowledge resources that are capable of solving many of these knowledge needs are now widely available, but a series of barriers hinder a more effective and frequent use of these resources at the point of care. Infobuttons are decision support tools that integrate knowledge resources into electronic health record (EHR) and personal health record (PHR) systems as an attempt to lower these barriers. To facilitate the integration of knowledge resources into EHR and PHR systems, the Clinical Decision Support Technical Committee developed the Context-aware knowledge retrieval (Infobutton) standard specification.
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
Line 48: Line 53:
 
===Links to current projects in development===
 
===Links to current projects in development===
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=130 Project Insight ID # 130], Infobutton URL-based implementation guide
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=130 Project Insight ID # 130], Infobutton URL-based implementation guide
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=265 Project Insight ID # 265], Infobutton Standard.
+
* Project Insight ID # 265 (archived), Infobutton Standard.
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=507 Project Insight ID # 507],Context Aware Information Retrieval (Infobutton) SOA Implementation Guide.
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=507 Project Insight ID # 507],Context Aware Information Retrieval (Infobutton) SOA Implementation Guide.
  
  
==Product Name - HL7 V3 IG: Context-Aware Information Retrieval (Infobutton) Release 1==
+
==Product Name - HL7 V3 IG: Context-Aware Information Retrieval (Infobutton)==
*HL7 V3 Implementation Guide: Context-Aware Information Retrieval (Infobutton) Domain
+
*HL7 V3 Implementation Guide: Context-Aware Information Retrieval (Infobutton) (Topic of Clinical Decision Support Domain)
  
 
===Type===
 
===Type===
Line 59: Line 64:
  
 
===Releases===
 
===Releases===
*HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 1 (2007)
+
HL7 V3 INFOBUTTON, R1
*HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 2 (2008)
+
 
*HL7 V3 Implementation Guide: URL-based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 3
+
*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===
 
===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 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.
 +
 +
===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.
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
Line 70: Line 80:
  
 
===Benefits===
 
===Benefits===
 +
The main goal of this implementation approach is to support compatibility with most EHR and knowledge resource implementations, maximizing adoption.
 +
This document assumes kznowledge 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.
 
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.
  
Line 86: Line 99:
 
Links to current projects in development
 
Links to current projects in development
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=130 Project Insight ID # 130], Infobutton URL-based implementation guide
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=130 Project Insight ID # 130], Infobutton URL-based implementation guide
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=265 Project Insight ID # 265], Infobutton Standard.
+
* Project Insight ID # 265 (archived), Infobutton Standard.
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=507 Project Insight ID # 507],Context Aware Information Retrieval (Infobutton) SOA Implementation Guide.
 
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=507 Project Insight ID # 507],Context Aware Information Retrieval (Infobutton) SOA Implementation Guide.

Revision as of 00:51, 12 August 2010

Product Brief - Infobutton

back to Main_Page
back to Product_List

Product Name

HL7 Version 3 Standard: Context-aware Information Retrieval (Infobutton), Release 1
Topic of Clinical Decision Support Domain


Topics

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Messaging

Type

Normative, ANSI Standard

Releases

ANSI/HL7 V3 INFOB, R1-2010

Summary

An 'infobutton' is a point-of-care information retrieval application that automatically generates and sends queries to on-line health information resources ('e-resources') using patient data extracted from the electronic medical record and background information ('context') that is captured from the interaction between a clinical user and a clinical information system (e.g., user role, patient age and gender, task being performed by the user).

This specification focuses on a context-aware knowledge retrieval transaction, primarily on the Knowledge Request step, representing a Context-aware knowledge request event initiated by the EHR (e.g., as a result of a user clicking on an Infobutton). The storyboard also includes the knowledge response step in which a knowledge resource fulfills a knowledge request. The latter step will be covered in a separate future specification.

Description

An 'infobutton' is a point-of-care information retrieval application that automatically generates and sends queries to on-line health information resources ('e-resources') using patient data extracted from the electronic medical record and background information ('context') that is captured from the interaction between a clinical user and a clinical information system (e.g., user role, patient age and gender, task being performed by the user). Currently, e-resources typically provide HTTP-based Application Program Interfaces (API) that can be used by infobuttons. However, these APIs are based on proprietary syntax and vocabularies, requiring the development of custom software for each e-resource that an infobutton needs to link to. The goal of this proposal is to facilitate the implementation of infobuttons by supporting the integration between Clinical Information Systems and e-resources.

The Knowledge resource response to an infobutton knowledge request message payload for this interaction is outside the scope of this specification.

Business Case (Intended Use, Customers)

Vendors: Health Care IT, Decision Support

Benefits

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. Online health knowledge resources that are capable of solving many of these knowledge needs are now widely available, but a series of barriers hinder a more effective and frequent use of these resources at the point of care. Infobuttons are decision support tools that integrate knowledge resources into electronic health record (EHR) and personal health record (PHR) systems as an attempt to lower these barriers. To facilitate the integration of knowledge resources into EHR and PHR systems, the Clinical Decision Support Technical Committee developed the Context-aware knowledge retrieval (Infobutton) standard specification.

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Clinical Decision Support

Education

Certification Available
  • none

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development


Product Name - HL7 V3 IG: Context-Aware Information Retrieval (Infobutton)

  • HL7 V3 Implementation Guide: 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 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.

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.

Business Case (Intended Use, Customers)

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

Benefits

The main goal of this implementation approach is to support compatibility with most EHR and knowledge resource implementations, maximizing adoption. This document assumes kznowledge 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)

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