| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: MLLP V2 Content Exchange Model |
|
| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: MLLP V2 Content Exchange Model |
|
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
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
MLLP Release 2 is a reliable Message Transport protocol. It guarantees In Order delivery and At Least Once delivery of HL7 Content. HL7 Content is framed in a Block and sent to the Destination system. The Destination system acknowledges the receipt of the message by returning a Commit Acknowledgement message. The MLLP V2 acknowledgement protocol is synchronous: the Source system shall not send new HL7 content until an acknowledgement for the previous HL7 Content has been received.
All HL7 Content (of any kind or type) is framed in a Block and sent to the Destination system. The Destination system acknowledges the receipt of the Block by returning a Commit Acknowledgement message. If the HL7 Content (a query in the example below) triggers the sending of HL7 Content (a Response) by the Destination system, then this HL7 Content is framed in a Block and sent. MLLP has no knowledge of the HL7 Content, nor does it base any part of its behavior on HL7 Content.
In HL7 adapter, a database is used to persist the message.
In Inbound Mode, once the message is received by the HL7 adapter, it is persisted into the database and a commit acknowledgement is sent to the sender before the HL7 message is passed to the collaboration level. If the persistence fails, a negative acknowledgement is sent to the sender and the collaboration receives null as its message. Inside the collaboration, the message received is null, the collaboration returns without proceeding.
If the message received is a duplicate message, and if an ACK/NAK is already available in the persistence database, the same is retrieved from the database sent to the sender. The collaboration receives null as the received message.
In Outbound Mode, the message is sent to the sender and waits for the commit acknowledgement and/or negative acknowledgement from the receiver. If the adapter receives a negative acknowledgement, the message is sent again until the configured Maximum Number of Retries is made.
|