Users will be unable to turn off some functionality for message reader, to gain performance. The functionalities that cannot be turned off are configurable response and message
Resolving the problem
This change reintroduces functionality from the pre 9.x code line. By enabling aggregate mode the user will turn off message validation by the message reader and the ability for the message reader to have a configurable response. This mode is strongly suggested to be turned off unless there is no need for message validation and no need for a configurable response.
New Madconfig Prompts:
Should the Inbound Reader Interface run in aggregate mode(n is recommended)?
Is the Inbound Interface HL7v3 message an HL7v2 over v3 Message?
Aggregate Mode Parameter:
HL7 Version Parameter:
Message Reader Response:
If aggregate mode is enabled then the message reader will send the following hard coded responses based on the message type:
Fixed: "OK "
HL7v2 over v3:"<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?><ACK><MSA><MSA.1>AA</MSA.1></MSA></ACK>
HL7v3: <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?><MCCI_IN000002><acknowledgement><typeCode code="CA" ></typeCode></acknowledgement></
XML: <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?><EmpiResp><MsgHeader><code>ok</code></MsgHeader></EmpiResp>