Skip to content

Latest commit

 

History

History
21 lines (17 loc) · 3.15 KB

File metadata and controls

21 lines (17 loc) · 3.15 KB
description title ms.date ms.service ms.topic
Learn more about: Validating Messages
Validating Messages
06/08/2017
biztalk-server
article

Validating Messages

Microsoft BizTalk Accelerator for HL7 ([!INCLUDEbtaBTAHL71.3abbrevnonumber]) supports sending acknowledgments (ACK) for inbound messages from an application or trading partner in the form of an HL7 XML receipt that might need conversion to an HL7 encoded ACK message. [!INCLUDEbtaBTAHL71.3abbrevnonumber] typically generates a receipt after it checks the inbound message against the relevant inbound (trading-partner format) document specification. When all the segments pass validation, [!INCLUDEbtaBTAHL71.3abbrevnonumber] returns a receipt that indicates acceptance to the application. Otherwise, [!INCLUDEbtaBTAHL71.3abbrevnonumber] generates a receipt indicating error or failure/reject.

The [!INCLUDEbtaBTAHL71.3abbrevnonumber] ACK transmission reports syntactical and schematic errors against the HL7 standard. If the validation fails, [!INCLUDEbtaBTAHL71.3abbrevnonumber] places the document in the suspended message queue and returns a receipt detailing the rejection. The [!INCLUDEbtaBTAHL71.3abbrevnonumber] parser performs validation that involves checking data types, syntax, and the schema validation. [!INCLUDEbtaBTAHL71.3abbrevnonumber] records any schematic errors that occur in parsing in the receipt along with the location details.

At configure time, you need to create the [!INCLUDEbtsBizTalkServerNoVersion] artifacts required for responding with an ACK. The [!INCLUDEbtaBTAHL71.3abbrevnonumber] parser creates the HL7 canonical ACK XML instance. BizTalk converts this to the required version format in an appropriate BizTalk map and validates the destination format. The [!INCLUDEbtaBTAHL71.3abbrevnonumber] serializer then converts the message into an HL7-encoded instance.

Note

If there is a conflict between the delimiters of an inbound message and those specified in the [!INCLUDEbtaBTAHL71.3abbrevnonumber] configuration, then [!INCLUDEbtaBTAHL71.3abbrevnonumber] will generate an ACK message that uses the same delimiters of the inbound message and overrides the configuration settings.

See Also

Creating and Processing Acknowledgments
Programming Guide
ACK Message Modes