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

Difference between revisions of "Product IM"

From HL7Wiki
Jump to navigation Jump to search
(New page: ==Product Brief - == back to Main_Page<br/>back to Product_List ===Product Name=== ===Topics=== * ===Standard Category=== * ===Integration Paradigm=== * ===Type=== ===Releases=...)
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
==Product Brief - ==
+
=Product Brief - HL7 V3: Infrastructure Management=
 +
__TOC__
 
back to [[Main_Page]]<br/>back to [[Product_List]]
 
back to [[Main_Page]]<br/>back to [[Product_List]]
 
===Product Name===
 
===Product Name===
 +
HL7 V3: Infrastructure Management - R1
  
 +
===Topics===
 +
*Message Control Infrastructure (MCAI v1 & v2)
 +
*Message Control Act Infrastructure (MCAI V3 ff)
 +
*Transmission Infrastructure(MCCI)
 +
**Generic Message Transmission
 +
**Polling Message Transmission
 +
**Batch Wrapper
 +
*Master File/Registry Infrastructure(MFMI)
 +
** This adds artifacts to the Message Control Act Infrastructure, and is dependent upon it.
 +
*Query Infrastructure(QUQI)
  
−
===Topics===
 
−
*
 
 
===Standard Category===
 
===Standard Category===
−
*
+
*Health Information Exchange Standards
 
===Integration Paradigm===
 
===Integration Paradigm===
−
*
+
*Messaging
 
===Type===
 
===Type===
 +
Normative, ANSI Standard
  
 +
===Releases===
 +
*ANSI/HL7 V3 IM, R1-2004
 +
*UVAI: Infrastructure Management - Message Control Act Infrastructure
 +
*UVCI: Infrastructure Management - Transmission Infrastructure
 +
*ANSI/HL7 V3 MFMI, R1-2006; HL7 MFMI, R2.  HL7 Version 3 Standard: Master File - Registry Infrastructure, Release 2
 +
Last Ballot: DSTU Ballot 1 - September 2008
  
−
===Releases===
+
===Summary===
 +
The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions.
  
 +
This domain addresses the following aspects about the communications environment that is considered common to all HL7 Version 3 messaging implementations:
  
−
===Summary===
+
A specification for the composite HL7 version 3 message
 +
A protocol for reliable message delivery
 +
Generic "Communication Roles" that support the modes of HL7 messaging
 +
Message control events that describe a framework for generic HL7 messaging 
  
 +
This document focuses on the development and management of the infrastructure of the V3 standard. It includes information from the Transmission Infrastructure, Control Act Infrastructure, Master File Infrastructure and the Query Infrastructure domains.
  
 
===Description===
 
===Description===
 +
Scope: Message control in the HL7 Version 3 messaging standard addresses
 +
*The HL7 domain content for transport
 +
*The identification of sending and receiving entities for an HL7 messaging interaction.
 +
*The relationship between interactions and generic "communication roles"
 +
*Generic Communication Environment for HL7 Messaging in Version 3
 +
 +
The primary purpose of the HL7 messaging standard is to support the exchange of common information content between healthcare applications. As a protocol at Level Seven of the ISO Open Systems Interconnection (OSI) model, HL7 relies upon well-defined protocols at the lower layers for mechanisms that ensure correct and complete packaging and delivery of message content.
 +
 +
A generic communication environment for HL7 messaging has the following characteristics:
 +
*A specification for messages that supports the routing of messages to their specified destination(s)
 +
*A protocol for reliable message delivery that can support
 +
*An acknowledgment mode indicating if a message was delivered for subsequent processing
 +
*An acknowledgment mode indicating if a message was delivered to a specific application that acknowledges the receipt with or without a response prepared to return to the originating application
 +
*An optional sequence number protocol to ensure messages are processed in a specific order when necessary
 +
*Error handling rules for use cases consistent with HL7 messaging
 +
*Security services that are consistent with the current technology capabilities
  
 +
To implement HL7 Version 3 messaging, the Version 3 messaging standard must be able to
 +
*specify how messaging communications should be conducted
 +
*respond to exceptions or errors that are experienced by a generic messaging framework that is processing an HL7 messaging interaction
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
Line 33: Line 75:
  
 
====Work Groups====
 
====Work Groups====
−
http://www.hl7.org/Special/committees/xyz/index.cfm
+
[http://www.hl7.org/Special/committees/inm/index.cfm Infrastructure and Messaging]
 
====Education====
 
====Education====
−
*
 
 
* See more at http://www.hl7.org/implement/training.cfm
 
* See more at http://www.hl7.org/implement/training.cfm
 
=====Certification Available=====
 
=====Certification Available=====
Line 45: Line 86:
 
*
 
*
 
===Links to current projects in development===
 
===Links to current projects in development===
−
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=xxx Project Insight ID # xxx],
+
* There are no current projects
 +
** Infoway is in the process of identifying how SAEAF/SOA work through the first service specifications.
 +
** Seems to be an overlap with SOAP wrappers.
 +
** Infoway will be looking at this in January 2010 to discuss plans at the Phoenix 2010 WGM.

Latest revision as of 20:38, 26 October 2009

Product Brief - HL7 V3: Infrastructure Management

back to Main_Page
back to Product_List

Product Name

HL7 V3: Infrastructure Management - R1

Topics

  • Message Control Infrastructure (MCAI v1 & v2)
  • Message Control Act Infrastructure (MCAI V3 ff)
  • Transmission Infrastructure(MCCI)
    • Generic Message Transmission
    • Polling Message Transmission
    • Batch Wrapper
  • Master File/Registry Infrastructure(MFMI)
    • This adds artifacts to the Message Control Act Infrastructure, and is dependent upon it.
  • Query Infrastructure(QUQI)

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Messaging

Type

Normative, ANSI Standard

Releases

  • ANSI/HL7 V3 IM, R1-2004
  • UVAI: Infrastructure Management - Message Control Act Infrastructure
  • UVCI: Infrastructure Management - Transmission Infrastructure
  • ANSI/HL7 V3 MFMI, R1-2006; HL7 MFMI, R2. HL7 Version 3 Standard: Master File - Registry Infrastructure, Release 2

Last Ballot: DSTU Ballot 1 - September 2008

Summary

The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions.

This domain addresses the following aspects about the communications environment that is considered common to all HL7 Version 3 messaging implementations:

A specification for the composite HL7 version 3 message A protocol for reliable message delivery Generic "Communication Roles" that support the modes of HL7 messaging Message control events that describe a framework for generic HL7 messaging

This document focuses on the development and management of the infrastructure of the V3 standard. It includes information from the Transmission Infrastructure, Control Act Infrastructure, Master File Infrastructure and the Query Infrastructure domains.

Description

Scope: Message control in the HL7 Version 3 messaging standard addresses

  • The HL7 domain content for transport
  • The identification of sending and receiving entities for an HL7 messaging interaction.
  • The relationship between interactions and generic "communication roles"
  • Generic Communication Environment for HL7 Messaging in Version 3

The primary purpose of the HL7 messaging standard is to support the exchange of common information content between healthcare applications. As a protocol at Level Seven of the ISO Open Systems Interconnection (OSI) model, HL7 relies upon well-defined protocols at the lower layers for mechanisms that ensure correct and complete packaging and delivery of message content.

A generic communication environment for HL7 messaging has the following characteristics:

  • A specification for messages that supports the routing of messages to their specified destination(s)
  • A protocol for reliable message delivery that can support
  • An acknowledgment mode indicating if a message was delivered for subsequent processing
  • An acknowledgment mode indicating if a message was delivered to a specific application that acknowledges the receipt with or without a response prepared to return to the originating application
  • An optional sequence number protocol to ensure messages are processed in a specific order when necessary
  • Error handling rules for use cases consistent with HL7 messaging
  • Security services that are consistent with the current technology capabilities

To implement HL7 Version 3 messaging, the Version 3 messaging standard must be able to

  • specify how messaging communications should be conducted
  • respond to exceptions or errors that are experienced by a generic messaging framework that is processing an HL7 messaging interaction

Business Case (Intended Use, Customers)

Benefits

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Infrastructure and Messaging

Education

Certification Available
  • none

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development

  • There are no current projects
    • Infoway is in the process of identifying how SAEAF/SOA work through the first service specifications.
    • Seems to be an overlap with SOAP wrappers.
    • Infoway will be looking at this in January 2010 to discuss plans at the Phoenix 2010 WGM.
Retrieved from "https://wiki.hl7.org/w/index.php?title=Product_IM&oldid=28440"