Handle Inbound Debatching of Large HL7 Message Payloads

If your inbound HL7 message includes a large payload, you can debatch (split) the payload into manageable messages if you select the Split payload into chunks operation in the healthcare action. This operation enables your inbound message to be successfully converted to XML format without errors in the healthcare action.

Because the native payload size can be large, the Split payload into chunks operation enables you to split the payload into smaller messages for processing. You can specify the number of messages into which to split the payload and the size for each message. The split into smaller messages occurs before translation from the native payload into XML format. For example, assume you have a payload that is 4 MB is size. You can specify to split the message into 4 messages, each of 1 MB in size.

The following types of inbound message format are supported for debatching of large payloads.
Supported Message Format How Debatching Works

A payload that contains multiple batch headers within a file header and multiple message header segments within a batch header:

[File Header]
{ [Batch Header]
{ [Message Header Segment ] }
[Batch Trailer]
}
  • Elements in a file header segment and batch header segment are gathered and each individual message header segment is debatched for the transaction.
  • The information (file header, batch header, and message header segment transaction) is passed to the healthcare action for conversion.
  • The HL7 (message header segment transaction) format is then converted into XML format and the values from the file header, batch header, file trailer, and batch trailer are set in headers and trailers when the transformed XML is returned from the healthcare action.

A batch payload that contains multiple message header segments:

{ [Message Header Segment for HL7 Message ] }
  • Each message header segment for the HL7 message transaction is passed to the healthcare action.
  • The healthcare action returns HL7 in XML format without header and trailer information because the incoming batch does not have file header, batch header, file trailer, and batch trailer segment information.

See Convert HL7 Messages with a Healthcare Action.