Skip to content
LambogeniusDocs

HL7 MLLP Connector for Azure Logic Apps

HL7 batches

How FHS/BHS batches are split, kept whole, or rejected, and how batch ACKs are built.

Service provider/serviceProviders/lamboHl7MllpLicensed together with the HL7 v2 Codec. One token covers both.

Batch modes

A frame holding [FHS] BHS {MSH ...} BTS [FTS] is a batch. The trigger's (or gateway listener's) batch mode decides what happens:

Batch modeBehaviour
Split (default)Like the BizTalk HL7 disassembler: each message starts its own run, in order, and the sender gets one batch ACK (BHS with BHS-12 = the original BHS-11, one ACK per message, BTS). Runs get batchControlId, batchIndex and batchCount. One batch can hold AA and AE.
SingleOne run for the whole batch: isBatch is true and messages lists each message with its MSH fields. Workflow acknowledgement mode always works this way; Send acknowledgement with an ACK code then builds the batch ACK.
RejectAR/CR for every message.
  • Sending a batch: Send message accepts one; its output has isBatch, messageCount and acknowledgements (one entry per MSA), and each MSA-2 must belong to the batch.
  • Create acknowledgement returns a batch ACK when given a batch.
  • Limit: a frame may hold one batch (one BHS).