Product Brief - HL7 V3: Infrastructure Management
- 1 Product Brief - HL7 V3: Infrastructure Management
- 1.1 Product Name
- 1.2 Topics
- 1.3 Standard Category
- 1.4 Integration Paradigm
- 1.5 Type
- 1.6 Releases
- 1.7 Summary
- 1.8 Description
- 1.9 Business Case (Intended Use, Customers)
- 1.10 Benefits
- 1.11 Implementations/ Case Studies (Actual Users)
- 1.12 Resources
- 1.13 Relationship to/ Dependencies on, other standards
- 1.14 Links to current projects in development
HL7 V3: Infrastructure Management - R1
- 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)
- Health Information Exchange Standards
Normative, ANSI Standard
- 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
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.
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)
Implementations/ Case Studies (Actual Users)
- See more at http://www.hl7.org/implement/training.cfm
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.