Filter
Top Products
Version Code, Processing Code, Processing Mode Code, and Interaction ID. If these elds do
not match the conguration, a NAK is returned.
The Collaboration receives the HL7 V3 message from the external using
receiveHL7Message(). If an exception occurs due to incomplete data, and the adapter fails to
read the data within the congured number of retries, the associated recourse action is taken. If
the exception is due to no response, the associated recourse action is taken.
HL7 V3 Standard Inbound Message Mode Data Flow (For Immediate
Mode of ACK Process) — Part 2
If no exception occurs, validateHL7Message() is called, which validates the message to
determine whether to ACK or NAK the message. Other helper methods are also called to
validate the HL7 V3 message.
If the HL7 V3 message does not pass validation, the Collaboration calls makeNak() and
sendHL7Nak() to create and send the NAK to the external. The HL7 V3 message, with the NAK,
is archived to the error queue. If the number of consecutive NAKs sent surpasses the maximum
number of retries, the associated recourse action is taken.
If the HL7 V3 message passes validation, the Collaboration calls makeAck() and sendHL7Ack()
to create and send the ACK to the external.
After the ACK is sent, the HL7 V3 message and the ACK are journaled to the JMS queue journal
destination. If the message fails to journal the associated recourse action is taken.
AboutTCP/IPHL7V3Collaborations
SunAdapterforTCP/IPHL7User's Guide 125