Thread template
To facilitate the configuration of complex thread definitions, you can use a thread template.
Use a template to set up the thread configuration. To create a new thread, instead of starting from scratch, you can specify a template that matches your requirement. Fields such as Port are clearly marked, for example, <enter-port-number-here>, for user-supplied variables.
You can also create a template from an existing thread.
The supplied templates are:
- HL7_MLLP_TCP_INBOUND
- Listens for connections on a specified port
- Expects HL7 messages that are encapsulated in MLLP wrapper
- Messages starting with MSH are ACK’d with HL7 AA
- Messages not starting with MSH are NAK’d with HL7 AE
- HL7_MLLP_TCP_OUTBOUND
- Connects to remote system on specified port and IP
- Sends HL7 messages that are encapsulated in MLLP wrapper
- Expects MLLP-encapsulated acknowledgment; any replies are stopped
- HL7_MLLP_TCP_OUTBOUND_VALIDATION
- Connects to remote system on specified port and IP
- Sends HL7 messages that are encapsulated in MLLP wrapper
- Expects MLLP-encapsulated HL7 acknowledgment
Action is taken based on reply type:
- AA or CA: Stop reply and send next message
- AE or CE: Put original message in error database, stop reply, send next message
- AR" or CR: Resend original message up to three times. If more than three AR or CR are received, then treat as AE
- CL_to_CL_INBOUND and
CL_to_CL_OUTBOUND
Sets up a thread-to-thread connection.
- Length encoded TCP/IP
- IB has standard ACK
- OB has recovery and ACK validation
- Used for Query/Response connections to be created
- Uses queuing and memory for fast hand-off
- Permits multi-server connections
- Faster than TCP/IP hand-off, where milliseconds are important in a Query/Response
The template settings are saved as template file under the folder $HCIROOT/templates/NetConfig.
The specific name has a _template suffix as the actual file name. For example, template file HL7_NCK_template.
The structure of the thread template matches that in NetConfig.