| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Benefits of V3 to HL7 |
|
| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Benefits of V3 to HL7 |
|
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
TCP/IP HL7 V3 Adapter Collaborations
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
Following are the benefits.
Reduces optionality that results in more specific messages
Uncovers hidden assumptions about application boundaries
Facilities defining clear, fine-grained, conformance claims
The HL7 V3 specification contains the XSDs for Interactions which can be used to construct the composite HL7 V3 message. This composite message then can be transmitted between the systems. The V3 Specification says that a system can claim for V3 conformance based on the Application Role it will play in a particular domain. The system playing the Application Role will recognize the Trigger Events, the message types and the data content of these messages. Thus a system whose sole responsibility is to exchange the V3 data between systems reliably should claim conformance for the Application Roles defined under Transmission Infrastructure Domain.
|