HL7 v2.x MLLP Sender
The HL7 v2.x MLLP Sender configuration category includes the following configurable options:
Transport Protocol
HL7 v2.x Destination Host
HL7 v2.x Destination Port
Request Path
Send Timeout (millis)
Map Identifiers using NamingSystem
Use Persisted Message Headers
Retry message on NAK
Delay Between Failed Deliveries (millis)
|
|
|
| ENUM | |
| Values |
|
| Specifies the transport to use when sending HL7 v2.x messages. Note that most existing systems expect the MLLP protocol unless specifically configured otherwise. | |
MLLP_OVER_TCP
|
|
| No |
|
|
|
| STRING | |
| The TCP hostname to which this module will transmit. | |
| (no default) | |
| No |
|
|
|
| POSITIVE_INTEGER | |
| The TCP port to which this module will transmit. | |
| (no default) | |
| No |
|
|
|
| STRING | |
| The path to transmit messages to. Note that this applies only to HTTP transports and will be ignored for MLLP transports. | |
/
|
|
| No |
|
|
|
| POSITIVE_INTEGER | |
| The number of milliseconds to wait for a response before timing out. | |
10000
|
|
| Yes |
|
|
|
| BOOLEAN | |
| If enabled, the FHIR -> HL7 v2.x mapper will attempt to use NamingSystem resources stored in the repository when mapping identifiers. See NamingSystem Mapping for information on this process. | |
false
|
|
| Yes |
|
|
|
| BOOLEAN | |
| If enabled, this setting causes the FHIR -> HL7 v2.x mapper to attempt to load a MessageHeader resource from FHIR Storage for use in populating the MSH segment on the generated HL7 v2.x message. | |
false
|
|
| No |
|
|
|
| BOOLEAN | |
If the receiving system responds with a non-positive acknowledgement message (e.g an ACK message with an AE response code), should we attempt to redeliver the message until we are successful?
|
|
true
|
|
| Yes |
|
|
|
| NON_NEGATIVE_INTEGER | |
| If set to a number above 0, sets the minimum number of milliseconds to wait after a failed delivery attempt before trying again. | |
10000
|
|
| Yes |