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 chunks if you select the Split payload into chunks option in the healthcare action. This option 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 option splits it into chunks for processing, such 1 MB for each native chunk or 1000 messages, whichever comes first. The split into smaller chunks occurs before translation from the native payload into XML format.

For example, if you have a payload that is more than 3 MB, but less than 4 MB is size, the chunking occurs as follows:
  • Three chunks are created that are each 1 MB in size
  • One chunk is created for the remaining 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.