Using the built-in HL7 TCP/IP Listener
Video: Creating A TCP/IP MLLP Listener
Creating a Schema Profile: Part 3
Found in Part 3 of your Schema Profile.
To use the listener just check the Receive HL7 Messages Over TCP/IP box in your Schema Profile.
Then enter a valid Port Number. Valid port numbers must be between 2048 and 65535.
Choose the Acknowledgement Settings. When the HL7 TCP/IP MLLP Listener receives a HL7 message, that message contains a flag in the MSH segment which will indicate whether the sender is expecting a HL7 ACK (Acknowledgement) message to be returned. This setting allows you to regulate that behavior a bit. You can select Automatic, which means to follow the instructions in the MSH segment. OR you can choose Always, which means IGNORE the MSH segment and always return an ACK. And finally, you can choose Never which means IGNORE the MSH segment and NEVER return an ACK.
Mirror the Control ID (MSH 10.1) in the Acknowledgement. The ACK message which is returned to the sender is actually a fully formed HL7 message in it's own right. By default when we create the ACK message we generate a new Message Control ID (MSH 10.1). You may come across a Trading Partner who wants you to "mirror" the control ID by using the same value (MSH 10.1) in the ACK as was used in the Message being acknowledged. NOTE: You can do this purely as a courtesy. The message control ID of the message being acknowledged is ALWAYS found in the MSA segment of the ACK message.
Include the Message Event (MSH 9.2) in the Acknowledgement. This is another setting which you can use as a courtesy if requested by a Trading Partner. In the HL7 ACK message, the Message Type (MSH 9.1) is always ACK, and there is no Message Event (MSH 9.2). A client may want you to mirror the value from the source message Message Event (MSH 9.2) in the ACK message Message Event (MSH 9.2). There is no valid HL7 compliance rule for doing this, but we provide it as a courtesy you can offer.