| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: TCP/IP HL7 V3 Adapter Collaborations |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
TCP/IP HL7 Adapter Collaborations Overview
TCP/IP HL7 Adapter Task Overview
TCP/IP HL7 V2 Adapter Collaborations
Inbound HL7 V2 Collaboration Overview
Outbound HL7 V2 Collaboration Overview
Creating a Copy of an HL7 V2 Project
Customizing Predefined Collaborations for HL7 V2
Creating Copies of an HL7 V2 Collaborations
To Create Copies of an HL7 V2 Collaborations
Adding HL7 V2 OTD to an Existing Collaboration
To Add HL7 V2 OTD to an Existing Collaboration
Artifact Identification System
HL7 V3 Message Development Process
Transmission Wrapper and Control Act Wrapper
Comparison between HL7 V2.x and HL7 V3
Inbound HL7 V3 Immediate Collaboration Overview
Inbound HL7 V3 Deferred Collaboration Overview
Outbound HL7 V3 Collaboration Overview
Creating a Copy of an HL7 V3 Project
Customizing Predefined Collaborations for HL7 V3
Creating Copies of an HL7 V3 Collaborations
Adding HL7 V3 OTD to an Existing Collaboration
To Add HL7 V3 OTD to an Existing Collaboration
MLLP V2 Content Exchange Model
Standard Inbound HL7 V2 Collaboration Overview over MLLPV2
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
HL7 V3, like V2.x, is a standard for exchanging messages among information systems that implement healthcare applications. However, V3 strives to improve the V2 process and its outcomes. The original process for defining HL7 messages was established in 1987. It has served well since. However, as HL7 membership grew and its standards became more widely used, HL7 has become aware of opportunities to revolutionize healthcare interface computing. HL7 interfaces substantially reduce costs and implementation times when compared to the industry's experience with proprietary interfaces. The development principles behind HL7 V3 lead to a more robust, fully specified standard.
V3 introduces a new approach to HL7 message development.
While the HL7 V2 standard was created mostly by clinical interface specialists, the V3 standard has been influenced strongly by work from volunteers representing the government and medical informatist users. This means that the level of formal modeling, complexity, and internal consistency is radically higher in V3 when compared to V2.
To assist with the comprehension of this new approach, the domain begins with a high-level overview and progressively drill down to lower levels of messaging detail (including storyboards, applications roles, trigger events, D-MIMs, R-MIMs, HMDs, message types, and interactions). Since a big picture understanding of the particular domain is crucial to understanding the messages defined within it, each domain provides a Storyboard.